All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-rebase.sh: Change .dotest directory to .git-dotest
Date: Wed, 06 Feb 2008 00:51:38 +0200	[thread overview]
Message-ID: <ejbrxbid.fsf@blue.sea.net> (raw)
In-Reply-To: alpine.LSU.1.00.0802052236220.8543@racer.site

* Tue 2008-02-05 Johannes Schindelin <Johannes.Schindelin@gmx.de>
* Message-Id: alpine.LSU.1.00.0802052236220.8543@racer.site
> On at least one machine (not the current one, because I was too lazy), I 
> have a git alias to call when the patch does not apply, to call another 
> program in turn which made it easier for me to integrate a non-applying 
> patch into the current working directory.
>
> And guess what: this script accesses .dotest/.  Yes, I know, it was 
> _prone_ to move.

If somebody has written scripts to do something with the internals, he
already knows the internals. I'm confident those can easily track the
changes. They are experts already if they use .dotest.

All good shell scripts test the conditions before they proceed. Like
in this case. Something:

    dir=.dotest

    [ -d "$dir" ] || { echo "No directory $dir" >&2; exit 1; }

Sloppy scripts are best left to script writers headache.

Jari

-- 
Welcome to FOSS revolution: we fix and modify until it shines

  reply	other threads:[~2008-02-05 22:53 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 [this message]
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
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=ejbrxbid.fsf@blue.sea.net \
    --to=jari.aalto@cante.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.