[llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED] (original) (raw)

Tom Stellard via llvm-dev llvm-dev at lists.llvm.org
Fri May 1 13:49:49 PDT 2020

On 05/01/2020 10:06 AM, via llvm-dev wrote:

Please reply to this proposal with your questions, comments, praise, or concerns. I think it's by and large a good plan, but I'd consider it a largely unnecessary wart to copy issues into existing PRs (OP would always have the wrong user, etc.). In a previous mail on this thread there was the proposal for a "bait-and-switch" style approach, which basically branches off from the proposal around step 5, by locking llvm/llvm-project, syncing all branches with llvm-bug-archive, and then deleting llvm-project and renaming the bug archive to llvm-project. I understand that there are unknown unknowns about deleting and replacing the repo in place (maybe those could be allayed by some GH people?), but if that remains a show-stopper, then I was wondering if it has been considered that the new repo could simply just be called llvm/llvm? This would be a nice and short name which is not taken, and then llvm/llvm-project could be archived, and people would only have to change their git remote once. I hope such a suggestion is not seen as sacrilege - my understanding of the llvm-history is hazy at best, but AFAICT the "-project" suffix is not necessary anymore, now that all the subprojects have been absorbed in the monorepo for a while.

I've asked the GitHub developers about the consequences of deleting and renaming another repo, so we'll see what they say.

The llvm/llvm repo name was rejected during the conversion. llvm-project was the name of the svn repo already so there was some consistency here, and it also avoided having too many redundant llvm's which seemed confusing.

-Tom

Best regards H.

LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

More information about the llvm-dev mailing list