public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: phantomjinx <p.g.richardson@phantomjinx•co.uk>
To: git@vger•kernel.org
Subject: git svn dcommit --commit-url
Date: Thu, 19 Apr 2012 11:09:00 +0100	[thread overview]
Message-ID: <4F8FE43C.2010004@phantomjinx.co.uk> (raw)

Greetings,

I have git-svn cloned a repo from its anonymous http url using git2svn.

This worked fine but in order to commit back, I would need to use the
committer-only https url.

I googled and found the 'commiturl' config option, as well as the
--commit-url switch on dcommit. Thank goodness for these!!

I edit my git config to look like this

[svn-remote "svn"]
        url = http://anonymous.blah.com/myproject
        fetch = trunk:refs/remotes/svn/trunk
        branches = branches/*:refs/remotes/svn/*
        tags = tags/*:refs/remotes/svn/tags/*
        commiturl = https://svn.blah.com/myproject

and prepare to dcommit my commits from SomeBranch

git co SomeBranch
git svn dcommit

or

git svn dcommit --commit-url https://svn.blah.com/myproject

which results in the following:

Committing to https://svn.blah.com/myproject ...
        M       plugins/somefile.txt
Incomplete data: Delta source ended unexpectedly at
/usr/libexec/git-core/git-svn line 848

However, the following syntax works correctly:

git svn dcommit --commit-url
https://svn.blah.com/myproject/branches/SomeBranch

I cannot add the 'branches/SomeBranch' to my config and I thought
git-svn would have deduced them from the branch I am currently on? Is
this expected behaviour, a bug in my repo or a bug in git-svn's code?

I can commit so it is not a problem but I would appreciate any
information that anyone has on this.

Not subscribed.

Many Thanks

Paul

-- 
Paul Richardson

                 reply	other threads:[~2012-04-19 11:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F8FE43C.2010004@phantomjinx.co.uk \
    --to=p.g.richardson@phantomjinx$(echo .)co.uk \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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