Andrew D Kirch a écrit :
Here's the script that I used to generate this. I have not manually
reviewed all of thousands of patches to determine the unique situation
of each patch, however I would like a suggestion on how to demonstrate
_real_ statistics short of auditing each and every patch
Santiago M. Mola wrote:
I think that's all we need in order to know how were things when the
patch was added and if it needs to be pushed/tracked upstream, removed
in the next version of the package, etc.
Some of us already put these kind of headers, or at least an URL to
upstream bug or a
On Tue, Aug 19, 2008 at 12:02 AM, Tobias Scherbaum
[EMAIL PROTECTED] wrote:
Santiago M. Mola wrote:
However, tracking the status of every patch since its inclusion in
portage until it's removed would be a huge work overhead... and I
doubt it's worthy.
I don't think it's a huge work
Santiago M. Mola wrote:
On Tue, Aug 19, 2008 at 12:02 AM, Tobias Scherbaum
[EMAIL PROTECTED] wrote:
Santiago M. Mola wrote:
However, tracking the status of every patch since its inclusion in
portage until it's removed would be a huge work overhead... and I
doubt it's worthy.
I
Andrew D Kirch wrote:
Denis Dupeyron wrote:
On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch [EMAIL PROTECTED]
wrote:
[...]
Looks like you counted the number of files in the files/
subdirectories. Not all of these are patches. Also, you probably
forgot to count seds, as some of us use sed more
Andrew D Kirch wrote:
Obviously the software needs to work, and therefore we need patches, but
Gentoo has not done enough to date to get them pushed upstream. Lets
look at some cringeworthy statistics on outstanding patches.
Have you even _looked_ at the patches? Can you tell which ones are :
On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch [EMAIL PROTECTED] wrote:
[...]
Looks like you counted the number of files in the files/
subdirectories. Not all of these are patches. Also, you probably
forgot to count seds, as some of us use sed more than patches.
Oh, and like Jeremy was hinting,
Andrew D Kirch wrote:
[...patches...]
Common practice is to work with upstream (if alive) and have the patches
merged asap. Nothing _that_ strange IMHO.
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
On Thu, Aug 14, 2008 at 12:00 AM, Andrew D Kirch [EMAIL PROTECTED] wrote:
Jeremy Olexa wrote:
Andrew D Kirch wrote:
snip all
Good points, I take it that you have found a mentor and are becoming a dev
to drive this project then?
-Jeremy
I've spoken in the past with both Elfyn McBratney,
On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch [EMAIL PROTECTED] wrote:
Patches in the metadata.xml should have some sort of status tracking for
each patch, repoman should flag any that don't, and warn on any that have
not been submitted upstream unless the status is signed off on by a herd
Am Donnerstag, 14. August 2008 17:24:41 schrieb Santiago M. Mola:
On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch [EMAIL PROTECTED] wrote:
Patches in the metadata.xml should have some sort of status tracking for
each patch, repoman should flag any that don't, and warn on any that have
not
Rémi Cardona wrote:
Andrew D Kirch wrote:
Obviously the software needs to work, and therefore we need patches, but
Gentoo has not done enough to date to get them pushed upstream. Lets
look at some cringeworthy statistics on outstanding patches.
Have you even _looked_ at the patches? Can you
Denis Dupeyron wrote:
On Thu, Aug 14, 2008 at 4:17 AM, Andrew D Kirch [EMAIL PROTECTED] wrote:
[...]
Looks like you counted the number of files in the files/
subdirectories. Not all of these are patches. Also, you probably
forgot to count seds, as some of us use sed more than patches.
Oh, and
On Fri, Aug 15, 2008 at 12:55:12AM -0400, Andrew D Kirch wrote:
Here's the script that I used to generate this. I have not manually
reviewed all of thousands of patches to determine the unique situation of
each patch, however I would like a suggestion on how to demonstrate _real_
It has become abundantly clear that distribution maintainers should have
as few patches as possible. Patches waste time due to duplicate work,
resources (portage disk space and bandwidth), and as the Debian project
recently found out after a major vulnerability was discovered in the
OpenSSH
Andrew D Kirch wrote:
snip all
Good points, I take it that you have found a mentor and are becoming a
dev to drive this project then?
-Jeremy
16 matches
Mail list logo
