From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joe Perches <joe@perches•com>
Cc: linux-next <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>,
users@kernel•org
Subject: Re: RFC: Removing old tags, reducing the git size of -next.
Date: Wed, 2 Mar 2011 16:54:47 +1100 [thread overview]
Message-ID: <20110302165447.f47fd4b2.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1299039746.4208.28.camel@Joe-Laptop>
[-- 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 --]
next prev parent reply other threads:[~2011-03-02 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 4:22 RFC: Removing old tags, reducing the git size of -next Joe Perches
2011-03-02 5:54 ` Stephen Rothwell [this message]
2011-03-08 15:29 ` Michal Marek
2011-03-08 16:23 ` Stephen Rothwell
2011-03-09 9:41 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110302165447.f47fd4b2.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=joe@perches$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=users@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox