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

Vss2Git not working after import of *.ssa SourceSafe-Archive into new VSS database. #58

Open
AxelWS opened this issue Jul 6, 2020 · 1 comment

Comments

@AxelWS
Copy link

AxelWS commented Jul 6, 2020

Hi trevorr,

Github is new to me w.r.t. actively contributing. I tried to push my local fixes branch but got "remote: Permission to trevorr/vss2git.git denied to AxelWS." Which probably means not every newbee can contribute into your repo?

Best Regards
Axel


This branch contains some changes I had to do because the Visual SourceSafe projects we have to work on were supplied as *.ssa exports from SourceSafe and after restoring them into a new VSS database Vss2Git got confused by the time stamps of restore actions in a way that made the resulting Git repository quite useless. I tried to make the changes low risk, but in the end I guess there is not enough testing yet for this branch to go to main. I won't have the time to do more testing beyond using it for our projects, but I will try to push the branch in the hope that it may help someone with similar problems. It may also help if you have a repository where the commit/checkin times are seriously messed up. The branch also includes some minor usability changes, including one or two from branch remigius.

@trevorr
Copy link
Owner

trevorr commented Jul 6, 2020

Hi Axel, you need to Fork the repository into your own account, and then you can push changes to that. The Fork button is usually in the upper right of the GitHub page. Once you have a fork, you can submit a pull request to merge changes from your branch into a branch on this repository. However, I don't generally accept pull requests unless they are very small and low-risk, since I don't have any way to test them anymore. Still, it can be useful to create one to help other people experiencing the same issue find your fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants