question about changeset structure
Matt Mackall
mpm at selenic.com
Tue Jun 7 08:38:46 UTC 2005
On Mon, Jun 06, 2005 at 02:33:57AM +0300, Alexey Stroganov wrote:
> Hello,
>
> Right now, if I understand correctly, every changeset has only one
> description field. It works ok for case when changeset contains
> changes in one file only. But if changes were made in several files it
> would be more logical to have one description field per file to store
> notes about file specific changes and one description filed for whole
> changeset. What do you think?
>
> So changeset info may look like:
>
> changeset #121
> Fixed issue #345
> Fixed issue #134
>
> test1.c
> specific notes about changes in test1.c
>
> test2.c
> specific notes about changes in test2.c
>
> etc..
Take a look at the hgeditor example script for hints on ways to do
that. I don't force any particular format on the changeset messages.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list