Re: The Software drives me crazy
Posted: Fri Feb 26, 2016 12:45 pm
.
LitePlacer support forums
https://liteplacer.com/phpBB/
Code: Select all
public bool CalibrateTape(TapeObj x)
Code: Select all
Tuple<double, double> result = SimpleRegression.Fit(Xs, Ys);
Pixopax wrote: Git does still not work for me, messes everything up. So I stay away from it. I am sure it us the user in front of the keyboard who makes the error here, but I just do not understand how git works, inspite reading the manuals 3 times. It does not do what I expect, so before I destroy anything I let it be.
As soon as I have a descent working software-version, I would post the result, and someone who knows how to do it could merge it to Github.
To this point, it seems about right.Pixopax wrote:I forked it from github, branched it and then changed the code.
Pixopax wrote:Now Git shows me changes I did not do
Sorry Louis, but I have to object. I have used (sometimes had to use) many different code versioning systems in my professional career.Pixopax wrote:As I said, Git is a p.i.t.a. made by linux fricklers for linux fricklers.
You have to understand that there are several repositories: You have a local repository, and any changes you do are committed to that local repository. New files have to be added to git control.Pixopax wrote:Also, I am afraid of killing something, as I cannot see what git does, I am also confused why the publish button is almost hidden, it seems to me as one should not really push that button, is that correct?
That fork is Karl's, who goes by the username knaster on this forum. And, btw, forks on GitHub are easy to find:Pixopax wrote:Also, who manages this "knaster" repository? Is there someone at all? In Git, one can hardly find it, under "liteplacer" it is not listed, "knaster" ist also not found. I got to it via the link here in the forum.
Please DON'T DO THIS. If you do a lot of changes outside version control and then commit a large bunch of files later, we loose history and transparency. My suggestion is to commit small and often. A self-contained change, as the ones you described above, deserves a quick commit with an explanation what was fixed and why. Together with the really good diff view on GitHub this allows anybody to follow along and merge that particular change into their fork.Pixopax wrote:So I stay away from it. I am sure it us the user in front of the keyboard who makes the error here, but I just do not understand how git works, inspite reading the manuals 3 times. It does not do what I expect, so before I destroy anything I let it be.