git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Victoria Dye via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  ps@pks.im,  Victoria Dye <vdye@github.com>
Subject: Re: [PATCH] glossary: add definitions for dereference & peel
Date: Fri, 10 Nov 2023 14:20:04 +0900	[thread overview]
Message-ID: <xmqqa5rmw5ff.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1qcyxxri.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 10 Nov 2023 09:22:41 +0900")

Junio C Hamano <gitster@pobox.com> writes:

> I've never seen "peel" used for commits, though.  So another
> improvement might be to say "peel" is "an act of dereferencing a
> tag" here.

I am reasonably sure I was the one who coined the term "peel", and
the picture I had in mind when I used it was to peel an onion, which
inherently was about unwrapping many levels repeatedly.  I think
that is why it felt strange to see "peel" used in the context of
using a commit as a tree-ish, which (as your documentation update
clearly said) is doable only once.


  reply	other threads:[~2023-11-10  6:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 23:57 [PATCH] glossary: add definitions for dereference & peel Victoria Dye via GitGitGadget
2023-11-10  0:22 ` Junio C Hamano
2023-11-10  5:20   ` Junio C Hamano [this message]
2023-11-10  8:28 ` Kristoffer Haugsbakk
2023-11-13 23:17 ` [PATCH v2] " Victoria Dye via GitGitGadget
2023-11-14  4:49   ` Junio C Hamano

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=xmqqa5rmw5ff.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=ps@pks.im \
    --cc=vdye@github.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 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).