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

Re: What's cooking in git.git (Dec 2015, #01; Tue, 1)

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 3, 2015, 03:02 UTC
Message-ID
<20151203030220.GB25412@vauxhall.crustytoothpaste.net>
In-Reply-To
<1449102580.14908.2.camel@twopensource.com>
On Wed, Dec 02, 2015 at 07:29:40PM -0500, David Turner wrote:
Show 8 quoted lines
> From a selfish perspective, I, would prefer for object-ids to not happen
> quite yet for the refs code.  I have already prepared (but not yet sent)
> a new version of the refs backend vtable (and lmdb) code on top of
> refs-backend-pre-vtable, and it'll be a hassle to reroll it on top of
> new object-id stuff.
> 
> I guess I'll go ahead and send mine now, and we can later make a
> decision about how to deal with the object-id stuff.

As Jeff pointed out, the patches to refs.c were mostly dropped, as the code that they modified had been removed. The likelihood of conflict is therefore low unless you're using struct object a lot.

My preference is that new code use object_id where possible, because otherwise I'm going to have to go through it later and fix it up. Keeping in mind that the refs code is likely to undergo a lot of changes, I'll try to keep away from it for now, but it will need to be converted at some point.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: David Turner
Message 12 of 12 in “What's cooking in git.git (Dec 2015, #01; Tue, 1)”
  1. Jeff KingDec 2, 2015
  2. Junio C HamanoDec 2, 2015
  3. Jeff KingDec 2, 2015
  4. Junio C HamanoDec 2, 2015
  5. Jeff KingDec 3, 2015
  6. Junio C HamanoDec 3, 2015
  7. Junio C HamanoDec 3, 2015
  8. Patrick SteinhardtDec 7, 2015
  9. Junio C HamanoDec 7, 2015
  10. Patrick SteinhardtDec 8, 2015
  11. David TurnerDec 3, 2015
  12. brian m. carlsonDec 3, 2015

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.