Allegro.cc - Online Community

Allegro.cc Forums » Allegro Development » Allegro 5.1.2 released!

This thread is locked; no one can reply to it. rss feed Print
 1   2 
Allegro 5.1.2 released!
Karadoc ~~
Member #2,749
September 2002
avatar

Quote:

Wha?

Notice that in the change log in the first post, some items are written in past tense (eg. "Fixed foo") whereas others are written in present imperative tense (eg. "Fix foo"). I think the inconsistency looks pretty bad.

The developers of git use the imperative style and suggest that others use it too, but in many circumstances the imperative style feels very unnatural to many people, and so the git advice is often ignored - hence the inconsistency.

Here is a stack overflow discussion about it.

-----------

torhu
Member #2,727
September 2002
avatar

If I ever saw a First World problem...

Arthur Kalliokoski
Second in Command
February 2005
avatar

torhu said:

If I ever saw a First World problem...

{"name":"606125","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/0\/600a774f0780079a05ddce2974cff183.png","w":401,"h":396,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/6\/0\/600a774f0780079a05ddce2974cff183"}606125

They all watch too much MSNBC... they get ideas.

torhu
Member #2,727
September 2002
avatar

Elias
Member #358
May 2000

I think in Allegro it depends on who the message is from and what that person felt like using at the time. There is no standard. We also still use SVN :X

--
"Either help out or stop whining" - Evert

Trezker
Member #1,739
December 2001
avatar

I have no standard in my commit messages, and I think it's often unclear what I mean.
But I do always leave some message hinting at what I've done.

weapon_S
Member #7,859
October 2006
avatar

Heh, I was just wondering if Peter Wang might not be a native English speaker ::)

Map SINGLE_CHANNEL_8 to red channel only.

Could someone explain to me why? Or should I understand it as: "mapped only the red channel to SINGLE_CHANNEL_8"?

Quote:

WANT_ANDROID_LEGACY

Out of curiosity (and because I maybe want to do an Android app in the future): which version is legacy? Does this imply a strong incentive to maintain the legacy, or is this the first step to perhaps dropping legacy support?
I'm gonna make a Git-build now... Wait, I mean: make Git-build now! :p

Elias
Member #358
May 2000

It's mapped to GL_RED. Because in GL 3.0+ that's the only single channel format. Before it was mapped to GL_LUMINANCE which they dropped.

--
"Either help out or stop whining" - Evert

Thomas Fjellstrom
Member #476
June 2000
avatar

weapon_S said:

Out of curiosity (and because I maybe want to do an Android app in the future): which version is legacy?

That was a bit of a hack initially. It shouldn't be necessary at all. I'm not sure it does much at the moment.

--
Thomas Fjellstrom - [website] - [email] - [Allegro Wiki] - [Allegro TODO]
"If you can't think of a better solution, don't try to make a better solution." -- weapon_S
"The less evidence we have for what we believe is certain, the more violently we defend beliefs against those who don't agree" -- https://twitter.com/neiltyson/status/592870205409353730

Karadoc ~~
Member #2,749
September 2002
avatar

torhu said:

If I ever saw a First World problem...

Hey man, just because it's a first world problem doesn't mean it isn't a problem. Essentially everything discussed on this site is about first world problems!

-----------

Peter Wang
Member #23
April 2000

Summarising the change log is the single most tedious and time consuming part of making a release. I don't want to complain too much as this is a volunteer project, but if you want to help me out:

  • Make small commits. This is good practice anyway, but as far as the change log goes it saves time splitting entries and prevents missing changes.


  • Provide context. Make the commit message clear without needing to look at the diff or the files that it touches.


  • Write complete sentences with proper capitalisation and punctuation so I don't have to fix them later. Ideally, the first sentence in the message can go directly in the change log.

 1   2 


Go to: