From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Olof Johansson <olof@lixom.net>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus <torvalds@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org, "Wu,
Josh" <Josh.wu@atmel.com>
Subject: Re: linux-next: manual merge of the v4l-dvb tree with the arm-soc tree
Date: Wed, 11 Jan 2012 16:46:24 +0000 [thread overview]
Message-ID: <201201111646.24731.arnd@arndb.de> (raw)
In-Reply-To: <4F0DB16B.3010302@atmel.com>
On Wednesday 11 January 2012, Nicolas Ferre wrote:
> I am so astonished and sad about all this! I have the feeling of having
> done exactly what Guennadi and Olof had asked me to do: What I get at
> the end: people having a bad feeling about my work, not expected merge
> conflicts which annoy everybody (only for a ridiculous amount of code),
> my patches delayed and a comment saying that I cannot handle simple
> dependency...
> Nice result!
I'm sorry for accusing you, you are right. You did exactly what was
agreed on in the mail thread, I just reread the history.
My impression is that Guennadi simply didn't know what he was doing
when he sent you a patch based on a branch that was clearly not
stable.
> - Guennadi did not want to take SoC/board code in his tree
> => I had to take those lines of code through at91/arm-soc breaking the
> patch series and allowing the introduction of an out-of-sync merge
This was probably the first mistake. It would have been trivial
to handle all this if we had just stuck the same commit into both
trees.
> I have understood and approved all the reasons for the requested
> changes, of course. But for which gain?
>
> Ok... well, it looks like a massive incomprehension which took us time
> and ends up by wastefulness.
Agreed. How about if you rebase the few other (non-ISI) patches that
I had in arm-soc onto v3.2 and send me an updated pull request so
I can send them on? There's no reason to hold them up.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the v4l-dvb tree with the arm-soc tree
Date: Wed, 11 Jan 2012 16:46:24 +0000 [thread overview]
Message-ID: <201201111646.24731.arnd@arndb.de> (raw)
In-Reply-To: <4F0DB16B.3010302@atmel.com>
On Wednesday 11 January 2012, Nicolas Ferre wrote:
> I am so astonished and sad about all this! I have the feeling of having
> done exactly what Guennadi and Olof had asked me to do: What I get at
> the end: people having a bad feeling about my work, not expected merge
> conflicts which annoy everybody (only for a ridiculous amount of code),
> my patches delayed and a comment saying that I cannot handle simple
> dependency...
> Nice result!
I'm sorry for accusing you, you are right. You did exactly what was
agreed on in the mail thread, I just reread the history.
My impression is that Guennadi simply didn't know what he was doing
when he sent you a patch based on a branch that was clearly not
stable.
> - Guennadi did not want to take SoC/board code in his tree
> => I had to take those lines of code through at91/arm-soc breaking the
> patch series and allowing the introduction of an out-of-sync merge
This was probably the first mistake. It would have been trivial
to handle all this if we had just stuck the same commit into both
trees.
> I have understood and approved all the reasons for the requested
> changes, of course. But for which gain?
>
> Ok... well, it looks like a massive incomprehension which took us time
> and ends up by wastefulness.
Agreed. How about if you rebase the few other (non-ISI) patches that
I had in arm-soc onto v3.2 and send me an updated pull request so
I can send them on? There's no reason to hold them up.
Arnd
next prev parent reply other threads:[~2012-01-11 16:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 2:31 linux-next: manual merge of the v4l-dvb tree with the arm-soc tree Stephen Rothwell
2012-01-11 2:31 ` Stephen Rothwell
2012-01-11 2:31 ` Stephen Rothwell
2012-01-11 5:08 ` Olof Johansson
2012-01-11 5:08 ` Olof Johansson
2012-01-11 8:36 ` Guennadi Liakhovetski
2012-01-11 8:36 ` Guennadi Liakhovetski
2012-01-11 10:35 ` Mauro Carvalho Chehab
2012-01-11 10:35 ` Mauro Carvalho Chehab
2012-01-11 14:50 ` Arnd Bergmann
2012-01-11 14:50 ` Arnd Bergmann
2012-01-11 15:09 ` Olof Johansson
2012-01-11 15:09 ` Olof Johansson
2012-01-11 15:57 ` Nicolas Ferre
2012-01-11 15:57 ` Nicolas Ferre
2012-01-11 16:44 ` Olof Johansson
2012-01-11 16:44 ` Olof Johansson
2012-01-11 20:47 ` Mauro Carvalho Chehab
2012-01-11 20:47 ` Mauro Carvalho Chehab
2012-01-11 16:46 ` Arnd Bergmann [this message]
2012-01-11 16:46 ` Arnd Bergmann
2012-01-11 16:58 ` Olof Johansson
2012-01-11 16:58 ` Olof Johansson
2012-01-11 17:56 ` Guennadi Liakhovetski
2012-01-11 17:56 ` Guennadi Liakhovetski
2012-01-12 11:42 ` [GIT PULL v3] at91: devices and boards files update for 3.3 Nicolas Ferre
-- strict thread matches above, loose matches on Subject: below --
2014-11-24 2:22 linux-next: manual merge of the v4l-dvb tree with the arm-soc tree Stephen Rothwell
2014-11-24 2:22 ` Stephen Rothwell
2014-11-24 2:22 ` Stephen Rothwell
2014-11-24 15:28 ` Tony Lindgren
2014-11-24 15:28 ` Tony Lindgren
2014-12-01 2:52 Stephen Rothwell
2014-12-01 2:52 ` Stephen Rothwell
2014-12-01 2:52 ` Stephen Rothwell
2014-12-05 3:03 Stephen Rothwell
2014-12-05 3:03 ` Stephen Rothwell
2014-12-05 3:03 ` Stephen Rothwell
2015-12-02 13:36 Mark Brown
2015-12-02 13:36 ` Mark Brown
2017-08-22 0:55 Stephen Rothwell
2017-08-22 0:55 ` Stephen Rothwell
2017-09-04 5:23 ` Stephen Rothwell
2017-09-04 5:23 ` Stephen Rothwell
2020-12-08 0:04 Stephen Rothwell
2020-12-08 0:04 ` Stephen Rothwell
2020-12-14 20:30 ` Stephen Rothwell
2020-12-14 20:30 ` Stephen Rothwell
2020-12-14 21:05 ` Mauro Carvalho Chehab
2020-12-14 21:05 ` Mauro Carvalho Chehab
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=201201111646.24731.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Josh.wu@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.