From: Christian Couder <christian.couder@gmail.com>
To: Kousik Sanagavarapu <five231003@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC][PATCH 0/2] Add new "signature" atom
Date: Thu, 1 Jun 2023 11:11:14 +0200 [thread overview]
Message-ID: <CAP8UFD1JDQ=A8T_MYCG2yRDvZBjN0iDSLE69mxb7deGRupbpKg@mail.gmail.com> (raw)
In-Reply-To: <20230529192209.17747-1-five231003@gmail.com>
On Mon, May 29, 2023 at 9:50 PM Kousik Sanagavarapu
<five231003@gmail.com> wrote:
> PATCH 1/2 introduces a new prereq GPG2 for the purpose of testing stuff
> that breaks with GPG version <= v2. This is evident from the CI failure
> in [1] that was sent with the same subject as this series (more info
> below).
>
> PATCH 2/2 adds a new "signature" atom, which is a duplication of the %G*
> formats in pretty. This was sent before by Nsengiyumva Wilberforce and
> was in "seen" until May and was removed because of CI failure. I have
> built upon it and have done some minor changes to it. The CI jobs are
> now successful which can be found at [2].
>
> [1]: Patch
>
> https://lore.kernel.org/git/20230311210607.64927-1-nsengiyumvawilberforce@gmail.com/
I don't think it's a big issue, but, as there are only minor change,
it might have been easier to refer to the previous work by just
calling this a v6 of the same patch series and using the
--in-reply-to=<message id> option of git format-patch to send it so it
would be in the same email thread as the previous work.
Now that a new series was started though, I think it makes more sense
for any improvement to this series to just be called v2 and be sent
using --in-reply-to=<message id> so that it is in the same thread as
this series.
Thanks!
next prev parent reply other threads:[~2023-06-01 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 18:32 [GSoC][PATCH 0/2] Add new "signature" atom Kousik Sanagavarapu
2023-05-29 18:32 ` [PATCH 1/2] t/lib-gpg: introduce new prereq GPG2 Kousik Sanagavarapu
2023-06-01 8:39 ` Christian Couder
2023-05-29 18:32 ` [PATCH 2/2] ref-filter: add new "signature" atom Kousik Sanagavarapu
2023-06-01 8:58 ` Christian Couder
2023-06-01 9:11 ` Christian Couder [this message]
2023-06-02 2:11 ` [PATCH v2 0/2] Add " Kousik Sanagavarapu
2023-06-02 2:11 ` [PATCH v2 1/2] t/lib-gpg: introduce new prereq GPG2 Kousik Sanagavarapu
2023-06-02 6:50 ` Christian Couder
2023-06-02 12:58 ` Kousik Sanagavarapu
2023-06-02 2:11 ` [PATCH v2 2/2] ref-filter: add new "signature" atom Kousik Sanagavarapu
2023-06-02 8:23 ` Oswald Buddenhagen
2023-06-02 7:29 ` [PATCH v2 0/2] Add " Junio C Hamano
2023-06-02 7:51 ` Eric Sunshine
2023-06-03 0:16 ` Junio C Hamano
2023-06-02 13:13 ` Kousik Sanagavarapu
2023-06-04 18:22 ` [PATCH v3 " Kousik Sanagavarapu
2023-06-04 18:22 ` [PATCH v3 1/2] t/lib-gpg: introduce new prereq GPG2 Kousik Sanagavarapu
2023-06-04 18:22 ` [PATCH v3 2/2] ref-filter: add new "signature" atom Kousik Sanagavarapu
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='CAP8UFD1JDQ=A8T_MYCG2yRDvZBjN0iDSLE69mxb7deGRupbpKg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=five231003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).