[lkml]   [2002]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BK Kernel Hacking HOWTO
> 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.

You can set up a publically accessible tree here, if you need one,
see the Hosting link on our website. You can make your tree publically
accessible in multiple ways, with varying levels of security, see
"bk help bkd".

The advantage of allowing him to pull is that you won't have the same data
in your BK tree twice, which you would have if you sent him diffs and then
pulled the diffs from him. This is ESPECIALLY IMPORTANT if you have renames
(and creates/deletes are a sort of rename) in your patch.

If the situation is that you've created a scratch tree, specifically for
sending stuff to Linus and you aren't going to use it for anything else
or build on it, then you can send him regular diffs, and toss the tree
once you know he accepted them.
Larry McVoy lm at
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.034 / U:0.796 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site