git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kees-Jan Dijkzeul" <k.j.dijkzeul@gmail.com>
To: git@vger.kernel.org
Subject: Fwd: git-svn dcommit fail
Date: Thu, 5 Jul 2007 10:28:57 +0200	[thread overview]
Message-ID: <fa0b6e200707050128h6bc3caa4rd661c64128ac7367@mail.gmail.com> (raw)
In-Reply-To: <fa0b6e200707050126m17a23de6uad4909533306eb06@mail.gmail.com>

This one should have gone to the list. Sorry, Steven, for mailing privately.

---------- Forwarded message ----------
From: Kees-Jan Dijkzeul <k.j.dijkzeul@gmail.com>
Date: Jul 5, 2007 10:26 AM
Subject: Re: git-svn dcommit fail
To: Steven Grimm <koreth@midwinter.com>


On 7/5/07, Steven Grimm <koreth@midwinter.com> wrote:
> git-svn doesn't support nonlinear history in any of the official
> releases, though there will be some support in the next release (you can
> try it out by grabbing the latest version from git.git's master branch).

I just fetched the master branch. For me it is at commit
d44c782bbd6b0e806e056f9e8ff8cd8e426e67a3.
At this point, git-svn is identical to the one in 1.5.2.3.

I've attempted to use git to merge two subversion branches, but when
dcommitting attempts to commit the correct delta to the wrong branch,
and subsequently claims that "Your file or directory is probably out
of date" (which, in a weird way, makes sense).

I'd be happy to test this support for nonlinear history, but so far,
I've been unable to locate the correct commit.

Groetjes,

Kees-Jan

  parent reply	other threads:[~2007-07-05  8:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  9:56 git-svn dcommit fail Dongsheng Song
2007-07-05  7:11 ` Steven Grimm
     [not found]   ` <fa0b6e200707050126m17a23de6uad4909533306eb06@mail.gmail.com>
2007-07-05  8:28     ` Kees-Jan Dijkzeul [this message]
2007-07-05  8:47       ` Fwd: " Junio C Hamano
2007-07-05 11:06         ` Kees-Jan Dijkzeul
2007-07-05 16:18           ` Steven Grimm

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=fa0b6e200707050128h6bc3caa4rd661c64128ac7367@mail.gmail.com \
    --to=k.j.dijkzeul@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).