-
Notifications
You must be signed in to change notification settings - Fork 44
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
Integrate changes from dsmithni/LabViewGitEnv with sourcetree support #2
Comments
Hey Joerg, I like your list of to-dos. I saw an example of a shell function in your script and it looks pretty straightforward. I thought about that as I was writing, but since I have such a tenuous grasp on the language, baby steps on the data made it easy to understand :) In the commit I made earlier, I changed /tmp/ to use the mingw $HOME variable, so its no longer linked to me--I'm not sure if the way I did it is the easiest, but it works. I also tried to comment what I added, but since I was learning as I played with the script, there are probably places where I modified things unnecessarily because I was just doing it wrong. Oh well. That having been said, I had already done what you described above and put together a test repo. Command line works with the following: Command line also works with: Anyway, as I mentioned in the email I've got a series of things going on for the next week and a half, so I probably won't have more time to work on it until at least the week of the 19th...but I'm sure it can wait a week. Thanks for your interest! |
"Refactoring some code, espacially in LVCompareWrapper.sh. Done "Testing if everything works with sourcetree and via command line." Looks like diff was an issue because of relative path, so I changed the init script to give a full path to the sh file. Still having issues with merge. No parameters are passed to the script by git, as is. I took a look at the git config --system -l results after calling LVInit and the parameters are not being added to the configuration--just the script path. Not sure whats going wrong. Would you mind taking a look at the init script? |
Wow, there really is something going on. I didn't have much time yet looking into it but there is one thing a found, maybe that hepls. $PWD ...This gives the value of the Variable PWD So line 44 should look like this: DIFFCMD="$(pwd)/bin/LVCompareWrapper.sh" Also, you did remove the explicit Variable use with the curly bracktes several times. Please add the brackets again. I know they are not needed always, but they can save hours of bebugging time. They are pretty much life guards... ;) Also in LVConfig you used: I will have a closer look into it once I am at a Windows PC again at University on monday. Great work, keep it up... thumbs up EDIT: OK, I checked it and the problem were the single quotes. As a rule of thumb: Don't ever use single quotes unless you really really know what you are doing. Just let DIFFCMD and MERGECMD look like described above. |
Hey, just saw your edit. I did replace all the |
OK, I give up. I pushed some changes which make everything work perfectly fine on the command line, and it also seems to work from sourcetree...but it only works with system, because I hardcoded the paths as /usr/local/bin/.....I can't make it work any other way. Sourcetree works with \Git\local\bin\LVCompareWrapper.sh "$LOCAL" "$REMOTE" and ...\LVMergeWrapper.sh "$BASE" "$REMOTE" "$LOCAL" "$MERGED" |
@dsmithni [1] did some great work to make this project run with sourctree [2]. This issue is intended to integrate his work into this project to make it even more awesome. But first things first.
What needs to work
On a simple git repo these commands need to work in command line and via sourcetree:
If they work everything else should work too. We could create a sample repo with two branches, some commits and simple VIs to test this.
What needs to be done
What could be done
I never liked using a "windows" branch too much. Maybe we should move everything into one branch and create kind of an installer, or an installable zip. A ZIP would be nice, we it had to be hosted somewhere and it would be completely static. An installer script would be nice and could do some of the configuration work, but we would have to write it.
We really need to test merging capabilities of LabView. Maybe a good solution would be to merge VIs and create a simple merge commit and later on fix the VIs. I just don't think that bigger projects can be merged in a nice way.
[1] https://github.com/dsmithni/LabViewGitEnv
[2] http://www.sourcetreeapp.com/
The text was updated successfully, but these errors were encountered: