zsh-users
 help / color / mirror / code / Atom feed
From: Seth House <seth@eseth.com>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: Ioannis Koutras <ioannis.koutras@gmail.com>, zsh-users@zsh.org
Subject: Re: vcs_info on a hg repository with a git subrepository; actionformats works ok, formats does not
Date: Mon, 17 Sep 2012 09:57:29 -0700	[thread overview]
Message-ID: <CABsXarF5CM=CjhrrCsPBdY0es2SpY=dQC2116grsq4rYDPsE=g@mail.gmail.com> (raw)
In-Reply-To: <87vcfca9sa.fsf@ft.bewatermyfriend.org>

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

That may be the answer.

That said, their addition of git commands to the debug output isn't
outputting terribly useful info. I wonder if that is intentional.
Especially since the output differs with the presence of the -r flag. (I
will research.)

The --debug flag is used to get hg to output the full sha. Perhaps there is
a better way to get all req'd info.
On Sep 17, 2012 9:34 AM, "Frank Terbeck" <ft@bewatermyfriend.org> wrote:

> Seth House wrote:
> [...]
> > The output for the newer Mercurial is below:
> >
> > % hg --debug id -i -n -b
> > nested: git --version
> > nested: git config --bool core.bare
> > nested: git rev-parse HEAD
> > nested: git update-index -q --refresh
> > nested: git diff-index --quiet HEAD
> > 4a0f6db684a9b73ca8da117d2e368d309385bc20 1 default
>
> ...so, what's the solution? read data until there is no more to read and
> then use the data from the last line of the output?
>
> Regards, Frank
>

  reply	other threads:[~2012-09-17 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 13:37 Ioannis Koutras
2012-09-17 14:50 ` Frank Terbeck
2012-09-17 15:02   ` Ioannis Koutras
2012-09-17 15:15     ` Frank Terbeck
2012-09-17 15:38       ` Ioannis Koutras
2012-09-17 16:01         ` Frank Terbeck
2012-09-17 16:06           ` Seth House
2012-09-17 16:33             ` Frank Terbeck
2012-09-17 16:57               ` Seth House [this message]
2012-09-17 19:53                 ` Seth House
2012-09-17 20:23                   ` Seth House

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='CABsXarF5CM=CjhrrCsPBdY0es2SpY=dQC2116grsq4rYDPsE=g@mail.gmail.com' \
    --to=seth@eseth.com \
    --cc=ft@bewatermyfriend.org \
    --cc=ioannis.koutras@gmail.com \
    --cc=zsh-users@zsh.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 public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).