Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] sstate-cache-management fixes
Date: Wed, 29 Jan 2014 22:03:38 +0100	[thread overview]
Message-ID: <cover.1391027849.git.Martin.Jansa@gmail.com> (raw)

The following changes since commit c3f3fed1b397b6ee6d44e7d39e63d084e4a88e30:

  toaster.bbclass: save original package name (2014-01-29 17:40:29 +0000)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib jansa/sstate-management
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/sstate-management

Martin Jansa (5):
  sstate-cache-management.sh: Fix remove_duplicated() to work after
    SSTATE_SWSPEC change
  sstate-cache-management.sh: Fix rm_by_stamps() to work after
    SSTATE_SWSPEC change
  sstate-cache-management.sh: Show total number of files when showing
    how many will be deleted
  sstate-cache-management.sh: Fix available architectures
  sstate-cache-management.sh: don't remove all packagedata sstate
    archives

 scripts/sstate-cache-management.sh | 99 +++++++++++++++++++++++++-------------
 1 file changed, 66 insertions(+), 33 deletions(-)

-- 
1.8.5.3



             reply	other threads:[~2014-01-29 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 21:03 Martin Jansa [this message]
2014-01-29 21:03 ` [PATCH 1/5] sstate-cache-management.sh: Fix remove_duplicated() to work after SSTATE_SWSPEC change Martin Jansa
2014-01-29 21:03 ` [PATCH 2/5] sstate-cache-management.sh: Fix rm_by_stamps() " Martin Jansa
2014-01-29 21:03 ` [PATCH 3/5] sstate-cache-management.sh: Show total number of files when showing how many will be deleted Martin Jansa
2014-01-29 21:03 ` [PATCH 4/5] sstate-cache-management.sh: Fix available architectures Martin Jansa
2014-01-29 21:03 ` [PATCH 5/5] sstate-cache-management.sh: don't remove all packagedata sstate archives Martin Jansa

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=cover.1391027849.git.Martin.Jansa@gmail.com \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox