The bksend script works just fine, provided you use it correctly...
I think the main use of the script is not merging with Linus but posting
public, reviewable BK patches.
> But if there is a clean tree to pull from, that is absolutely the
> preferred method for me to sync up, _especially_ with things like drivers.
> Then an email that just says
>
> Linus,
> please do
>
> bk pull .....
>
> to receive changes to the following files
>
> .. diffstat list ..
>
> through the following changes
>
> .. changset list ..
>
> and then I don't even need to see the diffs themselves if I can just see
> that it only touches the ALSA files (that's another reason why I really
> want clean trees - immediately that there is a changeset to a non-ALSA
> file I want to see diffs, so that I have a clue about potential conflicts)
And "Documentation/BK-usage/bk-make-sum ~/repo/linus-2.5" helpfully
generates this output ;-)
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/