restaurantport.blogg.se

1. #FREECIV ANDROID GUIDE HOW TO#
2. #FREECIV ANDROID GUIDE PATCH#
3. #FREECIV ANDROID GUIDE SOFTWARE#
4. #FREECIV ANDROID GUIDE CODE#

It is also possible to create patches using Git see section V.

#FREECIV ANDROID GUIDE HOW TO#

This section describes how to create patches using the program called "diff". Once you've finished with a work branch (or two), you can delete them. # See commit hash your changes are relative to now # cherry-pick further commits until you have one that you want to change. # check commit hashes of commits from old branch You have to use this method if you are changing commits other than the last, or if you want to rebase your patches (against newer head commit of the github branch) Second option is the create a new branch and cherry-pick commits there and do changes there. If you need to adjust just the latest commit (maybe the only one), you can do 'commit -amend' for it after adding your changes. If you later need to revisit the commits you've made, for example after they have been reviewed, there's two ways. If you want, you can now switch back to the branch you can sync from github patch, with filenames consisting of the number telling the order of patches and first line of the commit message. Now you should have patches for all your commits in.

#FREECIV ANDROID GUIDE PATCH#

Use 'git format-patch' to write the patch files. Once you want patch files created from all your commits, use 'git log' to find out commit hash of the commit just before your first commit, i.e., the commit your work is relative to. Optionally develop more commits the same way. 'git status' might help you see what are the files you want to add. To make a commit add files you've changed by 'git add' and once they are all there, do 'git commit'. Make sure you're in the head by pulling latest changes in.Ĭreate local branch, branched from your current commit, i.e, from the head you just got in to, to make your development onĭo your changes for one patch, and create a commit.

To develop such a patch, start from the head of the git branch you want to develop your change to. In most cases contributions to freeciv should be sent as a patch file to ticket tracker.

as a freeciv release tarball, see next chapter about creating a patch without git's internal tools.

#FREECIV ANDROID GUIDE CODE#

If you don't have git checkout, but have the source code e.g. This method can be used if you are working with a source code checkout in git.

#FREECIV ANDROID GUIDE SOFTWARE#

The software tools now in use can automatically handle a. See Freeciv source code repository for details.Īs of 2012 July 03, project developers now prefer patches to be named *.patch rather than *.diff. The Freeciv source code is maintained with Git. You may want to consult the mailing list archives to see if the answers to your questions are buried there. There are also other documents of interest in the doc/ directory. If you want to help out with the Freeciv code, then you should read Freeciv hacker's guide and the Style Guide. Pieces of Freeciv source code, however, such as bugfixes and new features, must be entered into the OSDN ticket tracking system - see how. Do not post large or binary contributions to our mailing lists. Please note that if you have files to contribute, create a new patch report on Freeciv's ticket tracker and attach them there. So you want to become a Freeciv contributor! Welcome on board.