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

[PATCH 4/4] git-remote: document the migration feature of the rename subcommand

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Nov 12, 2008, 17:11 UTC
Message-ID
<a8b13b05417ca3ecc360472c7c44e824402aa6e6.1226508805.git.vmiklos@frugalware.org>
In-Reply-To
<c3744d00a3d612a637cf520d2719492265e4f061.1226508805.git.vmiklos@frugalware.org>
Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
 Documentation/git-remote.txt |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
index 7b227b3..fad983e 100644
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@@ -66,6 +66,10 @@ was passed.
 
 Rename the remote named <old> to <new>. All remote tracking branches and
 configuration settings for the remote are updated.
++
+In case <old> and <new> are the same, and <old> is a file under
+`$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to
+the configuration file format.
 
 'rm'::
 
-- 
1.6.0.2
Previous: Miklos Vajna
Message 5 of 5 in “git-remote rename: support branches->config migration”
  1. 0/4 git-remote rename: support branches->config migrationMiklos Vajna, Nov 12, 2008
  2. 1/4 remote: add a new 'origin' variable to the structMiklos Vajna, Nov 12, 2008
  3. 2/4 git-remote rename: support remotes->config migrationMiklos Vajna, Nov 12, 2008
  4. 3/4 git-remote rename: support branches->config migrationMiklos Vajna, Nov 12, 2008
  5. 4/4 git-remote: document the migration feature of the rename subcommandMiklos Vajna, Nov 12, 2008

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.