From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Re: Git enterprise setup on a large project
Date: Sun, 3 Apr 2011 20:31:15 +0200 [thread overview]
Message-ID: <20110403183115.GA28901@nibiru.local> (raw)
In-Reply-To: <BANLkTikv4h3GBGB+hTHjJyAqwEmqZETyEg@mail.gmail.com>
* Frederic JECKER <frederic.jecker@gmail.com> wrote:
> What could I do then ?
> - Use submodules ?
> - Create a blessed per-project repository and instead of a public
> repository for each developer create a per-project public and shared
> repository ?
> ...I'm a bit lost
Just think about who has to see whose commits ?
I guess, each project's codebase is accessed by a relatively
small number of people. So it IMHO would be natural to give
each project a separate (blessed) repository. The project
leader will merge (or cherry-pick) the blessed changes here,
and other merge-down or better rebase from there.
If there's some big mainline (the base for many other projects),
it should live in its own repository. BTW: you dont have to use
full clones - you could also fetch individual refs if you like.
Individual WIP branches probably dont necessarily need to be pushed
into the central project repos - devs could sync each other
selectively.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2011-04-06 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 19:50 Git enterprise setup on a large project Frederic JECKER
2011-04-03 18:31 ` Enrico Weigelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-02 19:53 Frederic JECKER
2011-04-02 22:45 ` Git " Ævar Arnfjörð Bjarmason
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=20110403183115.GA28901@nibiru.local \
--to=weigelt@metux.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).