Andrey Okoshkin
@okodron on GitHub. Posts as a.okoshkin@samsung.com.
18
messages
10
patches posted
75%
of 4 series merged
4
threads started
2017
first message, Oct 18, 2017
Oct 31, 2017
since the latest message
Patch series
Of 4 patch series (re-rolls counted once), 3 landed on master and 1 did not.
- mergedmerge-recursive: check GIT_MERGE_VERBOSITY only oncev5, Oct 31, 2017, 804862209b
- mergeddiff: fix lstat() error handling in diff_populate_filespec()Oct 27, 2017, 10e0ca843d
- not mergedpath: use xmalloc in add_to_trieOct 24, 2017
- mergedcommit: check result of resolve_ref_unsafev4, Oct 20, 2017, c26de08370
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
- merge-recursive: check GIT_MERGE_VERBOSITY only once
- Re: [PATCH v4] merge-recursive: check GIT_MERGE_VERBOSITY only once
- merge-recursive: check GIT_MERGE_VERBOSITY only once
- diff: fix lstat() error handling in diff_populate_filespec()
- Re: [PATCH v3] merge-recursive: check GIT_MERGE_VERBOSITY only once
- Re: [PATCH v2] merge-recursive: check GIT_MERGE_VERBOSITY only once
- merge-recursive: check GIT_MERGE_VERBOSITY only once
- Re: [PATCH] merge-recursive: check GIT_MERGE_VERBOSITY only once
- Re: [PATCH] merge-recursive: check GIT_MERGE_VERBOSITY only once
- Re: [PATCH] merge-recursive: check GIT_MERGE_VERBOSITY only once
- merge-recursive: check GIT_MERGE_VERBOSITY only once
- path: use xmalloc in add_to_trie
- commit: check result of resolve_ref_unsafe
- commit: check result of resolve_ref_unsafe
- Re: [PATCH v2] commit: check result of resolve_ref_unsafe
- commit: check result of resolve_ref_unsafe
- Re: [PATCH] commit: check result of resolve_ref_unsafe
- commit: check result of resolve_ref_unsafe