Am 2019-10-11 um 15:20 schrieb Mark Thomas:
On 11/10/2019 14:10, Rémy Maucherat wrote:
On Fri, Oct 11, 2019 at 1:51 PM Michael Osipov <[email protected]
<mailto:[email protected]>> wrote:
Am 2019-10-11 um 11:32 schrieb Rémy Maucherat:
> On Fri, Oct 11, 2019 at 10:43 AM Mark Thomas <[email protected]
<mailto:[email protected]>> wrote:
>
>> On 11/10/2019 09:30, [email protected]
<mailto:[email protected]> wrote:
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> michaelo pushed a change to branch BZ-63835/8.5.x
>>
>> New features should be implemented against master and then
back-ported
>> (assuming the community accepts them).
>>
>
> I also (still) prefer either PRs (it allows comments) or in master.
This is a first draft, nothing PR worthy. As soon as I see the code
working, I will create the PR by then and when approved in general I
will add tests and re-request review. So please be patient.
For this use I'd recommend using your own forked repository then. Using
a branch for that doesn't work for me, it sends way too many emails that
are not actually useful to dev to the dev mailing list. I tried for a
while, it didn't work, sorry :(
I use upstream so much I should probably reconfigure the names of the
remotes in my checkout:
origin -> fork
upstream -> origin
This doesn't feel right. Origin always denotes the repo you cloned from,
your fork. So keeping origin and upstream seems fine. I call upstream
simply 'apache' in my forked ones and point to gitbox.apache.org.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
