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

Re: Fwd: [Survey] Signed push

From
Ted Ts'o <tytso@mit.edu>
Date
Sep 14, 2011, 12:56 UTC
Message-ID
<20110914125621.GE16815@dhcp-172-31-195-159.cam.corp.google.com>
In-Reply-To
<201109141428.53163.johanh@opera.com>
On Wed, Sep 14, 2011 at 02:28:52PM +0200, Johan Herland wrote:
Show 17 quoted lines
> On Wednesday 14. September 2011, Matthieu Moy wrote:
> > Michael Haggerty <mhagger@alum.mit.edu> writes:
> > > I wish that one could annotate a branch (e.g., at creation) and
> > > have the annotation follow the branch around.  This would be a
> > > useful place to record *why* you created the branch, your plans
> > > for it, etc.  The annotation should be modifiable, because often a
> > > branch evolves in unforeseen ways during its lifetime.  Anybody
> > > could read the annotation to get a quick idea of what kind of work
> > > is in progress.
> > 
> HOWEVER, "git notes prune" will assume that the SHA1 keys are supposed 
> to identify existing git objects, and will delete any note whose SHA1 
> key does not identify a reachable git object.
> 
> Hence, if you promise to never run "git notes prune" on 
> refs/notes/branch-descriptions, you could use that ref to store your 
> branch descriptions keyed by the SHA1 of your branch name.

It seems like notes is the wrong place to encode this. If people really want this, what if there was a convention where there could be a separate branch head: ref/heads/META

which contained a directory structure like this:

<e-mail>/key # The developer's GPG key <e-mail>/<tree>/URL # URL of developer's tree named <tree> <e-mail>/<tree>/description # Descrition of <tree> <e-mail>/<tree>/branch/<branch-name> # A description of that branch

etc.

Since it's a separate branch head, the contents can be pushed around and merged very easily, and there's no danger of the information getting lost via a garbage collection or prune operation.

If there was an association between a local branch and <e-mail>/<tree> that it was tracking, then either a modified git core or porcelein command could get the information from the META tree. It would also make it easy to fetch a developer's GPG key without having to go to outside GPG key servers, which is a minor benefit (although maybe that's not worth it).

	     	   	   	      	 - Ted
Previous: Johan HerlandNext: Linus Torvalds
Message 23 of 62 in “[Survey] Signed push”
  1. Junio C HamanoSep 13, 2011
  2. 0/2 State commit name explicitly in request-pull messagesJunio C Hamano, Sep 13, 2011
  3. 1/2 fetch: allow asking for an explicit commit object by nameJunio C Hamano, Sep 13, 2011
  4. 2/2 request-pull: state exact commit object nameJunio C Hamano, Sep 13, 2011
  5. Guenter RoeckSep 13, 2011
  6. Junio C HamanoSep 13, 2011
  7. Junio C HamanoSep 14, 2011
  8. Sam VilainSep 14, 2011
  9. Shawn PearceSep 14, 2011
  10. Sam VilainSep 14, 2011
  11. Nguyen Thai Ngoc DuySep 14, 2011
  12. Jonathan NiederSep 14, 2011
  13. Nguyen Thai Ngoc DuySep 14, 2011
  14. Jeff KingSep 15, 2011
  15. Andy LutomirskiSep 14, 2011
  16. Junio C HamanoSep 14, 2011
  17. Andrew LutomirskiSep 14, 2011
  18. Fwd: [Survey] Signed pushLinus Torvalds, Sep 14, 2011
  19. Michael HaggertySep 14, 2011
  20. Matthieu MoySep 14, 2011
  21. Nguyen Thai Ngoc DuySep 14, 2011
  22. Johan HerlandSep 14, 2011
  23. Ted Ts'oSep 14, 2011
  24. Linus TorvaldsSep 14, 2011
  25. Matthieu MoySep 14, 2011
  26. Johan HerlandSep 14, 2011
  27. Philip OakleySep 14, 2011
  28. Linus TorvaldsSep 14, 2011
  29. Junio C HamanoSep 14, 2011
  30. Linus TorvaldsSep 14, 2011
  31. Junio C HamanoSep 14, 2011
  32. Linus TorvaldsSep 14, 2011
  33. Junio C HamanoSep 14, 2011
  34. Sam VilainSep 14, 2011
  35. request-pull: state what commit to expectJunio C Hamano, Sep 16, 2011
  36. Junio C HamanoSep 20, 2011
  37. 2/3 branch: teach --edit-description optionJunio C Hamano, Sep 20, 2011
  38. Andrew ArdillSep 21, 2011
  39. Junio C HamanoSep 21, 2011
  40. request-pull: use the branch descriptionJunio C Hamano, Sep 20, 2011
  41. 0/6 A handful of "branch description" patchesJunio C Hamano, Sep 22, 2011
  42. 1/6 branch: add read_branch_desc() helper functionJunio C Hamano, Sep 22, 2011
  43. 2/6 format-patch: use branch description in cover letterJunio C Hamano, Sep 22, 2011
  44. 3/6 branch: teach --edit-description optionJunio C Hamano, Sep 22, 2011
  45. Michael J GruberSep 23, 2011
  46. Nguyen Thai Ngoc DuySep 23, 2011
  47. Junio C HamanoSep 23, 2011
  48. Nguyen Thai Ngoc DuySep 25, 2011
  49. 4/6 request-pull: modernize styleJunio C Hamano, Sep 22, 2011
  50. 5/6 request-pull: state what commit to expectJunio C Hamano, Sep 22, 2011
  51. 6/6 request-pull: use the branch descriptionJunio C Hamano, Sep 22, 2011
  52. Michael J GruberSep 23, 2011
  53. Jeff KingSep 23, 2011
  54. Junio C HamanoSep 23, 2011
  55. Jeff KingSep 23, 2011
  56. Michael J GruberSep 24, 2011
  57. Jeff KingSep 27, 2011
  58. Annotated branch ≈ annotated tag?Michael Haggerty, Sep 28, 2011
  59. Andrew ArdillSep 28, 2011
  60. Michael HaggertySep 28, 2011
  61. Branch annotations [Re: Annotated branch ≈ annotated tag?]Michael J Gruber, Sep 28, 2011
  62. Jeff KingSep 29, 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.