| blob | b42ad330b0757521b80a7d0c671f40ef44f801f8 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-commit-tree(1) Manual Page
407 </h1>
410 <p>git-commit-tree -
411 Create a new commit object
412 </p>
413 </div>
414 </div>
417 <div class="paragraph"><p><em>git commit-tree</em> <tree> [(-p <parent commit>)…] < changelog</p></div>
418 </div>
424 emits the new commit object id on stdout.</p></div>
426 parent, it is an ordinary commit. Having more than one parent makes
427 the commit a merge between several lines of history. Initial (root)
428 commits have no parents.</p></div>
430 directory, a commit represents that state in "time", and explains how
431 to get there.</p></div>
433 doesn’t care where you save the note about that state, in practice we
434 tend to just write the result to the file that is pointed at by
436 state was.</p></div>
437 </div>
443 </dt>
444 <dd>
445 <p>
446 An existing tree object
447 </p>
448 </dd>
451 </dt>
452 <dd>
453 <p>
455 </p>
456 </dd>
457 </dl></div>
458 </div>
463 <li>
464 <p>
465 all parent object ids
466 </p>
467 </li>
468 <li>
469 <p>
470 author name, email and date
471 </p>
472 </li>
473 <li>
474 <p>
475 committer name and email and the commit time.
476 </p>
477 </li>
478 </ul></div>
480 committer information is taken from the following environment variables,
481 if set:</p></div>
484 <pre><tt>GIT_AUTHOR_NAME
485 GIT_AUTHOR_EMAIL
486 GIT_AUTHOR_DATE
487 GIT_COMMITTER_NAME
488 GIT_COMMITTER_EMAIL
489 GIT_COMMITTER_DATE
490 EMAIL</tt></pre>
491 </div></div>
493 <div class="paragraph"><p>In case (some of) these environment variables are not set, the information
494 is taken from the configuration items user.name and user.email, or, if not
495 present, system user name and fully qualified hostname.</p></div>
498 for one to be entered and terminated with ^D.</p></div>
499 </div>
503 support the following date formats:</p></div>
506 Git internal format
507 </dt>
508 <dd>
509 <p>
514 </p>
515 </dd>
517 RFC 2822
518 </dt>
519 <dd>
520 <p>
521 The standard email format as described by RFC 2822, for example
523 </p>
524 </dd>
526 ISO 8601
527 </dt>
528 <dd>
529 <p>
530 Time and date specified by the ISO 8601 standard, for example
533 </p>
535 <table><tr>
538 </td>
541 </tr></table>
542 </div>
543 </dd>
544 </dl></div>
545 </div>
550 You don’t exist. Go away!
551 </dt>
552 <dd>
553 <p>
555 </p>
556 </dd>
558 Your parents must have hated you!
559 </dt>
560 <dd>
561 <p>
562 The passwd(5) gecos field is longer than a giant static buffer.
563 </p>
564 </dd>
566 Your sysadmin must hate you!
567 </dt>
568 <dd>
569 <p>
570 The passwd(5) name field is longer than a giant static buffer.
571 </p>
572 </dd>
573 </dl></div>
574 </div>
579 <li>
580 <p>
581 The pathnames recorded in the index and in the tree objects
582 are treated as uninterpreted sequences of non-NUL bytes.
583 What readdir(2) returns are what are recorded and compared
584 with the data git keeps track of, which in turn are expected
586 thing as pathname encoding translation.
587 </p>
588 </li>
589 <li>
590 <p>
591 The contents of the blob objects are uninterpreted sequences
592 of bytes. There is no encoding translation at the core
593 level.
594 </p>
595 </li>
596 <li>
597 <p>
598 The commit log messages are uninterpreted sequences of non-NUL
599 bytes.
600 </p>
601 </li>
602 </ul></div>
604 in UTF-8, both the core and git Porcelain are designed not to
605 force UTF-8 on projects. If all participants of a particular
606 project find it more convenient to use legacy encodings, git
607 does not forbid it. However, there are a few things to keep in
608 mind.</p></div>
610 <li>
611 <p>
613 a warning if the commit log message given to it does not look
614 like a valid UTF-8 string, unless you explicitly say your
615 project uses a legacy encoding. The way to say this is to
617 </p>
620 <pre><tt>[i18n]
622 </div></div>
625 help other people who look at them later. Lack of this header
627 </li>
628 <li>
629 <p>
632 log message into UTF-8 unless otherwise specified. You can
633 specify the desired output encoding with
635 </p>
638 <pre><tt>[i18n]
640 </div></div>
643 </li>
644 </ol></div>
646 message when a commit is made to force UTF-8 at the commit
647 object level, because re-coding to UTF-8 is not necessarily a
648 reversible operation.</p></div>
649 </div>
653 </div>
657 </div>
661 </div>
662 </div>
663 </body>
664 </html>