Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <yann.morin@orange.com>
To: <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin@orange.com>
Subject: [Buildroot] [PATCH 0/5] utils/get-developers: misc cleanups and improvements
Date: Fri, 20 Dec 2024 14:31:00 +0100	[thread overview]
Message-ID: <cover.1734701459.git.yann.morin@orange.com> (raw)

From: "Yann E. MORIN" <yann.morin@orange.com>

Hello All!

This small series brings in a few trivial cleanups and improvements to
get-developers.


Regards,
Yann E. MORIN.


The following changes since commit a0ebdd5cd8318d03693ffa2bfd95b311847bbc1c

  package/cloudflared: bump to version 2024.12.2 (2024-12-20 00:33:23 +0100)


are available as patches in this mail series,

for you to apply patches up to 64f9d09898aee7370ee86df702b207182e6d0cb5

  utils/get-developers: add option to report Cc: lines (2024-12-20 14:28:35 +0100)


----------------------------------------------------------------
Yann E. MORIN (5):
      utils/get-developers: don't offload parse_args()
      utils/get-developers: use parser.error rather than canned print+return
      utils/get-developers: read patch from stdin when it's not a tty
      utils/get-developers: sort reported developers
      utils/get-developers: add option to report Cc: lines

 utils/get-developers | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

--
                                        ____________
.-----------------.--------------------:       _    :------------------.
|  Yann E. MORIN  | Real-Time Embedded |    __/ )   | /"\ ASCII RIBBON |
|                 | Software  Designer |  _/ - /'   | \ / CAMPAIGN     |
| +33 638.411.245 '--------------------: (_    `--, |  X  AGAINST      |
| yann.morin (at) orange.com           |_="    ,--' | / \ HTML MAIL    |
'--------------------------------------:______/_____:------------------'

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-12-20 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 13:31 yann.morin [this message]
2024-12-20 13:30 ` [Buildroot] [PATCH 1/5] utils/get-developers: don't offload parse_args() yann.morin
2024-12-20 13:31 ` [Buildroot] [PATCH 2/5] utils/get-developers: use parser.error rather than canned print+return yann.morin
2024-12-20 21:31   ` Julien Olivain
2024-12-20 13:31 ` [Buildroot] [PATCH 3/5] utils/get-developers: read patch from stdin when it's not a tty yann.morin
2024-12-20 13:31 ` [Buildroot] [PATCH 4/5] utils/get-developers: sort reported developers yann.morin
2024-12-20 13:31 ` [Buildroot] [PATCH 5/5] utils/get-developers: add option to report Cc: lines yann.morin
2024-12-20 21:49   ` Julien Olivain
2024-12-23  7:06     ` yann.morin
  -- strict thread matches above, loose matches on Subject: below --
2024-12-23  7:27 [Buildroot] [PATCH 0/5] utils/get-developers: misc cleanups and improvements yann.morin

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=cover.1734701459.git.yann.morin@orange.com \
    --to=yann.morin@orange.com \
    --cc=buildroot@buildroot.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