From: "Noé Rubinstein" <nrubinstein@aldebaran.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] fs/iso9660: remove obsolete code
Date: Mon, 19 Jan 2015 20:52:56 +0100 [thread overview]
Message-ID: <1421697177-12995-2-git-send-email-nrubinstein@aldebaran.com> (raw)
In-Reply-To: <1421697177-12995-1-git-send-email-nrubinstein@aldebaran.com>
This rule is superseded by a rule defined in fs/common.mk:
rootfs-$(1)-show-depends:
@echo $$(ROOTFS_$(2)_DEPENDENCIES)
Signed-off-by: No? Rubinstein <nrubinstein@aldebaran.com>
---
fs/iso9660/iso9660.mk | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fs/iso9660/iso9660.mk b/fs/iso9660/iso9660.mk
index 0c6e526..58e90c6 100644
--- a/fs/iso9660/iso9660.mk
+++ b/fs/iso9660/iso9660.mk
@@ -77,9 +77,6 @@ endif
rootfs-iso9660: $(BINARIES_DIR)/rootfs.iso9660
-rootfs-iso9660-show-depends:
- @echo $(ROOTFS_ISO9660_DEPENDENCIES)
-
################################################################################
#
# Toplevel Makefile options
--
2.1.4
Please ignore the below footer, which is of course irrelevant to this patch.
--
*This email and any attachment thereto are confidential and intended solely
for the use of the individual or entity to whom they are addressed.If you
are not the intended recipient, please be advised that disclosing, copying,
distributing or taking any action in reliance on the contents of this email
is strictly prohibited. In such case, please immediately advise the sender,
and delete all copies and attachment from your system.This email shall not
be construed and is not tantamount to an offer, an acceptance of offer, or
an agreement by Aldebaran Robotics on any discussion or contractual
document whatsoever. No employee or agent is authorized to represent or
bind Aldebaran Robotics to third parties by email, or act on behalf of
Aldebaran Robotics by email, without express written confirmation by
Aldebaran Robotics? duly authorized representatives.*
------------------------------
*Ce message ?lectronique et ?ventuelles pi?ces jointes sont confidentiels,
et exclusivement destin?s ? la personne ou l'entit? ? qui ils sont
adress?s.*
*Si vous n'?tes pas le destinataire vis?, vous ?tes pri? de ne pas
divulguer, copier, distribuer ou prendre toute d?cision sur la foi de ce
message ?lectronique. Merci d'en aviser imm?diatement l'exp?diteur et de
supprimer toutes les copies et ?ventuelles pi?ces jointes de votre syst?me.*
*Ce message ?lectronique n'?quivaut pas ? une offre, ? une acceptation
d?offre, ou ? un accord d'Aldebaran Robotics sur toute discussion ou
document contractuel quel qu?il soit, et ne peut ?tre interpr?t? comme tel.
Aucun employ? ou agent d?Aldebaran Robotics n'est autoris? ? repr?senter ou
? engager la soci?t? par email, ou ? agir au nom et pour le compte de la
soci?t? par email, sans qu?une confirmation ?crite soit donn?e par le
repr?sentant l?gal d?Aldebaran Robotics ou par toute autre personne ayant
re?u d?l?gation de pouvoir appropri?e.*
next prev parent reply other threads:[~2015-01-19 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 19:52 [Buildroot] [PATCH 1/3] fs/iso9660: allow building a hybrid ISO image Noé Rubinstein
2015-01-19 19:52 ` Noé Rubinstein [this message]
2015-01-26 22:27 ` [Buildroot] [PATCH 2/3] fs/iso9660: remove obsolete code Thomas Petazzoni
2015-01-19 19:52 ` [Buildroot] [PATCH 3/3] docs/manual/beyond-buildroot: building and testing live-CDs Noé Rubinstein
2015-02-02 20:40 ` Thomas De Schampheleire
2015-07-10 17:18 ` Thomas Petazzoni
2015-02-02 20:39 ` [Buildroot] [PATCH 1/3] fs/iso9660: allow building a hybrid ISO image Thomas De Schampheleire
2015-02-03 9:43 ` Noé RUBINSTEIN
2015-02-03 14:35 ` Thomas De Schampheleire
2015-02-02 21:13 ` Arnout Vandecappelle
2015-02-03 14:15 ` Arnout Vandecappelle
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=1421697177-12995-2-git-send-email-nrubinstein@aldebaran.com \
--to=nrubinstein@aldebaran.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.