From: David Turner <dturner@twopensource.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: git@vger.kernel.org, mhagger@alum.mit.edu, j6t@kdbg.org
Subject: Re: [PATCH v8 0/7] ref backend preamble
Date: Fri, 10 Jul 2015 13:51:13 -0400 [thread overview]
Message-ID: <1436550673.4542.66.camel@twopensource.com> (raw)
In-Reply-To: <8C71190FFE324B1599E89376429C8F84@PhilipOakley>
On Fri, 2015-07-10 at 15:34 +0100, Philip Oakley wrote:
> From: "David Turner" <dturner@twopensource.com>
> > The current state of the discussion on alternate ref backends is that
> > we're going to continue to store pseudorefs (e.g. CHERRY_PICK_HEAD) as
>
> Assuming this is accepted, should the definition of pseudorefs be
> included in the gitglossary?
>
> Once ref backends become common, the distinction will needed in the
> docs.
This term is only in this message (that is, I don't think I used it in
any commit messages yet). The code uses it in at least one place
already. But yes, I think if we decided to go with the pseudoref
concept, we should document it.
next prev parent reply other threads:[~2015-07-10 17:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 22:50 [PATCH v8 0/7] ref backend preamble David Turner
2015-07-09 22:50 ` [PATCH v8 1/7] refs.c: add err arguments to reflog functions David Turner
2015-07-21 13:17 ` Michael Haggerty
2015-07-09 22:50 ` [PATCH v8 2/7] refs: Break out check for reflog autocreation David Turner
2015-07-09 22:50 ` [PATCH v8 3/7] refs: new public ref function: safe_create_reflog David Turner
2015-07-09 22:50 ` [PATCH v8 4/7] git-reflog: add exists command David Turner
2015-07-21 13:27 ` Michael Haggerty
2015-07-09 22:50 ` [PATCH v8 5/7] refs: add REF_FORCE_CREATE_REFLOG flag David Turner
2015-07-09 22:50 ` [PATCH v8 6/7] update-ref and tag: add --create-reflog arg David Turner
2015-07-21 13:46 ` Michael Haggerty
2015-07-09 22:51 ` [PATCH v8 7/7] git-stash: use update-ref --create-reflog instead of creating files David Turner
2015-07-10 14:34 ` [PATCH v8 0/7] ref backend preamble Philip Oakley
2015-07-10 17:51 ` David Turner [this message]
2015-07-21 14:02 ` Michael Haggerty
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=1436550673.4542.66.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=mhagger@alum.mit.edu \
--cc=philipoakley@iee.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 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.