From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: show merge info for git vc-log
Date: Thu, 09 Jul 2009 07:01:35 +0200 [thread overview]
Message-ID: <87zlbezbyo.fsf@tux.homenetwork> (raw)
In-Reply-To: <200907082208.n68M8Ixc024022@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Wed, 8 Jul 2009 15:08:18 -0700 (PDT)")
Dan Nicolaescu <dann@ics.uci.edu> writes:
> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>
> > Dan Nicolaescu <dann@ics.uci.edu> writes:
> >
> > > Dmitry Dzhus <dima@sphinx.net.ru> writes:
> > >
> > > > Mercurial can do the same with graphlog extension enabled (it's included
> > > > in Mercurial distribution now) if we add `-G` flag in
> > > > `vc-hg-log-switches`.
> > >
> > > Is there a way to force that flag to work?
> > >
> > > $ hg log -G
> > > hg log: option -G not recognized
> > > hg log [OPTION]... [FILE]
> >
> > Add this to your .hgrc
>
> That's not good. To enable this by default, we need to be able to force
> this flag to work from the command line.
>
That will work on the command line only if you activate the extension in
your .hgrc.
What is the problem? you try to enable a log with the graph, if it not
available, you fallback to a normal log. Or with a variable, something
like `vc-hg-use-graphlog'.
What do you want to do exactly, add support for that in vc?
--
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France
next prev parent reply other threads:[~2009-07-09 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 18:33 show merge info for git vc-log Dan Nicolaescu
2009-07-07 19:16 ` Leo
2009-07-07 23:09 ` Dmitry Dzhus
2009-07-08 20:44 ` Dan Nicolaescu
2009-07-08 21:35 ` Thierry Volpiatto
2009-07-08 22:08 ` Dan Nicolaescu
2009-07-09 2:11 ` Kevin Rodgers
2009-07-09 3:24 ` Dan Nicolaescu
2009-07-09 5:01 ` Thierry Volpiatto [this message]
2009-07-09 5:51 ` Dan Nicolaescu
2009-07-09 19:09 ` Dmitry Dzhus
2009-07-11 19:40 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zlbezbyo.fsf@tux.homenetwork \
--to=thierry.volpiatto@gmail.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.