Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot U-boot user patch applying problem
Date: Sat, 19 Nov 2011 16:52:06 +0100	[thread overview]
Message-ID: <8739dkrty1.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <B55DD04487614DE2890707C4FF7B640E@NX5000J> (Jerzy Grzegorek's message of "Sat, 19 Nov 2011 14:17:17 +0100")

>>>>> "Jerzy" == Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net> writes:

 Jerzy> Hi,
 Jerzy> Buildroot U-boot user patch name shoud be formated
 Jerzy> u-boot-<version>-<descryption>.patch
 
 Jerzy> buildroot-2011.11.rc2  patch

You can argue both for u-boot-*.patch and uboot-*.patch (E.G. like the
.mk file is named). By now, people are using the uboot-*.patch
convention, so I won't change it.

Just rename your patches.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2011-11-19 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19 13:17 [Buildroot] Buildroot U-boot user patch applying problem Jerzy Grzegorek
2011-11-19 15:52 ` 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=8739dkrty1.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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