From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: error trying to fetch the clockevents tree
Date: Thu, 15 May 2025 11:20:01 +0200 [thread overview]
Message-ID: <ba3ff719-ce60-4c0f-a215-fa332b614b82@linaro.org> (raw)
In-Reply-To: <db7fce1c-c051-41d9-9cf1-ef015b0f7fb4@linaro.org>
Hi Stephen,
On 4/29/25 00:35, Daniel Lezcano wrote:
> On 29/04/2025 00:20, Stephen Rothwell wrote:
>> Hi all,
>>
>> Fetching the clockevents tree produces this error:
>>
>> fatal: unable to access 'https://git.linaro.org/people/daniel.lezcano/
>> linux.git/': The requested URL returned error: 503
>
> Seems like there is some issues with the servers recently.
>
> Could you please disable the tree while I migrate it to kernel.org ?
I had no time yet to migrate the git tree to kernel.org but the servers
seem to work correctly now.
Is it possible to enable back the tree so its content gets some round in
linux-next before the PR ?
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2025-05-15 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 22:20 linux-next: error trying to fetch the clockevents tree Stephen Rothwell
2025-04-28 22:35 ` Daniel Lezcano
2025-04-28 22:49 ` Stephen Rothwell
2025-05-15 9:20 ` Daniel Lezcano [this message]
2025-05-15 12:10 ` Stephen Rothwell
2025-05-15 12:11 ` Daniel Lezcano
2025-05-20 17:23 ` Daniel Lezcano
2025-05-20 22:47 ` Stephen Rothwell
2025-05-20 22:59 ` Daniel Lezcano
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=ba3ff719-ce60-4c0f-a215-fa332b614b82@linaro.org \
--to=daniel.lezcano@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox