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

Re: git format-patch should honor notes

From
Johan Herland <johan@herland.net>
Date
Dec 8, 2010, 10:12 UTC
Message-ID
<201012081112.12112.johan@herland.net>
In-Reply-To
<4CFF3FE4.4080104@warpmail.net>
On Wednesday 08 December 2010, Michael J Gruber wrote:
Show 7 quoted lines
> Also, in order to be really useful, I would need a place to store the
> cover letter also. I was experimenting a while back with a design for
> annotating branchnames which "basically" worked but haven't had time
> to really implement it. If I remember correctly, I had to set up some
> "bogus" refs to keep my notes from being garbage collected and was
> still figuring out the best place to put them. I'll dig it up when I
> have time to.

I believe the last time the issue of adding notes to branch names was discussed, the consensus was that rather than using notes, they could be stored using a custom entry in the config file, e.g.

  git config branch.mybranch.description "Description of mybranch"
I might have misremembered this, though.
...Johan
-- 
Johan Herland, <johan@herland.net>
www.herland.net
Previous: Michael J GruberNext: Michael J Gruber
Message 5 of 8 in “git format-patch should honor notes”
  1. Eric BlakeDec 7, 2010
  2. Junio C HamanoDec 7, 2010
  3. Jeff KingDec 7, 2010
  4. Michael J GruberDec 8, 2010
  5. Johan HerlandDec 8, 2010
  6. Michael J GruberDec 8, 2010
  7. Johan HerlandDec 8, 2010
  8. Thomas RastDec 8, 2010

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.