Re: GNU Emacs is on Bazaar now.

[Kenichi Handa]

In article <address@hidden>, Juanma Barranquero <address@hidden> writes:

> Yes, but it is useful to start the commit log with a one-line
> description of the changes, because there are commands to show the
> commits with their comments in "single line mode". For example, I
> committed a change for vc-git, and the ChangeLog entry was this:

> 2009-12-28  Juanma Barranquero  <address@hidden>

>       Supersede color.diff settings in git log (bug#5211).

>       * vc-git.el (vc-git-print-log): Pass "--no-color" to log to avoid
>       escape chars in its output when the user has color.diff set to `always'.
>       This fix works on git 1.4.2 and newer (released on 2006-08-13).

> For the commit message I uses just the first line, but for more
> extensive changes I would've used the whole ChangeLog entry.

> Now, using "bzr log -l10 --line", you get:

> 99201: Juanma Barranquero 2009-12-28 [merge] Supersede color.diff
> settings in git log (bug#5211).
> 99200: Juanma Barranquero 2009-12-28 [merge] Update .bzrignore.
> 99199: Juanma Barranquero 2009-12-28 Update autoload checksum.
> 99198: Karl Fogel 2009-12-27 [merge] Merge: update nt/INSTALL for
> CVS->Bazaar switchover too.
> 99197: Karl Fogel 2009-12-27 [merge] Merge: document that we are on Bazaar 
> now.
> 99196: Andreas Schwab 2009-12-27 Add .bzrignore
> 99195: Chong Yidong 2009-12-27 * minibuf.c (Fall_completions): Minor
> optimization.
> 99194: Kevin Ryde 2009-12-26 * man.el
> 99193: Kevin Ryde 2009-12-26 (Man-bgproc-sentinel): When "-k foo"
> produces no output show error
> 99192: Kevin Ryde 2009-12-26 Tweak a comment: it's man-db on gnu/linux
> which agrees with posix that

Ah, I see.  Thank you for the detailed explanation.

---
Kenichi Handa
address@hidden