All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #02; Fri, 8)
Date: Sat, 09 Jan 2021 13:28:58 -0800	[thread overview]
Message-ID: <xmqqk0slg5ph.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <871reu752k.fsf@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sat, 09 Jan 2021 11:55:15 +0100")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

>> * ab/trailers-extra-format (2020-12-09) 5 commits
>>  ...
>>
>>  The "--format=%(trailers)" mechanism gets enhanced to make it
>>  easier to design output for machine consumption.
>
> Thanks! Am refactoring some out-of-tree code to take advantage of this
> :)

Thank you for interesting additions.

> I forgot that, oops. Is just declaring here that all of that's:
>
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
>
> Since you have some acks etc. squashed into it at this point...

Puzzlled.  The patches on the trailers topic were all signed-off by
you, unless I was careless when I checked before merging them to
'next'.

Do the above three lines refer to a different topic, on CoC 2.0?


>> * bc/hashed-mailmap (2020-12-12) 1 commit
>>  - mailmap: support hashed entries in mailmaps
>>
>>  The mailmap database learned to take hashed value as the original
>>  side of mapping.
>>
>>  Expecting a reroll.
>
> FWIW there was since a re-roll on 2021-01-03, but the discussion is
> sort-of outstanding, so maybe that's intentional...

I had an impression that those 4 or 5 patches haven't gained
concensus that they are good as-is.

Thanks.

  reply	other threads:[~2021-01-09 21:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 19:22 What's cooking in git.git (Jan 2021, #02; Fri, 8) Junio C Hamano
2021-01-09 10:55 ` Ævar Arnfjörð Bjarmason
2021-01-09 21:28   ` Junio C Hamano [this message]
2021-01-09 22:05     ` brian m. carlson
2021-01-09 23:20       ` Junio C Hamano
2021-01-11  1:53         ` brian m. carlson
2021-01-11 19:04           ` Junio C Hamano
2021-01-12 14:00             ` Ævar Arnfjörð Bjarmason
2021-01-14 23:52               ` Emily Shaffer
2021-01-14 23:56                 ` Emily Shaffer
2021-01-15  7:22                   ` Junio C Hamano
2021-01-15  0:29                 ` brian m. carlson
2021-01-15  1:44                 ` Junio C Hamano
2021-01-16 16:23                 ` Ævar Arnfjörð Bjarmason
2021-01-17 17:15                   ` Jeff King
2021-01-17 20:22                     ` Ævar Arnfjörð Bjarmason
2021-01-10 19:00     ` Ævar Arnfjörð Bjarmason
2021-01-11  0:21       ` Junio C Hamano
2021-01-09 21:38 ` David Aguilar
2021-01-09 23:08   ` Junio C Hamano
2021-01-14 23:06 ` Emily Shaffer
2021-01-15  1:50   ` Junio C Hamano
2021-01-15  2:24     ` Taylor Blau
2021-01-15  2:44       ` Taylor Blau
2021-01-15  2:36   ` Derrick Stolee
2021-01-15  2:54     ` Derrick Stolee
2021-01-15  6:36     ` Junio C Hamano
2021-01-15  6:38       ` Junio C Hamano
2021-01-15 11:36         ` Derrick Stolee
2021-01-15 19:44           ` Junio C Hamano
2021-01-15 20:08             ` Emily Shaffer
2021-01-15 20:59               ` Junio C Hamano
2021-01-15 19:52 ` Jeff King
2021-01-15 21:40   ` 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=xmqqk0slg5ph.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.