From: Peter Korsgaard <peter@korsgaard.com>
To: Daniel Lang <dalang@gmx.at>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] utils/getdeveloperlib.py: handle file removal
Date: Fri, 15 Sep 2023 19:51:03 +0200 [thread overview]
Message-ID: <871qezuxyw.fsf@48ers.dk> (raw)
In-Reply-To: <20230911035944.52216-2-dalang@gmx.at> (Daniel Lang's message of "Mon, 11 Sep 2023 05:59:44 +0200")
>>>>> "Daniel" == Daniel Lang <dalang@gmx.at> writes:
> If a patch only removes files, it is ignored. Meaning, that the
> registered developer isn't automatically picked up when calling
> get-developer.
> Fix this by also checking if the line starts with ---, as a patch
> removing a file has a line starting with --- with the name of the
> removed file and one started with +++ /dev/null.
> A set is used to store the changed files, which doesn't allow
> duplicates. Therefore normal patches aren't affected by this change.
> Signed-off-by: Daniel Lang <dalang@gmx.at>
Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-15 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 3:59 [Buildroot] [PATCH] utils/getdeveloperlib.py: handle file removal Daniel Lang
2023-09-15 17:51 ` Peter Korsgaard [this message]
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=871qezuxyw.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=dalang@gmx.at \
/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