Fork Clansuite on GitHub

Internet Relay Chat - Logs for #koch
Collected by k-logbot on chat.freenode.net

IRC Log for Samstag, 11. August 2012

  1. 1: [0:01] -jubii2.dk.quakenet.org- on 3 ca 1(4) ft 20(20) tr
  2. 2: [0:01] * cslogbot (~PircBot@server.jakoch.de) has joined #clansuite
  3. 3: [0:01] * Topic is '"Welcome! http://clansuite.com | http://www.youtube.com/watch?v=JPqFNQCXF9Y | https://travis-ci.org/#!/jakoch/Clansuite "'
  4. 4: [0:01] * Set by Q on Tue Aug 07 19:09:33 CEST 2012
  5. 5: [10:56] * SyNko (~chatzilla@81-174-23-229.v4.ngi.it) has joined #clansuite
  6. 6: [10:57] <SyNko> Hi
  7. 7: [10:57] <SyNko> today i will send some changes to fix linux case sensitive and if I have enough time I will send the translation too
  8. 8: [10:58] <SyNko> sorry, man im in no work days and i'm very slow
  9. 9: [10:58] <SyNko> lazyness sorround me
  10. 10: [10:58] <SyNko> :)
  11. 11: [10:59] <SyNko> How is it going? is it full working now?
  12. 12: [10:59] <SyNko> case sensitive a part
  13. 13: [11:50] * Rikku`on (~Daniel@92.225.230.193) has joined #clansuite
  14. 14: [11:51] <Rikku`on> o/
  15. 15: [12:27] <jakoch> hey
  16. 16: [12:28] <jakoch> SyNko: nice to hear, that you worked a bit on the translation. that's quite cool and a very good signal
  17. 17: [12:30] <jakoch> i'm not very fast at fixing all those PSR-0 related bugs and still the router has some bugs in it
  18. 18: [12:32] <jakoch> these PSR-0 bugs are things like this: https://travis-ci.org/#!/jakoch/Clansuite/L207
  19. 19: [12:32] <jakoch> thats not a functional problem but a case-sensitivity problem, the class could not be found, beause it was all lowercased, etc.
  20. 20: [12:34] <jakoch> the other problem is, that all want to see continous integration happening, but no one, but me actually addresses the bugs shown
  21. 21: [13:01] <CIA-1> Clansuite: New Commit: Revision #[769a4eb] by SyNko
  22. 22: [13:01] <CIA-1> Clansuite: File(s): Clansuite/ installation/bootstrap.php
  23. 23: [13:01] <CIA-1> Clansuite: Comment: Update installation/bootstrap.php - http://git.io/1sHdFw
  24. 24: [13:01] <CIA-1> Clansuite: View (delayed): http://trac.clansuite.com/changeset/769a4eb
  25. 25: [13:01] <CIA-1> Clansuite: New Commit: Revision #[cacb80d] by Jens-André Koch
  26. 26: [13:01] <CIA-1> Clansuite: File(s): Clansuite/ installation/bootstrap.php
  27. 27: [13:01] <CIA-1> Clansuite: Comment: Merge pull request #2 from SyNko/master - http://git.io/MB90Ng
  28. 28: [13:01] <CIA-1> Clansuite: View (delayed): http://trac.clansuite.com/changeset/cacb80d
  29. 29: [13:25] <SyNko> git is very slow and i got some issues with it
  30. 30: [13:25] <SyNko> like it not recognize the git.com public key now fixed
  31. 31: [13:27] <SyNko> I think PSR-0 is a good standard but is importatant that your software runs, was better to make a fork one with and one without PSR-0
  32. 32: [13:27] <jakoch> i'm glad you figured out how to do it. thanks for your bugfix, i merged it (see above)
  33. 33: [13:27] <SyNko> so the first will runs and you can show your suite function
  34. 34: [13:27] <SyNko> *functions
  35. 35: [13:27] <jakoch> yeah, the idea is good, but i just don't have the time to maintain and support two forks
  36. 36: [13:28] <SyNko> i never see your project demo running
  37. 37: [13:28] <SyNko> put a demo an the website m8
  38. 38: [13:28] <SyNko> it's just a suggestion
  39. 39: [13:29] <SyNko> you made a 60mb of php website and i cannot see what it does
  40. 40: [13:29] <SyNko> for PSR-0?
  41. 41: [13:29] <jakoch> 60mb?
  42. 42: [13:30] <SyNko> you don't need to support two forks just let die the no psr-0 fork and develope the other but at least you have got something to show
  43. 43: [13:30] <jakoch> yeah, ok.. that is the whole repository with developer tools and such
  44. 44: [13:30] <SyNko> 60 megabytes
  45. 45: [13:31] <jakoch> currently the systems is not running. so i have nothing to show
  46. 46: [13:32] <jakoch> i support the idea of settings up a demo website
  47. 47: [13:33] <jakoch> people ask for that a long time, but i simply can not get it done alone
  48. 48: [13:33] <SyNko> is a bad thing, because if the suite is good I could make more work because i trust it, now i'm in the sea again , i don't know if this site runs and i spend time on your project
  49. 49: [13:33] <SyNko> >currently the systems is not running. so i have nothing to show
  50. 50: [13:34] <jakoch> yeah, would be the same if work on a zend framework 2
  51. 51: [13:34] <jakoch> there is only a skeletopn application nothing more
  52. 52: [13:35] <jakoch> please let me fix the routing this weekend, then you can actually see modules rendering content
  53. 53: [13:35] <jakoch> i will then put up a small hello world demo appliation
  54. 54: [13:35] <jakoch> so that everybody can see it work
  55. 55: [13:36] <SyNko> i need a website for my clan, i'm a php developer , i know how much works it take, i can bet on your project but i need a strict way to get the job done running without psr-0 too, i'm able to work hard
  56. 56: [13:36] <SyNko> ok
  57. 57: [13:36] <SyNko> well
  58. 58: [13:37] <SyNko> i need a clan manager website , with calendar matches, presence function, rooster, past matches list etc, at which point are you developing this big pack of code
  59. 59: [13:37] <SyNko> i dislike framework, i go strict to code qhat i need
  60. 60: [13:37] <SyNko> *what
  61. 61: [13:38] <jakoch> just take a look at the modules folder
  62. 62: [13:38] <SyNko> k
  63. 63: [13:38] <jakoch> if you like to work on some of those functionalities that would be cool
  64. 64: [13:38] <jakoch> if you want a quick start for a clanwebsite i would point you to another project
  65. 65: [13:38] <jakoch> "clansphere"
  66. 66: [13:39] <jakoch> that is a simle script, not psr-0, does the job and is easy
  67. 67: [13:39] <SyNko> my git is broken
  68. 68: [13:40] <SyNko> i deleted the dir with all the files and now on clone don't download nothing and keep loading
  69. 69: [13:40] <jakoch> i will help you, but now i have to go to lunch.. i'm backing 30min or so. maybe ask Rikku`on in the meantime, he can help you, too
  70. 70: [13:40] <SyNko> wait a sec please
  71. 71: [13:41] <SyNko> i don't really need a quick solution because as you know the easy way after some times become a bad trick
  72. 72: [13:41] <SyNko> that's all
  73. 73: [13:42] <SyNko> i hope i could show something to my clan at the end of this summer
  74. 74: [13:42] <SyNko> have a good lunch
  75. 75: [13:58] * Rikku`on (~Daniel@92.225.230.193) Quit (Quit: Leaving.)
  76. 76: [14:06] <jakoch> re
  77. 77: [14:08] <jakoch> if the git folder is seriously broken, i would advise you to delete it and then do a fresh "clone" of your repo
  78. 78: [14:09] <SyNko> is what i've done
  79. 79: [14:09] <SyNko> now gave me the error of ssl again
  80. 80: [14:09] <SyNko> let's try
  81. 81: [14:10] <SyNko> RA layer request failed: PROPFIND request failed on '/product/showroom/list': PROPFIND of '/product/showroom/list': 200 OK (http://www.csphere.eu) at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 1365
  82. 82: [14:10] <SyNko> argh
  83. 83: [14:10] <SyNko> im dumb
  84. 84: [14:10] <SyNko> im pointing to clansphere
  85. 85: [14:12] <jakoch> this is the correct link git@github.com:SyNko/Clansuite.git
  86. 86: [14:12] <SyNko> now is right
  87. 87: [14:12] <SyNko> but keep loading
  88. 88: [14:12] <SyNko> Initialized empty Git repository in c:/Users/SyNko/Desktop/_Clansuite/Clansuite/.git/
  89. 89: [14:12] <SyNko> RA layer request failed: PROPFIND request failed on '/SyNko/Clansuite.git': PROPFIND of '/SyNko/Clansuite.git': 405 Not Allowed (https://github.com) at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 1365
  90. 90: [14:13] <SyNko> i will try your uri
  91. 91: [14:14] <SyNko> Bad URL passed to RA layer: Unrecognized URL scheme for 'git@github.com:SyNko/Clansuite.git' at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 1365
  92. 92: [14:15] <SyNko> i have the tortouse git and svn both installed
  93. 93: [14:15] <SyNko> maybe is some kind of conflict
  94. 94: [14:15] <SyNko> i try to remove the svn
  95. 95: [14:15] <jakoch> no
  96. 96: [14:15] <jakoch> i work with both systems, too
  97. 97: [14:15] <SyNko> ah ok
  98. 98: [14:15] <jakoch> they are not conflicting
  99. 99: [14:16] <SyNko> k
  100. 100: [14:17] <jakoch> how do you call it? "git clone git@github.com:SyNko/Clansuite.git"?
  101. 101: [14:17] <SyNko> i use the gui
  102. 102: [14:17] <jakoch> ah ok
  103. 103: [14:18] <SyNko> i used the cli only for the ssl acceptation
  104. 104: [14:18] <jakoch> so you go TortoiseGit context menu -> "clone" > "git clone" dialog window
  105. 105: [14:19] <jakoch> "Clone Exisiting Repository" URL : git@github.com:SyNko/Clansuite.git Directory: the target dir you want
  106. 106: [14:19] <jakoch> no other checkboxes crossed
  107. 107: [14:19] <SyNko> your uri don't work on the gui
  108. 108: [14:19] <SyNko> i used the last working
  109. 109: [14:20] <SyNko> because i get it working the first time i tryied
  110. 110: [14:20] <SyNko> the first day
  111. 111: [14:20] <jakoch> do you have your ssh key loaded in the background?
  112. 112: [14:20] <SyNko> sure
  113. 113: [14:20] <jakoch> ok
  114. 114: [14:21] <SyNko> but i doesnt ask me for the pass phrase just the first time
  115. 115: [14:21] <SyNko> it says: "Initialized empty Git repository in c:/Users/SyNko/Desktop/_Clansuite_repo/Clansuite/.git/
  116. 116: [14:21] <SyNko> and keep loading
  117. 117: [14:22] <jakoch> hmm, something wrong there
  118. 118: [14:22] <SyNko> i changed the name of the dir too
  119. 119: [14:22] <jakoch> https://help.github.com/articles/which-remote-url-should-i-use
  120. 120: [14:22] <SyNko> Initialized empty Git repository in c:/Users/SyNko/Desktop/_Clansuite_repo/Clansuite/.git/
  121. 121: [14:22] <SyNko> RA layer request failed: PROPFIND request failed on '/SyNko/Clansuite.git': PROPFIND of '/SyNko/Clansuite.git': 405 Not Allowed (https://github.com) at C:\Program Files (x86)\Git/libexec/git-core\git-svn line 1365
  122. 122: [14:23] <jakoch> 405 not allowed
  123. 123: [14:23] <SyNko> yep
  124. 124: [14:23] <SyNko> is html response code
  125. 125: [14:24] <jakoch> why are you using git-svn?
  126. 126: [14:24] <jakoch> git/libexec/git-core\git-svn <---
  127. 127: [14:25] <SyNko> i dunno maybe conflict, i invoked the clone from the context menu
  128. 128: [14:25] <SyNko> like the other day
  129. 129: [14:25] <SyNko> when was working
  130. 130: [14:25] <jakoch> hmmm, strange
  131. 131: [14:25] <SyNko> the svn is useless for me
  132. 132: [14:25] <SyNko> i try to uninstall it
  133. 133: [14:26] <SyNko> reboot required, ill be back
  134. 134: [14:26] <jakoch> allright
  135. 135: [14:27] * SyNko (~chatzilla@81-174-23-229.v4.ngi.it) Quit (Read error: EOF from client)
  136. 136: [14:30] * SyNko (~chatzilla@81-174-23-229.v4.ngi.it) has joined #clansuite
  137. 137: [14:31] <SyNko> back
  138. 138: [14:31] <SyNko> nothing new
  139. 139: [14:31] <SyNko> still the error
  140. 140: [14:31] <jakoch> do you have "Git Bash" in the context menu?
  141. 141: [14:33] <SyNko> yep
  142. 142: [14:35] <jakoch> ok, try the following click "git bash", then cd into an empty dir and do "git clone git@github.com:SyNko/Clansuite.git"
  143. 143: [14:35] <jakoch> let's hope that does not call git-svn again
  144. 144: [14:37] <SyNko> do i need to put the -d flag for develop?
  145. 145: [14:37] <SyNko> jacoch ^^
  146. 146: [14:37] <SyNko> soz jakoch ^^
  147. 147: [14:37] <jakoch> git clone has a --d flag?
  148. 148: [14:37] <SyNko> let me see
  149. 149: [14:38] <jakoch> http://www.kernel.org/pub/software/scm/git/docs/git-clone.html
  150. 150: [14:38] <SyNko> yep
  151. 151: [14:38] <SyNko> --help ;)
  152. 152: [14:38] <SyNko> when i use the gui i put always the develop branch
  153. 153: [14:39] <jakoch> hmm i dont see -d, but -b for branch
  154. 154: [14:40] <SyNko> ah yes yes sure
  155. 155: [14:40] <jakoch> ok, yes you might do that
  156. 156: [14:40] <SyNko> done, is downloading, tnx!
  157. 157: [14:40] <jakoch> really? cool! finally we got it :)
  158. 158: [14:41] <SyNko> yes
  159. 159: [14:41] <jakoch> let's hope we get this done for Clansuite, too
  160. 160: [14:41] <SyNko> which is the command for the push from the cli?
  161. 161: [14:41] <jakoch> "git push"
  162. 162: [14:42] <SyNko> tnx
  163. 163: [14:42] <jakoch> the order of commands is the following, let's think about creating a new file here
  164. 164: [14:42] <jakoch> "git add newfile.txt" (adds the new file to the index)
  165. 165: [14:42] <SyNko> and what about if you make changes on your repo?
  166. 166: [14:43] <SyNko> i still working on old
  167. 167: [14:43] <SyNko> version
  168. 168: [14:44] <jakoch> yes.. so in order to update your version to the lastest changes of my repo, you need to set up a remote branch
  169. 169: [14:44] <jakoch> thats called "remote branch tracking"
  170. 170: [14:44] <SyNko> wow cool
  171. 171: [14:44] <SyNko> could you show me this way?
  172. 172: [14:45] <jakoch> yes, let's try to set it up..
  173. 173: [14:45] <SyNko> would you like a voice communication?
  174. 174: [14:46] <jakoch> it's not that complicated
  175. 175: [14:46] <SyNko> ah ok
  176. 176: [14:47] <jakoch> "git remote add upstream-develop git://github.com/jakoch/Clansuite.git"
  177. 177: [14:48] <jakoch> that will add a new remote tracking named "upstream-develop", which points to the clansuite repo
  178. 178: [14:49] <jakoch> actually a good guide is http://gitref.org/remotes/#remote
  179. 179: [14:50] <SyNko> k
  180. 180: [14:50] <jakoch> the best way to check your remote setup is "git remote -v"
  181. 181: [14:53] <jakoch> after the "git remote add upstream-develop" command, you can do the following: "git fetch upstream-develop"
  182. 182: [14:53] <jakoch> that will fetch the latest changes from the main repo
  183. 183: [14:54] <jakoch> and after that just do a "git merge upstream-develop/develop"
  184. 184: [14:55] <jakoch> that will merge the latest changes from the "upstream-develop" remote tracking branch to your "develop" branch, which makes it being in "sync"
  185. 185: [14:56] <SyNko> do i need to run it in to the root of my local synko 's repo?
  186. 186: [14:56] <SyNko> or is better a new dir?
  187. 187: [14:57] <jakoch> inside the repo / at any directory level
  188. 188: [14:57] <SyNko> k
  189. 189: [14:57] <jakoch> also a little trick: "/Clansuite/.git/config"
  190. 190: [14:58] <jakoch> the file "config" in the ".git" folder contains the remote configuration too
  191. 191: [14:59] <jakoch> so there must be a section for your [branch "develop"]
  192. 192: [14:59] <SyNko> [branch "develop"]
  193. 193: [14:59] <SyNko> remote = origin
  194. 194: [14:59] <SyNko> merge = refs/heads/develop
  195. 195: [15:00] <jakoch> good.. see the remote.. thats the tracking
  196. 196: [15:00] <jakoch> it points to origin
  197. 197: [15:00] <jakoch> then there must be a [remote "origin"] description too
  198. 198: [15:00] <SyNko> [remote "origin"]
  199. 199: [15:00] <SyNko> fetch = +refs/heads/*:refs/remotes/origin/*
  200. 200: [15:00] <SyNko> url = git@github.com:SyNko/Clansuite.git
  201. 201: [15:01] <SyNko> k
  202. 202: [15:01] <jakoch> uhmm. that tracks your repo
  203. 203: [15:02] <SyNko> im changing
  204. 204: [15:02] <jakoch> do you see url= with "jakoch/Clansuite.git" somewhere ?
  205. 205: [15:02] <jakoch> [remote "upstream-develop"]?
  206. 206: [15:02] <SyNko> nope
  207. 207: [15:02] <SyNko> wait a moment
  208. 208: [15:03] <SyNko> i need to launch the commands before XD
  209. 209: [15:03] <jakoch> true
  210. 210: [15:04] <jakoch> in other words: what you do with the commands on the cli, will end up in this config file
  211. 211: [15:04] <SyNko> ah ok yes
  212. 212: [15:04] <SyNko> i know
  213. 213: [15:04] <jakoch> sometimes it's good to know, this file gives a good overview of all the things going on with the repo
  214. 214: [15:04] <SyNko> ok tnx
  215. 215: [15:07] <jakoch> ah found a better way
  216. 216: [15:08] <jakoch> http://stackoverflow.com/questions/520650/how-do-you-make-an-existing-git-branch-track-a-remote-branch
  217. 217: [15:08] <jakoch> "git branch --set-upstream"
  218. 218: [15:10] <SyNko> soz man
  219. 219: [15:11] <SyNko> i done all the command
  220. 220: [15:11] <SyNko> s
  221. 221: [15:11] <SyNko> and is ok
  222. 222: [15:11] <jakoch> allright
  223. 223: [15:11] <SyNko> but in the overview file still : remote = origin :: Is it right?
  224. 224: [15:12] <jakoch> ye
  225. 225: [15:12] <jakoch> yes
  226. 226: [15:12] <SyNko> then
  227. 227: [15:12] <SyNko> [remote "upstream-develop"]
  228. 228: [15:12] <SyNko> url = git://github.com/jakoch/Clansuite.git
  229. 229: [15:12] <SyNko> fetch = +refs/heads/*:refs/remotes/upstream-develop/*
  230. 230: [15:12] <SyNko> [remote "origin"]
  231. 231: [15:12] <SyNko> fetch = +refs/heads/*:refs/remotes/origin/*
  232. 232: [15:12] <SyNko> url = git@github.com:SyNko/Clansuite.git
  233. 233: [15:13] <SyNko> the order may vary
  234. 234: [15:13] <SyNko> *the real order may vary
  235. 235: [15:13] <jakoch> ok
  236. 236: [15:13] <SyNko> so if now i change a file how do you see that?
  237. 237: [15:14] <SyNko> or do i need to wait untill you make the patch and then resync?
  238. 238: [15:15] <SyNko> in the sense i push a change from the web, you check, if it's right I resync and restart to work
  239. 239: [15:15] <SyNko> but in this way there is delay
  240. 240: [15:16] <SyNko> is better i make multiple changes and then push and then if it right i resync
  241. 241: [15:16] <jakoch> yes, thats the distributed nature of git
  242. 242: [15:16] <SyNko> *if it's right
  243. 243: [15:17] <jakoch> the setup with the remote branch is done, to keep your develop branch updates with changes from the main repository
  244. 244: [15:17] <jakoch> you pull them in
  245. 245: [15:17] <jakoch> if you have done changes in the meantime (before pulling in) then a merge will happen
  246. 246: [15:19] <jakoch> if you commit and push, then you commit to your repository "github/SyNko/Clansuite"
  247. 247: [15:19] <jakoch> you have done that already, so i will then "pull your changes" and apply them to the main repository by merging
  248. 248: [15:21] <jakoch> then if you do "pull" the remote branch again, it will update, but for your branch there will be not changes to merge, because you have it already
  249. 249: [15:23] <SyNko> k
  250. 250: [15:23] <jakoch> and you are right.. the delay is between you "pushing changes" and "me, accpeting them" for main
  251. 251: [15:23] * Rikku`on (~Daniel@92.225.230.193) has joined #clansuite
  252. 252: [15:24] <SyNko> but i could make multiple push and work again and push again then you will review late and is not a problem
  253. 253: [15:24] <jakoch> yes, thats ok
  254. 254: [15:24] <SyNko> when you have completed the review session i can make a resync
  255. 255: [15:25] <SyNko> git merge upstream-develop/develop
  256. 256: [15:25] <SyNko> with this
  257. 257: [15:26] <jakoch> yes
  258. 258: [15:26] <SyNko> so i go to a revision IMHO
  259. 259: [15:26] <jakoch> that will update your local develop branch with the latest changes from "jakoch/Clansuite"
  260. 260: [15:26] <SyNko> IMHO is better that you make a review one or two time in a day at max rate
  261. 261: [15:27] <SyNko> so i dont risk to have modified the files after a push and you already reviewed
  262. 262: [15:27] <jakoch> the normal workflow is: you do a change and push, open a pull request
  263. 263: [15:27] <SyNko> in this case i cannot resync without loosing changes
  264. 264: [15:28] <jakoch> i will say in the comments if everything is ok or not. if not okay, i will say what needs to be changed
  265. 265: [15:28] <SyNko> yep sure
  266. 266: [15:28] <jakoch> every following commit will go into the list of commits for this pull request
  267. 267: [15:28] <jakoch> then i accept it and its merged
  268. 268: [15:31] <jakoch> you might also write in the comments, when you open a new pull request, that "more commits will follow - feature not complete, yet"
  269. 269: [15:31] <jakoch> i see that quite a lot on github
  270. 270: [15:31] <SyNko> yes, from the website
  271. 271: [15:31] <jakoch> and then they discuss there, whats good in the commits and not, etc. its cool for code review
  272. 272: [15:33] <SyNko> i keep "git push" for stupid things like CS things, but the more complex i will use the website
  273. 273: [15:33] <SyNko> sorry, is it right the command "git push"?
  274. 274: [15:34] <jakoch> i think so
  275. 275: [15:34] <SyNko> k
  276. 276: [15:35] <jakoch> back to the command order on CLI, its "git add newfile.txt" + "git commit -m "i added a newfile" + "git push"
  277. 277: [15:36] <SyNko> k perfect, that is what i want to know
  278. 278: [15:37] <jakoch> http://www-cs-students.stanford.edu/~blynn/gitmagic/ch02.html
  279. 279: [15:37] <jakoch> there a lot of tricks with git
  280. 280: [15:39] <jakoch> it's really a complex toolkit. i do not understand it fully and will never understand it in depth, but.. it's cool to work with
  281. 281: [15:39] <jakoch> i wanted to point you to "git reset --hard"
  282. 282: [15:39] <jakoch> that rewinds all your changes, so if you have done something strange and want to start over from scratch, thats the way to do it
  283. 283: [15:40] <SyNko> my problem is another
  284. 284: [15:40] <SyNko> i use a free web server
  285. 285: [15:40] <SyNko> i ve home server
  286. 286: [15:41] <SyNko> but is not working , i need to reformat
  287. 287: [15:41] <SyNko> i work directly on the free web server
  288. 288: [15:41] <SyNko> every time i need a change i make a ftp download
  289. 289: [15:42] <SyNko> ah yes, i have the option "overwrite newer" im save
  290. 290: [15:42] <SyNko> but i want to look when it takes
  291. 291: [15:43] <SyNko> is not as working directly to the dirs of the webserver
  292. 292: [15:44] <SyNko> uploading all the files to there takes 15 mins
  293. 293: [15:44] <jakoch> ok, so you develop locally and do the testing on the remote web server
  294. 294: [15:44] <SyNko> or 20
  295. 295: [15:45] <SyNko> yes, i try, if i found that too much expensive in time i will put on my local web server
  296. 296: [15:46] <jakoch> hmm, normally one would start with copying the complete thing to the remote server
  297. 297: [15:46] <jakoch> and then doing incremental updates (just the files changed) from local to remote server
  298. 298: [15:47] <jakoch> for instance an IDE like Netbeans is capbale of doing that
  299. 299: [15:47] <jakoch> ../s/capbale/capable
  300. 300: [15:48] <SyNko> yes im working directly to the ftp server with a file cache, after some mods i need to redownload all from there and push changes
  301. 301: [15:48] <SyNko> so usually i will make multiple file push
  302. 302: [15:49] <SyNko> *files
  303. 303: [15:49] <SyNko> good luck to understand the mod
  304. 304: [15:49] <SyNko> if i make a multiple changes how could you divide the bug discovered?
  305. 305: [15:51] <jakoch> by "bisecting".. which is running through all your commits, applying each one individually and testing if it still runs (or in our case, starts to run)
  306. 306: [15:51] <SyNko> for example i will find a bug that take 3 files to patch, and then another that take 4 files, and then another case sensitive patch, and then i make a push
  307. 307: [15:51] <jakoch> "3 files" (commit) "4 files" (commit) "case fix" (commit)
  308. 308: [15:52] <jakoch> then push
  309. 309: [15:53] <SyNko> git commit -m ?
  310. 310: [15:54] <jakoch> yes, thats "git commit" and -m for "message"
  311. 311: [15:54] <jakoch> git commit -m "fixed bug xy in 3 files"
  312. 312: [15:54] <SyNko> ah cool
  313. 313: [15:56] <jakoch> for syncing local with ftp i would use something like WinSCP or Filezilla with Synchronize enabled
  314. 314: [15:56] <SyNko> sure im using filezilla
  315. 315: [15:56] <SyNko> great germany!
  316. 316: [15:57] <SyNko> is working great
  317. 317: [15:57] <jakoch> yeah, they invest a lot of time in open source stuff here and have lots of fun doing it
  318. 318: [15:58] <jakoch> there is a feature "directory compare" or similar
  319. 319: [15:58] <jakoch> if that is enabled, FZ will check for changes only and upload them
  320. 320: [15:59] <SyNko> in my FZ there is an option to open file from a temp cache directly from the ftp srvr
  321. 321: [15:59] <SyNko> after the changes
  322. 322: [15:59] <SyNko> i will redownload all with the option
  323. 323: [16:00] <SyNko> "over write only if newer"
  324. 324: [16:01] <jakoch> one question.. where do you do all the git stuff on the free web server or locally?
  325. 325: [16:01] <SyNko> locally
  326. 326: [16:01] <jakoch> allright
  327. 327: [16:01] <SyNko> now i will see how mush will take the overwrite thing
  328. 328: [16:01] <SyNko> *much
  329. 329: [16:01] <jakoch> then i would not fetch all the stuff from the webserver all the time
  330. 330: [16:02] <SyNko> is what i've done this week
  331. 331: [16:02] <SyNko> fool
  332. 332: [16:02] <SyNko> i was not thinking
  333. 333: [16:02] <SyNko> holidays
  334. 334: [16:02] <SyNko> just 4 times
  335. 335: [16:05] * jakoch needs a coffee now
  336. 336: [16:06] * SyNko coffe breeze
  337. 337: [16:07] <SyNko> news of the moment: i see many windows \ in conflic with / linux
  338. 338: [16:13] <SyNko> we need to define somewhere define('SEP', "\\"); for windows and define("SEP', "/"); for linux
  339. 339: [16:13] <SyNko> and rewrite all the dirs
  340. 340: [16:14] <SyNko> ah yes there is
  341. 341: [16:14] <SyNko> define('DS', DIRECTORY_SEPARATOR);
  342. 342: [16:15] <SyNko> but doesnt autoload
  343. 343: [16:15] <SyNko> ah cool is a php constant
  344. 344: [16:23] <SyNko> mistake i dont put the keep the same data option
  345. 345: [16:23] <SyNko> i need to redownload all
  346. 346: [16:27] * SyNko ZzZzzZzzzzzz
  347. 347: [16:37] <jakoch> re
  348. 348: [16:38] <jakoch> yes, if you see DIRECTORY_SEPARATOR errors, please add the linux slash to the path directly
  349. 349: [16:38] <jakoch> that will work in windows, too
  350. 350: [16:38] <jakoch> the path will look ugly in windows, but will work..
  351. 351: [16:40] <SyNko> $filename = str_replace('Clansuite\Installation\\', '', $classname);
  352. 352: [16:40] <SyNko> $filename = str_replace('\\',DS,$filename);
  353. 353: [16:43] <jakoch> yes, that would work
  354. 354: [17:01] <SyNko> brb
  355. 355: [17:01] * SyNko (~chatzilla@81-174-23-229.v4.ngi.it) Quit (Quit: ChatZilla 0.9.88.2 [Firefox 14.0.1/20120713134347])
  356. 356: [17:13] * SyNko (~chatzilla@81-174-23-229.v4.ngi.it) has joined #clansuite
  357. 357: [17:54] * Rikku`on (~Daniel@92.225.230.193) Quit (Quit: Leaving.)

Links of Samstag, 11. August 2012

1) http://www-cs-students.stanford.edu/~blynn/gitmagic/ch02.html
2) http://stackoverflow.com/questions/520650/how-do-you-make-an-existing-git-branch-track-a-remote-branch
3) http://gitref.org/remotes/#remote
4) http://www.kernel.org/pub/software/scm/git/docs/git-clone.html
5) https://github.com)
6) https://help.github.com/articles/which-remote-url-should-i-use
7) http://www.csphere.eu)
8) http://trac.clansuite.com/changeset/cacb80d
9) http://git.io/MB90Ng
10) http://trac.clansuite.com/changeset/769a4eb
11) http://git.io/1sHdFw
12) https://travis-ci.org/#!/jakoch/Clansuite/L207
13) http://clansuite.com
14) http://www.youtube.com/watch?v=JPqFNQCXF9Y
15) https://travis-ci.org/#!/jakoch/Clansuite

These logs were automatically created by k-logbot on chat.freenode.net using the Clansuite IRC LogBot. Find the project at Github.