[ECOS] Public CVS ecos/images woe.

[ECOS] Public CVS ecos/images woe.

[Sergei Organov]

Hello,

Is it possible to entirely get rid of those painful ecos/images
subdirectory (by moving it into separate module or something)?

The problem is that while it is indeed not checked out on initial
checkout of the 'ecos' module, the next

cvs update -d -P

brings it back into the working tree. Updating without -d is a bad idea
as it doesn't checkout new directories into the working tree when they
appear in the repository.

BTW, is there a way to get entire eCos public CVS *repository* in order
to mirror it locally?

-- Sergei.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Public CVS ecos/images woe.

[Daniel Néri]

Sergei Organov <osv@javad.com> writes:

> BTW, is there a way to get entire eCos public CVS *repository* in order
> to mirror it locally?

$ rsync rsync://sourceware.org | grep ecos
ecos-ftp        ecos ftp area (429 MB)
ecos-cvs        ecos cvs repository (1 GB)
ecos-htdocs     ecos htdocs (132 MB)
ecos-announce-ml-archive        ecos-announce mailing list archive (1 MB)
ecos-bugs-ml-archive    ecos-bugs mailing list archive (90 MB)
ecos-cvs-ml-archive     ecos-cvs mailing list archive (41 MB)
ecos-devel-ml-archive   ecos-devel mailing list archive (22 MB)
ecos-discuss-ml-archive ecos-discuss mailing list archive (525 MB)
ecos-maintainers-ml-archive     ecos-maintainers mailing list archive (21 MB)
ecos-patches-ml-archive ecos-patches mailing list archive (108 MB)


Regards,
-- 
Daniel Néri <daniel.neri@sigicom.se>
Sigicom AB, Stockholm, Sweden


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Public CVS ecos/images woe.

[Sergei Organov]

daniel.neri@sigicom.se (Daniel Néri) writes:
> Sergei Organov <osv@javad.com> writes:
>
>> BTW, is there a way to get entire eCos public CVS *repository* in order
>> to mirror it locally?
>
> $ rsync rsync://sourceware.org | grep ecos
> ecos-ftp        ecos ftp area (429 MB)
> ecos-cvs        ecos cvs repository (1 GB)

Thanks a lot!

-- Sergei.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Public CVS ecos/images woe.

[Andrew Lunn]

On Fri, Feb 15, 2008 at 03:44:11PM +0300, Sergei Organov wrote:
> Hello,
> 
> Is it possible to entirely get rid of those painful ecos/images
> subdirectory (by moving it into separate module or something)?
> 
> The problem is that while it is indeed not checked out on initial
> checkout of the 'ecos' module, the next
> 
> cvs update -d -P
> 
> brings it back into the working tree. Updating without -d is a bad idea
> as it doesn't checkout new directories into the working tree when they
> appear in the repository.

Everything above packages in the tree changes very infrequently. So i
generally only do cvs up -d in the packages directory and plain cvs up
when above that in the tree structure.

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Public CVS ecos/images woe.

[Sergei Organov]

Andrew Lunn <andrew@lunn.ch> writes:

> On Fri, Feb 15, 2008 at 03:44:11PM +0300, Sergei Organov wrote:
>> Hello,
>> 
>> Is it possible to entirely get rid of those painful ecos/images
>> subdirectory (by moving it into separate module or something)?
>> 
>> The problem is that while it is indeed not checked out on initial
>> checkout of the 'ecos' module, the next
>> 
>> cvs update -d -P
>> 
>> brings it back into the working tree. Updating without -d is a bad idea
>> as it doesn't checkout new directories into the working tree when they
>> appear in the repository.
>
> Everything above packages in the tree changes very infrequently. So i
> generally only do cvs up -d in the packages directory and plain cvs up
> when above that in the tree structure.

Yeah, that's what I did as well, but after I didn't do it for a month, I
once again forgot it and fetched all the images :(

-- Sergei.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss