From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] What's the process on switching version control system for eCos?
Date: Tue, 22 Sep 2009 14:40:00 -0000 [thread overview]
Message-ID: <c09652430909220740t7a45e3eat9810c077e4465188@mail.gmail.com> (raw)
In-Reply-To: <pnljk7ujyd.fsf@delenn.bartv.net>
> b) how much history can we expect to lose, irrespective of the
> amount of effort put in?
And c) given that the *entire* repository will be replicated to everybody
who wants to clone the eCos repository, how big do we really want
the repository to be?
the distributed source control systems allow the repository to be
downloaded as a single huge file, so even if the repository size is
in the hundreds of megabytes, it's not *too* bad if you are blessed
with fiber...
I haven't heard any guestimates on the expected git repository
size(I don't know of a significant difference in repository size
efficiency between the various systems).
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
--
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 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 9:51 Øyvind Harboe
2009-09-21 11:26 ` Alex Schuilenburg
2009-09-22 14:34 ` Bart Veer
2009-09-22 14:40 ` Øyvind Harboe [this message]
2009-09-22 15:00 ` [ECOS] " Sergei Organov
2009-09-22 15:42 ` Alex Schuilenburg
2009-09-22 15:57 ` Sergei Organov
2009-09-25 0:28 ` Jonathan Larmour
2009-09-25 7:58 ` Sergei Organov
2009-09-22 16:09 ` [ECOS] " Alex Schuilenburg
2009-09-25 0:33 ` Jonathan Larmour
2009-10-01 11:43 ` [ECOS] Help required for LDI file Himanshu Patel
2009-10-01 21:14 ` [ECOS] " John Dallaway
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=c09652430909220740t7a45e3eat9810c077e4465188@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=bartv@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).