All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: Package Maintenance
Date: Tue, 24 Mar 2009 14:59:03 -0500	[thread overview]
Message-ID: <49C93B87.40607@dls.net> (raw)
In-Reply-To: <ac9c93b10903241136q779fe115sa595c31200b707c6@mail.gmail.com>

Frans Meulenbroeks wrote:
> Disadvantage of a Maintainers file is that it is yet another file to
> update when you create a package (adjacent to the checksums file and
> of course the package recipe). Guess it will be forgotten regularly.
> 
> Also I fear we're going to end up with a lot of orphaned packages.

Is lack of a Maintainers file _really_ our problem?

IMO, our current issue is what I would term "Drive-by Commits" (for
example, the past two weekends have seen commits that have introduced
major breakage of some sort where the committer has not been about for
some fairly significant period of time.

I don't think listing a name in a Maintainers file is going to change
anything, frankly.

Mike (mwester)



      parent reply	other threads:[~2009-03-24 20:00 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17 19:18 Package Maintenance Chris Larson
2009-03-17 19:25 ` Koen Kooi
2009-03-17 19:32   ` Chris Larson
2009-03-17 19:43   ` Frans Meulenbroeks
2009-03-23 20:35 ` Chris Larson
2009-03-24  9:06   ` Richard Purdie
2009-03-24 15:08     ` Chris Larson
2009-03-24 18:36       ` Frans Meulenbroeks
2009-03-24 18:54         ` Tom Rini
2009-03-24 18:55         ` Chris Larson
2009-03-24 19:14           ` Koen Kooi
2009-03-24 19:24             ` Chris Larson
2009-03-24 19:50               ` Tom Rini
2009-03-24 19:59                 ` Chris Larson
2009-03-24 18:56         ` Junqian Gordon Xu
2009-03-24 19:05           ` Chris Larson
2009-03-24 19:19             ` Junqian Gordon Xu
2009-03-24 19:29               ` Philip Balister
2009-03-24 19:51                 ` Tim Ellis
2009-03-24 20:01                   ` Chris Larson
2009-03-24 20:16                     ` Koen Kooi
2009-03-24 20:30                     ` Lon Lentz
2009-03-24 20:44                       ` Junqian Gordon Xu
2009-03-25  8:51                         ` Frans Meulenbroeks
2009-03-25 11:03                           ` Koen Kooi
2009-03-25 13:36                             ` Richard Purdie
2009-03-25 14:16                               ` Holger Schurig
2009-03-25 14:40                                 ` Richard Purdie
2009-03-25 15:32                                 ` Holger Schurig
2009-03-25 14:26                               ` Otavio Salvador
2009-03-25 16:05                             ` Mike (mwester)
2009-03-25 16:20                               ` Koen Kooi
2009-03-25 18:03                                 ` Jeremy Lainé
2009-03-25 18:22                                   ` Koen Kooi
2009-03-25 18:13                                 ` Mike (mwester)
2009-03-25 22:07                                 ` Frans Meulenbroeks
2009-03-25 22:27                                   ` Jeremy Lainé
2009-03-25 23:54                                     ` Mike (mwester)
2009-03-27  9:22                                       ` Richard Purdie
2009-03-24 19:59         ` Mike (mwester) [this message]

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=49C93B87.40607@dls.net \
    --to=mwester@dls.net \
    --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.