From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master abf0823 2/2: New test tramp-test30-make-auto-save-file-name
Date: Wed, 27 May 2015 18:59:59 +0200 [thread overview]
Message-ID: <87wpzu3qi8.fsf@gmx.de> (raw)
In-Reply-To: <af4mmyc8kn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 27 May 2015 12:02:32 -0400")
Glenn Morris <rgm@gnu.org> writes:
>> * tramp-tests.el (tramp-test30-make-auto-save-file-name): New test.
> [...]
>> * tramp.el (tramp-auto-save-directory): Add :tags.
>
> Please try to write the full filename relative to top-level.
> test/automated/tramp-tests.el etc.
You are right, but I really hate it that we have no ChangeLog
anymore. It was simple to extract the commit message from the ChangeLog
by "C-c C-a". Now we have to do it by hand, and I tend to fail this exam.
I still don't understand why we have given up ChangeLogs. And yes, I
have read all discussions about. No obvious advantage, from my point of view.
(And no, I don't want to start another endless discussion thread)
Best tregards, Michael.
next prev parent reply other threads:[~2015-05-27 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150527134830.719.88862@vcs.savannah.gnu.org>
[not found] ` <E1Yxbh9-0000Cc-Lr@vcs.savannah.gnu.org>
2015-05-27 15:41 ` [Emacs-diffs] master 3953c4b 1/2: Improve tramp-handle-make-auto-save-file-name Dmitry Gutov
2015-05-27 15:50 ` Eli Zaretskii
2015-05-27 16:53 ` Michael Albinus
[not found] ` <E1YxbhA-0000Cl-3b@vcs.savannah.gnu.org>
2015-05-27 16:02 ` master abf0823 2/2: New test tramp-test30-make-auto-save-file-name Glenn Morris
2015-05-27 16:59 ` Michael Albinus [this message]
2015-05-27 17:08 ` Eli Zaretskii
2015-05-27 17:39 ` Michael Albinus
2015-05-27 18:04 ` Yuri Khan
2015-05-27 18:10 ` Eli Zaretskii
2015-05-27 18:10 ` Eli Zaretskii
2015-05-27 19:48 ` Stefan Monnier
2015-05-29 15:57 ` Stephen Leake
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=87wpzu3qi8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/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).