git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jim Meyering <jim@meyering.net>
Cc: "David Symonds" <dsymonds@gmail.com>, "git list" <git@vger.kernel.org>
Subject: Re: [PATCH] Remove useless if-before-free tests.
Date: Mon, 18 Feb 2008 01:36:35 -0800	[thread overview]
Message-ID: <7vwsp2ppwc.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87pruuy64v.fsf@rho.meyering.net> (Jim Meyering's message of "Mon, 18 Feb 2008 10:18:40 +0100")

Jim Meyering <jim@meyering.net> writes:

> It's a definite loss of portability if you can find a reasonable porting
> target for which free(NULL) fails.  But even if you do, the fix is
> not to reject the clean-up, but to amend it with a wrapper function.
> That encapsulates the work-around in one place rather than polluting
> all of those files.

As we already have unchecked free(ptr) in our code _anyway_,
there _technically_ is no reason to reject the clean-up patch.

We just need to find a quiescent time to do so so that actively
cooking patches in people's trees (and topics in 'next') won't
get needless conflicts.

  reply	other threads:[~2008-02-18  9:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 21:58 [PATCH] Remove useless if-before-free tests Jim Meyering
2008-02-17 22:09 ` David Symonds
2008-02-18  9:18   ` Jim Meyering
2008-02-18  9:36     ` Junio C Hamano [this message]
2008-02-17 22:16 ` Johannes Schindelin
2008-02-18  9:01   ` Jim Meyering
2008-02-18 14:27 ` Jean-Luc Herren
2008-02-20 10:26   ` Jim Meyering
2008-02-22 17:18     ` Junio C Hamano
2008-02-22 17:35       ` Jim Meyering
2008-02-22 17:40         ` Junio C Hamano
2008-02-22 22:08           ` Jim Meyering
2008-02-22 23:05             ` Junio C Hamano
2008-02-24 18:15               ` Jim Meyering
2009-02-26 13:48                 ` Mike Ralphson
2008-02-26  6:59               ` Uwe Kleine-König
2008-02-23 13:30             ` Morten Welinder
2008-02-24 10:06               ` Johannes Schindelin

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=7vwsp2ppwc.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jim@meyering.net \
    /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 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 NNTP newsgroup(s).