public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Patrick Boettcher <pboettcher@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Replace Mercurial with GIT as SCM
Date: Thu, 03 Dec 2009 09:04:48 +0100	[thread overview]
Message-ID: <4B177120.6090900@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0912011003480.30797@pub3.ifh.de>

+1 for git, I really really really miss being able to do
a simple "git rebase", and no rebase is not evil not as long
as you don't use it for anything but local patches.

Regards,

Hans




On 12/01/2009 03:59 PM, Patrick Boettcher wrote:
> Hi all,
>
> 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.
>
> To start right away: I'm in favour of using GIT because of difficulties
> I have with my "daily" work with v4l-dvb. It is in my nature do to
> mistakes, so I need a tool which assists me in fixing those, I have not
> found a simple way to do my stuff with HG.
>
> I'm helping out myself using a citation from which basically describes
> why GIT fits the/my needs better than HG (*):
>
> "The culture of mercurial is one of immutability. This is quite a good
> thing, and it's one of my favorite aspects of gnu arch. If I commit
> something, I like to know that it's going to be there. Because of this,
> there are no tools to manipulate history by default.
>
> git is all about manipulating history. There's rebase, commit amend,
> reset, filter-branch, and probably other commands I'm not thinking of,
> many of which make it into day-to-day workflows. Then again, there's
> reflog, which adds a big safety net around this mutability."
>
> The first paragraph here describes exactly my problem and the second
> descibes how to solve it.
>
> My suggestion is not to have the full Linux Kernel source as a new base
> for v4l-dvb development, but "only" to replace the current v4l-dvb hg
> with a GIT one. Importing all the history and everything.
>
> Unfortunately it will change nothing for Mauro's job.
>
> I also understand that it does not give a lot to people who haven't used
> GIT until now other than a new SCM to learn. But believe me, once you've
> done a rebase when Mauro has asked you to rebuild your tree before he
> can merge it, you will see what I mean.
>
> I'm waiting for comments.
>
> Thanks,
>
> (*)
> http://www.rockstarprogrammer.org/post/2008/apr/06/differences-between-mercurial-and-git/
>
>
> --
>
> Patrick
> http://www.kernellabs.com/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-12-03  7:57 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
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 [this message]
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=4B177120.6090900@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=pboettcher@kernellabs.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