Git-svn-helpers

Latest version: v0.9

Safety actively analyzes 613750 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

1.0

----------------

* No changed yet.

0.9

----------------

* The cannonical repository is now in https://github.com/collective.
[rossp]

* Fix the handling when switching to a svn branch that git already has
a local branch for.
[rossp]

0.8

----------------

* Make the init command follow along if the svn repository has been switched
to another branch. Thanks to Calvin Hendryx-Parker for reporting the issue.
[tomster]

0.7

----------------

* Use full copies instead of symlinks to create working copies. This avoids
the issue of having the git and svn repository out of sync when working
with multiple copies of the same repository and greatly reduces the risk of
conflicts.

This also means, that the fetch command now only operates on the cache
without modifying the working copy (making it safe to run via crontab,
for example)

Running gitify against an old-style working copy will produce an error.
Simply deleting the symlink and re-running gitify remedies that, however.

Another effect, is that the init command is now only needed once for each
working copy (it is no longer necessary to re-run the command after
switching between different working copies of the same repository).

gitify therefore no longer defaults to the init command (just as neither
git nor svn do anything w/o supplying an explicit action). Also, it has been
renamed from ``gitify`` (back) to ``init``.
[tomster]

* Allow the ``help``, ``--version`` and ``fetch`` commands to run outside .svn directories
[tomster]

0.6

----------------

* add a file manifest so that all necessary files will get included for sdist
[proyvind]

* sample update hook for enforcing dcommits to help keeping the svn and git
repositories in sync
[chaoflow]

* updated tests to work with git 1.6.x
[tomster]

* removed deprecated entry points for clone, fetch and commit
[tomster]

0.5

-----------------------------------------

* Added ``gitify update`` command, which performs a git-svn rebase operation
for the current svn checkout but also handles uncommitted local changes
gracefully (unlike ``git svn`` but like svn does)

* No longer use the logging module for user feedback. That idea was rather
misguided :)

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.