| blob | b97b583c80eecc90524c9fe49df5ecfb6ec216b4 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
274 /* Workarounds for IE6's broken and incomplete CSS2. */
280 }
286 }
292 }
296 }
301 }
303 /* IE6 sets dynamically generated links as visited. */
305 </style>
307 </head>
308 <body>
311 </div>
315 people describing how they use git in their workflow.</p></div>
317 <li>
318 <p>
320 </p>
321 </li>
322 </ul></div>
324 neighborhood maintainer is struck down by a wayward bus. Out of the
325 hordes of suckers (loyal developers), you have been tricked (chosen) to
328 <li>
329 <p>
330 <a href="howto/rebase-from-internal-branch.txt">rebase-from-internal-branch</a> by Junio C Hamano <gitster@pobox.com>
331 </p>
332 </li>
333 </ul></div>
335 public "pu" branch using the core GIT tools when he updates
337 is how this applies to individual developers who sends patches
338 upstream.</p></div>
340 <li>
341 <p>
342 <a href="howto/rebuild-from-update-hook.txt">rebuild-from-update-hook</a> by Junio C Hamano <gitster@pobox.com>
343 </p>
344 </li>
345 </ul></div>
347 uses the post-update hook to automate git documentation page
348 shown at http://www.kernel.org/pub/software/scm/git/docs/.</p></div>
350 <li>
351 <p>
352 <a href="howto/recover-corrupted-blob-object.txt">recover-corrupted-blob-object</a> by Linus Torvalds <torvalds@linux-foundation.org>
353 </p>
354 </li>
355 </ul></div>
357 a corrupted repository.</p></div>
359 <li>
360 <p>
361 <a href="howto/revert-a-faulty-merge.txt">revert-a-faulty-merge</a> by Linus Torvalds <torvalds@linux-foundation.org>, Junio C Hamano <gitster@pobox.com>
362 </p>
363 </li>
364 </ul></div>
366 is later found to be faulty. Linus and Junio give guidance on
367 recovering from such a premature merge and continuing development
368 after the offending branch is fixed.</p></div>
370 <li>
371 <p>
372 <a href="howto/revert-branch-rebase.html">revert-branch-rebase</a> by Junio C Hamano <gitster@pobox.com>
373 </p>
374 </li>
375 </ul></div>
378 and easier sanity checking.</p></div>
380 <li>
381 <p>
382 <a href="howto/separating-topic-branches.txt">separating-topic-branches</a> by Junio C Hamano <gitster@pobox.com>
383 </p>
384 </li>
385 </ul></div>
388 <li>
389 <p>
390 <a href="howto/setup-git-server-over-http.txt">setup-git-server-over-http</a> by Rutger Nijlunsing <rutger@nospam.com>
391 </p>
392 </li>
393 <li>
394 <p>
395 <a href="howto/update-hook-example.txt">update-hook-example</a> by Junio C Hamano <gitster@pobox.com> and Carl Baldwin <cnb@fc.hp.com>
396 </p>
397 </li>
398 </ul></div>
400 implement repository maintenance policies, such as who can push
401 into which branch and who can make a tag.</p></div>
403 <li>
404 <p>
406 </p>
407 </li>
408 <li>
409 <p>
410 <a href="howto/using-merge-subtree.html">using-merge-subtree</a> by Sean <seanlkml@sympatico.ca>
411 </p>
412 </li>
413 </ul></div>
415 strategy.</p></div>
416 </div>
417 </div>
421 </div>
422 </div>
423 </body>
424 </html>