From: Joshua Juran <jjuran@gmail.com>
To: Mihamina Rakotomandimby <mihamina@gulfsat.mg>
Cc: git@vger.kernel.org
Subject: Re: workflow with blessed, lieutenant, and developers
Date: Mon, 9 Aug 2010 00:42:16 -0700 [thread overview]
Message-ID: <172AD488-0169-440A-89FB-DD78584D244A@gmail.com> (raw)
In-Reply-To: <20100809092152.5f32646a@packard.rktmb.org>
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
next prev parent reply other threads:[~2010-08-09 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 6:21 workflow with blessed, lieutenant, and developers Mihamina Rakotomandimby
2010-08-09 7:42 ` Joshua Juran [this message]
2010-08-09 7:57 ` Matthieu Moy
2010-08-09 19:30 ` Jared Hance
2010-08-13 16:47 ` Enrico Weigelt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172AD488-0169-440A-89FB-DD78584D244A@gmail.com \
--to=jjuran@gmail.com \
--cc=git@vger.kernel.org \
--cc=mihamina@gulfsat.mg \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).