From: Andreas Dilger <adilger@turbolabs.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BK Kernel Hacking HOWTO
Date: Tue, 26 Feb 2002 13:57:16 -0700 [thread overview]
Message-ID: <20020226135716.S12832@lynx.adilger.int> (raw)
In-Reply-To: <20020226113402.K12832@lynx.adilger.int> <Pine.GSO.4.21.0202262117380.8085-100000@vervain.sonytel.be>
In-Reply-To: <Pine.GSO.4.21.0202262117380.8085-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Tue, Feb 26, 2002 at 09:19:46PM +0100
On Feb 26, 2002 21:19 +0100, Geert Uytterhoeven wrote:
> So in case he wants a few csets only, I have to redo my for-Him-to-pull-tree.
> In which case I don't see any advantages compared to emailing a patch with
> changeset- and file-specific comments. Especially since setting up a
> for-Him-to-pull-tree requires setting up a publically accessible BK server.
If you want to just send occasional CSETs to Linus or Dave Jones (which
is the category that a large majority of people are in) then you can
always send a CSET in the mail instead of having a "pull" tree available.
Search the l-k archives for my "bksend" script which formats this nicely.
One of the benefits of using BK over patches, even in this situation, is
that if your tree is not exactly the same as Linus' the BK CSET will know
what version of the tree it was generated against and will make applying
and resolving conflicts a lot easier for Linus.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-02-26 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 16:13 Jeff Garzik
2002-02-21 16:31 ` Jeff Garzik
2002-02-21 16:40 ` Stelian Pop
2002-02-21 18:40 ` Andreas Dilger
2002-02-22 11:44 ` Stelian Pop
2002-02-26 17:45 ` Geert Uytterhoeven
2002-02-26 18:34 ` Andreas Dilger
2002-02-26 20:19 ` Geert Uytterhoeven
2002-02-26 20:29 ` Larry McVoy
2002-02-26 20:40 ` Geert Uytterhoeven
2002-02-26 20:57 ` Andreas Dilger [this message]
2002-02-21 16:54 willy tarreau
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=20020226135716.S12832@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=geert@linux-m68k.org \
--cc=jgarzik@mandrakesoft.com \
--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
all inboxes | Powered by JetHome®