On Aug 11, 2011, at 14:52, Niels Thykier wrote: > On 2011-08-11 14:33, Jeremiah Foster wrote: >> >> Is this the correct process to commit patches? Do I just do a regular 'git >> diff' in the git repo and then mail to the list? Or is there another format? > > Personally I prefer "git format-patch" patches as they contain author > and commit message. For larger changes, you may want to work in a > branch and then submit the resulting patch(es).
So something like this? From 40b90a004d7fc59581030bc282991bfa12100634 Mon Sep 17 00:00:00 2001 From: "Jeremiah C. Foster" <[email protected]> Date: Thu, 11 Aug 2011 15:07:32 +0200 Subject: [PATCH] Added first draft of developer documentation. --- README.developers | 15 +++++++++++++++ 1 files changed, 15 insertions(+), 0 deletions(-) create mode 100644 README.developers diff --git a/README.developers b/README.developers new file mode 100644 index 0000000..dc1edd0 --- /dev/null +++ b/README.developers @@ -0,0 +1,15 @@ +README.Developers for the Lintian tool +--- + +Lintian dissects Debian packages and tries to find bugs and policy +violations. It contains automated checks for many aspects of Debian +policy as well as some checks for common errors. + +This document describes how you can contribute to Lintian's +development as well as adapt it to your needs. + +Lintian has a large code base which has as its starting point the +directory "frontend." This directory holds the "lintian" executable. +This is what gets called when a user calls lintian. The frontend +then calls the lintian checks which run over the Debian package +that Lintian is checking. -- 1.7.5.4 > Some also publishes a git repository with a branch where they ask for > us to pull from them. I can do that too if that is preferred. Just point to a git repo where the lintian maintainer can pull? > >> If the patch is accepted, do I commit via git? > > You can commit as much as you like; but I do not think you have access > to pushing directly to the main repository. I do not know what the > criteria is to get commit/push access, but maybe someone else can > clarify that. :) That's okay, I don't need a commit bit. I can push stuff to github for example and fire off pull requests from there. Regards, Jeremiah -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
