"McMechan, Jim" wrote:
> <Big Snip>
> > One day we might get the patch process going fast enough, but for now,
> > the message remains that if you really want to follow the development
> > the only real way to do it is to usr the cvs tree.
> >
> > Thanks for the comments, I will reorder the fields in the superblock.
> >
> > Steve
> >
> Unfortunately my firewall at work wants my ip address the (fixed)
> destination ip address and a justification for any connections like CVS;
> This puts a dent in CVS update ease of use.
Not understanding your firewall setup I can't really comment on the
best tunnel through it, but I'm sure your network guru could give you a
working setup.
>
>
> XFS is most useful for server systems and nicer on a T3 link rather than a
> shared 56k modem. At home I can't get WinCVS to handle multiple
> repositories with any ease? (suggestions welcome)
Sorry know nothing of WinCVS, I assume it's a windows version of cvs?
Actually the two must faster methods of grabbing the devel tree
would be to either rsync a local copy of the cvs tree it self, or CVSup
which is the fastest and most efficient way of staying current.
http://linux-xfs.sgi.com/projects/xfs/cvsup.html
rsync -av oss.sgi.com::cvs/linux-2.4-xfs .
Note there is also a cvs "seed" patch in the "patches" directory on oss,
this is rarely current but can take a 2.4.x tree and patch it
into a CVS capable tree that can be make current with
cvs update -d
>
> Have you considered a automated (e.g. cron) snapshot procedure on the ftp
> server. Like the nightly builds at Mozilla.org or sourceforge.net? This
> would "get the patch process going fast enough" and limit the amount of
> update needed since a snapshot could then be updated by CVS.
Given the numerous methods of staying current with the devel tree all
of which are much less of a headache than nightly patches, no probably not.
Patches have their place but they lack any sort of revision tracking.
When tracking down bugs it is crucial for the developer to know which
version of what the user is working with.
Also as a follow up to the 2.4.4-*TEST* patch.
Occasionally I will make patches available for "testing" purposes as
such they are placed in the testing directory as an indication of it's
early unstable status.
--
Russell Cattelan
cattelan@xxxxxxxxxxx
|