From: Heiko Voigt <heiko.voigt@mahr.de>
To: git@vger.kernel.org
Cc: Jens Lehmann <Jens.Lehmann@mahr.de>
Subject: Partial tree export and merging
Date: Wed, 24 Sep 2008 15:58:07 +0200 [thread overview]
Message-ID: <48DA476F.1070700@mahr.de> (raw)
In-Reply-To: <48D9FACB.20901@mahr.de>
Hallo,
I am currently facing a challenge for adding limited access to a git
repository for the i18n and documentation (language) team. Our
repository contains *.html and *.loc files which are located along with
the code. The language team should not see the code. At the same time a
developer using the full tree needs to be able to contribute to the i8n
files.
To archieve this I would like to extract a repository that only contains
the documentation and localization files which can be used by the i8n
and doc team. This should be regularly merged into the development (with
code) repository.
My idea of a solution would be to export patches only for the specific
files and import them into a seperate empty repository/branch using
git-format-patch and git-am. This seperate repository then itself then
could be imported again with a normal merge operation. Has a anyone
already solved such a problem or other ideas how to solve this ?
cheers Heiko
next parent reply other threads:[~2008-09-24 14:36 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 ` Heiko Voigt [this message]
2008-09-24 14:39 ` Partial tree export and merging 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
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=48DA476F.1070700@mahr.de \
--to=heiko.voigt@mahr.de \
--cc=Jens.Lehmann@mahr.de \
--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 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).