From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Miriam Rubio <mirucam@gmail.com>
Cc: git@vger.kernel.org, Tanushree Tumane <tanushreetumane@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [Outreachy] [PATCH] bisect--helper: refer branch.buf before strbuf_release(...)
Date: Sun, 8 Dec 2019 20:11:47 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1912082003420.31080@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20191208172813.16518-1-mirucam@gmail.com>
Hi Miriam,
welcome to the Git project!
On Sun, 8 Dec 2019, Miriam Rubio wrote:
> From: Tanushree Tumane <tanushreetumane@gmail.com>
Is this really a patch authored by Tanushree, or is this a fix written by
you, intended to fix a patch authored by Tanushree?
If it is the latter, please use a completely new commit message and take
the authorship yourself.
> Move `error("...%s...", branch.buf);` before `strbuf_release(&branch);`
> to release string buffer `branch` and the memory it used.
This describes the "what?", but the patch already does that. The commit
message should be more about the "why?".
In this instance, I believe that the commit message should read more like
this:
-- snip --
bisect--helper: avoid free-after-use
In 5e82c3dd22a (bisect--helper: `bisect_reset` shell function in C,
2019-01-02), the `git bisect reset` subcommand was ported to C. When the
call to `git checkout` failed, an error message was reported to the
user.
However, this error message used the `strbuf` that had just been
released already. Let's switch that around: first use it, then release
it.
Signed-off-by: Miriam Rubio <mirucam@gmail.com>
-- snap --
>
> Mentored-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Mentored-by: Christian Couder <chriscool@tuxfamily.org>
> Signed-off-by: Tanushree Tumane <tanushreetumane@gmail.com>
> Signed-off-by: Miriam Rubio <mirucam@gmail.com>
> ---
> builtin/bisect--helper.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/builtin/bisect--helper.c b/builtin/bisect--helper.c
> index 1fbe156e67..3055b2bb50 100644
> --- a/builtin/bisect--helper.c
> +++ b/builtin/bisect--helper.c
> @@ -169,11 +169,12 @@ static int bisect_reset(const char *commit)
>
> argv_array_pushl(&argv, "checkout", branch.buf, "--", NULL);
> if (run_command_v_opt(argv.argv, RUN_GIT_CMD)) {
> + error(_("could not check out original"
> + " HEAD '%s'. Try 'git bisect"
> + " reset <commit>'."), branch.buf);
> strbuf_release(&branch);
> argv_array_clear(&argv);
> - return error(_("could not check out original"
> - " HEAD '%s'. Try 'git bisect"
> - " reset <commit>'."), branch.buf);
> + return -1;
The patch looks good.
Thanks!
Johannes
> }
> argv_array_clear(&argv);
> }
> --
> 2.21.0 (Apple Git-122.2)
>
>
next prev parent reply other threads:[~2019-12-08 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 17:28 [Outreachy] [PATCH] bisect--helper: refer branch.buf before strbuf_release(...) Miriam Rubio
2019-12-08 19:11 ` Johannes Schindelin [this message]
2019-12-09 8:15 ` Miriam R.
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=nycvar.QRO.7.76.6.1912082003420.31080@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=mirucam@gmail.com \
--cc=tanushreetumane@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).