From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Heiko Voigt" <heiko.voigt@mahr.de>
Cc: git@vger.kernel.org, "Jens Lehmann" <Jens.Lehmann@mahr.de>
Subject: Re: Partial tree export and merging
Date: Thu, 25 Sep 2008 21:51:10 +0700 [thread overview]
Message-ID: <fcaeb9bf0809250751x403a4b31vf05cdaba04563bbc@mail.gmail.com> (raw)
In-Reply-To: <48DBA1DF.3050502@mahr.de>
On 9/25/08, Heiko Voigt <heiko.voigt@mahr.de> wrote:
> 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
> > 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
prev parent reply other threads:[~2008-09-25 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ACF330629DFB034AB290061C320F43460836E082@GOEMAILBE02.europe.mahr.lan>
[not found] ` <48D9FACB.20901@mahr.de>
2008-09-24 13:58 ` Partial tree export and merging Heiko Voigt
2008-09-24 14:39 ` Shawn O. Pearce
2008-09-24 15:05 ` Heiko Voigt
2008-09-24 15:13 ` Shawn O. Pearce
2008-09-24 17:51 ` Nguyen Thai Ngoc Duy
2008-09-25 14:36 ` Heiko Voigt
2008-09-25 14:51 ` Nguyen Thai Ngoc Duy [this message]
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=fcaeb9bf0809250751x403a4b31vf05cdaba04563bbc@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Jens.Lehmann@mahr.de \
--cc=git@vger.kernel.org \
--cc=heiko.voigt@mahr.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).