Karsten Blees <karsten.blees@xxxxxxxxx> writes: > Am 25.02.2013 07:43, schrieb Junio C Hamano: >> Erik Faye-Lund <kusmabite@xxxxxxxxx> writes: > ... >> I'm in the "marking leftover bits" mode today, and noticed that >> nothing happened for this topic in my tree. Did msysgit folks expect >> me to pick this up directly, or did you guys want to feed this series >> to me (with possibly other changes you worked on outside this list)? > > The second patch changes the credential format in a > backward-incompatible way, so I think this should be in git.git, > too (better than having two incompatible versions around). I am a bit confused by that comment, as it was my understanding that the "credential format" only refers to what is stored in the Windows specific credential storage and relevant only to users of msysgit (and I expected folks who are using Git natively on Windows to be using msysgit, not git.git), but in any case, of course we would want a single version and format. My question was if msysgit folks want me to take your patch (which I cannot test myself) and then merge my tree to the msysgit tree as part of their regular updates to catch up with 1.8.2 (and future releases), or they want to test your patches in their tree first, and then either throw me a pull request or send me a patch series with Acked-by:. I can obviously go either way, but if they expect the former (i.e. I first apply and they pull) while I expect the latter (i.e. they first apply and I pull), then nothing will happen, and if we go the other way around, we would end up getting two copies of the same series. The question was primarily to avoid these possibilities. -- To unsubscribe from this list: 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