git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] RelNotes-1.7.2: cherry-pick and revert learned the same things

From
Christian Couder <chriscool@tuxfamily.org>
Date
Jul 1, 2010, 05:10 UTC
Message-ID
<20100701051028.2369.53975.chriscool@tuxfamily.org>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/RelNotes-1.7.2.txt |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/Documentation/RelNotes-1.7.2.txt b/Documentation/RelNotes-1.7.2.txt
index 8ed7406..53a71da 100644
--- a/Documentation/RelNotes-1.7.2.txt
+++ b/Documentation/RelNotes-1.7.2.txt
@@ -44,9 +44,12 @@ Updates since v1.7.1
    prepares to create a root commit that is not connected to any existing
    commit.
 
- * "git cherry-pick" learned to pick a range of commits (e.g. "cherry-pick
-   A..B"); this does not have nicer sequencing control "rebase [-i]" has,
-   though.
+ * "git cherry-pick" and "git revert" learned to pick a range of
+   commits (e.g. "cherry-pick A..B"); this does not have nicer
+   sequencing control "rebase [-i]" has, though.
+
+ * "git cherry-pick" and "git revert" learned --strategy option to
+   specify the merge strategy.
 
  * "git cvsserver" can be told to use pserver; its password file can be
    stored outside the repository.
@@ -92,8 +95,6 @@ Updates since v1.7.1
 
  * "git remote" learned "set-branches" subcommand.
 
- * "git revert" learned --strategy option to specify the merge strategy.
-
  * "git rev-list A..B" learned --ancestry-path option to further limit
    the result to the commits that are on the ancestry chain between A and
    B (i.e. commits that are not descendants of A are excluded).
-- 
1.7.2.rc0.223.g465131.dirty
Next: Peter Kjellerstedt
Message 1 of 2 in “RelNotes-1.7.2: cherry-pick and revert learned the same things”
  1. RelNotes-1.7.2: cherry-pick and revert learned the same thingsChristian Couder, Jul 1, 2010
  2. Peter KjellerstedtJul 1, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.