From: Sylvain Rabot <sylvain@abstraction.fr>
To: git@vger.kernel.org
Subject: Re: Can I enforce required approval on some files
Date: Tue, 20 Jul 2010 22:45:07 +0200 [thread overview]
Message-ID: <1279658706.2519.12.camel@kheops> (raw)
In-Reply-To: <AANLkTinQI9eBnwjzPhYHMM8XZ0ODfHJ1qiZJrNWQWUno@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1584 bytes --]
On Tue, 2010-07-20 at 13:22 -0700, Dominik Gront wrote:
> Dear Group,
>
> I have been a happy SVN user for quite a long time, but now I miss
> some functionality in Subversion. I wonder if it could be done in git.
> If so, I convert to git right away :-)
>
> There are some files in our repository that all their modification
> need to be approved by a project leader. In general the desired
> behavior would be (examples given in svn commands) :
> - user runs "svn ci"
> - some files have status "pending" or "waiting for approval"
> - anyone can do "svn up", modifications to the pending files are not
> retrieved, project leader can get the modified versions
> - project leader accepts the changes
> - anyone running "svn ci" sees all the modifications
>
> Best,
> Tim
Hi,
Git itself does not allow what you want but the workflow used to work
with git does.
Each developer work and on a "copy" of the "blessed" repository (the one
checked out in svn, cloned in git) so it does not matter if
modifications done to a file need approval or not. Once the developer is
happy with his work he has to send his commit(s) to the person(s) in
charge of maintaining the project and this/those people will review the
changes and push (commit in svn language) them to the "blessed"
repository if they are ok with the changes made.
With git, if not used like svn, all modifications need approval.
You can read more about git's distributed workflow here :
http://progit.org/book/ch5-1.html
Regards.
--
Sylvain Rabot <sylvain@abstraction.fr>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-07-20 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 20:22 Can I enforce required approval on some files Dominik Gront
2010-07-20 20:45 ` Bruce Stephens
2010-07-20 20:45 ` Sylvain Rabot [this message]
2010-07-20 22:03 ` Jakub Narebski
2010-07-21 0:42 ` Ævar Arnfjörð Bjarmason
2010-07-21 7:51 ` Jakub Narebski
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=1279658706.2519.12.camel@kheops \
--to=sylvain@abstraction.fr \
--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).