From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: restriction of pulls
Date: Fri, 09 Feb 2007 12:19:05 +0100 [thread overview]
Message-ID: <eqhl87$ut3$1@sea.gmane.org> (raw)
In-Reply-To: 200702091149.12462.duelli@melosgmbh.de
Christoph Duelli wrote:
> Is it possible to restrict a chechout, clone or a later pull to some
> subdirectory of a repository?
> (Background: using subversion (or cvs), it is possible to do a file or
> directory-restricted update.)
>
> Say, I have a repository containing 2 (mostly) independent projects
> A and B (in separate) directories:
> - R
> - A
> - B
> Is it possibly to pull all the changes made to B, but not those made to A.
> (Yes, I know that this causes trouble if there are dependencies into A.)
No, it is not possible. Moreover, it is not sensible, as it breaks atomicity
of a commit. Well, you can hack, but...
That said, there is experimental submodule (subproject) support
http://git.or.cz/gitwiki/SubprojectSupport
http://git.admingilde.org/tali/git.git/module2
(there was also proposal of more lightweight submodule support, but I don't
have a link to it), and you should have set A and B as submodules
(subprojects).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-09 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 10:49 restriction of pulls Christoph Duelli
2007-02-09 11:19 ` Jakub Narebski [this message]
2007-02-09 14:54 ` Johannes Schindelin
2007-02-09 15:32 ` Rogan Dawes
2007-02-09 16:19 ` Andy Parkins
2007-02-09 16:36 ` Rogan Dawes
2007-02-09 16:45 ` Andy Parkins
2007-02-09 17:32 ` Rogan Dawes
2007-02-10 9:59 ` Andy Parkins
2007-02-10 14:50 ` Johannes Schindelin
2007-02-12 13:58 ` Rogan Dawes
2007-02-12 14:13 ` Johannes Schindelin
2007-02-12 14:29 ` Rogan Dawes
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='eqhl87$ut3$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.