From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Chad Brown Newsgroups: gmane.emacs.devel Subject: Re: The name gnus-cloud.el Date: Tue, 2 Jan 2018 12:42:54 -0800 Message-ID: <329D7743-2F2D-4D8E-B40A-F8668A70CE2C@gmail.com> References: <87374jd66s.fsf@lifelogs.com> <87bmj6dda0.fsf@linux-m68k.org> <87vahe911g.fsf@lifelogs.com> <87374id7jy.fsf@linux-m68k.org> <877ett8g7k.fsf@lifelogs.com> <87a7yn7tqp.fsf@lifelogs.com> <878te75xa1.fsf@lifelogs.com> <87ind6l2tt.fsf@lifelogs.com> <877etklvsa.fsf@lifelogs.com> <83y3m0pv8u.fsf@gnu.org> <86608msw0h.fsf@dod.no> <838tdiet25.fsf@gnu.org> <87y3li4vh7.fsf@telefonica.net> <87efnan46u.fsf@linux-m68k.org> <86wp12qtgo.fsf@dod.no> <83tvw6chqv.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_48B98CE2-9160-4D1C-AD86-B18D8AF69A3B" X-Trace: blaine.gmane.org 1514925680 10775 195.159.176.226 (2 Jan 2018 20:41:20 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 2 Jan 2018 20:41:20 +0000 (UTC) To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 02 21:41:16 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eWTN3-00026s-19 for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2018 21:41:13 +0100 Original-Received: from localhost ([::1]:54765 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWTP0-0008KM-9W for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2018 15:43:14 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWTOr-0008Iu-IQ for emacs-devel@gnu.org; Tue, 02 Jan 2018 15:43:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWTOn-0004GP-Kf for emacs-devel@gnu.org; Tue, 02 Jan 2018 15:43:05 -0500 Original-Received: from mail-pg0-x22c.google.com ([2607:f8b0:400e:c05::22c]:34641) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWTOn-0004G9-BV for emacs-devel@gnu.org; Tue, 02 Jan 2018 15:43:01 -0500 Original-Received: by mail-pg0-x22c.google.com with SMTP id j4so24727785pgp.1 for ; Tue, 02 Jan 2018 12:43:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=EWewBsgQikyP4ZipJ+uhpXZOTENFdhO0nMRysmYZFzk=; b=vSCLfJfKn2WxwI6RuIx8/+/vVm6G760fF6wuBFQYKyHXQLbJtI7Mcxh+p/LzrGjxHT EgAMwNHnkUkIubiDZz4N7/GSFD84wuiBwanBlChyMuqdC/zWc76op/VOQ2Trs+NfhLso j59d2Y7HZXP3NUBhr6piIEvjw4C0zuOqb1JdM1sPeQzUKw0vtbN0KSxURKRtyx23uzFM nwAJpuWP6SZfhyGsB7sA7sB474dKBRRl4vC8XlV1vkFbQ3IDGE4y1Q5h6QuJMaEgM85n 4clyjPN8rIjGd1fmhqvPY8f1ejQpzL3KBl/nxxbxDNO1UQvYg/DFpv4Gm0G2M6Hz4qgv ybGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=EWewBsgQikyP4ZipJ+uhpXZOTENFdhO0nMRysmYZFzk=; b=OECGjGSzgHR/TrY5s5JPQpMUfyIZo7khw5crmFBlF7HLkUjd1NIFhMaPCeJar/NJOS KEPef0xfrbFbIj7akFBy1cVFkvW6Q/CqwqPYQoGmXuEYVPhlxUH6qBH/dm32nuId9bzr h8uzByVaMvQAbbF60sB7y6kPy7mnKPtwI5HHAuJ+NuWY2sq/f7szVgCl8zX5jPRv37+L xt5ZcMbVWRaf7LEUieRI1dL897O/cbAgFgd+92ambX18vlVsbYaWVZquUf63w2TOxaSd TuEiDWv79XemPI6fdXgnAMdV3FQhjkjQkGC4H/DB1EUSUSl/QVJ+xzq8f0HChPduX+p2 v/Ew== X-Gm-Message-State: AKGB3mJWfeKcaE3xGMwJsGi/SDdzIaPCj+MN7QMkc7Nzuv2eTXgMhgrw WHOdpB/8wYTIJ8iqbUwGYE9M8teq X-Google-Smtp-Source: ACJfBot6Rcdp+NWUi6W8xxNfAF9wbRRikAgnRaqACMyBJ+Hjxyo6KWKW15D2bXz4WZnJs5kXe9HzOA== X-Received: by 10.98.69.209 with SMTP id n78mr46093163pfi.28.1514925779543; Tue, 02 Jan 2018 12:42:59 -0800 (PST) Original-Received: from [10.3.1.41] (50-234-24-126-static.hfc.comcastbusiness.net. [50.234.24.126]) by smtp.gmail.com with ESMTPSA id f3sm10742484pgp.80.2018.01.02.12.42.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jan 2018 12:42:58 -0800 (PST) In-Reply-To: <83tvw6chqv.fsf@gnu.org> X-Mailer: Apple Mail (2.3445.5.20) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:400e:c05::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221539 Archived-At: --Apple-Mail=_48B98CE2-9160-4D1C-AD86-B18D8AF69A3B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Is there any way to patch up the git history for cases like this = (absolutely not a git expert)? I know that we don=E2=80=99t want to edit = history in general, but if there are a set of specific issues liek this, = it might be worth a batch change. ~Chad > On 31Dec, 2017, at 20:42, Eli Zaretskii wrote: >=20 >> From: Steinar Bang >> Date: Mon, 01 Jan 2018 02:05:27 +0100 >>=20 >>>>>>> Andreas Schwab : >>=20 >>> On Dez 31 2017, =C3=93scar Fuentes wrote: >>>> Most likely, the migration tool didn't bother to perform a `git mv >>>> ' and did the equivalent of `cp ; git rm = ; >>>> git add ' instead. >>=20 >>> No, that's exactly the same operation. The problem is that commit >>> b8d4c8d0e9 didn't rename anything. >>=20 >> Yep. This commit only adds that file, and doesn't remove the = existing >> file >=20 > The file was removed in the previous commit. >=20 >> 2007? Was that still CVS? Or was that during bazaar? >=20 > It was Bazaar. >=20 >> How did bazaar track renames? >=20 > Bazaar did track renames, but that commit didn't use "bzr mv". >=20 >> How was bazaar renames handled during the conversion to git? >=20 > I have no idea, but you see the results in the Git repository. --Apple-Mail=_48B98CE2-9160-4D1C-AD86-B18D8AF69A3B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Is = there any way to patch up the git history for cases like this = (absolutely not a git expert)? I know that we don=E2=80=99t want to edit = history in general, but if there are a set of specific issues liek this, = it might be worth a batch change.

~Chad

On 31Dec, 2017, at 20:42, Eli = Zaretskii <eliz@gnu.org> wrote:

From: Steinar Bang <sb@dod.no>
Date:= Mon, 01 Jan 2018 02:05:27 +0100

Andreas Schwab <schwab@linux-m68k.org>:

On Dez 31 2017, = =C3=93scar Fuentes <ofv@wanadoo.es> wrote:
Most likely, the migration tool didn't bother = to perform a `git mv
<from> <to>' and did the = equivalent of `cp <from> <to>; git rm <from>;
git add <to>' instead.

No, that's exactly the same operation. =  The problem is that commit
b8d4c8d0e9 didn't rename = anything.

Yep.  This = commit only adds that file, and doesn't remove the existing
file

The file was removed in the = previous commit.

2007?  Was that still = CVS?  Or was that during bazaar?

It was Bazaar.

How did bazaar track = renames?

Bazaar did track renames, but = that commit didn't use "bzr mv".

How was bazaar renames = handled during the conversion to git?

I have no idea, but you see the results in the = Git repository.

= --Apple-Mail=_48B98CE2-9160-4D1C-AD86-B18D8AF69A3B--