On Sat, Jun 25, 2016 at 7:09 PM, Fossil SCM user's discussion < fossil-users@lists.fossil-scm.org> wrote:
> (Sat, 25 Jun 18:40) Fossil SCM user's discussion: > > fwiw, i disagree. This patch removes an option from the user (specifying > an > > empty string) and does not add any new option (not specifying a prefix > > provides the same effect). > > But if I set a tarball prefix to some value, > and then rename the project; > How often does one rename a fossil project? (In my 8+ years with fossil, i've only once renamed a project.) I should simply delete a prefix via sql > to use a new project name as a tarball prefix.. ..or just duplicate a new name. > i don't understand what you mean by that. For your patch to apply, the user would literally have to had named his project the empty string (as opposed to NULL), and i cannot imagine anyone actually doing that, nor can i imagine any useful semantics for such cases. (But i'm often quite unimaginative.) i guess my question is: what _benefit_ does your patch provide for users other than yourself? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users