From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [RFC][PATCH] Rewriting revs in place in push target repository
Date: Sat, 13 Aug 2005 17:55:16 -0700 [thread overview]
Message-ID: <7vwtmpjq17.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050813214725.GM5608@pasky.ji.cz> (Petr Baudis's message of "Sat, 13 Aug 2005 23:47:25 +0200")
Petr Baudis <pasky@suse.cz> writes:
> Rewrite refs in place in receive-pack & friends
>
> When updating a ref, it would write a new file with the new ref and
> then rename it, overwriting the original file. The problem is that
> this destroys permissions and ownership of the original file, which is
> troublesome especially in multiuser environment, like the one I live in.
Hmph. If a repo is _really_ used multiuser then you should not
have to care about ownership. If you can write into a
repository for a project (implying that you are a member of that
project group), and if your umask is set up correctly (meaning
it is 002 or looser), and with g+s bit on the directory at the
repository root level when it was created, shouldn't your newly
created ref file be also writable by others in that project?
next prev parent reply other threads:[~2005-08-14 0:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 21:47 [RFC][PATCH] Rewriting revs in place in push target repository Petr Baudis
2005-08-13 22:20 ` Linus Torvalds
2005-08-14 0:55 ` Junio C Hamano [this message]
2005-08-14 2:10 ` Linus Torvalds
2005-09-15 17:16 ` Petr Baudis
2005-08-14 2:20 ` Chris Wedgwood
2005-08-14 10:02 ` Matthias Urlichs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vwtmpjq17.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).