+1
This would also guard against unplanned/accidental use of same branch name
in a repo with tens of older inactive branches one cannot possible remember
at all times.
-----Original Message-----
From: Richard Hipp
Sent: Monday, February 06, 2017 6:18 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Bug in "fossil branch new"
On 2/6/17, Richard Hipp <d...@sqlite.org> wrote:
That is correct, and it is by design. Fossil allows any number of
branches to share the same name.
On second thought, perhaps it would be worthwhile to enhance Fossil so
that it issued a warning if you include a --branch argument on "fossil
commit" with the same name as an existing open branch, and actually
fail the commit unless the --force flag is also present. Perhaps such
a change would make Fossil easier to transition to from other systems.
Does anybody else having any feelings one way or another about this?
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
