From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail•com>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas•com>
Subject: Re: linux-next: lots of merges in the sound-asoc tree
Date: Tue, 13 Feb 2018 11:42:10 +0000 [thread overview]
Message-ID: <20180213114210.GA5988@sirena.org.uk> (raw)
In-Reply-To: <20180213093857.2fe78090@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
On Tue, Feb 13, 2018 at 09:38:57AM +1100, Stephen Rothwell wrote:
> I know that you usually like to keep one topic branch per soc and then
> merge them all, but currently your tree seems to only contain a couple
> logical changes (platform to component and codec to component), so
> surely that could have been done in (maybe) 2 topic branches and saved
> large number of very small branches (often a single commit) and a large
> number of merges.
If you look at the changes that are per branch (one series is on a
single branch due to dependencies and a lower change rate) they're often
relatively large and likely to conflict with further development that
gets done. This also lets me drop anything that causes problems much
more easily.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-02-13 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 22:38 linux-next: lots of merges in the sound-asoc tree Stephen Rothwell
2018-02-13 11:42 ` Mark Brown [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=20180213114210.GA5988@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=kuninori.morimoto.gx@renesas$(echo .)com \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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