From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Fabian Ezequiel Gallina <galli.87@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, BT Templeton <bpt@hcoop.net>,
emacs-devel@gnu.org
Subject: Re: Git to Bzr - what works?
Date: Wed, 15 Aug 2012 13:16:51 +0900 [thread overview]
Message-ID: <87boicoklo.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <CABq4mQtMZ4vT9k6dwf-qR81ZDUuZQVdNu6WCgy7ThU_G0s3t0Q@mail.gmail.com>
Fabian Ezequiel Gallina writes:
> I generated the patches from git repo with git format-patch, modified
> paths in patch files with sed to match Emacs file structure, and then
> used bzr git-apply with no problems, except
This sounds reasonable (it should be unnecessary, but one can script
what Bazaar didn't think necessary to do), but
> for the fact that I had to create a commit adding a blank
> lisp/progmodes/python.el after deleting the old one in order for
> bzr git-apply to apply patches successfully.
IMO, this is hardly a "no problems, except" problem. This is a
show-stopper, unacceptable even the worker doesn't mind doing it by
hand. This makes the "blame" command useless for investigating the
provenance of any code that appears in the deleted-readded file. You
might get by with this in other projects, but Emacs cares greatly
about such issues for legal reasons.
It also makes one wonder about Bazaar, but that's a whole other issue.
Steve
next prev parent reply other threads:[~2012-08-15 4:16 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 [this message]
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=87boicoklo.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=bpt@hcoop.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
/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).