Zarel wrote:
> 2008/11/16 Gerard Krol <[EMAIL PROTECTED]>:
>
>> The untested commit: after a careful reading of the code you conclude
>> that there possibly can't be any bugs left. Unfortunately a trivial bug
>> renders the entire program unusable. Better stay available to do
>> emergency fix-up
2008/11/16 Gerard Krol <[EMAIL PROTECTED]>:
> The untested commit: after a careful reading of the code you conclude
> that there possibly can't be any bugs left. Unfortunately a trivial bug
> renders the entire program unusable. Better stay available to do
> emergency fix-ups.
>
> (coloured cursors
The untested commit: after a careful reading of the code you conclude
that there possibly can't be any bugs left. Unfortunately a trivial bug
renders the entire program unusable. Better stay available to do
emergency fix-ups.
(coloured cursors anyone?)
Nice list. Now how to make sure people re
On Sun, Nov 16, 2008 at 12:05 PM, Per Inge Mathisen
<[EMAIL PROTECTED]> wrote:
> The commit flood: Having been bitten by the superhuman commit, you
> split your work instead into dozens if not hundreds of separate
> commits. Guaranteed to make anyone who tries to follow the commit log
> give up in
On Sun, Nov 16, 2008 at 12:14 PM, Kreuvf <[EMAIL PROTECTED]> wrote:
> How about copying it over to the Wiki?
If you find a good place for it, feel free.
- Per
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
How about copying it over to the Wiki?
- Kreuvf
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
There are various ways you should not commit things into a version
control system. Let's go through some of them:
The commit & run: "I have to go now or I'll be late for...", then you
commit today's work and bolt out the door. A sure way to see to that
your colleagues sit late or go home early, de
