From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Eric Raymond <esr@thyrsus.com>
Cc: Bernd Schmidt <bernds_cb1@t-online.de>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
fallenpegasus@gmail.com
Subject: Re: Repo conversion troubles.
Date: Tue, 10 Jul 2018 08:20:00 -0000 [thread overview]
Message-ID: <CAH6eHdRVq0DYk6cJuO5RPFVZG35Lf8Cdj6WR1e5_jPZ9LKLWiQ@mail.gmail.com> (raw)
In-Reply-To: <20180709195957.GB32057@thyrsus.com>
On Mon, 9 Jul 2018 at 21:00, Eric S. Raymond <esr@thyrsus.com> wrote:
>
> Bernd Schmidt <bernds_cb1@t-online.de>:
> > On 07/09/2018 09:19 PM, Eric S. Raymond wrote:
> > > Last time I did a comparison between SVN head and the git conversion
> > > tip they matched exactly. This time I have mismatches in the following
> > > files.
> >
> > So what are the diffs? Are we talking about small differences (like one
> > change missing) or large-scale mismatches?
>
> Large-scale, I'm afraid. The context diff is about a GLOC.
I don't see how that's possible. Most of those files are tiny, or
change very rarely, so I don't see how that large a diff can happen.
Take zlib/configure.ac and zlib/configure, there's only been one
change in the past 18 months: https://gcc.gnu.org/r261739
That change didn't touch the other files in the list.
libtool.m4 has one change in the past 2 years (just a few days ago):
https://gcc.gnu.org/r262451
That was also tiny, and didn't touch the other files.
maintainer-scripts/crontab only has one change in the past 6 months:
https://gcc.gnu.org/r259637
That was a tiny change, and didn't touch any other files.
None of those were merges from any other branch.
next prev parent reply other threads:[~2018-07-10 8:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 19:19 Eric S. Raymond
2018-07-09 19:40 ` Jeff Law
2018-07-09 19:57 ` Eric S. Raymond
2018-07-09 20:01 ` Jeff Law
2018-07-09 20:06 ` Eric S. Raymond
2018-07-09 19:46 ` Bernd Schmidt
2018-07-09 19:59 ` Eric S. Raymond
2018-07-10 1:13 ` Alexandre Oliva
2018-07-20 21:48 ` Joseph Myers
2018-07-21 2:04 ` Eric S. Raymond
2018-07-10 8:20 ` Jonathan Wakely [this message]
2018-07-10 8:34 ` Jonathan Wakely
2018-07-10 10:48 ` Eric S. Raymond
2018-07-20 22:06 ` Joseph Myers
2018-07-09 20:04 ` Richard Biener
2018-07-09 20:20 ` Eric S. Raymond
2018-07-10 4:57 ` Richard Biener
2018-07-10 11:22 ` Philip Martin
2018-07-20 21:43 ` Joseph Myers
2018-07-20 23:48 ` Eric S. Raymond
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=CAH6eHdRVq0DYk6cJuO5RPFVZG35Lf8Cdj6WR1e5_jPZ9LKLWiQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=bernds_cb1@t-online.de \
--cc=esr@thyrsus.com \
--cc=fallenpegasus@gmail.com \
--cc=gcc@gcc.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.
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).