linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Wise <pabs3@bonedaddy.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Krzysztof Opasiak <k.opasiak@samsung.com>,
	Matt Porter <mporter@kernel.crashing.org>,
	Andrzej Pietrasiewicz <andrzej.p@collabora.com>,
	Karol Lewandowski <k.lewandowsk@samsung.com>,
	linux-usb@vger.kernel.org
Subject: Re: proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation?
Date: Wed, 20 Jan 2021 23:39:22 +0800	[thread overview]
Message-ID: <42c4ad2fa7709312b7ac7bc682f05ed1a3edc9a7.camel@bonedaddy.net> (raw)
In-Reply-To: <YAhKAiz2U9KQWQPE@kroah.com>

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

On Wed, 2021-01-20 at 16:19 +0100, Greg Kroah-Hartman wrote:

> If you can get the "owners" of these repos to agree, than sure.

Excellent, please invite these GitHub users to the linux-usb admin
list, so that they can move the projects if they want to.

Matt Porter: @ohporter (for libusbg)
Krzysztof Opasiak: @kopasiak (for libusbgx, gt)
Karol Lewandowski: @lmctl (for gadgetd)
Andrzej Pietrasiewicz: @andrzejtp (for cmtp-responder)

If you would like to invite me too, I'm @pabs3 on GitHub.

I expect some other folks on linux-usb might like to join too.

> But we should work out the libusbg and libusbx issue, which is really
> the "latest" one?

libusbgx is a fork of libusbg and is more recently updated.

I'd suggest to also move libusbg and archive it (make it read-only).

> If you are moving the repos, why do you care about the issue and pull
> request database anymore?  Will they just not end up going away?

When moving projects (as opposed to forking them), GitHub moves
everything along with the git repo, including issues and pull requests.

-- 
bye,
pabs

https://bonedaddy.net/pabs3/

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

  parent reply	other threads:[~2021-01-20 15:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210119200737eucas1p12bfb53d11543ee2ccb1a4bc2138f6535@eucas1p1.samsung.com>
2021-01-19 20:06 ` proposal: move Linux userspace USB gadget projects to linux-usb GitHub organisation? Paul Wise
2021-01-19 20:15   ` Krzysztof Opasiak
2021-01-20 11:58     ` Andrzej Pietrasiewicz
2021-01-20 15:19   ` Greg Kroah-Hartman
2021-01-20 15:34     ` Michael Sweet
2021-01-20 15:39     ` Paul Wise [this message]
2021-01-25 15:02       ` Michael Grzeschik
2021-02-05 23:35     ` Paul Wise
2021-02-06 13:14       ` Greg Kroah-Hartman
2021-02-06 23:28         ` Paul Wise
2021-02-14  2:17           ` Paul Wise
2021-02-15  9:53             ` Andrzej Pietrasiewicz
2021-02-15 10:07               ` Greg Kroah-Hartman
2021-02-15 10:31                 ` Krzysztof Opasiak
2021-02-25 13:24             ` Paul Wise
2021-02-26 19:24               ` Mike Sweet
2021-02-27  1:08                 ` Paul Wise
2021-02-27  1:54                   ` Michael Sweet
2021-07-13  3:43   ` Paul Wise
2021-07-13  4:53     ` Greg KH
2021-07-13  5:40       ` Paul Wise
2021-07-13  6:37         ` Greg KH
2021-07-14  2:11           ` Paul Wise

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=42c4ad2fa7709312b7ac7bc682f05ed1a3edc9a7.camel@bonedaddy.net \
    --to=pabs3@bonedaddy.net \
    --cc=andrzej.p@collabora.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=k.lewandowsk@samsung.com \
    --cc=k.opasiak@samsung.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mporter@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).