On Sun, Aug 21, 2011 at 03:29:38PM -0700, Sverre Rabbelier wrote: > > Yes, this was the conclusion I came to when I looked at this a month or > > so ago. You really need to give fast-export a mapping of objects to > > refnames, and it should output ref names _only_ for the mapping. That > > would handle this "not a ref" case, but would also let you push > > "refs/heads/foo" when it is equivalent to "refs/heads/master", without > > fast-export mentioning "refs/heads/master" at all. > > Does this bring any new insights into how the problem I was pointing > out (trying to push next if master points at the same commit does > nothing) could/should be solved? Hmm. Maybe I am misremembering the problem, but I thought that worked already. If you say: git fast-export refs/heads/foo you should get only reset/commit lines in the output for refs/heads/foo, no? Now I can't seem to replicate the case where refs/heads/master is mentioned, but you didn't want it to be. I may have to go back and re-read the thread from a month or two ago when we discussed these issues. -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