From: Nicholas Clark
Date: 23:31 on 16 Sep 2005
Subject: perforce file type metadata
$ p4 sync ...@24049
//depot/perl/opnames.h#16 - updating /home/nick/p4perl/perl/opnames.h
Can't clobber writable file /home/nick/p4perl/perl/opnames.h
//depot/perl/reentr.c#17 - updating /home/nick/p4perl/perl/reentr.c
Can't clobber writable file /home/nick/p4perl/perl/reentr.c
//depot/perl/reentr.h#19 - updating /home/nick/p4perl/perl/reentr.h
Can't clobber writable file /home/nick/p4perl/perl/reentr.h
$ p4 edit opnames.h reentr.c reentr.h
//depot/perl/opnames.h#19 - opened for edit
//depot/perl/reentr.c#23 - opened for edit
//depot/perl/reentr.h#25 - opened for edit
$ p4 revert opnames.h reentr.c reentr.h
//depot/perl/opnames.h#19 - was edit, reverted
//depot/perl/reentr.c#23 - was edit, reverted
//depot/perl/reentr.h#25 - was edit, reverted
$ ll opnames.h reentr.c reentr.h
-rw-r--r-- 1 nick nick 9378 Jun 9 10:43 opnames.h
-rw-r--r-- 1 nick nick 16323 Jul 8 17:22 reentr.c
-rw-r--r-- 1 nick nick 78393 Jul 5 19:21 reentr.h
$ p4 sync ...@24049
//depot/perl/opnames.h#16 - updating /home/nick/p4perl/perl/opnames.h
Can't clobber writable file /home/nick/p4perl/perl/opnames.h
//depot/perl/reentr.c#17 - updating /home/nick/p4perl/perl/reentr.c
Can't clobber writable file /home/nick/p4perl/perl/reentr.c
//depot/perl/reentr.h#19 - updating /home/nick/p4perl/perl/reentr.h
Can't clobber writable file /home/nick/p4perl/perl/reentr.h
Hello. You mean you can't cope with VERSION CONTROLLING YOUR METADATA?
No. No. No. That would be non-hateful.
So instead, if I attempt to sync back before this one:
$ p4 describe 24775
Change 24775 by nicholas@ship-in-a-bottle on 2005/06/09 09:22:18
Change perforce filetype from text to text+w (so regen.pl is happy)
Affected files ...
... //depot/perl/opnames.h#19 edit
... //depot/perl/reentr.c#22 edit
... //depot/perl/reentr.h#24 edit
Differences ...
==== //depot/perl/opnames.h#19 (text+w/text) ====
==== //depot/perl/reentr.c#22 (text+w/text) ====
==== //depot/perl/reentr.h#24 (text+w/text) ====
you bleat. FUCKING SHUT UP and JUST DAMN WELL WORK.
Please?
Is that too much to ask?
Nicholas Clark
From: hv Date: 03:13 on 17 Sep 2005 Subject: Re: perforce file type metadata Nicholas Clark <nick@xxxx.xxx> wrote: :$ p4 sync ...@24049 [...] :you bleat. FUCKING SHUT UP and JUST DAMN WELL WORK. : :Please? : :Is that too much to ask? I hear subversion works really well. :) H.
From: David Champion Date: 03:33 on 17 Sep 2005 Subject: Re: perforce file type metadata * On 2005.09.16, in <200509170213.j8H2D5O31304@xxx.xxxxx.xxx>, * "hv@xxxxx.xxx" <hv@xxxxx.xxx> wrote: > > I hear subversion works really well. :) I hear it's holy hell. But it's software, so I expect no more. And it's version-management software, so I super-duper expect no more. With a nod and a slight roll of eyes to the Senate Judiciary Subcomittee,
From: Nicholas Clark Date: 13:41 on 17 Sep 2005 Subject: Re: perforce file type metadata On Fri, Sep 16, 2005 at 09:33:11PM -0500, David Champion wrote: > * On 2005.09.16, in <200509170213.j8H2D5O31304@xxx.xxxxx.xxx>, > * "hv@xxxxx.xxx" <hv@xxxxx.xxx> wrote: > > > > I hear subversion works really well. :) > > I hear it's holy hell. But it's software, so I expect no more. And > it's version-management software, so I super-duper expect no more. It splats lots of pesky little .svn directories throughout my checkout, which confuses my tools no end, so that's hateful because I have to work round it. And as far as I know it doesn't work on VMS. (Which is more hateful than perforce) Then again, I suspect software on VMS is sufficiently hateful that would need a whole list just for it. Maybe HATE@xxxxxxxxxxxxxx.xxx, and then see how all the MUA software out there copes with the distinction... Nicholas Clark
From: Philip Newton Date: 14:02 on 17 Sep 2005 Subject: Re: perforce file type metadata On 9/17/05, Nicholas Clark <nick@xxxx.xxx> wrote: > Then again, I suspect software on VMS is sufficiently hateful that would = need > a whole list just for it. Maybe HATE@xxxxxxxxxxxxxx.xxx, and then see how > all the MUA software out there copes with the distinction... Then advertise it as HATE @ hates-software . com and see how many people can really parse RFC 2?822 addresses, including optional whitespace and comments between tokens. But yes. Hateful software that assumes it can just uppercase anything (why on earth would one want to do that anyway? If at all, wouldn't all-lowercase be easier to read? Oh, I forgot, you wouldn't then be able to spell "God" properly). I'll gnashingly admit that this is guaranteed to work for the bit to the right of the at-sign, but local-parts (with the exception of /postmaster/i) are *defined* to be case-sensitive. --=20 Philip Newton <philip.newton@xxxxx.xxx>
From: Nicholas Clark Date: 14:07 on 17 Sep 2005 Subject: Re: perforce file type metadata On Sat, Sep 17, 2005 at 03:02:11PM +0200, Philip Newton wrote: > On 9/17/05, Nicholas Clark <nick@xxxx.xxx> wrote: > > Then again, I suspect software on VMS is sufficiently hateful that would need > > a whole list just for it. Maybe HATE@xxxxxxxxxxxxxx.xxx, and then see how > > all the MUA software out there copes with the distinction... > > Then advertise it as HATE @ hates-software . com and see how many > people can really parse RFC 2?822 addresses, including optional > whitespace and comments between tokens. Mmm. This makes me think Spammers' scraping software is hateful if it can't. And differently hateful if it can. Nicholas Clark
Generated at 10:26 on 16 Apr 2008 by mariachi