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

Re: simple use case scenario for --read-tree and --write-tree with --prefix option

From
Junio C Hamano <junkio@cox.net>
Date
Jun 19, 2006, 07:52 UTC
Message-ID
<7vpsh5a8gs.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<cc723f590606190028t65c76c74t6a90d1dcec411598@mail.gmail.com>
"Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
> I searched the archives but didn't find anything. If i understand
> correctly the sub project idea is using the gitlink object type. So
> what is read-tree and write-tree with --prefix option supposed to
> achieve.

The --prefix option to read-tree was very useful when I did a hand merge of gitweb for example. I am reasonably sure clever people will find other uses as well.

Previous: Aneesh KumarNext: Aneesh Kumar
Message 2 of 5 in “simple use case scenario for --read-tree and --write-tree with --prefix option”
  1. Aneesh KumarJun 19, 2006
  2. Junio C HamanoJun 19, 2006
  3. Aneesh KumarJun 19, 2006
  4. Petr BaudisJun 19, 2006
  5. Aneesh KumarJun 19, 2006

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.