public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Switching to using git on eCosForge
Date: Thu, 17 Sep 2009 12:56:00 -0000	[thread overview]
Message-ID: <c09652430909170556p5bd4f2e4g32aca9a4dc713ea9@mail.gmail.com> (raw)
In-Reply-To: <4AB22E5F.8090807@ecoscentric.com>

First of all: great to hear you're looking to upgrade from CVS to
distributed development. A ~20 year leap in tools, bound to be
tricky that one :-)

> Why git in particular?

No reason not to really.

git is easy to use when cloning/downloading + web interfaces exist
where you can download snapshots.

+ git is becoming more of a required skill for embedded development
as Linux requires it, so I looked a bit at mercurial, but didn't really
feel like learning more than one of these distributed systems.. it's
been a while
that anybody suggested or wanted anything but git as an alternative
to svn in the circles I frequent. I'm sure git tools will improve with time.
We're looking 5-10 years into the future here, right?

> The choice of an alternative RCS should also take into consideration
> Windows users, as well as speed and ease of use.

Web interfaces on the server kinda take care of my greatest
concern about those that do not want or need to learn git.

They can wget + tar ...., no version control system at all involved.

Also there are nice git server sites for those that have some
pet project they are working on and want to share, e.g.
http://repo.or.cz/, which pretty much fills the role that
www.ecosforge.net has had up to now


The above said, I don't think I'll care if eCos CVS switches to
git or mercurial. Mercurial is next on my list of distributed systems
to look into and if I only did closed source development, probably
the preferred solution.


-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.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

  reply	other threads:[~2009-09-17 12:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 10:52 Øyvind Harboe
2009-09-17 12:41 ` Alex Schuilenburg
2009-09-17 12:56   ` Øyvind Harboe [this message]
     [not found]     ` <4AB23FD3.2020808@ecoscentric.com>
2009-09-17 14:10       ` Øyvind Harboe
2009-09-17 14:23     ` [ECOS] " Grant Edwards
2009-09-17 14:37       ` Ross Younger
2009-09-17 14:46       ` Patrick Doyle
2009-09-17 13:10   ` [ECOS] " Patrick Doyle
2009-09-17 14:11     ` Alex Schuilenburg
2009-09-21 14:57       ` Øyvind Harboe
2009-09-17 13:32   ` [ECOS] " Sergei Organov
2009-09-17 14:02   ` [ECOS] eCos VCS switch (was: Switching to using git on eCosForge) Daniel Néri
2009-09-21 13:06   ` [ECOS] Re: Switching to using git on eCosForge Sergei Organov
2009-09-21 13:55     ` Sergei Gavrikov
2009-09-21 14:11       ` Sergei Organov
2009-09-17 14:41 [ECOS] " Alex Schuilenburg
2009-09-17 15:27 ` Ross Younger

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=c09652430909170556p5bd4f2e4g32aca9a4dc713ea9@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).