> OK - Please see attached as a first attempt
This looks good, but not all files are covered. I suppose this was
intentional...
Werner
On Friday 26 December 2008 19:59:55 Werner LEMBERG wrote:
> > Basically what is needed is to upgrade all the source headers from
> > GPL2 to the following text:
> >
> > This file is part of groff.
> >
> > groff is free software: you can redistribute it and/or modify it
> > under the ter
> Basically what is needed is to upgrade all the source headers from
> GPL2 to the following text:
>
> This file is part of groff.
>
> groff is free software: you can redistribute it and/or modify it
> under the terms of the GNU General Public License as published
> by the Free S
On Monday 22 December 2008 19:18:15 Werner LEMBERG wrote:
> You could update all copyright notices from GPL2 to GPL3. This is
> something which should be done before the release, and which is
> completely non-technical. This would be indeed a great help!
Sure thing - since I'm new to this I just
> If there's anything I can do to assist in any way from a non-C-coder
> point of view, please let me know - I'd really like to see more
> utf-8 capabilities in groff so that we can move closer to a fully
> utf-8-capable console during 2009.
You could update all copyright notices from GPL2 to GPL3
> Werner, if you do decide to make a release, can you give us a day or
> two's warning? There are a couple of small fixes to the mom macros
> I've been holding off on checking in. Thanks.
Let's say the deadline is Dec. 28th.
Werner
On Mon, Dec 15, 2008, Halim Issa wrote:
> But my gut feeling tells me that if current cvs a) is used
> by yourself and a few others on a (semi-)daily basis without
> problems, and b) you have been at least somewhat restrictive
> against letting sloppy patches in, maybe releasing current cvs
> as 1.
Hi Werner,
On Monday 15 December 2008 14:13:53 Werner LEMBERG wrote:
> It should be released as soon as possible, I fully agree.
> Unfortunately, it's only me who is working on groff, and I can't
> afford enough time to really come to the point where I can
> wholeheartily say `it's time to do a re
> I've been searching the mailing list archives and wikis to try to
> understand why there has been no groff release for years, while
> during the same time what seems like a lot of useful commits have
> been done to the source code.
Sigh.
> I am sure there are good reasons from the core develop
All,
I've been searching the mailing list archives and wikis to try to understand
why there has been no groff release for years, while during the same time what
seems like a lot of useful commits have been done to the source code.
I am sure there are good reasons from the core developers to dev
10 matches
Mail list logo
