Re: [gitorious] Disable Check In's via command line

2013-01-30 Thread Marius Mårnes Mathiesen

Chris Holden writes:
 Is it possible to disable checkin's for a repo via the command line during
 a release and then renable it after the release is finished?

Since Git is distributed, there's no way you can control what individual
users do to their local clones of a repository, but it should be
possible to temporarily stop yourself from committing to your clone
(although it seems a little strange). If you're referring to temporarily
restricting access to a remote being pushed to, that's not something
that's supported by Gitorious.


Cheers,
- Marius

-- 
-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [gitorious] Disable Check In's via command line

2013-01-30 Thread Chris Holden
 Marius

Yes I meant pushing to remote sorry.  We have a group of devs who have 
interrupted releases by checking in during the release.

Instead of waiting they want to fix it programmatically.

Thank you!

Sent from my iPhone

On Jan 30, 2013, at 4:41 AM, Marius Mårnes Mathiesen 
marius.mathie...@gmail.com wrote:

 
 Chris Holden writes:
 Is it possible to disable checkin's for a repo via the command line during
 a release and then renable it after the release is finished?
 
 Since Git is distributed, there's no way you can control what individual
 users do to their local clones of a repository, but it should be
 possible to temporarily stop yourself from committing to your clone
 (although it seems a little strange). If you're referring to temporarily
 restricting access to a remote being pushed to, that's not something
 that's supported by Gitorious.
 
 
 Cheers,
 - Marius
 
 -- 
 -- 
 To post to this group, send email to gitorious@googlegroups.com
 To unsubscribe from this group, send email to
 gitorious+unsubscr...@googlegroups.com
 
 --- 
 You received this message because you are subscribed to the Google Groups 
 Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [gitorious] Disable Check In's via command line

2013-01-30 Thread Christian Johansen
Chris,

sounds like what you really need is a branching model where you don't
cut releases from the same branch that people are working from. We're
using http://nvie.com/posts/a-successful-git-branching-model/

Our master is the current release, which is also in production on
gitorious.org. 'next' is our main development branch. When there's a
release coming up, we will make a branch e.g. release-2.4.7. Only bug
fixes go onto that branch. When it's ready for deployment, we merge it
into master, tag/deploy, and then back to 'next'. Any commits happening
in the release process would go to 'next', and thus not interfere with
the release process.

You don't have to follow this route exactly, but I do believe your
problem is a social one, not a technical one - i.e. you need _some_
system to protect releases, and branches are the perfect tool.

Christian

Chris Holden writes:

  Marius

 Yes I meant pushing to remote sorry.  We have a group of devs who have 
 interrupted releases by checking in during the release.

 Instead of waiting they want to fix it programmatically.

 Thank you!

 Sent from my iPhone

 On Jan 30, 2013, at 4:41 AM, Marius Mårnes Mathiesen 
 marius.mathie...@gmail.com wrote:


 Chris Holden writes:
 Is it possible to disable checkin's for a repo via the command line during
 a release and then renable it after the release is finished?

 Since Git is distributed, there's no way you can control what individual
 users do to their local clones of a repository, but it should be
 possible to temporarily stop yourself from committing to your clone
 (although it seems a little strange). If you're referring to temporarily
 restricting access to a remote being pushed to, that's not something
 that's supported by Gitorious.


 Cheers,
 - Marius

 --
 --
 To post to this group, send email to gitorious@googlegroups.com
 To unsubscribe from this group, send email to
 gitorious+unsubscr...@googlegroups.com

 ---
 You received this message because you are subscribed to the Google Groups 
 Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.



 --

-- 
-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re: [gitorious] Disable Check In's via command line

2013-01-30 Thread Chris Holden
Christian

Yes our problem is very much a social one, I was just verifying.

Time to educate again. :)

Sent from my iPhone

On Jan 30, 2013, at 5:55 AM, Christian Johansen chrisj...@gmail.com wrote:

 Chris,
 
 sounds like what you really need is a branching model where you don't
 cut releases from the same branch that people are working from. We're
 using http://nvie.com/posts/a-successful-git-branching-model/
 
 Our master is the current release, which is also in production on
 gitorious.org. 'next' is our main development branch. When there's a
 release coming up, we will make a branch e.g. release-2.4.7. Only bug
 fixes go onto that branch. When it's ready for deployment, we merge it
 into master, tag/deploy, and then back to 'next'. Any commits happening
 in the release process would go to 'next', and thus not interfere with
 the release process.
 
 You don't have to follow this route exactly, but I do believe your
 problem is a social one, not a technical one - i.e. you need _some_
 system to protect releases, and branches are the perfect tool.
 
 Christian
 
 Chris Holden writes:
 
 Marius
 
 Yes I meant pushing to remote sorry.  We have a group of devs who have 
 interrupted releases by checking in during the release.
 
 Instead of waiting they want to fix it programmatically.
 
 Thank you!
 
 Sent from my iPhone
 
 On Jan 30, 2013, at 4:41 AM, Marius Mårnes Mathiesen 
 marius.mathie...@gmail.com wrote:
 
 
 Chris Holden writes:
 Is it possible to disable checkin's for a repo via the command line during
 a release and then renable it after the release is finished?
 
 Since Git is distributed, there's no way you can control what individual
 users do to their local clones of a repository, but it should be
 possible to temporarily stop yourself from committing to your clone
 (although it seems a little strange). If you're referring to temporarily
 restricting access to a remote being pushed to, that's not something
 that's supported by Gitorious.
 
 
 Cheers,
 - Marius
 
 --
 --
 To post to this group, send email to gitorious@googlegroups.com
 To unsubscribe from this group, send email to
 gitorious+unsubscr...@googlegroups.com
 
 ---
 You received this message because you are subscribed to the Google Groups 
 Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
 
 --
 
 -- 
 -- 
 To post to this group, send email to gitorious@googlegroups.com
 To unsubscribe from this group, send email to
 gitorious+unsubscr...@googlegroups.com
 
 --- 
 You received this message because you are subscribed to the Google Groups 
 Gitorious group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to gitorious+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
-- 
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
Gitorious group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitorious+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.