From 2efbb7f5218d5ca9d50cbcb86a365a08b2981d77 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 10 Oct 2018 09:20:03 +0900 Subject: [PATCH] Declare that the next one will be named 2.20 Signed-off-by: Junio C Hamano --- RelNotes => Documentation/RelNotes/2.20.0.txt | 0 RelNotes | 168 +------------------------- 2 files changed, 1 insertion(+), 167 deletions(-) copy RelNotes => Documentation/RelNotes/2.20.0.txt (100%) rewrite RelNotes (100%) mode change 100644 => 120000 diff --git a/RelNotes b/Documentation/RelNotes/2.20.0.txt similarity index 100% copy from RelNotes copy to Documentation/RelNotes/2.20.0.txt diff --git a/RelNotes b/RelNotes deleted file mode 100644 index 007bc065dd..0000000000 --- a/RelNotes +++ /dev/null @@ -1,167 +0,0 @@ -Git Release Notes -================= - -Backward Compatibility Notes ----------------------------- - - * "git branch -l " used to be a way to ask a reflog to be - created while creating a new branch, but that is no longer the - case. It is a short-hand for "git branch --list " now. - - * "git push" into refs/tags/* hierarchy is rejected without getting - forced, but "git fetch" (misguidedly) used the "fast forwarding" - rule used for the refs/heads/* hierarchy; this has been corrected, - which means some fetches of tags that did not fail with older - version of Git will fail without "--force" with this version. - - -Updates since v2.19 -------------------- - -UI, Workflows & Features - - * Running "git clone" against a project that contain two files with - pathnames that differ only in cases on a case insensitive - filesystem would result in one of the files lost because the - underlying filesystem is incapable of holding both at the same - time. An attempt is made to detect such a case and warn. - - * "git checkout -b newbranch [HEAD]" should not have to do as much as - checking out a commit different from HEAD. An attempt is made to - optimize this special case. - - * "git rev-list --stdin