From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3-mm2
Date: Tue, 03 May 2005 12:08:40 -0400 [thread overview]
Message-ID: <4277A208.8000309@tmr.com> (raw)
In-Reply-To: <20050501222630.2fed0bd7.akpm@osdl.org>
Andrew Morton wrote:
> James Cloos <cloos@jhcloos.com> wrote:
>
>>Apologies if this has already been asked and I missed it, but do you
>>expect to transition to exporting your working tree via git, now that
>>licensing concerns are not part of the equation?
>>
>
>
> Nope. At any particular point in time the tree I have here has lots of
> problems - failing to compile, crashing, etc. It takes me from four hours
> to three days just to get a halfway-respectable release out the door.
>
> So there's no way in which I'd want to make the tree-of-the-minute
> externally available - it would muck people around too much and would cause
> me to get a ton of email about stuff which I'd probably already fixed.
>
> That, plus a traditional SCM is an inappropriate format for something like
> -mm. This tree is a series of patches against Linus's tree - that's how it
> is developed, tested and sent upstream. Patches get added, dropped,
> reordered and merged at any time. It's hard to explain - you need to have
> used patch-scripts or quilt for a while...
>
> Prematurely flattening all this into an SCM view is a fairly pointless
> exercise - the only reason for doing it would be for people to be able to
> download it. And they can do that by grabbing the single diff anyway. I
> suppose someone might start offering git -mm trees sometime, as an
> alternative to grabbing the diff file.
For all of the reasons you describe putting up your tree would be a
waste of time, and putting up another tree is likely to only result in
duplicated effort; the folks who want SCC can use whatever works for
them and then send you patches.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-05-03 16:22 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 23:43 2.6.12-rc3-mm2 Andrew Morton
2005-05-01 0:27 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 0:37 ` 2.6.12-rc3-mm2 Andrew Morton
[not found] ` <40f323d00504301753140a7ef4@mail.gmail.com>
2005-05-01 1:12 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 2:32 ` 2.6.12-rc3-mm2 - /proc/ide/sr0/model: No such file or directory Jesper Juhl
2005-05-03 3:11 ` Greg KH
2005-05-03 3:18 ` Andrew Morton
2005-05-03 4:48 ` Greg KH
2005-05-03 7:11 ` Bartlomiej Zolnierkiewicz
2005-05-03 18:27 ` Greg KH
2005-05-01 3:30 ` [patch] alternative fix for VFS race (was Re: 2.6.12-rc3-mm2) Nick Piggin
2005-05-01 12:56 ` 2.6.12-rc3-mm2: ACPI problems Rafael J. Wysocki
2005-05-01 13:41 ` Brice Goglin
2005-05-01 15:07 ` 2.6.12-rc3-mm2 - kswapd0 keeps running Damir Perisa
2005-05-01 22:06 ` Andrew Morton
2005-05-02 6:01 ` Damir Perisa
2005-05-02 15:31 ` Damir Perisa
2005-05-02 18:14 ` Andrew Morton
2005-05-02 21:30 ` Damir Perisa
2005-05-06 18:07 ` Damir Perisa
2005-05-04 19:12 ` Cameron Harris
2005-05-04 21:47 ` Damir Perisa
2005-05-01 15:08 ` 2.6.12-rc3-mm2: ppc pte_offset_map() Sean Neakums
2005-05-01 15:50 ` Jesper Juhl
2005-05-01 22:46 ` Andrew Morton
2005-05-01 23:01 ` Jesper Juhl
2005-05-03 22:04 ` cliff white
2005-05-02 10:14 ` Hugh Dickins
2005-05-01 22:29 ` 2.6.12-rc3-mm2: fs/proc/task_mmu.c warnings Adrian Bunk
2005-05-02 22:30 ` Mauricio Lin
2005-05-02 23:35 ` Mauricio Lin
2005-05-02 23:45 ` Andrew Morton
2005-05-02 23:56 ` Mauricio Lin
2005-05-03 20:16 ` cliff white
2005-05-03 22:12 ` Mauricio Lin
2005-05-03 18:02 ` Cliff White
2005-05-02 5:07 ` 2.6.12-rc3-mm2 James Cloos
2005-05-02 5:26 ` 2.6.12-rc3-mm2 Andrew Morton
2005-04-30 21:34 ` 2.6.12-rc3-mm2 Diego Calleja
2005-05-03 16:08 ` Bill Davidsen [this message]
2005-05-03 13:37 ` 2.6.12-rc3-mm2 Barry K. Nathan
2005-05-04 15:12 ` 2.6.12-rc3-mm2 Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-05-01 10:10 2.6.12-rc3-mm2 Mikael Pettersson
2005-05-01 10:27 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 12:51 ` 2.6.12-rc3-mm2 Benoit Boissinot
2005-05-01 20:11 2.6.12-rc3-mm2 Rogério Brito
2005-05-01 20:26 ` 2.6.12-rc3-mm2 Jesper Juhl
2005-05-01 21:35 ` 2.6.12-rc3-mm2 Rogério Brito
2005-05-02 0:37 ` 2.6.12-rc3-mm2 Benjamin Herrenschmidt
2005-05-02 8:34 ` 2.6.12-rc3-mm2 Rogério Brito
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=4277A208.8000309@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@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