From: Johannes Sixt <J.Sixt@eudaptics•com>
To: git@vger•kernel.org
Cc: Junio C Hamano <gitster@pobox•com>
Subject: Re: Recent issues
Date: Mon, 09 Jul 2007 12:20:10 +0200 [thread overview]
Message-ID: <46920BDA.C1AC9F51@eudaptics.com> (raw)
In-Reply-To: 18065.65446.474822.436800@cargo.ozlabs.ibm.com
Paul Mackerras wrote:
>
> Junio C Hamano writes:
>
> > * gitk --left-right
> >
> > From: Linus Torvalds <torvalds@linux-foundation•org>
> > Message-ID: <alpine.LFD.0.98.0705051524300.17381@woody•linux-foundation.org>
> > From: Junio C Hamano <junkio@cox•net>
> > Message-ID: <7vabwifl23.fsf@assigned-by-dhcp•cox.net>
> >
> > Paulus?
>
> Looks mostly OK; I assume there's no possible downside to using git
> log -v --pretty=raw rather than git rev-list?
In general, there is a big down-side, although I don't know if this
particular case is affected: --pretty=raw prints the parents noted in
the commit object, but not those from .git/info/grafts.
-- Hannes
next prev parent reply other threads:[~2007-07-09 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 7:31 Recent issues Junio C Hamano
2007-07-09 9:28 ` Paul Mackerras
2007-07-09 10:20 ` Johannes Sixt [this message]
[not found] ` <18066.4639.682605.171418@cargo.ozlabs.ibm.com>
2007-07-09 11:03 ` Johannes Sixt
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=46920BDA.C1AC9F51@eudaptics.com \
--to=j.sixt@eudaptics$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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