Re: Partial tree export and merging
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Sep 25, 2008, 14:51 UTC
- Message-ID
- <fcaeb9bf0809250751x403a4b31vf05cdaba04563bbc@mail.gmail.com>
- In-Reply-To
- <48DBA1DF.3050502@mahr.de>
On 9/25/08, Heiko Voigt <heiko.voigt@mahr.de> wrote:
Show 11 quoted lines
> Nguyen Thai Ngoc Duy schrieb: > > > That could be done with (under-developing) sparse checkout. Basically > > language team's people do "git clone > --sparse-checkout='*.loc:*.html' > > your-repo.git". Then they only have *.loc and *.html files in working > > directory. When they commit, all other files are unchanged. Developers > > merge to have updated *.log/html as usual. > > > > Where is that option ? Or are you suggesting me to implement it ?
As I said, it is being developed. It should not be used in production environment yet but if you want to try, you can get it from here
http://repo.or.cz/w/git/pclouds.git in branch sparse-checkout
Show 8 quoted lines
> > I have a question though: is language team allowed to checkout/modify > > files other than *.loc and *.html? > > > > Well in an ideal world they should only have access to the "language" > files. But it is not crucial for us if they get access to the source. Its > more an issue of user friendlyness. The revision control which is in place > at the moment does allow them to selectively check out those files.
Thanks. Just wanted to know the scenario that sparse checkout could be used.
-- Duy