From: Manuel Corpas <mc@manuelcorpas.com>
To: git@vger.kernel.org
Subject: Checksum mismatch problem
Date: Wed, 14 Apr 2010 14:31:16 +0100 [thread overview]
Message-ID: <g2y67740bda1004140631h292e222dmefa68b91051d59cd@mail.gmail.com> (raw)
Hi there
has anyone come across this problem? Any ideas?
$ git svn rebase
Checksum mismatch:
branches/prerelease_4.2/data/templates/custom_print_read_ajax.tt2
87713960a22f08430930baa8826fbc5e17abc722
expected: 3d4d50882e2ca57f22518201a2cf26f2
got: 7985ae0b3e37d915347cfb1a82d4d48c
I've tried to delete .git/svn/ to no avail.
I have even created a fresh check out following the instructions on
the git book on git svn.
http://progit.org/book/ch8-1.html
git svn clone file:///tmp/test-svn -T trunk -b branches -t tags
Still couldn't fix the problem :-\
M
Manuel Corpas, PhD
The Wellcome Trust Sanger Institute
Wellcome Trust Genome Campus
Hinxton, Cambridge CB10 1HH (UK)
Tel: +44.122349.2372
Web: http://manuelcorpas.com/about/
reply other threads:[~2010-04-14 13:31 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=g2y67740bda1004140631h292e222dmefa68b91051d59cd@mail.gmail.com \
--to=mc@manuelcorpas.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).