git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alessandro Di Marco <dmr@ethzero.com>,
	Antoine Pelisse <apelisse@gmail.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>,
	git <git@vger.kernel.org>
Subject: Re: [PATCH] Geolocation support
Date: Mon, 9 Feb 2015 14:57:02 +0100	[thread overview]
Message-ID: <CACBZZX5rgah7Ucek8dicaDeqvjdkR5ybBC5O7PUxE8+KBwrpgA@mail.gmail.com> (raw)
In-Reply-To: <CAPc5daW5jYAj5z6UMJAQLoWS4L6OH-NSvbGBMd3LO0qCV40a4A@mail.gmail.com>

On Mon, Feb 9, 2015 at 2:24 AM, Junio C Hamano <gitster@pobox.com> wrote:
> In case I was not clear, I do not think it is likely for us to accept
> a patch that mucks with object header fields with this information.
> Have them in the log text and let UI interpret them.

We've already told clients for a long time to ignore fields they don't
know about, why would we not store what's intended to be
machine-readable key-value pair data in the commit object itself, as
opposed to sticking it in the log message where parsing it is always
going to be a bit more tricky & distracting, since users will have to
look at this arbitrary metadata when they do "git log" or "git show".

  reply	other threads:[~2015-02-09 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 13:25 [PATCH] Geolocation support Alessandro Di Marco
2013-05-23  8:45 ` Ramkumar Ramachandra
2013-05-23  9:52   ` Antoine Pelisse
2013-05-23 11:58     ` Alessandro Di Marco
2013-05-23 17:48     ` Junio C Hamano
2015-02-09  0:03       ` Alessandro Di Marco
2015-02-09  1:24         ` Junio C Hamano
2015-02-09 13:57           ` Ævar Arnfjörð Bjarmason [this message]
2015-02-09 19:13             ` Junio C Hamano
2015-02-12 20:50               ` Alessandro Di Marco
2015-02-12 20:57                 ` Junio C Hamano

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=CACBZZX5rgah7Ucek8dicaDeqvjdkR5ybBC5O7PUxE8+KBwrpgA@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=apelisse@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=dmr@ethzero.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).