From: Jeff King <peff@peff.net>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git Mailing List <git@vger.kernel.org>,
Stefan Beller <stefanbeller@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] repack: call prune_packed_objects() and update_server_info() directly
Date: Sat, 13 Sep 2014 16:15:38 -0400 [thread overview]
Message-ID: <20140913201538.GA24854@peff.net> (raw)
In-Reply-To: <5413F201.8030005@web.de>
On Sat, Sep 13, 2014 at 09:28:01AM +0200, René Scharfe wrote:
> Call the functions behind git prune-packed and git update-server-info
> directly instead of using run_command(). This is shorter, easier and
> quicker.
It can also introduce bugs, since a lot of git code assumes it is
running in a single process and can die() or mark up global variables at
will. :)
I gave a quick read-through of the code and I think these calls are OK.
The two things I noticed were:
1. We might die on a malloc failure that would otherwise go unnoticed
in a sub-process. That's probably OK.
2. The info/packs file is generated from our internal packed_git list.
This list can get crufty if you have a long-running process that
accesses objects and other processes are repacking. I think that's
OK here; the parent repack process is not very long-lived.
I did, however, notice that the code we are calling has some problems of
its own. :) Here are some fixes:
[1/3]: prune-packed: fix minor memory leak
[2/3]: make update-server-info more robust
[3/3]: server-info: clean up after writing info/packs
-Peff
next prev parent reply other threads:[~2014-09-13 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 7:28 [PATCH] repack: call prune_packed_objects() and update_server_info() directly René Scharfe
2014-09-13 8:59 ` Stefan Beller
2014-09-13 20:15 ` Jeff King [this message]
2014-09-13 20:16 ` [PATCH 1/3] prune-packed: fix minor memory leak Jeff King
2014-09-13 20:19 ` [PATCH 2/3] make update-server-info more robust Jeff King
2014-09-14 17:38 ` René Scharfe
2014-09-15 18:39 ` Junio C Hamano
2014-09-15 23:56 ` Jeff King
2014-09-13 20:19 ` [PATCH 3/3] server-info: clean up after writing info/packs Jeff King
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=20140913201538.GA24854@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=stefanbeller@gmail.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).