Re: auto-packing on kernel.org? please?
- From
Linus Torvalds <torvalds@osdl.org>
- Date
- Nov 22, 2005, 17:05 UTC
- Message-ID
- <Pine.LNX.4.64.0511220904040.13959@g5.osdl.org>
- In-Reply-To
- <b0943d9e0511220613h5978a600l@mail.gmail.com>
On Tue, 22 Nov 2005, Catalin Marinas wrote:
Show 8 quoted lines
> > > The preferred way would be to just list the references somewhere under > > .git/refs/stgit, in which case fsck and repack should pick them up > > automatically (so clearly stgit doesn't do that right now ;). > > I thought about adding .git/refs/patches/<branch>/* files > corresponding to the every StGIT patch. Are the above git commands > looking at all depths in the .git/refs/ directory?
Yes. Or at least they're supposed to. If they are not, it's a bug regardless, and we'll fix it.
Show 8 quoted lines
> The 'git repack -a' command would include the applied patches in the > newly created pack but leave out the unapplied ones. It would be even > better to leave all of them out since the StGIT patches are frequently > changed but an independent mechanism for this would complicate GIT - > 'git repack' shouldn't pack any of the objects found in > .git/refs/patches/, even if they are reachable via .git/refs/heads/* > (and maybe call the patches directory something like > .git/refs/unpackable or volatile).
If we have some default location (and .git/refs/patches/ sounds good), we can make git do the right thing - find them for git-fsck-objects, and ignore them for git-repack.
Linus