On Jul 13, 2015, at 7:51 AM, Warren Young <w...@etr-usa.com> wrote:
>
> Instead, use tags.
A couple more points:
1. You can see how this could be easily automated. A short bit of shell
scripting could do most of what I outlined. I haven’t bothered here because I
don’t think it would pay off in my case, but you might have a better reason for
automating it there.
2. You can adopt this scheme retroactively:
a. Use your current method of finding the checkin ID of a past version. Maybe
you’ve been recording checkin IDs in a file (“1.2.3: [c245067884b54d15]”) or
maybe you’ve just been spelunking the timeline.
b. Tag old releases:
$ fossil tag add v1.2.3 c245067884b54d15
If your current method for storing version-to-checkin-id mappings is parseable,
as in the above example, you could again fix all of this up with a small bit of
shell scripting.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
