Changeset 1481 in tailor
- Timestamp:
- 04/01/08 01:30:42 (5 years ago)
- Hash name:
- 20080331233042-97f81-430d82d385698eddafe7991d7c97e0e463a2a1e1
- File:
-
- 1 edited
-
README.rst (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
README.rst
r1480 r1481 579 579 The prototype may contain ``%(keyword)s`` such as 'author', 'date', 580 580 'revision', 'firstlogline', 'remaininglog' or 'project'. It 581 defaults to ``[%(project)s @ %(revision)s]``; setting it to the 582 empty string means that tailor will simply use the original 583 changelog. 581 defaults to ``[%(project)s @ %(revision)s]`` [#]_. 584 582 585 583 When you set it empty, as in … … 606 604 Off by default, when active tailor reformats every changelog before 607 605 committing on the target system. 606 607 .. [#] Modifying the changelog may have subtle consequences! 608 Under darcs, for example, you may hit issue772_ by producing 609 hash collisions, that happens when two distinct patches carry 610 the same "unique" identifier (the hash is computed using 611 *date*, *author*, *changelog* and other details, but **not** 612 the actual content): the default setting, that adds a 613 differentiating prefix, is safer from that point of view. 614 615 .. _issue772: http://bugs.darcs.net/issue772 608 616 609 617
Note: See TracChangeset
for help on using the changeset viewer.
