blob: 83bfa7ce30c2a10b31db80eb919b45a8bc6386d1 (
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
100
101
102
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] RFC: Opening Backports (once again...)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C201112060828.45956.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="010215.html">
<LINK REL="Next" HREF="010221.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C201112060828.45956.alien%40rmail.be%3E"
TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">alien at rmail.be
</A><BR>
<I>Tue Dec 6 08:28:45 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="010215.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI>Next message: <A HREF="010221.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10219">[ date ]</a>
<a href="thread.html#10219">[ thread ]</a>
<a href="subject.html#10219">[ subject ]</a>
<a href="author.html#10219">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op dinsdag 06 december 2011 00:29:03 schreef Anssi Hannula:
><i> On 06.12.2011 00:56, Thomas Backlund wrote:
</I>><i> > Now,
</I>><i> >
</I>><i> > here comes the question about backports once again.
</I>[...]
><i> > Using a separate branch is also a cleaner way of providing
</I>><i> > backports, and makes it easy to separate changes needed only
</I>><i> > for Cauldron (or backports).
</I>><i>
</I>><i> Hm, how does this help with enabling backports (i.e. compared to simply
</I>><i> using cauldron repo)?
</I>
not sure, but i thought the problem we're facing now was that submitting from
cauldron to backports was a "problem" in security scripting, ie: not being
able to specify 2 sources? than this would solve that problem?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="010215.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI>Next message: <A HREF="010221.html">[Mageia-dev] RFC: Opening Backports (once again...)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#10219">[ date ]</a>
<a href="thread.html#10219">[ thread ]</a>
<a href="subject.html#10219">[ subject ]</a>
<a href="author.html#10219">[ 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>
|
