Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

libActivities #37

Open
wants to merge 36 commits into
base: repoman
Choose a base branch
from
Open

libActivities #37

wants to merge 36 commits into from

Conversation

scunz
Copy link
Member

@scunz scunz commented May 8, 2015

Author @antis81:
To follow discussion and implementation status of all the related PR's, please head over to MGV-Redmine.

@antis81
Copy link
Member

antis81 commented May 9, 2015

@scunz I just cleaned up the issues, putting everything in the right places (well, technically 😄).

How about setting up a "real" integration branch like integrate/activities based on this one?

In theory, we could use those branches to built and check preview releases (milestones) by Jenkins.

@antis81
Copy link
Member

antis81 commented May 9, 2015

⚡ Build fails:

/home/nils/Projects/MacGitver/Libs/libActivities/Activity.cpp:79:13: error: use of undeclared identifier 'assert'
            assert(running + success > 0);
            ^

@scunz Something's missing?

@scunz
Copy link
Member Author

scunz commented May 9, 2015

You're on linux, right?

@antis81
Copy link
Member

antis81 commented May 9, 2015

Yes, I'm on Linux. There's a few more compile errors of the same kind after fixing this one. Further some typos cause problems in the include section on case sensitive file systems. Shall I commit the fixes to the sacu/activities branch?

Btw.: Why not use Q_ASSERT macro instead?

@scunz
Copy link
Member Author

scunz commented May 12, 2015

Yes, please commit them on top of this (Not sure if you already did, but if so, rebase and push again, please).

I've just rebased everything once more and force-push'ed it (without seeing your comment). There's obviously something wrong with github and my mail...

scunz added 3 commits May 12, 2015 07:14
When we'll move most of Internal to Data, the Dumper class
resides where it is. So this'll make things easier later on
@antis81
Copy link
Member

antis81 commented May 12, 2015

@scunz Hm ... the other fixes belong to libRepoMan. Should I commit them here anyways?

@scunz
Copy link
Member Author

scunz commented May 12, 2015

Again, no notification per email. Think I've to ask GH Support for that one now.

@antis81, yes, commit them here to not-block yourself. But bear in mind that I'm in the process of un-fucking my mistakes in the repoman and I'm constantly rebasing it, so I can get the contents of the 3 "big" commits separated out. While I'm doing that, it's likely that there will be new temporary breakage introduced and some will vanish occasionally. The goal is to have every commit in repoman compile by itself.

So, if you commit repoman fixes here, I'll take care that repoman is changed in a way that these problems don't exist in the first place - but to do that earlier I need to be aware of them; otherwise they'll probably not be fixed before I'm at that stage...

@scunz
Copy link
Member Author

scunz commented May 12, 2015

rebased again.

In addition to my previous comment: I.e. spot all the commits with "Fixup" in their name. They're meant to be moved into some other commit at some point.

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

Successfully merging this pull request may close these issues.

None yet

2 participants