git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: git@vger.kernel.org
Subject: git pull problem
Date: Tue, 14 Jun 2005 23:19:03 -0500	[thread overview]
Message-ID: <200506142319.03537.dtor_core@ameritech.net> (raw)

Hi,

I was trying to do:

	git-pull-script rsync://www.kernel.org/pub/scm/git/git.git

And got the following response:

...
fe/ca5e9b7c86b1aaa5903f1c2ca3afde09531c7b

sent 3804 bytes  received 468743 bytes  85917.64 bytes/sec
total size is 4930906  speedup is 10.43
Updating from 98a96b00b88ee35866cd0b1e94697db76bd5ddf9 to ce30a4b68ac220a2322dfe2a182194910143fafd.
fatal: git diff header lacks filename information (line 846)

Last time I did a pull and rebuild was on June 9th:

[dtor@anvil git]$ ls -la ~/bin/git-pull-script
-rwxr-xr-x  1 dtor dtor 425 Jun  9 01:08 /home/dtor/bin/git-pull-script

Just FYI.

-- 
Dmitry

                 reply	other threads:[~2005-06-15  4:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200506142319.03537.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --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).