[p4] svn revision properties p4 equiv?
De List. Man
listman at burble.net
Thu Jan 14 12:26:02 PST 2010
----- "Rick Macdonald" <rickmacd at shaw.ca> wrote:
> Now you say "the other part". Do you in fact want both?
> - to know after the fact which submits used the wrapper, and
> - to prevent submits that do not use the wrapper in the first place?
yes, i want to prevent submits that don't use my wrapper using "reasonable" means, and if someone really wants to get around this i'd at least like to be able to tell using a nightly cron check..
> If the prevention is absolute, which is difficult if not impossible,
> then the first is no longer required!
> I would simply go with the first requirement, and fire anybody who
> circumvents the required system. I assume Frank Cusack at fcusak.com
> that authority! (or is that not the actual place of business?)
> To understand better, I'm tempted to ask what the script does and what
> is the consequence of not using the wrapper?
hmm, thats a pretty long conversation in itself.. suffice to say i need it (and so do others apparently!)
> De List. Man wrote:
> > the other part of this is that i want to have the ability to stop a
> user submitting a change if they aren't going through my wrapper. so
> the process could be
> > 1) set an attribute on the file/s i'm checking in
> > 2) execute a pre-submit trigger to make sure the attribute is set on
> the file that's being submitted.
> > 3) if the file doesn't have the attribute reject the submit
> > is that doable in p4?
> > ----- Original Message -----
> > From: "Jeff A. Bowles" <jeff at vizim.com>
> > To: "Frank Cusack" <fcusack at fcusack.com>
> > Cc: "Rick Macdonald" <rickmacd at shaw.ca>, "De List. Man"
> <listman at burble.net>
> > Sent: Thursday, January 14, 2010 6:57:14 AM
> > Subject: Re: [p4] svn revision properties p4 equiv?
> > Rereading the OP, you're right.
> > Yet, this isn't that far off: add an attribute to the interesting
> revisions, and poll/query based on it using "p4 fstat"...
> > -Jeff Bowles
> > On Jan 14, 2010, at 6:47 AM, Frank Cusack wrote:
> >> On January 13, 2010 11:37:20 PM -0800 "Jeff A. Bowles"
> <jeff at vizim.com> wrote:
> >>> In "*git*", you can do a commit and include a '*symbolic name*'
> that is an
> >>> alias for the commit-number. Operations like "do the submit,
> >>> remember the entire shebang as release-2.5" could be done that
> >>> In Perforce parlance: Think "*p4 submit*" followed, immediately,
> by a *
> >>> label* operation to remember that specific changelist as part of a
> >>> name. (The user could, somehow, provide the label name.)
> >> Not at all what the OP asked for.
> > _______________________________________________
> > perforce-user mailing list - perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user