ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Alexey Borovskoy <alb@altlinux.ru>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] Q: git.alt: maintenance branch naming
Date: Sat, 11 Nov 2006 01:36:19 +1200
Message-ID: <45548053.8050404@altlinux.ru> (raw)
In-Reply-To: <455433F9.2090104@altlinux.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anton Farygin пишет:
> Sergey Vlasov wrote:
> 
>>Hello!
>>
>>Есть ли какие-то рекомендации по поводу того, как должны называться бранчи
>>для поддержки выпущенных дистрибутивов?
>>
>>В kernel cvs в этой области успел образоваться бардак - там есть бранчи с
>>именами std-2_4_22-patches, Master-2_4, branch-3_0; возможно, на git.alt
>>стоит привести это к какому-то общему стандарту.
> 
> 
> Я думаю что вполне достаточно сделать так:
> alt_linux_3_0
> alt_linux_2_4
> alt_linux_3_1

А может быть упростить:

ALM3.0
ALM2.4
ALM3.1

?

- --
Алексей.
GPG key fingerprint
DBB3 1832 13C6 5C96 4A58 4AFF 78F7 159F 66AD 8D7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFVIBTePcVn2atjX4RApwkAJ93RPsLTqDTGwZXQHDiUwzxDjxymACeMoho
0XtvDM/e2J1EGU4NPAG2iIM=
=Wk4i
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2006-11-10 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 13:11 Sergey Vlasov
2006-11-10  8:10 ` Anton Farygin
2006-11-10  9:27   ` Sergey Vlasov
2006-11-10 11:26     ` Anton Farygin
2006-11-10 13:36   ` Alexey Borovskoy [this message]
2006-11-10 14:22     ` Anton Farygin
2006-11-11 21:24       ` Dmitry V. Levin
2006-11-13 12:57         ` Anton Farygin

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=45548053.8050404@altlinux.ru \
    --to=alb@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