From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Olaf Hering <olh@suse.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.6
Date: Mon, 10 May 2004 09:48:14 +0100 [thread overview]
Message-ID: <20040510094814.B27524@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040510083905.GA18603@suse.de>; from olh@suse.de on Mon, May 10, 2004 at 10:39:05AM +0200
On Mon, May 10, 2004 at 10:39:05AM +0200, Olaf Hering wrote:
> On Sun, May 09, Linus Torvalds wrote:
> > Holler if I missed anything,
>
> add 'chmod -Rf a+rX,o-w,g-w .' to your release scripts.
That's not really a fix. These need to be reported as they occur
since it's BK which stores the permissions.
Maybe we can add a BK trigger to correct/fix/warn of this problem
on checkin ?
Meanwhile I'll fix up the following six:
> cp: cannot open `linux-2.6.6/arch/arm/mm/proc-v6.S' for reading: Permission denied
> cp: cannot open `linux-2.6.6/arch/arm/mm/cache-v6.S' for reading: Permission denied
> cp: cannot open `linux-2.6.6/arch/arm/mm/abort-ev6.S' for reading: Permission denied
> cp: cannot open `linux-2.6.6/arch/arm/mm/copypage-v6.c' for reading: Permission denied
> cp: cannot open `linux-2.6.6/arch/arm/mm/tlb-v6.S' for reading: Permission denied
> cp: cannot open `linux-2.6.6/arch/arm/mm/blockops.c' for reading: Permission denied
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-05-10 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 2:58 Linux 2.6.6 Linus Torvalds
2004-05-10 8:39 ` Olaf Hering
2004-05-10 8:48 ` Russell King [this message]
2004-05-10 10:40 ` Dave Jones
2004-05-10 10:49 ` Olaf Hering
2004-05-10 10:51 ` Daniele Venzano
2004-05-10 15:11 ` Linus Torvalds
2004-05-10 16:39 ` Daniele Venzano
2004-05-10 20:44 ` Tomas Szepe
2004-05-11 13:34 ` Mark Mielke
2004-05-10 13:27 ` David Eger
2004-05-10 14:58 ` Roland Dreier
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=20040510094814.B27524@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.