git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Dmitry Potapov <dpotapov@gmail.com>
To: Brian Foster <brian.foster@innova-card.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>, git@vger.kernel.org
Subject: Re: fsck --full is Ok, but clones are not, "missing commits"?!
Date: Wed, 16 Apr 2008 21:15:47 +0400	[thread overview]
Message-ID: <20080416171547.GE3133@dpotapov.dyndns.org> (raw)
In-Reply-To: <a537dd660804160804t252d2900j33e30a01dc58979c@mail.gmail.com>

On Wed, Apr 16, 2008 at 05:04:56PM +0200, Brian Foster wrote:
> 
>  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

  parent reply	other threads:[~2008-04-16 17:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804161626.44174.brian.foster@innova-card.com>
2008-04-16 15:04 ` fsck --full is Ok, but clones are not, "missing commits"?! Brian Foster
2008-04-16 15:22   ` Johannes Sixt
2008-04-16 16:11     ` Brandon Casey
     [not found]     ` <200804171643.15504.brian.foster@innova-card.com>
2008-04-17 14:53       ` Brian Foster
2008-04-17 15:41         ` Brandon Casey
     [not found]           ` <200804180943.20933.brian.foster@innova-card.com>
2008-04-18  8:41             ` Brian Foster
2008-04-18  8:55               ` Johannes Sixt
     [not found]                 ` <200804181114.47067.brian.foster@innova-card.com>
2008-04-18  9:29                   ` Brian Foster
2008-04-16 17:15   ` Dmitry Potapov [this message]
     [not found] <20080506115224.79802c7c@zebulon.innova-card.com>
2008-05-06 12:17 ` Johannes Sixt
     [not found] <200804171756.39911.brian.foster@innova-card.com>
2008-04-17 18:44 ` Brian Foster
     [not found] <200804161334.17748.brian.foster@innova-card.com>
2008-04-16 11:48 ` Re: " Brian Foster
2008-04-16 13:22   ` Johannes Sixt
2008-04-16 14:25     ` Dmitry Potapov
2008-04-16 14:56       ` Johannes Sixt
2008-04-16 16:17         ` Dmitry Potapov
2008-04-16 16:47           ` Jakub Narebski
2008-04-17  6:18           ` Johannes Sixt
     [not found] <20080416062925.8028e952@zebulon.innova-card.com>
2008-04-16  6:37 ` Brian Foster
2008-04-16  9:14   ` David Kastrup
2008-05-05  4:25   ` Bryan Donlan
     [not found]     ` <200805051608.55200.brian.foster@innova-card.com>
2008-05-05 14:44       ` Brian Foster
2008-05-05 15:12         ` Johannes Sixt
     [not found]           ` <200805061231.30135.brian.foster@innova-card.com>
2008-05-06 10:58             ` Brian Foster
2008-05-06 11:12               ` Johannes Sixt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080416171547.GE3133@dpotapov.dyndns.org \
    --to=dpotapov@gmail.com \
    --cc=brian.foster@innova-card.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).