Alberto Bertogli wrote:
It uses "darcs changes -v" output to get the darcs patch, and does some
simple parsing based on the rules you sent on a previous email.
It makes the alternative patch views appear on the regular diff views
(commitdiff, filediff, headdiff, headfilediff). It provides the unified
(default) one, plain, darcs; and in commitdiff's case also a raw one taken
right out of the patch file that will probably go away at some point if
the patch format is changed or it begins to break, so don't rely on it.
great :)
a small note: in darcs_commitdiff mode the raw_commitdiff link is missing
I haven't tested it widely, but I think it works; it's in the current
repository. If you try it, let me know how it goes.
hmm, one bug, but i'm not sure if it is related to the recent changes:
if you view the 'commit' of a patch that contains (only?) replaces, then
it will be shown as binary. that may be ok. but then if you go to the
filediff on that page, an error occures as the 'f' parameter left blank
for example:
http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=setup;a=filediff;h=20050827205444-e2957-58eddfb46ddfbd5fe20b5fc5c3292941f99476b2.gz;f=
PS: before somebody asks, I know some people would like the darcs format
to be the default (I certanly don't). I will see in the future if I can
make it configurable, but the code as-is makes this a bit tricky and
implementing it will require some cleanup and reorganization.
and what about a 'darcs_commitdiff' link after the commit and commitdiff
ones?
udv / greetings,
VMiklos
--
Developer of Frugalware Linux, to make things frugal - http://frugalware.org
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
