Michael Haggerty writes:
> On 02/09/2015 08:05 PM, Stefan Beller wrote:
>> On Mon, Feb 9, 2015 at 10:41 AM, Junio C Hamano wrote:
>>> Michael Haggerty writes:
[...]
This patch series applies on top of master merged together with
sb/atomic-push, which in turn depends on mh/reflog-
On Mon, Feb 9, 2015 at 12:40 PM, Michael Haggerty wrote:
>
>> I am not sure what advantages this would bring. A better history
>> for bisection? I cannot speak for Michael, but my understanding was
>> to have mh/reflog-expire and sb/atomic-push-fix merged now that 2.3
>> is out and everything els
On 02/09/2015 08:05 PM, Stefan Beller wrote:
> On Mon, Feb 9, 2015 at 10:41 AM, Junio C Hamano wrote:
>> Michael Haggerty writes:
>>> [...]
>>> This patch series applies on top of master merged together with
>>> sb/atomic-push, which in turn depends on mh/reflog-expire.
>>
>> I am a bit puzzled b
On Mon, Feb 9, 2015 at 10:41 AM, Junio C Hamano wrote:
> Michael Haggerty writes:
>
>> The main purpose of this series is to simplify the interface to
>> reference transactions as follows:
>>
>> * Remove the need to supply an explicit have_old parameter to
>> ref_transaction_update() and ref_tr
Michael Haggerty writes:
> The main purpose of this series is to simplify the interface to
> reference transactions as follows:
>
> * Remove the need to supply an explicit have_old parameter to
> ref_transaction_update() and ref_transaction_delete(). Instead,
> check the old_sha1 if and only
The main purpose of this series is to simplify the interface to
reference transactions as follows:
* Remove the need to supply an explicit have_old parameter to
ref_transaction_update() and ref_transaction_delete(). Instead,
check the old_sha1 if and only if it is non-NULL.
* Allow NULL to be
6 matches
Mail list logo
