gryf/pentadactyl-pm
1
0
Fork 0
mirror of https://github.com/gryf/pentadactyl-pm.git synced 2025-12-21 15:07:59 +01:00
Code Issues Projects Releases Wiki Activity

Added TODO: document remote git branches in HACKING

Browse Source
This commit is contained in:
Ted Pavlic
2009-01-06 19:05:48 -05:00
parent cefc994115
commit 7485dbba4d
2 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
HACKING
View File

@@ -117,3 +117,10 @@ Additionally, maybe there should be some benchmark information here --
something to let a developer know what's "too" slow...? Or general something to let a developer know what's "too" slow...? Or general
guidelines about optimization? guidelines about optimization?
== Source Code Management ==
TODO: Document the existence of remote branches and discuss when and how
to push to them. At least provide an index so that devs know where
to look if an old branch needs to be maintained or a feature needs
to be added to a new branch. Keep in mind that git is not the most
intuitive SCM.

1
vimperator/TODO
View File

@@ -97,6 +97,7 @@ FEATURES:
3 Splitting Windows with [:sp :vsp ctrl-w,s ctrl-w,v] and closing with [ctrl-w,q], moving with [ctrl-w,w or tab] 3 Splitting Windows with [:sp :vsp ctrl-w,s ctrl-w,v] and closing with [ctrl-w,q], moving with [ctrl-w,w or tab]
have a look into the split browser extension have a look into the split browser extension
1 Add information to liberator/HACKING file about testing and optimization 1 Add information to liberator/HACKING file about testing and optimization
1 Document remote branches in liberator/HACKING
1 Reformat liberator/HACKING so that git diff can find sections and report changes @ somewhere 1 Reformat liberator/HACKING so that git diff can find sections and report changes @ somewhere
- many other ideas are listed in the wiki - many other ideas are listed in the wiki