From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Should we restore manually maintained ChangeLogs Date: Thu, 10 Mar 2016 12:34:39 +0200 Message-ID: <8360wumxj4.fsf@gnu.org> References: <83lh5utbxb.fsf@gnu.org> <56DDD02A.20809@cs.ucla.edu> <83fuw2t2ue.fsf@gnu.org> <56DE0F6A.6010207@cs.ucla.edu> <83pov5rmt6.fsf@gnu.org> <56DFD78F.40205@cs.ucla.edu> <56E06093.7050509@cs.ucla.edu> <83twkfo7ij.fsf@gnu.org> <20160309181005.GF3948@acm.fritz.box> <87vb4vuu59.fsf@thinkpad.rath.org> <87pov3nrnm.fsf@linux-m68k.org> <83mvq6n7xs.fsf@gnu.org> <83d1r2mzuy.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1457606114 23259 80.91.229.3 (10 Mar 2016 10:35:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 10 Mar 2016 10:35:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 10 11:35:09 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1adxvw-00068E-FD for ged-emacs-devel@m.gmane.org; Thu, 10 Mar 2016 11:35:08 +0100 Original-Received: from localhost ([::1]:47500 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxvv-0008EE-Tr for ged-emacs-devel@m.gmane.org; Thu, 10 Mar 2016 05:35:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42342) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxvW-0008BR-D5 for emacs-devel@gnu.org; Thu, 10 Mar 2016 05:34:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adxvS-0002Gc-5K for emacs-devel@gnu.org; Thu, 10 Mar 2016 05:34:42 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39392) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adxvS-0002GY-2V; Thu, 10 Mar 2016 05:34:38 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1273 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1adxvQ-0003Ee-5t; Thu, 10 Mar 2016 05:34:37 -0500 In-reply-to: (message from Andreas Schwab on Thu, 10 Mar 2016 11:00:47 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:201367 Archived-At: > From: Andreas Schwab > Cc: emacs-devel@gnu.org > Date: Thu, 10 Mar 2016 11:00:47 +0100 > > > More generally, can we put something in .git/config that would cause > > that namespace to be pulled by default? > > git config --add remote.origin.fetch +refs/replace/*:refs/replace/* OK, thanks. So how does one go about creating a replacement commit for a commit that was pushed upstream? The man page of "git replace" mentions "git rebase", but I cannot find anything pertinent on the rebase man page. The procedure described here: https://git-scm.com/book/en/v2/Git-Tools-Replace sounds quite complicated. If we need to do all that every time we want to fix a single commit, I'd expect a lot of mistakes and snafus. But maybe there's an easier way, in which case we could consider this feature as part of the solution for fixing mistakes in log messages.