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

Bug fixes in seeking and fix for uninitialized usec in struct timeval #76

Merged
merged 2 commits into from
Dec 22, 2018

Conversation

mlburgett
Copy link
Contributor

No description provided.

Bugfixes  Seek, and uninitialed var

Fix uninitialized struct member in Socket.cpp

Fix seeks that aren't on block boundaries
Fixes in seeking, fix uninitialized struct timeval in socket.cpp
@sub3 sub3 merged commit 42a9a4b into kodi-pvr:master Dec 22, 2018
@ksooo
Copy link
Member

ksooo commented Dec 22, 2018

@sub3 the "Update addon.xml..." commit looks really insane. Look at all these strings.po changes. Only changes to en_gb must be committed, all other languages are handled through Transifex...

@mlburgett
Copy link
Contributor Author

mlburgett commented Dec 22, 2018

@ksooo I know it looks strange in the commit, I had some issues squashing my changes in my repo before putting up the PR, but if you look at the 'Files Changed' tab for this PR, it looks as I expected.

@ksooo
Copy link
Member

ksooo commented Dec 22, 2018

I would not have approved/merged the PR in this state. ;-)

@sub3
Copy link
Contributor

sub3 commented Dec 22, 2018

Sorry Ksooo - we'll try to get our shit a little more together for the next PR :-)

@mlburgett
Copy link
Contributor Author

I think it was because my changes were in progress over a number of months, and I pulled in the upstream master changes occasionally. So while those changes were in my commit in my repo, they were identical to changes already in this repo, and fell out in the PR. Next time I think I squash first, and then merge my working branch into my master, which was already synced with the upstream.

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

Successfully merging this pull request may close these issues.

3 participants