Julia Evans
@jvns on GitHub. Posts as julia@jvns.ca.
326
messages
196
patches posted
100%
of 10 series merged
19
threads started
2024
first message, Jun 29, 2024
21 hours
since the latest message
Patch series
Of 17 patch series (re-rolls counted once), 10 landed on master and 0 did not; 7 posted in the last 90 days are still in review.
- in reviewstatus: suggest `git merge --continue`, not `git commit`v3, Oct 9, 2026
- in review[doc] Add new page on merge conflictsv2, Oct 9, 2026
- in reviewdoc: checkout: rewrite detached HEAD state explanationOct 7, 2026
- in review[doc] Use `man git` to teach users how to navigate the docsv2, Oct 6, 2026
- in reviewWIP: doc: add new git tutorialOct 6, 2026
- in reviewdoc: don't require a SYNOPSIS in section 7v3, Oct 6, 2026
- in review[doc] Remove gittutorial-2v2, Oct 5, 2026
- mergeddoc: add more AsciiDoc cross-referencesv2, Sep 25, 2026, 2fc11e3382
- mergeddoc: git-pull: fix 'git --rebase abort' typoDec 3, 2025, 8ef7355a8f
- mergeddoc: remove stray text in Git data modelDec 2, 2025, cfdce4afcc
- mergeddoc: add a explanation of Git's data modelv7, Nov 12, 2025, dee80940b1
- mergeddoc: git-reset: clarify DESCRIPTION sectionOct 17, 2025, b767867fae
A series is merged when one of its patches matches a commit on master by the same author, by subject. Versions are linked when they share a patch subject. Patches reworded before landing, or applied under someone else's name, count as not merged.
Recent emails
- Re: [PATCH v2 5/6] doc: git-cherry-pick: link to new merge conflicts guide
- Re: [PATCH v2 1/6] doc: add new gitmergeconflicts man page
- Re: [PATCH v2 0/6] [doc] Add new page on merge conflicts
- status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH v2] status: suggest `git merge --continue`, not `git commit`
- status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH] status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH] status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH 7/7] [doc] ignore conflict markers in gitmergeconflicts.adoc
- doc: git-pull: link to new merge conflicts guide
- doc: git-cherry-pick: link to new merge conflicts guide
- doc: git-revert: link to new merge conflicts guide
- doc: git-rebase: link to new merge conflicts guide
- doc: git-merge: link to new merge conflicts guide
- doc: add new gitmergeconflicts man page
- [doc] Add new page on merge conflicts
- Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs
- Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs
- doc: checkout: rewrite detached HEAD state explanation
- Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs
- Re: [PATCH v2] doc: use `man git` to teach users how to navigate the docs
- doc: use `man git` to teach users how to navigate the docs
- doc: add new Git tutorial for beginners
- doc: remove gittutorial
- WIP: doc: add new git tutorial
- Re: [PATCH v2 0/2] [doc] Remove gittutorial-2
- doc: don't require a SYNOPSIS in section 7
- status: suggest `git merge --continue`, not `git commit`
- Re: [PATCH v2] doc: don't require a SYNOPSIS in section 7
- doc: remove references to gittutorial-2