From: Jonathan Larmour <jifl@jifvik.org>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: "Øyvind Harboe" <oyvind.harboe@zylin.com>,
"eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Eclipse support for git
Date: Tue, 22 Sep 2009 20:08:00 -0000 [thread overview]
Message-ID: <4AB92EAD.4070103@jifvik.org> (raw)
In-Reply-To: <4AB8B7D9.8080106@ecoscentric.com>
Alex Schuilenburg wrote:
> Ãyvind Harboe wrote on 2009-09-22 09:33:
>
>>I think it is important when choosing the next version control
>>system to think about whether we're getting onto the right
>>train.
>>
>>The support today is important, yes, but what happens
>>2-3 years from now?
I think in all cases, we should look at the state now. They are all
deployed in high profile projects and aren't going away soon. Due to their
better handling of metadata (compared to CVS certainly) it's also much
more feasible to swap between them, as many people do. We absolutely want
to make a good choice, but practically speaking this is not truthfully a
"forever" decision. Oh oops, yes Alex says that too.
> https://ldn.linuxfoundation.org/article/dvcs-roundup-one-system-rule-them-all-part-2
>
> Namely:
> If you really want a direct recommendation, it would be thus: download
> Git and Mercurial, then throw dice. Personally I like the âit just
> worksâ approach of Mercurial a bit better, and the fact that it is
> written in Python. Also for cross-platform projects needing Windows
> support Mercurial is (at this moment) probably a tiny bit less
> problematic. If you work in a completely UNIX-centered environment, Git
> might be the slightly better choice. However, both systems work very
> well, are stable and very, very fast. So it's a tie, more or less."
For what it's worth, despite being a linux fanboy myself obviously ;-),
considering the wider eCos community is a priority. And as such, usability
on Windows is a concern for me with git. And it's overall learning curve
(the "it just works" above) inherent to its design. I would slightly
prefer something that disenfranchised the small number of elite power
users to something that disenfranchised a much larger number of less
experienced users.
After all, one of the reasons for the popularity of CVS is its simplicity.
Talking about octopus merges with an eCos n00b is not going to get people
very far.
Of course one of the joys of DRCS's is the now-widespread ability to sync
and mereg in from other repositories using a different DRCS. That's
another reason why the power users will be able to get by. It also means
that the real decision is indeed probably going to be with the maintainers
as the ones who have to consider the wider eCos userbase as well as being
the ones that definitely have to interact with that particular VCS.
The discussions so far seem have been a bit ad hoc. I'd like to bring them
more on track. I personally agree with Alex's view that the choice of VCS
is probably between Git, Hg, and Bzr. If anyone would like to suggest SVN,
Arch or something more exotic, it's time to speak up.
Then we can do specific head-to-head comparisons between the three, which
is tractable.
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-09-22 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 8:33 Øyvind Harboe
2009-09-22 11:41 ` Alex Schuilenburg
2009-09-22 11:47 ` Øyvind Harboe
2009-09-22 20:08 ` Jonathan Larmour [this message]
2009-09-23 10:09 ` [ECOS] " Sergei Organov
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=4AB92EAD.4070103@jifvik.org \
--to=jifl@jifvik.org \
--cc=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=oyvind.harboe@zylin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).