From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: git@vger.kernel.org, Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)
Date: Mon, 04 Nov 2013 09:37:33 -0800 [thread overview]
Message-ID: <xmqqeh6w131e.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <52743547.7020001@ramsay1.demon.co.uk> (Ramsay Jones's message of "Fri, 01 Nov 2013 23:12:07 +0000")
Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
> 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'.
>>
> [ ... ]
>>
>>
>> * 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?
Good eyes, and no---this needs to be fixed before going forward.
Thanks for spotting.
next prev parent reply other threads:[~2013-11-04 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 22:52 What's cooking in git.git (Nov 2013, #01; Fri, 1) Junio C Hamano
2013-11-01 23:09 ` Thomas Rast
2013-11-04 21:50 ` Junio C Hamano
2013-11-13 16:03 ` Michael Haggerty
2013-11-01 23:12 ` Ramsay Jones
2013-11-04 17:37 ` Junio C Hamano [this message]
2013-11-11 22:25 ` Junio C Hamano
2013-11-03 19:15 ` Torstein Hegge
2013-11-04 18:07 ` Junio C Hamano
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=xmqqeh6w131e.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
/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.