I've gone ahead and pushed that, so I can start using it in coreutils.
If there are substantial objections, I'll be happy to revise.
>From 57789615cb81dba6075ef76d3faddaa10dc61a07 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Tue, 1 Nov 2011 18:04:21 +0100
Subject: [P
00:00 2001
> From: Jim Meyering
> Date: Tue, 1 Nov 2011 18:04:21 +0100
> Subject: [PATCH] gitlog-to-changelog: provide a ChangeLog-repair mechanism
...
> + # Barf if we fail to use an entry in the --amend=F specified file.
> + my $fail = 0;
> + if ($amend_code)
> +{
> +
Jim Meyering wrote:
> Eric Blake wrote:
>> On 11/01/2011 11:15 AM, Jim Meyering wrote:
>>> I've been thinking about this for years, ever since the unpleasantness
>>> of that first git commit that I mistakenly attributed to myself.
>>>
>>> With this new --amend=FILE option, you'll be able to maintai
Eric Blake wrote:
> On 11/01/2011 11:15 AM, Jim Meyering wrote:
>> I've been thinking about this for years, ever since the unpleasantness
>> of that first git commit that I mistakenly attributed to myself.
>>
>> With this new --amend=FILE option, you'll be able to maintain
>> a list of pairs where
hand-maintain a
touchup file. But even without 'git notes', having this option to fix
history makes sense, and I'm glad to see it made available.
From c190d4ffca4643e40cc22a953ef55f2944bebdd8 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Tue, 1 Nov 2011 18:04:21 +0100
Subje
Jim Meyering wrote:
> I've been thinking about this for years, ever since the unpleasantness
> of that first git commit that I mistakenly attributed to myself.
>
> With this new --amend=FILE option, you'll be able to maintain
> a list of pairs where SHA is a 40-byte SHA1
> (alone on a line) referr
hell on Solaris.
* bootstrap.conf (gnulib_modules): Add gnu-make, posix-shell.
Here's a proposed patch. Though note that I will move some description
and the example from the ChangeLog into the code:
==============================
>From
