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

[PATCH] git-relink.txt: describe more clearly how hard linking occurs

From
Brandon Casey <casey@nrlssc.navy.mil>
Date
Jan 11, 2008, 18:14 UTC
Message-ID
<4787B1FB.3020500@nrlssc.navy.mil>
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
---
 Documentation/git-relink.txt |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-relink.txt b/Documentation/git-relink.txt
index ccbda9f..06a3e32 100644
--- a/Documentation/git-relink.txt
+++ b/Documentation/git-relink.txt
@@ -7,12 +7,13 @@ git-relink - Hardlink common objects in local repositories
 
 SYNOPSIS
 --------
-'git-relink' [--safe] <dir> <dir> [<dir>]\*
+'git-relink' [--safe] <dir> [<dir>]\* <master_dir>
 
 DESCRIPTION
 -----------
-This will scan 2 or more object repositories and look for common objects, check
-if they are hardlinked, and replace one with a hardlink to the other if not.
+This will scan 1 or more object repositories and look for objects in common
+with a master repository. Objects not already hardlinked to the master
+repository will be replaced with a hardlink to the master repository.
 
 OPTIONS
 -------
-- 
1.5.4.rc2.84.gf85fd-dirty
Message 1 of 1 in “git-relink.txt: describe more clearly how hard linking occurs”
  1. git-relink.txt: describe more clearly how hard linking occursBrandon Casey, Jan 11, 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.