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 19:47:22 +0530 [thread overview]
Message-ID: <CAH3Anroub3a1+Nsj5C-ecTqaX9riUG7T27bHZYJOHiPJbeVCTQ@mail.gmail.com> (raw)
In-Reply-To: <87havs6v9s.fsf@thomas.inf.ethz.ch>
On Mon, May 7, 2012 at 5:46 PM, Thomas Rast <trast@student.ethz.ch> wrote:
> Jon Seymour <jon.seymour@gmail.com> writes:
> Oh, now I understand. Yes, specifying a revision C there acts mostly as
> if you said
>
> git checkout C^0
> git svn dcommit
> git checkout -
>
Ok, I see my mistake - I had created the branch in SVN (using external
means, since git svn branch doesn't use an HTTP proxy), had failed to
fetch and then rebase my work onto remotes/<branch> and do the commit
from there. If I had done that, it would have worked as expected.
Thanks for your help.
prev parent reply other threads:[~2012-05-07 14:17 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
2012-05-07 12:16 ` Thomas Rast
2012-05-07 14:17 ` Jon Seymour [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=CAH3Anroub3a1+Nsj5C-ecTqaX9riUG7T27bHZYJOHiPJbeVCTQ@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).