| commit | 1f9db6a4fa73f476cf4efc8c0f26b6acc1ac6e2b | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 29 Jun 2008 07:59:19 +0000 (29 03:59 -0400) | ||
| committer | Robin Rosenberg <robin.rosenberg@dewire.com> | |
| Mon, 30 Jun 2008 22:46:22 +0000 (1 00:46 +0200) | ||
| tree | 79c57fac2dcccdc8a94cd6a5a788e9a1fb8c40d5 | treesnapshot (tar.gz zip) |
| parent | 9ccfde23263145cdf49f094e00530e2350407437 | commitdiff |
Remember how a Ref was read in from disk and created
To efficiently deleted or update a ref we need to know where
it came from when it was read into the process. If the ref
is being updated we can usually just write the loose file,
but if it is being deleted we may need to remove not just a
loose file but also delete it from the packed-refs.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
To efficiently deleted or update a ref we need to know where
it came from when it was read into the process. If the ref
is being updated we can usually just write the loose file,
but if it is being deleted we may need to remove not just a
loose file but also delete it from the packed-refs.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>