public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Plattner <aplattner-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Aaron Plattner
	<aplattner-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: [PATCH tegra-uboot-flasher-scripts] README: use full file names for default.xml and default-notools.xml
Date: Tue, 11 Jun 2013 10:29:42 -0700	[thread overview]
Message-ID: <1370971782-25735-1-git-send-email-aplattner@nvidia.com> (raw)

Passing 'default' or 'default-notools' to repo init's -m parameter fails because
the manifests are actually called 'default.xml' and 'default-notools.xml'
respectively.

Signed-off-by: Aaron Plattner <aplattner-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
---
Repo sync failed when I tried to follow these instructions because these
manifest names don't exist.

 README-developer.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README-developer.txt b/README-developer.txt
index 46d3492..2525b40 100644
--- a/README-developer.txt
+++ b/README-developer.txt
@@ -51,15 +51,15 @@ repo init -u git://github.com/NVIDIA/tegra-uboot-flasher-manifests.git \
 repo sync
 
 There are two separate repo manifests for this project. Use repo's -m option
-to specify which you want. Valid values are default (all required
-dependencies) and default-notools (excludes the source to potentially distro-
-packaged utilities cbootimage, tegrarcm, dtc).
+to specify which you want. Valid values are default.xml (all required
+dependencies) and default-notools.xml (excludes the source to potentially
+distro-packaged utilities cbootimage, tegrarcm, dtc).
 
 Compiling Potentially Packaged Utilities
 ========================================
 
 If you have installed distro packages for the utilities mentioned above,
-and/or sync'd the default-notools manifest, skip this step.
+and/or sync'd the default-notools.xml manifest, skip this step.
 
 cd to the scripts sub-directory (i.e. the directory containing this README),
 and execute:
-- 
1.8.3

             reply	other threads:[~2013-06-11 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 17:29 Aaron Plattner [this message]
     [not found] ` <1370971782-25735-1-git-send-email-aplattner-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-11 17:34   ` [PATCH tegra-uboot-flasher-scripts] README: use full file names for default.xml and default-notools.xml Stephen Warren

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=1370971782-25735-1-git-send-email-aplattner@nvidia.com \
    --to=aplattner-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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