From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: linux-sh@vger.kernel.org
Subject: Re: A patch got applied to v4l bypassing v4l lists
Date: Thu, 18 Dec 2008 19:36:19 +0000 [thread overview]
Message-ID: <20081218193619.GJ10620@game.jcrosoft.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0812181613050.5510@axis700.grange>
> Agree - breaking bisection is not something I'm looking into.
>
> If you like, I can explain to you where this extra work comes from. That's
> my current understanding of the work flow on v4l, it might still be not
> quite right, so I'll be happy if anyone corrects me and tells me a better
> way to handle this.
>
> v4l uses mercurial repositories as primary dveelopment trees. These
> repositories do not contain complete kernel trees, instead, they present a
> directory with some tools, where linux is a subdirectory of, and that's
> where a part of the kernel is reproduced.
so why do not you use git and git-modules it will save you time and will be
simplest to use and track the v4l tree
Best Regards,
J.
next prev parent reply other threads:[~2008-12-18 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 15:23 A patch got applied to v4l bypassing v4l lists Guennadi Liakhovetski
2008-12-18 16:08 ` Paul Mundt
2008-12-18 16:22 ` Guennadi Liakhovetski
2008-12-18 16:24 ` Paul Mundt
2008-12-18 16:49 ` Guennadi Liakhovetski
2008-12-18 21:18 ` Mauro Carvalho Chehab
2008-12-18 23:30 ` Guennadi Liakhovetski
2008-12-18 22:57 ` Mauro Carvalho Chehab
2008-12-19 7:15 ` Guennadi Liakhovetski
2008-12-18 19:36 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-12-18 20:12 ` Guennadi Liakhovetski
2008-12-19 4:38 ` Magnus Damm
2008-12-19 7:52 ` Paul Mundt
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=20081218193619.GJ10620@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=linux-sh@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