On Thu, Aug 18, 2016 at 6:27 AM, Pino Toscano wrote:
> On Wednesday, 17 August 2016 14:14:34 CEST Jim Meyering wrote:
>> On Wed, Aug 17, 2016 at 6:06 AM, Pino Toscano wrote:
>> > Hi,
>> >
>> > On Tuesday, 29 March 2016 14:15:18 CEST Pino Toscano wrote:
>> >> as discussed in [1], this series adds
On Wednesday, 17 August 2016 14:14:34 CEST Jim Meyering wrote:
> On Wed, Aug 17, 2016 at 6:06 AM, Pino Toscano wrote:
> > Hi,
> >
> > On Tuesday, 29 March 2016 14:15:18 CEST Pino Toscano wrote:
> >> as discussed in [1], this series adds a new getprogname module.
> >> All it does is providing a get
On Wed, Aug 17, 2016 at 6:06 AM, Pino Toscano wrote:
> Hi,
>
> On Tuesday, 29 March 2016 14:15:18 CEST Pino Toscano wrote:
>> as discussed in [1], this series adds a new getprogname module.
>> All it does is providing a getprogname function, much like what is
>> found on e.g. *BSD systems, and usi
Hi,
On Tuesday, 29 March 2016 14:15:18 CEST Pino Toscano wrote:
> as discussed in [1], this series adds a new getprogname module.
> All it does is providing a getprogname function, much like what is
> found on e.g. *BSD systems, and using it in gnulib instead of progname.
> Also, using it explicit
Hi,
as discussed in [1], this series adds a new getprogname module.
All it does is providing a getprogname function, much like what is
found on e.g. *BSD systems, and using it in gnulib instead of progname.
Also, using it explicitly by modules avoids gnulib users the need of
either use the prognam
