Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jari Aalto <jari.aalto@cante.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] git-rebase.sh: Change .dotest directory to .git-dotest
Date: Wed, 6 Feb 2008 00:56:06 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LSU.1.00.0802060053570.8543@racer.site> (raw)
In-Reply-To: <1202253890.26144.8.camel@gaara.boston.redhat.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1119 bytes --]

Hi,

On Tue, 5 Feb 2008, Kristian Høgsberg wrote:

> I think there's a correlation here: anybody who's meddling with git 
> implementation details (yes, I'm talking about .dotest here) is probably 
> also subscribed to this list :)  Seriously though, in git there is often 
> no clear line between implementation details and supported features, so 
> it's way to easy to claim everything is set in stone and that the world 
> will break if we change it.  Especially if you've written a script that 
> happens to reach a little to far into the git guts.

I think you are being unfair here:

Imagine git-am stops somewhere because the patch fails.  What to do?  
Where to look?  What to fix?

Exactly.  You have _only_ one option.  You look into .dotest/.

So yes, it is an implementation detail.  But one that we could not 
_possibly_ hide.

What's so wrong with using a symlink first, trying hard not to break 
peoples' assumptions, then tell them that they should change their scripts 
(which they can do lazily now, since both .dotest/ _and_ .git/rebase/ 
are valid)?

How is being nice to people wrong?

Ciao,
Dscho

  reply	other threads:[~2008-02-06  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 15:14 [PATCH] git-rebase.sh: Change .dotest directory to .git-dotest Jari Aalto
2008-02-05 15:23 ` Mike Hommey
2008-02-05 15:28 ` Johannes Schindelin
2008-02-05 21:25   ` Jari Aalto
2008-02-05 21:49     ` Linus Torvalds
2008-02-05 22:41       ` Johannes Schindelin
2008-02-05 22:51         ` Jari Aalto
2008-02-05 23:04           ` Johannes Schindelin
2008-02-06  0:48             ` Junio C Hamano
2008-02-05 23:24         ` Kristian Høgsberg
2008-02-06  0:56           ` Johannes Schindelin [this message]
2008-02-06  1:37             ` Nicolas Pitre

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=alpine.LSU.1.00.0802060053570.8543@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jari.aalto@cante.net \
    --cc=krh@redhat.com \
    --cc=torvalds@linux-foundation.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