On 07/09/2015 03:50 PM, David Turner wrote:
> 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
> files in $GIT_DIR. So this re-roll of the refs backend preamble
> doesn't do anything to pseudorefs. It ju
On Fri, 2015-07-10 at 15:34 +0100, Philip Oakley wrote:
> From: "David Turner"
> > 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
From: "David Turner"
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, t
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
files in $GIT_DIR. So this re-roll of the refs backend preamble
doesn't do anything to pseudorefs. It just does reflog stuff.
In addition, this version rem
4 matches
Mail list logo