On Tue, 20 Nov 2012 16:48:00 +0100, James Turner <[email protected]>
wrote:
On Tue, Nov 20, 2012 at 03:39:06PM +0000, David Given wrote:
Richard Hipp wrote:
[...]
> CVS did not couple the actions, and I copied CVS in this regard. I
> agree with you now, that coupling them is the right thing to do. But
I
> fear to change it because that might cause problems for existing
scripts.
Add a -p for physical option to actually change the files, and leave the
default as is? I agree, changing the existing behaviour would be a
recipe for disaster.
I'd suggest -f like cvs rm uses.
obviously everybody seems to have his/her own preference how to handle
this. so only a fraction of users will be happy in the end it seems. -- I
would again second the proposal
of Remigiusz Modrzejewski in this thread: after a 'grace' period when it
would behave in the way you propose (explicitly add a -f flag to enforce
deletion), finally change the default to what _current_ VCSs (>= svn)
seemingly all (?) do by default which is to treat `svn(hg, git, bzr) rm'
as meaning
"remove from repository and also remove the working copy" while relegating
different behaviour (if at all) to an option such as "bzr rm --keep".
in my way that is the most frequently intended behaviour which should
therefore be the default.
sure a matter of taste as so many things, but at least it would avoid
surprises here for refugees from one of the other systems.
j.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
