nixo
/
gri3-wm
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Reworded the documentation slightly and fixed the link to correctly point to Github.

This commit is contained in:
Ingo Bürk 2015-04-01 17:47:38 +02:00
parent 37811b67b0
commit fec96c57bc
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/hacking-howto
View File

@ -959,18 +959,21 @@ http://web.archive.org/web/20121024222556/http://www.spheredev.org/wiki/Git_for_
or, for more documentation, see http://git-scm.com/documentation or, for more documentation, see http://git-scm.com/documentation
Please talk to us before working on new features to see whether they will be Please talk to us before working on new features to see whether they will be
accepted. There are a few things which we don’t want to see in i3, e.g. a accepted. A good way for this is to open an issue and asking for opinions on it.
command which will focus windows in an alt+tab like way. Even for accepted features, this can be a good way to refine an idea upfront. However,
we don't want to see certain features in i3, e.g., switching window focus in an
Alt+Tab like way.
When working on bugfixes, please make sure you mention that you are working on When working on bugfixes, please make sure you mention that you are working on
it in the corresponding bugreport at https://github.com/i3/i3/issues In case it in the corresponding bug report at https://github.com/i3/i3/issues. In case
there is no bugreport yet, please create one. there is no bug report yet, please create one.
After you are done, please submit your work for review at https://github.com/i3/i3 After you are done, please submit your work for review as a pull request at
https://github.com/i3/i3.
Do not send emails to the mailing list or any author directly, and don’t submit Do not send emails to the mailing list or any author directly, and don’t submit
them in the bugtracker, since all reviews should be done in public at them in the bugtracker, since all reviews should be done in public at
http://cr.i3wm.org/. In order to make your review go as fast as possible, you https://github.com/i3/i3. In order to make your review go as fast as possible, you
could have a look at previous reviews and see what the common mistakes are. could have a look at previous reviews and see what the common mistakes are.
=== Which branch to use? === Which branch to use?