On Wed, May 9, 2012 at 7:57 AM, ceki <ceki@qos.ch> wrote:

On 09.05.2012 13:03, Tony Trinh wrote:

That indeed looks interesting, but it sounds like it creates an
independent repo (removes the fork status of logback-android)...or am I
mistaken? I need it to be a fork so that I can easily merge updates from
qos-ch/logback.

Good point. I am at loss for more ideas. I guess you should contact github support asking them to help you transfer logback-android.

I got a response from support. Unfortunately, GitHub currently does not allow an account (or an organization) to fork its own repos. I think it's best for logback-android to remain a fork, so that means it has to be outside of the qos-ch organization.