2009/11/16 Graeme Geldenhuys gra...@mastermaths.co.za:
Vincent Snijders wrote:
I am interested to hear how long it takes/took to merge this weeks
changes. I think in the end automating a bit is worth the effort, unless
you can merge the current batch in less than 5 minutes.
:-) It was a
2009/11/16 Vincent Snijders vincent.snijd...@gmail.com:
Ok. That seems doable for now. It took you less time than me. :-)
Good to know. :)
I have written (or am writing) an application to identify which
revisions change the same files, so I can group them together in one
merge.
What if a
Graeme Geldenhuys schreef:
I have written (or am writing) an application to identify which
revisions change the same files, so I can group them together in one
merge.
What if a revision changed more that one file (which happens often)?
I see no problem, it just helps me to see that two
2009/11/16 Vincent Snijders vsnijd...@vodafonevast.nl:
Wouldn't that cause problems. Also how would that affect me?
Not at all.
Good to know, thanks. I was simply worried that the commit messages
will change etc if various commits are rolled into one and the commit
log description doesn't
On 31/10/2009, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
The Lazarus team is glad to announce the 0.9.28.2 release.
Thanks Vincent. I have updated the Git mirror with a v0.9.28.2 tag as well.
If anybody else is using the Git mirror, your next 'git pull' will get
the new tag as well,
On 04/11/2009, Vincent Snijders vsnijd...@vodafonevast.nl wrote:
On #lazarus-ide, IRC, somebody said that the fixes_0_9_28 branch was out of
sync, is that still true?
No. The sync (for fixes branch) is not a automated process, but I try
and update it once a week (normally Mondays). If
The Lazarus team is glad to announce the 0.9.28.2 release. This release
is based on fpc 2.2.4.
This release can be downloaded from the SourceForge download page:
http://sourceforge.net/projects/lazarus/files/
The Lazarus 0.9.28 release had two known issues. This release fixes:
* Fixed compiling
