Bug#721348: [Piuparts-devel] Bug#721348: clarify how to contribute (v2 patch)

2013-09-02 Thread Holger Levsen
control: tags -1 +pending

Hi,

On Montag, 2. September 2013, Vincent McIntyre wrote:
> > Could you please incorporate these changes and resend your patch?
> Thanks for the warm welcome. Next attempt attached.

thanks, applied.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.


Bug#721348: clarify how to contribute (v2 patch)

2013-09-02 Thread Vincent McIntyre
> Could you please incorporate these changes and resend your patch? 

Thanks for the warm welcome. Next attempt attached.

-- 
>From 2e07d1e01fb28d80dcc00711a0d9be97f72b2ed0 Mon Sep 17 00:00:00 2001
From: Vince McIntyre 
Date: Mon, 2 Sep 2013 20:58:38 +1000
Subject: [PATCH] Clarify how to contribute

---
 CONTRIBUTING | 26 ++
 1 file changed, 26 insertions(+)
 create mode 100644 CONTRIBUTING

diff --git a/CONTRIBUTING b/CONTRIBUTING
new file mode 100644
index 000..9395f1e
--- /dev/null
+++ b/CONTRIBUTING
@@ -0,0 +1,26 @@
+Contributing to this project
+
+
+It's helpful to track fixes or new features via wishlist bugs against the
+'piuparts' package, eg with the 'reportbug' tool ('devscripts' package).
+The BTS will ensure the developers' mailing list
+   piuparts-de...@lists.alioth.debian.org
+is notified.
+
+Patches can be submitted by mail (git format-patch, see below)
+or as requests to pull from a publicly-visible git repository.
+In either case, please make a topic branch based on the 'develop' branch.
+
+You can send patches or requests to the development list,
+or to the tracking bug: @bugs.debian.org.
+
+One possible workflow:
+  git clone git://anonscm.debian.org/piuparts/piuparts.git
+  git checkout origin/develop -b 
+  
+  git commit -a
+  git format-patch -M origin/develop
+
+  reportbug piuparts
+  
+
-- 
1.8.4