From: Michal Simek <monstr@monstr.eu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error fetching the microblaze tree
Date: Tue, 06 Jan 2015 12:30:04 +0100 [thread overview]
Message-ID: <54ABC73C.9050802@monstr.eu> (raw)
In-Reply-To: <20150106221156.060946b3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On 01/06/2015 12:11 PM, Stephen Rothwell wrote:
> Hi Michal,
>
> On Tue, 06 Jan 2015 07:48:53 +0100 Michal Simek <monstr@monstr.eu> wrote:
>>
>> sorry for trouble. Server has been moved to 92.62.235.6.
>> I have changed DNS record but it takes some time to update
>> it that's why you can't reach it. :-( It will be fixed soon
>> I believe.
>
> No worries, I was just letting you know in case there was something you
> were not aware of. I have just done a fetch and it worked fine, so
> things will be back to normal in tomorrows release.
Great.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-01-06 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 23:03 linux-next: error fetching the microblaze tree Stephen Rothwell
2015-01-06 6:48 ` Michal Simek
2015-01-06 11:11 ` Stephen Rothwell
2015-01-06 11:30 ` Michal Simek [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=54ABC73C.9050802@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.