From: Michael Stefaniuc <mstefani@redhat.com>
To: git@vger.kernel.org
Subject: [PATCH] git-am: Run git gc only once and not for every patch.
Date: Fri, 4 Jan 2008 19:59:26 +0100 [thread overview]
Message-ID: <20080104185926.GA11912@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
With "too many unreachable loose objects" git gc --auto will always
trigger. This clutters the output of git am and thus git rebase.
The work flow of the Wine project doesn't include git merge. git rebase
is therefor used to track the origin. This will produce soon too many
loose objects for git gc --auto's taste. Pruning the repository would
"fix" it. But we tell Wine developers new to git to NOT prune as long as
they aren't confident enough with git; just as a safety net in case they
have thrown away month of work.
Signed-off-by: Michael Stefaniuc <mstefani@redhat.com>
---
git-am.sh | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/git-am.sh b/git-am.sh
index 65c634f..5f0f241 100755
--- a/git-am.sh
+++ b/git-am.sh
@@ -469,9 +469,9 @@ do
"$GIT_DIR"/hooks/post-applypatch
fi
- git gc --auto
-
go_next
done
+git gc --auto
+
rm -fr "$dotest"
--
1.5.4.rc2
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-01-04 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 18:59 Michael Stefaniuc [this message]
2008-01-04 19:38 ` [PATCH] git-am: Run git gc only once and not for every patch Nicolas Pitre
2008-01-04 20:21 ` Michael Stefaniuc
2008-01-04 20:58 ` Nicolas Pitre
2008-01-04 20:38 ` Junio C Hamano
2008-01-04 21:08 ` Michael Stefaniuc
2008-01-04 22:00 ` Junio C Hamano
2008-01-05 6:55 ` Junio C Hamano
2008-01-05 16:23 ` Michael Stefaniuc
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=20080104185926.GA11912@redhat.com \
--to=mstefani@redhat.com \
--cc=git@vger.kernel.org \
/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).