I'd come to that belief too, but I was hoping otherwise!
Thanks for the URL - I'll see where that gets me.
#!/mjh
-----Baris Sahin <[EMAIL PROTECTED]> wrote: -----
To: [EMAIL PROTECTED]
From: Baris Sahin <[EMAIL PROTECTED]>
Date: 09/03/2002 12:05PM
cc: [EMAIL PROTECTED]
Subject: Re: (no subject)
hi,cvs doesnt pass branch information to commitinfo file,so you cant use commitinfo for that.I had the same problem, and then solved with writing a patch for access control. Available at http://www.geocities.com/barissahin/
baris
--- [EMAIL PROTECTED] wrote:
"wr&j)b b'~/ !f ?+-w)ߡ
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
ɚXXߡ{m{j)fjb?wr
To: [EMAIL PROTECTED]
From: Baris Sahin <[EMAIL PROTECTED]>
Date: 09/03/2002 12:05PM
cc: [EMAIL PROTECTED]
Subject: Re: (no subject)
hi,cvs doesnt pass branch information to commitinfo file,so you cant use commitinfo for that.I had the same problem, and then solved with writing a patch for access control. Available at http://www.geocities.com/barissahin/
baris
--- [EMAIL PROTECTED] wrote:
A simple question. Can I discover on which branch a file is being committed from within
a script run from the commitinfo file?
Basically, I know how to apply per user/module access controls, but I would like
to extend this to include branch information so that certain teams are confined
to branches. We have in the past experienced code fixes being applied to the
wrong branch and it would be preferable for the technology to help people avoid
that mistake in the future.
#!/mjh
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
