On Sun, Oct 06, 2002 at 01:03:57PM -0400, Skip Ford wrote:
> I was thinking more of just sharing the code. There are more trees out
> there than just Linus'. Deciding to apply one of your patches is much
> easier if we have the specific patch, rather than just a 600k patch from
> Linus that happens to include your patch buried inside it.
I think a commit trigger is what you want:
cd BitKeeper
test -d triggers || mkdir triggers
cd triggers
cat > post-commit-linux-patches <<EOF
#!/bin/sh
(
bk changes -v -r+
bk export -tpatch -r+
) | mail linux-patches@vger.kernel.edu
EOF
bk new post-commit-linux-patches
bk commit -y'Mail patches to linux-patches'
I haven't tested this but I think this will work, it will mail the patches as
they are created, not as they move through the trees.
-- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - 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/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:56 EST