[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#482102: qa.debian.org: intelligent listing of debian/patches, git/quilt v3 format packages, etc



Package: qa.debian.org
Severity: wishlist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

this is both a request and an notice of intent that i may try to
implement something :)

my proposal is that the current "patches" section on a source package's
qa package is modified so that the following information is somehow
provided, where appropriate (depending on structure/format of source
package naturally).

- - entire "debian patch"
- - individual quilt/dpatch patches
- - individual patches from v3 (quilt) format packages
- - feature-branch patches for v3 (git) format packages, if possible
  (would require more thinking through and i do not intend to do this initially)

additionally, for each patch, when possible provide the following
information:

- - which version of the package introduced it
- - any notes at the top of the patch
- - any relevant vcs metadata
- - any relevant bts metadata (could be found using heuristics in the
  previous items)
- - html markup and standard format versions of each patch for download/review

obviously not all of this could be gleaned automatically, but i imagine
much of it could, and with a few heuristics the rest could be figured
out.  future versions could also provide a way for packagers to override
such heuristics in the case of errors/false-positives.

questions/comments/etc welcome

	sean

- -- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIMyAMynjLPm522B0RAn/sAJ0TgRckJm/4yDdcxcrOaEC4vcLl4QCfVKvQ
lUtRYrVFQZPR6PqxxBOH+qM=
=Sggx
-----END PGP SIGNATURE-----



Reply to: