Le 15/01/2012 09:16, Daniel Shahaf a écrit :
Forwarding back to list.
dcz wrote on Sun, Jan 15, 2012 at 09:02:06 +0100:
Le dimanche 15 janvier 2012 00:48:01, Daniel Shahaf a écrit :
dcz wrote on Tue, Jan 10, 2012 at 13:55:52 +0100:
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.
Le mercredi 11 janvier 2012 15:32:11, dcz a écrit :
Le mardi 10 janvier 2012 13:55:52, dcz a écrit :
Hello,
I already posted this on the tortoise ML
(http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2906737)
and the only answer I got was that this should be repo
Le mardi 10 janvier 2012 13:55:52, dcz a écrit :
Hello,
I already posted this on the tortoise ML
(http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2906737)
and the only answer I got was that this should be reported here.
I've been reading you all since a
Hello,
I already posted this on the tortoise ML
(http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2906737)
and the only answer I got was that this should be reported here.
I've been reading you all since a while now, and actually registered on the
tortoise ML to post
Le jeudi 27 octobre 2011 22:12:46, Daniel Shahaf a écrit :
Does it work with a 1.6 client?
Erwane Breton wrote on Thu, Oct 27, 2011 at 16:19:54 +0200:
i CAN commit with
Tortoise 1.6.15
I guess he can.
Sorry Johan, I hit reply to instead of reply to list by accident (I'm
getting lazy since so many list do send the mails themselves)
Le 16/03/2011 10:02, Johan Corveleyn a écrit :
You are right, the locking of big trees in a Subversion working copy
is very expensive, especially on Windows and/or
Le 22/02/2010 06:58, Srilakshmanan, Lakshman a écrit :
Hi Dcz,
One point of clarification. Each JD does ** not ** have their own branch.
Each ** change ** has a branch. If the change is large and more than one
developer is working on the change, they will all work in the same branch.
Hello
écrit :
Hi dcz,
You can write a pre-commit hook or use AuthzSVNAccessFile to restrict
commit into trunk by only Senior Developers. This way the Junior
developer can perform his work in the branch and requests the Senior
Developer to review and merge his code back into trunk in preparation
for relea
Le 17/02/2010 18:34, Ryan Schmidt a écrit :
On Feb 17, 2010, at 08:36, dcz wrote:
Le 17/02/2010 15:24, Andy Levy a écrit :
There is no "dry run" for a commit. It's conceivable that you could
check the user ID in the pre-commit, and if the committer is
Le 17/02/2010 15:24, Andy Levy a écrit :
On Wed, Feb 17, 2010 at 09:19, dcz wrote:
Thanks for responding.
I was hopping that someone did put something together to handle this.
It looks like doable with a pre-commit hook that would have a look in a db
(or a file) to find out if the user is
17, 2010 at 08:17, dcz wrote:
Hello,
Here is what I'm trying to do : some user (let's call them junior developer)
should require their commit to be authorized by other (senior developer)
before they would actually be committed.
Since I saw this feature on an svn (though I do not ad
#x27;t tell how it is done, but it's svn for sure) and found it
pretty useful, I was a bit surprised not to be able to find any topic
about it after hours a googling.
Would be very nice if someone could share thoughts about how to set such
feature up.
Regards,
dcz
12 matches
Mail list logo
