From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: David Turner <dturner@twopensource.com>,
mhagger@alum.mit.edu, pclouds@gmail.com
Subject: [PATCH 0/10] cleaning up check_repository_format_gently
Date: Tue, 1 Mar 2016 09:35:46 -0500 [thread overview]
Message-ID: <20160301143546.GA30806@sigill.intra.peff.net> (raw)
After the discussion in:
http://thread.gmane.org/gmane.comp.version-control.git/287949/focus=288002
I came up with this series to try to address some of the warts in
check_repository_format_gently().
I had hoped to come up with something very small that could go at the
front of the refs-backend series, but as with any time I look at the
setup code, it managed to snowball into a potpourri of hidden
assumptions.
So I hope David isn't _too_ irritated to see this in his inbox. Rebasing
the refs-backend on top shouldn't be too bad, and the end result would
be cleaner and more correct. My bigger worry is just that changing the
setup code is inherently flaky, and I don't want to hold David's series
hostage.
[01/10]: setup: document check_repository_format()
[02/10]: wrap shared_repository global in get/set accessors
[03/10]: lazily load core.sharedrepository
[04/10]: check_repository_format_gently: stop using git_config_early
[05/10]: config: drop git_config_early
[06/10]: setup: refactor repo format reading and verification
[07/10]: init: use setup.c's repo version verification
[08/10]: setup: unify repository version callbacks
[09/10]: setup: drop repository_format_version global
[10/10]: setup: drop GIT_REPO_VERSION constants
-Peff
next reply other threads:[~2016-03-01 14:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 14:35 Jeff King [this message]
2016-03-01 14:37 ` [PATCH 01/10] setup: document check_repository_format() Jeff King
2016-03-01 14:38 ` [PATCH 02/10] wrap shared_repository global in get/set accessors Jeff King
2016-03-01 14:39 ` [PATCH 03/10] lazily load core.sharedrepository Jeff King
2016-03-03 13:00 ` Duy Nguyen
2016-03-03 18:23 ` Jeff King
2016-03-01 14:40 ` [PATCH 04/10] check_repository_format_gently: stop using git_config_early Jeff King
2016-03-03 13:08 ` Duy Nguyen
2016-03-03 18:27 ` Jeff King
2016-03-01 14:40 ` [PATCH 05/10] config: drop git_config_early Jeff King
2016-03-01 14:42 ` [PATCH 06/10] setup: refactor repo format reading and verification Jeff King
2016-03-01 21:20 ` David Turner
2016-03-02 2:51 ` Jeff King
2016-03-03 13:19 ` Duy Nguyen
2016-03-03 18:28 ` Jeff King
2016-03-01 14:43 ` [PATCH 07/10] init: use setup.c's repo version verification Jeff King
2016-03-01 14:45 ` [PATCH 08/10] setup: unify repository version callbacks Jeff King
2016-03-01 14:45 ` [PATCH 09/10] setup: drop repository_format_version global Jeff King
2016-03-01 14:45 ` [PATCH 10/10] setup: drop GIT_REPO_VERSION constants Jeff King
2016-03-02 0:13 ` David Turner
2016-03-02 2:52 ` Jeff King
2016-03-02 0:42 ` [PATCH 0/10] cleaning up check_repository_format_gently David Turner
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=20160301143546.GA30806@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@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).