From: Peter Baumann <waste.manager@gmx.de>
To: Steven Grimm <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Run garbage collection with loose object pruning after svn dcommit
Date: Fri, 5 Oct 2007 18:49:12 +0200 [thread overview]
Message-ID: <20071005164912.GE4797@xp.machine.xx> (raw)
In-Reply-To: <47066255.6080500@midwinter.com>
On Fri, Oct 05, 2007 at 09:12:05AM -0700, Steven Grimm wrote:
> Peter Baumann wrote:
>> I don't like the automatic prune. What if someone has other objects in
>> there which shouldn't be pruned? Making git svn dcommit doing the prune
>> would be at least suprising, because how is one supposed to know that
>> doing a commit into svn will prune all your precious objects?
>>
>
> "git commit" already does garbage collection, so we've already set a
> precedent for a commit operation also doing some cleanup at the end.
> However, you're correct that this cleanup behavior (and the way to turn it
> off) should be documented so that there's some way to know about it. Doc
> patch forthcoming.
>
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.
-Peter
next prev parent reply other threads:[~2007-10-05 16:49 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 ` Peter Baumann [this message]
2007-10-05 17:48 ` [PATCH 2/2] Run garbage collection with loose object pruning after svn dcommit Steven Grimm
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071005164912.GE4797@xp.machine.xx \
--to=waste.manager@gmx.de \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).