From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Eric S. Raymond <esr@thyrsus.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: New Git repository is up.
Date: Thu, 13 Nov 2014 15:01:34 +0900 [thread overview]
Message-ID: <b4ma93vljup.fsf@jpl.org> (raw)
In-Reply-To: 20141113050153.GA25055@thyrsus.com
On Thu, 13 Nov 2014 00:01:53 -0500, Eric S. Raymond wrote:
> Paul Eggert <eggert@cs.ucla.edu>:
>> Thanks a lot for doing the conversion.
>>
>> A problem I noticed: the last two commits in the trunk bzr (118359
>> and 118360) are not in the git master branch. Similarly, the last
>> commit in the emacs-24 bzr (117703, a backport) is not in the git
>> emacs-24 branch. Perhaps one last pass to apply these last-second
>> bzr changes to the git version? Or should we ask the authors of
>> those patches to reapply them?
> That "last pass" would cost a minimum of temn hours of repo downtime.
> I'm willing to do that if we find problems with the converted history
> that have to be surgically corrected, but fotr this it would be less
> work to just grab the patches from bzr and apply them.
> Sorry. I suspect I dropped those two commits while I was trying to
> bring the transition-day patch up to date.
No problem. I've repushed those two changed to the git repos.
I also have performed diff with the old bzr and the new git repos
for the trunk and the emacs-24 branch, and confirmed there are
no significant difference in the source codes.
Thanks for your great work.
Regards,
next prev parent reply other threads:[~2014-11-13 6:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 3:12 New Git repository is up Eric S. Raymond
2014-11-13 4:20 ` Paul Eggert
2014-11-13 5:01 ` Eric S. Raymond
2014-11-13 5:19 ` Christoph
2014-11-13 6:01 ` Katsumi Yamaoka [this message]
2014-11-13 4:48 ` Christoph
2014-11-13 8:12 ` Jan D.
2014-11-13 8:21 ` Bozhidar Batsov
2014-11-13 8:57 ` Dani Moncayo
2014-11-13 11:30 ` Aurélien Aptel
2014-11-13 11:35 ` Dani Moncayo
2014-11-13 11:43 ` Fixing repository conversion errors Eric S. Raymond
2014-11-13 11:58 ` Dani Moncayo
2014-11-13 12:07 ` Dani Moncayo
2014-11-13 12:25 ` Eric S. Raymond
2014-11-13 12:27 ` Harald Hanche-Olsen
2014-11-13 13:19 ` Óscar Fuentes
2014-11-13 14:01 ` Lars Magne Ingebrigtsen
2014-11-13 16:41 ` Bob Proulx
2014-11-13 17:34 ` Eric S. Raymond
2014-11-13 18:17 ` Stefan Monnier
2014-11-13 18:31 ` Eric S. Raymond
2014-11-13 21:39 ` Bob Proulx
2014-11-13 22:15 ` Stefan Monnier
2014-11-13 23:01 ` Bob Proulx
2014-11-13 13:19 ` New Git repository is up David Engster
2014-11-13 17:43 ` Stefan Monnier
2014-11-13 13:12 ` Lars Magne Ingebrigtsen
2014-11-13 13:20 ` Andreas Schwab
2014-11-13 13:28 ` Lars Magne Ingebrigtsen
2014-11-13 13:55 ` Christoph
2014-11-13 14:00 ` Lars Magne Ingebrigtsen
2014-11-13 14:15 ` Eric S. Raymond
2014-11-13 14:20 ` Lars Magne Ingebrigtsen
2014-11-13 15:57 ` Karl Fogel
2014-11-13 16:36 ` Jay Belanger
2014-11-13 16:39 ` Kelvin White
2014-11-15 15:15 ` Kelvin White
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=b4ma93vljup.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.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).