time for an xfsdump release?

[Nathan Scott]

Hi,

----- Original Message -----
> There aren't a lot of changes since v3.1.3, but with the rate of change of
> xfsdump (slow), I wonder if it's worth cutting a point release to get these
> bugfixes out there:

I've verified and pushed a few Debian packaging updates folks have sent
through to the git tree below.  Please include these odds & ends too...

thanks!


Changes committed to git://oss.sgi.com/nathans/xfsdump.git master

 debian/Makefile  |    2 +-
 debian/changelog |    8 ++++++++
 debian/control   |    2 +-
 debian/rules     |    3 +++
 debian/watch     |    3 +++
 5 files changed, 16 insertions(+), 2 deletions(-)

commit 96be05e971e1e23c252f5432fe430cd724a52910
Author: Nathan Scott <nathans at debian.org>
Date:   Wed Jul 16 13:29:12 2014 +1000

    xfsdump: update debian packaging for next release
    
    Make a note of each of the Debian bugs resolved in this release,
    so that they'll be automatically closed during next upload.
    
    Signed-off-by: Nathan Scott <nathans at debian.org>

commit f33aa73b89624feaeb94f4d48b88f2d480798420
Author: Nathan Scott <nathans at debian.org>
Date:   Wed Jul 16 13:25:36 2014 +1000

    xfsdump: add a watch file into the debian packaging
    
    Apparently it can improve some Debian tools that check it (e.g. UDD).
    Resolves Debian bug #748482.
    
    Signed-off-by: Nathan Scott <nathans at debian.org>

commit fae9bcf317ce3a0d919ebdc6fd667993a4dbd484
Author: Nathan Scott <nathans at debian.org>
Date:   Wed Jul 16 13:21:27 2014 +1000

    xfsdump: rebuild configure files during deb package builds
    
    Use the same technique applied to xfsprogs recently to tackle
    out-of-date config.{sub,guess} files in the build.
    
    Resolves Debian bug #746531.
    
    Signed-off-by: Nathan Scott <nathans at debian.org>