On Thu, Feb 09, 2006 at 10:53:02AM +0100, Joeri van Ruth wrote: > On Thu, Feb 02, 2006 at 10:30:17PM +0100, Albert Reiner wrote: > > [EMAIL PROTECTED], Thu, 02 Feb 2006 14:30:42 -0400]: > > > As for "darcs remove", it might be best to eliminate that command, > > > or at least to hide it in the section that we reserve for commands > > > that are unnecessary and that sometimes confuse newcomers. > > > > Please don't eliminate! Not only would that break backward > > compatibility, it is also a very useful command, just as unpull and > > unrecord are. > > I would suggest "darcs forget".
-1 Darcs will not forget the file. It just won't track any further changes. In particular, 'forget' fails to indicate that the file will be removed from any /other/ repo to which the patch is applied. I don't see that 'remove' is any less obvious than 'rollback', and I can't think of any succinct way of making clear that remove /does/ remove the file, just not from the current working copy. Since the latter detail is eminently discoverable, it seems more important to be clear about the former. -- Jamie Webb _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
