[task #16067] Submission of Dezyne

Follow-up Comment #11, task #16067 (project administration): What is holding up accepting this package? >From what I see the issues raised are minor. ___ Reply to this item at:

[task #15914] Submission of Intlfonts

Follow-up Comment #5, task #15914 (project administration): Is there a reason why this is still open? GNU intlfonts is a GNU package, and we have been hosting it since several years. ___ Reply to this item at:

[task #16067] Submission of Dezyne

Follow-up Comment #14, task #16067 (project administration): Lets please assume best intentions, people miss things. The files are small and can be considered non-copyrightable, so please don't dismiss it so abruptly. The examples/README also declares what the license is of the examples (AGPL).

Re: [task #16067] Submission of Dezyne

I'm sorry; in fact, I wasn't so busy as I was puzzled. Files like doc/examples/join.dzn should contain valid copyright and license notices, and if they are part of documentation, their license should be GFDL-compatible. I fail to explain why you missed that. Lets please assume best i

[task #16067] Submission of Dezyne

Follow-up Comment #17, task #16067 (project administration): For the examples, another solution is to license them under the AGPL and the GFDL. Your reading of the requirements is far to strict and not what is intended, the rules do not apply only to binaries, and it is not a matter of size. The

[task #16345] Submission of Gprofng GUI

Follow-up Comment #5, task #16345 (project administration): [comment #1 comment #1:] > Copyrightable files like gprofng_gui.spec rpmbuild.sh README have no [//savannah.gnu.org/maintenance/ValidNotices/ valid copyright and license notices], as well as the images e.g. in org/gprofng/mpmt/icons. >

[task #16345] Submission of Gprofng GUI

Follow-up Comment #8, task #16345 (project administration): We have gone through this before, your reading of those guidelines is wrong as has been explained MULTIPLE TIMES before. Now you are complaining about a typo of all things. ___

[Savannah-register-public] [task #4564] Submission of Hurd's AlteRnative Development

Follow-up Comment #7, task #4564 (project administration): Logged in now. I might note that other Hurd developers will use this new branch for their code. Sergio, I hope that you will not follow through with this fork, it will only hurt the community. _

[Savannah-register-public] [task #4564] Submission of Hurd's AlteRnative Development

Follow-up Comment #11, task #4564 (project administration): Sergio, sorry, but I must call you a liar. You know perfectly well that the branch in question is _NOT_ my branch, it is called ams-branch, but anyone with commit access is free to commit any kind of change they feel is approriate. Th

[Savannah-register-public] [task #4564] Submission of Hurd's AlteRnative Development

Follow-up Comment #14, task #4564 (project administration): Sergio, you still don't get it, ams-branch is not my branch. Nobody has to talk to me to get something commited there. The only rude one here is being you by quoting totally irrelevant information that isn't even related to this. Keep

[Savannah-register-public] [task #7218] Submission of hurdlx01

Follow-up Comment #8, task #7218 (project administration): The GNU project already has a project for the GNU system installer, it is part of the GNU Packaging project. If this is the same effort that someone submited to the [EMAIL PROTECTED] list, then we should incoperate it into the already ex