Hmmm... a bit too tricky for someone trying to learn darcs' ropes. I guess I'll stick with the "measure twice, cut once" for now - but this may be a usability point that the developers might like to address...
On 11/15/05, Tommy Pettersson <[EMAIL PROTECTED]> wrote: > > Now I've read your initial question more carefully, sorry for > leading astray at first. Messing with _darcs/patches/pending > is only good for unrecorded changes. > > 'darcs remove file' will create a patch in pending, that when > recorded removes the file from pristine, without removing > it from working, which is exactly what you want. However, > when this patch is pulled/pushed somewhere, it _will_ remove > the file from the working dir in the target repo, which is > _not_ what you want. I don't think there is a convenient way > around this problem yet. You'll have to remove the patches > that adds the config file (and the history of it) in every > repo manually. First unrecord the patch that creates the > config file. That will bring the patch to pending. Then use > 'darcs remove' to cancel the addfile from pending (as David > suggested -- I was unaware of this feature) but leaves the > file intact in working. > > > -- > Tommy Pettersson <[EMAIL PROTECTED]> > _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
