Mark Stosberg <[email protected]> writes:
>> 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
Here's my five-second effort:
$ darcs changes --max 1 -s -p 'Fix our version mechanism' --xml |
xmlstarlet sel -t -v /changelog/patch/summary |
tr -s '[:space:]' '\n'
Setup.lhs
darcs.cabal
src/Darcs/Commands/Help.lhs
src/Preproc.hs
src/ThisVersion.hs
src/darcs.hs
src/witnesses.hs
Correct support for add/remove/move primitives, and add/remove line
counts for modify hunks, are left as exercises for the reader.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
