> You currently can get that info from darcs, but its nowhere near readable.
> What I think we need in this case is a little front-end to present this
> stuff in a nice way. I'm inclined to say some innovative GUI work is
> needed to do this in a user friendly manner.
Would you need a GUI for that ?
bash$ darcs --deps -p "Name of a patch"
Sat May 14 15:23:29 CEST 2005 [EMAIL PROTECTED]
* Bla
Sat May 14 15:23:29 CEST 2005 [EMAIL PROTECTED]
* Blo
Of course, the -p can be ambiguous, so maybe it could even be done
interactively, where you select a set of patches, and return the series
of patches which are needed. Actually, this would just be a pull --dry-run
from a clean repository, only without needing to create a clean repository
first.
> Same here; I noted this feature earlier as a grouping of existing patches.
> Meaning a set of patches are grouped, but the individual patches still
> exist separately on disk sidestepping the problem you saw already.
> Anyway; this is a good feature request; could you check if its marked on
> the bugtracker as such? (follow darcs.net for the bugtracker)
So, you would only have 1 changes entry for the series of patches, right ?
That sounds very good to me. I'll check the bugtracker.
> You will then have loads of problems with file renames and moves being shown
> as way too much text, though.
Well, you can't expect more from a unified diff, so i can live with that.
> Naturally a darcs diff -u --to-tag will do this best, and having all in one
> tree is also easiest. But your milage may differ.
I'll try that, thanks!
cheers,
Remko
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
