From: Jens Axboe <axboe@suse.de>
To: Larry McVoy <lm@work.bitmover.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Larry McVoy <lm@bitmover.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: bk-commits: diff -p?
Date: Wed, 10 Nov 2004 09:49:09 +0100 [thread overview]
Message-ID: <20041110084908.GG5602@suse.de> (raw)
In-Reply-To: <20041108164302.GA489@work.bitmover.com>
On Mon, Nov 08 2004, Larry McVoy wrote:
> This has been fixed in the following releases:
>
> bk-3.2.3
> bk-3.2.2c
> bk-3.2.2b
>
> Correct usage is "bk diffs -up" which will get you unified + procedural diffs.
> -p is currently a hack, it implies -u, but don't depend on that behaviour,
> a future release does this correctly and if you teach your fingers that
> diffs -p is the same as diffs -up you'll get burned later.
Thanks! I requested this about a year ago :-)
--
Jens Axboe
prev parent reply other threads:[~2004-11-10 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 8:41 bk-commits: diff -p? Geert Uytterhoeven
2004-11-08 15:51 ` David Woodhouse
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 [this message]
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=20041110084908.GG5602@suse.de \
--to=axboe@suse.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=lm@work.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