* [ECOS] Public CVS ecos/images woe.
@ 2008-02-15 12:44 Sergei Organov
2008-02-15 13:24 ` [ECOS] " Daniel Néri
2008-02-15 15:27 ` [ECOS] " Andrew Lunn
0 siblings, 2 replies; 5+ messages in thread
From: Sergei Organov @ 2008-02-15 12:44 UTC (permalink / raw)
To: ecos-discuss
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ECOS] Re: Public CVS ecos/images woe.
2008-02-15 12:44 [ECOS] Public CVS ecos/images woe Sergei Organov
@ 2008-02-15 13:24 ` Daniel Néri
2008-02-15 14:02 ` Sergei Organov
2008-02-15 15:27 ` [ECOS] " Andrew Lunn
1 sibling, 1 reply; 5+ messages in thread
From: Daniel Néri @ 2008-02-15 13:24 UTC (permalink / raw)
To: ecos-discuss
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [ECOS] Public CVS ecos/images woe.
2008-02-15 12:44 [ECOS] Public CVS ecos/images woe Sergei Organov
2008-02-15 13:24 ` [ECOS] " Daniel Néri
@ 2008-02-15 15:27 ` Andrew Lunn
2008-02-15 16:36 ` [ECOS] " Sergei Organov
1 sibling, 1 reply; 5+ messages in thread
From: Andrew Lunn @ 2008-02-15 15:27 UTC (permalink / raw)
To: Sergei Organov; +Cc: ecos-discuss
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* [ECOS] Re: Public CVS ecos/images woe.
2008-02-15 15:27 ` [ECOS] " Andrew Lunn
@ 2008-02-15 16:36 ` Sergei Organov
0 siblings, 0 replies; 5+ messages in thread
From: Sergei Organov @ 2008-02-15 16:36 UTC (permalink / raw)
To: ecos-discuss
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-02-15 16:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-15 12:44 [ECOS] Public CVS ecos/images woe Sergei Organov
2008-02-15 13:24 ` [ECOS] " Daniel Néri
2008-02-15 14:02 ` Sergei Organov
2008-02-15 15:27 ` [ECOS] " Andrew Lunn
2008-02-15 16:36 ` [ECOS] " Sergei Organov
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).