From: Matheus Tavares Bernardino <matheus.bernardino@usp.br>
To: Lucas Oshiro <lucasseikioshiro@gmail.com>
Cc: git <git@vger.kernel.org>,
"Kernel USP" <kernel-usp@googlegroups.com>,
rcdailey.lists@gmail.com, "Taylor Blau" <me@ttaylorr.com>,
"Jeff King" <peff@peff.net>,
"Bárbara Fernandes" <barbara.dcf@gmail.com>
Subject: Re: [RFC WIP PATCH 1/3] tag: factor out tag reading from write_tag_body()
Date: Tue, 8 Oct 2019 22:48:43 -0300 [thread overview]
Message-ID: <CAHd-oW7HXzvjxzV=79yRAMHc=msB2rWmWCVEYuB4N1LnOMwDyQ@mail.gmail.com> (raw)
In-Reply-To: <20191008184727.14337-2-lucasseikioshiro@gmail.com>
On Tue, Oct 8, 2019 at 3:47 PM Lucas Oshiro <lucasseikioshiro@gmail.com> wrote:
>
> Improve code readability by moving tag reading to a new function called
> get_tag_body, which will be used in the implementation of the git tag
> --amend functionality.
This function is also used in your third patch, to fix git-tag's
--no-edit implementation, right? Maybe you could mention this here,
instead of referencing the --amend feature, as the former is already
present in this series.
> Add warning in write_tag_body() in case the tag body is not successfully
> recovered.
>
> Co-authored-by: Bárbara Fernandes <barbara.dcf@gmail.com>
> Signed-off-by: Bárbara Fernandes <barbara.dcf@gmail.com>
> Signed-off-by: Lucas Oshiro <lucasseikioshiro@gmail.com>
> Helped-by: Matheus Tavares <matheus.bernardino@usp.br>
These tags usually come in chronological order. So I think the
Helped-by should come first as I helped you, then you and Bárbara
co-authored the patch and then, lastly, you sent it.
> ---
> builtin/tag.c | 42 ++++++++++++++++++++++++++++++++++--------
> 1 file changed, 34 insertions(+), 8 deletions(-)
>
> diff --git a/builtin/tag.c b/builtin/tag.c
> index e0a4c25382..e1e3549af9 100644
> --- a/builtin/tag.c
> +++ b/builtin/tag.c
> @@ -170,26 +170,52 @@ static int git_tag_config(const char *var, const char *value, void *cb)
> return git_color_default_config(var, value, cb);
> }
>
> -static void write_tag_body(int fd, const struct object_id *oid)
> +/*
> + * Returns the tag body of the given oid or NULL, in case of error. If size is
> + * not NULL it is assigned the body size in bytes (excluding the '\0').
> + */
> +static char *get_tag_body(const struct object_id *oid, size_t *size)
> {
> - unsigned long size;
> + unsigned long buf_size;
> enum object_type type;
> - char *buf, *sp;
> + char *buf, *sp, *tag_body;
> + size_t tag_body_size, signature_offset;
>
> - buf = read_object_file(oid, &type, &size);
> + buf = read_object_file(oid, &type, &buf_size);
> if (!buf)
> - return;
> + return NULL;
> /* skip header */
> sp = strstr(buf, "\n\n");
>
> - if (!sp || !size || type != OBJ_TAG) {
> + if (!sp || !buf_size || type != OBJ_TAG) {
> free(buf);
> - return;
> + return NULL;
> }
> sp += 2; /* skip the 2 LFs */
> - write_or_die(fd, sp, parse_signature(sp, buf + size - sp));
> + signature_offset = parse_signature(sp, buf + buf_size - sp);
> + sp[signature_offset] = '\0';
>
> + /* detach sp from buf */
> + tag_body_size = strlen(sp) + 1;
> + tag_body = xmalloc(tag_body_size);
> + xsnprintf(tag_body, tag_body_size, "%s", sp);
> free(buf);
> + if (size)
> + *size = tag_body_size - 1; /* exclude '\0' */
> + return tag_body;
> +}
> +
> +static void write_tag_body(int fd, const struct object_id *oid)
> +{
> + size_t size;
> + const char *tag_body = get_tag_body(oid, &size);
> +
> + if (!tag_body) {
> + warning("failed to get tag body for %s", oid->hash);
> + return;
> + }
> + printf("tag_body: <%s>\n", tag_body);
Hm, is this addition right or perhaps was it added in the patch by mistake?
> + write_or_die(fd, tag_body, size);
> }
>
> static int build_tag_object(struct strbuf *buf, int sign, struct object_id *result)
> --
> 2.23.0
>
next prev parent reply other threads:[~2019-10-09 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 18:47 [RFC WIP PATCH 0/3] tag: fix --edit and --no-edit flags Lucas Oshiro
2019-10-08 18:47 ` [RFC WIP PATCH 1/3] tag: factor out tag reading from write_tag_body() Lucas Oshiro
2019-10-09 1:48 ` Matheus Tavares Bernardino [this message]
2019-10-10 2:42 ` Junio C Hamano
2019-10-08 18:47 ` [RFC WIP PATCH 2/3] tag: factor out prepare tag template code Lucas Oshiro
2019-10-09 3:02 ` Matheus Tavares Bernardino
2019-10-10 2:51 ` Junio C Hamano
2019-10-10 4:29 ` Junio C Hamano
2019-10-08 18:47 ` [RFC WIP PATCH 3/3] tag: add full support for --edit and --no-edit Lucas Oshiro
2019-10-09 9:19 ` Matheus Tavares Bernardino
2019-10-10 3:34 ` Junio C Hamano
2019-10-10 2:13 ` [RFC WIP PATCH 0/3] tag: fix --edit and --no-edit flags 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHd-oW7HXzvjxzV=79yRAMHc=msB2rWmWCVEYuB4N1LnOMwDyQ@mail.gmail.com' \
--to=matheus.bernardino@usp.br \
--cc=barbara.dcf@gmail.com \
--cc=git@vger.kernel.org \
--cc=kernel-usp@googlegroups.com \
--cc=lucasseikioshiro@gmail.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=rcdailey.lists@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).