svn log не показывает все изменения

Question

Я довольно новичок в svn, я в основном использовал git. Вопрос в том, как это происходит, когда я запускаю svn logon в этом репо: https://code.google.com/p/gwt-ext/source/list не все версии отображаются? Например, я запускаю svn log -v http://gwt-ext.googlecode.com/svn/trunk/ В нем не отображаются последние две версии (r1878 и r1877), и он не показывает r1870, и я не знаю почему.

Answer 1

Потому что эти изменения не относятся к багажнику.

Запуск svn log в корне репо, если вы хотите все увидеть.

Answer 2

svn log содержит только номера ревизий, применимых к ответвлению, к которой применяется.

Если в каталоге внесены изменения, он перечислит эти изменения и только эти изменения в журнале.

I.e. r1870 не относится к этой части кода.

Answer 3

Вы должны сделать

обновление СВН

$ svn help update 
update (up): Bring changes from the repository into the working copy. 
usage: update [PATH...] 

    If no revision is given, bring working copy up-to-date with HEAD rev. 
    Else synchronize working copy to revision given by -r. 

    For each updated item a line will be printed with characters reporting 
    the action taken. These characters have the following meaning: 

    A Added 
    D Deleted 
    U Updated 
    C Conflict 
    G Merged 
    E Existed 
    R Replaced 

    Characters in the first column report about the item itself. 
    Characters in the second column report about properties of the item. 
    A 'B' in the third column signifies that the lock for the file has 
    been broken or stolen. 
    A 'C' in the fourth column indicates a tree conflict, while a 'C' in 
    the first and second columns indicate textual conflicts in files 
    and in property values, respectively. 

    If --force is used, unversioned obstructing paths in the working 
    copy do not automatically cause a failure if the update attempts to 
    add the same path. If the obstructing path is the same type (file 
    or directory) as the corresponding path in the repository it becomes 
    versioned but its contents are left 'as-is' in the working copy. 
    This means that an obstructing directory's unversioned children may 
    also obstruct and become versioned. For files, any content differences 
    between the obstruction and the repository are treated like a local 
    modification to the working copy. All properties from the repository 
    are applied to the obstructing path. Obstructing paths are reported 
    in the first column with code 'E'. 

    If the specified update target is missing from the working copy but its 
    immediate parent directory is present, checkout the target into its 
    parent directory at the specified depth. If --parents is specified, 
    create any missing parent directories of the target by checking them 
    out, too, at depth=empty. 

    Use the --set-depth option to set a new working copy depth on the 
    targets of this operation. 

Valid options: 
    -r [--revision] ARG  : ARG (some commands also take ARG1:ARG2 range) 
          A revision argument can be one of: 
           NUMBER  revision number 
           '{' DATE '}' revision at start of the date 
           'HEAD'  latest in repository 
           'BASE'  base rev of item's working copy 
           'COMMITTED' last commit at or before BASE 
           'PREV'  revision just before COMMITTED 
    -N [--non-recursive]  : obsolete; try --depth=files or --depth=immediates 
    --depth ARG    : limit operation by depth ARG ('empty', 'files', 
          'immediates', or 'infinity') 
    --set-depth ARG   : set new working copy depth to ARG ('exclude', 
          'empty', 'files', 'immediates', or 'infinity') 
    -q [--quiet]    : print nothing, or only summary information 
    --diff3-cmd ARG   : use ARG as merge command 
    --force     : force operation to run 
    --ignore-externals  : ignore externals definitions 
    --changelist [--cl] ARG : operate only on members of changelist ARG 
    --editor-cmd ARG   : use ARG as external editor 
    --accept ARG    : specify automatic conflict resolution action 
          ('postpone', 'working', 'base', 'mine-conflict', 
          'theirs-conflict', 'mine-full', 'theirs-full', 
          'edit', 'launch') 
          (shorthand: 'p', 'mc', 'tc', 'mf', 'tf', 'e', 'l') 
    --parents    : make intermediate directories 

Global options: 
    --username ARG   : specify a username ARG 
    --password ARG   : specify a password ARG 
    --no-auth-cache   : do not cache authentication tokens 
    --non-interactive  : do no interactive prompting (default is to prompt 
          only if standard input is a terminal device) 
    --force-interactive  : do interactive prompting even if standard input 
          is not a terminal device 
    --trust-server-cert  : accept SSL server certificates from unknown 
          certificate authorities without prompting (but only 
          with '--non-interactive') 
    --config-dir ARG   : read user configuration files from directory ARG 
    --config-option ARG  : set user configuration option in the format: 
           FILE:SECTION:OPTION=[VALUE] 
          For example: 
           servers:global:http-library=serf 

Answer 4

Чтобы увидеть все изменения, независимо от отраслевого использования этой команды:

svn log -r 0:HEAD ^/ 

Это должно работать в то время как в любой отрасли