mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BK Kernel Hacking HOWTO
Date: Thu, 21 Feb 2002 11:31:09 -0500	[thread overview]
Message-ID: <3C7520CD.D325A3DC@mandrakesoft.com> (raw)
In-Reply-To: <3C751CB2.52110E58@mandrakesoft.com>

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

  reply	other threads:[~2002-02-21 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 16:13 Jeff Garzik
2002-02-21 16:31 ` Jeff Garzik [this message]
2002-02-21 16:40 ` Stelian Pop
2002-02-21 18:40   ` Andreas Dilger
2002-02-22 11:44     ` Stelian Pop
2002-02-26 17:45 ` Geert Uytterhoeven
2002-02-26 18:34   ` Andreas Dilger
2002-02-26 20:19     ` Geert Uytterhoeven
2002-02-26 20:29       ` Larry McVoy
2002-02-26 20:40         ` Geert Uytterhoeven
2002-02-26 20:57       ` Andreas Dilger
2002-02-21 16:54 willy tarreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C7520CD.D325A3DC@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®