| commit | 2c319886c04c5e77da55c66ee9e860b101e5af32 | |
| author | Jeff King <peff@peff.net> | |
| Mon, 7 Jan 2019 08:39:33 +0000 (7 03:39 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 8 Jan 2019 17:41:06 +0000 (8 09:41 -0800) | ||
| tree | b8d414b9f62bca7e79565f2388177aec50236ff0 | treesnapshot (tar.gz zip) |
| parent | 760113574ff6f503001e2c75b96233b8752cbc37 | commitdiff |
sha1-file: avoid "sha1 file" for generic use in messages
These error messages say "sha1 file", which is vague and not common in
user-facing documentation. Unlike the conversions from the previous
commit, these do not always refer to loose objects.
In finalize_object_file() we could be dealing with a packfile. Let's
just say "unable to write file" instead; since we include the filename,
the nature of the file is clear from the rest of the message.
In force_object_loose(), we're calling into read_object(), which could
actually be _any_ type of object. Just say "object".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
These error messages say "sha1 file", which is vague and not common in
user-facing documentation. Unlike the conversions from the previous
commit, these do not always refer to loose objects.
In finalize_object_file() we could be dealing with a packfile. Let's
just say "unable to write file" instead; since we include the filename,
the nature of the file is clear from the rest of the message.
In force_object_loose(), we're calling into read_object(), which could
actually be _any_ type of object. Just say "object".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| sha1-file.c | diffblobblamehistory |