From: Thomas Gummerer <t.gummerer@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: pclouds@gmail.com, ao2@ao2.it, bmwill@google.com,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 07/11] rerere: use repo_read_index_or_die
Date: Sun, 20 May 2018 18:45:37 +0100 [thread overview]
Message-ID: <20180520174537.GA18193@hank.intra.tgummerer.com> (raw)
In-Reply-To: <20180516222118.233868-8-sbeller@google.com>
On 05/16, Stefan Beller wrote:
> By switching to repo_read_index_or_die, we'll get a slightly different
> error message ("index file corrupt") as well as localization of it.
Apart from the slightly different error message, and the localization
(both of which I think are a good thing), I notice that this also
turns a "return error(...)" into a "die(...)". I thought we were
going more towards not 'die'ing in libgit.a code, and letting the
caller handling the errors? Either way I think this change should be
described in the commit message.
Also all other messages in 'rerere.c' are currently not translated.
I'm currently working on a series that includes a patch to do just
that (amongst some other changes to 'rerere'), which I'm hoping to
send soon-ish, but the textual conflicts should we still want this
patch should be easy to solve.
> Signed-off-by: Stefan Beller <sbeller@google.com>
> ---
> rerere.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/rerere.c b/rerere.c
> index 18cae2d11c9..5f35dd66f90 100644
> --- a/rerere.c
> +++ b/rerere.c
> @@ -10,6 +10,7 @@
> #include "attr.h"
> #include "pathspec.h"
> #include "sha1-lookup.h"
> +#include "repository.h"
>
> #define RESOLVED 0
> #define PUNTED 1
> @@ -567,8 +568,7 @@ static int check_one_conflict(int i, int *type)
> static int find_conflict(struct string_list *conflict)
> {
> int i;
> - if (read_cache() < 0)
> - return error("Could not read index");
> + repo_read_index_or_die(the_repository);
>
> for (i = 0; i < active_nr;) {
> int conflict_type;
> @@ -600,8 +600,7 @@ int rerere_remaining(struct string_list *merge_rr)
> int i;
> if (setup_rerere(merge_rr, RERERE_READONLY))
> return 0;
> - if (read_cache() < 0)
> - return error("Could not read index");
> + repo_read_index_or_die(the_repository);
>
> for (i = 0; i < active_nr;) {
> int conflict_type;
> @@ -1103,8 +1102,7 @@ int rerere_forget(struct pathspec *pathspec)
> struct string_list conflict = STRING_LIST_INIT_DUP;
> struct string_list merge_rr = STRING_LIST_INIT_DUP;
>
> - if (read_cache() < 0)
> - return error("Could not read index");
> + repo_read_index_or_die(the_repository);
>
> fd = setup_rerere(&merge_rr, RERERE_NOAUTOUPDATE);
> if (fd < 0)
> --
> 2.17.0.582.gccdcbd54c44.dirty
>
next prev parent reply other threads:[~2018-05-20 17:55 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 [this message]
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 ` [PATCH 00/11] Duy Nguyen
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=20180520174537.GA18193@hank.intra.tgummerer.com \
--to=t.gummerer@gmail.com \
--cc=ao2@ao2.it \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.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).