Conflicts:
	META
	NEWS

Conflicts:
	src/plugins/select/bluegene/bg_job_info.c

There was also some bad code that would reset the conn_type of a block
to SMALL no matter what type of SMALL it was.

Patsh from Rod Schulz, Bull.

into allowing them.

to NULL otherwise.

step.  If so there is no need to do any step cleanup since the allocation
has already been cleaned up.

don't need to.

looking for 1 midplane, no reason to go through any more than that.

when having multiple steps per job.

MAX should have been MIN

This was due to a bug in select/cons_res with some configuration
optiions and job options, especially if there is more than one
thread per core and the job option includes "--threads-per-core=1".
Fixes problem reported by CSCS.

Conflicts:
	src/slurmctld/job_mgr.c

lock was deemed not necessary because the information (db_index) was only
internal and was only modified in the same function later which is
protected by the write lock.

qos on the cluster to fill that in correctly.

incorrectly when getting fairshare from the parent.

Patches from Andriy Grytsenko (Massive Solutions Limited).

Cross cluster communication doesn't work with srun.

steps in the allocation if --no-kill is used on the allocation.

partial of each node.

ignoring all nodeboards in error state.

Moe,

I found that I need the following lines added in
order to allow LLONG_MIN and LLONG_MAX to be used
in the range routines.

Phil