From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/brauner/xfstests-dev
Date: Thu, 11 Mar 2021 08:17:15 -0000 [thread overview]
Message-ID: <161545063557.31813.10521616396072747697@gitolite.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
---
service: git-receive-pack
repo: pub/scm/linux/kernel/git/brauner/xfstests-dev
user: brauner
changes:
- ref: refs/heads/idmapped_mounts
old: 27712465751576c20fd378cfb35efc7f120f0658
new: e1ea7401a8279bd3f5256d972dfe1e6ed2eff7b1
log: revlist-277124657515-e1ea7401a827.txt
[-- Attachment #2: revlist-277124657515-e1ea7401a827.txt --]
[-- Type: text/plain, Size: 1925 bytes --]
2d4fb6bb3078547be73abf4f9913c20813c1e467 config: wrap xfs_metadump as $XFS_METADUMP_PROG like the other tools
5baeea6fe8c216debd3b05426e6907ec509bf52b check: allow '-e testid' to exclude a single test
3d79e8ea242462f8555455318147e662048b306c check: don't abort on non-existent excluded groups
49c09b5bad5effab656eb3dba1dc2df1f56a3ed9 check: run tests in exactly the order specified
656e1b10820d9f05cfecf90f79d91c78cb77b0ae fuzzy: capture core dumps from repair utilities
bdad282d47daddc0f2f7f18f30bd25a636535de4 btrfs: clone a hole post eof when using NO_HOLES feature
46f896c0a55d4fd979f473dcd5742f67746e66ec btrfs: make sure we rescan all devices after unregistering
9b298bdf540f29a0571998dfd150dc614ef7f34b check: add CLI option to repeat and stop tests in case of failure
8fe4fdf8ca22c8194889def2378bf20406af1f13 fstests: remove _require_no_rtinherit completely
71636cfbaf358931012d94fbaeed53ddfa6cea7d generic/623: don't fail on core dumps
5c076a5adbd15dc06128d7eea2747677b5eba704 xfs/271: fix test failure on non-reflink filesystems
e05491b34134f37e0e6f20b50b58014c4ec7b70d common/rc: fix detection of device-mapper/persistent memory incompatibility
976ca65307d2f0d16acb523833d15437bd0349f8 generic/60[78]: ensure the initial DAX file flag state before test
c363e7a1fca59895520b2747c5d0ffc43d181950 generic: factor out helpers for fs-verity built-in signatures
45495efc38292e7f121e3e6f28720ca7800149af generic: add helpers for dumping fs-verity metadata
c4ef001021eee73e71760a5c1180ab29b9335c4a generic: test retrieving verity Merkle tree and descriptor
456734557033b389e05dbee39aa2bd2d4c36d2fa generic: test retrieving verity signature
52a3700b26e15a7267527463766ef1f22768ae25 btrfs: Add simple stress test when qgroup limits are reached
6240f927ee8f99bc328a855992ce597a565b5ea0 generic/626: add test for detached mount propagation
e1ea7401a8279bd3f5256d972dfe1e6ed2eff7b1 generic/627: add fstests for idmapped mounts
next reply other threads:[~2021-03-11 8:17 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 8:17 Gitolite [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 6:59 post-receive: pub/scm/linux/kernel/git/brauner/xfstests-dev Gitolite
2021-08-14 10:30 Gitolite
2021-08-14 10:29 Gitolite
2021-08-14 10:16 Gitolite
2021-08-12 15:31 Gitolite
2021-08-12 15:23 Gitolite
2021-08-12 13:47 Gitolite
2021-08-12 13:13 Gitolite
2021-07-31 16:33 Gitolite
2021-07-31 16:24 Gitolite
2021-07-27 7:23 Gitolite
2021-07-26 9:55 Gitolite
2021-07-26 9:38 Gitolite
2021-07-13 10:40 Gitolite
2021-07-13 10:33 Gitolite
2021-07-02 9:23 Gitolite
2021-05-07 14:41 Gitolite
2021-05-07 14:27 Gitolite
2021-05-07 13:42 Gitolite
2021-05-07 13:39 Gitolite
2021-05-07 13:36 Gitolite
2021-05-04 18:24 Gitolite
2021-05-01 12:26 Gitolite
2021-04-12 12:00 Gitolite
2021-03-28 22:39 Gitolite
2021-03-28 22:37 Gitolite
2021-03-28 21:42 Gitolite
2021-03-28 21:31 Gitolite
2021-03-28 21:19 Gitolite
2021-03-28 19:47 Gitolite
2021-03-28 19:39 Gitolite
2021-03-27 11:24 Gitolite
2021-03-27 11:12 Gitolite
2021-03-27 11:08 Gitolite
2021-03-27 10:58 Gitolite
2021-03-27 9:50 Gitolite
2021-03-24 14:40 Gitolite
2021-03-24 9:49 Gitolite
2021-03-24 9:47 Gitolite
2021-03-22 12:52 Gitolite
2021-03-21 15:30 Gitolite
2021-03-21 15:06 Gitolite
2021-03-16 10:23 Gitolite
2021-03-16 10:18 Gitolite
2021-03-11 17:46 Gitolite
2021-03-11 17:02 Gitolite
2021-03-11 14:32 Gitolite
2021-03-11 14:27 Gitolite
2021-03-11 14:27 Gitolite
2021-03-11 14:26 Gitolite
2021-03-11 14:25 Gitolite
2021-03-11 13:39 Gitolite
2021-03-11 13:35 Gitolite
2021-03-11 13:23 Gitolite
2021-03-09 11:58 Gitolite
2021-03-09 11:56 Gitolite
2021-03-09 11:47 Gitolite
2021-03-09 11:43 Gitolite
2021-03-09 11:41 Gitolite
2021-03-09 11:39 Gitolite
2021-03-09 11:34 Gitolite
2021-03-05 15:32 Gitolite
2021-03-02 14:28 Gitolite
2021-03-02 14:24 Gitolite
2021-03-02 14:23 Gitolite
2021-03-02 14:23 Gitolite
2021-03-02 14:22 Gitolite
2021-03-02 14:21 Gitolite
2021-03-02 14:04 Gitolite
2021-03-02 14:00 Gitolite
2021-03-02 13:59 Gitolite
2021-03-02 13:55 Gitolite
2021-03-02 13:48 Gitolite
2021-03-02 13:41 Gitolite
2021-03-02 13:40 Gitolite
2021-03-02 13:33 Gitolite
2021-03-02 13:30 Gitolite
2021-03-02 13:28 Gitolite
2021-03-02 13:27 Gitolite
2021-03-02 13:26 Gitolite
2021-03-02 13:18 Gitolite
2021-03-02 12:45 Gitolite
2021-03-02 12:42 Gitolite
2021-03-02 12:28 Gitolite
2021-03-02 12:25 Gitolite
2021-03-02 12:19 Gitolite
2021-03-02 12:18 Gitolite
2021-03-02 12:16 Gitolite
2021-03-02 12:00 Gitolite
2021-03-02 11:59 Gitolite
2021-03-02 11:56 Gitolite
2021-03-02 11:50 Gitolite
2021-03-02 11:44 Gitolite
2021-03-02 11:43 Gitolite
2021-03-02 11:39 Gitolite
2021-03-02 11:30 Gitolite
2021-03-02 11:22 Gitolite
2021-03-02 11:17 Gitolite
2021-03-02 11:08 Gitolite
2021-03-02 11:08 Gitolite
2021-03-02 11:05 Gitolite
2021-03-02 11:03 Gitolite
2021-03-02 11:01 Gitolite
2021-03-02 10:07 Gitolite
2021-03-01 14:47 Gitolite
2021-03-01 14:46 Gitolite
2021-03-01 14:41 Gitolite
2021-03-01 14:34 Gitolite
2021-03-01 14:31 Gitolite
2021-03-01 14:28 Gitolite
2021-03-01 14:14 Gitolite
2021-03-01 13:28 Gitolite
2021-02-13 10:29 Gitolite
2021-02-13 10:24 Gitolite
2021-02-13 10:22 Gitolite
2021-02-13 10:01 Gitolite
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=161545063557.31813.10521616396072747697@gitolite.kernel.org \
--to=devnull@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.