From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans De Goede <hdegoede@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: pushes at v4l-utils tree
Date: Thu, 11 Mar 2010 21:21:50 -0300 [thread overview]
Message-ID: <4B99891E.9010406@redhat.com> (raw)
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;
2) people need to pull/rebase before pushing, if we fix the group permission
issue above. I've enabled a hook that is meant to avoid rebase upstream, to prevent
troubles if people push something with -f. I hope it works fine.
3) the mailbomb script uses the from: as the email author. However, the
linuxtv-commits is limited to posts from a few specific authors. So, I need to add
more emails there or change the policy, if we decide to use such script.
I'll keep the script disabled for now, until I have some time to check it.
In summary, for now, I think that the better is to post all patches to v4l-utils at ML
and ask Hans to merge them.
--
Cheers,
Mauro
next reply other threads:[~2010-03-12 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 0:21 Mauro Carvalho Chehab [this message]
2010-03-12 15:50 ` pushes at v4l-utils tree 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
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=4B99891E.9010406@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox