should commits in "/branches/KDE/4.6/" be picked?

[Marco Krohn]

Hi,

The second Release Candidate of 4.6 was announced recently; thus only
critical fixes are allowed. I would assume that all fixes to 4.6 will
be fixed in trunk, as well. In my opinion it is just fine to insert
the branch commit in case you do not find the trunk equivalent.

Good to see that so much work on the Commit Digest happens.... great
job everyone!

best regards,
  Marco

On Fri, Jan 14, 2011 at 9:55 PM, Vladislav Blanton <vblanton at gmail.com> wrote:
> Hello all,
>
> I am a little confused about commits in "/branches/KDE/4.6/"
>
> 4.6 hasn't been released yet, and so they don't always seem to be
> backports, but sometimes they are.
>
> Is it o.k. to add the most interesting last-minute fixes to this
> branch, or should we always look for the /trunk/ equivalent?
>
> V
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest
>