On Thu, Oct 11, 2018, 9:46 PM Adrian Bradd wrote:
>
> Sorry if this is obvious, but what is the next branch
>
Simply put, the next branch is even more bleeding edge than the master.
Bleeding-edgeness: next > master > maint
- maint :: gets published to Org Elpa, etc. Right now the version there
Hi all,
To prevent further complications with this branch, I suggest to
treat is
like master and master like maint. I.e., every commit done in
master is
duplicated into next so that final merge is easier.
Sorry if this is obvious, but what is the next branch?
This is the first I have hear
Am 03.10.18 um 13:45 schrieb Marco Wahl:
> My git fu was not strong enough and so the "next" branch is a bit messy
> right now. (I tried to activate a local clean version of the "next"
> branch.)
>
> I thought I could easily rollback the mess I created by going back to
> the git node 3c8fd4fa7 wh
>> My git fu was not strong enough and so the "next" branch is a bit messy
>> right now. (I tried to activate a local clean version of the "next"
>> branch.)
>> [...]
>> Can someone help to clean up the "next" branch, please?
>
> I think I cleaned it.
Thank you so much!
> To prevent further co
Hello,
Marco Wahl writes:
> Hello fellow Orgers,
>
> This is more an internal issue about the repo and in particular the
> "next" branch.
>
> My git fu was not strong enough and so the "next" branch is a bit messy
> right now. (I tried to activate a local clean version of the "next"
> branch.)
Hello fellow Orgers,
This is more an internal issue about the repo and in particular the
"next" branch.
My git fu was not strong enough and so the "next" branch is a bit messy
right now. (I tried to activate a local clean version of the "next"
branch.)
I thought I could easily rollback the mess
