From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Steven Drake <sdrake@xnet.co.nz>
Subject: Re: What's cooking in git.git (Mar 2010, #02; Sun, 07)
Date: Wed, 10 Mar 2010 14:59:42 -0500 [thread overview]
Message-ID: <20100310195941.GA32387@sigill.intra.peff.net> (raw)
In-Reply-To: <7vvdd5t2lf.fsf@alter.siamese.dyndns.org>
On Tue, Mar 09, 2010 at 04:58:04PM -0800, Junio C Hamano wrote:
> > With the current code, gitk (which calls "log --pretty=raw") barfs on a
> > repository with log.decorate turned on.
>
> Yuck. Do you mean we would need _at least_ something like this? I am
Yeah, your patch fixes the problem.
> undecided if we should limit to FMT_RAW if that is the case, though.
> Reading from "git log --pretty=raw" is just as unkosher as reading from
> "git log --pretty=oneline", but a bigger question is do we still have
> enough plumbing support to replace them, or Porcelain "log" has advanced
> too much too quickly, leaving plumbing "rev-list" behind.
It looks like the switch to "git log" in gitk came from c961b22 (gitk:
Use git log and add support for --left-right, 2007-07-09), which in
turn comes from:
http://article.gmane.org/gmane.comp.version-control.git/51977
It looks like rev-list supports --left-right properly now (not sure if
it did back then or not), so if that was the only reason, it could
probably switch back.
I seem to recall there are other reasons to use "log" in a script, but I
can't remember any off the top of my head.
-Peff
next prev parent reply other threads:[~2010-03-10 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 22:49 What's cooking in git.git (Mar 2010, #02; Sun, 07) Junio C Hamano
2010-03-08 9:20 ` Junio C Hamano
2010-03-09 23:13 ` Jeff King
2010-03-10 0:58 ` Junio C Hamano
2010-03-10 19:59 ` Jeff King [this message]
2010-03-08 12:23 ` SZEDER Gábor
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=20100310195941.GA32387@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sdrake@xnet.co.nz \
/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).