(original) (raw)
The downsides of an additional project are small. I can see:
1) It's not possible to do pull requests from there, because GitHub won't treat it as a fork.
2) It's still visible to people (http://lists.llvm.org/pipermail/llvm-dev/2020-June/142559.html)
In the end I don't have a strong opinion on whether this is a branch or a repository, as long as we move ahead soon.
On Thu, Jul 2, 2020 at 4:29 PM Johannes Doerfert via llvm-dev <llvm-dev@lists.llvm.org> wrote:
On 6/30/20 4:02 PM, Duncan Exon Smith via llvm-dev wrote:
\> Regardless, if a separate repo is preferred, then a better name from our perspective would be "llvm-project-staging" (dropping the "-apple" suffix). We could push a "staging/apple" branch there.
+1 for a separate repo with a neutral name and "company" branches.
\* Unlikely we spam people
\* Easy to understand from the github page
\* Invisible to the existing users of llvm-project/llvm
\* Unlikely to confuse people that have or download llvm (=accidental
build of staging/apple)
I haven't really seen a downside, though I might have missed something.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
LLVM Developers mailing list
llvm-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev