public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Patrick Mochel <mochel@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [bk patch] Make cardbus compile in -pre4
Date: Fri, 8 Feb 2002 23:41:18 -0800	[thread overview]
Message-ID: <20020208234118.C8129@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202081824070.25114-100000@segfault.osdlab.org> <20020208203931.X15496@lynx.turbolabs.com> <3C649F4F.7E190D26@mandrakesoft.com> <20020209002920.Z15496@lynx.turbolabs.com>
In-Reply-To: <20020209002920.Z15496@lynx.turbolabs.com>; from adilger@turbolabs.com on Sat, Feb 09, 2002 at 12:29:20AM -0700

On Sat, Feb 09, 2002 at 12:29:20AM -0700, Andreas Dilger wrote:
> Yes, that would be my thought as well.  Sadly, running the command
> 
> bk send -d -r+ -wgzip_uu -
> 
> does not work as I would _hope_ it would, namely putting a regular context
> diff at the beginning of the email, and gzip_uu for only the CSET.  

Whoops, that's a bug.  Type "bk sendbug" and send us a bug report, we'll
fix it.  Sorry about that.

> > But this is still a trial run of BK, so who knows what will wind up to
> > be the best policy for casual submitters.
> > 
> > And there's nothing wrong at all with sending GNU patches...
> 
> Oh, I agree that for people without BK they can keep sending patches.

It occurs to me that there is no reason you can't generate a regular
patch from BK and mail it to the list w/ the changeset comments.  That
keeps all the non-BK users perfectly happy, nothing has changed for
them and they can use BK or not as they see fit.  In addition, you can
send off a BK patch to Linus and/or stuff a patch into a publicly
available BK tree and point him at it.

If you all can reach any sort of concensus on what is a pleasant patch
format for non-BK users, just tell me, and I'll make sure BK can generate
that sort of patch easily.

> This might also be possible if BK could export/import a whole changeset
> in patch form, plus some magic stuff at the beginning/end (gzip_uu) which
> had all of the BK metadata in it, but I don't know if that is possible or
> desirable.

Well, send -d is essentially that - it's two patches, a GNU patch and a
BK patch.  It was a mistake for us to wrap the whole thing, we should
leave the regular diffs alone and just wrap the BK stuff.  We can do
that.  
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-02-09  7:41 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09  2:25 [bk patch] Make cardbus compile in -pre4 Patrick Mochel
2002-02-09  3:39 ` Andreas Dilger
2002-02-09  4:02   ` Jeff Garzik
2002-02-09  7:29     ` Andreas Dilger
2002-02-09  7:41       ` Larry McVoy [this message]
2002-02-10  2:39       ` Jeff Garzik
2002-02-10  3:52       ` Linus Torvalds
2002-02-10  7:47       ` Andreas Dilger
2002-02-10 20:57         ` Linus Torvalds
2002-02-11 18:38           ` Andreas Dilger
2002-02-09  5:12   ` Larry McVoy
2002-02-09  5:32     ` Andrew Morton
2002-02-09  9:36       ` Rob Landley
2002-02-09  9:57         ` Momchil Velikov
2002-02-09 10:01           ` Alexander Viro
2002-02-09 18:09             ` Rob Landley
2002-02-09 15:08           ` Daniel Phillips
2002-02-10  4:07             ` Linus Torvalds
2002-02-09 10:14     ` David Lang
2002-02-09 15:54       ` Larry McVoy
2002-02-09 16:50         ` Tom Rini
2002-02-09 17:05           ` Larry McVoy
2002-02-09 21:01             ` David Lang
2002-02-09 21:41               ` Larry McVoy
2002-02-09 23:36                 ` Andreas Dilger
2002-02-09 23:45                   ` Tom Rini
2002-02-10  0:42                     ` Andreas Dilger
2002-02-09 23:52                   ` Larry McVoy
2002-02-10  4:13                     ` Linus Torvalds
2002-02-10 18:02                     ` Tom Rini
2002-02-10  5:25                 ` William Stearns
2002-02-11 17:30                   ` Padraig Brady
2002-02-13 11:59                     ` Padraig Brady
2002-02-09  9:27   ` pull vs push (was Re: [bk patch] Make cardbus compile in -pre4) Rob Landley
2002-02-09 10:08     ` Andreas Dilger
2002-02-09 18:12       ` Stelian Pop
2002-02-09 20:59         ` Linus Torvalds
2002-02-09 20:12           ` Stelian Pop
2002-02-09 20:26             ` Larry McVoy
2002-02-09 20:51               ` Stelian Pop
2002-02-09 23:45                 ` Jeff Garzik
2002-02-09 23:49                 ` Larry McVoy
2002-02-09 20:57               ` Pau Aliagas
2002-02-09 21:07                 ` David Lang
2002-02-09 21:13                   ` Pau Aliagas
2002-02-09 21:45               ` Rob Landley
2002-02-10  0:19               ` Andreas Dilger
2002-02-10  0:36               ` Herbert Xu
2002-02-10  0:54                 ` ssh primer (was Re: pull vs push (was Re: [bk patch] Make cardbus compile in -pre4)) Jeff Garzik
2002-02-10  0:59                   ` Herbert Xu
2002-02-10  1:24                     ` Jeff Garzik
2002-02-10  8:13                       ` Herbert Xu
2002-02-13 17:13                       ` Aaron Lehmann
2002-02-14  0:22                         ` Rob Landley
2002-02-14  6:57                           ` Aaron Lehmann
2002-02-14 11:00                           ` Harald Arnesen
2002-02-10  0:59                   ` Ben Pfaff
2002-02-10  1:14                   ` David Lang
2002-02-10  1:22                     ` ssh primer (was Re: pull vs push (was Re: [bk patch] Make cardbuscompile " Jeff Garzik
2002-02-10  2:46               ` pull vs push (was Re: [bk patch] Make cardbus compile in -pre4) Alan Cox
2002-02-11 11:51     ` Pavel Machek
2002-02-11 18:42       ` John Alvord
2002-02-09 11:44 ` [bk patch] Make cardbus compile in -pre4 Peter Osterlund
  -- strict thread matches above, loose matches on Subject: below --
2002-02-10 20:12 Chris Adams

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=20020208234118.C8129@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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