> Here's my use case: I'm doing a peer review of a set patches that relate to a > certain ticket number. I want to make sure that I review each changed file, > so I would use this report as a checklist. > > In the past I've accomplished this by using "darcs changes --summary" and then > munging the results to a get unique list of files.
Here's the recipe I used for this today: darcs changes -p 7718 --summary | grep '\./' | cut -d ' ' -f 6-10 | sort -u As an alternative to having this in darcs, I suppose I could keep this in a reusable bash script. Mark _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
