Jeff King <peff@xxxxxxxx> writes: > Heh. I originally wrote just "put" and "get" for brevity, but then > worried that wasn't clear enough. Let's just use the full names. We can > afford the extra few bytes, and it makes it easier if we later need to > grep for them or whatever. Here's a replacement patch (I won't send the > whole series just yet, as it seems it hasn't gotten a whole lot of > review so far). It seems that you sent the original instead X-<. I'll just replace the original 09/23 with the following squashed in for now. Thanks. fsck.h | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/fsck.h b/fsck.h index f6f0c40060..6228f0b2d4 100644 --- a/fsck.h +++ b/fsck.h @@ -73,13 +73,13 @@ int fsck_finish(struct fsck_options *options); * If fsck_enable_object_names() has not been called, all other functions are * noops. * - * Use put_object_name() to seed initial names (e.g. from refnames); the fsck - * code will extend that while walking trees, etc. + * Use fsck_put_object_name() to seed initial names (e.g. from refnames); the + * fsck code will extend that while walking trees, etc. * - * Use get_object_name() to get a single name (or NULL if none). Or the more - * convenient describe_object(), which always produces an output string with - * the oid combined with the name (if any). Note that the return value points - * to a rotating array of static buffers, and may be invalidated by a + * Use fsck_get_object_name() to get a single name (or NULL if none). Or the + * more convenient describe_object(), which always produces an output string + * with the oid combined with the name (if any). Note that the return value + * points to a rotating array of static buffers, and may be invalidated by a * subsequent call. */ void fsck_enable_object_names(struct fsck_options *options);
