Skip to content

Linux kernel source tree -- Btrfs commits

active 2025-01-272026-08-08 (UTC)

Partial coverage12,010 / 13,503 hourly files (89%) · 2 absent upstream · 1,489 failed, retryable2025-01-252026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
768
Pushes
668
Pull requests
2
Issues
41
Stars
9
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 559 days from 2025-01-27 to 2026-08-08. Pushes: 668 total, peak 12 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 41 total, peak 17 in a day. Comments: 25 total, peak 4 in a day. Stars: 9 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
kdave48144918
adam90071012811207
fdmanana605500
morbidrsa242202
boryas131300
maharmstone6600
ddiss5012
naota4400
disposableone4002
Augusto77432001
Arcitec1001
ebiggers1001
osandov1100
leg71001
JohnRobson1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#1622ddiss2026-03-23 23:18
    ci: run xfstests quick group in a nested VM
  • Pull request#1624kdave2026-03-05 19:21
  • Issue comment#1624kdave2026-03-05 18:48
    Test for-next (regular, GH kvm)
  • Issue comment#1157kdave2026-03-05 18:48
    Regular for-next build test
  • Issue comment#1622kdave2026-03-05 02:20
    ci: run xfstests quick group in a nested VM
  • Issue comment#1623ddiss2026-03-05 00:20
    Test for-next (regular, GH kvm)
  • Issue comment#1622kdave2026-03-04 21:49
    ci: run xfstests quick group in a nested VM
  • Issue comment#1622kdave2026-03-04 21:48
    ci: run xfstests quick group in a nested VM
  • Issue comment#1622morbidrsa2026-03-04 06:48
    ci: run xfstests quick group in a nested VM
  • Pull request#1622ddiss2026-02-27 12:17
  • Issue#1618kdave2026-01-21 22:30
    [PATCH RFC 0/1] btrfs: don't allocate data off of conventional zones
  • Issue#1602kdave2026-01-21 22:00
    [PATCH] btrfs: fallback to buffered IO if the data profile has duplication
  • Issue#1608kdave2025-11-14 12:36
    [PATCH 0/4] btrfs: some code cleanups in ctree.c
  • Issue#1604kdave2025-11-12 07:27
    [PATCH] btrfs: trivial BTRFS_PATH_AUTO_FREE conversions for tests
  • Issue#1603kdave2025-11-11 13:58
    [PATCH] btrfs: scrub: always update btrfs_scrub_progress::last_physical
  • Issue comment#1000kdave2025-09-26 07:22
    [PATCH v5 00/52] btrfs: add fscrypt support
  • Issue comment#1000ebiggers2025-09-25 19:18
    [PATCH v5 00/52] btrfs: add fscrypt support
  • Issue#1600Augusto77432025-09-20 11:50
    BTRFS developers has priority to do any new feature to avoid the terrible "Parent Transid Verify Failed" error ?
  • Issue comment#1599Augusto77432025-09-20 11:40
    Why is "Metadata,DUP" almost 5x bigger now?
  • Issue comment#1599Arcitec2025-09-10 14:10
    Why is "Metadata,DUP" almost 5x bigger now?
  • Issue#1599JohnRobson2025-09-06 23:45
    Why is "Metadata,DUP" almost 5x bigger now?
  • Issue comment#1146kdave2025-08-04 11:08
    [PATCH 0/5] btrfs: use the super_block as bdev holder
  • Issue#1146kdave2025-08-04 11:08
    [PATCH 0/5] btrfs: use the super_block as bdev holder
  • Issue comment#1593disposableone2025-06-07 14:35
    "Warning no default label for /bla/blah" when mounting a BTRFS volume
  • Issue comment#1593disposableone2025-06-06 14:14
    "Warning no default label for /bla/blah" when mounting a BTRFS volume

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 9 stars here means stars gained during the window, not the repo's star count.