From: Murray.Jensen at csiro.au <Murray.Jensen@csiro.au>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix read-only "include/bmp_logo.h" after cvs checkout
Date: Thu, 30 Jun 2005 19:02:51 +1000 [thread overview]
Message-ID: <29594.1120122171@gerd> (raw)
The file "include/bmp_logo.h" is automatically generated during u-boot
build, but it is also present in the central CVS repository, and when
this file gets checked-out it is read-only. When the build reaches the
tools directory and trys to overwrite "include/bmp_logo.h" it fails,
and you have to change the write permissions and restart the build.
This patch removes any existing "include/bmp_logo.h" file before
generating the new one. Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen at csiro.au
To the extent permitted by law, CSIRO does not represent, warrant and/or
guarantee that the integrity of this communication has been maintained or
that the communication is free of errors, virus, interception or interference.
The information contained in this e-mail may be confidential or privileged.
Any unauthorised use or disclosure is prohibited. If you have received this
e-mail in error, please delete it immediately and notify Murray Jensen on
+61 3 9662 7763. Thank you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/x-patch
Size: 509 bytes
Desc: overwrite-logo-fix.patch
Url : http://lists.denx.de/pipermail/u-boot/attachments/20050630/dbd73b0b/attachment.bin
reply other threads:[~2005-06-30 9:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=29594.1120122171@gerd \
--to=murray.jensen@csiro.au \
--cc=u-boot@lists.denx.de \
/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.