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: Wed, 2 Dec 2009 01:13:54 +0100 [thread overview]
Message-ID: <20091202001354.GA32247@raptus.dandreoli.com> (raw)
In-Reply-To: <1259709900.3102.3.camel@palomino.walls.org>
On Tue, Dec 01, 2009 at 06:25:00PM -0500, Andy Walls wrote:
> On Tue, 2009-12-01 at 15:59 +0100, 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.
> >
>
> > I'm waiting for comments.
>
> I only have one requirement: reduce bandwidth usage between the server
> and my home.
>
> The less I have to clone out 65 M of history to start a new series of
> patches the better. I suppose that would include a rebase...
no, it would not. in case you feel better to clone something before a
rebase, you can clone it locally.
rebasing is an easily abused practice which destroys the history of
a branch and puts in trouble the followers of that branch. published
branch which is often rebased is usually frown upon.
git is a branch-merge-branch-throw-away-branch-branch-merge-... tool.
commit massaging is another tempting practice, it's so easy to produce a
cleaned up history of your branch. writing code in 2D is already pretty
difficult, God save us from writing code in 3D.
cheers,
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-02 0:13 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 [this message]
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=20091202001354.GA32247@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