Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One-way Bridge #11

Closed
WtfJoke opened this issue Apr 26, 2015 · 2 comments
Closed

One-way Bridge #11

WtfJoke opened this issue Apr 26, 2015 · 2 comments

Comments

@WtfJoke
Copy link
Member

WtfJoke commented Apr 26, 2015

One possible step during migration of a SCM-System is to have both systems running paralell to a certain point.

In that case I want to have an easy way, to keep the git-repository up to date. At the moment you can achieve the same by resume the script, but its a bit of an overhead.

So I like to have a special function, which only compares a workspace to the current stream and accept it one by one.

@WtfJoke WtfJoke changed the title Support of one-way Bridge One-way Bridge Apr 26, 2015
@WtfJoke
Copy link
Member Author

WtfJoke commented Aug 14, 2015

is partly fixed by 3c105e8.

The only advantage we would have with a real bridge, would be some unnecessary compare commands and a workspace load

EDIT: And a fire & forget style

@WtfJoke
Copy link
Member Author

WtfJoke commented Aug 28, 2015

With the latest improvements, its not necessary to have this bridge anymore.
If you want to update to the latest state of a workspace, you just can rerun the script.

@WtfJoke WtfJoke closed this as completed Aug 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant