cores)

A node can be used by two core based reservations overlapping in time

Conflicts:
	src/common/node_conf.c
	src/common/node_conf.h
	src/plugins/select/cons_res/select_cons_res.c
	src/plugins/select/serial/select_serial.c

Conflicts:
	src/plugins/select/bluegene/bl_bgq/bridge_status.cc

Adding cr_get_coremap_offset as a global function

+extern uint32_t cr_get_coremap_offset(uint32_t node_index)
+{
	+       return cr_node_cores_offset[node_index];
	+}

Conflicts:
	src/plugins/select/cons_res/select_cons_res.c
	src/slurmctld/reservation.c
	testsuite/expect/inc3.11.1
	testsuite/expect/inc3.11.7
	testsuite/expect/inc3.11.8
	testsuite/expect/test3.11

Conflicts:
	META
	NEWS

Conflicts:
	src/common/slurm_cred.c
	testsuite/expect/test12.2

no big deal, but now we get just a bit more memory allocated (4152 over
instead of the 4100 we were previously looking for)

Conflicts:
	configure
	doc/html/cray.shtml

they are a no-opt when they get to the DBD and we would favor having
job completion messages instead of step completion messages if possible.

or previous piecemeal method.

Adapted from a patch from Stephen Trofinoff <trofinoff@cscs.ch>