git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: Christophe Simonis <christophe@kn.gl>
Subject: [ANNOUNCE] git-remote-bzr 0.2
Date: Fri, 09 May 2014 11:27:00 -0500	[thread overview]
Message-ID: <536d01d41a7e1_4725b1d30cbf@nysa.notmuch> (raw)

Hi,

git-remote-bzr is a bidirectional bridge between Git and Bazaar. It is
production-ready, has been widely tested, and was previously part of
git.git.

As I already explained[1], there is no path forward for git-remote-hg
and git-remote-bzr; Junio C Hamano has retracted from his previous
statements where he wanted these tools to become part of the Git core
and distributed by default.

So it's time to move out-of-tree so they can be packaged and distributed
properly (as properly as any out-of-tree tool can).

Changes from v1.9 upstream:

 * Add manpage
 * Fix regression that will become active in Git v2.0
 * Add support for older versions of bzr

If you use ArchLinux, you can use the package I wrote[2].

Enjoy :)

https://github.com/felipec/git-remote-bzr

Felipe Contreras (10):
      Reorganize test
      Add README
      build: add install instructions
      doc: add manpage
      Add support for older versions
      Trivial test fix
      Store marks only on success
      test: fix redirection style
      travis: add initial configuration
      Use python2 instead of python

dequis (1):
      Include authors field in pushed commits

[1] http://article.gmane.org/gmane.comp.version-control.git/248561
[2] https://aur.archlinux.org/packages/git-remote-bzr/

-- 
Felipe Contreras

                 reply	other threads:[~2014-05-09 16:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=536d01d41a7e1_4725b1d30cbf@nysa.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=christophe@kn.gl \
    --cc=git@vger.kernel.org \
    /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).