| blob | dc43e6758f903f14b5d29d6ae2f032d6c5b51324 |
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>
418 <div class="verseblock-content"><em>git commit-tree</em> <tree> [(-p <parent commit>)…] < changelog</div>
420 </div></div>
421 </div>
427 emits the new commit object id on stdout.</p></div>
429 parent, it is an ordinary commit. Having more than one parent makes
430 the commit a merge between several lines of history. Initial (root)
431 commits have no parents.</p></div>
433 directory, a commit represents that state in "time", and explains how
434 to get there.</p></div>
436 doesn’t care where you save the note about that state, in practice we
437 tend to just write the result to the file that is pointed at by
439 state was.</p></div>
440 </div>
446 </dt>
447 <dd>
448 <p>
449 An existing tree object
450 </p>
451 </dd>
454 </dt>
455 <dd>
456 <p>
458 </p>
459 </dd>
460 </dl></div>
461 </div>
466 <li>
467 <p>
468 all parent object ids
469 </p>
470 </li>
471 <li>
472 <p>
473 author name, email and date
474 </p>
475 </li>
476 <li>
477 <p>
478 committer name and email and the commit time.
479 </p>
480 </li>
481 </ul></div>
483 committer information is taken from the following environment variables,
484 if set:</p></div>
487 <pre><tt>GIT_AUTHOR_NAME
488 GIT_AUTHOR_EMAIL
489 GIT_AUTHOR_DATE
490 GIT_COMMITTER_NAME
491 GIT_COMMITTER_EMAIL
492 GIT_COMMITTER_DATE
493 EMAIL</tt></pre>
494 </div></div>
496 <div class="paragraph"><p>In case (some of) these environment variables are not set, the information
497 is taken from the configuration items user.name and user.email, or, if not
498 present, system user name and fully qualified hostname.</p></div>
501 for one to be entered and terminated with ^D.</p></div>
502 </div>
506 support the following date formats:</p></div>
509 Git internal format
510 </dt>
511 <dd>
512 <p>
517 </p>
518 </dd>
520 RFC 2822
521 </dt>
522 <dd>
523 <p>
524 The standard email format as described by RFC 2822, for example
526 </p>
527 </dd>
529 ISO 8601
530 </dt>
531 <dd>
532 <p>
533 Time and date specified by the ISO 8601 standard, for example
536 </p>
538 <table><tr>
541 </td>
544 </tr></table>
545 </div>
546 </dd>
547 </dl></div>
548 </div>
553 You don’t exist. Go away!
554 </dt>
555 <dd>
556 <p>
558 </p>
559 </dd>
561 Your parents must have hated you!
562 </dt>
563 <dd>
564 <p>
565 The passwd(5) gecos field is longer than a giant static buffer.
566 </p>
567 </dd>
569 Your sysadmin must hate you!
570 </dt>
571 <dd>
572 <p>
573 The passwd(5) name field is longer than a giant static buffer.
574 </p>
575 </dd>
576 </dl></div>
577 </div>
582 <li>
583 <p>
584 The pathnames recorded in the index and in the tree objects
585 are treated as uninterpreted sequences of non-NUL bytes.
586 What readdir(2) returns are what are recorded and compared
587 with the data git keeps track of, which in turn are expected
589 thing as pathname encoding translation.
590 </p>
591 </li>
592 <li>
593 <p>
594 The contents of the blob objects are uninterpreted sequences
595 of bytes. There is no encoding translation at the core
596 level.
597 </p>
598 </li>
599 <li>
600 <p>
601 The commit log messages are uninterpreted sequences of non-NUL
602 bytes.
603 </p>
604 </li>
605 </ul></div>
607 in UTF-8, both the core and git Porcelain are designed not to
608 force UTF-8 on projects. If all participants of a particular
609 project find it more convenient to use legacy encodings, git
610 does not forbid it. However, there are a few things to keep in
611 mind.</p></div>
613 <li>
614 <p>
616 a warning if the commit log message given to it does not look
617 like a valid UTF-8 string, unless you explicitly say your
618 project uses a legacy encoding. The way to say this is to
620 </p>
623 <pre><tt>[i18n]
625 </div></div>
628 help other people who look at them later. Lack of this header
630 </li>
631 <li>
632 <p>
635 log message into UTF-8 unless otherwise specified. You can
636 specify the desired output encoding with
638 </p>
641 <pre><tt>[i18n]
643 </div></div>
646 </li>
647 </ol></div>
649 message when a commit is made to force UTF-8 at the commit
650 object level, because re-coding to UTF-8 is not necessarily a
651 reversible operation.</p></div>
652 </div>
656 </div>
660 </div>
664 </div>
665 </div>
666 </body>
667 </html>