All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: weigelt@metux.de
Subject: Re: git-svn mirror in bare repo
Date: Mon, 23 Aug 2010 17:05:16 +0200	[thread overview]
Message-ID: <4C728E2C.8080003@drmicha.warpmail.net> (raw)
In-Reply-To: <20100823131348.GC12810@nibiru.local>

Enrico Weigelt venit, vidit, dixit 23.08.2010 15:13:
> * Michael J Gruber <git@drmicha.warpmail.net> wrote:
>> Enrico Weigelt venit, vidit, dixit 23.08.2010 14:24:
>>>
>>> Hi folks,
>>>
>>> is it possible to use git-svn w/ an bare repository (eg. using
>>> an temporary workdir when necessary or directly creating tree
>>> and commit objects w/o going through workdir at all) ?
>>
>> No.
> 
> hmm, can it work with an external workdir ?

You can have the workdir anywhere you like by using the core.worktree
setting. So, if you mind the size requirements you can put it onto some
fast tempdir (tmpfs, say). In fact, if all you do is "git svn fetch"
then git svn may not even notice a missing worktree (would have to try).
"git svn rebase" does need a worktree.

> 
>>> I'm running a dozen of mirrors (also from cvs), some from fairly
>>> large and I'd like to get rid of the working copies.
>>
>> Your only option is a different conversion tool. GSoC resulted in a lot
>> of code in this direction, but I'm not sure it can do without a workdir.
>> It is based on svndump
> 
> I guess that requires access to the raw repository (on the server),
> not just unprivileged svn client access, right ?

In fact, Ram's GSoC project started off with svnrdump which is now part
of the subversion code base (i.e. in their trunk). It is basically
"svndump remote", i.e. a client outputting svn dump format.

Michael

P.S.: We usually keep cc's when replying here.

  reply	other threads:[~2010-08-23 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 12:24 git-svn mirror in bare repo Enrico Weigelt
2010-08-23 12:58 ` Michael J Gruber
2010-08-23 13:13   ` Enrico Weigelt
2010-08-23 15:05     ` Michael J Gruber [this message]
2010-08-28 16:45 ` Wesley J. Landaker

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=4C728E2C.8080003@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=weigelt@metux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.