git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Sidhant Sharma <tigerkid001@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: log --pretty accepts incomplete pre-defined formats
Date: Wed, 6 Apr 2016 14:07:01 -0700	[thread overview]
Message-ID: <CAPc5daVQwP2ZxpK6+57q+_EZLTU=CuHmcVT_VHmFH-KxrSKMog@mail.gmail.com> (raw)
In-Reply-To: <20160406210339.GA18799@dcvr.yhbt.net>

On Wed, Apr 6, 2016 at 2:03 PM, Eric Wong <normalperson@yhbt.net> wrote:
>> which was slightly tightend by aacd404e (Fix some
>> documentation typos and grammar, 2007-02-02).
>
> Huh?

Huh indeed.

b6936205 (Disallow invalid --pretty= abbreviations, 2007-02-02)

was what I meant to name.

      reply	other threads:[~2016-04-06 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  6:13 log --pretty accepts incomplete pre-defined formats Sidhant Sharma
2016-04-06 15:15 ` Junio C Hamano
2016-04-06 21:03   ` Eric Wong
2016-04-06 21:07     ` Junio C Hamano [this message]

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='CAPc5daVQwP2ZxpK6+57q+_EZLTU=CuHmcVT_VHmFH-KxrSKMog@mail.gmail.com' \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=tigerkid001@gmail.com \
    /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).