public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike@sf-mail.de>
To: gentoo-dev@lists.gentoo.org, net-mail@gentoo.org
Subject: Re: [gentoo-dev] What is the source for https://dev.gentoo.org/~hollow/distfiles/genqmail-*
Date: Thu, 10 Oct 2019 14:48:42 +0200	[thread overview]
Message-ID: <3872637.HkGNQo7gty@daneel.sf-tec.de> (raw)
In-Reply-To: <7c7759a24cf550462a2be8ed65053fdf6627c4d2.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

> > > > Please pick this up and move it somewhere into Gentoo git
> > > > infrastructure. I can transfer ownership to the Github Gentoo
> > > > organization if you would like.
> > > > Afterwards I just need someone to push the button and create a new
> > > > snapshot from that (preferably together with a git tag).
> > > 
> > > Is there really a reason to do that? Since you're maintaining it, just
> > > keep
> > > it on your gh.
> > 
> > I just want to prevent that the same thing happens again.
> 
> I don't see a difference between a stale repo on your GitHub account
> and a stale repo on Gentoo Infra.  Except the former is easy to fork,
> and the latter we have in dozens, and nobody knows what to do with them.

Then let's at least move it into the Gentoo org on GitHub and give me push 
access like it is for tatt.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2019-10-10 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21  8:50 [gentoo-dev] What is the source for https://dev.gentoo.org/~hollow/distfiles/genqmail-* Rolf Eike Beer
2019-10-10  9:39 ` Rolf Eike Beer
2019-10-10 10:15   ` Michał Górny
2019-10-10 10:31     ` Rolf Eike Beer
2019-10-10 12:16       ` Michał Górny
2019-10-10 12:48         ` Rolf Eike Beer [this message]
2019-10-10 12:55           ` Michał Górny

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=3872637.HkGNQo7gty@daneel.sf-tec.de \
    --to=eike@sf-mail.de \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=net-mail@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox