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

Re: how to filter a pull

From
Karl Hasselström <kha@treskal.com>
Date
May 4, 2007, 10:13 UTC
Message-ID
<20070504101329.GA16446@diana.vm.bytemark.co.uk>
In-Reply-To
<7vwszpzs33.fsf@assigned-by-dhcp.cox.net>
On 2007-05-03 11:21:04 -0700, Junio C Hamano wrote:
Show 7 quoted lines
> If I were doing this today, I would probably use separate
> repositories, next to the primary project, to host the whole tree of
> other projects, adjust the build procedure of the primary project to
> borrow the whole of these other projects not just subtree -- and/or
> have appropriate symlinks in the primary project that point into
> relevant subtrees in the neighbouring repositories that host these
> other projects.

It should be straightforward (and efficient) to make a script that takes an existing branch and makes a parallel branch that contains only one subtree of the first branch. This derived branch can then be used as a subproject or whatever.

Or is there some obvious reason why this wouldn't work, or would be inconvenient?

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Alex RiesenNext: marc zonzon
Message 6 of 7 in “how to filter a pull”
  1. marc.zonzon@gmail.comMay 3, 2007
  2. Peter BaumannMay 3, 2007
  3. Junio C HamanoMay 3, 2007
  4. marc zonzonMay 3, 2007
  5. Alex RiesenMay 3, 2007
  6. Karl HasselströmMay 4, 2007
  7. marc zonzonMay 4, 2007

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.