public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/27803] doc/SystemTap_Tapset_Reference/tapsets.pdf is removed during cleaning but not rebuilt
Date: Wed, 06 Dec 2023 21:42:22 +0000	[thread overview]
Message-ID: <bug-27803-6586-KgivKNkvSn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27803-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27803

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |wcohen at redhat dot com

--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
This should be addressed by the following commit:

commit ec6c1f93353e5a0f095943bc8bfe3c7749b9c9b7 (HEAD -> master)
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Dec 6 16:36:42 2023 -0500

    PR27803: Do not remove doc/SystemTap_Tapset_Reference/tapsets.pdf

    The "make clean" would remove tapsets.pdf and the "make" does
    not rebuild it.  tapsets.pdf is built using some other scripts
    and is checked into the SystemTap git repository.  Changing
    the Makefile.am and Makefile.in to avoid removing tapsets.pdf

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2023-12-06 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 22:26 [Bug documentation/27803] New: " ddstreet at canonical dot com
2023-12-06 21:42 ` wcohen at redhat dot com [this message]

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=bug-27803-6586-KgivKNkvSn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).