On 05/04/16 22:56, "Development on behalf of Giuseppe D'Angelo"
wrote:
>Il 10/03/2016 08:37, Knoll Lars ha scritto:
>>> >
>>> >Individually or together, +1 from me.
>> Fully agree with what
If it is, can someone try a regular toolchain for that platform with Qt 5.6
and report whether QtCore links? I'd like a second opinion with a different
toolchain than the reporter.
The question is: if you use functionality, do you need an extra -l
flag?
--
Thiago Macieira - thiago.macieira
Il 10/03/2016 08:37, Knoll Lars ha scritto:
>
>Individually or together, +1 from me.
Fully agree with what Alan is saying, so another +1 from me.
I guess it's time to do the honours then? :)
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a
If you want to know the names of all branches which contain a given ref,
there's also the `git branch --contains yourRef`.
Cheers,
Jan
--
Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
___
Development mailing list
On 2016-04-04 08:49, René J.V. Bertin wrote:
> [...] there's no way to obtain the branch from a given commit?
There is `git name-rev`, but it may or may not work or give you the
"best" answer. At least it should give you *a* branch name if a SHA is
the tip of a local branch. I'm not sure offhand
On Sunday, March 20, 2016 12:07:01 PM Sean Harmer wrote:
> Hi,
>
> Can MSVC 2012 configurations be removed from the CI please? My understanding
> is that this compiler was only kept around to support Windows EC but that
> this is now removed from 5.7.
I'd love to remove it, but it's blocked by
On segunda-feira, 4 de abril de 2016 10:25:16 PDT Welbourne Edward wrote:
> $ git stash
> $ git pull -r
> $ git stash pop
Also:
$ git fetch
$ git rebase --autostash
It's exactly the same.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology
I mentioned:
>> merge-base - if you have a strict tree, this isn't a merge, so it's
>> where one was branched off the other, but nothing about the merge-base
>> or any of its ancestors contains any hint as to which branch it was on
>> when it was committed.
René J.V. Bertin replied:
> In short,
> Forgot - maybe a stupid question, but can you set up a topic branch to
> track a remote branch (and would that make sense)?
$ git checkout -b topic remote/branch
will, by default, set up topic so that, while it's checked out, git pull
fetches remote/branch to merge with it (or rebase it onto)