From: Domenico Andreoli <cavokz@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Replace Mercurial with GIT as SCM
Date: Tue, 1 Dec 2009 16:44:13 +0100 [thread overview]
Message-ID: <20091201154413.GA11696@raptus.dandreoli.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0912011003480.30797@pub3.ifh.de>
On Tue, Dec 01, 2009 at 03:59:20PM +0100, Patrick Boettcher wrote:
> Hi all,
hi,
> I would like to start a discussion which ideally results in either
> changing the SCM of v4l-dvb to git _or_ leaving everything as it is
> today with mercurial.
i should not be stopped by a tool i'm not familiar with (that is hg)
but actually it is a barrier for me. i'd like to regularly follow v4l-dvb
and surely with git i'd not waste the time as with hg.
the result is that i have a separate git tree for "my" tw68xx driver
and the integration with v4l-dvb and hg is not my topomost priority
given also that everything needs to be ported back to git before kernel
inclusion.
while i accept that people doing real work should use the tool the
prefer i consider this fracture with the kernel SCM a mistake.
this is only my opinion, my intent is not to start any flamewar.
regards,
Domenico
-----[ Domenico Andreoli, aka cavok
--[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
next prev parent reply other threads:[~2009-12-01 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 14:59 Replace Mercurial with GIT as SCM Patrick Boettcher
2009-12-01 15:44 ` Domenico Andreoli [this message]
2009-12-01 16:07 ` Alex Deucher
2009-12-01 16:11 ` Antti Palosaari
2009-12-01 19:49 ` Trent Piepho
2009-12-01 23:25 ` Andy Walls
2009-12-02 0:13 ` Domenico Andreoli
2009-12-03 4:42 ` Hans Verkuil
2009-12-03 21:42 ` Guennadi Liakhovetski
2009-12-04 0:48 ` Mauro Carvalho Chehab
2009-12-03 8:04 ` Hans de Goede
2009-12-03 11:34 ` Laurent Pinchart
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=20091201154413.GA11696@raptus.dandreoli.com \
--to=cavokz@gmail.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