From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <l.s.r@web.de>,
"Git Mailing List" <git@vger.kernel.org>,
"Ronnie Sahlberg" <sahlberg@google.com>
Subject: Re: [PATCH] refs: release strbuf after use in check_refname_component()
Date: Mon, 29 Dec 2014 16:13:13 -0500 [thread overview]
Message-ID: <20141229211312.GA26793@peff.net> (raw)
In-Reply-To: <xmqq387y1hnc.fsf@gitster.dls.corp.google.com>
On Mon, Dec 29, 2014 at 09:37:43AM -0800, Junio C Hamano wrote:
> René Scharfe <l.s.r@web.de> writes:
>
> > Signed-off-by: Rene Scharfe <l.s.r@web.de>
> > ---
> > refs.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/refs.c b/refs.c
> > index 5fcacc6..ed3b2cb 100644
> > --- a/refs.c
> > +++ b/refs.c
> > @@ -2334,7 +2334,7 @@ static struct ref_lock *lock_ref_sha1_basic(const char *refname,
> > struct strbuf err = STRBUF_INIT;
> > unable_to_lock_message(ref_file, errno, &err);
> > error("%s", err.buf);
> > - strbuf_reset(&err);
> > + strbuf_release(&err);
> > goto error_return;
> > }
> > }
>
> The subject does not seem to match what the patch is doing, but the
> patch is obviously correct ;-)
The worst part of this is that I got it right in my hacked-up version:
http://article.gmane.org/gmane.comp.version-control.git/259853
but then after much discussion, we dropped all of the lead-in patches,
and I sent Ronnie's unedited:
http://article.gmane.org/gmane.comp.version-control.git/259911
All that looking and I didn't notice the release/reset difference
between our two versions. Sheesh.
Which is all a roundabout way of saying "yes, René's patch is obviously
correct". :)
-Peff
prev parent reply other threads:[~2014-12-29 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 0:18 [PATCH] refs: release strbuf after use in check_refname_component() René Scharfe
2014-12-29 17:37 ` Junio C Hamano
2014-12-29 21:13 ` Jeff King [this message]
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=20141229211312.GA26793@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=sahlberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.