git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Menard <nirvdrum@gmail.com>
To: Peter Oberndorfer <kumbayo84@arcor.de>
Cc: git@vger.kernel.org
Subject: Re: git svn dcommit difficulties/feature request
Date: Fri, 20 Feb 2009 07:59:44 -0500	[thread overview]
Message-ID: <7e3605160902200459x50e56c92x462d9a072eaa84d0@mail.gmail.com> (raw)
In-Reply-To: <200902191947.22622.kumbayo84@arcor.de>

We've run into the same issue with the experimental git support at the
ASF.  We dcommit to an EU mirror which lags behind the primary one for
a couple minutes.  While annoying, I don't think there's much that can
be done other than to commit and read from the master SVN server.
Otherwise, plan on getting good at "git svn dcommit; git svn rebase".
I tolerate this step because I think using git on top of SVN, even
with this lag, makes me more productive than SVN alone.

-- 
Kevin



On Thu, Feb 19, 2009 at 1:47 PM, Peter Oberndorfer <kumbayo84@arcor.de> wrote:
> Hi,
>
> With the patch i am replying to git-svn got a bit more comfortable for me but
> there is still a problem left.
>
> I fetch via svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
> and push to svn+ssh://YOUR_LOGIN@svn.kde.org/home/kde/trunk/KDE/kdelibs
>
> Pushing multiple changes at once to KDE servers with different fetch/commit
> url is not possible for me.
>
> Here is what it think what happens during a push:
> git svn dcommit pushes the first commit to svn.kde.org,
> then tries to fetch what it just pushed from anonsvn.kde.org
> (which lags behind authenticated svn by a few minutes).
>
> git svn does not see the just committed changes, gets confused
> and stops pushing the rest of the commits.
>
> My idea would be to temporarily fetch from the authenticated server, but not
> update the current head and revdb., so nothing is affected beside the push.
> But this seems quite complicated.
> Or do not care about difference between fetch/dcommit url, and just fetch from
> the dcommit url during dcommit.
>
> Anybody have a good idea if this is possible or a better way to solve this
> problem?
>
> Greetings Peter
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2009-02-20 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 18:30 [PATCH] git-svn: try to read the dcommit url from the config file Peter Oberndorfer
2009-02-19 18:47 ` git svn dcommit difficulties/feature request Peter Oberndorfer
2009-02-20 12:59   ` Kevin Menard [this message]
2009-02-21 12:12   ` Eric Wong
2009-02-21 12:08 ` [PATCH] git-svn: try to read the dcommit url from the config file Eric Wong
2009-02-22 21:41   ` Peter Oberndorfer
2009-02-23  2:05     ` Eric Wong
2009-02-23 11:02       ` [PATCH] git-svn: read the dcommit url from the config file on a per remote basis Peter Oberndorfer
2009-02-23 22:45         ` Eric Wong
2009-02-23 23:06           ` 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=7e3605160902200459x50e56c92x462d9a072eaa84d0@mail.gmail.com \
    --to=nirvdrum@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kumbayo84@arcor.de \
    /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).