3 ms·
Most high-profile projects have many contributors and change very quickly. Several years ago, I submitted a bug fix to git at the same time that someone else su
by mcguire 12y ago
Most high-profile projects have many contributors and change very quickly. Several years ago, I submitted a bug fix to git at the same time that someone else submitted a better fix for the same problem. (Junio Hamano was very nice about it.) I eventually dropped off the mailing list because that had too much traffic to follow while I was working.
Also, because of the high volume, they don't have a whole lot of time for hand-holding. I submitted a pull request to Rust which was approved but failed to auto-merge for some inexplicable reason and languished until someone cleaned up the queue. I never found out what the problem was. (And tracking master for tests, given how long it took to build, is Sisyphean.)
Lt;dr: Like drinking from a fire hose? Go for it!
- dbaupp 12y agoI try to "handhold" newbies to Rust if I notice a pull request from someone new (and I know a few other reviewers who try to reduce "jargon"/expand explanations for PRs from new people); you must've been one of the ones unfortunate enough to slip under the radar. Sorry! :( FWIW, if it was an automerge failure (rather than a test failure), that just means there were merge conflicts which git cannot resolve automatically, and just requires rebasing the PR. (I believe Github's interface for displaying when a PR is stale has improved recently, so hopefully this situation is now less confusing!)