From: Andreas Dilger <adilger@turbolabs.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: 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: Mon, 11 Feb 2002 11:38:48 -0700 [thread overview]
Message-ID: <20020211113848.H9826@lynx.turbolabs.com> (raw)
In-Reply-To: <20020210004748.G9826@lynx.turbolabs.com> <Pine.LNX.4.33.0202101250150.7412-100000@home.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0202101250150.7412-100000@home.transmeta.com>; from torvalds@transmeta.com on Sun, Feb 10, 2002 at 12:57:11PM -0800
On Feb 10, 2002 12:57 -0800, Linus Torvalds wrote:
> On Sun, 10 Feb 2002, Andreas Dilger wrote:
> > What about BK CSET (or regular patch) submissions from non-core
> > developers? Would you accept CSETs via email if they are preceeded
> > by a unified diff and explanation?
>
> I have worked with a few BK patches in email, and I have to say that I
> pretty much detest them. The less I have to work with them, the better,
> although that may just because I don't yet have the same kind of
> infrastructure for them as I have for regulat patches.
>
> (But _please_ do a "bk send" to a file, and edit the file before you send
> it, instead of sending directly with that "Bitkeeper patch" subject line.
> It looks like "bk send" was really designed for automatic merges, not for
> humans)
Yes, the first time I used "bk send" to send something directly to Ted it
happened that I was offline so I looked into my mail spool at the emails
and also hated it. What I was proposing instead of just "bk send" is to
prepend the changelog entry, a real unified diff, and gzip_uu CSET at the
end. Larry has agreed that "bk send -d -wgzip_uu" wrapping the diff part
of the patch is a bug to be fixed.
So, instead of the current layout of "'This is a BitKeeper patch' comment +
commented-out diff + BK stuff", I would send "CSET ChangeLog + unified diff +
gzip_uu wrapped BK stuff". This would be the output of (probably in a script):
bk changes -r<rev>
bk export -tpatch -h -du -r<rev>
bk send -wgzip_uu -r<rev> -
For example, your recent 2.5.4 release would look like the below, and I
_think_ you could just accept this with "bk receive -a [repository path]",
but I'm not sure how good the BK heuristics are for finding a CSET at the
end of a long patch. I'm only skeptical because the current "bk send"
output comments out the diff part of the output.
ChangeSet@1.262, 2002-02-10 19:24:03-08:00, torvalds@home.transmeta.com
update version
TAG: v2.5.4
diff -Nru a/Makefile b/Makefile
--- a/Makefile Mon Feb 11 10:44:32 2002
+++ b/Makefile Mon Feb 11 10:44:32 2002
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 5
SUBLEVEL = 4
-EXTRAVERSION =-pre6
+EXTRAVERSION =
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
This BitKeeper patch contains the following changesets:
1.262
## Wrapped with gzip_uu ##
begin 664 bkpatch3560
M'XL(`!\#:#P``[V4T6[;(!2&K\-3(/5RLG,.!H(M>5K71ENU=8V<==HMLFEL
MU;$K0[)6\L./6%U255.R1-LP<,'!1X?OY^>,WEK3)2-=5/7"=.2,?FRM2T;U
M4_,8/B^&5>-\(&M;'QBO;#>V73ZNJV;U&+!0$!^;:9>7=&TZFXPPC+8K[NG!
M)*-L^N'V\WE&2)K2BU(W"S,WCJ8I<6VWUG5AWVE7UFT3NDXW=FF<#O-VV6^W
M]@R`^4_@)`(A>Y3`)WV.!:+F:`I@7$F^RU:V2W,@%R(@CQGO47$AR"7%D$E&
M@8U]1Z`8)XPG$`6@$@"Z)S5]@S0`\I[^W<-<D)RN'@KMS("U:AORB?IBN2*S
M'402'-D(`0WD[8%BK_6]N:MJ\[+6.%(]@)K(OI"ZB'/4JA"QT&(?G->9//:(
M<8AZ%))+<JQDS_\.%*Y_+QF*/Y$,_H5D+W69T[6W1LB)I0L_:C^./2LJ$)ZX
M;R>HO+':+_:'G7:4WGM%>ZVWG[B*X@VR"1MLAE*=;#/\3S8;+N<-#;H?0_=`
M9UN:)XAQR2F2J\TT_?XU._\VS>97-U]HNGLY\]+D]W:U3/%.<B5B)#\!WOU:
%+9D%````
`
end
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-11 18:39 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 2:25 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
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 [this message]
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
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=20020211113848.H9826@lynx.turbolabs.com \
--to=adilger@turbolabs.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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®