From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>
Subject: Re: What's cooking in git.git (Jul 2015, #05; Mon, 20)
Date: Mon, 20 Jul 2015 22:15:04 -0700 [thread overview]
Message-ID: <xmqqsi8iw0pz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1437439832.30911.12.camel@twopensource.com> (David Turner's message of "Mon, 20 Jul 2015 20:50:32 -0400")
David Turner <dturner@twopensource.com> writes:
>> * 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
>> ...
>> 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.
I think I found the series more or less ready when I saw v7, but
there was a good discussion between Michael Haggerty and you on that
round after I thought so, and then you posted the reroll (v8) which
is what is queued above. As I was not closely following the earlier
exchange, I wanted to hear from Michael if everything is now good
with v8, which hasn't happened as far as I recall.
Also in $gmane/273828 [*1*] you hinted (but without showing a firm
commitment) that there might be a reroll coming, which was another
reason why I wasn't in a hurry to merge v8 iteration down to 'next'.
[Reference]
*1* http://thread.gmane.org/gmane.comp.version-control.git/273786/focus=273828
next prev parent reply other threads:[~2015-07-21 5:15 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
2015-07-21 5:15 ` Junio C Hamano [this message]
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=xmqqsi8iw0pz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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