Thanks to visit codestin.com
Credit goes to sourceforge.net

Menu

Tree [d01f85] master development /
 History

HTTPS access


File Date Author Commit
 historical 2017-11-14 tim tim [2df469] moved qt, jm, src, src13, and src14 to the hist...
 inst 2017-11-14 tim tim [91b160] Moved inst files into inst subfolder
 jm 2017-11-14 tim tim [2df469] moved qt, jm, src, src13, and src14 to the hist...
 tutorials 2017-11-14 tim tim [1aff08] renamed jmtutorials to tutorials
 README.md 2017-12-01 tim tim [d01f85] jMusic 1.6.6 - Now Git Enabled
 build.properties 2017-02-18 tim opie tim opie [786a74] Compiles with Java5 (tested with Java 5,6,7 & 8)
 build.xml 2017-02-18 tim opie tim opie [786a74] Compiles with Java5 (tested with Java 5,6,7 & 8)

Read Me

jMusic version 1.6.6 - Now Git Enabled

git clone https://git.code.sf.net/p/jmusic/src jmusic-src

Development is on the development Branch:

# Check out the "public" branch
git checkout development

# Get the latest version from remote
git pull

# create and checkout a new feature branch
git checkout -b feature_you_are_working_on

# do stuff here.. Make commits.. test...
git add .
git commit -m "My feature goes bing"

# Update your repository's origin branches from remote repo
git fetch origin

# Update branch and place your commits on top
git rebase development

# Switch to the development branch
git checkout development

# merge your commits to dev branch
git merge feature_you_are_working_on

# Push the public branch up to repository
git push -u origin development

See these for more details:
(https://randyfay.com/content/rebase-workflow-git)
(https://git-scm.com/docs/git-rebase)*

Tagged Releases are on the master Branch (need privileges to write):

git checkout master

Historical version are on the historical branch:

git checkout historical
(read only)