On Aug 8, 2010, at 11:21 PM, Mihamina Rakotomandimby wrote:
I would like to setup a similar thing but with
- Only one lieutenant (me)
In Linux terminology, you would be the benevolent dictator, not the
lieutenant. The lieutenants are those you trust to submit good patches.
- A blessed repository where I am the only one to push to
Okay, though I might use the term 'official'.
- Developers who push to me (the lieutenant)
Developers shouldn't push directly into your working repo. If you
don't want to use pull requests (where a developer tells you when a
branch is ready for you to pull into your own repo) then you can have
a centralized bare Git repository for them to push to. Either they
will push completed branches which you then merge into mainline (which
is essentially the same as the pull request model, except the
developers are sharing a repo for this purpose), or the developers
themselves will do the merging in the developer repo, which you then
pull into your working repo, and after vetting it push to the offical
repo.
Developers pull/clone from the blessed repository.
I initially clone from the blessed repository.
1°) What command line do developers use to push to me but not to the
blessed (origin)?
2°) After they pushed to me, I have the choice to "approve" or
"reject"
a commit: what is the keyword and git option for that?
3°) I push the merge of approved commits to the blessed repository:
what keywords and git options?
If you're going to manage a project, you need to spend enough time
learning how Git works that you can answer these questions yourself.
There are multiple good resources online. I suggest starting with a
tutorial, and then experimenting to see what works and what doesn't
before you actually try to start working for real. Along the way
you'll find Google very helpful.
Josh
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html