[Gnu-arch-users] Re: multiple committers, again

[Stefan Monnier]

>> If there was some kind of context that was detectable in a
>> startup file that said "this is a tla ssh session" then I could
>> set umask accordingly and that would work fine, and it wouldn't
>> compromise every other use of that startup file.

> I can think of half a dozen different ways to do it just offhand. You
> aren't even trying.

Hopefully it should be possible to set things up without having to think too
hard first.  E.g. by following some instructions.

I for one have no idea how to change the umask used when I access my
archive via sftp.  Googling indicates this was discussed here with
suggestions like sftp%umask=XXX:/foo/bar/baz (which I must say doesn't
sound right: the umask setting should be in the archive itself, so as to
make sure noone creates stuff with the wrong umask by mistake).

But is it necessary to change one's umask just to commit?
After all, committing should only need to create an immutable changeset
and add it to a preexisting directory, so nothing it creates needs to be
writable, right?  Or is it due to locking?

I think the page http://wiki.gnuarch.org/moin.cgi/Centralized_20Development
is pretty confusing in that it lists several options without making it quite
clear why there needs to be several options.  E.g. who'd bother patching
ssh when you can do without it?


        Stefan