[bind10-dev] Running make check/distcheck and git status before pushing merges

Mukund Sivaraman muks at isc.org
Tue Jun 4 15:36:00 UTC 2013


Hi all

This is a follow-up from our bi-weekly DNS meeting.

As a best practice, before any commits are pushed to the `master` branch
in the bind10 git repository, we should:

* Run `make check` at the top-level of the bind10 tree, and verify that
  it passes.

* If we have modified configure.ac or Makefile.am to add/remove any
  files, run `make distcheck` at the top-level of the bind10 tree and
  verify that it passes.

* Run `git status` after `make check` completes at the top-level of the
  bind10 tree and check if there are any files that are left and show up
  in the `git status` output. Such files may have to be cleaned up by
  tests which create them, or be added to .gitignore files. If we add
  any configure.ac/Makefile.am rules for generated content, we should
  remember to add corresponding .gitignore rules for them.

		Mukund
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20130604/ef8544d7/attachment.bin>


More information about the bind10-dev mailing list