From: "John Wiegley" <johnw@newartisans.com>
To: emacs-devel@gnu.org
Subject: Re: Git to Bzr - what works?
Date: Tue, 14 Aug 2012 12:54:17 -0500 [thread overview]
Message-ID: <m2k3x1fjg6.fsf@newartisans.com> (raw)
In-Reply-To: <5029AB54.8020804@dancol.org> (Daniel Colascione's message of "Mon, 13 Aug 2012 18:35:16 -0700")
>>>>> Daniel Colascione <dancol@dancol.org> writes:
> I have a bunch of patches locked up in my git mirror of the Emacs trunk. I'd
> like to commit some of them, and that involves pushing these patches to a
> bzr branch before pushing them to the main repository. But I can't the
> patches out of git. I can't find any working git-to-bzr packages that work
> with the Emacs trunk. The wiki suggests git-bzr, but both git-bzr and
> git-bzr-ng both complain (via git-fast-import) about missing committer
> records. Does anyone have a working bidirectional git setup?
I have never succeeded in getting anything to work, just FYI, and I've tried
several different things. If you can figure out something, please let me
know, because it impairs my ability to contribute upstream as well.
John
next prev parent reply other threads:[~2012-08-14 17:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 1:35 Git to Bzr - what works? Daniel Colascione
2012-08-14 17:54 ` John Wiegley [this message]
2012-08-14 18:12 ` Eli Zaretskii
2012-08-14 19:56 ` BT Templeton
2012-08-15 2:49 ` Eli Zaretskii
2012-08-15 3:08 ` Fabian Ezequiel Gallina
2012-08-15 4:16 ` Stephen J. Turnbull
2012-08-15 17:56 ` Eli Zaretskii
2012-08-15 20:45 ` Stefan Monnier
2012-08-15 23:49 ` Daniel Colascione
2012-08-16 2:52 ` Eli Zaretskii
2012-08-16 3:19 ` John Wiegley
2012-08-16 15:25 ` Eli Zaretskii
2012-08-16 10:49 ` Julien Danjou
2012-08-16 12:09 ` Andreas Schwab
2012-08-17 2:27 ` Daniel Colascione
2012-08-17 7:06 ` Daniel Colascione
2012-08-21 16:59 ` Stefan Monnier
2012-08-15 17:22 ` John Wiegley
2012-08-15 17:43 ` Eli Zaretskii
2012-08-16 3:18 ` John Wiegley
2012-08-16 3:42 ` Óscar Fuentes
2012-08-16 15:27 ` Eli Zaretskii
2012-08-17 3:30 ` Stefan Monnier
2012-08-17 4:02 ` Daniel Colascione
2012-08-17 6:23 ` Eli Zaretskii
2012-08-17 7:12 ` Stephen J. Turnbull
2012-08-17 15:03 ` Richard Stallman
2012-08-16 15:23 ` Eli Zaretskii
2012-08-16 22:12 ` John Wiegley
2012-08-17 6:32 ` Eli Zaretskii
2012-12-21 15:05 ` Ted Zlatanov
2012-12-21 19:01 ` Karl Fogel
2012-12-22 5:44 ` Bastien
2012-12-22 12:24 ` Stephen J. Turnbull
2012-12-22 12:48 ` Stephen J. Turnbull
2012-12-22 13:21 ` Xue Fuqiao
2012-12-22 13:40 ` Juanma Barranquero
2012-12-22 13:51 ` Xue Fuqiao
2012-12-22 14:13 ` Andreas Schwab
2012-12-22 14:11 ` Andreas Schwab
2012-12-22 13:08 ` Bastien
2012-12-22 19:20 ` Ted Zlatanov
2012-12-21 23:42 ` Xue Fuqiao
2012-12-22 8:22 ` Juri Linkov
2012-12-22 17:04 ` Thomas Koch
2012-12-22 17:28 ` Thien-Thi Nguyen
2012-12-22 19:06 ` Ted Zlatanov
2012-12-24 5:56 ` Thien-Thi Nguyen
2012-12-24 13:31 ` Ted Zlatanov
2012-12-24 16:30 ` Thien-Thi Nguyen
2012-12-25 4:12 ` Bastien
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2k3x1fjg6.fsf@newartisans.com \
--to=johnw@newartisans.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).