Jim Meyering wrote:
> Joel Brobecker wrote:
>>> > Yep, this is what we did for this year. I just want to go one step
>>> > further and just collapse all years into one single range, based on
>>> > the fact that I have verified that we have made significant changes
>>> > to at least one file each ye
Joel Brobecker wrote:
>> > Yep, this is what we did for this year. I just want to go one step
>> > further and just collapse all years into one single range, based on
>> > the fact that I have verified that we have made significant changes
>> > to at least one file each year since 1986.
>>
>> I hav
Joel Brobecker writes:
>> > Yep, this is what we did for this year. I just want to go one step
>> > further and just collapse all years into one single range, based on
>> > the fact that I have verified that we have made significant changes
>> > to at least one file each year since 1986.
>>
>> I
> > Yep, this is what we did for this year. I just want to go one step
> > further and just collapse all years into one single range, based on
> > the fact that I have verified that we have made significant changes
> > to at least one file each year since 1986.
>
> I have already done this for som
I just want to go one step
further and just collapse all years into one single range, based on
the fact that I have verified that we have made significant changes
to at least one file each year since 1986.
Based on my conversations with rms about this, I feel safe to say that
that
Joel Brobecker writes:
>> Good news: the GCS has been updated to explain that using copyright
>> year ranges is now ok. The only conditions are that you perform
>>
>> https://savannah.gnu.org/forum/forum.php?forum_id=6576
>>
>> the strict conversion (i.e., "2002,2004" cannot be converted t
> Good news: the GCS has been updated to explain that using copyright
> year ranges is now ok. The only conditions are that you perform
>
> https://savannah.gnu.org/forum/forum.php?forum_id=6576
>
> the strict conversion (i.e., "2002,2004" cannot be converted to
> "2002-2004") and that you a
Joel Brobecker wrote:
> Hi Jim,
>
>> Currently parted work and an imminent coreutils release are taking all of
>> my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
>
> This really has no urgency at all. I've done the update for GDB and
> we are good for another year.
>
> Al
Hi Jim,
> Currently parted work and an imminent coreutils release are taking all of
> my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
This really has no urgency at all. I've done the update for GDB and
we are good for another year.
Also, I am trying to get the OK from t
Joel Brobecker wrote:
> Hello, and Happy New Year :-).
Hi Joel,
Happy new year to you, too.
Currently parted work and an imminent coreutils release are taking all of
my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
> I am trying to use gnulib's update-copyright script to
Hello, and Happy New Year :-).
I am trying to use gnulib's update-copyright script to update all
of GDB's files. It's working quite beautifully, and it's quite fast
too. I only have a couple of issues:
- C files: In GDB, the style for comments is to avoid the '*'
at the start of new files.
11 matches
Mail list logo
