Re: [GSoC] current working status - Mailing list pgsql-hackers

From Charles Cui
Subject Re: [GSoC] current working status
Date
Msg-id CA+SXE9uxNQKRvKyH+g894qE=NKDRPHSm6EhZn0OFtwQwj=6UMA@mail.gmail.com
Whole thread Raw
In response to Re: [GSoC] current working status  (Aleksander Alekseeev <a.alekseev@postgrespro.ru>)
Responses Re: [GSoC] current working status
List pgsql-hackers
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 by date:

Previous
From: Aleksander Alekseeev
Date:
Subject: Re: [GSoC] current working status
Next
From: Peter Geoghegan
Date:
Subject: Re: Locking B-tree leafs immediately in exclusive mode