Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to apply a patch for the buildroot makedevs tool
Date: Mon, 19 Apr 2021 19:04:31 +0200	[thread overview]
Message-ID: <20210419170431.GA298901@scaer> (raw)
In-Reply-To: <AM6PR05MB59287FC07838F6A013DC9C9DA3499@AM6PR05MB5928.eurprd05.prod.outlook.com>

Ivan, All,

On 2021-04-19 05:58 +0000, Ivan Castell spake thusly:
> Please, proceed applying the patch, of course!

Can you please send the patch with:
  - a proper commit title
  - a proper commit log
  - your signed-off-by line

And then use 'git send-email' to actually send the patch.

See the manual for extensive explanations on how to send a patch:
    https://buildroot.org/downloads/manual/manual.html#submitting-patches

See also the actual 'git log' for examples pertaining to makedevs:

    git log package/makedevs/makedevs.c

Commit bdbbc72934bc7 (makedevs: support optional files) is a good
example: it also adds a new feature to makedevs, so you can model your
commit log after that one for example.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2021-04-19 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  6:58 [Buildroot] Unable to apply a patch for the buildroot makedevs tool Ivan Castell
2021-04-16 22:14 ` Peter Seiderer
2021-04-17  7:13 ` Yann E. MORIN
2021-04-19  5:58   ` Ivan Castell
2021-04-19 17:04     ` Yann E. MORIN [this message]
2021-04-26 21:48   ` Peter Korsgaard

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=20210419170431.GA298901@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox