On 07.05.2012 02:25, Tony Trinh wrote:
On Sun, May 6, 2012 at 11:54 AM, ceki <[email protected] <mailto:[email protected]>>
wrote:
For logback-android, as it's a fork of ceki/logback but already
bound to the target account, we need to contact support [1].
Ok. I assume logback-android will then be a fork of qos.ch/logback
<http://qos.ch/logback> instead of ceki/logback.
Have you contacted support already? Do I need to do anything for this
process?
Tony,
Actually yes, there is something you could do. Given the exchange I
had with github support (see below) could you please transfer the
qos-ch/logback-android repo back to tony19/ and once the move of
ceki/logback to qos-ch/logbaclk is done, retransfer
tony19/logback-android back to qos-ch/. Does it make sense?
Cheers,
--
Ceki
http://twitter.com/#!/cek
-----------------------------------------------------------------
Message sent to github support:
Hello github,
I am trying to transfer ownership of the the
https://github.com/ceki/logback repo to
https://github.com/qos-ch/logback. Unfortunately, the move is denied
with the message "qos-ch already has a repo in the ceki/logback
network". I presume this is due to the
https://github.com/qos-ch/logback-android repository which is a fork
of ceki/logback.
What are we missing? Many thanks in advance for your help,
Github's answer:
From: Tekkub (GitHub Staff)
Subject: Moving ceki/logback to
https://github.com/organizations/qos-ch/logback
That's correct, the fork must be removed to do the transfer. If you'd
rather the fork become the primary repo, we can switch the network's
root repo around for you.
------------------------------------------------------------------------
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
