On Thu, Nov 17, 2005 at 06:56:44PM +0100, Juliusz Chroboczek wrote: > David, let me know if that's okay with you before I implement this for > the other commands.
It seems fine to me. My only hesitation would be whether this should be done with an enforced flag of some sort, rather than by simply putting ALL --no-working-dir in your defaults file. Actually, I think this would be best. It would also seem valuable to add --no-working-dir to commands like whatsnew, in which case the flag would simply cause them to exit with failure. Perhaps these should be --without-working-dir and --with-working-dir? Hmmm. I'm not sure I like that better. My (naming) concern is that people may confuse --working-dir with --repo-dir in some sense, since they look parallel. I can't think of a flag that would make this mistake impossible... --use-working-dir? One solution to this dilemma would be to make --no-working-dir not have an opposite. In reality, if --no-working-dir is in the defaults file, you aren't practically going to want to override it on the command line. But unless someone else objects (speak up!), I think this is worth implementing, and we can iron out the naming later if necesary. > Thu Nov 17 18:55:16 CET 2005 Juliusz Chroboczek <[EMAIL PROTECTED]> > * Add --no-working-dir and --working-dir flags. > > Thu Nov 17 18:55:51 CET 2005 Juliusz Chroboczek <[EMAIL PROTECTED]> > * Implement pull --no-working-dir. -- David Roundy http://www.darcs.net _______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
