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: Re: git-log --parents broken post v1.3.0
Date: Thu, 4 May 2006 00:10:00 +1200 [thread overview]
Message-ID: <46a038f90605030510x6d582804w6c0d2fec60bd56e5@mail.gmail.com> (raw)
In-Reply-To: <46a038f90605030456q679ceebcsa037b834bced9ca2@mail.gmail.com>
On 5/3/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> Soon after v1.3.0 git-log --parents got broken. When using --parents,
Ok -- perhaps that was a bit of a rushed statement. Reading back on
the archives, it seems like it may have been intentional. The new
header format is more succint, but while technically I can fish the
data at the porcelain layer, it is quite convenient to get it directly
from the commit header. Specially given that git-log has the info at
that time...
I have to confess, I don't quite follow the changes happening in that
series of commits. If --parents is really not coming back I'll change
the log entry parsing in cvsserver. However, I suspect git-log should
error out on it ("fatal: deprecated option") so porcelains break
explicitly, rather than silently.
cheers,
martin
next prev parent reply other threads:[~2006-05-03 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 11:56 git-log --parents broken post v1.3.0 Martin Langhoff
2006-05-03 12:10 ` Martin Langhoff [this message]
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=46a038f90605030510x6d582804w6c0d2fec60bd56e5@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).