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

Re: per-ref data storage

From
MKmartin f krafft <madduck@madduck.net>
Date
Aug 2, 2011, 21:12 UTC
Message-ID
<20110802211241.GA29029@fishbowl.rw.madduck.net>
In-Reply-To
<20110802192727.GB20239@fishbowl.rw.madduck.net>
also sprach martin f krafft <madduck@madduck.net> [2011.08.02.2127 +0200]:
Show 6 quoted lines
> refs/heads/master is a file, containing its payload in the first
> line by format definition, right?
> 
> I mean: the storage is right there, isn't it?
> 
> Of course this opens a whole new can of worms: merging per-ref data.

origin/master can contain a different set of per-ref data than master, and the consolidation would need to happen during the normal merge.

But unless there's always a new commit associated with a change of those data, git-push will happily overwrite those data on the remote.

… unless the remote refuses to accept a ref update if the data have changed. Conceivably that's could lead into a control path similar to what happens on a non-fast-forward push — unless receive.nonFastForwards is on.

What then?
-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
seminars, n.:
  from "semi" and "arse", hence, any half-assed discussion.
 
spamtraps: madduck.bogus@madduck.net
Previous: martin f krafftNext: Jeff King
Message 20 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.