public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: goodmenlinux@gmail.com
Cc: crossgcc@sourceware.org
Subject: Re: [Maybe a boring Question] Why not GIT?
Date: Thu, 08 Aug 2013 19:42:00 -0000	[thread overview]
Message-ID: <20130808194243.GC3282@free.fr> (raw)
In-Reply-To: <20130808014749.GA9845@nagra.com>

Brock, All,

On 2013-08-08 09:47 +0800, goodmenlinux@gmail.com spake thusly:
> I found that github has ct-ng dir, but the latest update is 3 years ago.
> Does this great project has any plan to use GIT?
> Any comment on it?

Oh... That's been a long time since that one came last...

OK, a bit of history:
  - first I slightly hacked on the original crosstool (then maintained
    by Dan Kegel), and there was no repository, only occasional tarball
    releases
  - then I hacked a bit more, and that eventually became crosstool-NG
  - this was done in subversion, since I was really comfortable with it
  - I eventually reached the limits of svn especially when I witnessed
    an unrecoverable repository crash twice in a row, with no apparent
    reason
  - I looked at the other existing possibilities (circa 2009-07):
    - cvs? Muahaha!
    - bazaar: you must be kidding me! ;-)
    - git: widespread, powerfull, yet very complex to get up to speed;
      one needs his flight license and 200h in active duty before beinf
      able to at least land a merge sanely.
    - Hg: repository set up and live in two hours, with no prior
      knowledge of a DVCS.
  - choice made: Hg that was to be.

Now, time has passed, I am now confident in my git abilities (although I
am far from being an expert). When I get some time, I'll migrate to git,
but there is n oschedule for this.

Anyway, there exist Hg <-> git converter, and one can even use git to
work with an Hg repository in the meantime.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  parent reply	other threads:[~2013-08-08 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  1:48 goodmenlinux
2013-08-08  5:36 ` Austin Morton
2013-08-08  8:50   ` goodmenlinux
2013-08-08 12:12     ` ANDY KENNEDY
2013-08-08 13:02       ` Grant Edwards
2013-08-08 19:42 ` Yann E. MORIN [this message]
2013-08-08 20:02   ` Austin Morton
2013-08-09  1:44   ` goodmenlinux
2013-08-09  7:21   ` Thomas De Schampheleire
2013-08-09  7:40     ` goodmenlinux
2013-08-09  7:47       ` Thomas De Schampheleire

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=20130808194243.GC3282@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=crossgcc@sourceware.org \
    --cc=goodmenlinux@gmail.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).