From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] Makefile: fix rootfs overlay with BR2_ROOTFS_MERGED_USR enabled
Date: Sun, 15 May 2016 15:42:53 +0200 [thread overview]
Message-ID: <20160515154253.3f1cba23@free-electrons.com> (raw)
In-Reply-To: <a49b8176-f38e-5ce0-b088-6ff7bd03310e@mind.be>
Hello,
On Sat, 14 May 2016 23:20:01 +0200, Arnout Vandecappelle wrote:
> > Yes I know it is not necessary...., but I find it supportive for my 'workflow',
> > having local copies of the sent patches combined e.g.
> >
> > v1-0001-some-patch-subject.patch
> > v2-0001-some-patch-subject.patch
> > ....
> >
> > instead of
> >
> > 0001-some-patch-subject.patch
> > v2-0001-some-patch-subject.patch
> >
> > But I can try to change my habit in case more mailing list people prefer it otherwise...
>
> It certainly doesn't bother me, and I doubt that interferes with Peter's or
> Thomas's workflow too. So unless they object a second time, just keep on doing
> what works for you.
It doesn't matter at all for me, I'm fine with seeing "v1" for the
first version.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-15 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 19:18 [Buildroot] [PATCH v1] Makefile: fix rootfs overlay with BR2_ROOTFS_MERGED_USR enabled Peter Seiderer
2016-05-08 14:13 ` Yann E. MORIN
2016-05-12 19:06 ` Peter Seiderer
2016-05-14 21:20 ` Arnout Vandecappelle
2016-05-15 13:42 ` Thomas Petazzoni [this message]
2016-05-15 20:21 ` Peter Korsgaard
2016-05-13 20:07 ` Thomas Petazzoni
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=20160515154253.3f1cba23@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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