loadstone bit

If your inventory is full and you aren't already carrying a loadstone,
you can pick one up into the overflow slot.  But if you are already
carrying one and the one you're trying to pick up won't merge with it
(only criterium that matters would be BUC state, I think), you can't
pick it up and get a message saying so.  If loadstone isn't known
yet, the message always referred to it as "gray stone" rather than
"stone called <whatever-you-called-it>".

doc/fixes3-7-0.txt

@@ -1352,6 +1352,9 @@ some uses of mons[obj->corpsenm] weren't excluding obj->corpsenm==NON_PM (-1)
 if a covetous monster tried to teleport next to the hero but the level was
 	completely full, it would be booted off the level (set to migrate
 	back if the hero left and returned) instead of just staying put
+if loadstone was unIDed but had been assigned a type name and you failed to
+	pick one up, the message referred to it as "gray stone" rather than
+	"stone called <assigned name>"
 
 
 Fixes to 3.7.0-x General Problems Exposed Via git Repository

src/pickup.c

@@ -1702,9 +1702,12 @@ lift_object(
             || merge_choice(gi.invent, obj))
             return 1; /* lift regardless of current situation */
         /* if we reach here, we're out of slots and already have at least
-           one of these, so treat this one more like a normal item */
+           one of these, so treat this one more like a normal item
+           [this was using simpleonames(obj) for shortest description, but
+           that's suboptimal for loadstones because it omits user-assigned
+           type name which is something of interest for gray stones] */
         You("are carrying too much stuff to pick up %s %s.",
-            (obj->quan == 1L) ? "another" : "more", simpleonames(obj));
+            (obj->quan == 1L) ? "another" : "more", xname(obj));
         return -1;
     }