Skip to content

G
gitflow
Commit 0c927770 authored by Vincent Driessen's avatar Vincent Driessen
Browse files
Options

Fix more Markdown syntax.

parent f74a3a77
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
README.mdown
View file @ 0c927770
...@@ -61,7 +61,7 @@ starting place for installing git. ...@@ -61,7 +61,7 @@ starting place for installing git.
FAQ FAQ
--- ---
* **Can I still do manual branches and merges when I use git-flow?** * **Can I still do manual branches and merges when I use git-flow?**
Of course you can. ``git-flow`` does not forbid you to keep using vanilla Git Of course you can. `git-flow` does not forbid you to keep using vanilla Git
commands! commands!
So if you want to merge `master` into `develop` for whatever reason you want So if you want to merge `master` into `develop` for whatever reason you want
...@@ -71,7 +71,7 @@ FAQ ...@@ -71,7 +71,7 @@ FAQ
finishing those branches later on. finishing those branches later on.
* **I'm getting errors when I use flags with git-flow!** * **I'm getting errors when I use flags with git-flow!**
``git-flow`` uses the [shFlags](http://code.google.com/p/shflags/) library to `git-flow` uses the [shFlags](http://code.google.com/p/shflags/) library to
provide platform independent flag parsing (using wichever low-level flag provide platform independent flag parsing (using wichever low-level flag
parsing libraries like `getopt` or `getopts` are available). However, parsing libraries like `getopt` or `getopts` are available). However,
`shFlags` does not work too well on a few platforms that haven't been tested `shFlags` does not work too well on a few platforms that haven't been tested
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment