Submitting patches

Jonathan Nieder jrnieder at uchicago.edu
Thu May 29 10:31:21 UTC 2008


Dear Debian gpm maintainers,

I have five mostly trivial patches to submit as a by-product of trying
to get things to build:

 * Run autoheader from debian/rules
 * debian/rules: Make use of both doc/old/Changelog and ./Changes
 * Update packaging to reflect soname change
 * Build-conflict with libncurses-dev (workaround)
 * Drop various patches:
    - 015_libgpm_noverbose.patch, because it does not fix the problem
    - 001_logging.patch, 008_sun_repeat_000, and 030_segfault, applied
      upstream
    - 006_version_000, since the upstream soname is higher

At any rate, the patches are up at

    http://home.uchicago.edu/~jrnieder/gpm.git for-debian

or if you are interested in the patches alone,

    http://home.uchicago.edu/~jrnieder/patches/gpm/

They apply on top of 1.20.3~pre3-3, as tagged in svn (r320). 

What is the usual protocol for submitting a collection of patches? I
could submit a bug for each one, but I would want to know that that is
appropriate first. Sorry to fill your mailboxes with all this, and
thanks for the help.

Sincerely,
Jonathan



More information about the pkg-gpm-devel mailing list