On 5/15/2015 10:43 AM, Warren Young wrote: > On May 15, 2015, at 9:00 AM, Richard Hipp <d...@sqlite.org> wrote: >> The whole purpose of --allow-empty is to force Fossil to do a >> check-in that deliberately has no changes from the previous check-in. >> This is done, for example, to tag a release. > > I can see that that is shorter than “fossil tag add”, but it nets out > to about the same number of keystrokes, since the artifact ID needed > with “tag add” is within easy reach of a copy-paste. > > I find it best to tag the release with “ci --tag” when checking in the > file that holds the version number. That checkin updates the > ChangeLog, too, if there is one. I only resort to “tag add” when I > forget to do this.
drh's preference seems to be to make an additional check-in highlighting the release. I imagine the reason he does this is so that the comment can simply say something like "Version 3.8.10.1", rather than describing the changes that went into it, since there are none. You're obviously free to instead apply the release tag to the final change. >> Some people also do it to start a new branch. > > As above, --allow-empty is also unnecessary for this, since we still > have “f ci --branch”. I'm not sure you understand drh's point. He's once again saying that some people like to highlight special events (citing release and branch creation) as check-ins containing no actual changes. This gives Fossil users a space to describe the milestone. Of course Fossil also provides technotes née events, but technotes aren't tied to a version or branch and can't have tags and all that. I suppose technotes describe the project as a whole rather than a particular version, release, or branch. -- Andy Goth | <andrew.m.goth/at/gmail/dot/com>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
