Here is an explanation of how the source linkage in JIRA works.
The way that JIRA sees an issue being linked to a Git commit is via a plugin
that talks to a Fisheye server. You can see the list of repositories that are
followed by Fisheye through the main interface of the Fisheye server,
https
On Sun 16 Sep 2012 22:07:16 Yang Fan escribió:
> I built both x86 and x64 version, both have the problem. Also I tried
> to test on Windows, it seems that there
> are some other problems, eg .pro project file format is not fully
> compatible with early version (4.8.2 or lower).
OK, clearly not the
I built both x86 and x64 version, both have the problem. Also I tried
to test on Windows, it seems that there
are some other problems, eg .pro project file format is not fully
compatible with early version (4.8.2 or lower).
On Mon, Sep 17, 2012 at 1:39 AM, Lisandro Damián Nicanor Pérez Meyer
wrot
Hello,
Just an update. I fixed the originally reported problem by changing:
#define QT_SOCKLEN_T int
to
#define QT_SOCKLEN_T unsigned
in mkspecs/solaris-cc/qplatformdefs.h
However, now I've run head long in to a new compile error:
/opt/solarisstudio12.3/bin/CC -c -D_REENTRAN
On Fri 14 Sep 2012 04:59:01 Yang Fan escribió:
> I have tested 4.8.3 on LinuxMint12 x86 and Debian6 x64 for my application,
> it reports segment fault on starting up. I'm not quite sure if it is Qt's
> issue or my application's since my application works well yesterday when it
> was built against Q
On Sun, Sep 9, 2012 at 4:41 AM, Rene Jensen wrote:
>
> You got my attention enough that I wanted to look into it (although I'm
> totally *not* worthy of even attempting to fix stuff in Qt, nor do I have
> the time for it). I am pretty close to the scenario above. Fresh Win7, just
> installed the d
>
> I didn't say we don't need documentation. I said there will always be more
> information than what's documented and reviewers are supposed to teach.
>
Will document it.
> > > As I said, it's the "Task-number" that triggers the completion in the
> > > Gerrit
> > > UI.
> >
> > How will the "Ta
> I'm not especially familiar with debugging in VS, but I would have thought
> that in a debug build, VS has enough information about the data types of the
> pimpl classes to display them in the debugger.
Only if you build from the source. If you install the prebuilt libraries then
it has no id
On domingo, 16 de setembro de 2012 10.34.32, Laszlo Papp wrote:
> > In any case, this is why we have reviewers: so they can teach newcomers
> > what
> > the policies are and how we do things. There will never be documentation
> > for
> > every single little thing, there's a lot that is latent knowl
> It's intended for when the source code of the implementation isn't available
> so internal variables and function names can be completely hidden.
That is not the motivation at all in Qt's case. The reasons for it are:
- Binary compatibility between minor Qt versions. Adding, removing or
cha
I've been working on some networking code recently and I got very frustrated
with not being able to see the IP and MAC addresses in QHostAddress and
QNetworkInterface whilst debugging in Visual Studio. After a bit of
experimentation I was able to add viewers for these classes to autoexp.dat and
Hi,
On 09/16/2012 10:23 AM, Thiago Macieira wrote:
> On domingo, 16 de setembro de 2012 07.56.36, Laszlo Papp wrote:
>> wrote:
>>> On domingo, 16 de setembro de 2012 04.54.19, Laszlo Papp wrote:
1) Documentation welcome about such things from a person who well
understand those deeply.
>>
>
> In any case, this is why we have reviewers: so they can teach newcomers
> what
> the policies are and how we do things. There will never be documentation
> for
> every single little thing, there's a lot that is latent knowledge.
>
Why would they teach if the newcomers knew after reading the do
On domingo, 16 de setembro de 2012 10.33.11, Stephen Kelly wrote:
> On Saturday, September 15, 2012 10:36:20 Thiago Macieira wrote:
> > > Does we really need qplatformdefs.h for compile Qt-based application?
> > > I guess it only used to compile Qt self.
> >
> >
> >
> > Fortunately, it's only inclu
On Saturday, September 15, 2012 16:19:49 Loaden wrote:
> > It's probably the same. "default" is either a copy or a symlink to the
> > mkspec
> > Qt was compiled with.
>
> On Windows, "default" not a copy neither symlink. It only include an
> qmake.conf
Indeed. This is why you can't include qplatf
On domingo, 16 de setembro de 2012 07.56.36, Laszlo Papp wrote:
> wrote:
> > On domingo, 16 de setembro de 2012 04.54.19, Laszlo Papp wrote:
> > > 1) Documentation welcome about such things from a person who well
> > > understand those deeply.
> >
> > As far as I know, "Task-number:" is the keyword
>
> People now keep pasting the hard coded link in such situations as far as I
> see which is not clickable right away and hard coded. It would be nice if I
> could write something like "Review-number: QTREVIEW-31541" or something
> like that.
>
Sorry, I was wrong. The hard coded url is also click
17 matches
Mail list logo
