From: Sascha Kilian <sascha@sakisoft.de>
To: development@lists.ipfire.org
Subject: Question
Date: Fri, 15 Apr 2016 11:46:48 +0200 [thread overview]
Message-ID: <002601d196fb$bb1aaba0$315002e0$@sakisoft.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
Im sorry for my bad things,
i never have posted patches this way.
I hope my quality of patches going better and better :)
Can any tell me how i can provide the source-code of my patches?
The history of jabber tells me, that i am going wrong if i send the url only
in this list :(
Best regards,
Sascha
-----Ursprüngliche Nachricht-----
Von: Sascha Kilian [mailto:sascha(a)sakisoft.de]
Gesendet: Freitag, 15. April 2016 11:29
An: development(a)lists.ipfire.org
Cc: Sascha Kilian
Betreff: [PATCH] Update: man-pages to 4.05
Signed-off-by: Sascha Kilian <sascha(a)sakisoft.de>
---
lfs/man-pages | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/man-pages b/lfs/man-pages index 2ea81b3..8ad71ca 100644
--- a/lfs/man-pages
+++ b/lfs/man-pages
@@ -24,10 +24,10 @@
include Config
-VER = 2.34
+VER = 4.05
THISAPP = man-pages-$(VER)
-DL_FILE = $(THISAPP).tar.bz2
+DL_FILE = $(THISAPP).tar.xz
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = fb8d9f55fef19ea5ab899437159c9420
+$(DL_FILE)_MD5 = 9c32c8487d753f5894f6fba425b12add
install : $(TARGET)
@@ -69,7 +69,7 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
- @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)
+ @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar xf $(DIR_DL)/$(DL_FILE)
cd $(DIR_APP) && make $(MAKETUNING) $(EXTRA_MAKE)
cd $(DIR_APP) && make install
@rm -rf $(DIR_APP)
--
1.7.9.5
next reply other threads:[~2016-04-15 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 9:46 Sascha Kilian [this message]
[not found] <2d3f351d-66ac-4033-ac65-782be44f938a@email.android.com>
2016-04-15 11:12 ` Question Daniel Weismüller
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='002601d196fb$bb1aaba0$315002e0$@sakisoft.de' \
--to=sascha@sakisoft.de \
--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