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

Re: [PATCH] fmt-merge-msg: use branch.$name.description

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Oct 7, 2011, 09:45 UTC
Message-ID
<4E8ECA25.205@drmicha.warpmail.net>
In-Reply-To
<20111007091636.GA22822@elie.hsd1.il.comcast.net>
Jonathan Nieder venit, vidit, dixit 07.10.2011 11:16:
Show 7 quoted lines
> Michael J Gruber wrote:
> 
>> config based is so non-distributed, local in nature.
> 
> I don't follow.  Wouldn't a protocol change be enough to fix that, by
> sharing branch descriptions analagously to how refs themselves are
> shared?

I'd be surprised if we changed the protocol just to be able to share some descriptions, when we have everything we need for sharing refs. Also note that config is non-versioned etc.

But my main point here is that we should discuss the pros and cons of each approach in context (the context of the original thread), and I haven't heard many pros and cons for either.

Michael
Previous: Jonathan NiederNext: Jonathan Nieder
Message 4 of 12 in “fmt-merge-msg: use branch.$name.description”
  1. fmt-merge-msg: use branch.$name.descriptionJunio C Hamano, Oct 7, 2011
  2. Michael J GruberOct 7, 2011
  3. Jonathan NiederOct 7, 2011
  4. Michael J GruberOct 7, 2011
  5. Jonathan NiederOct 7, 2011
  6. Michael J GruberOct 7, 2011
  7. Jonathan NiederOct 7, 2011
  8. Junio C HamanoOct 7, 2011
  9. Michael J GruberOct 7, 2011
  10. Jonathan NiederOct 7, 2011
  11. Junio C HamanoOct 7, 2011
  12. Jakub NarebskiOct 8, 2011

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.