Re: auto-packing on kernel.org? please?

From: Catalin Marinas <catalin.marinas@gmail.com>
Date: Nov 23, 2005, 14:18 UTC
Message-ID: <b0943d9e0511230618u31d80e57v@mail.gmail.com>
In-Reply-To: <4383610D.7080100@citi.umich.edu>

On 22/11/05, Chuck Lever <cel@citi.umich.edu> wrote:

Show 8 quoted lines

> Linus Torvalds wrote:
> > But maybe that's what stgit wants (since they are "temporary"), but it
> > does mean that if you see a big advantage from packing, you might be
> > losing some of it.
>
> actually, those commits aren't all that "temporary".  the
> history/revision feature i'm working on would like to maintain all the
> commits ever done to an StGIT patch.

That's to avoid pruning them but you might not always want to add them to a pack.

Show 7 quoted lines

> the only time you can throw away such commits is when the patch is
> deleted or when it is finally committed to the repository via "stg
> commit".  otherwise, keeping these commits in a pack would be quite a
> good thing.
>
> maybe the first thing to do is to get a basic understanding of an StGIT
> commit's lifetime.

My initial idea was to throw the old commit away once a patch is refreshed. Even if you want to preserve the history, it would be only preserved until you send the patch to be merged upstream and you would delete it locally. If all the patches are meant to be sent upstream at some point, you can avoid packing them.

-- Catalin