From: Eric Wong <normalperson@yhbt.net>
To: Nicolas Vilz 'niv' <niv@iaglans.de>
Cc: git <git@vger.kernel.org>
Subject: Re: git-svn and svn sw --relocate
Date: Sun, 2 Apr 2006 15:21:00 -0700 [thread overview]
Message-ID: <20060402222100.GA17888@localdomain> (raw)
In-Reply-To: <4430123E.5090605@iaglans.de>
Nicolas Vilz 'niv' <niv@iaglans.de> wrote:
> ok, guys... next question:
>
> i have now my repository locally and i want to get it remotely on a
> server, in order to have a few collaborators...
>
> the steps on the svn-side are clear. But what do i have todo on the
> git-svn-side of this life?
>
> does a simple "svn sw --relocate" do the job in the git-svn meta-dir?
Yes, you'll need to do that in .git/git-svn/tree and also update
.git/git-svn/info/url by hand.
--
Eric Wong
next prev parent reply other threads:[~2006-04-02 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 18:04 git-svn and svn sw --relocate Nicolas Vilz 'niv'
2006-04-02 22:21 ` Eric Wong [this message]
2006-04-03 16:20 ` Nicolas Vilz 'niv'
2006-04-03 22:39 ` Eric Wong
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=20060402222100.GA17888@localdomain \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=niv@iaglans.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).