From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove BK docs ... + x86-64 2.5.8 sync
Date: Sat, 20 Apr 2002 21:44:20 +0200 [thread overview]
Message-ID: <20020420214420.A13635@wotan.suse.de> (raw)
In-Reply-To: <p73u1q68cfu.fsf_-_@oldwotan.suse.de> <Pine.LNX.4.33.0204201230140.11732-100000@penguin.transmeta.com>
On Sat, Apr 20, 2002 at 12:33:26PM -0700, Linus Torvalds wrote:
>
> > I don't want to use BitKeeper because I don't like open logging. I hope
> > I can continue to maintain the x86-64 port even without being part
> > of the inner bitkeeper circle.
>
> Absolutely - as you noticed I accepted the patch, even though there was a
> clash (with a released kernel) in there.
What clash was there? (just curious) I just checked and at least the
kernel.org finger still shows 2.5.8 as the latest released kernel.
>
> > It would be good if you did e.g.
> > a pre patch for every change that could require action from architecture
> > or other maintainers as sync point (i guess that could be made easy with
> > the appropiate script)
>
> This is why I think it might be a good reason to just have a daily script:
> not just to create the patches, but also to kind of keep a running
> commentary on the kernel list on what I've merged..
Would be fine for me.
-Andi
next prev parent reply other threads:[~2002-04-20 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E16ycFR-0000Vg-00@starship.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0204201039130.19512-100000@home.transmeta.com.suse.lists.linux.kernel>
2002-04-20 18:14 ` Andi Kleen
2002-04-20 19:33 ` Linus Torvalds
2002-04-20 19:44 ` Andi Kleen [this message]
2002-04-20 23:14 ` Linus Torvalds
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=20020420214420.A13635@wotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®