All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: drop quilt version 0.39
Date: Thu, 20 Dec 2007 12:34:43 +0100	[thread overview]
Message-ID: <476A5353.7040301@student.utwente.nl> (raw)
In-Reply-To: <fkdeel$p9o$1@ger.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rolf Leggewie schreef:
> Koen Kooi schrieb:
>>> driven by bug 1960, I have been doing some work on quilt in OE,
> 
>> What are your good reasons to drop it? I see no point in removing stuff
>> just to boost someones commit stats under the moniker "clean up"
> 

<snip usual rolf drivel>

> * had you bothered to look at the referenced bug you would have realized
>   that it was not really me proposing to drop it initially.

That is still no reason to drop it.

> * why keep old stuff (AKA cruft) longer than necessary?  Just so koen
>   can bully fellow contributors?

So vendor can keep using it without having check IRC every 5 minutes to
say "No, we still need it". To keep the work needed when merging
branches down to a minumum. To do regression testing. To do statistical
analysis on packages.

> * patches that apply fine to 0.45 and 0.46 don't apply cleanly to 0.39.
>   This somehow gets into the way of how I reworked it.

FILES_PATH and FILES_DIR both have ${PN}-${PV} overrides, so this is
still no reason to drop it.

> IMHO that suffices to drop it unless there is good reason to keep it.
> If there are, please state them. 

You're under the impression we actively delete 'old' stuff in OE, which
we don't, since we have vendors using the OE tree that aren't on IRC and
don't check this mailinglist regulary.

> And as you all know, OE is versioned
> so if anybody were to want it back anytime in the future mtn would
> gladly spew out the last known 0.39 version, I am sure.

This attitude is exactly why vendors have difficulty with OE.

Again, you must have good reasons for removing it, not have no reasons
to keep it.
And even if you have good reasons, you have to put it in removal.txt
first, with at least a month notice.
If the 1/4000th impact on parsing bothers you, we also have
packages/obsolete/.

This all applies to OE in general as well, so your recent deletion of
atk will probably need reverting as well.


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHalNTMkyGM64RGpERAiOyAKChC3aPIZZgEHO6PFLZTFPfbQw51wCdGLxD
Wzy5YcN0ttqe/UET4xrS/kc=
=ZSLV
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-12-20 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 23:27 RFC: drop quilt version 0.39 Rolf Leggewie
2007-12-20  8:24 ` Koen Kooi
2007-12-20  9:59   ` Rolf Leggewie
2007-12-20 11:34     ` Koen Kooi [this message]
2007-12-20 13:08   ` Paul Sokolovsky
2007-12-21  0:48     ` Robert Schuster
2007-12-21  1:15       ` Felix Fietkau
2007-12-21 12:14       ` Paul Sokolovsky
2007-12-21 14:45         ` Michael 'Mickey' Lauer
2008-01-14 23:19 ` Rolf Leggewie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=476A5353.7040301@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.