@steveklabnik Is that argument correct? I don't see why you couldn't send-email a patch that I could apply normally. School me.
-
-
Replying to @JEG2
@JEG2@steveklabnik You are correct. These are normal git remotes and you can use stuff like send-email outside the loop all you want.1 reply 0 retweets 0 likes -
Replying to @wfarr2 replies 0 retweets 0 likes
-
Replying to @steveklabnik
@steveklabnik@JEG2 it’s up to maintainers on how they want to manage their projects. They have every right to do that.1 reply 0 retweets 0 likes -
Replying to @wfarr1 reply 0 retweets 0 likes
-
Replying to @steveklabnik
@steveklabnik@JEG2 they’re implying PR/send-email is lock-in when it’s not at all. It’s a false dichotomy. It’s a project mgmt problem.3 replies 0 retweets 0 likes -
Replying to @wfarr1 reply 0 retweets 0 likes
-
Replying to @steveklabnik
@steveklabnik@JEG2 we make it easy to use PRs because that’s how we like to work. We have never made it harder to use send-email/am1 reply 0 retweets 0 likes -
Replying to @wfarr1 reply 0 retweets 0 likes
-
Replying to @steveklabnik
@steveklabnik@JEG2 the Linux project is on github and accepts patches only through email and rejects all PRs. I think it’s fine, tbh2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.