"J.D. Smith" <[email protected]> writes:

Hi,

>> Fixed now. Pushed to the repositories.
>
> Thanks very much.  BTW, I noticed that neither of these fixes have yet
> propagated to ELPA or ELPA-devel.  Do you usually update those after
> testing on main master for a time?

Well, Tramp lives in its own git repo on Savannah. Since there are some
subtle differences to the version which is released on GNU ELPA, there
is a branch tramp-elpa. This is the reference the ELPA sync scripts get
upstream updates.

Usually once a month I run a script which synchronizes the master and
tramp-elpa branches, including changing the release number for Tramp on
GNU ELPA. Therefore, this reaches the ELPA git repo only with this
frequency.

For your convenience, I've applied the script (w/o changing the release
number). You should see this on ELPA-devel soon.

Best regards, Michael.

Reply via email to