From: David Turner <dturner@twopensource.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2015, #05; Mon, 20)
Date: Mon, 20 Jul 2015 20:50:32 -0400 [thread overview]
Message-ID: <1437439832.30911.12.camel@twopensource.com> (raw)
In-Reply-To: <xmqqwpxuwh8d.fsf@gitster.dls.corp.google.com>
> * dt/refs-backend-preamble (2015-07-13) 7 commits
> - git-stash: use update-ref --create-reflog instead of creating files
> - update-ref and tag: add --create-reflog arg
> - refs: add REF_FORCE_CREATE_REFLOG flag
> - git-reflog: add exists command
> - refs: new public ref function: safe_create_reflog
> - refs: Break out check for reflog autocreation
> - refs.c: add err arguments to reflog functions
>
> In preparation for allowing different "backends" to store the refs
> in a way different from the traditional "one ref per file in $GIT_DIR
> or in a $GIT_DIR/packed-refs file" filesystem storage, reduce
> direct filesystem access to ref-like things like CHERRY_PICK_HEAD
> from scripts and programs.
>
> Still under discussion.
>
> Will hold.
What's left to discuss on this one? I think the latest version addresses
all concerns, but I'm happy to do another reroll or discuss further if
necessary.
next prev parent reply other threads:[~2015-07-21 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 23:18 What's cooking in git.git (Jul 2015, #05; Mon, 20) Junio C Hamano
2015-07-21 0:50 ` David Turner [this message]
2015-07-21 5:15 ` Junio C Hamano
2015-07-21 16:36 ` David Turner
2015-07-21 18:56 ` Jakub Narębski
2015-07-21 19:41 ` Junio C Hamano
2015-07-21 19:42 ` 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=1437439832.30911.12.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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