zarb-ml/mageia-dev/2011-June/006011.html


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Proposal of a backporting process
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106251954.03904.maarten.vanraes%40gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006010.html">
   <LINK REL="Next"  HREF="006013.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Proposal of a backporting process</H1>
    <B>Maarten Vanraes</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106251954.03904.maarten.vanraes%40gmail.com%3E"
       TITLE="[Mageia-dev] Proposal of a backporting process">maarten.vanraes at gmail.com
       </A><BR>
    <I>Sat Jun 25 19:54:03 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006010.html">[Mageia-dev] Proposal of a backporting process
</A></li>
        <LI>Next message: <A HREF="006013.html">[Mageia-dev] Proposal of a backporting process
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6011">[ date ]</a>
              <a href="thread.html#6011">[ thread ]</a>
              <a href="subject.html#6011">[ subject ]</a>
              <a href="author.html#6011">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Op zaterdag 25 juni 2011 19:33:15 schreef Samuel Verschelde:
[...]
&gt;<i> However, I think it must be made a painless as possible to packagers :
</I>&gt;<i> - in the common case, allow to submit directly from cauldron to the
</I>&gt;<i> backports media, but let the BS detect that and automatically do the SVN
</I>&gt;<i> copy part. 
</I>&gt;<i> - for the situations I described above, work with the backport
</I>&gt;<i> branch similarly as we work on updates (technically speaking : SVN,
</I>&gt;<i> BS...).
</I>[...]

i would prefer to keep things separate, an mgarepo switch command or even a 
mgarepo backport shortcut, then current branch/revision/whatever could be made 
into backports or something...
and from then on, you can submit like &quot;normal&quot;
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006010.html">[Mageia-dev] Proposal of a backporting process
</A></li>
	<LI>Next message: <A HREF="006013.html">[Mageia-dev] Proposal of a backporting process
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6011">[ date ]</a>
              <a href="thread.html#6011">[ thread ]</a>
              <a href="subject.html#6011">[ subject ]</a>
              <a href="author.html#6011">[ 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>