Re: [Gnu-arch-users] Some issues

[Colin Walters]

On Wed, 2004-06-09 at 15:22, Florian Weimer wrote:

> This is not a real barrier.  AFAIK, SFTP exposes the whole file system
> without restrictions.  This probably means that local vulnerabilities
> can well turn into remote ones.

Fine, so run a ssh server on a different port and have the sftp
subsystem be in a chroot.

> rssh probably doesn't support the SFTP subsystem (i.e. it's not
> possible to add further restrictions to the paths you can access).

That's correct.

> WebDAV could be an option, but there aren't any implementations which
> one could consider lightweight AFAIK.

And this translates into "tla doesn't support centralized development"?!

> Uh-oh.  This needs a global view and thus is very hard to do.

But it's generally automatable.

> For GCC, this means that most patchlogs cannot be removed until the
> branch is officially dead (not only unmaintained, but really dead).
> Currently, GCC 3.2, 3.3, 3.4 and of course HEAD are still in
> development.  A sizable number of patch logs has to live for years.

It depends on the merge style.  For example, if you use star-merge, then
I believe you only need to keep the most recent patch log.  However for
missing/replay style merging - yes, you need to keep the whole history.

> But I'll lurk a bit on the Rhythmbox mailing list...

We don't actually discuss arch much there, becuase we haven't had any
problems with it really.  But feel free to lurk :)

The archive is here:
http://mail.gnome.org/archives/rhythmbox-devel/

But searching is broken at the moment.

signature.asc
Description: This is a digitally signed message part