[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tramp as ELPA package
From: |
Steinar Bang |
Subject: |
Re: Tramp as ELPA package |
Date: |
Tue, 16 Apr 2019 09:53:01 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (windows-nt) |
>>>>> Michael Albinus <address@hidden>:
> Dmitry Gutov <address@hidden> writes:
> Hi Dmitry,
>> Why don't you create a branch in the Tramp repository which will fit
>> those requirements, and regularly sync it with master, as well as push
>> it to ELPA?
> This branch would have a different file system layout. sync is not trivial.
Well, actually, if you ensure that git history is tracked (by ensuring
that the first commit for a file in the new location is an exact copy
of the file in its previous location), and if the changes you do have to
make because of the new layout doesn't conflict with the changes you're
merging from master, then sync should be as simple as:
git checkout elpa-layout
git merge master
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/04
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/04
- Re: Tramp as ELPA package, Stephen Leake, 2019/04/05
- Re: Tramp as ELPA package, Stephen Leake, 2019/04/05
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/05
- Re: Tramp as ELPA package, Stephen Leake, 2019/04/06
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/07
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/06
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/08
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/08
- Re: Tramp as ELPA package, Michael Albinus, 2019/04/08
- Re: Tramp as ELPA package, Stefan Monnier, 2019/04/08