From: Michael Krufky <mkrufky@linuxtv.org>
To: Brandon Philips <brandon@ifup.org>
Cc: video4linux-list@redhat.com,
Guennadi Liakhovetski <g.liakhovetski@pengutronix.de>,
v4lm <v4l-dvb-maintainer@linuxtv.org>,
Brandon Philips <bphilips@suse.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [v4l-dvb-maintainer] Moving to git for v4l-dvb
Date: Wed, 13 Feb 2008 21:35:37 -0500 [thread overview]
Message-ID: <47B3A8F9.3080106@linuxtv.org> (raw)
In-Reply-To: <20080214023415.GB23519@plankton.ifup.org>
Brandon Philips wrote:
> On 18:24 Wed 13 Feb 2008, Michael Krufky wrote:
>
>> On Feb 13, 2008 3:20 PM, Brandon Philips <bphilips@suse.de> wrote:
>>
>>> On 10:24 Tue 05 Feb 2008, Mauro Carvalho Chehab wrote:
>>>
>>>> Maybe we've took the wrong direction when we've decided to select
>>>> mercurial. It were better and easier to use, on that time, but the -git
>>>> improvements happened too fast.
>>>>
>>> We should consider a move to a full-tree git. Particularly, it would be
>>> nice to be have v4l-dvb merging/building against other subsystems in the
>>> linux-next tree:
>>>
>>> http://lkml.org/lkml/2008/2/11/512
>>>
>>> Also, it would save the silly pain of things like this meye.h thing and
>>> pulling in fixes from the rest of the community that patches against git
>>> trees.
>>>
>> Additionally, the moment we move development from hg to git, we are
>> bound to the development kernel -- we will no longer be able to work
>> against any stable kernel series, and we will lose all of our testers.
>>
>
> Good point. Testers seem pretty happy with our current system.
>
> I will look into auto-generating a full git tree from the hg v4l-dvb
> repo. That way we can participate in linux-next while still using
> mercurial for development.
I like that *much* better -- good idea!
-Mike
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-02-14 2:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 1:24 NACK NACK! [PATCH] Add two new fourcc codes for 16bpp formats Brandon Philips
2008-02-05 7:16 ` Guennadi Liakhovetski
2008-02-05 8:00 ` Brandon Philips
2008-02-05 12:24 ` Mauro Carvalho Chehab
[not found] ` <20080213202055.GA26352@plankton.ifup.org>
2008-02-13 23:24 ` [v4l-dvb-maintainer] Moving to git for v4l-dvb Michael Krufky
2008-02-13 23:54 ` Alex Deucher
2008-02-14 0:56 ` Michael Krufky
2008-02-13 23:55 ` hermann pitton
2008-02-14 2:34 ` Brandon Philips
2008-02-14 2:35 ` Michael Krufky [this message]
2008-02-14 12:20 ` Mauro Carvalho Chehab
2008-02-14 19:46 ` Mauro Carvalho Chehab
2008-02-14 23:08 ` Brandon Philips
2008-12-17 14:12 ` Guennadi Liakhovetski
2008-12-17 14:18 ` Michael Krufky
2008-12-17 14:33 ` Guennadi Liakhovetski
2008-12-17 16:52 ` Mauro Carvalho Chehab
2008-12-17 17:05 ` Guennadi Liakhovetski
2008-12-17 18:23 ` Mauro Carvalho Chehab
2008-02-05 13:23 ` NACK NACK! [PATCH] Add two new fourcc codes for 16bpp formats Michael Krufky
2008-02-05 14:01 ` Mauro Carvalho Chehab
2008-02-05 23:15 ` Brandon Philips
2008-02-06 1:27 ` Michael Krufky
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=47B3A8F9.3080106@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=bphilips@suse.de \
--cc=brandon@ifup.org \
--cc=g.liakhovetski@pengutronix.de \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@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