From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>, Pavel Roskin <proski@gnu.org>,
David Gibson <hermes@gibson.dropbear.id.au>
Subject: Re: [PATCH] Update in-kernel orinoco drivers to upstream current CVS
Date: Sat, 03 Jul 2004 02:08:49 -0400 [thread overview]
Message-ID: <40E64D71.5020802@pobox.com> (raw)
In-Reply-To: <20040702222655.GA10333@bougret.hpl.hp.com>
Jean Tourrilhes wrote:
> Jeff, does BitKeeper allow to merge patches at an earlier
> point than the last version and reconciliate both branches ? That
> might come handy.
Yes, this is one of BitKeeper's strengths.
I can create a BitKeeper repository circa 2.6.0, merge a patch, and then
merge that repository into the 2.6.7-BK-latest repository.
Jeff
next prev parent reply other threads:[~2004-07-03 6:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 22:26 [PATCH] Update in-kernel orinoco drivers to upstream current CVS Jean Tourrilhes
2004-07-02 23:07 ` Francois Romieu
2004-07-03 20:15 ` Francois Romieu
2004-07-03 23:11 ` Francois Romieu
2004-07-04 2:13 ` David Gibson
2004-07-04 17:17 ` Francois Romieu
2004-07-05 23:14 ` Francois Romieu
2004-07-05 23:39 ` Jeff Garzik
2004-07-06 22:54 ` Francois Romieu
2004-07-07 1:25 ` Michael Clark
2004-07-07 18:50 ` Pavel Roskin
2004-07-08 22:04 ` Jeff Garzik
2004-07-09 18:53 ` [PATCH] Updated pci-skeleton.c Pavel Roskin
2004-07-09 19:18 ` Jeff Garzik
2004-07-08 23:17 ` [PATCH] Update in-kernel orinoco drivers to upstream current CVS Francois Romieu
2004-07-08 23:30 ` Jeff Garzik
2004-07-03 6:08 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 19:11 Dan Williams
2004-07-02 19:25 ` Jeff Garzik
2004-07-04 2:01 ` David Gibson
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=40E64D71.5020802@pobox.com \
--to=jgarzik@pobox.com \
--cc=dcbw@redhat.com \
--cc=hermes@gibson.dropbear.id.au \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.