public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Sergei Organov <osv@javad.com>
Cc: eCos discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS]  Re: What's the process on switching version control system   for  	eCos?
Date: Fri, 25 Sep 2009 00:28:00 -0000	[thread overview]
Message-ID: <4ABC0EA2.7010707@jifvik.org> (raw)
In-Reply-To: <h9as44$sto$1@ger.gmane.org>

Sergei Organov wrote:
> Alex Schuilenburg <alexs@ecoscentric.com> writes:
> 
>>Sergei Organov wrote on 2009-09-22 15:59:
>>
>>>Øyvind Harboe <oyvind.harboe@zylin.com> writes:
>>>[...]
>>>IMHO, eCos is not that big to worry about the size of the repository,
>>>provided huge binary images are not put into the repository.
>>>  
>>
>>ROTFLMAO!!!
>>
>>Seen ecos-images?!?!?
> 
> 
> That's what I meant. They shouldn't be there in the eCos source code
> repository, be it CVS or anything else. Someone who needs them (though I
> doubt anybody does) should be able to download them separately.

Given their original raison d'etre it made sense at the time - known good 
images appropriate (more or less) to the source code at a particular date, 
and put under version control.

But they have not been kept up-to-date, and the ones there are pretty much 
all for obsolete platforms. I would have no objections for a new DRCS 
leaving them out. We will always have the original CVS sitting around for 
archaeology, although I'd doubt we'd ever touch them!

Even if someone was willing to (somehow) make a new set of known-good 
images for current platforms, that should live in a separate repo, 
precisely to allow DRCS's to function sensibly.

>>I say closer because, rather than doing a faithful CVS convertion, I am
>>fixing problems like files not actually being tagged as part of a
>>release (i.e cvs co -r <tag>) despite existing in the repo on a branch
>>when the tag was made and being shipped with the release and others
>>previously mentions.  I have had to become a CVS expert to detect and
>>fix most of these problems and now HATE CVS with such a passion you
>>would not believe.
> 
> 
> I've tried to convert a few CVS repositories to git, so I do know what
> you are talking about. You have my sympathies!

I think the eCos repository has more challenges than usual due to various 
tricks played with over the years. I'll be glad to see the back of the 
ecos-net modules hack.

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

  reply	other threads:[~2009-09-25  0:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  9:51 [ECOS] " Øyvind Harboe
2009-09-21 11:26 ` Alex Schuilenburg
2009-09-22 14:34 ` Bart Veer
2009-09-22 14:40   ` Øyvind Harboe
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 [this message]
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=4ABC0EA2.7010707@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=osv@javad.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).