git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: jk/unused-annotation + ab/unused-annotation
Date: Wed, 31 Aug 2022 19:21:18 +0200	[thread overview]
Message-ID: <220831.86tu5s8h1a.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqr10wgz64.fsf@gitster.g>


On Wed, Aug 31 2022, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
>
>> Yeah, I think we should use the deprecated attribute. Since the original
>> has been reverted, I think the next step would be for me to fix up the
>> patches to use that approach from the start, and re-submit.
>>
>> I was dragging my feet a little hoping that we might get some coccinelle
>> parsing miracle in the interim.
>
> Yup, that was why I ignored the "deprecated" one when I dealt with
> the replacement series yesterday.

Ah, even if that's the case we'd need to start requiring bleeding-edge
spatch, which doesn't seem practical to me, and would reduce the
audience for our rules.

Or we'd need to split off the "bleeding edge" rules, or something...


  reply	other threads:[~2022-08-31 17:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 19:17 What's cooking in git.git (Aug 2022, #10; Tue, 30) Junio C Hamano
2022-08-30 20:40 ` js/bisect-in-c, was " Johannes Schindelin
2022-08-31  8:00 ` jk/unused-annotation + ab/unused-annotation (was: What's cooking in git.git (Aug 2022, #10; Tue, 30)) Ævar Arnfjörð Bjarmason
2022-08-31 15:27   ` Jeff King
2022-08-31 16:23     ` jk/unused-annotation + ab/unused-annotation Junio C Hamano
2022-08-31 17:21       ` Ævar Arnfjörð Bjarmason [this message]
2022-08-31  8:29 ` js/add-p-diff-parsing-fix (was: What's cooking in git.git (Aug 2022, #10; Tue, 30)) Ævar Arnfjörð Bjarmason
2022-08-31  9:31   ` Phillip Wood
2022-08-31 19:54     ` Johannes Schindelin
2022-08-31 20:15       ` js/add-p-diff-parsing-fix 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=220831.86tu5s8h1a.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).