From: Jeff King <peff@peff.net>
To: Jose Gisbert <jose.gisbert@live.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Using git svn rebase at quarantine environment or a feasible alternative to synchronize git and svn repositories
Date: Tue, 2 Oct 2018 10:27:25 -0400 [thread overview]
Message-ID: <20181002142725.GB24375@sigill.intra.peff.net> (raw)
In-Reply-To: <VI1PR0902MB2223AB8C9A721478E82449FEE2E80@VI1PR0902MB2223.eurprd09.prod.outlook.com>
On Tue, Oct 02, 2018 at 10:28:38AM +0000, Jose Gisbert wrote:
> Moreover, assuming that solution #1 will generally work and the facts that:
>
> - I think it would be possible to us to recover from a corrupted repository
> somehow easily. Couldn't we, for instance, reset from a failed push and try
> it again?
Yes, I think that would generally allow you to recover (it just may
require some manual fiddling by the admin).
> - the chances of corrupting the svn repository, our reference here, seem small
> because git svn dcommit is the last operation in the chain and is only
> performed when everything else went ok
> - we are a small team and git is not our main CVS, so we can stop pushing to
> git while we fix the repository
>
> I'm more inclined to apply this solution. Maybe I'm being too much optimistic
> with my assumptions.
I think your analysis of the risk seems pretty accurate. I make no
promises, of course. :)
-Peff
prev parent reply other threads:[~2018-10-02 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 8:12 Using git svn rebase at quarantine environment or a feasible alternative to synchronize git and svn repositories Jose Gisbert
2018-10-01 8:55 ` Ævar Arnfjörð Bjarmason
2018-10-01 14:17 ` Jose Gisbert
2018-10-01 15:00 ` Ævar Arnfjörð Bjarmason
2018-10-02 10:29 ` Jose Gisbert
2018-10-01 14:53 ` Jeff King
2018-10-02 10:28 ` Jose Gisbert
2018-10-02 14:27 ` Jeff King [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181002142725.GB24375@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jose.gisbert@live.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).