From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, 28792@debbugs.gnu.org
Subject: bug#28792: 26.0.60; Deleting to a custom trash directory in Dired gives error
Date: Sun, 15 Oct 2017 09:47:28 -0400 [thread overview]
Message-ID: <87wp3w8qvj.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAFyQvY3LkSOPDC44UOWGLVz9e6OvpFDxR91q768erYxH5RLPgA@mail.gmail.com> (Kaushal Modi's message of "Sun, 15 Oct 2017 13:35:16 +0000")
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Is it that the bug got reopened automatically when Tino merged it
> with another bug, and so it had to be re-closed?
Looks like, yes. The command was 'forcemerge 28828 28792' which puts
the open bug first, hence this bug gets reopened.
https://debbugs.gnu.org/cgi/bugreport.cgi?msg=78;bug=28792
next prev parent reply other threads:[~2017-10-15 13:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 3:26 bug#28792: 26.0.60; Deleting to a custom trash directory in Dired gives error Kaushal Modi
2017-10-12 3:36 ` Kaushal Modi
2017-10-12 3:51 ` Kaushal Modi
2017-10-12 12:50 ` Göktuğ Kayaalp
2017-10-12 12:58 ` Eli Zaretskii
2017-10-12 13:02 ` Kaushal Modi
2017-10-12 13:37 ` Göktuğ Kayaalp
2017-10-12 12:58 ` Kaushal Modi
2017-10-12 13:16 ` Eli Zaretskii
2017-10-12 13:31 ` Kaushal Modi
2017-10-12 13:44 ` Eli Zaretskii
2017-10-12 14:02 ` Andreas Schwab
2017-10-12 14:06 ` Kaushal Modi
2017-10-12 15:07 ` Kaushal Modi
2017-10-12 15:15 ` Eli Zaretskii
2017-10-12 15:27 ` Andreas Schwab
2017-10-12 15:31 ` Kaushal Modi
2017-10-12 20:25 ` Paul Eggert
2017-10-12 21:41 ` Kaushal Modi
2017-10-15 7:18 ` Paul Eggert
2017-10-15 13:35 ` Kaushal Modi
2017-10-15 13:47 ` Noam Postavsky [this message]
2017-10-12 14:24 ` Noam Postavsky
2017-10-12 14:43 ` Drew Adams
2017-10-12 15:07 ` Andreas Schwab
2017-10-12 15:10 ` Drew Adams
2017-10-12 13:34 ` Tino Calancha
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp3w8qvj.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=28792@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=kaushal.modi@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).