also sprach David Kastrup <dak@xxxxxxx> [2007.08.23.0812 +0200]:
> The modes are recorded in patches and push/pull, so if you have
> several people working with different permissions/umasks, you get
> wagonloads of unnecessary patches and get your local permissions
> messed up by other contributors.
>
> For colloborative work, you _really_ don't want to have _personal_
> preferences distributed.
How about a patch that
(a) ensures that modes of existing files are preserved
across checkouts and merges?
(b) for files it creates (e.g. checkout of a branch introducing
a file), it consults the default for this file tracked in the
archive and uses that.
(c) in order to change the mode recorded for a file, a user has to
tell git-add to specifically record the mode change in the
index.
There should be a tri-state policy: mode-from-archive vs. umask, and
umask could be according to core.umask or if that's set to user,
then the user's umask.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
"the only difference between shakespeare and you
was the size of his idiom list -- not the size of his vocabulary."
-- alan perlis
spamtraps: madduck.bogus@xxxxxxxxxxx
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
