summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes-1.6.1.1.txt
diff options
context:
space:
mode:
authorNicolas Pitre <nico@fluxnic.net>2010-09-06 20:29:57 -0400
committerJunio C Hamano <gitster@pobox.com>2010-09-06 17:41:18 -0700
commit761e742d69296393804e9a942263e86ece369257 (patch)
tree024ef23b84b09f8e5b59ec28731fffea4ba2130b /Documentation/RelNotes-1.6.1.1.txt
parent7505ae272bad53c6451f34ff5f04ad24f29b6dd9 (diff)
downloadgit-761e742d69296393804e9a942263e86ece369257.tar.gz
Documentation: move RelNotes into a directory of their own
There are 108 of them already. That's a bit more than one third of all the files in the Documentation directory already, and still growing. Signed-off-by: Nicolas Pitre <nico@fluxnic.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes-1.6.1.1.txt')
-rw-r--r--Documentation/RelNotes-1.6.1.1.txt59
1 files changed, 0 insertions, 59 deletions
diff --git a/Documentation/RelNotes-1.6.1.1.txt b/Documentation/RelNotes-1.6.1.1.txt
deleted file mode 100644
index 8c594ba02f..0000000000
--- a/Documentation/RelNotes-1.6.1.1.txt
+++ /dev/null
@@ -1,59 +0,0 @@
-GIT v1.6.1.1 Release Notes
-==========================
-
-Fixes since v1.6.1
-------------------
-
-* "git add frotz/nitfol" when "frotz" is a submodule should have errored
- out, but it didn't.
-
-* "git apply" took file modes from the patch text and updated the mode
- bits of the target tree even when the patch was not about mode changes.
-
-* "git bisect view" on Cygwin did not launch gitk
-
-* "git checkout $tree" did not trigger an error.
-
-* "git commit" tried to remove COMMIT_EDITMSG from the work tree by mistake.
-
-* "git describe --all" complained when a commit is described with a tag,
- which was nonsense.
-
-* "git diff --no-index --" did not trigger no-index (aka "use git-diff as
- a replacement of diff on untracked files") behaviour.
-
-* "git format-patch -1 HEAD" on a root commit failed to produce patch
- text.
-
-* "git fsck branch" did not work as advertised; instead it behaved the same
- way as "git fsck".
-
-* "git log --pretty=format:%s" did not handle a multi-line subject the
- same way as built-in log listers (i.e. shortlog, --pretty=oneline, etc.)
-
-* "git daemon", and "git merge-file" are more careful when freopen fails
- and barf, instead of going on and writing to unopened filehandle.
-
-* "git http-push" did not like some RFC 4918 compliant DAV server
- responses.
-
-* "git merge -s recursive" mistakenly overwritten an untracked file in the
- work tree upon delete/modify conflict.
-
-* "git merge -s recursive" didn't leave the index unmerged for entries with
- rename/delete conflicts.
-
-* "git merge -s recursive" clobbered untracked files in the work tree.
-
-* "git mv -k" with more than one erroneous paths misbehaved.
-
-* "git read-tree -m -u" hence branch switching incorrectly lost a
- subdirectory in rare cases.
-
-* "git rebase -i" issued an unnecessary error message upon a user error of
- marking the first commit to be "squash"ed.
-
-* "git shortlog" did not format a commit message with multi-line
- subject correctly.
-
-Many documentation updates.