git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shawn wilson <ag4ve.us@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v1.8.3-rc0
Date: Fri, 26 Apr 2013 22:24:07 -0400	[thread overview]
Message-ID: <CAH_OBievcf-_z_AX9UrmWL_HVFT2vSQTu+wXAjAFeQBM8iFSGw@mail.gmail.com> (raw)
In-Reply-To: <7vvc78u8jl.fsf@alter.siamese.dyndns.org>

On Fri, Apr 26, 2013 at 8:22 PM, Junio C Hamano <gitster@pobox.com> wrote:

>  * There was no good way to ask "I have a random string that came from
>    outside world. I want to turn it into a 40-hex object name while
>    making sure such an object exists".  A new peeling suffix ^{object}
>    can be used for that purpose, together with "rev-parse --verify".
>

What does this mean / what is the reason behind this? I can only think
it might be useful in a test suite to make sure git isn't doing
anything stupid with hashes...?

  reply	other threads:[~2013-04-27  2:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27  0:22 [ANNOUNCE] Git v1.8.3-rc0 Junio C Hamano
2013-04-27  2:24 ` shawn wilson [this message]
2013-04-27  5:32   ` Michael Haggerty
2013-04-28 21:12     ` Junio C Hamano
2013-04-27  9:18 ` John Keeping
2013-04-29  3:31   ` Junio C Hamano
2013-04-29 19:15 ` [PATCH] Fix grammar in the 1.8.3 release notes Marc Branchaud
2013-04-29 21:15   ` Junio C Hamano
2013-04-29 21:16     ` Junio C Hamano
2013-04-30 14:28     ` Marc Branchaud
2013-05-01  8:24       ` Lukas Fleischer
2013-05-01 14:06         ` Marc Branchaud
2013-05-01 17:55           ` Junio C Hamano
2013-04-29 21:20   ` Junio C Hamano
2013-04-30  3:09   ` Eric Sunshine
2013-04-30 15:12   ` Phil Hord

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=CAH_OBievcf-_z_AX9UrmWL_HVFT2vSQTu+wXAjAFeQBM8iFSGw@mail.gmail.com \
    --to=ag4ve.us@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).