From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/colyli/linux-bcache
Date: Tue, 12 Jan 2021 11:11:33 -0000 [thread overview]
Message-ID: <161044989392.19100.2731306632015272904@gitolite.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
---
service: git-receive-pack
repo: pub/scm/linux/kernel/git/colyli/linux-bcache
user: colyli
changes:
- ref: refs/heads/nvdimm-meta
old: 7c53f6b671f4aba70ff15e1b05148b10d58c2837
new: a0d54b4f5b219fb31f0776e9f53aa137e78ae431
log: revlist-7c53f6b671f4-a0d54b4f5b21.txt
[-- Attachment #2: revlist-7c53f6b671f4-a0d54b4f5b21.txt --]
[-- Type: text/plain, Size: 1766 bytes --]
72d78717c6d06adf65d2e3dccc96d9e9dc978593 nfsd: Fixes for nfsd4_encode_read_plus_data()
b68f0cbd3f95f2df81e525c310a41fc73c2ed0d3 nfsd: Don't set eof on a truncated READ_PLUS
d6c9e4368cc6a61bf25c9c72437ced509c854563 NFSD: Fix sparse warning in nfssvc.c
4a85a6a3320b4a622315d2e0ea91a1d2b013bce4 SUNRPC: Handle TCP socket sends with kernel_sendpage() again
7b723008f9c95624c848fad661c01b06e47b20da NFSD: Restore NFSv4 decoding's SAVEMEM functionality
dfe94d4086e40e92b1926bddcefa629b791e9b28 x86/hyperv: Fix kexec panic/hang issues
ad0a6bad44758afa3b440c254a24999a0c7e35d5 x86/hyperv: check cpu mask after interrupt has been disabled
71008734d27f2276fcef23a5e546d358430f2d52 btrfs: print the actual offset in btrfs_root_name
29b665cc51e8b602bf2a275734349494776e3dbc btrfs: prevent NULL pointer dereference in extent_io_tree_panic
347fb0cfc9bab5195c6701e62eda488310d7938f btrfs: tree-checker: check if chunk item end overflows
50e31ef486afe60f128d42fb9620e2a63172c15c btrfs: reloc: fix wrong file extent type check to avoid false ENOENT
e076ab2a2ca70a0270232067cd49f76cd92efe64 btrfs: shrink delalloc pages instead of full inodes
f1ee3e150bd9da2dd60a210926c86cffd4a336ea Merge tag 'hyperv-fixes-signed-20210111' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux
c912fd05fab97934e4cf579654d0dc4835b4758c Merge tag 'nfsd-5.11-1' of git://git.linux-nfs.org/projects/cel/cel-2.6
7bb83f6fc4ee84e95d0ac0d14452c2619fb3fe70 tracing/kprobes: Do the notrace functions check without kprobes on ftrace
6e68b9961ff690ace07fac22c3c7752882ecc40a Merge tag 'for-5.11-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
a0d54b4f5b219fb31f0776e9f53aa137e78ae431 Merge tag 'trace-v5.11-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
next reply other threads:[~2021-01-12 11:11 UTC|newest]
Thread overview: 268+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 11:11 Gitolite [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-27 2:44 post-receive: pub/scm/linux/kernel/git/colyli/linux-bcache Gitolite
2021-08-24 6:45 Gitolite
2021-08-18 18:12 Gitolite
2021-08-11 17:14 Gitolite
2021-08-11 16:50 Gitolite
2021-08-10 16:08 Gitolite
2021-08-10 16:07 Gitolite
2021-08-09 16:38 Gitolite
2021-08-06 7:47 Gitolite
2021-08-05 17:01 Gitolite
2021-08-04 15:57 Gitolite
2021-08-04 15:55 Gitolite
2021-07-26 16:10 Gitolite
2021-07-26 16:10 Gitolite
2021-06-30 12:45 Gitolite
2021-06-30 12:24 Gitolite
2021-06-23 11:49 Gitolite
2021-06-15 5:51 Gitolite
2021-06-15 5:15 Gitolite
2021-06-15 4:30 Gitolite
2021-06-15 3:34 Gitolite
2021-06-08 13:58 Gitolite
2021-06-08 13:20 Gitolite
2021-06-03 13:12 Gitolite
2021-06-03 13:12 Gitolite
2021-06-03 12:32 Gitolite
2021-06-03 6:08 Gitolite
2021-06-02 13:36 Gitolite
2021-06-02 13:05 Gitolite
2021-06-02 12:34 Gitolite
2021-06-02 6:08 Gitolite
2021-06-02 5:27 Gitolite
2021-05-21 2:06 Gitolite
2021-05-13 4:09 Gitolite
2021-04-20 5:03 Gitolite
2021-04-13 13:05 Gitolite
2021-04-13 11:22 Gitolite
2021-04-11 13:57 Gitolite
2021-04-11 13:03 Gitolite
2021-04-10 2:58 Gitolite
2021-04-10 2:55 Gitolite
2021-04-08 16:22 Gitolite
2021-04-08 16:21 Gitolite
2021-03-29 15:00 Gitolite
2021-03-29 15:00 Gitolite
2021-03-29 2:00 Gitolite
2021-03-05 2:25 Gitolite
2021-02-10 13:59 Gitolite
2021-02-10 12:29 Gitolite
2021-02-08 13:21 Gitolite
2021-02-08 10:55 Gitolite
2021-02-08 10:55 Gitolite
2021-02-07 15:06 Gitolite
2021-02-06 13:04 Gitolite
2021-02-06 12:27 Gitolite
2021-02-03 8:31 Gitolite
2021-02-03 6:50 Gitolite
2021-01-30 8:36 Gitolite
2021-01-30 8:32 Gitolite
2021-01-30 7:37 Gitolite
2021-01-28 16:46 Gitolite
2021-01-28 15:39 Gitolite
2021-01-27 15:11 Gitolite
2021-01-22 11:06 Gitolite
2021-01-20 11:54 Gitolite
2021-01-17 14:35 Gitolite
2021-01-12 11:11 Gitolite
2021-01-11 10:01 Gitolite
2021-01-11 9:58 Gitolite
2021-01-04 8:32 Gitolite
2021-01-02 8:04 Gitolite
2021-01-02 8:03 Gitolite
2021-01-02 7:26 Gitolite
2020-12-23 14:50 Gitolite
2020-12-07 8:42 Gitolite
2020-11-02 14:18 Gitolite Activity Feed
2020-10-09 14:33 Gitolite
2020-09-18 9:50 Gitolite
2020-09-18 8:27 Gitolite
2020-09-18 6:18 Gitolite
2020-08-15 16:42 Gitolite
2020-08-15 16:41 Gitolite
2020-08-15 4:27 Gitolite
2020-08-15 4:26 Gitolite
2020-08-14 16:59 Gitolite
2020-08-12 16:03 Gitolite
2020-08-12 16:03 Gitolite
2020-08-04 16:12 Gitolite
2020-08-04 16:11 Gitolite
2020-07-24 16:53 Gitolite
2020-07-17 11:39 Gitolite
2020-07-14 14:37 Gitolite
2020-07-13 12:27 Gitolite
2020-07-12 17:44 Gitolite
2020-07-10 15:50 Gitolite
2020-07-10 15:49 Gitolite
2020-07-09 17:16 Gitolite
2020-07-05 16:07 Gitolite
2020-07-03 15:55 Gitolite
2020-07-03 15:54 Gitolite
2020-06-26 15:11 Gitolite
2020-06-14 8:49 Gitolite
2020-06-03 8:25 Gitolite
2020-06-03 8:24 Gitolite
2020-06-03 8:24 Gitolite
2020-06-03 8:23 Gitolite
2020-06-02 2:52 Gitolite
2020-05-26 8:58 Gitolite
2020-05-26 8:14 Gitolite
2020-05-26 5:02 Gitolite
2020-05-23 8:15 Gitolite
2020-05-22 12:27 Gitolite
2020-05-22 12:25 Gitolite
2020-05-22 11:00 Gitolite
2020-05-04 15:41 Gitolite
2020-05-04 15:40 Gitolite
2020-05-04 15:39 Gitolite
2020-05-04 15:39 Gitolite
2020-05-04 15:38 Gitolite
2020-03-23 2:17 Gitolite
2020-03-22 9:53 Gitolite
2020-03-22 5:25 Gitolite
2020-03-22 4:47 Gitolite
2020-03-01 15:11 Gitolite
2020-02-10 13:35 Gitolite
2020-02-10 13:35 Gitolite
2020-02-10 13:32 Gitolite
2020-01-28 16:46 Gitolite
2020-01-28 12:40 Gitolite
2020-01-28 12:39 Gitolite
2020-01-23 16:24 Gitolite
2020-01-23 16:21 Gitolite
2020-01-08 14:59 Gitolite
2019-12-22 12:30 Gitolite
2019-12-22 5:22 Gitolite
2019-12-06 10:20 Gitolite
2019-12-06 10:19 Gitolite
2019-12-05 15:39 Gitolite
2019-12-05 15:16 Gitolite
2019-12-03 16:17 Gitolite
2019-11-30 7:53 Gitolite
2019-11-30 2:59 Gitolite
2019-11-30 2:59 Gitolite
2019-11-30 2:47 Gitolite
2019-11-13 8:06 Gitolite
2019-11-13 7:17 Gitolite
2019-11-13 5:41 Gitolite
2019-09-25 7:04 Gitolite
2019-07-22 14:19 Gitolite
2019-07-10 0:59 Gitolite
2019-07-10 0:59 Gitolite
2019-06-27 15:48 Gitolite
2019-06-27 15:47 Gitolite
2019-06-27 12:23 Gitolite
2019-06-22 15:56 Gitolite
2019-06-22 15:56 Gitolite
2019-06-22 15:46 Gitolite
2019-06-22 15:28 Gitolite
2019-06-22 15:28 Gitolite
2019-06-20 17:31 Gitolite
2019-06-20 17:30 Gitolite
2019-06-20 17:29 Gitolite
2019-06-12 16:33 Gitolite
2019-06-12 16:33 Gitolite
2019-06-10 16:04 Gitolite
2019-06-10 14:41 Gitolite
2019-06-10 14:41 Gitolite
2019-06-10 14:39 Gitolite
2019-06-05 16:37 Gitolite
2019-06-05 16:36 Gitolite
2019-06-04 6:57 Gitolite
2019-05-31 18:07 Gitolite
2019-05-31 18:07 Gitolite
2019-05-31 10:46 Gitolite
2019-05-24 16:16 Gitolite
2019-05-24 16:06 Gitolite
2019-05-22 14:42 Gitolite
2019-05-22 14:42 Gitolite
2019-05-22 14:26 Gitolite
2019-05-22 14:20 Gitolite
2019-05-22 9:24 Gitolite
2019-05-21 16:16 Gitolite
2019-05-21 14:43 Gitolite
2019-05-13 9:10 Gitolite
2019-05-13 8:58 Gitolite
2019-05-13 8:28 Gitolite
2019-05-13 8:26 Gitolite
2019-05-13 8:26 Gitolite
2019-04-26 6:13 Gitolite
2019-04-26 6:13 Gitolite
2019-03-27 11:56 Gitolite
2019-03-27 11:56 Gitolite
2019-03-25 8:46 Gitolite
2019-03-25 8:45 Gitolite
2019-03-24 16:29 Gitolite
2019-03-24 16:28 Gitolite
2019-03-24 16:14 Gitolite
2019-03-24 16:14 Gitolite
2019-03-20 15:28 Gitolite
2019-03-20 15:28 Gitolite
2019-03-19 4:42 Gitolite
2019-03-19 4:41 Gitolite
2019-03-19 4:41 Gitolite
2019-03-02 10:37 Gitolite
2019-03-02 10:37 Gitolite
2019-03-01 10:13 Gitolite
2019-03-01 10:13 Gitolite
2019-03-01 10:06 Gitolite
2019-03-01 10:06 Gitolite
2019-02-27 12:45 Gitolite
2019-02-27 7:06 Gitolite
2019-02-08 15:24 Gitolite
2019-02-08 15:24 Gitolite
2019-02-05 13:10 Gitolite
2019-02-05 13:10 Gitolite
2019-02-05 12:10 Gitolite
2019-02-05 12:10 Gitolite
2019-02-05 12:09 Gitolite
2018-12-23 11:06 Gitolite
2018-12-23 10:48 Gitolite
2018-12-23 10:38 Gitolite
2018-12-23 10:38 Gitolite
2018-12-23 8:54 Gitolite
2018-12-23 8:53 Gitolite
2018-12-23 8:11 Gitolite
2018-12-23 7:32 Gitolite
2018-12-23 7:30 Gitolite
2018-12-20 15:06 Gitolite
2018-12-20 15:04 Gitolite
2018-12-18 8:16 Gitolite
2018-12-13 14:34 Gitolite
2018-12-13 14:22 Gitolite
2018-12-13 14:22 Gitolite
2018-11-22 15:33 Gitolite
2018-11-22 15:33 Gitolite
2018-11-22 14:42 Gitolite
2018-11-22 14:36 Gitolite
2018-11-14 6:34 Gitolite
2018-11-14 6:34 Gitolite
2018-11-14 6:30 Gitolite
2018-09-30 9:41 Gitolite
2018-09-30 9:41 Gitolite
2018-09-27 2:56 Gitolite
2018-09-27 2:55 Gitolite
2018-09-25 16:07 Gitolite
2018-09-25 12:27 Gitolite
2018-09-25 12:27 Gitolite
2018-09-25 10:36 Gitolite
2018-09-16 17:41 Gitolite
2018-09-14 7:53 Gitolite
2018-09-14 7:53 Gitolite
2018-08-11 13:03 Gitolite
2018-08-11 12:01 Gitolite
2018-08-10 15:45 Gitolite
2018-08-10 15:45 Gitolite
2018-08-10 7:22 Gitolite
2018-08-10 7:22 Gitolite
2018-08-10 4:35 Gitolite
2018-08-09 5:22 Gitolite
2018-08-09 5:22 Gitolite
2018-08-04 14:24 Gitolite
2018-08-04 14:24 Gitolite
2018-08-02 14:58 Gitolite
2018-08-02 14:58 Gitolite
2018-08-02 14:09 Gitolite
2018-08-02 12:07 Gitolite
2018-07-26 16: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=161044989392.19100.2731306632015272904@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.