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>
65 lines
2.4 KiB
Plaintext
65 lines
2.4 KiB
Plaintext
Git v1.8.0.1 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.8.0
|
|
------------------
|
|
|
|
* The configuration parser had an unnecessary hardcoded limit on
|
|
variable names that was not checked consistently.
|
|
|
|
* The "say" function in the test scaffolding incorrectly allowed
|
|
"echo" to interpret "\a" as if it were a C-string asking for a
|
|
BEL output.
|
|
|
|
* "git mergetool" feeds /dev/null as a common ancestor when dealing
|
|
with an add/add conflict, but p4merge backend cannot handle
|
|
it. Work it around by passing a temporary empty file.
|
|
|
|
* "git log -F -E --grep='<ere>'" failed to use the given <ere>
|
|
pattern as extended regular expression, and instead looked for the
|
|
string literally.
|
|
|
|
* "git grep -e pattern <tree>" asked the attribute system to read
|
|
"<tree>:.gitattributes" file in the working tree, which was
|
|
nonsense.
|
|
|
|
* A symbolic ref refs/heads/SYM was not correctly removed with "git
|
|
branch -d SYM"; the command removed the ref pointed by SYM
|
|
instead.
|
|
|
|
* Earlier we fixed documentation to hyphenate "remote-tracking branch"
|
|
to clarify that these are not a remote entity, but unhyphenated
|
|
spelling snuck in to a few places since then.
|
|
|
|
* "git pull --rebase" run while the HEAD is detached tried to find
|
|
the upstream branch of the detached HEAD (which by definition
|
|
does not exist) and emitted unnecessary error messages.
|
|
|
|
* The refs/replace hierarchy was not mentioned in the
|
|
repository-layout docs.
|
|
|
|
* Sometimes curl_multi_timeout() function suggested a wrong timeout
|
|
value when there is no file descriptors to wait on and the http
|
|
transport ended up sleeping for minutes in select(2) system call.
|
|
A workaround has been added for this.
|
|
|
|
* Various rfc2047 quoting issues around a non-ASCII name on the
|
|
From: line in the output from format-patch have been corrected.
|
|
|
|
* "git diff -G<pattern>" did not honor textconv filter when looking
|
|
for changes.
|
|
|
|
* Bash completion script (in contrib/) did not correctly complete a
|
|
lazy "git checkout $name_of_remote_tracking_branch_that_is_unique"
|
|
command line.
|
|
|
|
* RSS feed from "gitweb" had a xss hole in its title output.
|
|
|
|
* "git config --path $key" segfaulted on "[section] key" (a boolean
|
|
"true" spelled without "=", not "[section] key = true").
|
|
|
|
* "git checkout -b foo" while on an unborn branch did not say
|
|
"Switched to a new branch 'foo'" like other cases.
|
|
|
|
Also contains other minor fixes and documentation updates.
|