That was the title of a famous book by Joseph Heller.
http://www.amazon.com/exec/obidos/tg/detail/-/0684833395/002-0109254-6032057?v=glance
Alex
On Thu, 2004-07-01 at 08:50, John Casey wrote:
:) sorry.
Catch-22 is when no possible action can have a good result...sort of
damned if you do,
On Tue, 2004-06-29 at 23:27, John Casey wrote:
Catch-22 alleviated.
Could please someone explain a non-native speaker like me that
mysterious catch-22 term. Thanks folks,
--
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com
:) sorry.
Catch-22 is when no possible action can have a good result...sort of
damned if you do, damned if you don't to use another cliche.
HTH,
john
On Thu, 2004-07-01 at 08:36, Martin Skopp wrote:
On Tue, 2004-06-29 at 23:27, John Casey wrote:
Catch-22 alleviated.
Could please someone
: OT: What the hell is catch-22 [was Re: howto: request
committer status]
On Tue, 2004-06-29 at 23:27, John Casey wrote:
Catch-22 alleviated.
Could please someone explain a non-native speaker like me that
mysterious catch-22 term. Thanks folks,
--
Martin Skopp
Riege Software
Lovely, it's one of my favorite books ... :-)
-Original Message-
From: Peter Bright [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 01. Juli 2004 14:49
To: 'Maven Users List'
Subject: RE: What the hell is catch-22 [was Re: howto: request committer status]
It's a literary reference
Sounds like you just need read only access, you don't need commit for that.
Commit is to commit changes to CVS. People usually start out by submitting
patches. But if you're just doing a review, read only will work. Everyone
has read only, see the project info page of the maven website.
Hello Jason,
I appreciate the work you and several of your compatriots have done.
From my perspective it's moving in the right direction and I've seen
you around in several places for several years (I think your the same
person anyway).
I do know the etiquette for the apache group, though I
I think you're the first person who has ever asked for commit status, so
the answer is you don't request committer status, it will be offered
when someone feels you've earned it.
I think you and the others were a little hard on him. I got the impression
that he doesn't know how it works and
On Tue, 2004-06-29 at 16:43, Brill Pappin wrote:
How do I go about requesting commit status for this project?
It is bad etiquette to request committer status in OSS projects and
generally looked dimly upon. The normal course of action is you
contribute for a period of time and one of the
On Jun 29, 2004, at 17:10, Jason van Zyl wrote:
On Tue, 2004-06-29 at 16:43, Brill Pappin wrote:
How do I go about requesting commit status for this project?
It is bad etiquette to request committer status in OSS projects and
generally looked dimly upon. The normal course of action is you
On Tue, 2004-06-29 at 18:16, Craig S. Cottingham wrote:
On Jun 29, 2004, at 17:10, Jason van Zyl wrote:
On Tue, 2004-06-29 at 16:43, Brill Pappin wrote:
How do I go about requesting commit status for this project?
It is bad etiquette to request committer status in OSS projects and
No idea what patch, but it was probably me that rejected it. Sorry if
it caused an offence, but I always try to give a reason that something
is not suitable. If I didn't, or you don't think it's correct, you're
welcome to continue to debate it in the relevant JIRA issue, or take
it up on the -dev
Without getting into the merits of his patch, it's a little bit
ridiculous to expect to gain committer status immediately and with no
effort on the project. If he can't get the patch through, then he still
has the option to fork the war plugin. Catch-22 alleviated.
-john
On Tue, 2004-06-29 at
Brett,
AFAIK this is still purely hypothetical. Not to worry.
-j
On Tue, 2004-06-29 at 19:14, Brett Porter wrote:
No idea what patch, but it was probably me that rejected it. Sorry if
it caused an offence, but I always try to give a reason that something
is not suitable. If I didn't, or you
14 matches
Mail list logo
