From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: David Turner <dturner@twopensource.com>, pclouds@gmail.com
Subject: [PATCH v2 0/10] cleaning up check_repository_format_gently
Date: Fri, 11 Mar 2016 17:36:20 -0500 [thread overview]
Message-ID: <20160311223620.GA7963@sigill.intra.peff.net> (raw)
This is a re-roll of:
http://article.gmane.org/gmane.comp.version-control.git/288017
The changes from v1 are:
- dropped original 10/10 that got rid of GIT_REPO_VERSION defines
(David mentioned that he's going to be expanding their use, so the
argument that they are not used does not make sense)
- added new 10/10 marking messages for translation (suggested by Duy)
- added int return value to new read_repository_format(); this is
redundant with the error value returned in the struct, but allows a
more idiomatic:
if (read_repository_format(&format, file) < 0)
...
- drop confusing comment from 06/10, in favor of a better explanation
in the commit message
- fixed newline regression from v1 when printing out unknown
extensions. Note that because we switch from looping over warning()
or die() to sticking errors into a strbuf (which the caller then
feeds to warning/die), the format changed a bit. Naively, it would
become:
warning: unknown extension: foo
unknown:extension: bar
but I turned it into the more pleasant:
warning: unknown repository extensions found:
foo
bar
I think it would be better still if warning() was smart enough to
stick its prefix in front of all lines (like advise() does). But
that's outside the scope of this series. And it probably doesn't
matter much either way; this is not a message we'd expect anyone to
see routinely.
[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]: verify_repository_format: mark messages for translation
-Peff
next reply other threads:[~2016-03-11 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 22:36 Jeff King [this message]
2016-03-11 22:36 ` [PATCH v2 01/10] setup: document check_repository_format() Jeff King
2016-03-11 22:36 ` [PATCH v2 02/10] wrap shared_repository global in get/set accessors Jeff King
2016-03-11 22:36 ` [PATCH v2 03/10] lazily load core.sharedrepository Jeff King
2016-03-11 22:36 ` [PATCH v2 04/10] check_repository_format_gently: stop using git_config_early Jeff King
2016-03-11 22:37 ` [PATCH v2 05/10] config: drop git_config_early Jeff King
2016-03-11 23:33 ` Junio C Hamano
2016-03-11 22:37 ` [PATCH v2 06/10] setup: refactor repo format reading and verification Jeff King
2016-03-11 22:37 ` [PATCH v2 07/10] init: use setup.c's repo version verification Jeff King
2016-03-11 22:37 ` [PATCH v2 08/10] setup: unify repository version callbacks Jeff King
2016-03-11 22:37 ` [PATCH v2 09/10] setup: drop repository_format_version global Jeff King
2016-03-11 22:37 ` [PATCH v2 10/10] verify_repository_format: mark messages for translation 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=20160311223620.GA7963@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--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).