First of all, my sincere apologies for the inordinate delay in reply.
The user who created the mess went on leave. By the time he was back,
I got stuck in some other issue. Later, I took the log of 'history'
command from his machine because i wanted to first simulate the
scenario before i could
On Fri, Feb 20, 2015 at 10:16:18PM -0700, Technext wrote:
Thanks Junio for the prompt reply! :) Yes, that's exactly how i would like
things to be. I'll definitely try to push this thing and see if this flow
can be implemented.
However, can you please guide me whether there's any way i could
On 23 Feb 2015, Kevin Daudt wrote:
On Fri, Feb 20, 2015 at 10:16:18PM -0700, Technext wrote:
Thanks Junio for the prompt reply! :) Yes, that's exactly how i would
like things to be. I'll definitely try to push this thing and see if
this flow can be implemented.
However, can you please
Thanks Junio for the prompt reply! :) Yes, that's exactly how i would like
things to be. I'll definitely try to push this thing and see if this flow
can be implemented.
However, can you please guide me whether there's any way i could have
figured out about the git reset command that the developer
On Fri, Feb 20, 2015 at 8:46 PM, Technext varuag.chha...@gmail.com wrote:
The biggest problem that I see here is that
every developer has the rights to commit, which I feel is not right.
Hmm, if you have some way to classify developers into two (or more?)
categories, what would you do instead?
5 matches
Mail list logo