From: David Woodhouse <dwmw2@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Larry McVoy <lm@bitmover.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: bk-commits: diff -p?
Date: Mon, 08 Nov 2004 15:51:31 +0000 [thread overview]
Message-ID: <1099929091.4542.83.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411080940310.27771@anakin>
On Mon, 2004-11-08 at 09:41 +0100, Geert Uytterhoeven wrote:
> Hi Larry,
>
> Would it be possible to enable the `-p' option (Show which C function each
> change is in) of diff for all patches sent to the bk-commits-* mailing lists?
I did consider that but 'bk diffs -up' gives a context diff, not a
unified diff.
--
dwmw2
next prev parent reply other threads:[~2004-11-08 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 8:41 Geert Uytterhoeven
2004-11-08 15:51 ` David Woodhouse [this message]
2004-11-08 16:16 ` Geert Uytterhoeven
2004-11-08 16:24 ` David Woodhouse
2004-11-08 16:43 ` Larry McVoy
2004-11-09 23:41 ` David Woodhouse
2004-11-10 15:06 ` Larry McVoy
2004-11-10 15:13 ` David Woodhouse
2004-11-10 8:49 ` Jens Axboe
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=1099929091.4542.83.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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®