From: Heiko Voigt <heiko.voigt@mahr.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org, Jens Lehmann <Jens.Lehmann@mahr.de>
Subject: Re: Partial tree export and merging
Date: Thu, 25 Sep 2008 16:36:15 +0200 [thread overview]
Message-ID: <48DBA1DF.3050502@mahr.de> (raw)
In-Reply-To: <fcaeb9bf0809241051se24bcf7tb836d1b820e288d6@mail.gmail.com>
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 ?
> 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.
Heiko
next prev parent reply other threads:[~2008-09-25 14:38 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 [this message]
2008-09-25 14:51 ` Nguyen Thai Ngoc Duy
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=48DBA1DF.3050502@mahr.de \
--to=heiko.voigt@mahr.de \
--cc=Jens.Lehmann@mahr.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).