Re: [v4l-dvb-maintainer] Moving to git for v4l-dvb
- Date: Thu, 14 Feb 2008 10:20:45 -0200
- From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx>
- Subject: Re: [v4l-dvb-maintainer] Moving to git for v4l-dvb
On Wed, 13 Feb 2008 21:35:37 -0500
Michael Krufky <mkrufky@xxxxxxxxxxx> wrote:
> Brandon Philips wrote:
> > On 18:24 Wed 13 Feb 2008, Michael Krufky wrote:
> >
> >> On Feb 13, 2008 3:20 PM, Brandon Philips <bphilips@xxxxxxx> 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.
We do have a full git tree. I don't understand what you're meaning. This tree
is generated by script (although I prefer to generate it manually, it shouldn't
be hard to automate it).
>
> I like that *much* better -- good idea!
>
> -Mike
Cheers,
Mauro
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list