From: Mariusz Kozlowski <mk@lab.zgora.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.0-rc1
Date: Mon, 30 May 2011 22:03:29 +0200 [thread overview]
Message-ID: <20110530200329.GA1833@mako-laptop> (raw)
In-Reply-To: <BANLkTinsO2=tO_UyzzgeU6LE1fObgq+p1Q@mail.gmail.com>
On Sun, May 29, 2011 at 06:47:57PM -0700, Linus Torvalds wrote:
[...]
> However, I did *not* rename the git tree, because that would just be a
> huge inconvenience to git users, so it's still in the same old place
> and yes, that means that my git tree is still called "linux-2.6.git"
> on kernel.org. But it has the v3.0-rc1 tag in it.
>
> I'll probably add a symlink or something, if people really hate being
> reminded about our long history with the "2.6" numbering. But that
> won't be until closer to the real release, methinks.
You could consider freezing linux-2.6.git repository and creating new
linux-3.git repository that would serve for a couple of years until
linux-4.git. At the same time development history could be dropped between
trees so that inital clones are lighter. Anyone interested in history
can download idx/pack from linux-2.6.git repo and attach it using gratf
point[1] anyway.
Pros:
- obvious naming scheme wrt repository contents
- smaller initial clone
- new clean tag namespace
Cons:
- broken bisection for some time
- impaired log/blame/whatchanged and friends
Cons can be fixed by attaching history when needed.
[1] https://git.wiki.kernel.org/index.php/GraftPoint
--
Mariusz Kozlowski
next prev parent reply other threads:[~2011-05-30 20:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 1:30 Linux 3.0-rc1 Linus Torvalds
2011-05-30 1:47 ` Linus Torvalds
2011-05-30 2:29 ` Américo Wang
2011-05-30 6:38 ` Boaz Harrosh
2011-05-30 20:03 ` Mariusz Kozlowski [this message]
2011-05-30 22:48 ` david
2011-05-31 5:40 ` Mariusz Kozlowski
2011-05-31 7:25 ` Geert Uytterhoeven
2011-05-30 1:59 ` Rafael J. Wysocki
2011-05-30 15:07 ` Steven Rostedt
2011-05-30 2:04 ` Greg KH
2011-05-30 6:39 ` Tarkan Erimer
2011-05-30 9:46 ` Miles Bader
2011-05-30 10:09 ` Anca Emanuel
2011-05-30 10:37 ` Pekka Enberg
2011-05-30 12:03 ` Wanlong Gao
2011-05-30 12:05 ` Zhang, Shijie
2011-05-30 12:58 ` Valdis.Kletnieks
2011-05-30 2:07 ` CaT
2011-05-30 6:01 ` Arkadiusz Miskiewicz
2011-05-30 6:43 ` [GIT PULL] small perf fix for v3.0-rc1 Ingo Molnar
2011-05-30 13:38 ` Linux 3.0-rc1 Camille Moncelier
2011-05-30 14:07 ` 15Hz
2011-05-30 14:33 ` trapDoor
2011-05-30 20:33 ` Mustapha Rabiu
2011-05-30 20:50 ` Valdis.Kletnieks
2011-05-31 5:59 ` Benjamin Herrenschmidt
2011-05-31 10:34 ` Steven Rostedt
2011-05-31 6:01 ` Dave Airlie
2011-05-31 9:23 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2011-05-30 9:28 Sedat Dilek
2011-05-31 19:27 ` Sedat Dilek
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=20110530200329.GA1833@mako-laptop \
--to=mk@lab.zgora.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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