From: Ivan Fedorov <ns@altlinux.org>
To: ALT Linux Team development discussions
<public-devel-XbBxUvOt3X3HsNE/8sQLYR2eb7JE58TQ@hugh.gmane.org>
Subject: Re: [devel] релиз пакета, если upstream в git
Date: Mon, 24 Nov 2008 17:06:19 +0300
Message-ID: <m3bpw5fcbo.fsf@altlinux.org> (raw)
In-Reply-To: <774a4f4a0811240226s77257e51m28f395276c17c9cf@mail.gmail.com> (Artem Zolochevskiy's message of "Mon\, 24 Nov 2008 12\:26\:05 +0200")
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
"Artem Zolochevskiy"
<artem.zolochevskiy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> Ну я обычно использую схему alt0.N, где меняется N, если релиз на самом
>> деле pre-1.4, и схему altN.git если релиз post-1.4. :)
>>
>
> ммм...
>
> если 1.4-pre,то
> * 1.4-alt0.1
> - updated to gitXXXXXXXX
> и далее alt0.2 alt0.3 и т.д
>
> если 1.4-post,то
> * 1.4-alt1.git
> - updated to gitXXXXXXXX
> и далее alt2.git alt3.git и т.д.
>
> так?
Почти, в updated лучше писать вывод git describe на ваш коммит с
исходниками. Вот пример из мана:
[torvalds@g5 git]$ git describe parent
v1.0.4-14-g2414721
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2008-11-24 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 16:10 Artem Zolochevskiy
2008-11-24 7:18 ` Denis Klimov
2008-11-24 8:06 ` Artem Zolochevskiy
2008-11-24 9:30 ` Mikhail Gusarov
2008-11-24 9:41 ` Artem Zolochevskiy
2008-11-24 9:48 ` Mikhail Gusarov
2008-11-24 9:54 ` Artem Zolochevskiy
2008-11-24 9:58 ` Mikhail Gusarov
2008-11-24 10:06 ` [devel] релиз пакета , " Led
2008-11-24 10:21 ` Mikhail Gusarov
2008-11-24 16:07 ` [devel] релиз пакета, " Artem Zolochevskiy
2008-11-24 16:37 ` [devel] релиз пакета , " Led
2008-11-25 5:34 ` Denis Klimov
2008-11-24 10:14 ` [devel] релиз пакета, " Ivan Fedorov
2008-11-24 10:26 ` Artem Zolochevskiy
2008-11-24 14:06 ` Ivan Fedorov [this message]
2008-11-24 16:03 ` Artem Zolochevskiy
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=m3bpw5fcbo.fsf@altlinux.org \
--to=ns@altlinux.org \
--cc=devel@lists.altlinux.org \
--cc=public-devel-XbBxUvOt3X3HsNE/8sQLYR2eb7JE58TQ@hugh.gmane.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