git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] transport-helper: check if the dry-run is supported

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 21, 2013, 21:14 UTC
Message-ID
<CAMP44s14ZBUYhxDkSwjoi+6JPx4whfQDhiq_4QfMteALsbuQ_Q@mail.gmail.com>
In-Reply-To
<7vli78p920.fsf@alter.siamese.dyndns.org>
On Tue, May 21, 2013 at 11:55 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> Certain remote-helpers (the ones with 'export') would try to push
>> regardless.
>>
>> Obviously this is not what the user wants.
>>
>> Also, add a check for the 'dry-run' option, so remote-helpers can
>> implement it.
>
> This sounds like a good thing to do.  Perhaps the refspec mapping
> can be handled the same way as a backend feature so that you do not
> have to unconditionally disable it in the other patch.

With my patch the remote helper doesn't need to know about the refspec handling at all, it just works magically.

-- 
Felipe Contreras
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 5 in “transport-helper: check if the dry-run is supported”
  1. transport-helper: check if the dry-run is supportedFelipe Contreras, May 21, 2013
  2. Junio C HamanoMay 21, 2013
  3. Felipe ContrerasMay 21, 2013
  4. Junio C HamanoMay 22, 2013
  5. Felipe ContrerasMay 22, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.