public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Alex Schuilenburg <alexs@ecoscentric.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] What's the process on switching version control system   for eCos?
Date: Fri, 25 Sep 2009 00:33:00 -0000	[thread overview]
Message-ID: <4ABC0FC1.3090502@jifvik.org> (raw)
In-Reply-To: <4AB8F69B.1000307@ecoscentric.com>

Alex Schuilenburg wrote:
> Bart Veer wrote on 2009-09-22 15:34:
>>  b) how much history can we expect to lose, irrespective of the
>>     amount of effort put in?
>>  
> 
> Only what cvsps misses, or rather, does not know what to do with (google
> CVSPS_NO_BRANCH for details). Those files or changes are basically
> orphaned.  However, I will send a list of the files along with their
> revisions to the maintainers and you can decide what to do with them.

Frankly I wouldn't worry about it to that level - if that level of digging 
is required to find out past history, the best thing to do is to look 
directly at the old CVS repository.

Those orphaned changes are probably the result of "cvs admin" hacks and so 
on. In which case they were probably orphaned for a reason.

>>So, a suggestion that e.g. eCos should switch over to git because it
>>is already in use on other projects is unlikely to get much attention
>>from the maintainers. A serious offer to do the hard work will get
>>much more attention, especially if it is backed up with experimental
>>data and explanations of why some of the problems with cvs are just
>>too hard to work around.
>>  
> 
> My offer in my previous email is serious.  Little skin off my nose and
> most CPU cycles are free.  I have already developed my script in-house
> for an internal conversion and so we can evaluate the different DRCS
> systems.  What the maintainers or community choose to do with the repo
> is up to them, but moving an hg repo to sourceware will be has hard as
> "hg clone http://hg.ecoscentric.com/ecos", while converting it to git or
> bzr a matter of exporting the patchsets (this time without error) from
> hg after cloning it and importing them.

I for one would like to take you up on that! Even if the choice isn't hg 
that effort would be useful and not wasted.

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:33 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
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 [this message]
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=4ABC0FC1.3090502@jifvik.org \
    --to=jifl@jifvik.org \
    --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).