git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Frank Lichtenheld <frank@lichtenheld.de>,
	Git Mailing List <git@vger.kernel.org>,
	Martin Langhoff <martin.langhoff@gmail.com>
Subject: Re: [PATCH] cvsserver: Actually implement --export-all
Date: Sat, 16 Jun 2007 18:01:10 -0700	[thread overview]
Message-ID: <7vy7ij1jjd.fsf@assigned-by-dhcp.pobox.com> (raw)
In-Reply-To: <20070616235250.GA3231@steel.home> (Alex Riesen's message of "Sun, 17 Jun 2007 01:52:50 +0200")

Thanks.

      reply	other threads:[~2007-06-17  1:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15  1:01 [PATCH] cvsserver: Let --base-path and pserver get along just fine Frank Lichtenheld
2007-06-15  1:01 ` [PATCH] cvsserver: Actually implement --export-all Frank Lichtenheld
2007-06-16 23:52   ` Alex Riesen
2007-06-17  1:01     ` Junio C Hamano [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=7vy7ij1jjd.fsf@assigned-by-dhcp.pobox.com \
    --to=gitster@pobox.com \
    --cc=frank@lichtenheld.de \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    --cc=raa.lkml@gmail.com \
    /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).