New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Developers/SVN_QuickReference (diff) – NEMO

Changes between Version 28 and Version 29 of Developers/SVN_QuickReference


Ignore:
Timestamp:
2017-12-08T17:58:22+01:00 (7 years ago)
Author:
nicolasmartin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Developers/SVN_QuickReference

    v28 v29  
    8080# for csh  "    "      "      ""  ,      "      ""    "    "" "" ~/.login                     ) 
    8181setenv SVN_EDITOR='your_favourite_editor' 
    82 # Commit and write the log message (ticket link #.... and so on) in your editor 
    83 svn ci files_list # `svn ci` without files list will commit all modified files recursively from the current directory 
    84 # or directly from the command line of the shell session 
    85 svn ci  -m 'log message' files_list 
    8682}}} 
    8783 
    88 ==== Commit message syntax 
     84{{{#!div class="notice system-message" 
    8985 
    90 New syntax to add in commit message to enable extended functionalities `[command #ticket_number]` 
    91 * Add commit message as comment in the ticket: ex `[see #ticket_number]`, you can use a word in `addresses re references refs see` 
    92 * Close a ticket with the commit: ex `[fix #ticket_number]`,  you can use a word in `close closed closes fix fixed fixes` 
     86__Recommended syntax to be added in the commit message__ 
     87 
     88* If the commit is related to one or several tickets, we highly suggest to add the commit message as ticket comment.     \\ 
     89  To do so, you can use one of the word in the list `addresses re references refs see` followed by usual ticket link(s). \\ 
     90  ''Ex: `see #1948` somewhere in the commit message to link with #1948'' 
     91 
     92* If the commit is a fix for one or several tickets, you can close them with the commit.                                    \\ 
     93  To do so, you can use one of the word in the list `close closed closes fix fixed fixes` followed by usual ticket link(s). \\ 
     94  ''Ex: `fix #1948` somewhere in the commit message to close #1948 without a browser.'' 
     95 
     96__Be careful if you mix the 2.__ 
     97 
     98}}} 
     99 
     100{{{#!sh 
     101# Commit and write the log message (ticket link #.... and so on) in your editor 
     102svn ci files_list 
     103# `svn ci` without files list will commit all modified files recursively from the current directory 
     104# or directly from the command line of the shell session 
     105svn ci -m 'log_message' files_list 
     106}}} 
     107 
    93108 
    94109=== Tag