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 01:12:12 +0200 [thread overview]
Message-ID: <20050420231212.GN19112@pasky.ji.cz> (raw)
In-Reply-To: <200504201706.09656.elenstev@mesatop.com>
Dear diary, on Thu, Apr 21, 2005 at 01:06:09AM CEST, I got a letter
where Steven Cole <elenstev@mesatop.com> told me that...
> After getting the latest tarball, and make, make install:
>
> Tree change: 55f9d5042603fff4ddfaf4e5f004d2995286d6d3:a46844fcb6afef1f7a2d93f391c82f08ea322221
> *100755->100755 blob a78cf8ccab98861ef7aecb4cb5a79e47d3a84b67->74b4083d67eda87d88a6f92c6c66877bba8bda8a gitcancel.sh
> Tracked branch, applying changes...
> Fast-forwarding 55f9d5042603fff4ddfaf4e5f004d2995286d6d3 -> a46844fcb6afef1f7a2d93f391c82f08ea322221
> on top of 55f9d5042603fff4ddfaf4e5f004d2995286d6d3...
> patch: **** Only garbage was found in the patch input.
>
> This may be a harmless message, but I thought I'd bring it to your attention.
This _is_ weird. What does
$ git diff -r 55f9d5042603fff4ddfaf4e5f004d2995286d6d3:a46844fcb6afef1f7a2d93f391c82f08ea32222
tell you? What if you feed it to patch -p1? What if you feed it to git
apply?
Thanks,
--
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-20 23:08 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 [this message]
2005-04-20 23:15 ` Steven Cole
2005-04-21 0:20 ` Steven Cole
2005-04-21 7:11 ` Petr Baudis
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=20050420231212.GN19112@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).