Re: RFC: Removing old tags, reducing the git size of -next.

Re: RFC: Removing old tags, reducing the git size of -next.

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

Hi Joe,

On Tue, 01 Mar 2011 20:22:26 -0800 Joe Perches <joe@perches.com> wrote:
>
> I personally do not find git history to be very useful
> for the next tree.  The collected next tree history
> also makes the repository fairly large and unwieldy to
> use on smaller development systems.

Yeah, I have been thinking about this again recently.

> Would it be reasonable to create a separate history tree
> for -next every once in awhile and have say a maximum of
> a few weeks of next history in the current tree?

I could easily have a tree that is historical and contains what the
current linux-next tree contains while also removing old stuff from the
normal linux-next tree (I could push into both each day).  The only
connection between the daily releases is the "history" branch which,
frankly, does not serve any purpose and I will remove.

The main thing stopping me from doing this right now is that there are
several git repositories on master.kernel.org that use the linux-next
tree as an alternate.   They should not be doing this, but it has been
safe up until now since nothing has ever been removed from the linux-next
tree.  If I did the clean up right now, those trees would be severely
broken.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: RFC: Removing old tags, reducing the git size of -next.

[Michal Marek]

On 2.3.2011 06:54, Stephen Rothwell wrote:
> Hi Joe,
> 
> On Tue, 01 Mar 2011 20:22:26 -0800 Joe Perches <joe@perches.com> wrote:
>>
>> I personally do not find git history to be very useful
>> for the next tree.  The collected next tree history
>> also makes the repository fairly large and unwieldy to
>> use on smaller development systems.
> 
> Yeah, I have been thinking about this again recently.
> 
>> Would it be reasonable to create a separate history tree
>> for -next every once in awhile and have say a maximum of
>> a few weeks of next history in the current tree?
> 
> I could easily have a tree that is historical and contains what the
> current linux-next tree contains while also removing old stuff from the
> normal linux-next tree (I could push into both each day).  The only
> connection between the daily releases is the "history" branch which,
> frankly, does not serve any purpose and I will remove.

FWIW, I use the following setup for linux-next:

[remote "linux-next"]
        url =
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
        fetch = +refs/heads/master:refs/heads/linux-next
        fetch = +refs/heads/stable:refs/remotes/linux-next/stable
        tagopt = --no-tags

and fetch the next-* tags manually only when I need them.

Michal

Re: RFC: Removing old tags, reducing the git size of -next.

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 770 bytes --]

Hi Michal,

On Tue, 08 Mar 2011 16:29:29 +0100 Michal Marek <mmarek@suse.cz> wrote:
>
> FWIW, I use the following setup for linux-next:
> 
> [remote "linux-next"]
>         url =
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git

This should now be
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(its the same repository, just a more generic name).

>         fetch = +refs/heads/master:refs/heads/linux-next
>         fetch = +refs/heads/stable:refs/remotes/linux-next/stable
>         tagopt = --no-tags
> 
> and fetch the next-* tags manually only when I need them.

That should all continue to work.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: RFC: Removing old tags, reducing the git size of -next.

[Michal Marek]

On 8.3.2011 17:23, Stephen Rothwell wrote:
> Hi Michal,
> 
> On Tue, 08 Mar 2011 16:29:29 +0100 Michal Marek <mmarek@suse.cz> wrote:
>>
>> FWIW, I use the following setup for linux-next:
>>
>> [remote "linux-next"]
>>         url =
>> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> 
> This should now be
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (its the same repository, just a more generic name).
> 
>>         fetch = +refs/heads/master:refs/heads/linux-next
>>         fetch = +refs/heads/stable:refs/remotes/linux-next/stable
>>         tagopt = --no-tags
>>
>> and fetch the next-* tags manually only when I need them.
> 
> That should all continue to work.

I probably quoted the wrong part of your email. I wanted to show that
the full history of linux-next is not forced on anyone; git can be
configured to only fetch the latest state and leave the previously
fetched states to the garbage collector.

Michal