Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
33 lines
1.3 KiB
Plaintext
33 lines
1.3 KiB
Plaintext
Git v2.0.2 Release Notes
|
|
========================
|
|
|
|
* Documentation for "git submodule sync" forgot to say that the subcommand
|
|
can take the "--recursive" option.
|
|
|
|
* Mishandling of patterns in .gitignore that has trailing SPs quoted
|
|
with backslashes (e.g. ones that end with "\ ") have been
|
|
corrected.
|
|
|
|
* Recent updates to "git repack" started to duplicate objects that
|
|
are in packfiles marked with .keep flag into the new packfile by
|
|
mistake.
|
|
|
|
* "git clone -b brefs/tags/bar" would have mistakenly thought we were
|
|
following a single tag, even though it was a name of the branch,
|
|
because it incorrectly used strstr().
|
|
|
|
* "%G" (nothing after G) is an invalid pretty format specifier, but
|
|
the parser did not notice it as garbage.
|
|
|
|
* Code to avoid adding the same alternate object store twice was
|
|
subtly broken for a long time, but nobody seems to have noticed.
|
|
|
|
* A handful of code paths had to read the commit object more than
|
|
once when showing header fields that are usually not parsed. The
|
|
internal data structure to keep track of the contents of the commit
|
|
object has been updated to reduce the need for this double-reading,
|
|
and to allow the caller find the length of the object.
|
|
|
|
* During "git rebase --merge", a conflicted patch could not be
|
|
skipped with "--skip" if the next one also conflicted.
|