From: Joe Perches <joe@perches.com>
To: linux-next <linux-next@vger.kernel.org>
Subject: RFC: Removing old tags, reducing the git size of -next.
Date: Tue, 01 Mar 2011 20:22:26 -0800 [thread overview]
Message-ID: <1299039746.4208.28.camel@Joe-Laptop> (raw)
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.
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?
next reply other threads:[~2011-03-02 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 4:22 Joe Perches [this message]
2011-03-02 5:54 ` RFC: Removing old tags, reducing the git size of -next Stephen Rothwell
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=1299039746.4208.28.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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