On Wed, Oct 31, 2012 at 2:08 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Felipe Contreras wrote: > >> I don't think it's my job to explain to you how 'git fast-export' >> works. > > Actually, if you are submitting a patch for inclusion, it is your job > to explain to future readers what the patch does. That's already explained. > Yes, the reader > might not be deeply familiar with the part of fast-export you are > modifying. This has nothing to do with what you said. I'm literally explaining to you how 'git fast-export' works in situations that are completely orthogonal to this patch, because you are using wrong examples as grounds to prevent this patch from being accepted. It's not my job to explain to you that 'git fast-export' doesn't work this way, you have a command line to type those commands and see for yourself if they do what you think they do with a vanilla version of git. That's exactly what I did, to make sure I'm not using assumptions as basis for arguing, it took me a few minutes. That being said, if your problem is that it's not clear to people not deeply familiar with that part of fast-export, this extra paragraph in addition to the current commit message should do the trick: --- The reason this happens is that before traversing the commits, fast-export checks if any of the refs point to the same object, and any duplicated ref gets added to a list in order to issue 'reset' commands after the traversing. Unfortunately, it's not even checking if the commit is flagged as UNINTERESTING. The fix of course, is to do precisely that. --- And to get that all had to do is ask: "Can you please add an explanation of what this part of the code does? For the ones of us not familiar with it". Not; "This patch looks unsafe", "This patch makes Sally mad", "This patch causes regressions", and so on. But hey, at least we are not arguing about what is wrong with this patch (or so I hope). Cheers. -- Felipe Contreras -- 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