From: Eric Wong <normalperson@yhbt.net>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-svn: unlink internal index files after operations
Date: Fri, 14 Dec 2007 00:29:45 -0800 [thread overview]
Message-ID: <20071214082945.GA19559@soma> (raw)
In-Reply-To: <20071213202757.GA2387@diana.vm.bytemark.co.uk>
Karl Hasselström <kha@treskal.com> wrote:
> On 2007-12-13 08:27:34 -0800, Eric Wong wrote:
>
> > Being git, we can generate these very quickly on the fly as needed,
> > so there's no point in wasting space for these things for large
> > projects.
>
> Excellent!
>
> For existing repos, I assume the correct thing to do is to just blast
> all the existing index files manually?
Yes. index files inside $GIT_DIR/svn have always been safely deletable
(except while a git-svn is actually running :).
I'll probably work on an automated full migration strategy at some
point (handling rev_db => rev_map, mainly) when I have time.
--
Eric Wong
prev parent reply other threads:[~2007-12-14 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 16:27 [PATCH] git-svn: unlink internal index files after operations Eric Wong
2007-12-13 20:27 ` Karl Hasselström
2007-12-14 8:29 ` Eric Wong [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=20071214082945.GA19559@soma \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kha@treskal.com \
/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).