From: Dmitry Gutov <dmitry@gutov.dev>
To: Olivier Certner <ocert.dev@free.fr>, Eli Zaretskii <eliz@gnu.org>
Cc: 62693-done@debbugs.gnu.org
Subject: bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it
Date: Thu, 20 Apr 2023 13:22:56 +0300 [thread overview]
Message-ID: <4c4ccb20-ea8c-7721-bfdb-02aef3786460@gutov.dev> (raw)
In-Reply-To: <4034636.ERVBdo8R52@ravel>
On 20/04/2023 12:42, Olivier Certner wrote:
> Hi,
>
>> Thank, but please always mention the bug number in the commit log
>> messages.
>
> This is what I did in all my previous fixes, by first sending the bug
> description and only then patches with the commit messages having the bug
> number. I didn't do it this time because this is a (minor) annoyance consuming
> a bit of time. In order to help maintainers, I'll make sure I revert to my
> previous behavior in future submissions.
Thank you. This was more of an omission on my part (I forgot to check),
given that at the time when the bug is first submitted, the bug number
is not known anyway.
> Thanks.
>
> PS: Don't know if this was intentional, but you sent the mail to
> 62693@debbugs.gnu.org, which AFAIU reopens the bug.
Nah, it doesn't. When closed, it stays closed.
next prev parent reply other threads:[~2023-04-20 10:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:51 bug#62693: 28.2; VC: CVS: Fix lost file reporting and enable reverting it Olivier Certner
2023-04-12 22:48 ` Dmitry Gutov
2023-04-13 16:40 ` Olivier Certner
2023-04-14 22:59 ` Dmitry Gutov
2023-04-15 9:28 ` Eli Zaretskii
2023-04-17 9:24 ` Olivier Certner
2023-04-17 17:48 ` Eli Zaretskii
2023-04-17 20:10 ` Olivier Certner
2023-04-19 0:54 ` Dmitry Gutov
2023-04-19 8:10 ` Olivier Certner
2023-04-20 8:55 ` Eli Zaretskii
2023-04-20 9:42 ` Olivier Certner
2023-04-20 10:22 ` Dmitry Gutov [this message]
2023-04-17 8:04 ` Olivier Certner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c4ccb20-ea8c-7721-bfdb-02aef3786460@gutov.dev \
--to=dmitry@gutov.dev \
--cc=62693-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ocert.dev@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.