[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: moving the project source to gitlab.com/libidn?
From: |
Tim Rühsen |
Subject: |
Re: moving the project source to gitlab.com/libidn? |
Date: |
Sun, 12 Mar 2017 19:37:49 +0100 |
User-agent: |
KMail/5.2.3 (Linux/4.9.0-2-amd64; KDE/5.28.0; x86_64; ; ) |
On Donnerstag, 9. März 2017 16:28:54 CET Simon Josefsson wrote:
> I like the idea. We should also make a new release shortly! Thanks for your
> work Tim and Nikos, I will try to review what's in master soon.
>
> /Simon
>
> Nikos Mavrogiannopoulos <address@hidden> skrev: (9 mars 2017
> 14:29:00 CET)
> >Hi,
> >
> > I've created the libidn group in gitlab.com in order to host the
> >
> >images used for the CI [0]. Does it make sense to move the source
> >code there as well, to avoid having the code in private repositories?
> >(in that case I'll leave the group and stay only in the build-images
> >repo).
> >
> >regards,
> >Nikos
> >
> >[0]. https://gitlab.com/libidn/build-images
I just exported libidn2 from 'jas' and imported it into group libidn.
IMO, next steps would be:
- change links from 'jas/libidn2' to 'libidn/libidn2' (also on Debian collab-
maint)
- remove make target 'check-coverage'
- add coverage output to gitlab web pages (https://about.gitlab.com/
2016/04/07/gitlab-pages-setup/)
Regards, Tim
signature.asc
Description: This is a digitally signed message part.