From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: arch taglines in Tramp files -- how to keep them?
Date: Sun, 30 Nov 2003 18:19:38 +0000 [thread overview]
Message-ID: <87ptf9vhvp.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: 87isl1x3ys.fsf@emptyhost.emptydomain.de
Kai Grossjohann <kai@emptydomain.de> writes:
> Miles Bader <miles@gnu.org> writes:
>
>> Just copy the taglines from the emacs CVS files into the official
>> files before copying the whole files in the opposite direction.
>
> Okay, that's what I will do. Thanks.
Tramp 2.0.38 is now committed to Emacs CVS. I hope I haven't b0rked
it, being a bit rusty in this. (I b0rked the commit message for the
lisp subdir already -- it contains only a subset of the ChangeLog
entries. Gnah.)
Kai
prev parent reply other threads:[~2003-11-30 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 17:08 arch taglines in Tramp files -- how to keep them? Kai Grossjohann
2003-11-29 22:53 ` Miles Bader
2003-11-30 15:37 ` Kai Grossjohann
2003-11-30 18:19 ` Kai Grossjohann [this message]
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=87ptf9vhvp.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).