[lkml]   [2002]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-2.5.4-pre1 - bitkeeper testing
On Thu, Feb 07, 2002 at 09:26:40AM -0800, Larry McVoy wrote:
> On Thu, Feb 07, 2002 at 08:36:20AM -0800, Linus Torvalds wrote:
> > > What about people who send you occasionnal patches, and happen to
> > > be using Bitkeeper too ?
> >
> > For those people, "bk send -d" is fine. It ends up
> No! This will send the entire repository. Do a "bk help send", you probably
> want "bk send -d -r+" to send the most recent cset.

Larry, I think this means you should change the default behavior of 'bk
send' to ask the user what the hell they are smoking if they the patch to
be sent is larger than say, oh 200k.

I got clobbered by this a couple of times trying to get someone to 'bk
send' me a patch.

I got burned enough times to just decide never to use it again.

Either remove 'bk send' or at least warn us before we shoot off a foot.

Ideally, this should ask what changesets you want to send, and what
public tree to look at to see *what* makes sense to send.

Troy Benjegerdes | master of mispeeling | 'da hozer' |
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Schulz
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:24    [W:0.070 / U:18.104 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site