summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016955.html
blob: 054deb284280fb0f4b2d3dd1173306fa5bc94d0c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Backports Summary
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C201206280400.36341.cooker%40solbu.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016946.html">
   <LINK REL="Next"  HREF="016961.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports Summary</H1>
    <B>Johnny A. Solbu</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C201206280400.36341.cooker%40solbu.net%3E"
       TITLE="[Mageia-dev] Backports Summary">cooker at solbu.net
       </A><BR>
    <I>Thu Jun 28 04:00:33 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016946.html">[Mageia-dev] Backports Summary
</A></li>
        <LI>Next message: <A HREF="016961.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16955">[ date ]</a>
              <a href="thread.html#16955">[ thread ]</a>
              <a href="subject.html#16955">[ subject ]</a>
              <a href="author.html#16955">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wednesday 27 June 2012 20:05, andre999 wrote:
&gt;<i> However talking about _backport repos_, exactly how we tag them is arbitrary.
</I>
The fact that this stirs a huge conversation surely serves to show that it is Not arbitrarely how we tag them.

&gt;<i> Although obviously backports are updates relative to the initial release 
</I>&gt;<i> in question, so it is not unreasonable to tag the backport repos as updates.
</I>
No, it is Not obvious.
It is called Backports for a reason. It is software that is not part of the release, and is to be treated as experimental/beta software, as it could wery well break your system if you don't know what you are doing.

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: &lt;/pipermail/mageia-dev/attachments/20120628/0cd598a7/attachment-0001.asc&gt;
</PRE>
























<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016946.html">[Mageia-dev] Backports Summary
</A></li>
	<LI>Next message: <A HREF="016961.html">[Mageia-dev] Backports Summary
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16955">[ date ]</a>
              <a href="thread.html#16955">[ thread ]</a>
              <a href="subject.html#16955">[ subject ]</a>
              <a href="author.html#16955">[ author ]</a>
         </LI>
       </UL>

<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>