Hi, Hoan Ton-That has submitted a patch that adds a darcs ignore mechanism. The basic idea is that ignored files are skipped when you do a darcs record, even if it's something that darcs is supposed to be keeping track of.
I am inclined to accept this feature (with a few modifications), but wanted to see what you might think. I understand that this is not the most general solution -- domains might be a better choice -- but what I imagine is that if we did manage to implement such a system, we would always be able to translate the ignore mechanism into the more general terms. One question for the community: Do we actually want an actual ignore/unignore command, or would an ignore file suffice? I would suggest that an ignore file is plenty, and that two extra commands would just be clutter. Any thoughts on the matter? Thanks! -- Eric Kow http://www.loria.fr/~kow PGP Key ID: 08AC04F9 Merci de corriger mon français.
--- Begin Message ---Hey everyone, I wrote this feature because I was working on a repository with configuration files in it. I was always being pestered about the changes I made to them, but I never wanted to record them, because they were local changes (like a STMP server address). Boring files didn't do the job, as they only stop certain files from being added. Once they have been added, darcs still asks for their changes. You might be working on darcs (as I was) and have modified the makefile so it still compiles despite warnings. Here is an example of the new commands in action: ~/haskell/darcs> darcs whatsnew { hunk ./GNUmakefile 14 -GHCFLAGS += -Wall -Werror -I. +GHCFLAGS += -Wall -I. } ~/haskell/darcs> darcs ignore GNUmakefile ~/haskell/darcs> darcs whatsnew No changes! ~/haskell/darcs> darcs unignore GNUmakefile ~/haskell/darcs> darcs whatsnew { hunk ./GNUmakefile 14 -GHCFLAGS += -Wall -Werror -I. +GHCFLAGS += -Wall -I. } All the files that are ignored are stored in the ignorefile, which is _darcs/prefs/ignore by default. You can use darcs setpref ignorefile .ignore to change it, just like you do with boringfile. Also the revert, whatsnew, record and amend-record commands now take a --ignore option which ignores the ignores. So to take a look at all the changes: ~/haskell/darcs> darcs ignore GNUmakefile ~/haskell/darcs> darcs whatsnew No changes! ~/haskell/darcs> darcs whatsnew --ignore { hunk ./GNUmakefile 14 -GHCFLAGS += -Wall -Werror -I. +GHCFLAGS += -Wall -I. } A few people on IRC were supportive of this, including Eric Kow. lispy suggested the names ignore/unignore instead of hide/show. I think its worth adding these two commands, they're both easy to use, and still won't clutter up the interface. I'd also like to give a big thank you to David for creating darcs in the first place---its wonderful. Not just in ease of use, but the internals are sparkling clean as well. It didn't take me long to feel comfortable making changes to the code. I hope you guys appreciate this as much as I love darcs. Hoan
CHANGESET
Description: Binary data_______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
--- End Message ---
pgp9GM8dJLtMw.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
