4 ms·

>I think I’d take that bet. Becoming idiot proof isn’t hard. The trick is for all commits to be automatically backed up in the central hub. That's the last thi

>I think I’d take that bet. Becoming idiot proof isn’t hard. The trick is for all commits to be automatically backed up in the central hub. That's the last thing I want. Random WIP commits being sent off to some central hub? Fuck that, man. Fuck that. >And for commits to be locked and stable once made. Git’s ability to re-write history is, imho, a huge mistake and I don’t think actually necessary to support Linux. Flattening on PR merge doesn’t require a rewrite. Being able to re-write history is absolutely necessary. I seriously doubt you've ever looked at a patch series posted for any free software project if you say that rewriting history isn't necessary. To put it quite simply: my data is under my control. I can do whatever I want with it. I commit frequently because it is useful to be able to go back in history through changes as I make them. For the purpose of publication, it is not useful to see the various stages I went through when thinking about how to solve a problem. That's not what git history is for. It's for presenting a logical series of changes in a way that is easy to understand and bisect. Flattening on 'PR merge' is abysmal. I don't want one massive commit. I want a series of logical commits.

lentil_soup 3y ago
But in Perforce you can have your own private branch, in practice it feels not much different than having a local git one. You can then merge to main as you want.
forrestthewoods 3y ago
> That's the last thing I want. Random WIP commits being sent off to some central hub? Fuck that, man. Fuck that. This is where you’re objectively wrong. I have this feature available to me today. It’s a killer feature. It’s amazing. Having it has zero downsides. Not having it is a pain in the ass and makes life worse. Imagine this. You’re working at a company with thousands of engineers. Everyone is making stacks and stacks of local commits. At various points in time people push their commit(s) to code review. If approved it gets merged into master. Now imagine if anyone could check out any commit from any employee just by typing “git checkout #####”. That’s it. That’s the feature. If you browse the repo it is perfectly clean. There’s no dirt or noise. This includes letting you checkout your own commit on one of your five different machines/platforms/cloud servers without having to push or pull or any of that shit. Commit on one machine and checkout on another. It’s pure automagic. > Flattening on 'PR merge' is abysmal. I don't want one massive commit. I want a series of logical commits. Sure fine. Shape the series of commits however you want. As few or as many as you want. With nice clean messages. The world is your oyster. But those are new commits. The initial commits should be, imho, unaltered (and unmerged). They can be GC’d months/years down the road if needed.
- memefrog 3y ago
  >Imagine this. You’re working at a company with thousands of engineers. No, I don't think I will. No problem requires thousands of programmers.
  - forrestthewoods 3y ago
    Really? That’s your response? You were mostly giving thoughtful replies. How disappointing.

lentil_soup 3y ago

But in Perforce you can have your own private branch, in practice it feels not much different than having a local git one. You can then merge to main as you want.

forrestthewoods 3y ago

> That's the last thing I want. Random WIP commits being sent off to some central hub? Fuck that, man. Fuck that. This is where you’re objectively wrong. I have this feature available to me today. It’s a killer feature. It’s amazing. Having it has zero downsides. Not having it is a pain in the ass and makes life worse. Imagine this. You’re working at a company with thousands of engineers. Everyone is making stacks and stacks of local commits. At various points in time people push their commit(s) to code review. If approved it gets merged into master. Now imagine if anyone could check out any commit from any employee just by typing “git checkout #####”. That’s it. That’s the feature. If you browse the repo it is perfectly clean. There’s no dirt or noise. This includes letting you checkout your own commit on one of your five different machines/platforms/cloud servers without having to push or pull or any of that shit. Commit on one machine and checkout on another. It’s pure automagic. > Flattening on 'PR merge' is abysmal. I don't want one massive commit. I want a series of logical commits. Sure fine. Shape the series of commits however you want. As few or as many as you want. With nice clean messages. The world is your oyster. But those are new commits. The initial commits should be, imho, unaltered (and unmerged). They can be GC’d months/years down the road if needed.

memefrog 3y ago
>Imagine this. You’re working at a company with thousands of engineers. No, I don't think I will. No problem requires thousands of programmers.
- forrestthewoods 3y ago
  Really? That’s your response? You were mostly giving thoughtful replies. How disappointing.