From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <50F69A90.6030107@siemens.com>
Date: Wed, 16 Jan 2013 13:18:24 +0100
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <50F19CE1.5080106@zultron.com> <50F19DE4.4030805@xenomai.org>
	<50F239E1.40400@zultron.com> <50F2A59D.5050600@xenomai.org>
	<50F30781.3050302@zultron.com> <50F30DE5.7030007@xenomai.org>
	<50F3F36A.8050804@siemens.com> <50F45358.1020601@xenomai.org>
	<50F458E9.7080504@siemens.com> <50F4594C.8090907@xenomai.org>
	<50F45E87.9030701@siemens.com> <50F46D0E.9000706@xenomai.org>
	<50F53F0E.7020604@siemens.com> <50F54641.3010802@xenomai.org>
	<50F546E8.2050606@xenomai.org> <50F549AD.7040508@siemens.com>
	<50F55D33.3020205@xenomai.org> <50F55E22.9030308@siemens.com>
	<50F56074.50203@xenomai.org> <50F5B08D.60504@xenomai.org>
	<50F65EB3.1000301@siemens.com> <50F6687C.7040809@siemens.com>
	<50F675C8.1060009@xenomai.org> <50F67750.60408@siemens.com>
	<50F682DB.5000509@xenomai.org> <50F69709.8040506@xenomai.org>
In-Reply-To: <50F69709.8040506@xenomai.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai] 3.5.7 "I-pipe: could not find timer" (Was: Re: Kernel
 OOPS during regression tests)
List-Id: Discussions about the Xenomai project <xenomai.xenomai.org>
List-Unsubscribe: <http://www.xenomai.org/mailman/options/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=unsubscribe>
List-Archive: <http://www.xenomai.org/pipermail/xenomai>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-request@xenomai.org?subject=help>
List-Subscribe: <http://www.xenomai.org/mailman/listinfo/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=subscribe>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: John Morris <john@zultron.com>, Xenomai <xenomai@xenomai.org>

On 2013-01-16 13:03, Gilles Chanteperdrix wrote:
> On 01/16/2013 11:37 AM, Philippe Gerum wrote:>
> 
>> What happened is a misunderstanding between Gilles and myself on the 
>> presence of a pending pull request, nothing more, which eventually led 
>> to an out-of-sync pulling on my end. Since this happened when several 
>> people were pushing stuff to Gilles, this triggered my warning to the 
>> list, so that everyone involved may know that things stopped going as 
>> smoothly as usual. Rest assured that under normal circumstances, Gilles 
>> is very well aware of what I'm working on daily, and conversely. I 
>> understand your willingness to work the right way now that you recently 
>> committed to maintaining the x86 branch, and this is appreciated.
> 
> 
> My problem was to send the pull request then continue working on the
> branch, I should have a branch for pull requests, or send pull request
> for tags if that is possible.

I think this all melts down to communicating, like formally revoking a
pull or notifying the contributor about the merge of his pull. And this
will be more important when more people work on I-pipe now. There are
much bigger projects that struggle with such glitches, but we should
more easily be able to avoid them.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux