From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen@xemacs.org, yandros@MIT.EDU, emacs-devel@gnu.org
Subject: Re: Bootstrap deleted DOC-nnn file
Date: Sun, 12 May 2013 15:39:59 -0400 [thread overview]
Message-ID: <E1Ubc7j-0007IF-Cy@fencepost.gnu.org> (raw)
In-Reply-To: <83d2swaom8.fsf@gnu.org> (message from Eli Zaretskii on Sun, 12 May 2013 06:00:47 +0300)
Don't you update from bzr whenever you build? If so, sorting your
files by time stamp will show you your previous updates, which
correspond to your builds.
Thanks. This shows that my previous update was Mar 28.
The bug did not occur in that version.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call
next prev parent reply other threads:[~2013-05-12 19:39 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 0:22 Bootstrap deleted DOC-nnn file Richard Stallman
2013-05-10 9:24 ` Eli Zaretskii
2013-05-10 11:02 ` Stephen J. Turnbull
2013-05-10 12:51 ` Eli Zaretskii
2013-05-10 17:01 ` Stephen J. Turnbull
2013-05-10 17:19 ` Eli Zaretskii
2013-05-11 2:46 ` Stephen J. Turnbull
2013-05-10 22:08 ` Richard Stallman
2013-05-10 22:33 ` chad
2013-05-11 3:09 ` Stephen J. Turnbull
2013-05-11 12:10 ` Richard Stallman
2013-05-11 16:49 ` Richard Stallman
2013-05-11 17:16 ` Eli Zaretskii
2013-05-11 21:44 ` Richard Stallman
2013-05-11 22:14 ` Christopher Schmidt
2013-05-12 19:39 ` Richard Stallman
2013-05-12 3:00 ` Eli Zaretskii
2013-05-12 19:39 ` Richard Stallman [this message]
2013-05-12 20:00 ` Eli Zaretskii
2013-05-13 14:09 ` Richard Stallman
2013-05-13 16:27 ` Andreas Schwab
2013-05-14 13:32 ` Richard Stallman
2013-05-14 16:32 ` Paul Eggert
2013-05-15 11:43 ` Richard Stallman
2013-05-15 12:22 ` Eli Zaretskii
2013-05-15 13:24 ` Xue Fuqiao
2013-05-15 23:27 ` Richard Stallman
2013-05-15 19:08 ` Stefan Monnier
2013-05-15 22:37 ` Xue Fuqiao
2013-05-14 16:54 ` Andreas Schwab
2013-05-15 11:43 ` Richard Stallman
2013-05-15 12:20 ` Eli Zaretskii
2013-05-15 23:27 ` Richard Stallman
2013-05-13 16:30 ` Eli Zaretskii
2013-05-12 2:45 ` Stephen J. Turnbull
2013-05-12 15:33 ` Eli Zaretskii
2013-05-12 19:39 ` Richard Stallman
2013-05-12 19:39 ` Richard Stallman
2013-05-12 23:32 ` Stephen J. Turnbull
2013-05-13 23:47 ` Richard Stallman
2013-05-14 1:24 ` Stephen J. Turnbull
2013-05-12 19:39 ` Richard Stallman
2013-05-12 23:04 ` Stephen J. Turnbull
2013-05-11 7:13 ` Eli Zaretskii
2013-05-11 12:10 ` Richard Stallman
2013-05-11 12:58 ` Eli Zaretskii
2013-05-11 14:50 ` Stefan Monnier
2013-05-11 16:49 ` Richard Stallman
2013-05-11 17:37 ` Stefan Monnier
2013-05-11 21:44 ` Richard Stallman
2013-05-13 15:15 ` Stefan Monnier
2013-05-13 23:47 ` Richard Stallman
2013-05-14 1:56 ` Stefan Monnier
2013-05-14 6:29 ` Eli Zaretskii
2013-05-14 12:48 ` Stefan Monnier
2013-05-15 0:05 ` Richard Stallman
2013-05-11 16:49 ` Richard Stallman
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=E1Ubc7j-0007IF-Cy@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
--cc=yandros@MIT.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).