From: Matthias Kestenholz <lists@irregular.ch>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Bug in git log
Date: Tue, 2 May 2006 15:41:58 +0200 [thread overview]
Message-ID: <20060502134158.GC4592@spinlock.ch> (raw)
In-Reply-To: <7virooomve.fsf@assigned-by-dhcp.cox.net>
* Junio C Hamano (junkio@cox.net) wrote:
> [...]
> We used to have a build problem where we forgot to remove
> libgit.a and an old object from the archive was used by
> mistake. Could you try rm -f libgit.a and rebuild your git to
> see if it helps?
>
Ok I did that. I also removed all files which were installed by
'make install' and did a complete rebuild and install of the current
master branch. My git version is now 1.3.1.g7464
The "double dash" problem is not a big deal since it only happens
with the deprecated shellscript-version of whatchanged.
Does anyone get some output with the following command? That was the
bug I tried to report (sorry for my bad/convoluted english)
$ git log -- unresolve.c
--
:wq
next prev parent reply other threads:[~2006-05-02 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 7:51 Bug in git log Matthias Kestenholz
2006-05-02 8:24 ` Junio C Hamano
2006-05-02 13:41 ` Matthias Kestenholz [this message]
2006-05-02 15:26 ` Linus Torvalds
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=20060502134158.GC4592@spinlock.ch \
--to=lists@irregular.ch \
--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 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.