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

Re: [PATCH v2 0/2] remote-bzr: couple of fixes

From
Junio C Hamano <gitster@pobox.com>
Date
May 5, 2013, 18:33 UTC
Message-ID
<7vd2t5uvi2.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1367627467-15132-1-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> The previous version had an indentation bug (did I mention I hate python?).
>
> A few fixes to be applied on top of the massive changes already queued. Nothing
> major.

[2/2] may not matter much in the context of my tree (people would use post 1.8.2 fast-export if they are using remote-bzr from 1.8.3 from my tree ;-), but [1/2] sounds like it is a good thing to have in 1.8.3 (not "on top of that 'massive' series").

Assuming the "otherwise some version of bzr might barf" problem is that repo.generate_revision_history() in those versions may not apply str() to its first parameter and the caller is expected to pass a string there, or something?

Thanks.
Show 7 quoted lines
>
> Felipe Contreras (2):
>   remote-bzr: convert all unicode keys to str
>   remote-bzr: avoid bad refs
>
>  contrib/remote-helpers/git-remote-bzr | 42 +++++++++++++++++++++--------------
>  1 file changed, 25 insertions(+), 17 deletions(-)
Previous: Stefano LattariniNext: Felipe Contreras
Message 5 of 10 in “remote-bzr: couple of fixes”
  1. 0/2 remote-bzr: couple of fixesFelipe Contreras, May 4, 2013
  2. 1/2 remote-bzr: convert all unicode keys to strFelipe Contreras, May 4, 2013
  3. 2/2 remote-bzr: avoid bad refsFelipe Contreras, May 4, 2013
  4. Stefano LattariniMay 4, 2013
  5. Junio C HamanoMay 5, 2013
  6. Felipe ContrerasMay 5, 2013
  7. Junio C HamanoMay 5, 2013
  8. Felipe ContrerasMay 5, 2013
  9. Junio C HamanoMay 5, 2013
  10. Felipe ContrerasMay 5, 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.