-
-
Notifications
You must be signed in to change notification settings - Fork 712
Merging changes after introduction of formatting guidelines
Manuel Benz edited this page Apr 20, 2018
·
13 revisions
If you forked and modified Soot before the introduction of our coding-style guidelines, you might want to take this in to account before merging:
Git should be able to automatically merge all formatting changes to files that weren't touched in your version of Soot's codebase. Also, files with small changes should be easy to merge. However, if you made huge changes to some files, it might make more sense to throw away the remote files, keep your own versions and apply the auto formatting to your files afterward.
- Pull the commit previous to our formatting commit:
git pull 5c8bfba2594942e89be978167febf533177879bd
- Merge your code with the remote code using a merge tool
- Pull our formatting changes
git pull ae1cf8c4126771873414a127b89e59d0ba4c0d57
and manually merge small changes but throw away remote files with a large number of changes (keeping your own). - Apply formatting as stated in our formatting tutorials (Eclipse, IntelliJ Idea)
- Validate the state of your revision with
mvn validate
and fix potential styling issues - Pull and merge changes after the formatting commit
git pull
Also check out Soot's webpage.
NOTE: If you find any bugs in those tutorials (or other parts of Soot) please help us out by reporting them in our issue tracker.
- Home
- Getting Help
- Tutorials
- Reference Material
- General Notions
- Getting Started
- A Few Uses of Soot
- Using Soot as a Command-Line Tool
- Using the Soot Eclipse Plugin
- Using Soot as a Compiler Framework
- Building Soot
- Coding Conventions
- Contributing to Soot
- Updating the Soot Web Page
- Reporting Bugs
- Preparing a New Soot Release