git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: nolan.ring@emc.com
Cc: git@vger.kernel.org
Subject: Re: Svn2git: question about --branches
Date: Thu, 30 Sep 2010 16:07:34 +0200	[thread overview]
Message-ID: <20100930160734.056754ec@jk.gs> (raw)
In-Reply-To: <4E10ACF241081344B9702AA8C6440440C5B15CB469@MX01A.corp.emc.com>

Hi,

--- nolan.ring@emc.com <nolan.ring@emc.com> wrote:

> Our svn directory structure at the top level is:
> [...]
> branches
> REbranches
> [...]
> Branches is developer branches; REbranches is release engineering
> branches.  Is there any way to specify both using --branches?

Yep... just use --branches twice. The documentation for these options
even mentions that you can do that, actually. Just saying. :)

-Jan

  reply	other threads:[~2010-09-30 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 11:49 Svn2git: question about --branches nolan.ring
2010-09-30 14:07 ` Jan Krüger [this message]
2010-10-01 11:24   ` nolan.ring

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=20100930160734.056754ec@jk.gs \
    --to=jk@jk.gs \
    --cc=git@vger.kernel.org \
    --cc=nolan.ring@emc.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).