Re: No ChangeLog's (was: bzr send workflow)

[Stephen J. Turnbull]

Eli Zaretskii writes:

 > What do we do instead when there are no ChangeLog files?

You keep a temporary ChangeLog file, just not under version control.

More complex workflows could use the "pipeline" or "loom" plugins,
which I think have features for keeping track of log messages while
development proceeds.

 > Are there any commands that let us edit log messages for future
 > commits, keep their record, and use them conveniently when the time
 > comes to commit?

This sounds like job for Emacs to me.  The basic workflow for a commit
is

1.  move relevant log entry to .msg
2.  bzr commit --file=.msg    # assumes commitables already bzr add'ed
3.  rm .msg

I suspect that a simple command that

1.  looks for a ChangeLog
    if not found, edits .msg directly, then does 2 and 3 of the basic
    workflow
2.  marks the top log entry
3.  asks for confirmation y/n
    if not confirmed, drop into a recursive edit allowing user to mark
    a different log entry or perhaps edit it, then confirm with C-c C-c
4.  do 1, 2, and 3 of the basic workflow above

might be a good UI that could even be added to vc.el.