unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Bob Proulx <bob@proulx.com>, emacs-devel@gnu.org
Subject: Re: Fixing repository conversion errors.
Date: Thu, 13 Nov 2014 13:31:07 -0500	[thread overview]
Message-ID: <20141113183106.GA12320@thyrsus.com> (raw)
In-Reply-To: <jwvy4rfq8b1.fsf-monnier+emacs@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca>:
> > Eric S. Raymond wrote:
> >> We need a procedure for this - I don't want us to lose another day and
> >> a half.  Copying Bob Proulx.  Here's how I think it should go:
> 
> Please don't.  This revision number is redundant data (e.g. I never
> include it in my commit message when I do those merges) and the
> corresponding revid is trivially available already.
> I prefer to live with it than having to rebase my branches yet again.

OK, maintainer directive that the present glitches are not worth fixing 
accepted.  But I would still like to have the procedure in place in case
in case anything more serious comes up.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>



  reply	other threads:[~2014-11-13 18:31 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
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 [this message]
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=20141113183106.GA12320@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=bob@proulx.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).