Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nasser Afshin <afshin.nasser@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] test-pkg: Use the correct config prefix when merging
Date: Wed, 14 Nov 2018 12:25:27 +0330	[thread overview]
Message-ID: <20181114085527.GB12239@smart-All-Series> (raw)
In-Reply-To: <20181114082951.GA4886@dell5510>

Dear Petr,
On Wed, Nov 14, 2018 at 09:29:52AM +0100, Petr Vorel wrote:
> Hi Nasser,
> 
> agree with Arnout. + one more tip: increase version each time you send it,
> even it's just a tiny change.
> 
> Kind regards,
> Petr
Thank you for your tip. Yes, you are right, I forgot to do so.
Kind regards,
Nasser

  reply	other threads:[~2018-11-14  8:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  7:11 [Buildroot] [PATCH v3 0/3] Fix merging configuration fragments Nasser Afshin
2018-11-14  7:11 ` [Buildroot] [PATCH v3 1/3] merge_config.sh: Fix merging buildroot config files Nasser Afshin
2018-11-23 21:14   ` Yann E. MORIN
2018-11-24  9:12   ` Thomas Petazzoni
2018-11-14  7:11 ` [Buildroot] [PATCH v3 2/3] test-pkg: Use the correct config prefix when merging Nasser Afshin
2018-11-14  7:17   ` Petr Vorel
2018-11-14  7:49     ` Nasser Afshin
2018-11-14  8:24       ` Arnout Vandecappelle
2018-11-14  8:29         ` Petr Vorel
2018-11-14  8:55           ` Nasser Afshin [this message]
2018-11-14  9:04         ` Nasser Afshin
2018-11-14  7:11 ` [Buildroot] [PATCH v3 3/3] merge_config.sh: Avoid false positive matches from comment lines Nasser Afshin
2018-11-23 21:16   ` Yann E. MORIN
2018-11-24  9:12   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2018-11-05  8:35 [Buildroot] [PATCH] merge_config.sh: Fix merging buildroot config files Petr Vorel
2018-11-13 13:44 ` [Buildroot] [PATCH v3 0/3] Fix merging configuration fragments Nasser Afshin
2018-11-13 13:44   ` [Buildroot] [PATCH v3 2/3] test-pkg: Use the correct config prefix when merging Nasser Afshin
2018-11-13 18:26     ` Petr Vorel

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=20181114085527.GB12239@smart-All-Series \
    --to=afshin.nasser@gmail.com \
    --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