From: Petr Baudis <pasky@ucw.cz>
To: Steven Cole <elenstev@mesatop.com>
Cc: git@vger.kernel.org
Subject: Re: Possible problem with git-pasky-0.6.2 (patch: **** Only garbage was found in the patch input.)I
Date: Thu, 21 Apr 2005 09:11:05 +0200 [thread overview]
Message-ID: <20050421071104.GC31910@pasky.ji.cz> (raw)
In-Reply-To: <200504201820.27497.elenstev@mesatop.com>
Dear diary, on Thu, Apr 21, 2005 at 02:20:27AM CEST, I got a letter
where Steven Cole <elenstev@mesatop.com> told me that...
> Actually, I meant "patch -p1 <stuff_from_above".
So, how did it end up?
Actually, never mind. I forgot that I bring the local changes forward as
patches instead. So this is Harmless (tm). It means the patch containing
your local changes has just that kind of git diff output containing
filename: hash. I will probably just chain grep -v '^[^+-@ ]' in front
of patch. (Someone starting his filename with a space _deserves_ the
trouble. ;-)
> But before doing that, I did a fsck-cache as follows, with these results.
> This seems damaged.
>
> [steven@spc git-pasky-0.6.2]$ fsck-cache --unreachable $(cat .git/HEAD)
You can't do just this. In Cogito repository, you may have multiple
branches, each with different HEAD of course. So you need to
fsck-cache --unreachable $(cat .git/heads/*)
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-04-21 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 23:06 Possible problem with git-pasky-0.6.2 (patch: **** Only garbage was found in the patch input.)I Steven Cole
2005-04-20 23:12 ` Petr Baudis
2005-04-20 23:15 ` Steven Cole
2005-04-21 0:20 ` Steven Cole
2005-04-21 7:11 ` Petr Baudis [this message]
2005-04-21 10:23 ` Steven Cole
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050421071104.GC31910@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=elenstev@mesatop.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).