Carl Worth <cworth@xxxxxxxxxx> writes: > I'm still not sure what the easiest way is for me to provide changes > to you. I've been doing it here on the list, like with the current > message. But would it be easier for me to send pull requests? You can decide what is easier for _you_ ;-). But for me, emailed patches are easier to work on than pull requests. I will need to read and understand most of the changes anyway, unless the change is to an isolated corner of the system that would affect only one class of users and breakage will be noticed either immediately or can be left broken if nobody uses that (e.g. things like contrib/ and some foreign SCM interfaces). I would like others on the list to be able to review the same changes that might hit my tree and provide extra sets of eyeballs to spot things I might miss myself alone. > For example, with the git-clone failure cleanup I recently did, it > seems the new test case I wrote didn't land in your tree. Sorry, I think I just forgot to apply that one. I still have the message so no need to resend. Thanks for reminding. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html