On Fri, Mar 06, 2015 at 03:46:08PM +0100, j. van den hoff wrote:
> On Fri, 06 Mar 2015 15:11:31 +0100, Tontyna <tont...@ultrareal.de> wrote:
Hi there,
> >I'd prefer that default `rm`/`mv` without options leave my file
> >system alone. A `--forcefilesytem` flag would be a convenient
> >enhancement.
>
> personally, I would _not_ like to see a mandatory
> `--forcefilesystem' "option" in order to get the usually desired
> behaviour.
This discussion does seem to be taking more-or-less the same shape as
the last time around. The end result then was: no change; whatever code
was written was not accepted into stock fossil.
This time, there is some code visible in the recent timeline, so maybe
it will progress.
I think there were three main "issues" brought up, with some opinions
for and against each.
I'll (try to) summarise them here; but do feel free to check and correct
me if I've mischaracterised anything.
* the current fossil commands "mv" and "rm" make changes to the
repository, but not to the local filesystem.
Issue 1 - there should be a way, in fossil, to make "the corresponding"
changes to the filesystem.
Issue 2 - that way should be the default for a command, not requiring
a --option argument.
Issue 3 - that command should be exactly "mv" or "rm".
Issue 1 seemed to be generally positive, with a few questions about when
exactly the filesystem changes should happen -- at command time or at
commit time -- and with a question about what "revert" or other "undo"
features should be available.
Issue 2 seemed to be generally positive (once issue 1 is considered
accepted); I don't think I saw any objections to the theory of it.
Issue 3 seemed to be mixed. Those in favour were greatly in favour;
those against were greatly against. The arguments were broadly what was
seen in this thread, which is roughly: consistency with non-fossil things
vs consistency with previous-fossil things.
I don't think I've anything new to bring to the discussion. Hopefully the
above notes are useful to clarify thoughts or recollections. Or possibly
they are wrong or unsubtle enough to induce someone to expand on them.
When the code is ready, it'll be time for the One Person to use the One
Vote, and we'll see what's in the next version of fossil ;-)
f
--
Francis Daly fran...@daoine.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
