From: Miklos Vajna <vmiklos@frugalware.org>
To: Eric Wong <normalperson@yhbt.net>
Cc: Peter Baumann <waste.manager@gmx.de>, git@vger.kernel.org
Subject: Re: git-svn branch naming question
Date: Sun, 9 Dec 2007 03:36:00 +0100 [thread overview]
Message-ID: <20071209023600.GP3199@genesis.frugalware.org> (raw)
In-Reply-To: <20071209022624.GA31033@soma>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Sat, Dec 08, 2007 at 06:26:24PM -0800, Eric Wong <normalperson@yhbt.net> wrote:
> I'm not sure if it's considered a "bug", but that's just the
> way it is at the moment. I can't remember why, but I did
> make git-svn force the presence of the "remotes/" prefix
> in all refs it writes to...
okay, i see. one problem: git-svnimport is to be removed and (afaik) the
supposed way is to use git-svn instead. what is the supposed way to use
git-svn to convert an svn repo to a git one if the method i tried is not
working?
(if the branches are fetched to "remotes/" then they won't be visible
when one clones the converted repo)
thanks,
- VMiklos
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-12-09 2:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 1:04 git-svn branch naming question Miklos Vajna
2007-12-08 10:59 ` Peter Baumann
2007-12-08 14:14 ` Miklos Vajna
2007-12-08 16:56 ` Peter Baumann
2007-12-08 23:52 ` Miklos Vajna
2007-12-09 2:05 ` Miklos Vajna
2007-12-09 2:13 ` Björn Steinbrink
2007-12-09 2:25 ` Miklos Vajna
2007-12-09 2:26 ` Eric Wong
2007-12-09 2:36 ` Miklos Vajna [this message]
2007-12-09 3:26 ` Eric Wong
2007-12-09 5:16 ` Harvey Harrison
2007-12-09 19:36 ` Miklos Vajna
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=20071209023600.GP3199@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=waste.manager@gmx.de \
/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).