Hello.
Some time ago, https://github.com/llvm/apple-llvm-project-staging appeared.
I do not recall seeing any discussions about it (especially before the
fact) here.
It is a standalone repository, not a fork, therefore github wrongfully counts
everyones commits twice - once in the proper repo, and once in there.
That can not be worked around, as far as i understand.
So, why is it there in the first place?
Why was there no discussion about it?
Why is it not in Apple · GitHub ?
Can it be moved in the right place?
Roman.
Hey Duncan - perhaps you know something about this? (given the recent
thread on adding an apple branch for upstreaming purposes)
There’s an email thread at this point 
-eric
There's an email thread at this point
You mean http://lists.llvm.org/pipermail/llvm-dev/2020-July/142951.html
? I wasn't sure that was directly related - since that thread seems to
be asking for permission/buy-in to /add/ a branch, it doesn't (based
on my reading at least) talk about any pre-existing branch, which is
what Roman seems to be asking about?
So I'm not sure if they're related or not.
- Dave
Yep. That thread. It got there eventually around this branch as well. It’s a… long thread at this point.
-eric
Yep. That thread. It got there eventually around this branch as well. It's a... long thread at this point.
*nod* I think I've read it all - and don't see mention of this
subproject/fork/thingy. (& that entire thread occurred after (June
29th) this email from Roman (June 21st) - and was seeking permission,
not asking about a pre-existing fork)). Chris proposed a possible fork
name ("I don’t have a opinion on this either way, but can git/GitHub
maintain forks within the same organization? You could have
llvm/llvm-project and llvm/llvm-project-apple-staging or something
like that?") but it's not the one that's already there/Roman's asking
about (almost the same, though): apple-llvm-project-staging.
So I'm still confused, at least.
Perhaps someone accidentally pushed this branch while trying to
prototype ideas before sending the proposal?
- Dave
Yep. That thread. It got there eventually around this branch as well. It's a... long thread at this point.
*nod* I think I've read it all - and don't see mention of this
subproject/fork/thingy. (& that entire thread occurred after (June
29th) this email from Roman (June 21st) - and was seeking permission,
not asking about a pre-existing fork)). Chris proposed a possible fork
name ("I don’t have a opinion on this either way, but can git/GitHub
maintain forks within the same organization? You could have
llvm/llvm-project and llvm/llvm-project-apple-staging or something
like that?") but it's not the one that's already there/Roman's asking
about (almost the same, though): apple-llvm-project-staging.
So I'm still confused, at least.
Perhaps someone accidentally pushed this branch while trying to
prototype ideas before sending the proposal?
This was a repo I created as a landing spot for the Apple patches
that were discussed in the recent mailing list thread. We eventually
decided this was the wrong approach and that the issue should be brought
before the community for discussion. The repo is gone now, sorry for the confusion.
- Tom
>>
>> Yep. That thread. It got there eventually around this branch as well. It's a... long thread at this point.
>
> *nod* I think I've read it all - and don't see mention of this
> subproject/fork/thingy. (& that entire thread occurred after (June
> 29th) this email from Roman (June 21st) - and was seeking permission,
> not asking about a pre-existing fork)). Chris proposed a possible fork
> name ("I don’t have a opinion on this either way, but can git/GitHub
> maintain forks within the same organization? You could have
> llvm/llvm-project and llvm/llvm-project-apple-staging or something
> like that?") but it's not the one that's already there/Roman's asking
> about (almost the same, though): apple-llvm-project-staging.
>
> So I'm still confused, at least.
>
> Perhaps someone accidentally pushed this branch while trying to
> prototype ideas before sending the proposal?
>
This was a repo I created as a landing spot for the Apple patches
that were discussed in the recent mailing list thread. We eventually
decided this was the wrong approach and that the issue should be brought
before the community for discussion. The repo is gone now, sorry for
the confusion.
Cool, no worries - thanks for the context & cleanup!