From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANN] Rasdaemon main tree moved to git.infradead.org
Date: Tue, 14 Mar 2017 09:13:31 -0300 [thread overview]
Message-ID: <20170314091331.01013e21@vento.lan> (raw)
In-Reply-To: <20170314075623.75e78b79@vento.lan>
Em Tue, 14 Mar 2017 07:56:23 -0300
Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> I was caught by surprise by some weird decision from Fedora to simply
> remove *all* git repositories stored there on March, 1st *without* notifying
> the owners of those repositories:
>
> https://fedoraproject.org/wiki/Infrastructure/Fedorahosted-retirement
>
> Thankfully, someone pinged me today to warn about it. That's said, the
> rasdaemon always had a secondary repository, stored at:
>
> http://git.infradead.org/users/mchehab/rasdaemon.git
>
> So, I'm promoting it to be the main repository for it. I'm still keeping
> rasdaemon tarballs stored at Fedora facilities, at:
> https://mchehab.fedorapeople.org/
Copied everything there to http://www.infradead.org/~mchehab/ and
better organized its contents.
> But I'm seriously considering moving it elsewhere, as I consider
> a disrespect with Rasdaemon users and with me that someone
> decides to simply remove git repositories without a warning.
Ok, I'm now storing the tarballs at:
http://www.infradead.org/~mchehab/rasdaemon/
I'll keep the existing ones at fedorapeople, but I may not update
them there anymore.
Thanks,
Mauro
prev parent reply other threads:[~2017-03-14 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 10:56 [ANN] Rasdaemon main tree moved to git.infradead.org Mauro Carvalho Chehab
2017-03-14 12:13 ` Mauro Carvalho Chehab [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=20170314091331.01013e21@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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