[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A problem with old bugs
From: |
Phillip Lord |
Subject: |
Re: A problem with old bugs |
Date: |
Tue, 07 Mar 2017 12:24:31 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Marcin Borkowski <address@hidden> writes:
> On 2017-03-06, at 14:19, Phillip Lord <address@hidden> wrote:
>
>> Marcin Borkowski <address@hidden> writes:
>>>> If not (no write privs), why not? What are you waiting for?
>>>
>>> Nobody gave them to me.
>>>
>>> What should be the workflow once I have them? I assume that I branch
>>> off fresh master, push my branch and write here - correct?
>>
>>
>> Emacs doesn't have a well developed branch merge workflow. In general,
>> people push things straight onto master. If you are unsure whether your
>> patch is good, then asking on emacs-devel, then no one complaining for a
>> while is probably a good sign.
>
> That's interesting. I'd be a bit afraid of pushing to master, if only
> because I have a habit of compiling Emacs from master from time to
> time...
In practice, master is the only way to get people to test things for
you.
You can always push to a branch and ask for feedback. It's less usual,
but you'll often get something.
Phil
Re: A problem with old bugs, Eli Zaretskii, 2017/03/01