diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006011.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006011.html | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006011.html b/zarb-ml/mageia-dev/2011-June/006011.html new file mode 100644 index 000000000..132b11632 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006011.html @@ -0,0 +1,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: +[...] +><i> However, I think it must be made a painless as possible to packagers : +</I>><i> - in the common case, allow to submit directly from cauldron to the +</I>><i> backports media, but let the BS detect that and automatically do the SVN +</I>><i> copy part. +</I>><i> - for the situations I described above, work with the backport +</I>><i> branch similarly as we work on updates (technically speaking : SVN, +</I>><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 "normal" +</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> |