From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] new bitkeeper tree for 2.5 linux/ia64 kernel
Date: Wed, 14 May 2003 23:53:56 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705811@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705780@msgid-missing>
On Wed, 14 May 2003 10:27:02 -0700,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On 14 May 2003 09:37:54 -0400, Jes Sorensen <jes@wildopensource.com> said:
>
>>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
> David> My hidden agenda is of course to encourage more folks to keep
> David> pushing fixes back to Linus, so that by the time 2.6 comes
> David> around, the ia64 kernel will build directly from Linus' source
> David> tree. We're actually reasonably close at the moment.
>
> Jes> Just to be sure, your hidden agenda doesn't include a clause about no
> Jes> longer releasing patches on a regular basis?
>
>Not at all. BitKeeper isn't Open Source and I'm certainly not going
>to force anybody into using it.
Are you going to set up the automatic patch extraction from this tree,
like ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.4/testing/cset?
next prev parent reply other threads:[~2003-05-14 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 8:01 [Linux-ia64] new bitkeeper tree for 2.5 linux/ia64 kernel David Mosberger
2003-05-14 13:37 ` Jes Sorensen
2003-05-14 17:27 ` David Mosberger
2003-05-14 23:53 ` Keith Owens [this message]
2003-05-15 1:13 ` David Mosberger
2003-05-15 1:22 ` Keith Owens
2003-05-15 16:37 ` Bjorn Helgaas
2003-05-15 21:32 ` David Mosberger
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=marc-linux-ia64-105590723705811@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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