view tests/fixtures/executable_file_empty_prop.svndump @ 1236:f367a4462191

push: update to branch tip instead of tip We previously updated to the repository tip after pushing a revision, presumably on the assumption that tip would be the last revision we just pushed. This assumption is flawed for high traffic repositories. In particular, you previsouly would sometimes end up on a completley unrelated commit if someone else commits to a different branch in between the time we push a revision and pull it back from the server. This changes to instead update to the branch tip of the branch we were on at the beginning of the push. This should be either the revision we just pushed or a linear descendent of the revision we just pushed, with a fair degree of reliability.
author David Schleimer <dschleimer@fb.com>
date Sat, 30 Aug 2014 09:23:31 -0700
parents 5497d1264b4d
children
line wrap: on
line source

SVN-fs-dump-format-version: 2

UUID: 60adb0cc-4d5c-4038-bbb4-90f4595cf81c

Revision-number: 0
Prop-content-length: 56
Content-length: 56

K 8
svn:date
V 27
2008-11-25T15:02:16.557895Z
PROPS-END

Revision-number: 1
Prop-content-length: 115
Content-length: 115

K 7
svn:log
V 15
Basic structure
K 10
svn:author
V 5
Augie
K 8
svn:date
V 27
2008-11-25T15:02:45.454954Z
PROPS-END

Node-path: branches
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END


Node-path: tags
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END


Node-path: trunk
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END


Revision-number: 2
Prop-content-length: 103
Content-length: 103

K 7
svn:log
V 4
blah
K 10
svn:author
V 5
Augie
K 8
svn:date
V 27
2008-11-25T15:03:45.151223Z
PROPS-END

Node-path: trunk/foo
Node-kind: file
Node-action: add
Prop-content-length: 36
Text-content-length: 4
Text-content-md5: c157a79031e1c40f85931829bc5fc552
Content-length: 40

K 14
svn:executable
V 0

PROPS-END
bar