From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Alexander Klimov <alserkli@inbox.ru>,
12666@debbugs.gnu.org, Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Subject: bug#12666: dired sort by date in ange-ftp dired buffers
Date: Wed, 17 Oct 2012 19:45:10 -0400 [thread overview]
Message-ID: <k8k3uowtmh.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <507F3952.6050302@cs.ucla.edu> (Paul Eggert's message of "Wed, 17 Oct 2012 16:03:46 -0700")
Paul Eggert wrote:
> As near as I can make out the problem was introduced in trunk bzr
> 104541, so I'll CC: this to Alexander.
Nope. r101356, back in 2010.
http://lists.gnu.org/archive/html/emacs-diffs/2010-09/msg00106.html
next prev parent reply other threads:[~2012-10-17 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 23:03 bug#12666: dired sort by date in ange-ftp dired buffers Paul Eggert
2012-10-17 23:45 ` Glenn Morris [this message]
2012-10-18 3:51 ` Glenn Morris
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=k8k3uowtmh.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=12666@debbugs.gnu.org \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--cc=alserkli@inbox.ru \
--cc=eggert@cs.ucla.edu \
/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).