From: Jon Seymour <jon.seymour@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git svn dcommit <branch> committed to trunk anyway
Date: Mon, 7 May 2012 17:08:56 +0530 [thread overview]
Message-ID: <CAH3Anrq5SGZZsTpKd1MFBRVD8xzsUvckt6d-BxtTYYce--F1+g@mail.gmail.com> (raw)
In-Reply-To: <87txzsba0o.fsf@thomas.inf.ethz.ch>
On Mon, May 7, 2012 at 3:14 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> Jon Seymour <jon.seymour@gmail.com> writes:
>
>> I expected git svn dcommit <branch> to push commits into the svn
>> branch called <branch> (a repo relative URL of
>> /branches/foobar1/foobar2/<branch>)
>>
>> However, it decided to push into trunk instead, which was not the
>> intended effect.
>>
>> What have I misunderstood about how git svn dcommit is supposed to work?
>
> Did the commits you dcommitted have any git-svn-id lines? It dcommits
> (or at least it's supposed to :-) in the directory listed in the
> git-svn-id line found by (roughly)
>
> git log --first-parent -1 --grep=^git-svn-id:
>
None of the commits that dcommit committed to svn had such lines, but
the immediately preceding commit did, and that commit referred to the
trunk URL, rather than the branch URL.
I guess I am confused by this guidance in git-svn(1) in the section on dcommit:
"An optional revision or branch argument may be specified, and
causes git svn to do all work on that revision/branch instead of
HEAD":
I had assumed that dcommit would respect the optional (SVN branch)
argument that I had specified, but it seems that this is not the case.
What do the words in the man page actually mean, if they don't mean
what I thought they meant. Do the words "optional revision or branch"
actually refer to the git commit/branch rather than the SVN
revision/branch?
Regards,
jlon.
> --
> Thomas Rast
> trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-07 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 13:00 git svn dcommit <branch> committed to trunk anyway Jon Seymour
2012-05-07 9:44 ` Thomas Rast
2012-05-07 11:38 ` Jon Seymour [this message]
2012-05-07 12:16 ` Thomas Rast
2012-05-07 14:17 ` Jon Seymour
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=CAH3Anrq5SGZZsTpKd1MFBRVD8xzsUvckt6d-BxtTYYce--F1+g@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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).