Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)

From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Date: Nov 1, 2013, 23:12 UTC
Message-ID: <52743547.7020001@ramsay1.demon.co.uk>
In-Reply-To: <xmqqob6320rt.fsf@gitster.dls.corp.google.com>

On 01/11/13 22:52, Junio C Hamano wrote:

> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.
>

[ ... ]

Show 20 quoted lines

> 
> 
> * fc/transport-helper-fixes (2013-11-01) 11 commits
>  - transport-helper: demote lack of "force" option to a warning
>  - 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
>  - 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.
> 
>  Will merge to 'next'.

Commit ad24a30ef ("fast-export: add new --refspec option", 31-10-2013) causes sparse to complain:

      SP builtin/fast-export.c
  builtin/fast-export.c:739:55: warning: Variable length array is used.

Do we want to use this C99 feature?

ATB, Ramsay Jones