All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
	Elijah Newren <newren@gmail.com>,
	Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH 2/3] fast-export: add new --refspec option
Date: Thu, 09 May 2013 17:21:42 -0700	[thread overview]
Message-ID: <7vobcj65wp.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s1d_9iT7nqtu3gTy=kX-Kapnf0AUZJ-Z-MpLkBuWxBgSw@mail.gmail.com> (Felipe Contreras's message of "Thu, 9 May 2013 18:32:16 -0500")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> On Thu, May 9, 2013 at 6:23 PM, Junio C Hamano <gitster@pobox.com> 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 ...

  reply	other threads:[~2013-05-10  0:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  1:31 [PATCH 0/3] Support for old:new remote-helper push Felipe Contreras
2013-05-09  1:31 ` [PATCH 1/3] fast-export: improve argument parsing Felipe Contreras
2013-05-09 22:17   ` Junio C Hamano
2013-05-09 23:02     ` Felipe Contreras
2013-05-09 23:27       ` Junio C Hamano
2013-05-09 23:33         ` Felipe Contreras
2013-05-10  4:49           ` Junio C Hamano
2013-05-09  1:31 ` [PATCH 2/3] fast-export: add new --refspec option Felipe Contreras
2013-05-09 22:32   ` Junio C Hamano
2013-05-09 22:53     ` Felipe Contreras
2013-05-09 23:23       ` Junio C Hamano
2013-05-09 23:32         ` Felipe Contreras
2013-05-10  0:21           ` Junio C Hamano [this message]
2013-05-10  0:44             ` Felipe Contreras
2013-05-10  1:13             ` Junio C Hamano
2013-05-10  6:42               ` Johannes Sixt
2013-05-16  9:15               ` Felipe Contreras
2013-05-09  1:31 ` [PATCH 3/3] transport-helper: add support for old:new refspec Felipe Contreras
2013-05-16  9:15 ` [PATCH 0/3] Support for old:new remote-helper push Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vobcj65wp.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --cc=srabbelier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.