Jeff Garzik wrote:
> 3) Include a summary and "diffstat -p1" of each changeset that will be
> downloaded, when Linus issues a "bk pull". The author auto-generates
> these summaries using "bk push -nl <parent> 2>&1", to obtain a listing
> of all the pending-to-send changesets, and their commit messages.
Two notes I wanted to get out before the rewrite:
1) The preferred format is likely to be a -single- diffstat followed by
a changeset, and
2) "bk changes -L <local-linus-repository>" is the preferred way to get
a listing of changesets not yet sent to Linus, not "bk push -nl"
A script should be appearing in the very near future, which generates
the desired for-Linus changeset format automatically. In the medium
term future and beyond, BK itself will hopefully generate the text.
Jeff
-- Jeff Garzik | XXX FREE! secure AFSPC AK-47 unclassified CDC Building 1024 | NATO SAS CDMA fun with filters Bellcore kibo SSL MandrakeSoft | high security goat clones infowar 2600 Magazine - 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 : Sat Feb 23 2002 - 21:00:34 EST