synchronizing with Emacs, take two

[Ted Zlatanov <tzz@lifelogs.com>]

On Wed, 30 Jun 2010 16:35:35 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote: 

TZ> Maybe we should close the bug when the merge happens.  As long as
TZ> there's a consistent way to associate the bug with the commit message.

On Thu, 01 Jul 2010 00:08:51 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> As long as you are committing to the Emacs repository many unrelated
EZ> changes, there really is no way of making the commit messages more
EZ> useful.  But at least in several cases, it looks like the committed
EZ> changes belong to a single changeset.  Examples:
...
EZ> For such changes, it would be more useful if the first line of the
EZ> commit message summarized the change, instead of saying just "Synch
EZ> with Gnus trunk".  That would allow to, e.g., find the merge which
EZ> introduced some specific change in Gnus by just looking at the output
EZ> of "bzr log --line", which shows only those first lines from the
EZ> commit messages.

>> I plan to eventually set up a more automatic synchronization method.

EZ> Thanks.  For that, I hope the original commit message would become the
EZ> commit message in the Bazaar repository.

I'm aggregating two threads here and limiting the discussion to just the
Ding list.

Yamaoka-san, how do you synchronize Gnus and Emacs?  Do you use a script
or do it manually?  I'd like to help with the process (and automate it,
as previously discussed) while adding these two features:

- for a single change, make the commit message the same as the change's
  commit message (with a prefix to indicate it's a synch)

- close bugs when they are mentioned in the commit message

I'd like this to be as automatic as possible, but never do a push
automatically.  So it can't happen on every commit.

Ted