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, 20:51 UTC
Message-ID
<20110801205143.GA15401@fishbowl.rw.madduck.net>
In-Reply-To
<CACPiFCLPgsC+9cX7r33oCQ2AnuRXMTqOAE5RZLS7hXdHc6B-9Q@mail.gmail.com>
also sprach Martin Langhoff <martin.langhoff@gmail.com> [2011.08.01.2133 +0200]:
> What data are you trying to include? Some time ago, I had similar
> ideas to yours for a while... and it ended up being that all I needed
> was to put the additional data /in a file/ and commit that file.
Hi, thanks for taking the time to reply to me!

I am trying to store the top-base of a TopGit branch, which is the merge of all a branch's dependencies.

TopGit uses refs for that, but a ref can only ever point at one such merge, and so it's hard-to-impossible to reconstruct a branch dependency in the past.

TopGit does use files in the worktree too. I would love to get rid of this as well, since a file like .topmsg (which differs between all branches, even related ones), requires to always remember to use the 'ours' merge driver, which requires setup, which makes it harder to use.

> If you are using a wrapper program,

I am trying to stay as close as possible to plain Git. All of this could easily be done by a wrapper, but a wrapper always makes too many assumptions to become a viable standard for Debian packaging.

> it's valid/sane, in the preparations to commit, perhaps ensuring
> that a pre-commit-hook script is in place and executable.

Again, that requires setup, which increases the barrier of entry to passerby's and new contributors.

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"verbing weirds language."
                                                           -- calvin
 
spamtraps: madduck.bogus@madduck.net
Previous: Martin LanghoffNext: Jeff King
Message 8 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.