32
LLVM is deciding on linear Git history vs. merge commits
source link: https://www.tuicool.com/articles/hit/N7Ffaa2
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
[llvm-dev] [Github] RFC: linear history vs merge commits
Tom Stellard via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 29 14:33:41 PST 2019- Previous message: [llvm-dev] Finding label of basic block where a conditional branch merges
- Next message: [llvm-dev] [Github] RFC: linear history vs merge commits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, As part of the migration of LLVM's source code to github, we need to update our developer policy with instructions about how to interact with the new git repository. There are a lot of different topics we will need to discuss, but I would like to start by initiating a discussion about our merge commit policy. Should we: 1. Disallow merge commits and enforce a linear history by requiring a rebase before push. 2. Allow merge commits. 3. Require merge commits and disallow rebase before push. I'm going to propose that if we cannot reach a consensus that we adopt policy #1, because this is essentially what we have now with SVN. What does everyone think? Thanks, Tom
- Previous message: [llvm-dev] Finding label of basic block where a conditional branch merges
- Next message: [llvm-dev] [Github] RFC: linear history vs merge commits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK