git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Joey Hess <joey@kitenet.net>
Cc: git@vger.kernel.org
Subject: Re: git notes: notes
Date: Wed, 20 Jan 2010 12:10:30 -0800	[thread overview]
Message-ID: <7vska01qrt.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100120195626.GA6641@gnu.kitenet.net> (Joey Hess's message of "Wed\, 20 Jan 2010 14\:56\:26 -0500")

Joey Hess <joey@kitenet.net> writes:

> Do you think it makes sense for even git log --format=format:%s to be
> porcelain and potentially change when new features are used?

If the series changed the meaning of "%s" format to mean "the subject of
the commit and notes information", with or without documenting it, then it
is just a bug we would like to fix.

But I cannot reproduce such a bug.  In my tree locally:

    $ git notes show a97a74
    Origin of commit notes feature was at
    a97a74).
    $ git show -s --pretty=short a97a74
    commit a97a74686d70a318cd802003498054cc1e8b0ae2
    Author: Johannes Schindelin <Johannes.Schindelin@gmx.de>

        Introduce commit notes

    Notes:
        Origin of commit notes feature was at
        a97a74).
    $ git show -s --pretty=format:%s a97a74
    Introduce commit notes

Puzzled...

  reply	other threads:[~2010-01-20 20:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  5:03 git notes: notes Joey Hess
2010-01-20  9:48 ` Thomas Rast
2010-01-20 18:14   ` Joey Hess
2010-01-20 10:48 ` Johan Herland
2010-01-20 18:24   ` Joey Hess
2010-01-20 19:30     ` Junio C Hamano
2010-01-20 19:56       ` Joey Hess
2010-01-20 20:10         ` Junio C Hamano [this message]
2010-01-20 20:36           ` Joey Hess
2010-01-20 20:54             ` Jeff King
2010-01-20 20:59               ` Junio C Hamano
2010-01-20 21:31                 ` Jeff King
2010-01-20 21:41                   ` Jeff King
2010-01-20 22:07                     ` Junio C Hamano
2010-01-20 22:21                       ` Jeff King
2010-01-20 21:02           ` Michael J Gruber
2010-01-20 21:08             ` Junio C Hamano
2010-01-20 21:36               ` Jeff King
2010-01-20 21:59               ` Junio C Hamano
2010-01-20 22:25                 ` Jeff King
2010-01-20 22:33                   ` Junio C Hamano
2010-01-20 22:58                 ` Johannes Schindelin
2010-01-20 23:06                   ` Jeff King
2010-01-20 23:14                   ` Junio C Hamano
2010-01-21  2:54                     ` Johan Herland
2010-01-21  3:03                       ` Junio C Hamano
2010-01-21  3:37                     ` Junio C Hamano
2010-01-21  8:45               ` Michael J Gruber
2010-01-24 14:20               ` Matthieu Moy
2010-01-24 14:27                 ` Sverre Rabbelier
2010-01-21  2:05     ` Johan Herland
2010-01-21  3:59       ` Johannes Schindelin
2010-01-21  4:05         ` Joey Hess
2010-01-27 11:55           ` Johan Herland
2010-01-25 18:08       ` John Koleszar
2010-01-27 20:01         ` Christian Couder

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=7vska01qrt.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=joey@kitenet.net \
    /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).