From: Jonathan Nieder <jrnieder@gmail.com>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Eric Wong <normalperson@yhbt.net>
Subject: Re: Git-SVN & subdirectory branches
Date: Fri, 27 Aug 2010 20:45:08 -0500 [thread overview]
Message-ID: <20100828014508.GC2004@burratino> (raw)
In-Reply-To: <F393D37F-9BDE-4F29-94E9-806AF88D1A30@gernhardtsoftware.com>
Hi,
Brian Gernhardt wrote:
> For visual learners:
>
> /trunk
> /bigports
> /src
> /boot
> /commands
> ...
> /branches
> /R3.1.0
> /bigports
> /src
> /R3.1.7
> /boot
> /commands
> ...
Right, I don't think git svn has any logic for this. If you want to track
branches like R3.1.7 keeping the layout of trunk, you'll have to patch
git svn.
prev parent reply other threads:[~2010-08-28 1:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 16:37 Git-SVN & subdirectory branches Brian Gernhardt
2010-08-28 1:45 ` Jonathan Nieder [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=20100828014508.GC2004@burratino \
--to=jrnieder@gmail.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).