public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add profiling outputs to .gitignore
Date: Thu, 26 Dec 2019 06:53:00 -0000 [thread overview]
Message-ID: <cef2097a8731b04accf50d99c9b5a556cebd5f15@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT cef2097a8731b04accf50d99c9b5a556cebd5f15 ***
commit cef2097a8731b04accf50d99c9b5a556cebd5f15
Author: Christian Biesinger <cbiesinger@google.com>
AuthorDate: Thu Dec 19 15:19:26 2019 -0600
Commit: Christian Biesinger <cbiesinger@google.com>
CommitDate: Thu Dec 26 06:54:58 2019 +0100
Add profiling outputs to .gitignore
"perf record" creates files perf.data/perf.data.old; these can be safely
ignored in .gitignore, to avoid showing up in git status.
ChangeLog:
2019-12-26 Christian Biesinger <cbiesinger@google.com>
* .gitignore: Add perf.data and perf.data.old.
Change-Id: I214ae9d6b7265c2cb1356f11c9b0b82e2b391352
diff --git a/.gitignore b/.gitignore
index 4460159c84..356b2eb94b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -41,6 +41,9 @@ TAGS.sub
.gdbinit
.gdb_history
+perf.data
+perf.data.old
+
# ignore core files, but not java/net/protocol/core/
core
!core/
diff --git a/ChangeLog b/ChangeLog
index 8c60466345..2eeac27510 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2019-12-26 Christian Biesinger <cbiesinger@google.com>
+
+ * .gitignore: Add perf.data and perf.data.old.
+
2019-10-17 Sergio Durigan Junior <sergiodj@redhat.com>
* src-release.sh (GDB_SUPPORT_DIRS): Add libctf.
next reply other threads:[~2019-12-26 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 6:53 gdb-buildbot [this message]
2019-12-26 6:54 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-12-26 7:29 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-26 7:33 ` Failures on Fedora-i686, " gdb-buildbot
2019-12-26 7:40 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-26 7:42 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-12-26 8:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-12-26 8:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-26 8:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-26 8:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
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=cef2097a8731b04accf50d99c9b5a556cebd5f15@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-testers@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).