Hi,
> In short: committing to trunk is enough. :)
Thanks Mr. Kügler !! :P
Regards,
Rafael Fernández López.
signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/ma
On Tuesday 02 December 2008 17:27:45 Rafael Fernández López wrote:
> > Why would you want to backport patches to a tag? It's either branch/
> > (4.1.x) or trunk (next release of that is beta2). Tags are not supposed
> > to change after a release, which for 4.1.80 a.k.a beta1 has happened :).
>
> Be
On 02.12.08 17:27:45, Rafael Fernández López wrote:
> Hi,
>
> > Why would you want to backport patches to a tag? It's either branch/
> > (4.1.x) or trunk (next release of that is beta2). Tags are not supposed to
> > change after a release, which for 4.1.80 a.k.a beta1 has happened :).
>
> Because
Hi,
> Why would you want to backport patches to a tag? It's either branch/
> (4.1.x) or trunk (next release of that is beta2). Tags are not supposed to
> change after a release, which for 4.1.80 a.k.a beta1 has happened :).
Because I want it to be on the 4.2 branch that will be created from the 4
On Tuesday 02 December 2008 02:08:20 Rafael Fernández López wrote:
> I have tried to backport some patches that were going to be useful while I
> found out that I had no karma to commit on tags.
Why would you want to backport patches to a tag? It's either branch/ (4.1.x)
or trunk (next release of
Hi there,
I have tried to backport some patches that were going to be useful while I
found out that I had no karma to commit on tags.
I am placing patches here, with the explanation:
backport.diff:
This patch corresponds to revisions 891277, 891278, 891359 and 891377 in
trunk.
The aiming of
