From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: git <git@vger.kernel.org>, "Junio C Hamano" <junkio@cox.net>,
"Linus Torvalds" <torvalds@osdl.org>
Subject: git-log --parents broken post v1.3.0
Date: Wed, 3 May 2006 23:56:16 +1200 [thread overview]
Message-ID: <46a038f90605030456q679ceebcsa037b834bced9ca2@mail.gmail.com> (raw)
Soon after v1.3.0 git-log --parents got broken. When using --parents,
the 'commit <sha1>' opening line would also list the SHA1 of the
parent commits. This seems to have broken git-cvsserver.
Just by testing git-cvsserver, git-bisect has said that
9153983310a169a340bd1023dccafd80b70b05bc is first bad commit
Author: Linus Torvalds <torvalds@osdl.org>
Date: Mon Apr 17 11:59:32 2006 -0700
Log message printout cleanups
But I am not too confident that it's this particular commit -- but it
is definitely one in this series. I had suspected of changes in
git-diff-tree, but the output of git-diff-tree remains unchanged as
far as I could test it.
cheers,
martin
next reply other threads:[~2006-05-03 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 11:56 Martin Langhoff [this message]
2006-05-03 12:10 ` git-log --parents broken post v1.3.0 Martin Langhoff
2006-05-03 14:59 ` Linus Torvalds
2006-05-03 22:14 ` Martin Langhoff
2006-05-03 22:53 ` [PATCH] cvsserver: use git-rev-list instead of git-log Martin Langhoff
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=46a038f90605030456q679ceebcsa037b834bced9ca2@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).