From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/pkgcore/snakeoil:master commit in: /
Date: Thu, 25 Jan 2024 15:41:44 +0000 (UTC) [thread overview]
Message-ID: <1706155312.85eb98f8a1ac763822e1819b81e00727a98d4612.arthurzam@gentoo> (raw)
commit: 85eb98f8a1ac763822e1819b81e00727a98d4612
Author: Brian Harring <ferringb <AT> gmail <DOT> com>
AuthorDate: Thu Jan 25 01:12:00 2024 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 25 04:01:52 2024 +0000
URL: https://gitweb.gentoo.org/proj/pkgcore/snakeoil.git/commit/?id=85eb98f8
History: add rev suppression for commits that bulk moved files.
The point here is to be able to pull the full history for a change
rather than losing the thread because folks moved files around. Some
of this code is old enough to vote, so knowing why something was done
back in py2.2 era matters.
This is also useful for un-obscuring some of the original authors for
double checking no major holder is being dropped.
Signed-off-by: Brian Harring <ferringb <AT> gmail.com>
.git-blame-ignore-revs | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/.git-blame-ignore-revs b/.git-blame-ignore-revs
index 1e4ba234..c2309bec 100644
--- a/.git-blame-ignore-revs
+++ b/.git-blame-ignore-revs
@@ -2,3 +2,9 @@
2fbaa7b40c7a6107d3c4b558324e9ba6e8ce1acc
# Reformat via black-23.1.0
266d2c7b8b975ccc6361eb47bcab7e73b578a1f6
+# tests being moved into tests/* layout
+69eb509bf9dad811fa7060807c2be4d0570bc7cc
+795d355af19a0440385070b3693b89da33f6e74c
+3db0d6447d8bd7e25bfdd97a31414ea44ef610bf
+# migration of code into src/* layout.
+7df0022b7ebd530a3287fa9677531c49237fba62
next reply other threads:[~2024-01-25 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:41 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-08 19:43 [gentoo-commits] proj/pkgcore/snakeoil:master commit in: / Arthur Zamarin
2024-01-26 19:50 Arthur Zamarin
2024-01-26 9:19 Arthur Zamarin
2024-01-25 15:41 Arthur Zamarin
2024-01-19 9:59 Arthur Zamarin
2023-12-22 15:04 Arthur Zamarin
2023-12-22 14:59 Arthur Zamarin
2023-03-24 10:55 Arthur Zamarin
2022-12-25 18:20 Arthur Zamarin
2022-12-25 18:11 Arthur Zamarin
2022-12-25 17:49 Arthur Zamarin
2022-12-09 13:50 Arthur Zamarin
2022-11-15 6:24 Arthur Zamarin
2022-11-08 19:22 Arthur Zamarin
2022-11-08 18:38 Arthur Zamarin
2022-11-08 18:38 Arthur Zamarin
2022-11-02 18:53 Arthur Zamarin
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=1706155312.85eb98f8a1ac763822e1819b81e00727a98d4612.arthurzam@gentoo \
--to=arthurzam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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