All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [oe-layersetup][PATCH 0/5] RFC: cleanup and remove	denzil configs
Date: Thu, 24 Apr 2014 13:10:41 -0400	[thread overview]
Message-ID: <20140424171041.GS18053@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C68D7F2@DFLE08.ent.ti.com>

On Wed, Apr 23, 2014 at 08:30:04PM +0000, Cooper Jr., Franklin wrote:
> > -----Original Message-----
> > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-
> > bounces@arago-project.org] On Behalf Of Denys Dmytriyenko
> > Sent: Wednesday, April 23, 2014 2:42 PM
> > To: meta-arago@arago-project.org
> > Subject: [meta-arago] [oe-layersetup][PATCH 0/5] RFC: cleanup and remove
> > denzil configs
> > 
> > From: Denys Dmytriyenko <denys@ti.com>
> > 
> > RFC: Remove some cruft of old denzil configs.
> > 
> > I would have left amsdk* and mcsdk* configs alone, if they didn't reference
> > other config files in sample-files/, which I would like to clean up mostly.

> [Franklin] So how about subdirectories in sample-files for each maintenance 
> branch?

Ok, I'll see what I can do...


> I wouldn't mind deleting the generic arago config files from old maintenance 
> branches since most of the time people really care about the sdk specific 
> config files.

Depends on people...


> > This repository is not tagged, but used as a BOM-reference for old release
> > configs. Do we need to preserve those files some other place?
> > 
> > Other alternatives for preserving the configs are:
> > * in a separate "old/deprecated" branch
> > * in a sub-directory of a similar name
> > * tagging the repo before removal

> [Franklin] I envisioned oe-layersetup as a way that you can simply rebuild 
> any sdk no matter how old by simply swapping out config files. So I would 
> prefer a sub-directory approach instead of a branch or tagging approach 
> since that will add complexity for users.
> > 
> > Denys Dmytriyenko (5):
> >   bblayers-denzil: remove denzil-specific bblayers file, deprecated
> >   local-arago-linaro.conf: remove denzil-specific version setting Linaro
> >     TC
> >   mcsdk-03.00.00.xx: remove old denzil-based configs
> >   arago-denzil-config: remove denzil-specific config
> >   amsdk-05.06.00.00: remove denzil-specific config
> > 
> >  configs/amsdk/amsdk-05.06.00.00-config.txt  |  10 --
> >  configs/arago-denzil-config.txt             |  11 --
> >  configs/mcsdk/mcsdk-03.00.00.03-config.txt  |  10 --  configs/mcsdk/mcsdk-
> > 03.00.00.05-config.txt  |  11 --  configs/mcsdk/mcsdk-03.00.00.06-config.txt  |
> > 11 --  configs/mcsdk/mcsdk-03.00.00.07-config.txt  |  11 --
> >  sample-files/bblayers-denzil.conf.sample    |   9 --
> >  sample-files/local-arago-linaro.conf.sample | 160 ----------------------------
> >  8 files changed, 233 deletions(-)
> >  delete mode 100644 configs/amsdk/amsdk-05.06.00.00-config.txt
> >  delete mode 100644 configs/arago-denzil-config.txt  delete mode 100644
> > configs/mcsdk/mcsdk-03.00.00.03-config.txt
> >  delete mode 100644 configs/mcsdk/mcsdk-03.00.00.05-config.txt
> >  delete mode 100644 configs/mcsdk/mcsdk-03.00.00.06-config.txt
> >  delete mode 100644 configs/mcsdk/mcsdk-03.00.00.07-config.txt
> >  delete mode 100644 sample-files/bblayers-denzil.conf.sample
> >  delete mode 100644 sample-files/local-arago-linaro.conf.sample
> > 
> > --
> > 1.9.2
> > 
> > _______________________________________________
> > meta-arago mailing list
> > meta-arago@arago-project.org
> > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


      reply	other threads:[~2014-04-24 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 19:42 [oe-layersetup][PATCH 0/5] RFC: cleanup and remove denzil configs Denys Dmytriyenko
2014-04-23 19:42 ` [oe-layersetup][PATCH 1/5] bblayers-denzil: remove denzil-specific bblayers file, deprecated Denys Dmytriyenko
2014-04-23 19:42 ` [oe-layersetup][PATCH 2/5] local-arago-linaro.conf: remove denzil-specific version setting Linaro TC Denys Dmytriyenko
2014-04-23 19:42 ` [oe-layersetup][PATCH 3/5] mcsdk-03.00.00.xx: remove old denzil-based configs Denys Dmytriyenko
2014-04-23 19:42 ` [oe-layersetup][PATCH 4/5] arago-denzil-config: remove denzil-specific config Denys Dmytriyenko
2014-04-23 19:42 ` [oe-layersetup][PATCH 5/5] amsdk-05.06.00.00: " Denys Dmytriyenko
2014-04-23 20:30 ` [oe-layersetup][PATCH 0/5] RFC: cleanup and remove denzil configs Cooper Jr., Franklin
2014-04-24 17:10   ` Denys Dmytriyenko [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=20140424171041.GS18053@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.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.