From: Matt Wozniski <godlygeek@gmail.com>
To: git@vger.kernel.org
Subject: "clean" filter breaks git-svn
Date: Thu, 29 Jul 2010 23:55:37 -0400 [thread overview]
Message-ID: <AANLkTikp6PgHyj2ujbuD52884ny88hMyxR1CpsbNAVCJ@mail.gmail.com> (raw)
I'm playing around with smudge and clean filters, and I've discovered
that they seem to completely break git-svn. When trying to fetch
commits A and B from the SVN repos, it will fetch A, and then clean(A)
is committed to my repository. Then when it tries to fetch B, it is
horribly confused - it complains of a checksum mismatch, since the
md5sums of the files in A in the SVN repos don't match up with the
md5sums of the files in the clean(A) commit in git land. Is this a
known problem? And, are there any work arounds other than just not
using filters when using git-svn? Could git-svn be made to accept the
md5sum of *either* A or clean(A) instead?
Thanks!
~Matt
PS - Please CC me if possible; I'm not subscribed
next reply other threads:[~2010-07-30 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 3:55 Matt Wozniski [this message]
2010-07-30 20:31 ` "clean" filter breaks git-svn Jonathan Nieder
2010-07-30 21:21 ` Junio C Hamano
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=AANLkTikp6PgHyj2ujbuD52884ny88hMyxR1CpsbNAVCJ@mail.gmail.com \
--to=godlygeek@gmail.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).