Hi, On Wed, Oct 31, 2012 at 7:59 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Felipe Contreras wrote: >> On Wed, Oct 31, 2012 at 7:20 PM, Johannes Schindelin >> <Johannes.Schindelin@xxxxxx> wrote: > >>> I just tested this with junio/next and it seems this issue is still >>> unfixed: instead of >>> >>> reset refs/heads/blub >>> from e7510461b7db54b181d07acced0ed3b1ada072c8 >>> >>> I get >>> >>> reset refs/heads/blub >>> from :0 >>> >>> when running "git fast-export ^master blub". >> >> That is not a problem. It has been discussed extensively, and the >> consensus seems to be that such command should throw nothing: >> >> http://article.gmane.org/gmane.comp.version-control.git/208729 > > Um. Are you claiming I have said that "git fast-export ^master blub" > should silently emit nothing? Or has this been discussed extensively > with someone else? Maybe I misunderstood when you said: > A patch meeting the above description would make perfect sense to me. Anyway, when you have: % git fast-export ^next next^{commit} # nothing % git fast-export ^next next~0 # nothing % git fast-export ^next next~1 # nothing % git fast-export ^next next~2 # nothing It only makes sense that: % git fast-export ^next next # nothing It doesn't get any more obvious than that. But to each his own. 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