From: <osv@javad.com>
To: 5181@emacsbugs.donarmstrong.com
Subject: bug#5181: [PATCH] vc-revert-file: fix setting of file time-stamp into the past.
Date: Fri, 11 Dec 2009 20:21:38 +0300 [thread overview]
Message-ID: <878wd9whnh.fsf_-_@osv.gnss.ru> (raw)
In-Reply-To: <handler.5181.B.126054797316423.ack@emacsbugs.donarmstrong.com> (Emacs bug Tracking System's message of "Fri\, 11 Dec 2009 16\:15\:05 +0000")
This bug was supposed to be a patch to bug#3298 instead, -- sorry for
sending it to a wrong address.
next prev parent reply other threads:[~2009-12-11 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 16:12 bug#5181: [PATCH] vc-revert-file: fix setting of file time-stamp into the past Sergei Organov
[not found] ` <handler.5181.B.126054797316423.ack@emacsbugs.donarmstrong.com>
2009-12-11 17:21 ` osv [this message]
2011-07-13 7:57 ` 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=878wd9whnh.fsf_-_@osv.gnss.ru \
--to=osv@javad.com \
--cc=5181@emacsbugs.donarmstrong.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).