Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Seeking Ubuntu PPA Maintainer
Date: Wed, 16 Nov 2016 12:10:21 +0100	[thread overview]
Message-ID: <c5b6cb19-32b8-7f7c-f3f0-ac542579917a@eggiecode.org> (raw)
In-Reply-To: <87lgwj9b43.fsf@alice.fifthhorseman.net>

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

Hey Deniel,

Thank your for the support.

I was search for the git repo of the debian package, thank you for the link.
Besides that only difference between ours repo's is that I use a 
submodule for the wireguard source.

Git repo: https://git.launchpad.net/wireguard?h=master

Greetz,
Egbert

On 2016-11-16 07:45, Daniel Kahn Gillmor wrote:
> Hi Egbert--
>
> On Wed 2016-11-16 09:34:12 +0900, Egbert Verhage wrote:
>> I just copyed the debian folder of the experimental package of the
>> debian repo.
> I'm the package maintainer in debian.  Glad to hear that my packaging
> work has been useful for you.
>
> If you're tracking the debian packaging, you might also be interested in
> the revision control history of it:
>
>      git clone https://anonscm.debian.org/git/collab-maint/wireguard.git
>
> If you find that there are specific changes to the debian packaging that
> you find useful when packaging for ubuntu, i'd be happy to hear about
> them.  Also, if you run into packaging difficulties and want someone to
> brainstorm with, feel free to reach out.
>
> Regards,
>
>          --dkg


[-- Attachment #2: Type: text/html, Size: 2018 bytes --]

  reply	other threads:[~2016-11-16 11:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 20:44 Jason A. Donenfeld
2016-11-15 23:41 ` Egbert Verhage
     [not found] ` <454ad249-3313-9423-c2d4-7602d56849fc@eggiecode.org>
2016-11-16  0:12   ` Jason A. Donenfeld
2016-11-16  0:34     ` Egbert Verhage
2016-11-16  1:31       ` Jason A. Donenfeld
2016-11-16  6:20         ` Dan Luedtke
2016-11-16 11:18           ` Egbert Verhage
2016-11-16 11:34             ` Dan Lüdtke
2016-11-16 14:04               ` Jason A. Donenfeld
2016-11-16 10:03         ` Egbert Verhage
2016-11-16 14:09           ` Jason A. Donenfeld
2016-11-16 14:22             ` Egbert Verhage
2016-11-16 14:25               ` Jason A. Donenfeld
2016-11-16  6:45       ` Daniel Kahn Gillmor
2016-11-16 11:10         ` Egbert Verhage [this message]
2016-11-16 14:24           ` Jason A. Donenfeld
2016-11-16 22:17             ` Daniel Kahn Gillmor
2016-11-16 22:52               ` Jason A. Donenfeld
2016-11-16 14:11 ` Jason A. Donenfeld
2016-11-16 14:37 Anonymous Anonymous
2016-11-16 15:00 ` Jason A. Donenfeld
2016-11-16 15:08   ` Egbert Verhage
2016-11-16 14:47 Anonymous Anonymous

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=c5b6cb19-32b8-7f7c-f3f0-ac542579917a@eggiecode.org \
    --to=egbert@eggiecode.org \
    --cc=Jason@zx2c4.com \
    --cc=dkg@fifthhorseman.net \
    --cc=wireguard@lists.zx2c4.com \
    /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;
as well as URLs for NNTP newsgroup(s).