From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brian Downing <bdowning@lavos.net>,
git@vger.kernel.org, Martin Langhoff <martin.langhoff@gmail.com>
Subject: Re: [PATCH] cvsserver: Fix for work trees
Date: Thu, 9 Aug 2007 09:45:07 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708090943340.21857@racer.site> (raw)
In-Reply-To: <7v1wedz2er.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 8 Aug 2007, Junio C Hamano wrote:
> This new world order is probably an improvement, and if the rules were
> like this from the beginning, it would have been much nicer. However,
> this _is_ a change of semantics in the middle of the road, and probably
> we will see many fallouts like this. Unfortunate... I am torn between
> a cleaner semantics and the short-term pain...
With your warning at the beginning of the ReleaseNotes, I think it would
be the same amount of pain if we did it later. It just would be...
later.
Ciao,
Dscho
prev parent reply other threads:[~2007-08-09 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 4:26 [PATCH] cvsserver: Fix for work trees Brian Downing
2007-08-09 5:45 ` Junio C Hamano
2007-08-09 8:45 ` Johannes Schindelin [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=Pine.LNX.4.64.0708090943340.21857@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.langhoff@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).