and to also separate their commits, in order words don't do one commit
containing multiple things like a bugfix and a feature... make them into 2
commits.
On Sun, Jan 13, 2008 at 12:05:01AM +0100, Harry Vennik wrote:
> I agee to that. As we have to use the 0_97 branch anyway (and we do),
> why
I agee to that. As we have to use the 0_97 branch anyway (and we do),
why not skip the MSNP15-related commits... That means less work and a
better bugfix release!
Anyway, everyone should take care to have real descriptive commit
messages, it will be easier then to select which commits should
The branch is here
We only have to merge changes applied to the trunk to it
In fact I hope we will do 0.97.1 without any P15 code !
Phil
Youness Alaoui a écrit :
> Can be done, but we can also do it later...
> basically, why later.. only because the more I wait, the more chance someone
> else
Can be done, but we can also do it later...
basically, why later.. only because the more I wait, the more chance someone
else will do this boring task... lol
no seriously, the reason is because if we have two branches now, we'll have to
commit in both branches, which is difficult/complicated/blab
Why not branch now? Then new features can go to trunk, bug fixes go on
the 0.97.1 branch?
On 12 Jan 2008, at 20:26, Youness Alaoui wrote:
> I don't agree
> well.. I don't like the idea because we want to have a bugfix
> release, and I don't want new features in...
> The MSNP15 was ok beca
I don't agree
well.. I don't like the idea because we want to have a bugfix release, and I
don't want new features in...
The MSNP15 was ok because everything was inside an 'if [config::getKey
protocol] == 15' so it wouldn't affect anything else.
But now, you're already working on it, and s
