From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Git to Bzr - what works?
Date: Sat, 22 Dec 2012 14:20:47 -0500 [thread overview]
Message-ID: <87wqw9gagg.fsf@lifelogs.com> (raw)
In-Reply-To: 87ehiiw9zf.fsf@uwakimon.sk.tsukuba.ac.jp
On Sat, 22 Dec 2012 21:24:20 +0900 "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
SJT> Bastien writes:
>> If FSF cannot have someone to do the work Ted describes,
>> maybe this could be a nice GSoC project for 2013?
SJT> It's not a GSoC project. Many man-months have been spent on the
SJT> problem (Lele Gaifax's Tailor, work by the Bazaar developers, plus
SJT> work by the various projects on making the git-import format more
SJT> generic), and there's no satisfactory solution yet. It might be
SJT> somewhat easier with a specific pair in mind, but there's good reason
SJT> to believe that Bazaar is the most difficult because of its much
SJT> richer metadata (including tracking both directories and few
SJT> "containers").
I really think it's a job, not a technical problem to be solved.
Katsumi Yamaoka does it for Gnus. He has good procedures in place for
synchronizing Gnus' Git repo with Emacs' Bazaar repo.
Ted
next prev parent reply other threads:[~2012-12-22 19:20 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
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 [this message]
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=87wqw9gagg.fsf@lifelogs.com \
--to=tzz@lifelogs.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).