On Wildlife@Home's project preferences pages, it lists the applications which
can be selected to run as:
Application one
Application two
Instead of their actual names. Any reason this would be happening, or any good
way to fix it?
--Travis
--
Hi Steffen,
For what it's worth, I have been building BOINC on the Mac using the "LLVM GCC
4.2" compiler for quite some time with no problems. (This is one of two
compilers provided as part of Xcode 4.4.1, the other is "Apple LLVM Compiler
4.0".)
According to Apple's documentation:
> In Xcode
I will see what I can do.
The git migration made everything interesting.
- Rom
From: boinc_loc [mailto:boinc_loc-boun...@ssl.berkeley.edu] On Behalf Of
Nikolay Saharov
Sent: Wednesday, May 29, 2013 12:21 PM
To: Gianfranco Costamagna
Cc: boinc_dev@ssl.berkeley.edu; boinc_...@ssl.ber
Hi,
Fixed in BTS.
PS: This error is strange. Why there should be additional empty strings if
translated text is shorter than the original msg?
PPS: Rom, could you please update all BTS translation projects from sources? I
think there are a lot of new untranslated strings. The last update was
Sorry for quoting the entire digest
anyway the bug in de.po fixed by Steffen
http://i18n.debian.org/l10n-pkg-status/b/boinc.html
is not only in de, but on ru too
ru.po:371
so would be nice for the russian translator to fix it too.
thanks
Gianfranco
- Messaggio originale -
> Da: "bo
On 5/29/13 11:51 , "Steffen Möller" wrote:
>> Yeah - I was just grumbling about a commit with the only message
>>
>> "Include instead of various places"
>>
>> nothing else - and of course gitk shows for a dozen of files such a
>> change. Every ?!&%%$$ user can see the diff using gitk - so im
Hi Toralf,
>
> Yeah - I was just grumbling about a commit with the only message
>
> "Include instead of various places"
>
> nothing else - and of course gitk shows for a dozen of files such a
> change. Every ?!&%%$$ user can see the diff using gitk - so important
> IMO is just a short n
Hello,
The compiler LLVM (http://en.wikipedia.org/wiki/Clang) makes continuous
progress, both technically and for its acceptance in the community, and is
faster than gcc/g++ in some cases. They have a gcc-compatibility frontent
called "clang", which after a countable number of patches I could
On 05/29/2013 01:08 AM, Charlie Fenton wrote:
> I agree with Jord that 'quick updates', or 'quick fixes' is not helpful, but
> I also don't want to see empty commit messages. I feel that _every_ commit
> should have a commit message briefly describing what was changed and why.
Yeah - I was just
