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

Re: Storing additional information in commit headers

From
MKmartin f krafft <madduck@madduck.net>
Date
Aug 1, 2011, 18:34 UTC
Message-ID
<20110801183411.GA5182@fishbowl.rw.madduck.net>
In-Reply-To
<CAGdFq_h5gimMkwhyOv0PFqVwx4pExL7Zri8Tki_dT5HDtFcBFA@mail.gmail.com>
also sprach Sverre Rabbelier <srabbelier@gmail.com> [2011.08.01.2027 +0200]:
Show 6 quoted lines
> On Mon, Aug 1, 2011 at 20:20, martin f krafft <madduck@madduck.net> wrote:
> > My intent was to add an extra commit header to select commits as
> > a way to store extra information needed to automate the management
> > of interdependent branches and patch generation à la TopGit.
> 
> Have you had a look at git notes?
Hello, and thanks for taking the time to reply to me!

Yes, I have considered git-notes. The issue I have with git-notes is that it requires every contributor to set up refspecs for fetch and push, or else the notes will not be exchanged/shared.

I realise this is a minor concern to most of you, or maybe even a feature (part of the beauty of Git is, after all, that it works without requiring everyone to have the same local setup), but in our use-case (distro packaging), it's a relatively large burden to new contributors and passerby's (sp?).

Also, git-notes are mutable (at least from the UI perspectiv) and I strive to encode information immutably.

Therefore I am looking for a means to encode this (necessary) information as part of the main DAG (i.e. not polluting the worktree).

I hope this makes sense.
-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"first get your facts; then you can distort them at your leisure."
                                                       -- mark twain
 
spamtraps: madduck.bogus@madduck.net
Previous: Sverre RabbelierNext: Clemens Buchacher
Message 3 of 23 in “Storing additional information in commit headers”
  1. martin f krafftAug 1, 2011
  2. Sverre RabbelierAug 1, 2011
  3. martin f krafftAug 1, 2011
  4. Clemens BuchacherAug 1, 2011
  5. martin f krafftAug 1, 2011
  6. martin f krafftAug 1, 2011
  7. Martin LanghoffAug 1, 2011
  8. martin f krafftAug 1, 2011
  9. Jeff KingAug 1, 2011
  10. martin f krafftAug 1, 2011
  11. Jeff KingAug 2, 2011
  12. martin f krafftAug 2, 2011
  13. working prototype of orphan parent commits as datastores (was: Storing additional information in commit headers)martin f krafft, Aug 2, 2011
  14. Jeff KingAug 2, 2011
  15. martin f krafftAug 2, 2011
  16. martin f krafftAug 2, 2011
  17. Jeff KingAug 2, 2011
  18. martin f krafftAug 2, 2011
  19. per-ref data storage (was: Storing additional information in commit headers)martin f krafft, Aug 2, 2011
  20. martin f krafftAug 2, 2011
  21. Jeff KingAug 4, 2011
  22. Jeff KingAug 4, 2011
  23. Michael HaggertyAug 2, 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.