From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Does GIT require property like Subversion?
Date: Sun, 08 Oct 2006 18:40:20 +0200 [thread overview]
Message-ID: <egb9js$1sk$1@sea.gmane.org> (raw)
In-Reply-To: 20061008162410.GK20017@pasky.or.cz
Petr Baudis wrote:
> Dear diary, on Sun, Oct 08, 2006 at 05:52:10PM CEST, I got a letter
> where Robin Rosenberg <robin.rosenberg.lists@dewire.com> said that...
>> söndag 08 oktober 2006 12:16 skrev Jakub Narebski:
>>> But in fact the philosophy of Git _prohibits_ I think property bits.
>> I don't think so, but they aren't needed for the original purpose. Git
>> already does manage file permissions.
>
> Incorrect, Git manages only the execute bit.
And symlinks.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-08 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 9:10 Does GIT require property like Subversion? Liu Yubao
2006-10-08 9:19 ` Jan-Benedict Glaw
2006-10-08 10:16 ` Jakub Narebski
2006-10-08 10:26 ` Jakub Narebski
2006-10-08 15:52 ` Robin Rosenberg
2006-10-08 16:24 ` Petr Baudis
2006-10-08 16:40 ` Jakub Narebski [this message]
2006-10-09 2:53 ` Liu Yubao
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='egb9js$1sk$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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).