From: Slava Dubrovskiy <slava@tangramltd.com>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] I: branch release naming policy violation
Date: Thu, 05 Feb 2009 12:04:40 +0200
Message-ID: <498AB9B8.4040308@tangramltd.com> (raw)
In-Reply-To: <20090204195534.GD22156@wo.int.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Dmitry V. Levin пишет:
>> + зная, что искать, все равно нашлось не сразу - backports и branch немного
>> названиями отличаются ;-)
>>
>
> Дело тут вот в чём: backports policy -- это не правило формирования
> backports, а правило портирования пакетов.
>
А где находятся правила формирования backports и branch?
Например я правильно понимаю, что если я хочу поместить пакет в бранч,
то сначала я должен поместить пакет в Сизиф?
--
WBR,
Dubrovskiy Vyacheslav
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3262 bytes --]
next prev parent reply other threads:[~2009-02-05 10:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 10:07 ` Dmitry V. Levin
2009-02-04 15:44 ` Stanislav Ievlev
2009-02-04 16:27 ` Dmitry V. Levin
2009-02-04 16:49 ` Ivan A. Melnikov
2009-02-04 17:28 ` Igor Vlasenko
2009-02-05 7:10 ` Vladimir V. Kamarzin
2009-02-05 13:37 ` Денис Смирнов
2009-02-06 7:00 ` Eugene Prokopiev
2009-02-05 12:53 ` Денис Смирнов
2009-02-06 8:57 ` Igor Vlasenko
2009-02-05 6:58 ` Sergey V Turchin
2009-02-04 18:37 ` Denis Pynkin
2009-02-04 18:46 ` Andrey Rahmatullin
2009-02-04 19:04 ` Denis Pynkin
2009-02-04 19:55 ` Dmitry V. Levin
2009-02-05 10:04 ` Slava Dubrovskiy [this message]
2009-02-05 11:10 ` Alexey I. Froloff
2009-02-05 11:33 ` Slava Dubrovskiy
2009-02-06 11:09 ` Ivan Fedorov
2009-02-04 18:53 ` Ivan A. Melnikov
2009-02-04 19:29 ` Igor Vlasenko
2009-02-04 19:40 ` Igor Vlasenko
2009-02-05 8:41 ` Ivan A. Melnikov
2009-02-06 23:49 ` Dmitry V. Levin
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=498AB9B8.4040308@tangramltd.com \
--to=slava@tangramltd.com \
--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