From: Deskin Miller <deskinm@umich.edu>
To: git@vger.kernel.org
Subject: [ANNOUNCE] git-svn-bugfix script (Re: [PATCH] git-svn: Make following parents atomic)
Date: Sun, 7 Dec 2008 11:10:39 -0500 [thread overview]
Message-ID: <20081207161039.GA21319@euler> (raw)
In-Reply-To: <1228665970-21204-1-git-send-email-deskinm@umich.edu>
git-svn has some bugs where it won't create identical commits in
different git-svn copies of the same svn history, despite all relevant
configuration being identical; oftentimes, the copies will diverge from
each other at some point. My theory for a long time was that
interrupting git svn fetch could cause this, and it turns out I was
right in one case, but since it's not something I could easily interrupt
my normal workflow with to do forensics when it occurred, I ended up
writing a script to repeatedly fetch from a certain svn repository, and
compare refs to a supposedly pristine fetch until the refs diverged or
one fetched all the svn history; then, rinse and repeat the process from
the beginning. It's available at
git://git.deskinm.fdns.net/git-svn-bugfix.git
Using this script, r3924 of SVN's svn repository flagged one bug
repeatedly, for which I've posted a patch. I'm posting the repo because
there are other places where history diverges that I've not had a chance
to debug yet, so others should feel free to use the script to find and
fix them. If anyone feels inclined, I'll gladly take patches to the
script, but I don't really care to handle data or bug reports you
generate with it (at least not at this point); I can generate plenty of
data myself.
Deskin Miller
next prev parent reply other threads:[~2008-12-07 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 16:06 [PATCH] git-svn: Make following parents atomic Deskin Miller
2008-12-07 16:10 ` Deskin Miller [this message]
2008-12-07 22:24 ` Deskin Miller
2008-12-08 6:20 ` [PATCH v2] " Deskin Miller
2008-12-08 8:33 ` Junio C Hamano
2008-12-08 13:31 ` [PATCH v3] " Deskin Miller
2008-12-08 23:35 ` Eric Wong
2008-12-16 13:22 ` Thomas Jarosch
2008-12-22 8:41 ` Thomas Jarosch
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=20081207161039.GA21319@euler \
--to=deskinm@umich.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.