Github/Source code saltiness thread

dragontamer8740

Well-Known Member
Nov 9, 2015
53
55
Please don't spam @ Gedan. Also, she has other priorities that come before the public github she will do it if she finds time to do it
Not sure if two people doing it really counts as spamming yet.
Anyway, unless I'm forgetting something this is all that it should take to do it. Correct me if I'm wrong.
Code:
git push <remote> <commit hash>:master
…assuming there's already a remote set up, like what would be done with
Code:
git remote add public_github https://github.com/OXOIndustries/TiTS-Public.git
Final command:
Code:
git push public_github <revision hash>:master
I really just wish that if we were getting a delayed release that we'd at least get some statement to that effect so I could stop having the expectation that my 'git pull' would actually check out the latest public build's code when I tried it.
And it's the saltiness thread, so I'm a little salty. we're a day or so short of halfway through October now.

All that said, I'm really sorry if there's a good reason for this and I'm just getting worked up over nothing.
 
Last edited:

dragontamer8740

Well-Known Member
Nov 9, 2015
53
55
Nip the problem in the bud before it becomes one
OK.
It just seems a little strange to me that you, original author of this salt thread, apparently aren't at all salty that we haven't gotten a git push in two months now (although it's only one month since we were supposed to get one last.)
At this point I am still salty but kind of resigned to it and only checking in every week or so.

Your original requests still don't feel unreasonable to me, especially after a month rather than a simple three days:
It's been like three days please give us the source code. How do you expect me to keep the wiki up to date without it?

Increase the salt to force them to release the code (or at least give a reason for not releasing with an ETA)
 

SeriousBlueJewel

Well-Known Member
Nov 5, 2018
1,677
867
OK.
It just seems a little strange to me that you, original author of this salt thread, apparently aren't at all salty that we haven't gotten a git push in two months now (although it's only one month since we were supposed to get one last.)
At this point I am still salty but kind of resigned to it and only checking in every week or so.

Your original requests still don't feel unreasonable to me, especially after a month rather than a simple three days:

The ship update that was released at that time was a rather major update that I wanted to work on, so i got rather impatient. Although I will bug them extremely hard a soon as the next public goes online though.
 

dragontamer8740

Well-Known Member
Nov 9, 2015
53
55
We're still down a couple version numbers. 0.8.029 vs 0.8.031.
Not really very upset/annoyed this time, since we're at least close to current and the changes are pretty small, but I thought I might as well mention it in case anyone's listening.
Thanks for the .029 bump in any event.
 
  • Like
Reactions: SeriousBlueJewel

Nitan

New Member
Dec 21, 2019
2
2
Switch the branch from "master" to "public", the latter was updated with 0.8.040 code, apparently on 10th december. That's recent enough, but I only just now found out it was updated at all. I wish the public github was less of a mess, huge delays and sometimes updates go on the default branch, other times onto the second one.
 

Dorkulon

Well-Known Member
Sep 10, 2015
89
25
Switch the branch from "master" to "public", the latter was updated with 0.8.040 code, apparently on 10th december. That's recent enough, but I only just now found out it was updated at all. I wish the public github was less of a mess, huge delays and sometimes updates go on the default branch, other times onto the second one.
To be precise: fen committed the changes to the branch in his local repo on 10 dec, but only pushed the changes in the past twelve hours or so. (And no, there's no way to show within git when a change was actually pushed, because git is terrible.)
 

Nitan

New Member
Dec 21, 2019
2
2
To be precise: fen committed the changes to the branch in his local repo on 10 dec, but only pushed the changes in the past twelve hours or so. (And no, there's no way to show within git when a change was actually pushed, because git is terrible.)
Ah, that explains a lot, thanks!