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

From Aleksander Alekseeev
Subject Re: [GSoC] current working status
Date
Msg-id 20180614180353.154cce55@e733.localdomain
Whole thread Raw
In response to Re: [GSoC] current working status  (Charles Cui <charles.cui1984@gmail.com>)
Responses Re: [GSoC] current working status
List pgsql-hackers
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: Tom Lane
Date:
Subject: Re: ntile() throws ERROR when hashagg is false
Next
From: Charles Cui
Date:
Subject: Re: [GSoC] current working status