From: Patrick Doyle <wpdster@gmail.com>
To: Reynald Borer <reynald.borer@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn checksum mismatch
Date: Wed, 8 Dec 2010 10:36:04 -0500 [thread overview]
Message-ID: <AANLkTinZocHeu3ho6U9oL=Q608NBJaUf-nKehppWaDYp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimVyCndGZQLUnVM9CCQmDfOHYywcfzBAL2w0gbC@mail.gmail.com>
On Wed, Dec 8, 2010 at 10:17 AM, Reynald Borer <reynald.borer@gmail.com> wrote:
> Hi again,
>
> Sorry to bother you again but I am still experiencing this problem. I
> tried with a more up to date version of Git (version 1.7.3.2), and
> this is still happening. I also tried to diagnose this issue but I am
> completely lost.
>
> I am very annoyed because this is preventing me using Git on all my
> SVN repos (2 are failing on 30...)
>
> Does anyone know how I could try to solve this issue?
Tossing out a random theory with nothing to back it up...
I don't know anything about the "well known checksum mismatch
problem", but are you trying to check out the SVN repository onto a
file system that is case insensitive, such as on a Windows or (default
setup) Mac host?
If so, the repository might have files with different spellings such
as README and Readme in the same directory, which will get clobbered
on such a host. I've run into that issue in the past in a different
context.
--wpd
next prev parent reply other threads:[~2010-12-08 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik0NBkjrPTzLp9ozMnnV+bng_u5Br1v+H4y6ed0@mail.gmail.com>
2010-12-08 15:17 ` git-svn checksum mismatch Reynald Borer
2010-12-08 15:36 ` Patrick Doyle [this message]
2010-12-08 16:13 ` Reynald Borer
2010-11-04 13:45 Reynald Borer
[not found] <fa34f1941002170821p66cf0ac7i9385b341c94993c3@mail.gmail.com>
[not found] ` <20100218005347.GA8528@dcvr.yhbt.net>
[not found] ` <fa34f1941002180652wb91c36bt8feba5c7f653701d@mail.gmail.com>
2010-02-18 14:55 ` Jason Baker
2010-02-18 23:08 ` Eric Wong
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='AANLkTinZocHeu3ho6U9oL=Q608NBJaUf-nKehppWaDYp@mail.gmail.com' \
--to=wpdster@gmail.com \
--cc=git@vger.kernel.org \
--cc=reynald.borer@gmail.com \
/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).