Changes between Version 8 and Version 9 of SvnLogFormat


Ignore:
Timestamp:
Oct 31, 2023, 12:58:53 AM (13 months ago)
Author:
jac
Comment:

Fix wording

Legend:

Unmodified
Added
Removed
Modified

  • SvnLogFormat

    v8 v9  
    11== How to write good SVN logs ==
    22
    3 Always write log comment during the commit. The change may appear obvious to you now, it won't to someone else in a few years.
    4 Always write where you got the new files from (eg. "Pin sent me his new SAPs") and why you are making changes ("Miker said he didn't composed it", "Fixed playback with new ASAP").
    5 It's less important to describe what you actually changed - double-clicking a file in TortoiseSVN Log will show changes to AUTHOR, NAME, DATE, etc.
     3Always write log comments during the commit. The change may appear obvious to you now, but it won't to someone else in a few years.
     4Always write where you got the new files from (eg. "Pin sent me his new SAPs") and why you are making changes ("Miker said he didn't compose it", "Fixed playback with new ASAP").
     5It's less important to describe what you changed - double-clicking a file in TortoiseSVN Log will show changes to AUTHOR, NAME, DATE, etc.
    66
    77== Old discussion (to be continued and translated) ==
    … …  
    99'''pfusik:''' I don't think the following makes much sense compared to the above.
    1010
    11 This is a draft description for now so that there is something to discuss. Just loose thoughts - I have not yet tested how it would look in practice.
     11This is a draft description for now so there is something to discuss. Just loose thoughts - I have not yet tested how it would look in practice.
    1212
    1313=== Operations ===
    1414
    15 The user can add, delete and move SAP files to another location.
     15The user can add, delete, and move SAP files to another location.
    1616
    17 The user can Wit can add change and delete fields in SAP files.
     17The user can Wit can add, change, and delete fields in SAP files.
    1818
    1919=== Oznaczenia działań na plikach ===
    … …  
    5151Trac displays SVN logs using its markup. I suggest not to overdo it with it, but there are useful things:
    5252
    53 "Fixed file broken in changeset:256".
     53"Fixed file is broken in changeset:256".
    5454"Fixed ticket:128".
    5555
    5656You can alternatively write the short forms [256] and #128.
    5757
    58 I also configured TortoiseSVN to recognize markup for tickets (ticket: and #). It turns them into clickable links, displays a column in the show log and a field in the commit box.
     58I also configured TortoiseSVN to recognize markup for tickets (ticket: and #). It turns them into clickable links and displays a column in the show log and a field in the commit box.
    5959Changeset: links are also worth using in tickets. Repo links can also be useful in tickets.