{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":741070720,"defaultBranch":"master","name":"git","ownerLogin":"vdye","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-01-09T16:31:33.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/3619353?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1718066611.0","currentOid":""},"activityList":{"items":[{"before":"0371a3aafb9504dcdc802203cde943adcbb2e2f4","after":"d392c440b8a243a9fa3e5b603c42a81f02c26e62","ref":"refs/heads/vdye/mktree-recursive","pushedAt":"2024-06-19T21:16:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"mktree: remove entries when mode is 0\n\nIf tree entries are specified with a mode with value '0', remove them from\nthe tree instead of adding/updating them. If the mode is '0', both the\nprovided type string (if specified) and the object ID of the entry are\nignored.\n\nNote that entries with mode '0' are added to the 'struct tree_ent_array'\nwith a trailing slash so that it's always treated like a directory. This is\na bit of a hack to ensure that the removal supercedes any preceding entries\nwith matching names, as well as any nested inside a directory matching its\nname.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"mktree: remove entries when mode is 0"}},{"before":"90c64036b83303b0991c93e19ca4724459f196d5","after":"0371a3aafb9504dcdc802203cde943adcbb2e2f4","ref":"refs/heads/vdye/mktree-recursive","pushedAt":"2024-06-19T19:15:27.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"mktree: remove entries when mode is 0\n\nIf tree entries are specified with a mode with value '0', remove them from\nthe tree instead of adding/updating them. If the mode is '0', both the\nprovided type string (if specified) and the object ID of the entry are\nignored.\n\nNote that entries with mode '0' are added to the 'struct tree_ent_array'\nwith a trailing slash so that it's always treated like a directory. This is\na bit of a hack to ensure that the removal supercedes any preceding entries\nwith matching names, as well as any nested inside a directory matching its\nname.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"mktree: remove entries when mode is 0"}},{"before":"a90d6d0c943283e9e7bd181cd6e9bb6d4572aaeb","after":"90c64036b83303b0991c93e19ca4724459f196d5","ref":"refs/heads/vdye/mktree-recursive","pushedAt":"2024-06-19T18:54:35.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"mktree: remove entries when mode is 0\n\nIf tree entries are specified with a mode with value '0', remove them from\nthe tree instead of adding/updating them. If the mode is '0', both the\nprovided type string (if specified) and the object ID of the entry are\nignored.\n\nNote that entries with mode '0' are added to the 'struct tree_ent_array'\nwith a trailing slash so that it's always treated like a directory. This is\na bit of a hack to ensure that the removal supercedes any preceding entries\nwith matching names, as well as any nested inside a directory matching its\nname.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"mktree: remove entries when mode is 0"}},{"before":"277a81839cb296828efc3baafca11694340a0ba4","after":"a90d6d0c943283e9e7bd181cd6e9bb6d4572aaeb","ref":"refs/heads/vdye/mktree-recursive","pushedAt":"2024-06-11T05:05:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"mktree: remove entries when mode is 0\n\nIf tree entries are specified with a mode with value '0', remove them from\nthe tree instead of adding/updating them. If the mode is '0', both the\nprovided type string (if specified) and the object ID of the entry are\nignored.\n\nNote that entries with mode '0' are added to the 'struct tree_ent_array'\nwith a trailing slash so that it's always treated like a directory. This is\na bit of a hack to ensure that the removal supercedes any preceding entries\nwith matching names, as well as any nested inside a directory matching its\nname.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"mktree: remove entries when mode is 0"}},{"before":null,"after":"277a81839cb296828efc3baafca11694340a0ba4","ref":"refs/heads/vdye/mktree-recursive","pushedAt":"2024-06-11T00:43:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"mktree: remove entries when mode is 0\n\nIf tree entries are specified with a mode with value '0', remove them from\nthe tree instead of adding/updating them. If the mode is '0', both the\nprovided type string (if specified) and the object ID of the entry are\nignored.\n\nNote that entries with mode '0' are added to the 'struct tree_ent_array'\nwith a trailing slash so that it's always treated like a directory. This is\na bit of a hack to ensure that the removal supercedes any preceding entries\nwith matching names, as well as any nested inside a directory matching its\nname.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"mktree: remove entries when mode is 0"}},{"before":"6d4a10c6acefdf4fa904df823276ab01cbf3270b","after":"93a15110ed23733cd3255aaa0a171578495537b2","ref":"refs/heads/vdye/merge-tree-strategy-option","pushedAt":"2024-05-07T21:19:14.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Documentation/git-merge-tree.txt: document -X\n\nAdd an entry in the 'merge-tree' builtin documentation for\n-X/--strategy-option (added in 6a4c9e7b32 (merge-tree: add -X strategy\noption, 2023-09-24)). The same option is documented for 'merge', 'rebase',\n'revert', etc. in their respective Documentation/ files, so let's do the\nsame for 'merge-tree'.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"Documentation/git-merge-tree.txt: document -X"}},{"before":null,"after":"6d4a10c6acefdf4fa904df823276ab01cbf3270b","ref":"refs/heads/vdye/merge-tree-strategy-option","pushedAt":"2024-05-07T21:07:52.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Documentation/git-merge-tree.txt: document -X\n\nAdd a documentation entry for -X/--strategy-option in '--merge-tree',\nincluding a link to the 'git-merge' documentation with more details on which\nstrategy options are available and what they do.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"Documentation/git-merge-tree.txt: document -X"}},{"before":"64d1f76d96f97602cbde7304eab68c08e65bf52e","after":"10f928d4bec06bbe07ad52e1c5b2459f4813547e","ref":"refs/heads/hackweek/more-odb-over-ipc","pushedAt":"2024-04-23T15:18:54.000Z","pushType":"pr_merge","commitsCount":3,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Merge pull request #1 from mjcheetham/ipc-hash-object\n\nAdd basic object writing to ODB over IPC hackweek project","shortMessageHtmlLink":"Merge pull request #1 from mjcheetham/ipc-hash-object"}},{"before":null,"after":"64d1f76d96f97602cbde7304eab68c08e65bf52e","ref":"refs/heads/hackweek/more-odb-over-ipc","pushedAt":"2024-04-22T23:29:08.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"hackathon: add results to summarize my week of hacking\n\nSigned-off-by: Jeff Hostetler ","shortMessageHtmlLink":"hackathon: add results to summarize my week of hacking"}},{"before":null,"after":"64d1f76d96f97602cbde7304eab68c08e65bf52e","ref":"refs/heads/graph-odb","pushedAt":"2024-04-22T16:47:41.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"hackathon: add results to summarize my week of hacking\n\nSigned-off-by: Jeff Hostetler ","shortMessageHtmlLink":"hackathon: add results to summarize my week of hacking"}},{"before":null,"after":"64d1f76d96f97602cbde7304eab68c08e65bf52e","ref":"refs/heads/jh/odb-over-ipc","pushedAt":"2024-04-22T16:34:26.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"hackathon: add results to summarize my week of hacking\n\nSigned-off-by: Jeff Hostetler ","shortMessageHtmlLink":"hackathon: add results to summarize my week of hacking"}},{"before":"89103d2ba4694a658cd961230351adaa94755d4c","after":"25699f02493d7f27cabe850e45debaab12f602bf","ref":"refs/heads/tentative/vfs-2.44.0","pushedAt":"2024-02-27T01:00:10.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Fix `sparse-checkout set` crashes (#607)","shortMessageHtmlLink":"Fix sparse-checkout set crashes (git#607)"}},{"before":"54f2bdb627e81ca399935754fa02437ed68630b9","after":"89103d2ba4694a658cd961230351adaa94755d4c","ref":"refs/heads/tentative/vfs-2.44.0","pushedAt":"2024-02-27T00:58:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Fix `sparse-checkout set` crashes (#607)","shortMessageHtmlLink":"Fix sparse-checkout set crashes (git#607)"}},{"before":null,"after":"54f2bdb627e81ca399935754fa02437ed68630b9","ref":"refs/heads/tentative/vfs-2.44.0","pushedAt":"2024-02-26T23:08:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Fix `sparse-checkout set` crashes (#607)","shortMessageHtmlLink":"Fix sparse-checkout set crashes (git#607)"}},{"before":"a4fd641aa41ecba9cc26a81af974343f6971c7af","after":"456101b2a61fe686b2f6fce831e792edfefec373","ref":"refs/heads/vdye/for-each-ref-date-sorting","pushedAt":"2024-02-08T01:39:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"ref-filter.c: sort formatted dates by byte value\n\nUpdate the ref sorting functions of 'ref-filter.c' so that when date fields\nare specified with a format string (such as in 'git for-each-ref\n--sort=creatordate:'), they are sorted by their formatted string\nvalue rather than by the underlying numeric timestamp. Currently, date\nfields are always sorted by timestamp, regardless of whether formatting\ninformation is included in the '--sort' key.\n\nLeaving the default (unformatted) date sorting unchanged, sorting by the\nformatted date string adds some flexibility to 'for-each-ref' by allowing\nfor behavior like \"sort by year, then by refname within each year\" or \"sort\nby time of day\". Because the inclusion of a format string previously had no\neffect on sort behavior, this change likely will not affect existing usage\nof 'for-each-ref' or other ref listing commands.\n\nAdditionally, update documentation & tests to document the new sorting\nmechanism.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"ref-filter.c: sort formatted dates by byte value"}},{"before":"563b254bfb898f12f33c9749f1164294b80cdce6","after":"a4fd641aa41ecba9cc26a81af974343f6971c7af","ref":"refs/heads/vdye/for-each-ref-date-sorting","pushedAt":"2024-02-07T23:05:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"ref-filter.c: sort formatted dates by byte value\n\nUpdate the ref sorting functions of 'ref-filter.c' so that when date fields\nare specified with a format string (such as in 'git for-each-ref\n--sort=creatordate:'), they are sorted by their formatted string\nvalue rather than by the underlying numeric timestamp. Currently, date\nfields are always sorted by timestamp, regardless of whether formatting\ninformation is included in the '--sort' key.\n\nLeaving the default (unformatted) date sorting unchanged, sorting by the\nformatted date string adds some flexibility to 'for-each-ref' by allowing\nfor behavior like \"sort by year, then by refname within each year\" or \"sort\nby time of day\". Because the inclusion of a format string previously had no\neffect on sort behavior, this change likely will not affect existing usage\nof 'for-each-ref' or other ref listing commands.\n\nAdditionally, update documentation & tests to document the new sorting\nmechanism.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"ref-filter.c: sort formatted dates by byte value"}},{"before":null,"after":"563b254bfb898f12f33c9749f1164294b80cdce6","ref":"refs/heads/vdye/for-each-ref-date-sorting","pushedAt":"2024-02-07T22:56:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"ref-filter.c: sort formatted dates by byte value\n\nUpdate the handling of date fields in the ref sorting functions of\n'ref-filter.c' so that date atoms specified with a format string (such as in\n'git for-each-ref --sort=creatordate:') are sorted by the\nformatted string value rather than by the numeric timestamp. Currently, date\nfields are always sorted by timestamp, regardless of whether formatting\ninformation is included in the '--sort' key.\n\nLeaving the default (unformatted) date sorting unchanged, sorting by the\nformatted date string adds some flexibility to 'for-each-ref' by allowing\nfor behavior like \"sort by year, then by refname within each year\" or \"sort\nby time of day\". Because the inclusion of a format string previously had no\neffect on sort behavior, this change likely will not affect existing usage\nof 'for-each-ref' and other ref listing commands.\n\nAdditionally, update documentation & tests to document the new sorting\nmechanism.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"ref-filter.c: sort formatted dates by byte value"}},{"before":"c5428bd8dae827eed68b05819329fc831205c007","after":"b79b1a7178076be1d1a80212dfabd3c37587d443","ref":"refs/heads/vdye/strengthen-fsck-url-checks","pushedAt":"2024-01-18T01:08:01.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"submodule-config.c: strengthen URL fsck check\n\nUpdate the validation of \"curl URL\" submodule URLs (i.e. those that specify\nan \"http[s]\" or \"ftp[s]\" protocol) in 'check_submodule_url()' to catch more\ninvalid URLs. The existing validation using 'credential_from_url_gently()'\nparses certain URLs incorrectly, leading to invalid submodule URLs passing\n'git fsck' checks. Conversely, 'url_normalize()' - used to validate remote\nURLs in 'remote_get()' - correctly identifies the invalid URLs missed by\n'credential_from_url_gently()'.\n\nTo catch more invalid cases, replace 'credential_from_url_gently()' with\n'url_normalize()' followed by a 'url_decode()' and a check for newlines\n(mirroring 'check_url_component()' in the 'credential_from_url_gently()'\nvalidation).\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"submodule-config.c: strengthen URL fsck check"}},{"before":"5eb2f1c0c99e2ada6981a1d4dae409dd2f7bb287","after":"c5428bd8dae827eed68b05819329fc831205c007","ref":"refs/heads/vdye/strengthen-fsck-url-checks","pushedAt":"2024-01-17T21:53:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"submodule-config.c: strengthen URL fsck check\n\nUpdate the validation of \"curl URL\" submodule URLs (i.e. those that specify\nan \"http[s]\" or \"ftp[s]\" protocol) in 'check_submodule_url()' to catch more\ninvalid URLs. The existing validation using 'credential_from_url_gently()'\nparses certain URLs incorrectly, leading to invalid submodule URLs passing\n'git fsck' checks. Conversely, 'url_normalize()' - used to validate remote\nURLs in 'remote_get()' - correctly identifies the invalid URLs missed by\n'credential_from_url_gently()'.\n\nTo catch more invalid cases, replace 'credential_from_url_gently()' with\n'url_normalize()' followed by a 'url_decode()' and a check for newlines\n(mirroring 'check_url_component()' in the 'credential_from_url_gently()'\nvalidation).\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"submodule-config.c: strengthen URL fsck check"}},{"before":"893071530d3b77d6b72b7f69a6dfb9947579865e","after":"5eb2f1c0c99e2ada6981a1d4dae409dd2f7bb287","ref":"refs/heads/vdye/strengthen-fsck-url-checks","pushedAt":"2024-01-17T20:00:24.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"submodule-config.c: strengthen URL fsck check\n\nUpdate the validation of \"curl URL\" submodule URLs (i.e. those that specify\nan \"http[s]\" or \"ftp[s]\" protocol) in 'check_submodule_url()' to catch more\ninvalid URLs. The existing validation using 'credential_from_url_gently()'\nparses certain URLs incorrectly, leading to invalid submodule URLs passing\n'git fsck' checks. Conversely, 'url_normalize()' - used to validate remote\nURLs in 'remote_get()' - correctly identifies the invalid URLs missed by\n'credential_from_url_gently()'.\n\nTo catch more invalid cases, replace 'credential_from_url_gently()' with\n'url_normalize()' followed by a 'url_decode()' and a check for newlines\n(mirroring 'check_url_component()' in the 'credential_from_url_gently()'\nvalidation).\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"submodule-config.c: strengthen URL fsck check"}},{"before":null,"after":"010d5e51595bd3f77b6d3606298a2b436c66ecc6","ref":"refs/heads/reset/handle-missing-dirs","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"unpack-trees: unpack new trees as sparse directories\n\nIf 'unpack_single_entry()' is unpacking a new directory tree (that is, one\nnot already present in the index) into a sparse index, unpack the tree as a\nsparse directory rather than traversing its contents and unpacking each file\nindividually. This helps keep the sparse index as collapsed as possible in\ncases such as 'git reset --hard' restoring a outside-of-cone directory\nremoved with 'git rm -r --sparse'.\n\nWithout this patch, 'unpack_single_entry()' will only unpack a directory\ninto the index as a sparse directory (rather than traversing into it and\nunpacking its files one-by-one) if an entry with the same name already\nexists in the index. This patch allows sparse directory unpacking without a\nmatching index entry when the following conditions are met:\n\n1. the directory's path is outside the sparse cone, and\n2. there are no children of the directory in the index\n\nIf a directory meets these requirements (as determined by\n'is_new_sparse_dir()'), 'unpack_single_entry()' unpacks the sparse directory\nindex entry and propagates the decision back up to 'unpack_callback()' to\nprevent unnecessary tree traversal into the unpacked directory.\n\nReported-by: Shaoxuan Yuan \nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"unpack-trees: unpack new trees as sparse directories"}},{"before":null,"after":"032d5d306733bb3548a654cfa0a1400aa389f717","ref":"refs/heads/vdye/update-actions-ms","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"fixup! ci: run Scalar's Functional Tests\n\nUpdate the runner versions for the Scalar Functional tests to supported\nversions. For MacOS, update to the main supported version (macos-11). For\nUbuntu, ensure we're still testing the two latest LTS versions by replacing\n18.04 with 22.04.\n\nAlso update the installed dotnet version to the latest v3.1 patch version.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"fixup! ci: run Scalar's Functional Tests"}},{"before":null,"after":"0f0fe7cabfd9b3a0d283443eb2156c58004a7e90","ref":"refs/heads/bugfix/index-v4","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"read-cache: avoid misaligned reads in index v4\n\nThe process for reading the index into memory from disk is to first read its\ncontents into a single memory-mapped file buffer (type 'char *'), then\nsequentially convert each on-disk index entry into a corresponding incore\n'cache_entry'. To access the contents of the on-disk entry for processing, a\nmoving pointer within the memory-mapped file is cast to type 'struct\nondisk_cache_entry *'.\n\nIn index v4, the entries in the on-disk index file are written *without*\naligning their first byte to a 4-byte boundary; entries are a variable\nlength (depending on the entry name and whether or not extended flags are\nused). As a result, casting the 'char *' buffer pointer to 'struct\nondisk_cache_entry *' then accessing its contents in a 'SANITIZE=undefined'\nbuild can trigger the following error:\n\n read-cache.c:1886:46: runtime error: member access within misaligned\n address
for type 'struct ondisk_cache_entry', which requires 4\n byte alignment\n\nAvoid this error by reading fields directly from the 'char *' buffer, using\nthe 'offsetof' individual fields in 'struct ondisk_cache_entry'.\nAdditionally, add documentation describing why the new approach avoids the\nmisaligned address error, as well as advice on how to improve the\nimplementation in the future.\n\nReported-by: Jeff King \nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"read-cache: avoid misaligned reads in index v4"}},{"before":null,"after":"100c01e936cb331ab5b3c231dcd3050ea06e1868","ref":"refs/heads/feature/cache-tree-optimization","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"rebase: use 'skip_cache_tree_update' option\n\nEnable the 'skip_cache_tree_update' option in both 'do_reset()'\n('sequencer.c') and 'reset_head()' ('reset.c'). Both of these callers invoke\n'prime_cache_tree()' after 'unpack_trees()', so we can remove an unnecessary\ncache tree rebuild by skipping 'cache_tree_update()'.\n\nWhen testing with 'p3400-rebase.sh' and 'p3404-rebase-interactive.sh', the\nperformance change of this update was negligible, likely due to the\noperation being dominated by more expensive operations (like checking out\ntrees). However, since the change doesn't harm performance, it's worth\nkeeping this 'unpack_trees()' usage consistent with others that subsequently\ninvoke 'prime_cache_tree()'.\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"rebase: use 'skip_cache_tree_update' option"}},{"before":null,"after":"148cbf6e25bf5775baf52ddfa152d61496e7a2af","ref":"refs/heads/bugfix/repack-kept-pack","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"repack: respect --keep-pack with geometric repack\n\nUpdate 'repack' to ignore packs named on the command line with the\n'--keep-pack' option. Specifically, modify 'init_pack_geometry()' to treat\ncommand line-kept packs the same way it treats packs with an on-disk '.keep'\nfile (that is, skip the pack and do not include it in the 'geometry'\nstructure).\n\nWithout this handling, a '--keep-pack' pack would be included in the\n'geometry' structure. If the pack is *before* the geometry split line (with\nat least one other pack and/or loose objects present), 'repack' assumes the\npack's contents are \"rolled up\" into another pack via 'pack-objects'.\nHowever, because the internally-invoked 'pack-objects' properly excludes\n'--keep-pack' objects, any new pack it creates will not contain the kept\nobjects. Finally, 'repack' deletes the '--keep-pack' as \"redundant\" (since\nit assumes 'pack-objects' created a new pack with its contents), resulting\nin possible object loss and repository corruption.\n\nAdd a test ensuring that '--keep-pack' packs are now appropriately handled.\n\nCo-authored-by: Taylor Blau \nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"repack: respect --keep-pack with geometric repack"}},{"before":null,"after":"170636508dd5dd2f6501cbec0a962fca16962a94","ref":"refs/heads/vfs-next","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"fixup! pack-objects (mingw): demonstrate a segmentation fault with large deltas","shortMessageHtmlLink":"fixup! pack-objects (mingw): demonstrate a segmentation fault with la…"}},{"before":null,"after":"1a9faffaea11338909b51cf314086d3dd72b84bf","ref":"refs/heads/vdye/sparse-checkout-test-fails","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"t1092: add test for untracked files and directories\n\nAdd a test verifying that sparse-checkout (with and without sparse index\nenabled) treat untracked files & directories correctly when changing sparse\npatterns. Specifically, it ensures that 'git sparse-checkout set'\n\n* deletes empty directories outside the sparse cone\n* does _not_ delete untracked files outside the sparse cone\n\nSigned-off-by: Victoria Dye ","shortMessageHtmlLink":"t1092: add test for untracked files and directories"}},{"before":null,"after":"20ff6e18e01a1219f9f5ba3ef0b9db7e5d09972d","ref":"refs/heads/linux-deployment-update-test","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Get release by tag","shortMessageHtmlLink":"Get release by tag"}},{"before":null,"after":"220b1cc6b80de35d5a9092377d6879d042031bcc","ref":"refs/heads/vfs-2.26.2","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Merge pull request #270 from jeffhostetler/fix-deserialize-error-vfs\n\ndeserialize-status: silently fallback if we cannot read cache file","shortMessageHtmlLink":"Merge pull request git#270 from jeffhostetler/fix-deserialize-error-vfs"}},{"before":null,"after":"26f52f4e7cc51fbf0a6255a8ccae76126d26852d","ref":"refs/heads/features/fsmonitor-2.27.0","pushedAt":"2024-01-09T16:35:17.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"vdye","name":"Victoria Dye","path":"/vdye","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3619353?s=80&v=4"},"commit":{"message":"Merge upstreamable patches\n\nIncludes commits from these pull requests:\n\n\t#188\n\nSigned-off-by: Derrick Stolee ","shortMessageHtmlLink":"Merge upstreamable patches"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEafBmagA","startCursor":null,"endCursor":null}},"title":"Activity · vdye/git"}