PHP Notice Fixes

OpenEMR Development
1

apmuthu wrote on Sunday, April 14, 2013:

@BM: Also reset the older pull requests from my GitHub fork.

2

apmuthu wrote on Sunday, April 14, 2013:

3

apmuthu wrote on Sunday, April 14, 2013:

4

yehster wrote on Monday, April 15, 2013:

Some git “best practices” advice. Try to avoid messing with your “master” branch directly, and instead only update it from an official mirror by pull.
When you have changes you want to share, create a new branch, do a checkout on that branch, and then make changes.
It’s easier for others to review and test your changes that way, and you won’t have to do things like your “synced with upstream” commit.

5

apmuthu wrote on Wednesday, April 24, 2013:

Thankyou Kevin. As I had used GitHub for resurrecting old unmaintained projects (myseat) and unsupported project versions (joomla v1.5) I did not need to have any branches there, but now on a live maintained project like OpenEMR your advice is best to follow.

Old habits die hard / old ****** learning new tricks slowly…

6

apmuthu wrote on Sunday, April 28, 2013:

Thanks Brady, taken care of now.
Also now including comments removed in:

7

bradymiller wrote on Sunday, April 28, 2013:

Hi,
Just pushed that commit to sourceforge.
thanks,
-brady
OpenEMR

8

apmuthu wrote on Sunday, April 28, 2013:

Comments race condition. Commit not yet included:

9

bradymiller wrote on Sunday, April 28, 2013:

Hi,
I pushed it to sourceforge. The sourceforge code gets mirrored to the github repo every 30 minutes(9:00,9:30,…), so it will show up there in about 13 minutes :slight_smile:
-brady
OpenEMR