From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.14
Date: Sat, 05 Nov 2005 13:37:16 -0500 [thread overview]
Message-ID: <436CFBDC.8060509@pobox.com> (raw)
In-Reply-To: <1131215595.3614.13.camel@mulgrave>
James Bottomley wrote:
> On Sat, 2005-11-05 at 13:25 -0500, Jeff Garzik wrote:
>
>>Do you have standard permissions (chmod -R og+rX) on your repo, and, are
>>you using rsync to push to kernel.org?
>>
>>I've attached my rsync-based push script. git people seem to dislike
>>rsync, but this tends to work every time, for all users.
>
>
> No, I push to my scsi-misc-2.6 repository and then clone that on hera
> for linus. the scsi-misc-2.6 permissions are fine, it was the clone -l
> on hera that caused the problems.
Well, _something_ is clearly screwed up in your scsi-misc-2.6 repo on
master.kernel.org, as its the only repo that I cannot pull from (last
successful pull was Oct 31, before I left for Portland).
Jeff
next prev parent reply other threads:[~2005-11-05 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 16:18 [GIT PATCH] SCSI updates for 2.6.14 James Bottomley
2005-11-05 17:44 ` Linus Torvalds
2005-11-05 18:13 ` James Bottomley
2005-11-05 18:25 ` Jeff Garzik
2005-11-05 18:33 ` James Bottomley
2005-11-05 18:37 ` Jeff Garzik [this message]
[not found] ` <Pine.LNX.4.64.0511051031250.3316@g5.osdl.org>
[not found] ` <1131216913.3614.15.camel@mulgrave>
2005-11-05 19:32 ` Linus Torvalds
2005-11-08 23:35 ` Dave C Boutcher
2005-11-09 5:09 ` Christoph Hellwig
2005-11-09 15:07 ` Dave C Boutcher
2005-11-09 18:30 ` Mike Christie
2005-11-09 18:35 ` Mike Christie
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=436CFBDC.8060509@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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.