On Sat, Oct 10, 2015 at 7:36 PM, Christian Couder
wrote:
> A draft of Git Rev News edition 8 is available here:
> https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-8.md
Does Karsten's comprehensive post[1] about nanosecond-related racy
detection problems merit mention?
[1]
Hi,
A draft of Git Rev News edition 8 is available here:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-8.md
Everyone is welcome to contribute in any section either by editing the
above page on GitHub and sending a pull request, or by commenting on
this GitHub issue:
h
On Fri, Oct 9, 2015 at 12:10 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> --- a/ref-filter.c
>> +++ b/ref-filter.c
>> @@ -1118,8 +1118,10 @@ static void populate_value(struct ref_array_item *ref)
>> char buf[40];
>>
>> if (stat_t
On Fri, Oct 9, 2015 at 12:31 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> Copy the implementation of get_head_description() from branch.c. This
>> gives a description of the HEAD ref if called. This is used as the
>> refname for the HEAD ref whenever the FILTER_REFS_DETACHED_HEAD option
On Fri, Oct 9, 2015 at 12:28 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> --- a/ref-filter.c
>> +++ b/ref-filter.c
>> @@ -464,14 +464,28 @@ static void *get_obj(const unsigned char *sha1, struct
>> object **obj, unsigned lo
>> static int grab_objectname(const char *name, const unsigned
On Fri, Oct 9, 2015 at 12:21 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> @@ -309,11 +319,19 @@ static void then_atom_handler(struct atom_value
>> *atomv, struct ref_formatting_st
>> if (if_then_else->then_atom)
>> die(_("format: %%(then) atom used more than once"));
On Fri, Oct 9, 2015 at 12:49 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> --- a/Documentation/git-for-each-ref.txt
>> +++ b/Documentation/git-for-each-ref.txt
>> @@ -134,9 +134,17 @@ align::
>> `` is either left, right or middle, default being
>> left and `` is the total lengt
I noticed that git-credential-cache--daemon quits on SIGHUP. This
seems like surprising behaviour for a daemon. Would it be acceptable
to change it to ignore SIGHUP?
(This came up while investigating a Magit bug[1], we are also
considering ways to avoid sending a SIGHUP in the first place)
[1]: h
On Fri, Oct 9, 2015 at 12:18 AM, Matthieu Moy
wrote:
> Karthik Nayak writes:
>
>> +static void if_then_else_handler(struct ref_formatting_stack **stack)
>> +{
>> + struct ref_formatting_stack *cur = *stack;
>> + struct ref_formatting_stack *prev = cur->prev;
>> + struct if_then_else *
On 09.10.15 12:11, Johannes Schindelin wrote:
> Me again,
>
> On 2015-10-09 11:50, Johannes Schindelin wrote:
>>
>> On 2015-10-09 03:40, Paul Tan wrote:
>>> On Fri, Oct 9, 2015 at 8:52 AM, Junio C Hamano wrote:
Johannes Schindelin writes:
> Brendan Forster noticed that we no longer
10 matches
Mail list logo