Michael G Schwern <schwern@xxxxxxxxx> writes: >>> Also I just realized I've been basing my work on master. Should I move to maint? >> >> I don't think so. It is not fixing any urgent breakage (iow, by >> being told about .pm explicitly, it knows about them just fine >> without being taught how to find them). > > How about the git-svn SVN 1.7 fix in general? All of these patch sets I'm > sending build on one another, is that going to be a problem? It's going to > come in about six parts. Judging from the rate of the discussion this is progressing, I was imagining that this series would be ready by 1.7.13 at the earliest, possibly back-merged to 1.7.12.X maintenance series, and 1.7.11.X maintenance series is no longer relevant by then. But I certainly do not mind seeing the series based on earlier maintenance releases, e.g. maint-1.7.9. There however are tons of other git-svn.perl and perl/ updates since then, so basing the series on the current maint branch to abandon 1.7.10.X and earlier but still leaving the door open to downmerge to 1.7.11.X may be a good trade-off. -- 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