[darcs-users] a couple of features (logs & managing patches)

[David Roundy]

I've just implemented the below... --delete-logfile, the ignoring of an
empty logfile (and prompting in that case), and now --edit-long-comments
works together with --logfile, and it supports editing the patch name
(first line), and has a changes summary down at the bottom which gets left
out.

On Thu, Aug 19, 2004 at 07:00:03AM -0400, David Roundy wrote:
> I'm thinking that by adding a "--delete-logfile" option to record, and
> simply changing darcs' behavior when the specified logfile doesn't exist,
> and changing the behavior of --edit-long-comment, we should be in very good
> shape, in that we should be able to satisfy everyone I've heard from on
> this subject (which has been a lot).
> 
> Obviously the --delete-logfile would address your concern about
> accidentally re-using a logfile.
> 
> If we make --logfile=foo simply be ignored if --foo doesn't exist, then you
> could safely add this to your defaults, without restricting yourself to
> always create a logfile.
> 
> If we make --edit-long-comments have the result (when combined with
> of the comments, which I personally would find valuable.  This would imply
> changing the behavior of the --edit-long-comments option, in that it would
> presumably allow you to edit the patch name, as --logfile does, with the
> patch name being the first line.
> 
> The only additional feature that people seem likely to want is the ability
> to flag part of the --edit-long-comments file as ignored, and to add a
> patch summary to the file before it pops up in the editor, so you can see
> what you're recording.
-- 
David Roundy
http://www.abridgegame.org