Trent W. Buck writes:
> I'd like someone on the hacking team to verify the accuracy of my
> performance paragraph ("Tagging also provides ...").
>
> Before:
>
> | Tag the contents of the repository with a version name.
> |
> | Tag is used to name a version of this repository (i.e. the whole tree).
>
> After:
>
> | Name the current repository state for future reference.
I think that the verb "tag" can and should be used here. People
familiar with other VCSes will know exactly what is meant, while those
new to the scene will get the right connotations from the English word
(of course, if they're not native English speakers all bets on
connotations are mostly off, so I think we needn't worry about whether
they'll get the wrong idea from "tag"). Also I think the connotations
of "version name" are useful, giving
Tag the current repository state with a version name for future
reference.
> | [...]
> | The `darcs tag' command names the current repository state, so that it
> | can easily be referred to later. Every `important' state should be
> | tagged; in particular it is common to tag each stable release with a
s/common/good practice/
> | number or codename. A discussion of release numbering can be found at
> | http://producingoss.com/en/development-cycle.html.
The rest is fine IMHO.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
