Subject: Re: bk-commits: diff -p?
From: David Woodhouse <dwmw2@infradead.org>
To: Larry McVoy <lm@bitmover.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
       Linux Kernel Development <linux-kernel@vger.kernel.org>
In-Reply-To: <20041108164302.GA489@work.bitmover.com>
References: <Pine.LNX.4.61.0411080940310.27771@anakin>
	 <20041108164302.GA489@work.bitmover.com>
Content-Type: text/plain
Message-Id: <1100043712.21273.26.camel@baythorne.infradead.org>
Mime-Version: 1.0
Date: Tue, 09 Nov 2004 23:41:52 +0000
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 800
Lines: 24

On Mon, 2004-11-08 at 08:43 -0800, 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.

Actually my script is using 'bk export -du -tpatch -r$CSET'. '-dup'
doesn't seem to do the right thing.

-- 
dwmw2


-
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/