 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm going to pass on the latest version, beta.3 , because it doesn't
include the stack fix (#235) which I can't work around, and it doesn't
include the "." fix, which I *could* work around.
origin/release/v3.7.1 looks tempting though...
--
dik
Post a reply to this message
Attachments:
Download 'smartgitvisualizepovray.png' (31 KB)
Preview of image 'smartgitvisualizepovray.png'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 19.02.2017 um 06:17 schrieb dick balaska:
> I'm going to pass on the latest version, beta.3 , because it doesn't
> include the stack fix (#235) which I can't work around, and it doesn't
> include the "." fix, which I *could* work around.
> origin/release/v3.7.1 looks tempting though...
Tagged the wrong branch.
Try again now.
(Sheesh, why do you folks always have to look just when I'm busy making
a mistake... 30 minutes later, and nobody would have noticed my blunder...)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 19-2-2017 6:40, clipka wrote:
> (Sheesh, why do you folks always have to look just when I'm busy making
> a mistake... 30 minutes later, and nobody would have noticed my blunder...)
>
LOL
A fair example of how Real Life works... :-)
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 2017-02-19 00:40, also sprach clipka:
>
> (Sheesh, why do you folks always have to look just when I'm busy making
> a mistake... 30 minutes later, and nobody would have noticed my blunder...)
>
I gathered by the commit dates that that was not what you wanted. "I'll
just tag this 2 week old branch/commit instead of the one that has the
fixes and stuff I just committed"
Weird that my local git repo refused to move that tag. But this worked:
rm -rf povray && git clone https://github.com/POV-Ray/povray.git && cd
povray && git checkout v3.7.1-beta.3 && cd unix && ./prebuild.sh && cd
.. && ./configure COMPILED_BY="Dick Balaska <dic### [at] buckosoft com>" &&
make && cp unix/povray ~/bin/povray371.beta.3
It passes my smoke tests on Windows and Linux. I will let it go live on
my farm tomorrow when I can keep an eye on it for a bit. (Between 40
minutes to 2 hours before it kicks in and if it goes south, it takes a
minute to create 1000s of bad frames that may be painful to remove.)
--
dik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 19.02.2017 um 09:37 schrieb dick balaska:
> Weird that my local git repo refused to move that tag. But this worked:
I guess in the Git world there technically isn't such a thing as moving
a tag, and Git seems to refuse to automatically ditch a local tag in
favour of a remote tag of the same name.
Deleting the tag from your local repo and then fetching all tags again
should also have worked.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
