James Vega wrote:
> Sounds like we should be doing something like we do for git & hg.
> If the commit message is longer than 1 line, show the text to the
> user and let them munge it accordingly. Then we can use --logfile
> to feed the message to darcs so it properly handles the patch name
> (first line) and long description (subsequent lines).
Looks like you can get exactly this behaviour with:
--logfile <initial version> --edit-long-comment
Here's a demonstration (where EDITOR=ed):
$ printf %s\\n foo bar baz quux >m
$ touch x
$ darcs rec -la -mm --logfile m --edit x
Recording changes in "x":
223
,p
foo
bar
baz
quux
***END OF DESCRIPTION***
Place the long patch description above the ***END OF DESCRIPTION*** marker.
The first line of this file will be the patch name.
This patch contains the following changes:
A ./x
1,4d
1i
This is the new commit message.
And this is the
long description.
.
wq
272
Finished recording patch 'This is the new commit message.'
$ darcs cha --last=1 -v
Thu Jan 7 00:39:32 EST 2010 Trent W. Buck <[email protected]>
* This is the new commit message.
And this is the
long description.
addfile ./x
$
--
To unsubscribe, send mail to [email protected].
