This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: Migrating away from CVS
Grant Edwards wrote:
> On 2008-10-28, Chris Zimman <czimman@bloomberg.com> wrote:
>
>>> Here's an interesting web page: https://vpnout.com/
>>>
>>> Not that _I'd_ oficially condone using something like that to
>>> get around the roadblocks to getting work done that have been
>>> set up by your local Mordac.
>>>
>> Yeah, I know how to get around it, but I would rather have
>> something that worked with it. CVS is just outdated in the
>> networking department as well. Both GIT and SVN work fine over
>> HTTP/HTTPS.
>>
>
> True.
>
> It's a bit OT, but there's one thing I've been wondering about
> should eCos switch over to SVN. Since we use SVN locally for
> our eCos source tree, is there any way to simultaneusly use SVN
> with the "main" repository and with a local repository?
>
> Right now we can configure svn to ignore the cvs stuff and cvs
> to ignore the svn stuff. Then we can have a source tree that's
> both a working copy of our local SVN repository and a working
> copy of the main CVS repository. Obviously the diffs with
> respect to the two repository aren't always the same, but
> they're still useful.
>
> Does either GIT or SVN provide a way to work with two
> repositories?
>
I'm not a VCS wizard (know just enough to basically run our SVN) so
please regard following comment as both hint and question.
Doesn't distributed repository provide a solution this problem?
Can we consider that with VCS everyone effectively has an own repository
that is/(can be) synchronized with "official" repository?
Regards
Ilija
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss