From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Mihamina Rakotomandimby <mihamina@gulfsat.mg>
Cc: git@vger.kernel.org
Subject: Re: workflow with blessed, lieutenant, and developers
Date: Mon, 09 Aug 2010 09:57:42 +0200 [thread overview]
Message-ID: <vpqr5i8dxqh.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20100809092152.5f32646a@packard.rktmb.org> (Mihamina Rakotomandimby's message of "Mon\, 9 Aug 2010 09\:21\:52 +0300")
Assuming you actually want what you want:
Mihamina Rakotomandimby <mihamina@gulfsat.mg> writes:
> 1°) What command line do developers use to push to me but not to the
> blessed (origin)?
For example:
git remote add submission <your repository URL>
and then, submit with
git push HEAD:submission/branch-name
> 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?
Actually, you have the choice between "push" and "don't push", and you
can complement the later with "git branch -D" to delete the branch.
> 3°) I push the merge of approved commits to the blessed repository:
> what keywords and git options?
What do you want that "git push" doesn't do?
Now, you may not really want this ;-). Here are some alternatives:
* Use a system like github/gitorious/giroco/gitolite, that allows you
to manage a set of repositories with shared storage, on a single
site. Take gitorious, for example. People would clone the blessed
repository (like http://gitorious.org/project/repo.git) online
(costs almost nothing thanks to shared storage). They get a remote
repository like http://git.gitorious.org/~user/project/own-repo.git.
Then get a local copy. They would push to
http://git.gitorious.org/~user/project/own-repo.git, notify you of
the changes (by email, or using gitorious itself), and you'd pull
from them and push to the blessed repository. This way, each user
has his own private local repository, and his submission repository.
You avoid people messing their submission with each other.
* Look at code review tools like gerrit. I've never used them so I
can't say much more.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-08-09 7:58 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
2010-08-09 7:57 ` Matthieu Moy [this message]
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=vpqr5i8dxqh.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--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).