git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Geolocation support

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Feb 9, 2015, 13:57 UTC
Message-ID
<CACBZZX5rgah7Ucek8dicaDeqvjdkR5ybBC5O7PUxE8+KBwrpgA@mail.gmail.com>
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".

Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 11 in “Geolocation support”
  1. Geolocation supportAlessandro Di Marco, May 22, 2013
  2. Ramkumar RamachandraMay 23, 2013
  3. Antoine PelisseMay 23, 2013
  4. Alessandro Di MarcoMay 23, 2013
  5. Junio C HamanoMay 23, 2013
  6. Alessandro Di MarcoFeb 9, 2015
  7. Junio C HamanoFeb 9, 2015
  8. Ævar Arnfjörð BjarmasonFeb 9, 2015
  9. Junio C HamanoFeb 9, 2015
  10. Alessandro Di MarcoFeb 12, 2015
  11. Junio C HamanoFeb 12, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.