Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 53cb105

Browse files
committed
Merge pull request #107 from jekil/master
Removed "How to Apply These Terms to Your New Program"
2 parents dcf8a27 + 3e0e2f3 commit 53cb105

1 file changed

Lines changed: 0 additions & 58 deletions

File tree

doc/COPYING

Lines changed: 0 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -344,61 +344,3 @@ POSSIBILITY OF SUCH DAMAGES.
344344

345345
END OF TERMS AND CONDITIONS
346346

347-
How to Apply These Terms to Your New Programs
348-
349-
If you develop a new program, and you want it to be of the greatest
350-
possible use to the public, the best way to achieve this is to make it
351-
free software which everyone can redistribute and change under these terms.
352-
353-
To do so, attach the following notices to the program. It is safest
354-
to attach them to the start of each source file to most effectively
355-
convey the exclusion of warranty; and each file should have at least
356-
the "copyright" line and a pointer to where the full notice is found.
357-
358-
<one line to give the program's name and a brief idea of what it does.>
359-
Copyright (C) <year> <name of author>
360-
361-
This program is free software; you can redistribute it and/or modify
362-
it under the terms of the GNU General Public License as published by
363-
the Free Software Foundation; either version 2 of the License, or
364-
(at your option) any later version.
365-
366-
This program is distributed in the hope that it will be useful,
367-
but WITHOUT ANY WARRANTY; without even the implied warranty of
368-
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
369-
GNU General Public License for more details.
370-
371-
You should have received a copy of the GNU General Public License along
372-
with this program; if not, write to the Free Software Foundation, Inc.,
373-
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
374-
375-
Also add information on how to contact you by electronic and paper mail.
376-
377-
If the program is interactive, make it output a short notice like this
378-
when it starts in an interactive mode:
379-
380-
Gnomovision version 69, Copyright (C) year name of author
381-
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
382-
This is free software, and you are welcome to redistribute it
383-
under certain conditions; type `show c' for details.
384-
385-
The hypothetical commands `show w' and `show c' should show the appropriate
386-
parts of the General Public License. Of course, the commands you use may
387-
be called something other than `show w' and `show c'; they could even be
388-
mouse-clicks or menu items--whatever suits your program.
389-
390-
You should also get your employer (if you work as a programmer) or your
391-
school, if any, to sign a "copyright disclaimer" for the program, if
392-
necessary. Here is a sample; alter the names:
393-
394-
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
395-
`Gnomovision' (which makes passes at compilers) written by James Hacker.
396-
397-
<signature of Ty Coon>, 1 April 1989
398-
Ty Coon, President of Vice
399-
400-
This General Public License does not permit incorporating your program into
401-
proprietary programs. If your program is a subroutine library, you may
402-
consider it more useful to permit linking proprietary applications with the
403-
library. If this is what you want to do, use the GNU Lesser General
404-
Public License instead of this License.

0 commit comments

Comments
 (0)