public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
	 GNU C Library <libc-alpha@sourceware.org>,
	 DJ Delorie <dj@redhat.com>
Subject: Re: [PATCH v4] libc: Extend __libc_freeres framework (Bug 23329).
Date: Mon, 02 Jul 2018 08:56:00 -0000	[thread overview]
Message-ID: <mvm36x210ey.fsf@suse.de> (raw)
In-Reply-To: <448769ad-a10a-3c3c-2229-464a893c12bb@redhat.com> (Florian Weimer's message of "Thu, 28 Jun 2018 21:10:39 +0200")

On Jun 28 2018, Florian Weimer <fweimer@redhat.com> wrote:

> I used git cat-file blob.  I'm surprised that git show handles blob hashes
> because doing so increases the chances of collisions

git cat-file is plumbing, git show is porcelain.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

      reply	other threads:[~2018-07-02  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  3:06 [PATCH] " Carlos O'Donell
2018-06-27  9:46 ` Florian Weimer
2018-06-28  4:15   ` [PATCH v2] " Carlos O'Donell
2018-06-28 12:13     ` Florian Weimer
2018-06-28 13:07       ` [PATCH v3] " Carlos O'Donell
2018-06-28 13:22         ` Florian Weimer
2018-06-28 13:36           ` [PATCH v4] " Carlos O'Donell
2018-06-28 13:44             ` Florian Weimer
2018-06-28 14:13               ` Carlos O'Donell
2018-06-28 14:15                 ` Florian Weimer
2018-06-28 14:26                   ` Carlos O'Donell
2018-06-28 14:50                     ` Florian Weimer
2018-06-28 19:03                 ` Andreas Schwab
2018-06-28 19:10                   ` Florian Weimer
2018-07-02  8:56                     ` Andreas Schwab [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=mvm36x210ey.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).