emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#60218: closed ([PATCH 0/2] New teams.scm 'get-maintainer' command (f


From: GNU bug Tracking System
Subject: bug#60218: closed ([PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman))
Date: Wed, 28 Dec 2022 20:43:02 +0000

Your message dated Wed, 28 Dec 2022 15:42:03 -0500
with message-id <87a6375kh0.fsf@gmail.com>
and subject line Re: bug#60218: [PATCH 0/2] New teams.scm 'get-maintainer' 
command (for integration with patman)
has caused the debbugs.gnu.org bug report #60218,
regarding [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration 
with patman)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60218: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60218
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman) Date: Tue, 20 Dec 2022 08:58:10 -0500
Along with the correct '.patman' configuration file for Guix, this makes it
possible to invoke the 'patman' command and have it add all the required
'--cc' directives, as computed by 'etc/teams.scm get-maintainers
<patch-file>'.


Maxim Cournoyer (2):
  teams: Add a "get-maintainer" command.
  .patman: New configuration file.

 .patman          |  9 +++++++++
 etc/teams.scm.in | 21 ++++++++++++++++++++-
 2 files changed, 29 insertions(+), 1 deletion(-)
 create mode 100644 .patman


base-commit: f28ca2447c5e2eef1ba6a3a11587380a665b0e26
-- 
2.38.1




--- End Message ---
--- Begin Message --- Subject: Re: bug#60218: [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman) Date: Wed, 28 Dec 2022 15:42:03 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Hi Mathieu,

Mathieu Othacehe <othacehe@gnu.org> writes:

> Hey,
>
>> Implemented in v2!  I guess it could be useful.  Note that it doesn't
>> parse the patch for the file names touched, instead it assumes the patch
>> was produced from a commit registered in git and then use the usual code
>> path (for simplicity).
>
> Nice! I think that it is fair to assume that the commit is registered in
> the local git repository.
>
> As a follow-up a documentation update could also be interesting as I
> think that the new 'cc-members patch' command is easier to use that the
> 'cc-member start end' variant.

OK!  I intend to document the use of patman along teams.scm, as I find
it helps automate things and keep submissions organized.  We can
probably briefly mention the tool, and point the interested user to its
full doc (which lives in u-boot-documentation).

> I had a look to the rest of the patchset it seems fine to me :)

OK, great!  I've now pushed the series.  Happy New Year!

-- 
Thanks,
Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]