Coreutils maintainers,
It appears that Bison's bootstrap script is occasionally sync'ed against
Coreutils'. Paul Hilfinger, one of the Bison developers, recently made
the discovery quoted below, which I figure might also be relevant to
Coreutils.
On Fri, 4 Apr 2008, Joel
On Tue, 22 Apr 2008, Jim Meyering wrote:
> > as the preferred method for getting started, avoiding the need to check in
> > bootstrap? Or even have a two-level bootstrap: ./bootstrap is a simple
> > checked-in wrapper which portably calls autom4te on bootstrap_inner.m4sh
> > then runs bootstrap_i
On Tue, 22 Apr 2008, Jim Meyering wrote:
> "Joel E. Denny" <[EMAIL PROTECTED]> wrote:
> There's already a bootstrap module in gnulib.
You mean build-aux/bootstrap?
> We sync things around periodically.
I was hoping for something more formal: all developers comm
On Wed, 23 Apr 2008, Jim Meyering wrote:
> > I was hoping for something more formal: all developers commit their
> > bootstrap-inner.m4sh changes to gnulib instead of to their own projects.
>
> That's already the idea, using gnulib's bootstrap.
Ok, thanks. I wasn't aware.
> > Writing bootstrap
On Wed, 23 Apr 2008, Eric Blake wrote:
> I'm not quite sure what is best to do here. It seems like the simplest
> wrapper might be this untested script (short enough to possibly be worth
> distributing without copyright notice, since adding the notice would
> double its size):
>
> #!/bin/sh
> if
possible comment styles, the following patch manually
concatenates the copyright statement lines in the affected files.
Unfortunately, after many years, copyright statements might wrap around
the margin several times, but I guess that's a small price.
>From 4773a2257e67950f9a0713f7a1cde16f1
On Wed, 29 Jul 2009, Jim Meyering wrote:
> Joel E. Denny wrote:
> > I'd like to use this in Bison. Would you consider contributing
> > build-aux/update-copyright to gnulib so we don't maintain separate copies?
>
> Sure.
Thanks. I'll watch for that. In
ble to extend
this further to automatically format the added text. I might work on that
some other time.
>From ed7de5b95ddc6888592dbe8f38f77b2a6fd83bc9 Mon Sep 17 00:00:00 2001
From: Joel E. Denny
Date: Wed, 29 Jul 2009 09:59:34 -0400
Subject: [PATCH] maint: generalize update-copyright's
On Wed, 29 Jul 2009, Jim Meyering wrote:
> Joel E. Denny wrote:
>
> > On Wed, 29 Jul 2009, Jim Meyering wrote:
> >
> >> Joel E. Denny wrote:
> >
> >> > I'd like to use this in Bison. Would you consider contributing
> >> > buil
On Thu, 30 Jul 2009, Jim Meyering wrote:
> Thank you!
Thank you. :)
> Here's an incremental change I'm about to fold into yours.
> It changes "comment" to "prefix" and adjusts syntax.
Makes sense.
> There remains at least one infelicity: if someone discusses
> the Copyright (C) notation (e.g.
On Thu, 30 Jul 2009, Joel E. Denny wrote:
> On Thu, 30 Jul 2009, Jim Meyering wrote:
> > There remains at least one infelicity: if someone discusses
> > the Copyright (C) notation (e.g., as on this line), and later
> > has the copyright-with-dates line, the prefixes may no
nd more importantly, we should also fix the tool to allow longhand years
> for maintainers that want longhand).
Below are some patches to implement that.
>From 75dd6c0c64ee03ebb4eb7b0b14cf8905b9ad65ad Mon Sep 17 00:00:00 2001
From: Joel E. Denny
Date: Thu, 13 Aug 2009 22:40:34 -0400
Subjec
On Fri, 14 Aug 2009, Jim Meyering wrote:
> > Below are some patches to implement that.
> ...
> > +2009-08-14 Joel E. Denny
> > +
> > + update-copyright: convert 2-digit to 4-digit years
> > + * build-aux/update-copyright: Implement and document.
> &g
't know how to configure update-copyright permanently
for a project. The following patch gives me a way.
>From cf17e05d931eb3e7d995650eb01c354533c61886 Mon Sep 17 00:00:00 2001
From: Joel E. Denny
Date: Fri, 14 Aug 2009 15:26:20 -0400
Subject: [PATCH] maint.mk: support update-copyright-env
*
14 matches
Mail list logo
