Mercurial > hgsubversion
view tests/fixtures/binaryfiles.sh @ 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 | f1919e1c35bf |
children |
line wrap: on
line source
#!/bin/sh # # Generate binaryfiles.svndump # mkdir temp cd temp mkdir project-orig cd project-orig mkdir trunk cd .. svnadmin create testrepo svnurl=file://`pwd`/testrepo svn import project-orig $svnurl -m "init project" svn co $svnurl project cd project/trunk # Add a regular binary file, and an unflagged one python -c "file('binary1', 'wb').write('a\0\0\nb\0b')" python -c "file('binary2', 'wb').write('b\0\0\nc\0d')" svn add binary1 binary2 svn propset svn:mime-type application/octet-stream binary1 svn propdel svn:mime-type binary2 svn ci -m 'add binaries' # Update them python -c "file('binary1', 'wb').write('a\0\0\nc\0d')" python -c "file('binary2', 'wb').write('b\0\0\0\nd\0e')" svn ci -m 'change binaries' # Remove them svn rm binary1 binary2 svn ci -m 'remove binaries' cd ../.. svnadmin dump testrepo > ../binaryfiles.svndump