On Feb 6, 2017, at 9:18 AM, Richard Hipp <[email protected]> wrote:
>
> Does anybody else having any feelings one way or another about this?
I’m not sure I’ve run into *quite* the same case, but a related one I did run
into recently was trying to migrate from a “release” tag (as Fossil itself
uses) to a “release” branch.[*]
You can see some of the circus this caused here, as it’s a public repo:
https://tangentsoft.com/pidp8i/timeline?r=release&c=2016-12-23
[*] Why use a branch instead of a tag? Because I want the binary OS images I
create from the current release version to remain pinned to the release branch,
so that if someone using one of those OS images says “fossil update” in the
source checkout directory — which remains on the OS images — they get the
current release, rather than get sent back to the trunk.
You may be happy to know that this software project is also using autosetup, by
the way.
And if any of you think PDP-8s were cool:
https://tangentsoft.com/pidp8i/wiki?name=Warren%27s+PiDP-8/I+System
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
