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

multiple branch shallow clones and object sharing

From
SDSerhat Sevki Dincer <jfcgauss@gmail.com>
Date
Mar 6, 2011, 20:00 UTC
Message-ID
<AANLkTimo-Ba8dt5p7aDG8X1VJC=tQfricD=iJvcUw7_y@mail.gmail.com>

Hi, Say, I would like to get just the recent history of two branches of a big project with, for example: git clone -b REL-1_10_0_PATCHES --depth 99 git://git.postgresql.org/git/pgadmin3.git pgadmin-1.10 git clone -b REL-1_12_0_PATCHES --depth 299 git://git.postgresql.org/git/pgadmin3.git pgadmin-1.12

If the 1st one were not a shallow clone, we could have --referenced it in the 2nd command to avoid unnecassary downloads of many objects, but since the history of the project is very big we just want some recent history. Is the following commandline syntax too absurd/naive for a new feature of git :?

git clone -b REL-1_10_0_PATCHES --depth 99 -b REL-1_12_0_PATCHES --depth 299 git://git.postgresql.org/git/pgadmin3.git pgadmin-1.10 pgadmin-1.12

this is supposed to download the two branches simultaneously into two respective local directories, making any possible download savings along the way.

Thanks, Serhat

Message 1 of 1 in “multiple branch shallow clones and object sharing”
  1. Serhat Sevki DincerMar 6, 2011

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.