BIND 10 trac3109, updated. d640e2711d36ff59c9adf84b092ccba7f17ef46a [3109] Re-justify paragraph (after changes in previous commits)
BIND 10 source code commits
bind10-changes at lists.isc.org
Thu Sep 12 06:52:57 UTC 2013
The branch, trac3109 has been updated
via d640e2711d36ff59c9adf84b092ccba7f17ef46a (commit)
via 0e24ff0516f95c8f0ae4a4b82892d97e40891530 (commit)
via 14aecfe2eb61e067200a91684eec7b04b10e0634 (commit)
via 08d4a94ef93b4a1fb0ba0fcbadc3793793c8c73a (commit)
via e674965bfb4fefd24fd44b70e80429ddea92e6ca (commit)
via e18f0aeceb9095198c3081cbd08e772a5715baf8 (commit)
via 2f326350f8f49fd6db247d38d6c3575e9e82a0a5 (commit)
via d2b3d82dc02b9e6fe5fab81b78f6dfc532888d3b (commit)
via 46e6d05e9f1c6990c17afff7890607db8c5acc04 (commit)
via cfd7033c2710b19d92d719f54ceb50fe866261bc (commit)
from 8ce7f740b84364774d90f3438634577cc556ae66 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit d640e2711d36ff59c9adf84b092ccba7f17ef46a
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:22:33 2013 +0530
[3109] Re-justify paragraph (after changes in previous commits)
commit 0e24ff0516f95c8f0ae4a4b82892d97e40891530
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:22:12 2013 +0530
[3109] Update text
commit 14aecfe2eb61e067200a91684eec7b04b10e0634
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:18:03 2013 +0530
[3109] Re-justify paragraph (after changes in previous commits)
commit 08d4a94ef93b4a1fb0ba0fcbadc3793793c8c73a
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:17:51 2013 +0530
[3109] Update text
commit e674965bfb4fefd24fd44b70e80429ddea92e6ca
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:16:54 2013 +0530
[3109] Add punctuation
commit e18f0aeceb9095198c3081cbd08e772a5715baf8
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:15:56 2013 +0530
[3109] Re-justify paragraph (after changes in previous commits)
commit 2f326350f8f49fd6db247d38d6c3575e9e82a0a5
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:15:03 2013 +0530
[3109] Update text
commit d2b3d82dc02b9e6fe5fab81b78f6dfc532888d3b
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:14:04 2013 +0530
[3109] Add articles
commit 46e6d05e9f1c6990c17afff7890607db8c5acc04
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:13:18 2013 +0530
[3109] Update text for easier reading
commit cfd7033c2710b19d92d719f54ceb50fe866261bc
Author: Mukund Sivaraman <muks at isc.org>
Date: Thu Sep 12 12:11:48 2013 +0530
[3109] Add article and trailing newline
-----------------------------------------------------------------------
Summary of changes:
doc/devel/contribute.dox | 56 ++++++++++++++++++++++++----------------------
1 file changed, 29 insertions(+), 27 deletions(-)
-----------------------------------------------------------------------
diff --git a/doc/devel/contribute.dox b/doc/devel/contribute.dox
index f5f3e24..0d57974 100644
--- a/doc/devel/contribute.dox
+++ b/doc/devel/contribute.dox
@@ -22,34 +22,36 @@ changes and not get disappointed in the process.
@section contributorGuideWritePatch Writing a patch
-Before you start working on a patch or new feature, it is a good idea
-to discuss it first with BIND10 developers. You can post your
-questions to bind10-dev
+Before you start working on a patch or a new feature, it is a good idea
+to discuss it first with BIND10 developers. You can post your questions
+to the \c bind10-dev mailing list
(https://lists.isc.org/mailman/listinfo/bind10-dev) for general BIND10
-stuff or to bind10-dhcp
-(https://lists.isc.org/mailman/listinfo/bind10-dhcp) mailing lists for DHCP specific
+stuff, or to the \c bind10-dhcp mailing list
+(https://lists.isc.org/mailman/listinfo/bind10-dhcp) for DHCP specific
topics. If you prefer to get faster feedback, most BIND10 developers
-hang out at bind10 jabber room
-(xmpp:bind10 at conference.jabber.isc.org). Those involved in DHCP also
-use dhcp chatroom (xmpp:dhcp at conference.jabber.isc.org). Feel free to
-drop a note. It is possible that someone else is working on your
-specific issue or perhaps the solution you plan to implement is not
-the best one. Often having 10 minutes talk could save many hours of
-engineering work.
-
-First step would be to get a source code from our GIT repository. The procedure
-is very easy and is explained here: http://bind10.isc.org/wiki/GitGuidelines.
-While it is possible to provide a patch against stable release, it makes
-the review process much easier if it is for latest code grom a git 'master' branch.
-
-Ok, so you have a patch? Great! Before you submit it, make sure that
-your code compiles. This may seem obvious, but it there's more to
-it. I'm sure you have checked that it compiles on your system, but
-BIND10 is a portable software. Besides Linux, it is being compiled on
-relatively uncommon systems, like OpenBSD or Solaris 11. Will your
-code compile there? Will it work? What about endianess? It is likely
-that you used regular x86, but the software is expected to run on many
-other architectures.
+hang out in the \c bind10 jabber room
+(xmpp:bind10 at conference.jabber.isc.org). Those involved in DHCP also use
+the \c dhcp chatroom (xmpp:dhcp at conference.jabber.isc.org). Feel free to
+join these rooms and talk to us. It is possible that someone else is
+working on your specific issue or perhaps the solution you plan to
+implement is not the best one. Often having a 10 minute talk could save
+many hours of engineering work.
+
+First step would be to get the source code from our Git repository. The
+procedure is very easy and is explained here:
+http://bind10.isc.org/wiki/GitGuidelines. While it is possible to
+provide a patch against the latest stable release, it makes the review
+process much easier if it is for latest code from the Git \c master
+branch.
+
+Ok, so you have written a patch? Great! Before you submit it, make sure
+that your code compiles. This may seem obvious, but there's more to
+it. You have surely checked that it compiles on your system, but BIND10
+is portable software. Besides Linux, it is compiled and used on
+relatively uncommon systems like OpenBSD and Solaris 11. Will your code
+compile and work there? What about endianess? It is likely that you used
+a regular x86 architecture machine to write your patch, but the software
+is expected to run on many other architectures.
Does your patch conforms to BIND10
http://bind10.isc.org/wiki/CodingGuidelines? You still can submit
@@ -149,4 +151,4 @@ and more. Although it is not possible for non ISC employees to run tests
on that farm, it is possible that your contributed patch will end up there
sooner or later.
-*/
\ No newline at end of file
+*/
More information about the bind10-changes
mailing list