From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Cc: openezx-devel@lists.gnumonks.org
Subject: Re: [PATCH 01/12] fso-image.inc: add an even shorter alias, for ls -l
Date: Mon, 31 May 2010 13:19:30 +0200 [thread overview]
Message-ID: <hu0602$c6i$2@dough.gmane.org> (raw)
In-Reply-To: <1275299757-28908-2-git-send-email-ospite@studenti.unina.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 31-05-10 11:55, Antonio Ospite wrote:
> 'l' is a must have along with 'll'.
>
> Signed-off-by: Antonio Ospite <ospite@studenti.unina.it>
> ---
> recipes/images/fso-image.inc | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/recipes/images/fso-image.inc b/recipes/images/fso-image.inc
> index cc626f3..704d267 100644
> --- a/recipes/images/fso-image.inc
> +++ b/recipes/images/fso-image.inc
> @@ -110,6 +110,7 @@ fso_rootfs_postprocess() {
> echo "alias fso='cd /local/pkg/fso'" >>./etc/profile
> echo "alias ipkg='opkg'" >>./etc/profile
> echo "alias vim=vi" >>./etc/profile
> + echo "alias l='ls -l'" >>./etc/profile
> echo "alias ll='ls -al'" >>./etc/profile
> # nfs
> mkdir -p ./local/pkg
And what happens if you opkg upgrade base-files? You suddenly lost all
your tweaks to /etc/profile.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMA5tCMkyGM64RGpERAvTLAKCoiQEUoCu0JGj/uOrp7iyRxAMj6ACglhn0
PHnpQdgGf53SuA5JG1DDIiw=
=ZVr0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-31 11:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 9:55 [PATCH 00/12] motorola-ezx related changes Antonio Ospite
2010-05-31 9:55 ` [PATCH 01/12] fso-image.inc: add an even shorter alias, for ls -l Antonio Ospite
2010-05-31 11:19 ` Koen Kooi [this message]
2010-06-07 7:24 ` Antonio Ospite
2010-06-07 7:50 ` Martin Jansa
2010-06-07 7:54 ` Koen Kooi
2010-05-31 9:55 ` [PATCH 02/12] device_table-minimal.txt: fix input device nodes path Antonio Ospite
2010-05-31 9:55 ` [PATCH 03/12] device_table-ezx.txt: add needed device nodes Antonio Ospite
2010-05-31 9:55 ` [PATCH 04/12] xserver-kdrive-common/Xserver: fix EZX settings Antonio Ospite
2010-05-31 9:55 ` [PATCH 05/12] tslib: Add config file for a780 machine Antonio Ospite
2010-05-31 9:55 ` [PATCH 06/12] motorola-ezx-base.inc: use PREFERRED_PROVIDER_virtual/xserver Antonio Ospite
2010-05-31 9:55 ` [PATCH 07/12] motorola-ezx-base.inc: refresh machine definition Antonio Ospite
2010-05-31 11:18 ` Koen Kooi
2010-05-31 12:13 ` Antonio Ospite
2010-05-31 14:28 ` [PATCH 07/12 v2] " Antonio Ospite
[not found] ` <hu0ob2$ivu$1@dough.gmane.org>
2010-06-01 15:17 ` Antonio Ospite
2010-05-31 9:55 ` [PATCH 08/12] motorola-ezx-base.inc: Add support for ubifs Antonio Ospite
2010-05-31 9:55 ` [PATCH 09/12] openezx-kernel_git: update recipe Antonio Ospite
2010-05-31 9:55 ` [PATCH 10/12] ezx-gen-blob: bump SRCREV Antonio Ospite
2010-05-31 9:55 ` [PATCH 11/12] ezx-boot-usb-native: " Antonio Ospite
2010-05-31 9:55 ` [PATCH 12/12] frameworkd_git.bb: " Antonio Ospite
2010-05-31 10:20 ` [PATCH 00/12] motorola-ezx related changes Stefan Schmidt
2010-05-31 11:30 ` Holger Freyther
2010-05-31 12:07 ` Antonio Ospite
2010-05-31 12:09 ` Holger Freyther
2010-05-31 11:50 ` Dr. Michael Lauer
2010-05-31 14:11 ` Koen Kooi
2010-05-31 14:33 ` Antonio Ospite
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='hu0602$c6i$2@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openezx-devel@lists.gnumonks.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