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

Re: fsck --full is Ok, but clones are not, "missing commits"?!

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Apr 16, 2008, 17:15 UTC
Message-ID
<20080416171547.GE3133@dpotapov.dyndns.org>
In-Reply-To
<a537dd660804160804t252d2900j33e30a01dc58979c@mail.gmail.com>
On Wed, Apr 16, 2008 at 05:04:56PM +0200, Brian Foster wrote:
Show 5 quoted lines
> 
>  in the later case, the  info/grafts  still existed at the end,
>  and `fsck --full' was happy.  (I suppose this isn't surprising
>  since the filter-branch was not happy.)   moving  info/grafts
>  out of the way caused the same complaints from `fsck --full'.

Do not remove info/grafts. Just clone this repository after filter-branch and then the _newly_ cloned repository should be fine.

Dmitry
Previous: Brandon CaseyNext: Brian Foster
Message 4 of 9 in “Re: fsck --full is Ok, but clones are not, "missing commits"?!”
  1. Brian FosterApr 16, 2008
  2. Johannes SixtApr 16, 2008
  3. Brandon CaseyApr 16, 2008
  4. Dmitry PotapovApr 16, 2008
  5. Brian FosterApr 17, 2008
  6. Brandon CaseyApr 17, 2008
  7. Brian FosterApr 18, 2008
  8. Johannes SixtApr 18, 2008
  9. Brian FosterApr 18, 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.