git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fred <fred@akafred.com>
To: git@vger.kernel.org
Subject: Re: git+svn - repo upgrade from 1.6.6.4 to 1.7.1 fails
Date: Mon, 31 May 2010 14:27:06 +0200	[thread overview]
Message-ID: <AANLkTilTx0Eh5WTxucWRVcvFcFUQoYfauU953pXx-P5N@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikYYjl6Gv8SRMvtmzW1pyzkyu_mwLyEGHdWuH00@mail.gmail.com>

On 31 May 2010 13:09, Fred <fred@akafred.com> wrote:
> Hi, I have a project with two remotes - one git and one svn. One
> branch is only used for "git svn rebase", and then I cherrypick or
> merge from it into my master branch. Most work is done in the master
> branch (or other topic branches only available in git)
>
> The repo was created under git 1.6.6.4. After updating git a while
> back (to 1.7.1) it was time to merge inn a few things from svn - so i
> switched to my "subversion" branch and did a
>
> $ git svn rebase
>
> Migrating from a git-svn v1 layout...
> Data from a previous version of git-svn exists, but
> .git/svn
> (required for this version (1.7.1) of git-svn) does not exist.
> Done migrating from a git-svn v1 layout
> Unable to determine upstream SVN information from working tree history
> ---
> I read this as: "I see your repo has some svn stuff and that it is
> backlevel. I'll fix it for you. Oh shit, now I can't determine what
> svn revision you are on."
>
> Any ideas on how to resolve this? We're a dozen developers relying on
> this so it would be nice find a way with minimal impact to the
> users...
>
> For now I'll do the rebasing in a back-level git client...
>
> - Fred
>

Additional info:

$ git log --grep=^git-svn-id --first-parent

returns mulitple commits - the first one here:

commit e2f9e115f07fa1fb0932f893c6f94173f9dc4515
Author: geir <geir@f9caaf5b-9695-4c42-8d37-d0d3d7799616>
Date:   Mon Apr 26 12:37:09 2010 +0000

    Modofied search for ED01119000 from web. Handles the case that the
user enters the birth date as a complete ssn or as 8 digits in

    git-svn-id: svn://svnserver/Decision/decisionmaker/trunk@45839
f9caaf5b-9695-4c42-8d37-d0d3d7799616

----

And here is the config-file - only changed the github username to xxx

[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
	ignorecase = true
[svn-remote "svn"]
	url = svn://svnserver/
	fetch = Decision/decisionmaker/trunk:refs/remotes/trunk
	branches = Decision/decisionmaker/branches/*:refs/remotes/*
	tags = Decision/decisionmaker/tags/*:refs/remotes/tags/*
[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:xxx/decisionmaker.git
[branch "master"]
	remote = origin
	merge = refs/heads/master
[branch "subversion"]
        remote = origin
        merge = refs/heads/subversion

---

      reply	other threads:[~2010-05-31 12:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTin-k5zIDZysiLbTusqDwqxGWDxxAOPljLuRlIMD@mail.gmail.com>
2010-05-31 11:09 ` Fwd: git+svn - repo upgrade from 1.6.6.4 to 1.7.1 fails Fred
2010-05-31 12:27   ` Fred [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTilTx0Eh5WTxucWRVcvFcFUQoYfauU953pXx-P5N@mail.gmail.com \
    --to=fred@akafred.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).