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

Re: [ANNOUNCE] GIT 1.6.1

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Dec 26, 2008, 01:38 UTC
Message-ID
<slrngl8dc8.klo.sitaramc@sitaramc.homelinux.net>
In-Reply-To
<20081225114443.GD6115@zakalwe.fi>

["Followup-To:" header set to gmane.comp.version-control.git.] On 2008-12-25, Heikki Orsila <shdl@zakalwe.fi> wrote:

> * What would be the probability for a single bit flip to corrupt the 
> repository?
> * And what is the situation where a single bit flip can not corrupt the 
> database?

These two questions are not specific to git; whatever answers apply to sha1 also apply here. Sha1 will always be strong enough to detect any combination of random errors. As for deliberate attacks, it is considered strong enough to resist all but the most computationally intensive attacks (the kind that require a worldwide effort or maybe NSA type facilities).

> * When (which commands/functions) is error detection done?

"git fsck --full" will do it of course, but I'm not sure what other operations also start off or end up doing a check.

Previous: Heikki OrsilaNext: Nicolas Pitre
Message 13 of 15 in “[ANNOUNCE] GIT 1.6.1”
  1. Junio C HamanoDec 25, 2008
  2. Christian MICHONDec 25, 2008
  3. bill lamDec 25, 2008
  4. Junio C HamanoDec 25, 2008
  5. bill lamDec 25, 2008
  6. René ScharfeDec 25, 2008
  7. bill lamDec 25, 2008
  8. Junio C HamanoDec 25, 2008
  9. bill lamDec 26, 2008
  10. Pau Garcia i QuilesDec 25, 2008
  11. bill lamDec 26, 2008
  12. Heikki OrsilaDec 25, 2008
  13. Sitaram ChamartyDec 26, 2008
  14. Nicolas PitreDec 27, 2008
  15. [ANNOUNCE] MSYSGIT 1.6.1Steffen Prohaska, Dec 27, 2008

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.