Am 24.10.2010 20:20, schrieb Vincent Snijders:
> 2010/10/24 Graeme Geldenhuys :
>> On 24 October 2010 19:50, Florian Klämpfl wrote:
>>>
>>> Everybody gets the replys he deserves :)
>>
>> That's correct. :)
>>
>
> At least you agree on some thing :-)
I wondered too, I expected complaints about mi
2010/10/24 Graeme Geldenhuys :
> On 24 October 2010 19:50, Florian Klämpfl wrote:
>>
>> Everybody gets the replys he deserves :)
>
> That's correct. :)
>
At least you agree on some thing :-)
Vincent
___
fpc-other maillist - fpc-other@lists.freepascal
On 24 October 2010 19:50, Florian Klämpfl wrote:
>
> Everybody gets the replys he deserves :)
That's correct. :)
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net:8080/fpgui/
__
Am 24.10.2010 19:48, schrieb Graeme Geldenhuys:
> On 24 October 2010 19:43, Florian Klämpfl wrote:
>>
>> Why shows git log only a one liners? I though using git fixes this?
>
> God, now you're being stupid too. 'git log' if you are using the FPC
> git mirror, or 'svn log' if you are using FPC's s
On 24 October 2010 19:43, Florian Klämpfl wrote:
>
> Why shows git log only a one liners? I though using git fixes this?
God, now you're being stupid too. 'git log' if you are using the FPC
git mirror, or 'svn log' if you are using FPC's subversion repository
directly.
--
Regards,
- Graeme -
On 24 October 2010 19:11, Marco van de Voort wrote:
>
> I don't understand what providing quick and dirty patches that
How do you get to 'quick and dirty'? Not every small patch is a hack
or quick or dirty. The same applies for bigger patches. If the author
of the patch simply explains in th
Am 24.10.2010 19:37, schrieb Graeme Geldenhuys:
> Just to 'svn log' or 'git log' and actually look at the history of the
> FPC project and the commit messages of each commit. 99% are one
> liners.
Why shows git log only a one liners? I though using git fixes this?
_
On 24 October 2010 19:09, Florian Klämpfl wrote:
>
> Oh yes, the vcs is to blame for poor commit comment.
Or maybe actually manager YOUR project better, by telling all the
read/write users of your project to give better commit messages.
Nobody can describe a patch very well, and the reason for th
2010/10/23 Adem :
> work, use git to ingrate that fix/feature after every update.
> This way, you will have micro-forked FPC (or Lazarus or whatever) but it is
This works very well indeed. I have +- 15 such feature branches for
Lazarus IDE alone, and it takes all of 1 minute to rebase and merge
th
In our previous episode, Graeme Geldenhuys said:
> > Graeme's last mail where he explains he just wants to drop quick and dirty
> > patches AND IT IS FPC'S CORE TEAM JOB to make head or tails of it,
> > explains the fundamental misconception better than I could do here.
>
> And here I thought that
Am 24.10.2010 19:03, schrieb Graeme Geldenhuys:
> On 22 October 2010 20:20, Marco van de Voort wrote:
>>
>> Graeme's last mail where he explains he just wants to drop quick and dirty
>> patches AND IT IS FPC'S CORE TEAM JOB to make head or tails of it,
>> explains the fundamental misconception bett
On 22 October 2010 20:20, Marco van de Voort wrote:
>
> Graeme's last mail where he explains he just wants to drop quick and dirty
> patches AND IT IS FPC'S CORE TEAM JOB to make head or tails of it,
> explains the fundamental misconception better than I could do here.
And here I thought that is w
On 2010-10-24 13:15, Marco van de Voort wrote:
In our previous episode, Adem said:
But, I must say I am disappointed at the lack of management skills.
You should ask yourself how management skills work in a community where
nobody can force work on sb else.
It takes an infinite amount of patie
In our previous episode, Adem said:
> >>
> >> But, I must say I am disappointed at the lack of management skills.
> > You should ask yourself how management skills work in a community where
> > nobody can force work on sb else.
> >
> It takes an infinite amount of patience.
Yes. Forever, since it
14 matches
Mail list logo
