Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes: >> > Sorry, but I'm not comfortable sending code I can't check for myself >> > (and already muscle-memoried into my format-patch/send-email workflow). >> > If you send a scissors I can roll it into the series with your SOB. >> >> But you can check it yourself! I worked _really_ hard on that Azure >> Pipeline backing the PR builds at https://github.com/git/git. _REALLY_ >> hard. You might just as well reap the benefits so that I did not spend all >> of that time and sweat and stress in vain... > > I thought a bit about this. From your Github-using point of view, "just > check my Pipeline" sounds like "just look at one more thing". From my > format-patch using point of view, "just check my Pipeline" sounds like > "ugh, I have to add this remote again... I don't have a fork already? > How do I make that? Or is my fork just 6 months behind? How do I open a > PR again? Yeesh." Sorry, but this is how a typical conversation between two techies who are more intelligent than good for their social skills ;-) Each side is not extending its hand enough to reach the other side, expecting that what s/he knows should be obvious to the others. Dscho may be frustrated for you not being aware of what he worked on, but "I worked really hard" is much less useful thing for others, who may benefit from what he worked hard on, to hear, than "here is one pager that tells you how to use it". Quite honestly, reading the above exchange from the sidelines, it is not clear to me if it is a part of, or a completely separate from, the service offered by GGG from the end-users' point of view. Can some of you come up with a one-pager to cover the following (and related but not listed) areas, that can be added as an appendix to Documentation/SubmittingPatches? It does not have to cover the common stuff like style guidelines, writing good log messages, need for test coverage, choice of fork point, etc. "Now you have a patch or a series of patches, but you obviously do not have direct and personal access to all the platforms Git supports. But there are servies to help you test them on the more common ones." - How to cause TravisCI to run our test suite with your modification. - How to trigger the same on Azure Pipeline PR builds. There may be others. Thanks.
