GNU bug report logs - #36462
[PATCH] Prefer progress-reporter in bookmark.el

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#36462: closed ([PATCH] Prefer progress-reporter in bookmark.el)
Date: Sat, 06 Jul 2019 08:49:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 06 Jul 2019 11:48:03 +0300
with message-id <83wogv8s70.fsf <at> gnu.org>
and subject line Re: bug#36462: [PATCH] Prefer progress-reporter in bookmark.el
has caused the debbugs.gnu.org bug report #36462,
regarding [PATCH] Prefer progress-reporter in bookmark.el
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
36462: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36462
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefan Kangas <stefan <at> marxist.se>
To: bug-gnu-emacs <at> gnu.org
Subject: [PATCH] Prefer progress-reporter in bookmark.el
Date: Mon, 1 Jul 2019 19:14:33 +0200

[Message part 3 (text/plain, inline)]

The attached patch changes remaining uses of `message' to
`make-progress-reporter' where it makes sense in bookmark.el.

Thanks,
Stefan Kangas

[0001-Prefer-progress-reporter-in-bookmark.el.patch (text/x-patch, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 36462-done <at> debbugs.gnu.org
Subject: Re: bug#36462: [PATCH] Prefer progress-reporter in bookmark.el
Date: Sat, 06 Jul 2019 11:48:03 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Mon, 1 Jul 2019 19:14:33 +0200
> 
> The attached patch changes remaining uses of `message' to
> `make-progress-reporter' where it makes sense in bookmark.el.

Thanks, pushed to the master branch.

Would it be possible for you to send a patch when the bug number is
already known, and then include the reference to the bug number in the
log message?  E.g., send just the description first, and the actual
patch after you receive the acknowledgement with the bug number.  That
would allow to apply the patch with "git am", without the necessary
followup with "git commit --amend".

TIA

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.