On 27 Jan 2011, at 14:47, Tony Finch wrote:
Oh man, and there was I thinking you were trying to be satirical.
I especially laughed at your advice on reverting changes.
"Boldly going forward 'cause we can't find reverse!"
Tony,
I'm always happy to present hard empirical data to hates-softwar
On 27 Jan 2011, at 12:50, Marco Von Ballmoos wrote:
On Jan 27, 2011, at 12:45 PM, Neil Brewitt wrote:
Nicholas,
Anyone who hates perforce is a victim of bad education or software religion.
I can't agree here. I'm a long-time user of Perforce as well and evangelized it
On 27 Jan 2011, at 11:49, Philip Newton wrote:
On Thu, Jan 27, 2011 at 12:45, Neil Brewitt wrote:
Reverts too difficult for you? Then don't revert changes. Use the software how
it's meant to be used.
Oh, right. I completely forgot that developers exist to serve tools
the way the
Nicholas,
Anyone who hates perforce is a victim of bad education or software religion.
It's faster, it's safer, it's lighter. It just works.
Reverts too difficult for you? Then don't revert changes. Use the software how
it's meant to be used. In a live perforce install for twenty developers I
Bash lets me work every day, despite its shortcomings.
Just start me on Finder.
Neil
PS and top posting.
On 19 Oct 2010, at 00:02, Daniel Pittman wrote:
Nicholas Clark writes:
Dear bash,
Why do you insist on hashing the paths to commands.
And never expiring the cache.
Or detecting that
On 27 Aug 2008, at 07:37, Joshua Juran wrote:
Perforce does not have branches.
The notion of a "branch" of development is implemented in different
ways by different SCM tools. For me, CVS' invisible branching scares
the hell out of me - it's too easy to get non-sticky stuff mixed with
st
