From: Steven Grimm <koreth@midwinter.com>
To: Peter Baumann <waste.manager@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Run garbage collection with loose object pruning after svn dcommit
Date: Fri, 05 Oct 2007 10:48:29 -0700 [thread overview]
Message-ID: <470678ED.8050407@midwinter.com> (raw)
In-Reply-To: <20071005164912.GE4797@xp.machine.xx>
Peter Baumann wrote:
> That's new to me. Glancing over git-commit.sh, I could only find a
> 'git-gc --auto', but no prune. I am not against doing a 'git gc --auto',
> but I am against the --prune, because this could make shared
> repositories unfunctional.
>
Does anyone run "git svn dcommit" from a shared repository? That is the
only command that will trigger this code path.
Given that you lose all the svn metadata if you do "git clone" (or "git
clone -s") on a git-svn-managed repository, it's not clear to me that
anyone would ever be bitten by this. Counterexamples welcome, of course.
How would you feel about a separate config option to specifically enable
auto-pruning, and having "git svn clone" set that option by default?
Presumably anyone who is setting up a shared git-svn repository will be
up to the task of disabling the option.
-Steve
next prev parent reply other threads:[~2007-10-05 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 0:15 [PATCH 2/2] Run garbage collection with loose object pruning after svn dcommit Steven Grimm
2007-10-05 8:04 ` Andreas Ericsson
2007-10-05 8:27 ` Johannes Schindelin
2007-10-05 8:21 ` Peter Baumann
2007-10-05 16:12 ` Steven Grimm
2007-10-05 16:15 ` [PATCH 3/2] Document the fact that git-svn now runs git-gc Steven Grimm
2007-10-05 16:49 ` [PATCH 2/2] Run garbage collection with loose object pruning after svn dcommit Peter Baumann
2007-10-05 17:48 ` Steven Grimm [this message]
2007-10-06 8:15 ` Peter Baumann
2007-10-05 23:54 ` 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=470678ED.8050407@midwinter.com \
--to=koreth@midwinter.com \
--cc=git@vger.kernel.org \
--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 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.