Atousa Duprat
Posts as atousa.p@gmail.com.
21
messages
9
patches posted
0%
of 2 series merged
1
threads started
2015
first message, Oct 29, 2015
May 31, 2017
since the latest message
Patch series
Of 2 patch series (re-rolls counted once), 0 landed on master and 2 did not.
- not mergedgit rev-list doesn't complain when repo is emptyNov 25, 2015
- not mergedProvide another level of abstraction for the SHA1 utilities.v4, Nov 5, 2015
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: [Bug] git branch -v has problems with carriage returns
- Re: [Bug] git branch -v has problems with carriage returns
- Re: Delivery Status Notification (Failure)
- git rev-list doesn't complain when repo is empty
- Re: Suspected bug on `git -C <rp> rev-list --all` where <rp> has 0 commits
- Re: [PATCH v4 2/3] Limit the size of the data block passed to SHA1_Update()
- Move all the SHA1 implementations into one directory
- Limit the size of the data block passed to SHA1_Update()
- Provide another level of abstraction for the SHA1 utilities.
- Re: Bug: stash save -u removes (some) ignored files
- Re: [PATCH 1/2] Limit the size of the data block passed to SHA1_Update()
- Limit the size of the data block passed to SHA1_Update()
- Limit the size of the data block passed to SHA1_Update()
- Re: [PATCH] Limit the size of the data block passed to SHA1_Update()
- Re: [PATCH] Limit the size of the data block passed to SHA1_Update()
- Re: [PATCH] Limit the size of the data block passed to SHA1_Update()
- Limit the size of the data block passed to SHA1_Update()
- Limit the size of the data block passed to SHA1_Update()
- Limit the size of the data block passed to SHA1_Update()
- Re: git fsck failure on OS X with files >= 4 GiB
- Re: git fsck failure on OS X with files >= 4 GiB