From: Felipe Contreras <felipe.contreras@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: git@vger.kernel.org
Subject: Re: Git access to Bzr repository fails for enwc
Date: Wed, 21 Aug 2013 15:16:49 -0500 [thread overview]
Message-ID: <CAMP44s0zMbgt8snc=HkDqYHCWGZ3b4_oFZs64K48RjoXVR+1Tw@mail.gmail.com> (raw)
In-Reply-To: <jwvbo4ygbo8.fsf-monnier+emacs@gnu.org>
On Thu, Aug 15, 2013 at 11:31 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> I've had good success recently with the git->bzr bridge, but the
> following still fails. This is on Debian with the git from "unstable".
Which version are you using? The latest version works fine here:
https://github.com/felipec/git/blob/fc/master/git-remote-bzr.py
--
Felipe Contreras
next prev parent reply other threads:[~2013-08-21 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 16:31 Git access to Bzr repository fails for enwc Stefan Monnier
2013-08-21 20:16 ` Felipe Contreras [this message]
2013-08-22 1:18 ` Stefan Monnier
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='CAMP44s0zMbgt8snc=HkDqYHCWGZ3b4_oFZs64K48RjoXVR+1Tw@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=monnier@iro.umontreal.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).