Re: libutil shlib_version lossage
Date: Fri, 14 Aug 2015 03:23:08 + From: Taylor R Campbell Something very strange happened recently, which I noticed by tracing the forced update in joerg@'s Git mirror: [...] Whisky tango foxtrot? Did someone botch a cvs admin? >From discussion with kamil@ in private, the answer is `yes'. I cleaned it up with some more cvs adminning, and made the change I assume kamil@ intended to make (replace `shalib' by `shlib' in the commit message). This will cause another Git forced update, but with any luck, it should restore the history from 2012 to a month ago as it was before the botched cvs admin. General reminder: cvs admin is dangerous business and can wreak all sorts of havoc, and causes trouble for anyone following the Git mirror. If you think you want to do it, please (a) ask yourself whether it's really warranted (one-character typo in commit message?); (b) notify source-changes-d if you made a serious mistake; and (c) ask another developer to double-check your `cvs admin' invocation first before you do it. (That said: in spite of its danger, cvs admin is nevertheless not an effective way to sneak changes into the CVS repository, because anyone following the Fossil or Git mirror will notice.)
Re: libutil shlib_version lossage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 14.08.2015 08:53, Christos Zoulas wrote: > In article <20150814032236.1da9260...@jupiter.mumble.net>, Taylor R > Campbell wrote: >> Whisky tango foxtrot? Did someone botch a cvs admin? > > Looks that way, let's verify first and then we can fix it. > > christos > > I will investigate it and prepare a proper patch for review to address i t. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVz35MAAoJEEuzCOmwLnZsu0YP/3dc2QjTbb4yCVPer8l3Gudg Hn0a8pyrt0qjBhSBCBquE0bG4QX6tWYvEE3v3+mSrH0Da68R5bCaGw/MUpkYYeZW z3gKBszDlYKYndIIlFX7++TxDA/smBl7R5kZjqGjc48SLd2BMxrLf41h8YU502+t 5XbQleS6yM9Km42IdTWxEemFp39GMauJEh6lGZda8ld7iWettXCcS960D4Ooigeb jIz3LXJa86JHt1V+uW8NhtDw8+6DPFBGM85cfZ29JOMF10FkvdhZ3uUInuVA583C YErBkUfpl8Aa+5ROVnodCCEd7tAbFLz2kPDEwM2TUGX1I03+m0duNdkKbP8zEy8+ g96QeeXBe3Dwrd1iCeJo3vHIeAe0ygGbK0/6LKo/qYyYwYtTmOkb6AiWlb9mV26b 3EpfYv1yYj5bapRDs+cl9pAYGJJ6EyhcEVlFw/n4LHp30QJSBATE1T3BoWwHABOk bjoU2w02+G1RSvJ89DenP+TPZNrPxRNpu19xGh8818tB4gYxETo4/oICtvDQtzXZ knCn1yDsFqMvoihWkj/t9NnIErdJNmgywRZBgpIsZ8dIhz6idxs5HnFnFiao/lI0 YL38UrTtnvot+ojEiBOWeJoH17r68pE2Vg1ARKpiR+A0uDbf0arCiD2c85mrdc+1 k7w1XTQxL5DnWMUqVkWN =SIzK -END PGP SIGNATURE-
Re: libutil shlib_version lossage
In article <20150814032236.1da9260...@jupiter.mumble.net>, Taylor R Campbell wrote: >Something very strange happened recently, which I noticed by tracing >the forced update in joerg@'s Git mirror: > >+Author: christos >+Date: Sat Apr 7 16:44:39 2012 + >+ >+Bump shlib minor for new function: ereallocarr(3) >+ >+Noted by >+ > diff --git a/lib/libutil/shlib_version b/lib/libutil/shlib_version > index a658a26..7115edc 100644 > --- a/lib/libutil/shlib_version >@@ -50118645,7 +50118653,9 @@ > Author: christos > Date: Wed Jul 8 17:29:56 2015 + > >-bump bind libraries >+Bump shlib minor for new function: ereallocarr(3) >+ >+Noted by > > diff --git a/distrib/sets/lists/base/shl.mi >b/distrib/sets/lists/base/shl.mi > >The CVS log for lib/libutil/shlib_version now shows an anachronistic >commit about ereallocarr: > >revision 1.52 >date: 2015-07-26 15:15:31 +; author: kamil; state: Exp; >lines: +2 -2; co >mmitid: axBRfUsc0duU7Ouy; >Bump shalib minor for new function: ereallocarr(3) > >Noted by > >revision 1.51 >date: 2012-04-07 16:44:39 +; author: christos; state: Exp; >lines: +2 -2; >Bump shlib minor for new function: ereallocarr(3) > >Noted by > >Likewise the CVS log for distrib/sets/lists/base/shl.mi: > > revision 1.744 > date: 2015-07-26 15:15:31 +; author: kamil; state: Exp; lines: >+3 -3; co > mmitid: axBRfUsc0duU7Ouy; >Bump shalib minor for new function: ereallocarr(3) > > Noted by > > revision 1.743 > date: 2015-07-08 17:29:56 +; author: christos; state: Exp; >lines: +8 -8; >commitid: zxPJFEcgglAbsvsy; >Bump shlib minor for new function: ereallocarr(3) > > Noted by > >Whisky tango foxtrot? Did someone botch a cvs admin? Looks that way, let's verify first and then we can fix it. christos
libutil shlib_version lossage
Something very strange happened recently, which I noticed by tracing the forced update in joerg@'s Git mirror: +Author: christos +Date: Sat Apr 7 16:44:39 2012 + + +Bump shlib minor for new function: ereallocarr(3) + +Noted by + diff --git a/lib/libutil/shlib_version b/lib/libutil/shlib_version index a658a26..7115edc 100644 --- a/lib/libutil/shlib_version @@ -50118645,7 +50118653,9 @@ Author: christos Date: Wed Jul 8 17:29:56 2015 + -bump bind libraries +Bump shlib minor for new function: ereallocarr(3) + +Noted by diff --git a/distrib/sets/lists/base/shl.mi b/distrib/sets/lists/base/shl.mi The CVS log for lib/libutil/shlib_version now shows an anachronistic commit about ereallocarr: revision 1.52 date: 2015-07-26 15:15:31 +; author: kamil; state: Exp; lines: +2 -2; co mmitid: axBRfUsc0duU7Ouy; Bump shalib minor for new function: ereallocarr(3) Noted by revision 1.51 date: 2012-04-07 16:44:39 +; author: christos; state: Exp; lines: +2 -2; Bump shlib minor for new function: ereallocarr(3) Noted by Likewise the CVS log for distrib/sets/lists/base/shl.mi: revision 1.744 date: 2015-07-26 15:15:31 +; author: kamil; state: Exp; lines: +3 -3; co mmitid: axBRfUsc0duU7Ouy; Bump shalib minor for new function: ereallocarr(3) Noted by revision 1.743 date: 2015-07-08 17:29:56 +; author: christos; state: Exp; lines: +8 -8; commitid: zxPJFEcgglAbsvsy; Bump shlib minor for new function: ereallocarr(3) Noted by Whisky tango foxtrot? Did someone botch a cvs admin?
