From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFT] cvsserver: only allow checkout of branches
Date: Thu, 4 Oct 2007 17:55:02 -0400 [thread overview]
Message-ID: <20071004215502.GO2137@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710042248330.4174@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Thu, 4 Oct 2007, Frank Lichtenheld wrote:
> >
> > Should I sent a patch on top of this one or as a replacement?
>
> Better a replacement. Otherwise I have to fly to California with a brown
> paper bag over my HEAD.
That may be the safer way to travel. If your head is in a bag you
have no idea what sort of wait in the security line you are about
to face. Or what horrible movie they are showing you on the flight
both over *and* back.
--
Shawn.
prev parent reply other threads:[~2007-10-04 21:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 11:48 git-cvsserver commit trouble (unexpected end of file in client) Jan Wielemaker
2007-10-03 13:13 ` Jan Wielemaker
2007-10-03 14:57 ` Jan Wielemaker
2007-10-03 16:11 ` Johannes Schindelin
2007-10-03 18:42 ` Jan Wielemaker
2007-10-03 18:55 ` Johannes Schindelin
[not found] ` <200710032325.55128.wielemak@science.uva.nl>
[not found] ` <Pine.LNX.4.64.0710032311480.28395@racer.site>
2007-10-04 7:27 ` Jan Wielemaker
2007-10-04 11:18 ` git-cvsserver commit trouble BUG+Work-around Jan Wielemaker
2007-10-04 12:56 ` Johannes Schindelin
2007-10-04 13:06 ` Jan Wielemaker
2007-10-04 15:29 ` [PATCH/RFT] cvsserver: only allow checkout of branches Johannes Schindelin
2007-10-04 16:18 ` Frank Lichtenheld
2007-10-04 16:32 ` Johannes Schindelin
2007-10-04 17:06 ` Jan Wielemaker
2007-10-04 17:18 ` Johannes Schindelin
2007-10-04 18:04 ` Frank Lichtenheld
2007-10-04 21:15 ` Frank Lichtenheld
2007-10-04 21:49 ` Johannes Schindelin
2007-10-04 21:55 ` Shawn O. Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071004215502.GO2137@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).