public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alex Schuilenburg <alexs@ecoscentric.com>
To: "Øyvind Harboe" <oyvind.harboe@zylin.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos submodule support
Date: Tue, 20 Oct 2009 23:19:00 -0000	[thread overview]
Message-ID: <4ADE4589.4010102@ecoscentric.com> (raw)
In-Reply-To: <c09652430910200347n1aad06a9w809423e71f1501ad@mail.gmail.com>

Øyvind Harboe wrote:
> [...]
> I have never tried to manage hg as a submodule in git.
>
> So, eCos choosing "the other DVCS" would
> make my life harder even if that "other DVCS" is
> better.
>   
I missed this bit :-/

I dont believe it will be harder - in fact I dont think it will make any
difference if hg were chosen because hg plays nicely with git.  More
like the other way round - if git were chosen it would make proper use
of a DRCS harder on the majority of the eCos community.

git may be mainstream to Linux users, but is IMHO is not as user
friendly as what the majority of eCos users and contributors should
expect from a DRCS.  I believe that it will make life harder than it
ought to be when converting to a DRCS model, and particularly to anyone
who is not familiar with Linux (Windows users, and the average eCos user). 

Think about it.  Most eCos users and developers use Windows for their
development, yet most contributors are Linux power users.  Surely we
want something that would encourage and make it easier for Windows
hosted eCos developers to contribute, yet does not inhibit those Linux
power users and existing regular eCos contributors (and of course the
eCos maintainers) in any way?

-- Alex Schuilenburg

Managing Director/CEO                                eCosCentric Limited
www.ecoscentric.com


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2009-10-20 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c09652430910191038m6ddd7153gcb6d7616719a72c9@mail.gmail.com>
2009-10-19 21:17 ` [ECOS] " Øyvind Harboe
2009-10-20  7:50   ` [ECOS] " Daniel Néri
2009-10-20 10:47   ` Øyvind Harboe
2009-10-20 14:45     ` Sergei Organov
2009-10-20 21:37       ` Alex Schuilenburg
2009-10-20 23:19     ` Alex Schuilenburg [this message]
2009-10-21  6:47       ` Øyvind Harboe
2009-10-20 14:37   ` [ECOS] " Alex Schuilenburg
2009-10-20 14:50     ` Øyvind Harboe
2009-10-20 19:22       ` Alex Schuilenburg
2009-10-20 19:36         ` Øyvind Harboe
2009-10-21  0:00       ` Jonathan Larmour
2009-10-20 23:55     ` Jonathan Larmour
2009-10-21  1:43       ` Alex Schuilenburg
2009-10-23  8:54 [ECOS] " Alex Schuilenburg

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=4ADE4589.4010102@ecoscentric.com \
    --to=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).