From: Mathieu Arnold <mat@FreeBSD.org>
To: git@vger.kernel.org
Subject: problem with git worktree and git svn
Date: Wed, 12 Oct 2016 16:45:29 +0200 [thread overview]
Message-ID: <6c83c905-b10a-7f54-873f-54186faacfc8@FreeBSD.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
Hi,
I'm a FreeBSD ports developer, and while our main repository is in
Subversion, some of us use git-svn a lot for development.
I discovered git worktree earlier this week, and I found it a great
asset to be able to have more than one branch of my worktree accessible
at the same time...
Anyway, back to my problem, the way git-svn works, is that it looks for
a directory named "svn" in its gitdir and if it is not present, decide
the repository is using git-svn version 1 (whatever that is) and goes to
parse all the revisions to recreate the svn directory.
So I can only use git svn commands in my main worktree, the one with the
real gitdir.
To fix that, all I had to do is to add a symlink named svn in each
worktree's gitdir and pointing to ../../svn.
I think all that needs to happen is that when adding a new worktree, if
the main git directory has a "svn" directory, add a symlink to it in the
worktree's gitdir.
--
Mathieu Arnold
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]
next reply other threads:[~2016-10-12 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 14:45 Mathieu Arnold [this message]
2016-10-12 21:05 ` problem with git worktree and git svn Stefan Beller
2016-10-13 1:52 ` Eric Wong
2016-10-13 10:29 ` Duy Nguyen
2016-10-13 20:55 ` Eric Wong
2016-10-14 1:46 ` [PATCH 0/2] git-svn: implement "git worktree" awareness Eric Wong
2016-10-14 1:46 ` [PATCH 1/2] git-svn: reduce scope of input record separator change Eric Wong
2016-10-14 1:46 ` [PATCH 2/2] git-svn: "git worktree" awareness Eric Wong
2016-10-26 20:02 ` [PATCH 0/2] git-svn: implement " Eric Wong
2016-10-26 21:17 ` Junio C Hamano
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=6c83c905-b10a-7f54-873f-54186faacfc8@FreeBSD.org \
--to=mat@freebsd.org \
--cc=git@vger.kernel.org \
/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).