all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Converted git repository available for review
Date: Fri, 21 Mar 2014 23:00:17 -0400	[thread overview]
Message-ID: <20140322030017.GA29313@thyrsus.com> (raw)
In-Reply-To: <532CE0B7.3010309@cs.ucla.edu>

Paul Eggert <eggert@cs.ucla.edu>:
> Thanks.  I compared the latest revision (d245cfa) in the converted
> git repository's master to the corresponding revision (116808) in
> the bzr trunk, and found some discrepancies (see attached).  They
> fall into two major categories.
> 
> 1.  The git version is missing some changes to .gitignore files.
> For example, we removed the arch-tag lines a while ago, but the git
> version has resurrected them.  I expect the conversion machinery
> needs to be tweaked to handle .gitignore files correctly.

Take a look at the relevant section of the lift script.  What I've
done is treat the Bazaar ignore files as authoritative for those
revisions during which Bazaar was in use, ignoring .gitignores during
that period.  The other major possibility would be to simply remove
.bzrignores where .gitignore files exist.

I don't care.  Either is doable; somebody make a policy choice, please?

> 2.  The git version has rewritten 100 ChangeLog lines, replacing
> strings like "revno 108687" with strings like
> "2012-06-22T21:17:42Z!eggert@cs.ucla.edu" using the principles you
> discussed earlier.  In many cases the ChangeLog lines have gotten
> too long.  I propose converting them to the new form and fixing
> resulting line-length problems in the bzr trunk, now, so that the
> automated conversion process has nothing to do in this area.  I'll
> volunteer to do this by hand, as it hardly seems worth automating.

Here's I could do instead: select commit comments and ChangeLog
revisions with overlong lines, mailboxize them, and craft some filter
commands to fix up the line breaks.  That would fix up the history
for maximumm readability.

But how much do we care about fewer than 108 overlong lines, really?
I'm not even sure your small effort would be really justified, let
alone my larger one.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>



  reply	other threads:[~2014-03-22  3:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 20:00 Converted git repository available for review Eric S. Raymond
2014-03-21 22:00 ` Stefan
2014-03-21 22:12   ` Eric S. Raymond
2014-03-21 22:06 ` Juanma Barranquero
2014-03-22  1:00 ` Paul Eggert
2014-03-22  3:00   ` Eric S. Raymond [this message]
2014-03-22  3:37     ` Paul Eggert
2014-03-22  3:42       ` Juanma Barranquero
2014-03-22  4:29       ` Eric S. Raymond
2014-03-22 14:56         ` Paul Eggert
2014-03-22 18:47           ` Eric S. Raymond
2014-03-24  9:24             ` .gitignore and .bzrignore files Nicolas Richard
2014-03-24 10:38               ` Eric S. Raymond
2014-03-24 11:53                 ` Stephen J. Turnbull
2014-03-24 15:54                 ` Nicolas Richard
2014-03-24 22:44               ` Achim Gratz
2014-03-22  4:41 ` Converted git repository available for review Juanma Barranquero
2014-03-22  7:32   ` Stephen J. Turnbull
2014-03-22  7:38     ` David Kastrup
2014-03-22  7:35   ` Eli Zaretskii
2014-03-22 11:48     ` Juanma Barranquero
2014-03-22  9:12   ` Eric S. Raymond
2014-03-22 11:47     ` Juanma Barranquero
2014-03-22  9:40   ` Andreas Schwab
2014-03-22  8:02 ` Andreas Schwab
2014-03-22  9:20   ` Eric S. Raymond
2014-03-22  9:44     ` Andreas Schwab
2014-03-22 11:03       ` Eric S. Raymond
2014-03-24 22:33         ` James Cloos
2014-03-24 22:39           ` Eric S. Raymond
2014-03-25  7:57             ` David Kastrup
2014-03-25 10:54               ` Eric S. Raymond
2014-03-25 11:04                 ` David Kastrup
2014-03-25 11:32                   ` Eric S. Raymond
2014-03-25 11:39                     ` David Kastrup
2014-03-25 11:50                       ` Eric S. Raymond
2014-03-25 12:47                   ` Phillip Lord
2014-03-25 13:04                     ` David Kastrup

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140322030017.GA29313@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=eggert@cs.ucla.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.