From: Pascal Obry <pascal@obry.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Avery Pennarun <apenwarr@gmail.com>,
adambrewster@gmail.com, git list <git@vger.kernel.org>
Subject: Re: git-svn problem with v1.6.5
Date: Thu, 12 Nov 2009 10:03:06 +0100 [thread overview]
Message-ID: <a2633edd0911120103y688a2b2ah2c33c47de195ee81@mail.gmail.com> (raw)
In-Reply-To: <a2633edd0911120011u34d69100p1565ab5bf96a7709@mail.gmail.com>
Eric,
> Will review the procedure for filtering branches :(
A quick review does not show something obviously wrong on my side.
The commit on the rewritten repo has a different sha-1 which is
expected. So to me it seems that after a filter-branch on a git-svn
repo it is mandatory to recreate all .rev_map*? Is that right? Is so,
this is the missing piece in the procedure on my side.
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2009-11-12 9:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 22:23 git-svn problem with v1.6.5 Pascal Obry
2009-11-10 22:28 ` Avery Pennarun
2009-11-11 10:28 ` Pascal Obry
2009-11-11 19:41 ` Avery Pennarun
2009-11-11 19:58 ` Pascal Obry
2009-11-11 20:22 ` Eric Wong
2009-11-11 20:34 ` Eric Wong
2009-11-11 21:55 ` Pascal Obry
2009-11-11 22:44 ` Eric Wong
2009-11-12 6:39 ` Pascal Obry
2009-11-12 7:11 ` Eric Wong
2009-11-12 8:11 ` Pascal Obry
2009-11-12 9:03 ` Pascal Obry [this message]
2009-11-12 9:35 ` Eric Wong
2009-11-12 10:00 ` Pascal Obry
2009-11-11 4:02 ` Sam Vilain
2009-11-11 8:11 ` Pascal Obry
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=a2633edd0911120103y688a2b2ah2c33c47de195ee81@mail.gmail.com \
--to=pascal@obry.net \
--cc=adambrewster@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).