On Thu, May 9, 2013 at 6:23 PM, Junio C Hamano <gits...@pobox.com> wrote: > Felipe Contreras <felipe.contre...@gmail.com> writes: > >> Of course, but how do you implement that? That's mixing refspecs and >> revlist arguments, which AFAIK don't mix: > > Simple. You treat everything as refspecs and form revision ranges > out of them. Note that that is exactly the reason why "git push" > can take "master" as a short-hand for "master:master" [*1*].
And how do you implement that? >> % git fast-export ^next:new-next master:new-master --not >> refs/tags/*:refs/tags/backup/* > > I thought you stopped mentioning the bottom of the range > (e.g. ^next) in the output from export stream at around 49266e8a11cf > (fast-export: don't handle uninteresting refs, 2012-11-28). That doesn't prevent the rev-list parsing from working. > What does ^next:new-next (or mapping after "--not" in general) even > mean? They would not make sense, would they? They don't, which is precisely my point. > So I would imagine you would be spelling that as: > > git fast-export master:new-master --not next refs/tags/* > > or something, no? rev-list doesn't accept 'refs/tags/*'. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
