From 42ee99943c41ea841ba7fe64aa35bbcdeab579d2 Mon Sep 17 00:00:00 2001 From: Jens Lehmann Date: Fri, 10 May 2013 01:51:51 -0700 Subject: [PATCH] Created history (textile) --- history.textile | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 history.textile diff --git a/history.textile b/history.textile new file mode 100644 index 0000000..f487d6d --- /dev/null +++ b/history.textile @@ -0,0 +1,33 @@ +*Issues already solved and merged into Junio's Repo:* + +* Since git 1.8.2: +** Tracked floating submodules are supported in core git through the new @--remote@ option for @git submodule update@ and the new @--branch@ option for @git submodule add@ +* Since git 1.8.1: +** @git rm@ removes submodules from index and work tree (unless they contain a .git directory) +** @git submodule add@ learned the @--name@ option so the user can choose the name for a submodule (e.g. when its name clashes with that of a submodule which was present at the same path earlier in history but was removed). +* Since git 1.7.11: +** @git rebase --continue@ works if the commit only contains submodule changes. +** @git push@ learned the --recurse-submodules=on-demand option +* Since git 1.7.8: +** The @update@ option learned the value @none@, which disables @submodule init@ and @submodule update@ +** The git directory of a newly cloned submodule is stored in the .git directory of the superproject; the submodules work tree contains only a gitfile. This is the first step towards recursive checkout, as it enables us to remove a submodule directory (part of Frederik Gustafsson's 2011 GSoC project) +* Since git 1.7.7: +** @git push@ learned the @--recurse-submodules=check@ option which errors out when trying to push a superproject commit where the submodule changes are not pushed (part of Frederik Gustafsson's 2011 GSoC project) +* Since git 1.7.5: +** @fetch@ runs recursively on submodules by default when new commits have been recorded for them in the superproject +* Since git 1.7.4: +** Recursive fetching of submodules can be enabled via command line option or configuration. +* Since git 1.7.3: +** Add the "ignore" config option for the default behaviour of @git diff@ and @git status@. Both .git/config and .gitmodules are parsed for this option; the value set in .git/config. will override that from .gitmodules +** Add a global config option to control when a submodule is considered dirty (written by Dscho) +** Better support for merging of submodules (thanks to Heiko Voigt for writing that) +* Since git 1.7.2: +** Add parameters to the @--ignore-submodules@ option for @git diff@ and @git status@ to control when a submodule is considered dirty +* Since git 1.7.1: +** Show the reason why working directories of submodules are dirty (untracked content and/or modified content) in superproject +* Since git 1.7.0: +** @git status@ and @git diff*@ show submodules with untracked or modified files in their work tree as "dirty" +** @git gui@: New popup menu for submodule diffs +* Since git 1.6.6: +** New @--submodule@ option to @git diff@ (many thanks to Dscho for writing the core part!) +** Display of submodule summaries instead of plain hashes in @git gui@ and @gitk@ -- 2.26.2