Le Vendredi 03 Février 2006 15:27, [EMAIL PROTECTED] a écrit : > > > 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. > > Don't worry, I'm sure that "darcs remove" will live a long time, if only > because of backwards compatibility. Could you please tell us what you use > it for? Why don't you just delete the file in question instead?
Because darcs remove != rm ? darcs remove remove the file the repos, this mean darcs will longer check changes on this file when recording patch. This can be usefull to remove a file from repos without really deleting it (imagine you add by mistake ./configure). # darcs remove --help [...] Remove should be called when you want to remove a file from your project, but don't actually want to delete the file. Otherwise just delete the file or directory, and darcs will notice that it has been removed. And this is a nice feature comparing to CVS which is unable to forget a file until it is existing... (hack is mv file file.hidden; cvs rm file; mv file.hidden file, very annoying). > > Regards, > > Zooko > > _______________________________________________ > darcs-users mailing list > [email protected] > http://www.abridgegame.org/mailman/listinfo/darcs-users
pgp2NVpHX4DJf.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
