Re: [GSoC] current working status
От | Charles Cui |
---|---|
Тема | Re: [GSoC] current working status |
Дата | |
Msg-id | CA+SXE9skOOg-5hA8K0xCSJ5mgdh6Bq9EWvrqE7GNokmzcfcn8w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GSoC] current working status (Charles Cui <charles.cui1984@gmail.com>) |
Ответы |
Re: [GSoC] current working status
|
Список | pgsql-hackers |
Hi mentors,
The repo currently can be build on my mac. You can check it out.
Also I am working on the CI config to monitor each commit.
Thanks
2018-06-14 8:29 GMT-07:00 Charles Cui <charles.cui1984@gmail.com>:
good idea, will keep a feature branch, and set up ci.On Thu, Jun 14, 2018, 8:03 AM Aleksander Alekseeev <a.alekseev@postgrespro.ru> wrote:Hello Charles,
> I saw the list of errors you posted. That's because I have some new
> function implemented and pushed without testing(in order forget my
> change in local machine).
> So you are saying it is best to keep each commit workable. Right?
Ideally, yes. You can always create a separate branch to experiment with
new code and merge it to master branch when it becomes stable. This is
not a strict GSoC requirement or something like this, but a good
practice. If something goes wrong you can just delete an experimental
branch and go back to working master branch.
--
Best regards,
Aleksander Alekseev
В списке pgsql-hackers по дате отправления: