From: Alexey Tourbin <at@altlinux.ru>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Big ChangeLog policy
Date: Fri, 13 Nov 2009 21:01:25 +0300
Message-ID: <20091113180125.GK10659@altlinux.org> (raw)
In-Reply-To: <777d80610911130932s4473f271p2b1dcd75e06bd0e5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Fri, Nov 13, 2009 at 08:32:31PM +0300, Aleksey Novodvorsky wrote:
> 13.11.09, Igor Vlasenko<vlasenko@imath.kiev.ua> написал(а):
> > Уважаемые коллеги,
> > Мы с Игорем Зубковым выносим на обсуждение варианты Big Changelog policy.
> >
> > [19:21:50] <vlasenko> а какое полиси по Big Changelog?
> > в подпакет и сжать,
> > просто сжать?
> > [19:23:14] <icesik> ChangeLog более 200 килобайт это уже много. полиси по этому нет. и проще всего выкинуть это Changelog из пакета. типа s/ChangeLog//g
> >
> > Надо выбрать один из 3-х вариантов,
> > можно предлагать свои.
> >
> > 1) просто сжать
> > 2) в подпакет и сжать
> > 3) убить. (ChangeLog более 200 килобайт это уже много).
> >
> > IMHO Убить.
>
> Не будет ли это нарушением авторского права?
I believe that "Big Changelogs" are written in order to conform
to GPLv2 2a:
You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
Thus, it is formally required to include changelog into source
distribution. It is then arguably not required to include changelogs
into binary packages.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-13 18:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 17:29 Igor Vlasenko
2009-11-13 17:32 ` Aleksey Novodvorsky
2009-11-13 17:36 ` Igor Vlasenko
2009-11-13 17:41 ` Aleksey Novodvorsky
2009-11-13 17:56 ` Igor Vlasenko
2009-11-13 18:06 ` Igor Vlasenko
2009-11-14 10:18 ` [devel] Big ChangeLog policy [gzip|bzip2] Michael Shigorin
2009-11-13 17:46 ` [devel] Big ChangeLog policy Valery V. Inozemtsev
2009-11-13 18:01 ` Alexey Tourbin [this message]
2009-11-13 18:04 ` Igor Vlasenko
2009-11-13 19:39 ` Alexey Tourbin
2009-11-13 20:19 ` Igor Vlasenko
2009-11-13 20:27 ` Led
2009-11-14 5:35 ` Alexey Tourbin
2009-11-14 7:49 ` Andrey Rahmatullin
2009-11-14 11:59 ` Dmitry V. Levin
2009-11-14 14:30 ` Andrey Rahmatullin
2009-11-14 17:09 ` Led
2009-11-14 10:11 ` Michael Shigorin
2009-11-13 17:33 ` Afanasov Dmitry
2009-11-13 17:37 ` Igor Vlasenko
2009-11-13 17:38 ` Andrey Rahmatullin
2009-11-13 17:41 ` Igor Vlasenko
2009-11-13 17:47 ` Igor Vlasenko
2009-11-13 21:21 ` Anton Farygin
2009-11-14 7:36 ` Motsyo Gennadi aka Drool
2009-11-14 10:21 ` Michael Shigorin
2009-11-14 11:28 ` Igor Vlasenko
2009-11-17 14:32 ` Igor Vlasenko
2009-11-16 7:59 ` Timur Batyrshin
2009-11-16 8:11 ` Led
2009-11-16 8:27 ` Afanasov Dmitry
2009-11-16 8:30 ` Led
2009-11-17 14:33 ` Igor Vlasenko
2009-11-17 14:35 ` Igor Vlasenko
2009-11-21 16:12 ` Igor Vlasenko
2009-11-13 17:46 ` Alexey Tourbin
2009-11-14 8:31 ` Sergey Y. Afonin
2009-11-14 10:10 ` Michael Shigorin
2009-11-14 10:13 ` Andrey Rahmatullin
2009-11-14 11:16 ` Igor Vlasenko
2009-11-14 11:18 ` Andrey Rahmatullin
2009-11-14 11:30 ` Igor Vlasenko
2009-11-14 12:18 ` Michael Shigorin
2009-11-14 11:51 ` Anton Farygin
2009-11-18 20:03 ` Igor Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091113180125.GK10659@altlinux.org \
--to=at@altlinux.ru \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git