unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: show merge info for git vc-log
Date: Wed, 8 Jul 2009 22:51:57 -0700 (PDT)	[thread overview]
Message-ID: <200907090551.n695pvZ0000269@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87zlbezbyo.fsf@tux.homenetwork> (Thierry Volpiatto's message of "Thu, 09 Jul 2009 07:01:35 +0200")

Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:

  > 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'.

See what I wrote above your answer.

Yes, it can be solved, but I won't add extra complexity and inconsistent
behavior that depends of the contents of users .hgrc.

Consistent behavior cannot be obtained as long as the graphlog is
something that requires the user to edit her .hgrc.




  reply	other threads:[~2009-07-09  5:51 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
2009-07-09  5:51           ` Dan Nicolaescu [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200907090551.n695pvZ0000269@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=thierry.volpiatto@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).