How to convert scripts/get_maintainer.pl output as input to mutt or git-send email?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I create a .patch
, then:
scripts/get_maintainer.pl 0001-my-patch.patch
and that gives output of format:
Josh Poimboeuf <jpoimboe@redhat.com> (maintainer:LIVE PATCHING)
Jessica Yu <jeyu@kernel.org> (maintainer:LIVE PATCHING)
linux-kernel@vger.kernel.org (open list:BPF (Safe dynamic programs and tools))
live-patching@vger.kernel.org (open list:LIVE PATCHING)
on Linux v4.17.
Is there any way to feed that output to either mutt
or git send-email
to save some copy paste time?
The help gives a hint at:
Using "--roles" or "--rolestats" with git send-email --cc-cmd or any
other automated tools that expect only ["name"] <email address>
may not work because of additional output after <email address>.
but let's just document it clearly here to save other people some time.
linux-kernel
add a comment |Â
up vote
0
down vote
favorite
I create a .patch
, then:
scripts/get_maintainer.pl 0001-my-patch.patch
and that gives output of format:
Josh Poimboeuf <jpoimboe@redhat.com> (maintainer:LIVE PATCHING)
Jessica Yu <jeyu@kernel.org> (maintainer:LIVE PATCHING)
linux-kernel@vger.kernel.org (open list:BPF (Safe dynamic programs and tools))
live-patching@vger.kernel.org (open list:LIVE PATCHING)
on Linux v4.17.
Is there any way to feed that output to either mutt
or git send-email
to save some copy paste time?
The help gives a hint at:
Using "--roles" or "--rolestats" with git send-email --cc-cmd or any
other automated tools that expect only ["name"] <email address>
may not work because of additional output after <email address>.
but let's just document it clearly here to save other people some time.
linux-kernel
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I create a .patch
, then:
scripts/get_maintainer.pl 0001-my-patch.patch
and that gives output of format:
Josh Poimboeuf <jpoimboe@redhat.com> (maintainer:LIVE PATCHING)
Jessica Yu <jeyu@kernel.org> (maintainer:LIVE PATCHING)
linux-kernel@vger.kernel.org (open list:BPF (Safe dynamic programs and tools))
live-patching@vger.kernel.org (open list:LIVE PATCHING)
on Linux v4.17.
Is there any way to feed that output to either mutt
or git send-email
to save some copy paste time?
The help gives a hint at:
Using "--roles" or "--rolestats" with git send-email --cc-cmd or any
other automated tools that expect only ["name"] <email address>
may not work because of additional output after <email address>.
but let's just document it clearly here to save other people some time.
linux-kernel
I create a .patch
, then:
scripts/get_maintainer.pl 0001-my-patch.patch
and that gives output of format:
Josh Poimboeuf <jpoimboe@redhat.com> (maintainer:LIVE PATCHING)
Jessica Yu <jeyu@kernel.org> (maintainer:LIVE PATCHING)
linux-kernel@vger.kernel.org (open list:BPF (Safe dynamic programs and tools))
live-patching@vger.kernel.org (open list:LIVE PATCHING)
on Linux v4.17.
Is there any way to feed that output to either mutt
or git send-email
to save some copy paste time?
The help gives a hint at:
Using "--roles" or "--rolestats" with git send-email --cc-cmd or any
other automated tools that expect only ["name"] <email address>
may not work because of additional output after <email address>.
but let's just document it clearly here to save other people some time.
linux-kernel
asked Jul 5 at 8:37
Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
3,97613432
3,97613432
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
The kernel documentation suggests doing this manually, using the roles output by get_maintainer.pl
to decide which recipients to include.
However, if you know get_maintainer.pl
does the right thing, you can get it to produce output that will work as input to MUAs or git send-email
by adding the --no-rolestats
and --separator=,
options:
scripts/get_maintainer.pl --separator=, --no-rolestats 0001-my-patch.patch
You can use this in cc-cmd
to fill in carbon copies:
git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, --no-rolestats" 0001-my-patch.patch
but that will strip the mailing lists, and wonâÂÂt help you fill in the main recipients (which should include the maintainers and at least one of the mailing lists). It will still save you some copy-pasting, as requested.
Thanks Stephen, can you also give the fullgit send-email
command as well for completeness?
â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
The kernel documentation suggests doing this manually, using the roles output by get_maintainer.pl
to decide which recipients to include.
However, if you know get_maintainer.pl
does the right thing, you can get it to produce output that will work as input to MUAs or git send-email
by adding the --no-rolestats
and --separator=,
options:
scripts/get_maintainer.pl --separator=, --no-rolestats 0001-my-patch.patch
You can use this in cc-cmd
to fill in carbon copies:
git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, --no-rolestats" 0001-my-patch.patch
but that will strip the mailing lists, and wonâÂÂt help you fill in the main recipients (which should include the maintainers and at least one of the mailing lists). It will still save you some copy-pasting, as requested.
Thanks Stephen, can you also give the fullgit send-email
command as well for completeness?
â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
add a comment |Â
up vote
3
down vote
The kernel documentation suggests doing this manually, using the roles output by get_maintainer.pl
to decide which recipients to include.
However, if you know get_maintainer.pl
does the right thing, you can get it to produce output that will work as input to MUAs or git send-email
by adding the --no-rolestats
and --separator=,
options:
scripts/get_maintainer.pl --separator=, --no-rolestats 0001-my-patch.patch
You can use this in cc-cmd
to fill in carbon copies:
git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, --no-rolestats" 0001-my-patch.patch
but that will strip the mailing lists, and wonâÂÂt help you fill in the main recipients (which should include the maintainers and at least one of the mailing lists). It will still save you some copy-pasting, as requested.
Thanks Stephen, can you also give the fullgit send-email
command as well for completeness?
â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
add a comment |Â
up vote
3
down vote
up vote
3
down vote
The kernel documentation suggests doing this manually, using the roles output by get_maintainer.pl
to decide which recipients to include.
However, if you know get_maintainer.pl
does the right thing, you can get it to produce output that will work as input to MUAs or git send-email
by adding the --no-rolestats
and --separator=,
options:
scripts/get_maintainer.pl --separator=, --no-rolestats 0001-my-patch.patch
You can use this in cc-cmd
to fill in carbon copies:
git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, --no-rolestats" 0001-my-patch.patch
but that will strip the mailing lists, and wonâÂÂt help you fill in the main recipients (which should include the maintainers and at least one of the mailing lists). It will still save you some copy-pasting, as requested.
The kernel documentation suggests doing this manually, using the roles output by get_maintainer.pl
to decide which recipients to include.
However, if you know get_maintainer.pl
does the right thing, you can get it to produce output that will work as input to MUAs or git send-email
by adding the --no-rolestats
and --separator=,
options:
scripts/get_maintainer.pl --separator=, --no-rolestats 0001-my-patch.patch
You can use this in cc-cmd
to fill in carbon copies:
git send-email --cc-cmd="scripts/get_maintainer.pl --separator=, --no-rolestats" 0001-my-patch.patch
but that will strip the mailing lists, and wonâÂÂt help you fill in the main recipients (which should include the maintainers and at least one of the mailing lists). It will still save you some copy-pasting, as requested.
edited Jul 5 at 9:40
answered Jul 5 at 9:00
Stephen Kitt
139k22296359
139k22296359
Thanks Stephen, can you also give the fullgit send-email
command as well for completeness?
â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
add a comment |Â
Thanks Stephen, can you also give the fullgit send-email
command as well for completeness?
â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
Thanks Stephen, can you also give the full
git send-email
command as well for completeness?â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
Thanks Stephen, can you also give the full
git send-email
command as well for completeness?â Ciro Santilli æ°çÂÂæ¹é ä¸Âå¿ å ÂÃ¥ÂÂäºÂ件 æ³Âè½®åÂÂ
Jul 5 at 9:28
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453552%2fhow-to-convert-scripts-get-maintainer-pl-output-as-input-to-mutt-or-git-send-ema%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password