Git development
 help / color / mirror / Atom feed
From: Torgny Nyblom <kde@nyblom.org>
To: git@vger.kernel.org
Subject: git log broken?
Date: Wed, 22 Sep 2010 09:48:08 +0200	[thread overview]
Message-ID: <20100922094808.07be1757@explosive.nyblom.org> (raw)

Hi,

(Resend as it got no replies and I want to be sure that is wasn't lost
in the noise)

I'm working on converting the KDE subversion repository to git, as
a part of this I'm trying to validate that the conversion hasn't missed
any revisions or merges but when I run "git log" with different options
I get (in my mind) strange results.

git log <file> -> produces a list of commits
git log --follow <file> -> produces an empty list (no output)
git log --name-status <file> -> no info about file

It seems like this occurs when there is a merge only commit as the
first commit in the list returned by the "bare" log command.

Is there any legit situation where this might happen?
If so what?
If not is this a bug in my convert program or in git?

/Regards
Torgny

             reply	other threads:[~2010-09-22  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22  7:48 Torgny Nyblom [this message]
2010-09-22  8:05 ` git log broken? Matthieu Moy
2010-09-22  8:15 ` Michael J Gruber

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=20100922094808.07be1757@explosive.nyblom.org \
    --to=kde@nyblom.org \
    --cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox