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

Re: [PATCH v2] remote-bzr: reuse bzrlib transports when possible

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 10, 2013, 22:01 UTC
Message-ID
<xmqqbo40wd3d.fsf@gitster.dls.corp.google.com>
In-Reply-To
<xmqqa9jl1u7j.fsf@gitster.dls.corp.google.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 24 quoted lines
> Richard Hansen <rhansen@bbn.com> writes:
>
>>  def do_export(parser):
>> -    global parsed_refs, dirname
>> +    global parsed_refs, dirname, transports
>
> As this has been acked by Felipe who knows the script the best, I'll
> apply this directly to 'master'.
>
> These additions of "global transports" however have trivial
> interactions with fc/contrib-bzr-hg-fixes topic Felipe posted
> earlier, which I was planning to start merging down to 'next' and
> then to 'master'.  Most funcions merely use the variable without
> assigning, so "global transports" can be removed, in line with the
> spirit of 641a2b5b (remote-helpers: cleanup more global variables,
> 2013-08-28), except for the obvious initialisation in main(), I
> think.  Please double check the conflict resolution result in a
> commit on 'pu' with
>
>     git show 'origin/pu^{/Merge fc/contrib-bzr}'
>
> when I push the result out.
>
> Thanks.

Ping? I'd like to merge fc/contrib-bzr.hg-fixes topic to 'next' (and fast track it to 'master' after that), and it would be helpful to get an Ack on the conflict resolution I have.

Previous: Junio C HamanoNext: Richard Hansen
Message 7 of 10 in “remote-bzr: reuse bzrlib transports when possible”
  1. remote-bzr: reuse bzrlib transports when possibleRichard Hansen, Sep 7, 2013
  2. Richard HansenSep 8, 2013
  3. Felipe ContrerasSep 8, 2013
  4. Richard HansenSep 8, 2013
  5. remote-bzr: reuse bzrlib transports when possibleRichard Hansen, Sep 8, 2013
  6. Junio C HamanoSep 9, 2013
  7. Junio C HamanoSep 10, 2013
  8. Richard HansenSep 12, 2013
  9. Junio C HamanoSep 12, 2013
  10. Felipe ContrerasSep 8, 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.