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 at 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 at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200708/6504d34a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3852 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200708/6504d34a/attachment.bin>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4