git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: catalin.marinas@gmail.com
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Junio C Hamano" <junkio@cox.net>
Subject: Possible BUG with git-rev-list --all in a StGit repository
Date: Sun, 26 Nov 2006 17:27:27 +0100	[thread overview]
Message-ID: <e5bfff550611260827t686a5071w7f050f17f784e5d9@mail.gmail.com> (raw)

In a StGit repository the --all option causes a lot of spurious
revisions, possibly stgit related.

$ git branch
* master
  origin
  test

$ git rev-list master origin test -- src/settingsimpl.cpp | wc
     13      13     533

$ git rev-list --all -- src/settingsimpl.cpp | wc
     26      26    1066


The extra revisions have shortlogs of the kind of:

 push        a3bc76fd0bdd154149c26a3c208f0344e9cd873b
 new e7baf56544cd8b4f8601a35fad274b8de97fd558
refresh     8fa01a56a40b04ed9c6d006c669ca9d370176728

From qgit these are easily seen from file history tab of a file
modified by stgit patches or when filtering in main view on the same
file.

Shouldn't 'git-rev-list --all'  print  *the same output* of when the
list  with all branches is given in command line?

Thanks
Marco

P.S:
$ git version
git version 1.4.4.1.g7002
$ stg --version
Stacked GIT 0.11
git version 1.4.4.1.g7002
Python version 2.4.3 (#2, Oct  6 2006, 15:32:41)

             reply	other threads:[~2006-11-26 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26 16:27 Marco Costalba [this message]
2006-11-26 20:16 ` Possible BUG with git-rev-list --all in a StGit repository Junio C Hamano
2006-11-27  6:31   ` Marco Costalba
2006-11-27  6:38     ` Marco Costalba
2006-11-27  7:25       ` Junio C Hamano
2006-11-27 15:09         ` [PATCH] revision traversal: Add --refs=<pattern> option Sergey Vlasov
2006-11-27 23:59           ` Junio C Hamano
2006-11-28  7:57         ` Possible BUG with git-rev-list --all in a StGit repository Marco Costalba
2006-11-28  8:41           ` Junio C Hamano
2006-11-28 12:11             ` Marco Costalba

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=e5bfff550611260827t686a5071w7f050f17f784e5d9@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.
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).