On Sun, Nov 15, 2015 at 01:53:31PM +0100, Lars Schneider wrote: > > Hrm. Do we want to make these workarounds work correctly? Or is the > > final solution going to be that the first command you gave simply works, > > and no workarounds are needed. If the latter, I wonder if we want to be > > adding tests for the workarounds in the first place. > > > > I'm not clear on the expected endgame. > > I see your point. I'll remove the workaround tests in the next roll. > That being said, I think the we should do something about the > workarounds, too, because it certainly confused me as Git user. Would > you merge a patch that prints a warning message like "--depth > parameter not supported for submodules update command" or something if > a user tries this command? I would never promise to merge something without seeing it first. :) It does sound sensible to me to warn the user when some of their request is being ignored. I'm not familiar enough with submodules to know whether there are hidden gotchas here (so I would rely on folks like Stefan and Jens for review). -Peff -- 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