From: Linus Torvalds <torvalds@osdl.org>
To: Jan Harkes <jaharkes@cs.cmu.edu>, Peter Anvin <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Careful object writing..
Date: Tue, 3 May 2005 15:37:36 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505031531270.26698@ppc970.osdl.org> (raw)
In-Reply-To: <20050503200034.GA16104@delft.aura.cs.cmu.edu>
On Tue, 3 May 2005, Jan Harkes wrote:
>
> I tried to pull in the latest version of your tree, but it doesn't look
> like this commit has propagated to rsync.kernel.org yet.
Hmm.. It's still not there a few hours later. I wonder what the mirroring
rules are. Or maybe mirroring is just broken right now. Peter?
One change introduced by me is that the new objects changed from 0664
(-rw-rw-r--) to (0444) -r--r--r-- due to the object writing rules. Maybe
the mirroring decides that such objects shouldn't be mirrored, since they
are "private"?
Or maybe it's just that Peter has shut down mirroring in preparation for
the imminent memory upgrade on master.kernel.org.
Linus
next prev parent reply other threads:[~2005-05-03 22:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 19:15 Careful object writing Linus Torvalds
2005-05-03 19:27 ` Chris Wedgwood
2005-05-03 19:47 ` Linus Torvalds
2005-05-03 19:47 ` Chris Wedgwood
2005-05-03 19:56 ` Linus Torvalds
2005-05-03 20:02 ` Daniel Barkalow
2005-05-03 20:00 ` Jan Harkes
2005-05-03 20:11 ` Linus Torvalds
2005-05-03 20:59 ` Jan Harkes
2005-05-03 22:13 ` Linus Torvalds
2005-05-03 22:37 ` Linus Torvalds [this message]
2005-05-03 22:40 ` H. Peter Anvin
2005-05-03 23:04 ` Alex Riesen
2005-05-03 23:22 ` Linus Torvalds
2005-05-03 23:25 ` Alex Riesen
2005-05-03 23:22 ` Junio C Hamano
2005-05-04 4:07 ` [PATCH] Careful object pulling Daniel Barkalow
2005-05-04 9:35 ` Morten Welinder
2005-05-04 16:16 ` Daniel Barkalow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0505031531270.26698@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=jaharkes@cs.cmu.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).