[darcs-users] Fwd: Darcs Problems
Ben Franksen
benjamin.franksen at bessy.de
Sat Mar 2 11:43:55 UTC 2013
Stephen J. Turnbull wrote:
> Ganesh Sittampalam writes:
> > On 28/02/2013 15:14, Stephen J. Turnbull wrote:
> >
> > > Indeed, I find it surprising that Darcs has no equivalent to "bzr
> > > missing" or "hg incoming/outgoing". (git rev-list would be overkill
> > > for Darcs!)
> >
> > Do darcs pull/push --dry-run -a fulfill this purpose?
>
> Yes, in great part. But note that both bzr missing and hg outgoing
> accept log-like options such as -p (show patch), so you can get a lot
> more information than just the identity of the commits. AFAIK pull
> dry-run only gives patch identities.
In Darcs there is -s (--summary, show affected files) and -v (--verbose,
show everything including hunks). You can also use -i (--interactive) and
use 'x' and 'v' to see these informations for the currently selected patch.
However, sometimes it can be cumbersome to issue
> darcs whatsnew -l
> darcs push --dry-run
> darcs pull --dry-run
to get a summary of all the differences between 'here' and 'upstream'. A
single command that does this would be helpful. Or, even better, a way to
create new Darcs commands as aliases for one or more other commands (with
options. I imagine something like a ~/.darcs/aliases that I could fill with
things like
outgoing = push --dry-run
incoming = pull --dry-run
compare = whatsnew -l && incoming && outgoing
gdiff = diff --diff-command="kompare %1 %2"
This shouldn't be too hard to do. Bonus points for listing these in 'darcs
help' and 'darcs --commands'. Extra bonus points for devising a way to
declare how to distribute options given to such a command to its
constituents.
Cheers
--
Ben Franksen
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
More information about the darcs-users
mailing list