On 04/07/2018 16:42, jungle Boogie wrote:
On 12:42AM, Wed, Jul 4, 2018 Nicola
> Maybe, the sentence above could be complemented with an example of how
> to do that and how *not* to do it (e.g., explaining what the effect of
> adding a 'trunk' tag to a random check-in is and why it should not be
> done).
So provide a patch with the enhancement and let's see what happens.
IIUC, the sentence refers to an implementation detail: moving check-ins
between branches is implemented by simply renaming tags. But, it is easy
(at least, for a newcomer like myself) on a first (and possibly second)
reading to interpret it in the sense that *the user* can move check-ins
between branches that way.
As for contributing to the project, currently I'd likely do more harm
than good :) I have been using Fossil for a short time, and many details
are not entirely clear to me yet (e.g., I still don't understand well
the purpose of tagging branches with both branch=name and sym-name), but
I am taking notes as I am learning, and I am willing to share them some
time in the future for the benefit of other beginners.
Nicola
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
