All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Christian Aistleitner <christian@quelltextlich.at>
Cc: Mike Frysinger <vapier@gentoo.org>,
	"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
	John Marshall <John.W.Marshall@glasgow.ac.uk>
Subject: Re: Man-pages Git repository
Date: Sat, 4 Jun 2022 03:26:41 +0200	[thread overview]
Message-ID: <8a672358-07d0-3a64-30b0-5e25a46f1b80@gmail.com> (raw)
In-Reply-To: <a3a53704-84fe-7fc8-55d4-46094dc38ef2@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

Hi Christian,

On 3/22/22 12:44, Alejandro Colomar (man-pages) wrote:
>> P.S.: If you think that yet-another-linux-man-pages-repo-on-GitHub is
>> counter-productive or you object to have your server queried for new
>> commits every hour, please let me know and I'll tear that repo down
>> again.
> 
> a) Not really, and that's your decision.  But if you ask me, if I have 
> to choose between (too) many forks/mirrors, or just a single source of 
> truth, I prefer many.  When things go wrong, mirrors/forks save the world.
> 
> b) Nah, I don't mind that kind of traffic.  Go ahead.  What I don't 
> promise is that my server will respond always; I may turn it off for 
> maintenance without notice.


I now have push access to kernel.org, and pushed all of my commits (for 
now to a branch called alx/main, and soon to master).  To me it's fine 
if you keep the github mirror of my personal server.  Just noticing you 
that the reason it originated is fading and you way want to save a few 
cents on electricity and/or maintenance, and stop that script :)


Cheers,

Alex

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-04  1:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 13:14 Man-pages Git repository John Marshall
2022-03-16 17:27 ` Alejandro Colomar (man-pages)
2022-03-21 21:14   ` Mike Frysinger
2022-03-21 22:55     ` Alejandro Colomar (man-pages)
2022-03-22  9:49       ` Christian Aistleitner
2022-03-22 11:44         ` Alejandro Colomar (man-pages)
2022-06-04  1:26           ` Alejandro Colomar [this message]
2022-06-04 11:43             ` Christian Aistleitner

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=8a672358-07d0-3a64-30b0-5e25a46f1b80@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=John.W.Marshall@glasgow.ac.uk \
    --cc=christian@quelltextlich.at \
    --cc=linux-man@vger.kernel.org \
    --cc=vapier@gentoo.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 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.