git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karl Hasselström" <kha@treskal.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Peter Baumann <waste.manager@gmx.de>,
	git@vger.kernel.org, marc.zonzon@gmail.com
Subject: Re: how to filter a pull
Date: Fri, 4 May 2007 12:13:29 +0200	[thread overview]
Message-ID: <20070504101329.GA16446@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <7vwszpzs33.fsf@assigned-by-dhcp.cox.net>

On 2007-05-03 11:21:04 -0700, Junio C Hamano wrote:

> 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

  parent reply	other threads:[~2007-05-04 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 13:17 how to filter a pull marc.zonzon
2007-05-03 15:07 ` Peter Baumann
2007-05-03 18:21   ` Junio C Hamano
2007-05-03 19:32     ` marc zonzon
2007-05-03 20:37       ` Alex Riesen
2007-05-04 10:13     ` Karl Hasselström [this message]
2007-05-04 13:13       ` marc zonzon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070504101329.GA16446@diana.vm.bytemark.co.uk \
    --to=kha@treskal.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=marc.zonzon@gmail.com \
    --cc=waste.manager@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).