From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [patch hail 1/2] Add subdomain calling format
Date: Tue, 7 Dec 2010 10:00:24 -0700 [thread overview]
Message-ID: <20101207100024.28cdebed@lembas.zaitcev.lan> (raw)
In-Reply-To: <4CFE06F2.5050108@garzik.org>
On Tue, 07 Dec 2010 05:05:38 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> On 12/05/2010 10:53 PM, Pete Zaitcev wrote:
> > Amazon appears to give up on forcing users to migrate and bucket-in-path
> > format is going to stay. However, they still refuse to list buckets from
> > other regions on the default endpoint, which leads to annoying indirection
> > (need to know the region somehow before listing). Easier just use the
> > subdomain format in one invocation.
> applied 1-2
Thanks. I eventually got around this by calling buckets foo-west,
foo-east, but might as well just have this.
-- Pete
prev parent reply other threads:[~2010-12-07 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 3:53 [patch hail 1/2] Add subdomain calling format Pete Zaitcev
2010-12-07 10:05 ` Jeff Garzik
2010-12-07 17:00 ` Pete Zaitcev [this message]
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=20101207100024.28cdebed@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.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 read-only IMAP folder(s) and NNTP newsgroup(s).