All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Wyckoff <pw@padd.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Luke Diamand <luke@diamand.org>,
	git@vger.kernel.org
Subject: Re: [PATCHv3 02/11] git-p4: test debug macro
Date: Mon, 19 Dec 2011 17:35:17 -0800	[thread overview]
Message-ID: <20111220013517.GB20591@padd.com> (raw)
In-Reply-To: <7vwr9to8kk.fsf@alter.siamese.dyndns.org>

gitster@pobox.com wrote on Sun, 18 Dec 2011 13:48 -0800:
> You may have found this handy yourself, but I would rather not to see it
> here in the current form for multiple reasons.
> 
>  - Why "ctrl-c"? You are not even spawning shell from here but are having
>    the user interact with this state in the middle of a test from another
>    shell, no?
> 
>    Why not "When done, type <RET>" and have a "read junk" or something
>    instead? That would be a lot simpler and you do not have to worry about
>    portability with many lines of comments.
> 
>    An alternative is to spawn an interactive shell here, and change the
>    "Debug me" comment to say "ctrl-d when done".

Good point.  I'll get rid of all that trap business.

>  - This is not linked to the generic "debug" option "txxxx-name.sh -d".
>    Shouldn't you be extending test_debug so that it can go interactive,
>    give customized comments&insns (i.e. "cd $here" may be useful for test
>    scripts outside testing p4, but "P4PORT=..." would not be, so the user
>    of test_debug in t9800-git-p4.* needs customizability of the message).

That's good advice; each (set of) script(s) could customize as
needed.

The pain of having to track down the P4PORT, which varies with
each test script, was my main motivation for trying to automate
this.

I'll not resubmit this one until coming up with something
prettier.

> Also could we please rename p4 related tests in t/t98* series so that it
> is clear that they are about git-p4 from "ls t/" output (i.e. have them
> all have "git-p4" in their names)?

Sure.  That was a mistake.  We'll fix it up.

		-- Pete

  reply	other threads:[~2011-12-20  1:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 18:52 [PATCH 00/11] git-p4: asciidoc documentation and fixes Pete Wyckoff
2011-12-17 18:52 ` [PATCH 01/11] git-p4: introduce asciidoc documentation Pete Wyckoff
2011-12-17 18:52 ` [PATCH 02/11] git-p4: test debug macro Pete Wyckoff
2011-12-17 22:43   ` Luke Diamand
2011-12-18  1:36     ` [PATCHv2 " Pete Wyckoff
2011-12-18  3:26       ` Jonathan Nieder
2011-12-18 13:50         ` Pete Wyckoff
2011-12-18 14:06         ` [PATCHv3 " Pete Wyckoff
2011-12-18 17:10           ` Luke Diamand
2011-12-18 21:48           ` Junio C Hamano
2011-12-20  1:35             ` Pete Wyckoff [this message]
2011-12-17 18:52 ` [PATCH 03/11] git-p4: clone does not use --git-dir Pete Wyckoff
2011-12-17 18:52 ` [PATCH 04/11] git-p4: test cloning with two dirs, clarify doc Pete Wyckoff
2011-12-17 18:52 ` [PATCH 05/11] git-p4: document and test clone --branch Pete Wyckoff
2011-12-17 18:52 ` [PATCH 06/11] git-p4: honor --changesfile option and test Pete Wyckoff
2011-12-17 18:52 ` [PATCH 07/11] git-p4: document and test --import-local Pete Wyckoff
2011-12-17 18:52 ` [PATCH 08/11] git-p4: test --max-changes Pete Wyckoff
2011-12-17 18:52 ` [PATCH 09/11] git-p4: test --keep-path Pete Wyckoff
2011-12-17 18:52 ` [PATCH 10/11] git-p4: test and document --use-client-spec Pete Wyckoff
2011-12-17 18:52 ` [PATCH 11/11] git-p4: document and test submit options Pete Wyckoff

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=20111220013517.GB20591@padd.com \
    --to=pw@padd.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=luke@diamand.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.