RE: What's cooking in git.git (Dec 2013, #02; Fri, 6)

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Dec 7, 2013, 10:03 UTC
Message-ID: <52a2f27bfe07_29836d5e98f5@nysa.notmuch>
In-Reply-To: <xmqqk3fh1qrc.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:

Show 22 quoted lines

> * fc/transport-helper-fixes (2013-11-13) 12 commits
>  - remote-bzr: support the new 'force' option
>  - transport-helper: add support to delete branches
>  - fast-export: add support to delete refs
>  - fast-import: add support to delete refs
>  - transport-helper: add support for old:new refspec
>  - fast-export: add new --refspec option
>  - fast-export: improve argument parsing
>  - test-hg.sh: tests are now expected to pass
>  - transport-helper: check for 'forced update' message
>  - transport-helper: add 'force' to 'export' helpers
>  - transport-helper: don't update refs in dry-run
>  - transport-helper: mismerge fix
> 
>  Updates transport-helper, fast-import and fast-export to allow the
>  ref mapping and ref deletion in a way similar to the natively
>  supported transports.
> 
>  The option name "--refspec" needs to be rethought. It does not mean
>  what refspec usually means, even though it shares the same syntax
>  with refspec; calling it --refspec only because it shares the same
>  syntax is like calling it --asciistring and does not make sense.

Not true. remote.<name>.fetch is a refspec, and doesn't specify what to fetch, so does the "refspec" capability in remote helpers, and so does the proposed --refspec option.

It is exactly what it already means.

-- 
Felipe Contreras