All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Miriam R." <mirucam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH v4 0/7] Finish converting git bisect to C part 3
Date: Tue, 26 Jan 2021 14:32:29 -0800	[thread overview]
Message-ID: <xmqqv9bjz5vm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CAPc5daWO8JT1p0xhBtNyAjvy1hzjt3s-ho7LCPxEe-E_y8-a-w@mail.gmail.com> (Junio C. Hamano's message of "Tue, 26 Jan 2021 12:05:09 -0800")

Junio C Hamano <gitster@pobox.com> writes:

>> > Did we lose [2/7] somewhere in the mailing list?  I see the same
>> > thing as what is shown in
>> >
>> > https://lore.kernel.org/git/20210125191710.45161-1-mirucam@gmail.com/
>> >
>> > i.e. a 7-patch series that lack its second part.
>>
>> I received the [2/7] patch:
>>
>> -------------------------------------------
>> De: Miriam Rubio <mirucam@gmail.com>
>> Date: lun, 25 ene 2021 a las 20:17
>> Subject: [PATCH v4 2/7] bisect--helper: reimplement `bisect_replay`
>> shell function in C
>> To: <git@vger.kernel.org>
>> Cc: Pranit Bauva <pranit.bauva@gmail.com>, Lars Schneider
>> <larsxschneider@gmail.com>, Christian Couder
>> <chriscool@tuxfamily.org>, Johannes Schindelin
>> <Johannes.Schindelin@gmx.de>, Tanushree Tumane
>> <tanushreetumane@gmail.com>, Miriam Rubio <mirucam@gmail.com>
>
> It does not count---you are on the direct path of the message
> and are not relying on the list to relay it back to you.
>
> It seems that today's one of those days that the mailing list is
> hiccupping. The message I am responding to, which is sent both
> to the list and directly to me, hasn't appeared either on the public-inbox
> or the lore list archive, either.
>
> Hopefully we'll see all 7 messages eventually ;-).

Now I am seeing it on the lore NNTP server (so presumably it has
been relayed to list subscribers).


  reply	other threads:[~2021-01-27 13:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 19:17 [PATCH v4 0/7] Finish converting git bisect to C part 3 Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 1/7] bisect--helper: reimplement `bisect_log` shell function in C Miriam Rubio
2021-01-30  1:46   ` Đoàn Trần Công Danh
2021-01-30  9:49     ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 2/7] bisect--helper: reimplement `bisect_replay` " Miriam Rubio
2021-01-29  7:51   ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 3/7] bisect--helper: retire `--bisect-write` subcommand Miriam Rubio
2021-01-29  7:54   ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 4/7] bisect--helper: use `res` instead of return in BISECT_RESET case option Miriam Rubio
2021-01-29  7:57   ` Christian Couder
2021-01-25 19:17 ` [PATCH v4 5/7] bisect--helper: retire `--bisect-auto-next` subcommand Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 6/7] bisect--helper: reimplement `bisect_skip` shell function in C Miriam Rubio
2021-01-25 19:17 ` [PATCH v4 7/7] bisect--helper: retire `--check-and-set-terms` subcommand Miriam Rubio
2021-01-29  0:49   ` Junio C Hamano
2021-01-26 17:55 ` [PATCH v4 0/7] Finish converting git bisect to C part 3 Junio C Hamano
2021-01-26 18:27   ` Miriam R.
2021-01-26 20:05     ` Junio C Hamano
2021-01-26 22:32       ` Junio C Hamano [this message]
2021-01-27 14:12         ` Miriam R.

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=xmqqv9bjz5vm.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mirucam@gmail.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 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.