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

Re: fs-uae_2.4.1+ds-2~bpo70+1_amd64.changes REJECTED



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am 21.05.14 09:03, schrieb Vincent Cheng:
> It's certainly not the only way to see changes done in a backport 
> (fetching the changelog manually does the job equally well,
> although it is less convenient). I guess the question to be
> answered here is whether the frustration and time lost due to the
> "-v" requirement is worth the added convenience of having a full
> set of changes sent to the list for each upload.

As all the uploads are announced to debian-backports-changes, many
(like me) are monitoring this list. Having the changes since the last
upload to the recent version in bpo/stable here is the right place.

Fetching all that stuff manually is moving the load from uploaders to
users, which are (hopefully) much more people affected.

Anyways ... just opening the browser at
http://packages.qa.debian.org/<package> and having a look at the
version table, doing copy&paste is just 30 seconds work.

Cheers, Jan.
- -- 
Never write mail to <waja@spamfalle.info>, you have been warned!
- -----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V-
PS PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++
- ------END GEEK CODE BLOCK------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTfFOSAAoJEAxwVXtaBlE+FloQAJcQRgBwF0qMFYb+2t4H/f6M
2sg6mqFop2dnfBe9bmrSxnNlVNg6zorU5yAJWyhg/YppM8U4fKU+h3rprNXz5BgF
YZqN8f1triXBtXhMZGTuw+sNRI4WYF1r4xXB02HdOwJhJvXjQh62zeRXU6Ub9GhY
fdnTy7KXvtIHbP/2Z898f0qYGgbPZ6FvsFIwZc/Jcq2SU8TYZNFzN8CYGWCg5hPe
vKvJXkC1ycYnInZxBeiIKs2xxbppzcmZ7e0vwOL7/sVVl12d7kSklr/cm5DfU56O
ULPtVoWOObNfsK74/LAomM8K6MZolarHguhuHprweCBmxEgbP5ho1bH11e6BXASk
lkYqyQ0Nq6BJIWvfIjSKfNcTaZRpwAGDEFypnIpK0STwJdS/z9jzjyGxvLLW/KKg
UYL3h+czUOHxpvHxMWqq16krSPcviV4elO71WkKcXdcZFKH5fgk4pqxOqWq4xkxD
dkS52Th7/0du9COr+5fhYm4SY1bATbIGKudM/LUQnQ4jPRN4wkFWmXu6b5qmg2vT
jT7hnyjOUyIhdK5UFffarmdyVMMaNBWopDI08uFQQ5/Pp9b5bmSwLl7hEiwioQ8F
CM6Tq/PxKM6W2kJDQ14XwtA7NNfMVig3DUOWLLMW3GTlvIotdvvgzwcUgQnrK3BL
YfSMPdtCwZ9h4r5aFG/h
=BlqT
-----END PGP SIGNATURE-----


Reply to: