This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] FUSE 2.8


Corinna Vinschen wrote:
On Jul 29 11:48, Corinna Vinschen wrote:
On Jul 29 02:15, Mark Geisert wrote:
Corinna Vinschen wrote:
On Jul 29 01:19, Mark Geisert wrote:
Bill Zissimopoulos wrote:
On 7/28/16, 5:17 PM, Bill Zissimopoulos wrote:
Ok. I did the transfer (twice, because of some ambiguous GitHub messages).
Someone from cygwin’s side has to accept the repo within a day according
to GitHub.

Turns out I can transfer a repo to another user, but not to an
organization that I do not have admin rights for:

   From github’s transfer repo instructions:
<<
Transfer this repository to another user or to an organization where you
have admin rights.



FWIW I've signed up with GitHub with username mgeisert.  I think I need to
be invited to join the cygwin@github org.  Then maybe I can transfer your
repo to me?  Corrections welcome...

I invited you with email mark AT maxrnd DOT com

There appears to be a user account called mgeisert, but it has no further
info attached, not even a name.

Thanks Corinna, I've accepted the invite and filled in my profile a bit.
How would I/we accept the repo as Bill mentions above?  Then I guess a
transfer needs to be done after that?

I really don't know, sorry.  I'm not actually using github a lot since
the cygwin repo is only mirrored to github.  I'd guess there's some
kind of documentation on github explaining stuff like that...?

Mark, did you find out how to move the repo under the Cygwin org
in the meantime?  Is it the "Import repository" functionality by
any chance?

Hi Corinna,
Bill and I worked it out on a different thread of this conversation. I currently have a public repo mgeisert/cygfuse on GitHub. That seemed to be sufficient to me as maintainer. Does it need to be moved under cygwin/ ? If yes, it looks like "Import Repository" is a way to do it.

I was planning to make sure the package Bill supplied met all the requirements for a Cygwin package. I figure it's real close but there was something I wasn't sure about and needed to research further, then real life intervened. Something to do with where its cygport file was getting package source from.

..mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]