It was not possible to cut or delete bitmap references from bitmap view.
I don't think using -idirafter is appropriate on the gcc commands.
Bug when loading a type3 font with references.
Merge branch 'master' of ssh://fontforge.git.sourceforge.net/gitroot/fontforge/fontforge
Somehow code got lost that was supposed to preserve open font filenames across application exit and restart
Adam Twardoch reports a few glitches in feature files output:

- in the 'size' feature the parameters were written with a locale-dependent
decimal separator, while the decimal dotis only allowed by the spec;

- FF used to generate empty definitions for standard GDEF classes if there
were no glyphs to assign to them, while they should have been omitted
according to the spec. Although the class names in GlyphClassDef should be
comma-separated, and the positions for omitted classes still should be
indicated with commas.

Moreover, FF would put some glyphs into wrong classes due to a difference
between its internal standard class IDs and ones used in the feature file
syntax.
The previous patch for control point selection had an odd side effect
of losing control points when moving them around their original location.
The gasp table version was ignored when writing and opening SFD files.
Merge branch 'master' of ssh://fontforge.git.sourceforge.net/gitroot/fontforge/fontforge
Various patche from Steve White, mainly related with Unicode glyph ranges.
Khaled notices a typo in math kerning dialog.
A wrong Descender value has been written into generated afm files, if
the font lacked typical glyphs with descenders.
A patch from Haled, fixing a memory issue in python interface.
When displaying a pair of kerned glyphs in a tooltip box, FF would actually
ignore the left bearing of the second glyph. If bearing was negative (e. g.
in case of a combining mark) this could even result into a crash.
Khaled reports a typo in SFD format documentation.
Kerning pairs associated with a glyph weren't properly reinstantiated when
reverting that glyph from the original SFD file. This could result to crashes
(e. g. when attempting to save the font).
Merge branch 'master' of ssh://fontforge.git.sourceforge.net/gitroot/fontforge/fontforge
When the user moved a control point, and that cp got close to the other cp, then ff would stap back to the original location of the cp. In other words, you could not put two cps (of the same base point) on top of one another. Or not easily.
When closing a gradient window, ff tended to crash.
PostScript and PDF patterns/gradients behave differently with respect to the current transformation matrix, and I didn't get that right (comes up when a reference containing a pattern/gradient is transformed).
Also didn't handle opacity properly in pdf.