git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Nicolas Pitre <nico@cam.org>,
	Jason Sewall <jasonsewall@gmail.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: New repo quickly corrupted
Date: Fri, 16 Nov 2007 08:35:03 +0100	[thread overview]
Message-ID: <473D4827.1060109@op5.se> (raw)
In-Reply-To: <200711160645.04352.chriscool@tuxfamily.org>

Christian Couder wrote:
> Le jeudi 15 novembre 2007, Linus Torvalds a écrit :
>> On Thu, 15 Nov 2007, Nicolas Pitre wrote:
>>> Does "dos2unix" override file access bits?  Because the object store is
>>> always made read-only.
>> Almost all programs like that will entirely ignor the fact that something
>> is read-only.
> 
> What if the .git/objects/ sudirectories were also read-only ?
> 

Then git wouldn't be able to write to it without chmod()'ing it each time.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2007-11-16  7:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 21:50 New repo quickly corrupted Jason Sewall
2007-11-15 21:55 ` Junio C Hamano
2007-11-15 21:59   ` Jason Sewall
2007-11-15 22:01 ` Linus Torvalds
2007-11-15 22:06   ` Jason Sewall
2007-11-15 22:12   ` Nicolas Pitre
2007-11-15 22:37     ` Linus Torvalds
2007-11-16  5:45       ` Christian Couder
2007-11-16  7:35         ` Andreas Ericsson [this message]
2007-11-17 12:53           ` Christian Couder
2007-11-17 14:13             ` Robin Rosenberg

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=473D4827.1060109@op5.se \
    --to=ae@op5.se \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jasonsewall@gmail.com \
    --cc=nico@cam.org \
    --cc=torvalds@linux-foundation.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).