From: Hans de Goede <hdegoede@redhat.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: pushes at v4l-utils tree
Date: Sat, 13 Mar 2010 07:41:03 +0100 [thread overview]
Message-ID: <4B9B337F.50203@redhat.com> (raw)
In-Reply-To: <4B9A962A.2020407@redhat.com>
Hi,
On 03/12/2010 08:29 PM, Mauro Carvalho Chehab wrote:
> Hans de Goede wrote:
>> Hi,
>>
>> On 03/12/2010 01:21 AM, Mauro Carvalho Chehab wrote:
>>> Hi Hans,
>>>
>>> As we've agreed that the idea is to allow multiple people to commit at
>>> v4l-utils,
>>> today, I've added 3 commits at v4l-utils tree (2 keycode-related and 1
>>> is .gitignore
>>> stuff). One of the reasons were to test the viability for such commits.
>>>
>>> I've temporarily enabled the same script that we use for upstream
>>> patches to
>>> generate patches against linuxtv-commits ML.
>>>
>>> From my experiences, I have some notes:
>>> 1) git won't work fine if more than one is committing at the same
>>> tree.
>>> The reason is simple: it won't preserve the same group as the previous
>>> commits. So,
>>> the next committer will have troubles if we allow multiple committers;
>>>
>>
>> I assume you are talking about some issues with permissions on the
>> server side here ?
>
> Yes. The new objects and the touched files got a different group ownership
> after git push. I had to manually fix them at the server.
>
I'll get you in touch with one of the Fedora infrastructure admins.
Regards,
Hans
prev parent reply other threads:[~2010-03-13 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 0:21 pushes at v4l-utils tree Mauro Carvalho Chehab
2010-03-12 15:50 ` Hans de Goede
2010-03-12 19:29 ` Mauro Carvalho Chehab
2010-03-12 21:03 ` Antonio Ospite
2010-03-13 1:24 ` Mauro Carvalho Chehab
2010-03-13 3:50 ` Mauro Carvalho Chehab
2010-03-13 6:43 ` Hans de Goede
2010-03-13 20:44 ` Mauro Carvalho Chehab
2010-03-13 6:41 ` Hans de Goede [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=4B9B337F.50203@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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