From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 3/3] New package ncat (ncat is the new standard netcat) and change the build order of netcat
Date: Wed, 06 Apr 2016 22:03:25 +0100 [thread overview]
Message-ID: <1459976605.30749.373.camel@ipfire.org> (raw)
In-Reply-To: =?utf-8?q?=3C20160406165011=2EHorde=2E6KoWfa=5FjtzPkIe=5FzLnko8?= =?utf-8?q?=5Fp=40owncloud=2Ehelmsklamm=2Elocal=2Efamilyschlag=3E?=
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Yes, just change TARGET and you are fine :)
-Michael
On Wed, 2016-04-06 at 16:50 +0000, Jonatan Schlag wrote:
> Hi,
> I tested my second solution and the solution works perfectly :-)
>
> THISAPP = ncat-$(VER)
> DL_FILE = nmap-$(VER).tar.bz2 # name of the download file
> DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/nmap-$(VER) #name of the directory in the tarball
> TARGET = $(DIR_INFO)/ncat-$(VER) # name of the logfile
>
> I will send a new patch for this today or tomorrow.
>
> Regards Jonatan
>
> PS.: The comments are for me. I have to write a little bit
> documentation about this, although I will forget everything. In this
> Mail, they are safe till I write the documentation.
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-04-06 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 21:03 Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-06 16:50 Jonatan Schlag
2016-04-04 15:19 Libvirt and Ncat/Netcat Jonatan Schlag
2016-04-04 15:19 ` [PATCH 3/3] New package ncat (ncat is the new standard netcat) and change the build order of netcat Jonatan Schlag
2016-04-05 22:09 ` Michael Tremer
2016-04-06 10:26 ` Jonatan Schlag
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=1459976605.30749.373.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