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

Re: [PATCH 1/3] setup: drop return value from `read_repository_format()`

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Dec 20, 2018, 00:17 UTC
Message-ID
<20181220001752.GA35965@genre.crustytoothpaste.net>
In-Reply-To
<20181219152735.GA14802@sigill.intra.peff.net>
On Wed, Dec 19, 2018 at 10:27:35AM -0500, Jeff King wrote:
Show 5 quoted lines
> I dunno. This is one of those dark corners of the code where we appear
> to do the wrong thing, but nobody seems to have noticed or cared much,
> and changing it runs the risk of breaking some obscure cases. I'm not
> sure if we should bite the bullet and try to address that, or just back
> away slowly and pretend we never looked at it. ;)

I will point out that with the SHA-256 work, reading the config file becomes essential for SHA-256 repositories, because we need to know the object format. Removing the config file leads to things blowing up in a bad way (what specific bad way I don't remember).

That may influence the direction we want to take in this work, or not.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: Martin ÅgrenNext: Jeff King
Message 5 of 40 in “setup: add `clear_repository_format()`”
  1. 0/3 setup: add `clear_repository_format()`Martin Ågren, Dec 18, 2018
  2. 1/3 setup: drop return value from `read_repository_format()`Martin Ågren, Dec 18, 2018
  3. Jeff KingDec 19, 2018
  4. Martin ÅgrenDec 19, 2018
  5. brian m. carlsonDec 20, 2018
  6. Jeff KingDec 20, 2018
  7. brian m. carlsonDec 20, 2018
  8. Jeff KingDec 20, 2018
  9. 2/3 setup: do not use invalid `repository_format`Martin Ågren, Dec 18, 2018
  10. brian m. carlsonDec 19, 2018
  11. Martin ÅgrenDec 19, 2018
  12. Jeff KingDec 19, 2018
  13. Martin ÅgrenDec 19, 2018
  14. Jeff KingDec 19, 2018
  15. brian m. carlsonDec 20, 2018
  16. 3/3 setup: add `clear_repository_format()`Martin Ågren, Dec 18, 2018
  17. Jeff KingDec 19, 2018
  18. Martin ÅgrenDec 19, 2018
  19. 0/3 setup: add `clear_repository_format()`Martin Ågren, Jan 14, 2019
  20. 1/3 setup: free old value before setting `work_tree`Martin Ågren, Jan 14, 2019
  21. 2/3 setup: do not use invalid `repository_format`Martin Ågren, Jan 14, 2019
  22. Jeff KingJan 15, 2019
  23. Martin ÅgrenJan 17, 2019
  24. Jeff KingJan 22, 2019
  25. Martin ÅgrenJan 22, 2019
  26. 0/2 setup: fix memory leaks with `struct repository_format`Martin Ågren, Jan 22, 2019
  27. 1/2 setup: free old value before setting `work_tree`Martin Ågren, Jan 22, 2019
  28. 2/2 setup: fix memory leaks with `struct repository_format`Martin Ågren, Jan 22, 2019
  29. Jeff KingJan 23, 2019
  30. brian m. carlsonJan 24, 2019
  31. Martin ÅgrenJan 25, 2019
  32. Martin ÅgrenJan 25, 2019
  33. Jeff KingJan 25, 2019
  34. Martin ÅgrenFeb 25, 2019
  35. Jeff KingFeb 26, 2019
  36. 0/2 setup: fix memory leaks with `struct repository_format`Martin Ågren, Feb 28, 2019
  37. 1/2 setup: free old value before setting `work_tree`Martin Ågren, Feb 28, 2019
  38. 2/2 setup: fix memory leaks with `struct repository_format`Martin Ågren, Feb 28, 2019
  39. Jeff KingMar 6, 2019
  40. 3/3 setup: add `clear_repository_format()`Martin Ågren, Jan 14, 2019

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.