gmane.comp.sysutils.automake.general archive

393 archived articles, newest first (page 4 of 4). Latest articles →

Re: End of life dates vs regression test matrix
Fri, 14 Jun 2024 07:59:56 -0500
Bob Friesenhahn <[email protected]> • #16467
Re: End of life dates vs regression test matrix
Fri, 14 Jun 2024 00:14:38 -0500
Jacob Bachmeyer <[email protected]> • #16466
End of life dates vs regression test matrix
Thu, 13 Jun 2024 21:12:04 -0700
Dan Kegel <[email protected]> • #16465
Re: 1.16.90 regression: configure now takes 7 seconds to start
Fri, 14 Jun 2024 01:59:37 +0200
Bruno Haible <[email protected]> • #16464
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 13 Jun 2024 16:54:12 -0600
Karl Berry <[email protected]> • #16463
Re: improved timestamp resolution test (was: 1.16.90 regression: configure now takes 7 seconds to start)
Thu, 13 Jun 2024 16:09:59 -0600
Karl Berry <[email protected]> • #16462
Re: 1.16.90 regression: configure now takes 7 seconds to start
Thu, 13 Jun 2024 16:09:58 -0600
Karl Berry <[email protected]> • #16461
Re: 1.16.90 regression: configure now takes 7 seconds to start
Thu, 13 Jun 2024 14:23:23 +0200
Bruno Haible <[email protected]> • #16460
Re: 1.16.90 regression: configure now takes 7 seconds to start
Thu, 13 Jun 2024 13:50:56 +0900
Simon Richter <[email protected]> • #16459
Re: improved timestamp resolution test (was: 1.16.90 regression: configure now takes 7 seconds to start)
Wed, 12 Jun 2024 23:31:27 -0500
Jacob Bachmeyer <[email protected]> • #16458
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 20:44:29 -0500
Jacob Bachmeyer <[email protected]> • #16457
Re: Bug Resilience Program of German Sovereign Tech Fund
Wed, 12 Jun 2024 20:31:52 -0500
Jacob Bachmeyer <[email protected]> • #16456
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 19:29:45 -0600
Karl Berry <[email protected]> • #16455
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 19:29:46 -0600
Karl Berry <[email protected]> • #16454
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 14:50:14 -0600
Karl Berry <[email protected]> • #16453
Re: Bug Resilience Program of German Sovereign Tech Fund
Wed, 12 Jun 2024 22:15:45 +0200
Christoph Grüninger <[email protected]> • #16452
Re: Bug Resilience Program of German Sovereign Tech Fund
Wed, 12 Jun 2024 21:55:28 +0200
Christoph Grüninger <[email protected]> • #16451
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 10:03:14 -0400
"Zack Weinberg" <[email protected]> • #16450
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 15:54:45 +0900
Simon Richter <[email protected]> • #16449
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 02:20:53 -0400
[email protected] • #16448
Re: 1.16.90 regression: configure now takes 7 seconds to start
Tue, 11 Jun 2024 23:04:05 -0500
Jacob Bachmeyer <[email protected]> • #16447
Re: 1.16.90 regression: configure now takes 7 seconds to start
Wed, 12 Jun 2024 02:45:15 +0200
Bruno Haible <[email protected]> • #16446
Re: 1.16.90 regression: configure now takes 7 seconds to start
Tue, 11 Jun 2024 17:00:46 -0600
Karl Berry <[email protected]> • #16445
Re: 1.16.90 regression: configure now takes 7 seconds to start
Tue, 11 Jun 2024 17:00:49 -0600
Karl Berry <[email protected]> • #16444
Re: Bug Resilience Program of German Sovereign Tech Fund
Tue, 11 Jun 2024 17:00:48 -0600
Karl Berry <[email protected]> • #16443
Re: 1.16.90 regression: configure now takes 7 seconds to start
Tue, 11 Jun 2024 17:00:48 -0600
Karl Berry <[email protected]> • #16442
Re: 1.16.90 regression: configure now takes 7 seconds to start
Sat, 8 Jun 2024 11:01:26 -0400
Nick Bowler <[email protected]> • #16441
Re: 1.16.90 regression: configure now takes 7 seconds to start
Fri, 07 Jun 2024 23:04:16 -0500
Jacob Bachmeyer <[email protected]> • #16440
Re: 1.16.90 regression: configure now takes 7 seconds to start
Sat, 8 Jun 2024 12:21:27 +0900
Simon Richter <[email protected]> • #16439
system info in test-suite.log
Fri, 07 Jun 2024 17:24:13 +0200
Bruno Haible <[email protected]> • #16438
Re: 1.16.90 regression: configure now takes 7 seconds to start
Sat, 08 Jun 2024 01:50:46 +0200
Bruno Haible <[email protected]> • #16437
First draft of application to Sovereign Tech Fund
Fri, 7 Jun 2024 21:23:11 +0200
Christoph Grüninger <[email protected]> • #16436
Re: 1.16.90 regression: configure now takes 7 seconds to start
Fri, 07 Jun 2024 18:26:06 -0500
Jacob Bachmeyer <[email protected]> • #16435
1.16.90 regression: configure now takes 7 seconds to start
Sat, 08 Jun 2024 00:27:39 +0200
Bruno Haible <[email protected]> • #16434
no easy way to generate a test-suite.log without skipped tests
Fri, 07 Jun 2024 18:26:15 +0200
Bruno Haible <[email protected]> • #16433
Re: Bug Resilience Program of German Sovereign Tech Fund
Fri, 7 Jun 2024 14:44:59 -0700
Paul Eggert <[email protected]> • #16432
Re: Bug Resilience Program of German Sovereign Tech Fund
Fri, 7 Jun 2024 00:20:06 +0200
Christoph Grüninger <[email protected]> • #16431
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 13:17:51 -0700
Paul Eggert <[email protected]> • #16430
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 19:48:46 +0200
Christoph Grüninger <[email protected]> • #16429
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 19:43:25 +0200
Christoph Grüninger <[email protected]> • #16428
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 09:30:30 -0700
Paul Eggert <[email protected]> • #16427
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 06 Jun 2024 11:10:29 -0400
"Zack Weinberg" <[email protected]> • #16426
automake-1.16.90 released
Thu, 06 Jun 2024 07:40:47 -0700
Jim Meyering <[email protected]> • #16425
Re: Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 07:37:11 -0700
Dan Kegel <[email protected]> • #16424
Bug Resilience Program of German Sovereign Tech Fund
Thu, 6 Jun 2024 15:09:13 +0200
Christoph Grüninger <[email protected]> • #16423
Re: small patch to make a test work with upcoming autoconf
Sun, 2 Jun 2024 21:55:47 -0700
Jim Meyering <[email protected]> • #16422
small patch to make a test work with upcoming autoconf
Sun, 2 Jun 2024 18:25:16 -0700
Jim Meyering <[email protected]> • #16421
Re: automake 1.17 release plan?
Wed, 15 May 2024 07:35:33 -0400
Will Estes <[email protected]> • #16420
Re: automake 1.17 release plan?
Wed, 15 May 2024 08:22:45 +0200
Christoph Grüninger <[email protected]> • #16419
Re: automake 1.17 release plan?
Tue, 14 May 2024 19:18:50 -0600
Karl Berry <[email protected]> • #16418
automake 1.17 release plan?
Tue, 14 May 2024 21:53:06 +0200
Christoph Grüninger <[email protected]> • #16417
Re: How to force libtool to use CXX mode?
Mon, 13 May 2024 16:27:38 -0600
Karl Berry <[email protected]> • #16416
Re: How to force libtool to use CXX mode?
Mon, 13 May 2024 17:22:01 -0500
Bob Friesenhahn <[email protected]> • #16415
Re: How to force libtool to use CXX mode?
Mon, 13 May 2024 15:37:59 -0600
Karl Berry <[email protected]> • #16414
How to force libtool to use CXX mode?
Sun, 12 May 2024 16:01:12 -0500
Bob Friesenhahn <[email protected]> • #16413
Re: follow-up on backdoor CPU usage (was: libsystemd dependencies)
Fri, 26 Apr 2024 20:28:39 -0500
Jacob Bachmeyer <[email protected]> • #16412
Re: GCC reporting piped input as a security feature
Fri, 12 Apr 2024 21:14:41 -0500
Jacob Bachmeyer <[email protected]> • #16411
Re: GCC reporting piped input as a security feature
Thu, 11 Apr 2024 20:19:47 -0400
"Zack Weinberg" <[email protected]> • #16410
Re: GCC reporting piped input as a security feature
Tue, 09 Apr 2024 22:35:05 -0500
Jacob Bachmeyer <[email protected]> • #16409
Re: GCC reporting piped input as a security feature
Tue, 09 Apr 2024 22:35:26 -0500
Jacob Bachmeyer <[email protected]> • #16408
Re: GCC reporting piped input as a security feature
Tue, 9 Apr 2024 13:07:39 -0400
"Alan D. Salewski" <[email protected]> • #16407
Re: GCC reporting piped input as a security feature
Tue, 9 Apr 2024 07:27:19 +0200 (CEST)
Jan Engelhardt <[email protected]> • #16406
Re: GCC reporting piped input as a security feature
Mon, 08 Apr 2024 22:37:50 -0500
Jacob Bachmeyer <[email protected]> • #16405
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Mon, 08 Apr 2024 18:32:01 -0400
Richard Stallman <[email protected]> • #16404
Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Mon, 08 Apr 2024 18:29:46 -0400
Richard Stallman <[email protected]> • #16403
Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Mon, 08 Apr 2024 18:29:45 -0400
Richard Stallman <[email protected]> • #16402
Re: detecting modified m4 files (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Sun, 07 Apr 2024 19:26:38 -0500
Jacob Bachmeyer <[email protected]> • #16401
Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Fri, 05 Apr 2024 23:49:02 -0500
Jacob Bachmeyer <[email protected]> • #16400
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Fri, 05 Apr 2024 17:42:32 -0400
Richard Stallman <[email protected]> • #16399
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Fri, 05 Apr 2024 16:37:02 +0100
Sam James <[email protected]> • #16398
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Fri, 05 Apr 2024 02:04:42 +0200
Bruno Haible <[email protected]> • #16397
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Thu, 04 Apr 2024 18:43:40 -0400
Richard Stallman <[email protected]> • #16396
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Thu, 04 Apr 2024 18:43:39 -0400
Richard Stallman <[email protected]> • #16395
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Thu, 04 Apr 2024 18:42:59 -0400
Richard Stallman <[email protected]> • #16394
Re: libsystemd dependencies
Wed, 03 Apr 2024 18:37:23 -0400
Richard Stallman <[email protected]> • #16393
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Wed, 03 Apr 2024 01:07:04 -0400
"Alfred M. Szmidt" <[email protected]> • #16392
Re: compressed release distribution formats (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Tue, 02 Apr 2024 20:34:16 -0500
Jacob Bachmeyer <[email protected]> • #16391
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 20:33:13 -0500
Jacob Bachmeyer <[email protected]> • #16390
Re: checking aclocal m4 files (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Tue, 02 Apr 2024 20:32:32 -0500
Jacob Bachmeyer <[email protected]> • #16389
Re: binary data in source trees (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Tue, 02 Apr 2024 20:31:08 -0500
Jacob Bachmeyer <[email protected]> • #16388
Re: reproducible dists and builds (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)
Tue, 02 Apr 2024 20:30:49 -0500
Jacob Bachmeyer <[email protected]> • #16387
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 2 Apr 2024 18:11:30 -0400
Jeffrey Walton <[email protected]> • #16386
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 2 Apr 2024 17:05:51 -0500
Bob Friesenhahn <[email protected]> • #16385
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 2 Apr 2024 16:04:49 -0600
Karl Berry <[email protected]> • #16384
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 2 Apr 2024 16:49:54 -0500
Bob Friesenhahn <[email protected]> • #16383
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 17:43:11 -0400
Richard Stallman <[email protected]> • #16382
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 17:42:50 -0400
Richard Stallman <[email protected]> • #16381
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 17:40:48 -0400
Richard Stallman <[email protected]> • #16380
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 17:40:47 -0400
Richard Stallman <[email protected]> • #16379
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 17:39:53 -0400
Richard Stallman <[email protected]> • #16378
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 2 Apr 2024 16:37:47 -0500
Eric Blake <[email protected]> • #16377
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 13:25:06 +0200
Bruno Haible <[email protected]> • #16376
Re: GNU Coding Standards, automake, and the recent xz-utils backdoor
Tue, 02 Apr 2024 10:38:26 +0200
"Jose E. Marchesi" <[email protected]> • #16375
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.