git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Jon Seymour <jon.seymour@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: git svn dcommit <branch> committed to trunk anyway
Date: Mon, 7 May 2012 14:16:47 +0200	[thread overview]
Message-ID: <87havs6v9s.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAH3Anrq5SGZZsTpKd1MFBRVD8xzsUvckt6d-BxtTYYce--F1+g@mail.gmail.com> (Jon Seymour's message of "Mon, 7 May 2012 17:08:56 +0530")

Jon Seymour <jon.seymour@gmail.com> writes:

> 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?

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 -

(IIRC, I haven't used it in a while).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-05-07 12: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 [this message]
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=87havs6v9s.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=git@vger.kernel.org \
    --cc=jon.seymour@gmail.com \
    /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).