Ray Lee wrote:
it allows regular expressions for the match and replace, which means
multiple unique tokens could change atomically. (Does anyone actually
*use* regexes? Sounds like a cannon that'd be hard to aim.)
Yes, and replace patches need to be used very carefully.
Regardless, I only care a
Ray Lee wrote:
I'm still not communicating well.
Give me a case where assuming it's a replace will do the wrong thing,
for C code, where it's a variable or function name.
Ray
-
I think you are communicating fine, but not fully understanding darcs.
try this:
initial patch creates hello.c
#include
i
Ray Lee wrote:
Here's where we disagree. If you checkpoint your tree before the
replace, and immediately after, the only differences in the
source-controlled files would be due to the replace.
This is assuming that you only have one replace and no other operations
recorded in the patch. If you hav
Linus Torvalds wrote:
(In other words: if it looks like something a careful human _could_ have
written, it's certainly ok. But if it looks like something a careful human
would have used a script to generate 40 entries of, it's bad).
Linus
This is the way that darcs would currently represent a
4 matches
Mail list logo
