From: Duy Nguyen <pclouds@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: ao2@ao2.it, bmwill@google.com, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 00/11]
Date: Sat, 19 May 2018 08:57:18 +0200 [thread overview]
Message-ID: <20180519065718.GD14755@duynguyen.home> (raw)
In-Reply-To: <20180516222118.233868-1-sbeller@google.com>
On Wed, May 16, 2018 at 03:21:07PM -0700, Stefan Beller wrote:
> > If you have time, yes translate them all. I don't see how any of these
> > strings are meant for script. If not, just _() the new string you
> > added is fine.
>
> > With a majority of call sites dying like this though, I wonder if we
> > should just add repo_read_index_or_die() with die() inside. Then the
> > next person won't likely accidentally forget _()
>
> So this comment tricked me into coming up with a patch series. :)
Yay! (And sorry, Junio)
>
> Each patch is themed, I tried to make each commit special w.r.t. reviewers
> attention.
>
> We'd start out with a resend of the origin patch, which is boring.
>
> Then we'll move all similar cases into one function (no-op for
> introducing the repo_read_index_or_die function as all callers will have the
> same error message and the same localisation).
>
> Any following patch will be more controversial then the previous patches,
> I would expect, as we introduce more and more change.
>
> The last patch is just an attempt to finish the series gracefully,
> and may contain errors (sometimes we do not want to die() in case of
> corrupt index).
>
> Is this series roughly what you had in mind?
This is better than what I had in mind, in fact.
--
Duy
next prev parent reply other threads:[~2018-05-19 6:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 1:04 [PATCH] grep: handle corrupt index files early Stefan Beller
2018-05-15 12:18 ` Johannes Schindelin
2018-05-15 13:13 ` Duy Nguyen
2018-05-15 16:44 ` Stefan Beller
2018-05-16 15:24 ` Duy Nguyen
2018-05-16 22:21 ` [PATCH 00/11] Stefan Beller
2018-05-16 22:21 ` [PATCH 01/11] grep: handle corrupt index files early Stefan Beller
2018-05-16 22:21 ` [PATCH 02/11] repository: introduce repo_read_index_or_die Stefan Beller
2018-05-19 6:37 ` Duy Nguyen
2018-05-21 18:38 ` Stefan Beller
2018-05-21 18:50 ` Brandon Williams
2018-05-21 19:27 ` Stefan Beller
2018-05-22 15:13 ` Duy Nguyen
2018-05-22 17:49 ` Why do we have both x*() and *_or_die() for "do or die"? Ævar Arnfjörð Bjarmason
2018-05-22 17:55 ` Duy Nguyen
2018-05-22 18:38 ` Jonathan Nieder
2018-05-22 18:04 ` Stefan Beller
2018-05-23 3:19 ` Junio C Hamano
2018-05-16 22:21 ` [PATCH 03/11] builtin/grep: use repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 04/11] submodule: " Stefan Beller
2018-05-16 22:21 ` [PATCH 05/11] builtin/ls-files: " Stefan Beller
2018-05-16 22:21 ` [PATCH 06/11] read_cache: use repo_read_index_or_die with different error messages Stefan Beller
2018-05-16 22:21 ` [PATCH 07/11] rerere: use repo_read_index_or_die Stefan Beller
2018-05-20 17:45 ` Thomas Gummerer
2018-05-21 18:46 ` Stefan Beller
2018-05-16 22:21 ` [PATCH 08/11] check-attr: switch to repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 09/11] checkout-index: switch to repo_read_index Stefan Beller
2018-05-16 22:21 ` [PATCH 10/11] test helpers: switch to repo_read_index_or_die Stefan Beller
2018-05-16 22:21 ` [PATCH 11/11] read_cache: convert most calls " Stefan Beller
2018-05-16 22:27 ` Brandon Williams
2018-05-19 6:55 ` Duy Nguyen
2018-05-19 6:54 ` Duy Nguyen
2018-05-19 6:57 ` Duy Nguyen [this message]
2018-05-17 1:36 ` [PATCH] grep: handle corrupt index files early Junio C Hamano
2018-05-17 17:21 ` Stefan Beller
2018-05-17 22:57 ` Junio C Hamano
2018-05-15 17:01 ` Brandon Williams
2018-05-15 23:58 ` Junio C Hamano
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=20180519065718.GD14755@duynguyen.home \
--to=pclouds@gmail.com \
--cc=ao2@ao2.it \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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).