From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Brandon Philips <brandon@ifup.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Douglas Landgraf <dougsland@gmail.com>
Subject: Re: [ANNOUNCE] git tree repositories & libv4l
Date: Tue, 23 Feb 2010 10:36:16 -0300 [thread overview]
Message-ID: <4B83D9D0.6000105@infradead.org> (raw)
In-Reply-To: <1a297b361002230507v53aa12d8te780b5fd0463b8c5@mail.gmail.com>
Manu Abraham wrote:
>>> What's the advantage in merging the dvb and v4l2 utils, other than to
>>> make the download/clone bigger ?
>> There aren't any big advantages on merging, nor there are big advantages on keeping
>> them alone.
>>
>> Advantages to merge:
>> - One single release control. Currently, only Hans de Goede is doing a
>> good job with release names, on libv4l. By having everything into one place, all other
>> v4l2-apps and dvb-apps will have a release name, making easier even for us when helping
>> people with troubles (as we'll know for sure if they're using the latest version or
>> a very old version;
>> - One single tree for the user to download, for IR, DVB and V4L apps;
>> - Distro packagers will have one single tarball to maintain.
>>
>> Disadvantages:
>> - More people will need access to the same git master tree;
>> - The tree will be bigger.
>
>
> It is quite noble to think of having to have everything unified in the
> world. But that doesn't seem how things are in practice. It's quite
> understood that the concept of "one-single-ring-to-rule-them-all"
> doesn't work well.
>
> The mercurial dvb-apps tree has worked quite well for me as well as
> the other few people who have been involved with it and don't have any
> problems in that arena and I am very happy with it on that front.
>
> FWIW, I am not very much interested to move to git.
>
> Are we making a mockery, switching between SCM's every now and then .. ?
>
> Maybe there are others as well, who feel that way. But that's not the
> more important point. For me, it is like simply that a simple update
> is quite fast and easy.
I don't think moving it to git would bring any significant advantage or
disadvantage.
> With regards to distro stuff; This is best left to distro vendors.
Agreed.
> With regards to release control, we have had a 1.1.1 release. Looking
> back, we haven't had a proper stable state yet, for another release.
Hmm...
http://www.linuxtv.org/downloads/
May, 18 2006...
$ hg log -d ">05/18/2006" -p|diffstat -p1|grep changed
1402 files changed, 66559 insertions(+), 16267 deletions(-)
Sorry, but it is really failing with release control. There were _lots_ of change
since 2006, including several new applications, and tons of new channel/transponders
added to it.
> Thinking of which, it is more of these discussions that hold back real
> development rather than anything else. Moving to git, or have a merged
> tree with v4l2 and dvb utils is not going to make dvb-apps development
> any faster.
>
> On the contrary, I don't think it is going to help dvb-apps in anyway
> on the development front, but rather make it worser.
Why would it be worse?
> My few cents, being one of the dvb-apps maintainers and author of some
> the bits and pieces in it.
PS.: while removing that "need maintainer" warning from the wiki, I noticed that,
just like v4l2-apps, there's one application there for IR (util/av7110_loadkeys).
Even if we decide to keep the trees separate, we should really put this utility
and the IR code at v4l2-apps at the same place.
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-23 13:36 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 5:34 [ANNOUNCE] git tree repositories Mauro Carvalho Chehab
2010-01-19 7:53 ` Hans Verkuil
2010-01-19 8:10 ` Patrick Boettcher
2010-01-19 11:20 ` Johannes Stezenbach
2010-01-19 11:49 ` Patrick Boettcher
2010-01-19 12:44 ` Mauro Carvalho Chehab
2010-01-20 8:04 ` Markus Heidelberg
2010-01-20 15:11 ` Mauro Carvalho Chehab
2010-01-19 11:55 ` Mauro Carvalho Chehab
2010-01-19 23:38 ` Andy Walls
2010-01-20 1:10 ` hermann pitton
2010-01-20 3:29 ` Andy Walls
2010-01-20 3:29 ` Mauro Carvalho Chehab
2010-01-20 4:08 ` Andy Walls
2010-01-20 15:05 ` Mauro Carvalho Chehab
2010-01-20 11:43 ` BOUWSMA Barry
2010-01-20 10:19 ` BOUWSMA Barry
2010-01-19 11:08 ` Mauro Carvalho Chehab
2010-01-20 8:36 ` [ANNOUNCE] git tree repositories & libv4l Hans de Goede
2010-01-20 8:55 ` Hans Verkuil
2010-01-20 15:41 ` Mauro Carvalho Chehab
2010-01-20 18:50 ` Hans de Goede
2010-01-20 21:07 ` Brandon Philips
2010-01-21 2:07 ` Mauro Carvalho Chehab
2010-01-21 2:46 ` Brandon Philips
2010-01-21 7:34 ` Hans Verkuil
2010-01-21 20:15 ` Mauro Carvalho Chehab
2010-01-23 17:24 ` Hans de Goede
2010-02-22 22:54 ` Brandon Philips
2010-02-22 23:26 ` Hans Verkuil
2010-02-22 23:38 ` Brandon Philips
2010-02-23 0:41 ` Mauro Carvalho Chehab
2010-02-23 1:12 ` Mauro Carvalho Chehab
2010-02-23 8:04 ` Brandon Philips
2010-02-23 13:37 ` Mauro Carvalho Chehab
2010-02-23 9:45 ` Manu Abraham
2010-02-23 11:20 ` Mauro Carvalho Chehab
2010-02-24 2:32 ` hermann pitton
2010-02-23 11:20 ` Manu Abraham
2010-02-23 8:49 ` Hans de Goede
2010-02-23 9:01 ` Hans Verkuil
2010-02-23 9:23 ` Hans de Goede
2010-02-23 9:38 ` Manu Abraham
2010-02-23 12:21 ` Mauro Carvalho Chehab
2010-02-23 13:07 ` Manu Abraham
2010-02-23 13:36 ` Mauro Carvalho Chehab [this message]
2010-02-23 14:09 ` Manu Abraham
2010-02-23 12:10 ` Mauro Carvalho Chehab
2010-02-23 11:49 ` Mauro Carvalho Chehab
2010-02-23 15:37 ` Mauro Carvalho Chehab
2010-02-23 15:51 ` Hans de Goede
2010-02-24 0:58 ` Mauro Carvalho Chehab
2010-02-24 12:55 ` Hans de Goede
2010-02-24 13:40 ` Hans Verkuil
2010-02-24 13:42 ` Mauro Carvalho Chehab
2010-02-24 14:32 ` Brandon Philips
2010-02-25 10:52 ` Hans de Goede
2010-02-24 6:05 ` Brandon Philips
2010-02-24 12:44 ` Hans de Goede
2010-02-24 13:26 ` Mauro Carvalho Chehab
2010-02-24 14:29 ` Patrick Boettcher
2010-02-25 4:55 ` Douglas Schilling Landgraf
2010-01-21 7:23 ` Hans Verkuil
2010-01-21 20:04 ` Mauro Carvalho Chehab
2010-01-23 17:28 ` Hans de Goede
2010-01-24 0:42 ` Mauro Carvalho Chehab
2010-01-25 16:03 ` Hans de Goede
2010-01-20 9:43 ` Laurent Pinchart
2010-01-20 9:54 ` Paulo Assis
2010-01-20 10:43 ` libwecam & uvcdynctrl (was Re: [ANNOUNCE] git tree repositories & libv4l) Hans de Goede
2010-01-19 15:54 ` [ANNOUNCE] git tree repositories Douglas Schilling Landgraf
2010-01-19 8:04 ` Laurent Pinchart
2010-01-19 11:12 ` Mauro Carvalho Chehab
2010-01-19 11:50 ` Laurent Pinchart
2010-01-19 12:36 ` Mauro Carvalho Chehab
2010-01-19 10:04 ` Devin Heitmueller
2010-01-19 11:52 ` Patrick Boettcher
2010-01-19 12:39 ` Mauro Carvalho Chehab
2010-01-19 12:16 ` Mauro Carvalho Chehab
2010-01-19 21:21 ` Bob Cunningham
2010-01-19 22:37 ` hermann pitton
2010-01-20 13:54 ` Laurent Pinchart
2010-01-20 15:00 ` Mauro Carvalho Chehab
2010-01-19 12:56 ` Laurent Pinchart
2010-01-19 13:07 ` Mauro Carvalho Chehab
2010-01-19 13:12 ` Laurent Pinchart
2010-01-19 21:59 ` Johannes Stezenbach
2010-01-21 2:19 ` Mauro Carvalho Chehab
2010-01-21 2:53 ` Trent Piepho
2010-01-21 3:09 ` Mauro Carvalho Chehab
2010-01-20 19:09 ` Guennadi Liakhovetski
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=4B83D9D0.6000105@infradead.org \
--to=mchehab@infradead.org \
--cc=abraham.manu@gmail.com \
--cc=brandon@ifup.org \
--cc=dougsland@gmail.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--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