[Re-sending this mail because of some local e-mail problem - apologies for possible duplicates.]
[Albert Reiner <[EMAIL PROTECTED]>, 10 Aug 2005 14:38:52 +0200]: > [Charles Goodwin <[EMAIL PROTECTED]>, Tue, 09 Aug 2005 19:45:59 +0100]: > > 2) Does not work on directories (MISSING FEATURE) > > It has always been my feeling that replace doesn't work correctly: > Especially given patch algebra I think that the natural operation is > to perform any given replacement over the whole repo by default, with an > additional option to restrict this to a subset of the files. IOW, I > always felt that > > darcs replace foo bar > > should replace foo by bar in all darcs-managed files, now and in the > future. This would be different from > > darcs replace --current-files foo bar > > that would do the replacement only in those files that are currently > part of the repo. (And I wonder if not such an --current-files option > might be handy for other commands, too, given the difficulty of > finding all the files darcs currently manages, especially in the > context of not yet recorded addfile's.) > > In QM-inspired notation, `darcs replace foo bar` would correspond to > an operator foo->bar, which is the fundamental replacement. It is > then easy to restrict it to file qux as > > |file qux> <foo->bar> <file qux| + |file /= qux><file /= qux|. > > And yes, I would expect `darcs replace foo bar` to cause pulling of an > addfile patch plus some contents to result in a new file where foo has > been replaced with bar. > > In short, I would love to see > > - REPLACE to work without explicit file list, with the above behavior; > and > > - an option --current-files (or similar) to apply REPLACE (and possibly > other commands) to all the files in the repo, plus those with > unrecorded addfiles, minus those with unrecorded removes. > > Albert. _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
