specific guideline for KDE on Windows related commits?

[Roger Pixley]

I agree that those that are interesting should make it to the digest. I can
at least speak for myself that that audience I know of the commit digest
probably would not be all that interested in a build fix unless it was a
long standing issue. Perhaps we can start a collaborative document to put
together an Inclusion Guideline?

On Sat, Dec 11, 2010 at 8:38 AM, Alexander van Loon <
a.vanloon at alexandervanloon.nl> wrote:

> Sorry for flooding the mailing list, but I simply have a lot of
> questions. This one concerns the commits related to KDE on Windows. I’ve
> seen a lot of commits in the directory
> http://websvn.kde.org/trunk/kdesupport/emerge/portage/ during the
> reviewing process.
>
> I thought it was something Gentoo specific because of emerge and
> portage, but it appears that’s merely software which is used for the
> Windows build of KDE –
> http://websvn.kde.org/trunk/kdesupport/emerge/README?view=markup – but
> even so, I wasn’t sure if the nature of the commits was interesting
> enough in every case, most of the time they’re build fixes which don’t
> seem to be interesting at all.
>
> So I haven’t been consistent with including and excluding these commits.
> Can we reach an agreement on when to include or exclude them and
> formulate a guideline for the Inclusion Guidelines?
>
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/digest/attachments/20101212/fbe153b0/attachment-0001.htm