From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] mango-lassi: Typo. s/ESCRIPTION/DESCRIPTION/
Date: Mon, 14 Mar 2011 20:28:26 -0400 [thread overview]
Message-ID: <20110315002826.GA29374@denix.org> (raw)
In-Reply-To: <1300148053.3828.9.camel@mattotaupa>
On Tue, Mar 15, 2011 at 01:14:13AM +0100, Paul Menzel wrote:
> Date: Fri, 18 Feb 2011 00:32:01 +0100
>
>
> Signed-off-by: Paul Menzel <paulepanter@users.sourceforge.net>
> ---
> Dear OE folks,
>
>
> before I push this, could you please tell me, if a PR bump is needed.
>
> I would say yes, since the description gets included in the package?
Makes sense to bump the PR, so binary feeds get updated with the correct
package containing proper description.
--
Denys
> [1] http://www.openembedded.org/index.php/When_To_Bump_PR
> ---
> recipes/avahi/mango-lassi_git.bb | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/recipes/avahi/mango-lassi_git.bb b/recipes/avahi/mango-lassi_git.bb
> index c2250d8..a1a4117 100644
> --- a/recipes/avahi/mango-lassi_git.bb
> +++ b/recipes/avahi/mango-lassi_git.bb
> @@ -1,4 +1,4 @@
> -ESCRIPTION = "Input sharing, the avahi way"
> +DESCRIPTION = "Input sharing, the avahi way"
> DEPENDS = "avahi-ui libglade libnotify"
>
> SRCREV = "73638817126a68d62f1233f6e6859ce75a259e93"
> --
> 1.7.4.1
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2011-03-15 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 0:14 [PATCH] mango-lassi: Typo. s/ESCRIPTION/DESCRIPTION/ Paul Menzel
2011-03-15 0:28 ` 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=20110315002826.GA29374@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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