public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Indu Bhagat <indu.bhagat@oracle.com>
To: binutils@sourceware.org
Cc: Indu Bhagat <indu.bhagat@oracle.com>
Subject: [COMMITTED] Upload SFrame spec files as well
Date: Fri, 20 Jan 2023 11:18:42 -0800	[thread overview]
Message-ID: <20230120191842.3799467-1-indu.bhagat@oracle.com> (raw)

This patch was pre-approved earlier, and has now been committed to master
branch.

Thanks

------------------------------------------

binutils/
	* README-how-to-make-a-release: Include sframe-spec html and pdf
	files.
---
 binutils/README-how-to-make-a-release | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index ccac8a6610b..e488c0700d4 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -310,7 +310,7 @@ When the time comes to actually make the release....
         make install-gas install-gold install-ld install-binutils install-gprofng
 
         # Needed for step 29...
-        make html pdf html-libctf pdf-libctf
+	make html pdf html-libctf pdf-libctf html-libsframe pdf-libsframe
 
         popd
 
@@ -434,6 +434,10 @@ When the time comes to actually make the release....
 	 lcd ../../libctf/doc
 	 put ctf-spec.html
 	 put ctf-spec.pdf
+
+	 lcd ../../libsframe/doc
+	 put sframe-spec.html
+	 put sframe-spec.pdf
 	 
       Edit the top level binutils index.html file to change the links
       to point to the new documentation.
-- 
2.39.0


                 reply	other threads:[~2023-01-20 19:18 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=20230120191842.3799467-1-indu.bhagat@oracle.com \
    --to=indu.bhagat@oracle.com \
    --cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).