Kaartic Sivaraam
@sivaraam on GitHub. Posts as kaartic.sivaraam@gmail.com, kaarticsivaraam91196@gmail.com.
753
messages
200
patches posted
68%
of 37 series merged
76
threads started
2016
first message, Dec 18, 2016
2 days
since the latest message
Patch series
Of 38 patch series (re-rolls counted once), 25 landed on master and 12 did not; 1 posted in the last 90 days is still in review.
- in reviewImprove error reporting to mention "why" a directory is not a repositoryv2, Sep 29, 2026
- mergedbuiltin/history: unuse the commit buffer after usev4, Sep 15, 2026, 0e75d17ff7
- mergedsubmodule: corret an incorrectly formatted error messagev3, Oct 23, 2021, c21fb4676f
- mergedSome submodule related code cleanupv2, Jun 22, 2021, 1cf823d8f0
- not mergedUpdate ProGit for pu -> seen change? (was Re: [PATCH v3 0/3] Accommodate for pu having been renamed to seen)v3, Jun 26, 2020
- not mergedDoc/SubmittingPatches: re-phrashing a sentence about alternate solutions (was Re: [PATCH] Makefile: make NO_ICONV really mean "no iconv")Jun 17, 2018
- mergedt3200: clarify description of --set-upstream testv2, Jun 17, 2018, cf317877e3
- mergedbranch --list: print useful info whilst interactive rebasing a detached HEADv3, Apr 3, 2018, a236f900d8
- mergedbranch: improve error messages of branch renamingv5, Mar 10, 2018, 9c93ff7cc4
- mergedDoc/submodules: a few updatesv3, Jan 14, 2018, e1b3f3dd38
- not mergedError in `git': free(): invalid pointer (was Re: [PATCH] sequencer: improve config handling)Dec 20, 2017
- not mergedimap-send: URI encode server folderv3, Dec 18, 2017
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 1/1] repo: add filtering options to "repo structure"
- Re: Participating in Outreachy's December 2026 cohort
- Re: [RFC PATCH v2 4/4] setup: communicate why a directory is not a valid git directory
- Re: [RFC PATCH v2 3/4] setup: introduce new helper 'is_git_directory_verbose'
- Re: [PATCH 0/7] A couple of Meson improvements
- Re: [PATCH 6/7] meson: update wrappers
- Re: [PATCH 4/7] meson: use precompiled headers for unit tests
- Re: [PATCH 1/7] meson: avoid recompiling HTTP sources several times
- Re: [PATCH v2 2/3] parse-options: add early_scan_options()
- setup: communicate why a directory is not a valid git directory
- setup: introduce new helper 'is_git_directory_verbose'
- t0009: add tests to cover more error reporting scenarios
- Improve error reporting to mention "why" a directory is not a repository
- setup: normalize an if-else to follow our convention
- Re: [PATCH v2 0/7] setup: enforce repo passed to `create_repository()` has no state
- Re: [PATCH v2 0/7] setup: enforce repo passed to `create_repository()` has no state
- Re: [PATCH 2/7] path: introduce `safe_create_leading_directories_no_share_const()`
- Re: [PATCH 0/7] setup: enforce repo passed to `create_repository()` has no state
- Re: [PATCH 4/7] builtin/init: move handling of "core.sharedRepository" into "setup.c"
- Re: [PATCH 3/7] builtin/init: refactor messy creation of leading directories
- Re: [PATCH 2/7] path: introduce `safe_create_leading_directories_no_share_const()`
- Re: [RFC PATCH 2/3] setup: introduce new helper 'is_git_directory_verbose'
- Re: [RFC PATCH 3/3] setup: communicate why a directory is not a valid git directory
- Re: [RFC PATCH 1/3] t0009: add tests to cover more error reporting scenarios
- Re: [PATCH v6 0/3] t40*: modernize
- Re: [PATCH v6 0/3] t40*: modernize
- setup: communicate why a directory is not a valid git directory
- setup: introduce new helper 'is_git_directory_verbose'
- t0009: add tests to cover more error reporting scenarios
- Improve error reporting to mention "why" a directory is not a repository