From: Felipe Contreras Date: Fri, 10 May 2013 00:44:24 GMT Subject: Re: [PATCH 2/3] fast-export: add new --refspec option Message-ID: In-Reply-To: <7vobcj65wp.fsf@alter.siamese.dyndns.org> On Thu, May 9, 2013 at 7:21 PM, Junio C Hamano wrote: > Felipe Contreras writes: > >> On Thu, May 9, 2013 at 6:23 PM, Junio C Hamano wrote: >>> 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*]. >> ... >>> 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/*'. > > I think you misunderstood. That is meant to illustrate what your > end users feed "fast-export". "fast-export" in turn expands that > into a revision range, which needs to happen anyway when it strips > :new-master from the positive end of the range to make the range > into > > master ^next ^refs/tags/v1.0 ^refs/tags/v1.1 ... 'git fast-export' accepts rev-list arguments, to make it do something else would not only break existing users, but would require massive work. I'm not interested in doing that. Cheers. -- Felipe Contreras