From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Confused about emacs-23 revno: 100005
Date: Sat, 28 Aug 2010 23:24:33 +0200 [thread overview]
Message-ID: <87hbiewhv2.fsf@gmx.de> (raw)
In-Reply-To: <83hbield4o.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Aug 2010 23:02:15 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Glenn Morris <rgm@gnu.org>
>> Date: Sat, 28 Aug 2010 15:49:51 -0400
>> Cc: michael.albinus@gmx.de
>>
>> Secondly, did this change go to the right branch? A 7000 line diff
>> seems large for the emacs-23 branch. Eg lisp/ChangeLog contains
>> several entries related to selinux; but the selinux primitives
>> (file-selinux-context etc) are only in the trunk, so I don't see why
>> this change ended up in emacs-23.
>
> Maybe Michael meant to commit to the trunk, or committed from a wrong
> branch?
No, I meant committing to the Emacs 23 branch.
This is a sync with Tramp 2.1.19 (as indicated in the Changelog). Don't
know, why there is no email in emacs-diff.
It is huge, I know (changes of the last 5 months in Tramp). But I do
plan to start with Tramp 2.2, which includes a rearrangement of the
files, in order to solve the heavy load dependencies. This will go into
the trunk. That's why, Tramp 2.1 will be kept in the Emacs 23 branch
only, and I have done the sync.
Carrying new features of the trunk (like selinux) is not necessary for
the branch, of course. But separating new features from just bug fixes
would be error prone. And Tramp 2.1 will live also outside the
repository, also for Emacs 22 and XEmacs. Compatibility shall be
ensured.
Sorry for the inconvenience.
Best regards, Michael.
next prev parent reply other threads:[~2010-08-28 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 19:49 Confused about emacs-23 revno: 100005 Glenn Morris
2010-08-28 20:02 ` Eli Zaretskii
2010-08-28 21:24 ` Michael Albinus [this message]
2010-08-29 1:46 ` Glenn Morris
2010-08-29 3:12 ` Eli Zaretskii
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=87hbiewhv2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).