All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] buildhistory.bbclass: Fix hostname print for 'No changes' case
Date: Thu, 18 Oct 2012 13:59:31 -0700	[thread overview]
Message-ID: <50806DB3.6050705@linux.intel.com> (raw)
In-Reply-To: <1349992001-3965-1-git-send-email-otavio@ossystems.com.br>

On 10/11/2012 02:46 PM, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   meta/classes/buildhistory.bbclass |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/buildhistory.bbclass b/meta/classes/buildhistory.bbclass
> index 49f2ea5..0a5753f 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -403,9 +403,9 @@ END
>   		fi
>   		# Check if there are new/changed files to commit (other than metadata-revs)
>   		repostatus=`git status --porcelain | grep -v " metadata-revs$"`
> +		HOSTNAME=`hostname 2>/dev/null || echo unknown`
>   		if [ "$repostatus" != "" ] ; then
>   			git add .
> -			HOSTNAME=`hostname 2>/dev/null || echo unknown`
>   			# porcelain output looks like "?? packages/foo/bar"
>   			# Ensure we commit metadata-revs with the first commit
>   			for entry in `echo "$repostatus" | awk '{print $2}' | awk -F/ '{print $1}' | sort | uniq` ; do
>
Merged into OE-Core

Thanks
	Sau!




  reply	other threads:[~2012-10-18 21:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 21:46 [PATCH] buildhistory.bbclass: Fix hostname print for 'No changes' case Otavio Salvador
2012-10-18 20:59 ` Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-16  3:45 Otavio Salvador

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=50806DB3.6050705@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.