From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/brauner/xfstests-dev
Date: Mon, 22 Mar 2021 12:52:24 -0000 [thread overview]
Message-ID: <161641754468.14102.7316500238801092601@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: bd88c8406b475b83243ea704d50d5dc9ee7b8b48
new: eee25916962c8fafa34c5b53f1b8654f9a8c721c
log: revlist-bd88c8406b47-eee25916962c.txt
[-- Attachment #2: revlist-bd88c8406b47-eee25916962c.txt --]
[-- Type: text/plain, Size: 1990 bytes --]
0a3e2198a80935732f4148cfa4cff9f89b71545c fstests: rename RENAME_WHITEOUT test on fs no enough space
2ecbf171ba8c2a12f4c7931ab98b987386f99940 generic: test which tries to exercise AIO/DIO into unwritten space
c532a65528c5e03729798b5750b766e026b4bcf4 generic: clean up tests using fio
f5c3de7d2f4cc99a9beef53a1468051b24c42ca0 fsstress: get rid of attr_list
69a5de82890832addc2d20d2aef0738cebf5f3ee fstests: remove libattr dependencies
0ea70dceec63a08e4ca629eeb7361f9e10281adf xfs: test fallocate ops when rt extent size is and isn't a power of 2
6497ede7ad4e9fc8e5a5a121bd600df896b7d9c6 fstests: remove DMAPI tests
49a59dbfed38f4a67793aa79bcb87bedc6629a67 fstests: remove DMAPI support from build system
42484d90a0982e562cf5567fa935a406945e0d9f xfs: test regression in xfs_bmap_validate_extent
f99e436241f939cfb22d0349b419288abdf4659a generic: test reflink and copy_file_range behavior with O_SYNC and FS_XFLAG_SYNC files
cef0ac422b5142c845cbb5a8d850483133820fee xfs: test mkfs min log size calculation w/ rt volumes
4f4737df70528135a515132e434f105defbbd743 common/filter: refactor quota report filtering
1e3cf5aeb53fd13936fb45e62d687d850313dbcb xfs: test quota softlimit warning functionality
8df851f5a1e191e35ffd6362474d4df3c7958519 xfs/122: fix test for xfs_attr_shortform_t conversion
01b30c9da97c41ceee38ff5bedc6841dcfd41c0e generic: test file writers racing with FIDEDUPERANGE
f6ddaf130d5b0817278afe441fdde52f464f321b xfs: test delalloc quota leak when chprojid fails
229e2a4baa8c940ec6f2b6e667c00f39a92b8c4c generic/631: add test for detached mount propagation
bb5890c17c8f4e39a63d552137d4dd93e5c476c9 generic/632: add fstests for idmapped mounts
b036c70241b1ee977f11a2696d71386cea85d6c3 common/rc: add _scratch_{u}mount_idmapped() helpers
0d32e62340cd1f756f87a4cb2adc51fd6fe57006 common/quota: move _qsetup() helper to common code
5fb746f423ff2edc43552a582d87f5fa4712309b xfs/529: quotas and idmapped mounts
eee25916962c8fafa34c5b53f1b8654f9a8c721c xfs/530: quotas on idmapped mounts
next reply other threads:[~2021-03-22 12:52 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:52 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-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-11 8:17 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=161641754468.14102.7316500238801092601@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.