public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] ding-libs: Update to 0.6.1
Date: Thu, 12 Oct 2017 10:49:34 +0100	[thread overview]
Message-ID: <1507801774.4045.81.camel@ipfire.org> (raw)
In-Reply-To: <20171012090036.17843-1-stefan.schantl@ipfire.org>

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

Hi,

it would have been better to have this sent together with sssd in a patch set.

I merged it this time.

Best,
-Michael

On Thu, 2017-10-12 at 11:00 +0200, Stefan Schantl wrote:
> This is a minor update to the latest available version of the
> ding-libs.
> 
> * Adjust project and source URL
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
>  ding-libs/ding-libs.nm | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/ding-libs/ding-libs.nm b/ding-libs/ding-libs.nm
> index 51e9736..213d7a4 100644
> --- a/ding-libs/ding-libs.nm
> +++ b/ding-libs/ding-libs.nm
> @@ -4,11 +4,11 @@
>  #############################################################################
> ##
>  
>  name       = ding-libs
> -version    = 0.6.0
> +version    = 0.6.1
>  release    = 1
>  
>  groups     = System/Libraries
> -url        = http://fedorahosted.org/sssd/
> +url        = https://pagure.io/SSSD/ding-libs
>  license    = GPLv3+
>  summary    = "Ding is not GLib" assorted utility libraries.
>  
> @@ -16,7 +16,7 @@ description
>  	A set of helpful libraries used by projects such as SSSD.
>  end
>  
> -source_dl  = http://fedorahosted.org/releases/d/i/ding-libs/
> +source_dl  = https://releases.pagure.org/SSSD/ding-libs/
>  
>  build
>  	configure_options += \

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-10-12  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  9:00 Stefan Schantl
2017-10-12  9:49 ` Michael Tremer [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=1507801774.4045.81.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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