All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][daisy][PATCH] qt5-git.inc: Move to code.qt.io
Date: Fri, 13 Mar 2015 14:50:46 +0100	[thread overview]
Message-ID: <20150313135046.GC2345@jama> (raw)
In-Reply-To: <1426231791-25435-1-git-send-email-erik.boto@pelagicore.com>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

On Fri, Mar 13, 2015 at 08:29:51AM +0100, Erik Botö wrote:
> Gitorious switch of git:// protocol and will close down in a while, so
> move over to code.qt.io.

This isn't enough.. I'll cherry-pick commit from master instead.

> Signed-off-by: Erik Botö <erik.boto@pelagicore.com>
> ---
>  recipes-qt/qt5/qt5-git.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-qt/qt5/qt5-git.inc b/recipes-qt/qt5/qt5-git.inc
> index fa0c06e..2281b75 100644
> --- a/recipes-qt/qt5/qt5-git.inc
> +++ b/recipes-qt/qt5/qt5-git.inc
> @@ -5,7 +5,7 @@ QT_MODULE_BRANCH ?= "stable"
>  
>  # each module needs to define valid SRCREV
>  SRC_URI += " \
> -    git://qt.gitorious.org/qt/${QT_MODULE}.git;branch=${QT_MODULE_BRANCH} \
> +    git://code.qt.io/qt/${QT_MODULE}.git;branch=${QT_MODULE_BRANCH} \
>  "
>  
>  S = "${WORKDIR}/git"
> -- 
> 2.1.4
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-03-13 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  7:29 [meta-qt5][daisy][PATCH] qt5-git.inc: Move to code.qt.io Erik Botö
2015-03-13 13:50 ` Martin Jansa [this message]
2015-03-13 14:21   ` Erik Botö

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=20150313135046.GC2345@jama \
    --to=martin.jansa@gmail.com \
    --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 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.