Re: [PATCH 0/3] sb/config-write-fix done without robbing Peter

2018-08-02 Thread Junio C Hamano
Stefan Beller writes: >> Am I correct to understand that this patch is a "FIX" for breakage >> introduced by that commit? The phrasing is not helping me to pick >> a good base to queue these patches on. > > Please pick 4f4d0b42bae (Merge branch 'js/empty-config-section-fix', > 2018-05-08) > as

Re: [PATCH 0/3] sb/config-write-fix done without robbing Peter

2018-08-01 Thread Eric Sunshine
On Wed, Aug 1, 2018 at 3:34 PM Stefan Beller wrote: > The first patch stands as is unchanged, and the second and third patch > are different enough that range-diff doesn't want to show a diff. For future reference, range-diff's --creation-factor tweak may help here. Depending upon just how

[PATCH 0/3] sb/config-write-fix done without robbing Peter

2018-08-01 Thread Stefan Beller
> Am I correct to understand that this patch is a "FIX" for breakage > introduced by that commit? The phrasing is not helping me to pick > a good base to queue these patches on. Please pick 4f4d0b42bae (Merge branch 'js/empty-config-section-fix', 2018-05-08) as the base of this new series (am