git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/4] t3400 (rebase): don't set GIT_AUTHOR_{NAME,EMAIL}
Date: Fri, 10 May 2013 10:53:16 -0400	[thread overview]
Message-ID: <CAPig+cSW39bnmKOeNDz0H5ZyNzPt3oCLnCUttaMJU9fGuKvJeQ@mail.gmail.com> (raw)
In-Reply-To: <1368196178-5807-2-git-send-email-artagnon@gmail.com>

On Fri, May 10, 2013 at 10:29 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> test-lib.sh already sets a sane GIT_AUTHOR_{NAME,EMAIL} for all test
> scripts to use.  Don't unnecessarily duplicate the work.
>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
>  t/t3400-rebase.sh | 4 ----
>  1 file changed, 4 deletions(-)
>
> diff --git a/t/t3400-rebase.sh b/t/t3400-rebase.sh
> index b58fa1a..a7ca2f1 100755
> --- a/t/t3400-rebase.sh
> +++ b/t/t3400-rebase.sh
> @@ -10,10 +10,6 @@ among other things.
>  '
>  . ./test-lib.sh
>
> -GIT_AUTHOR_NAME=author@name
> -GIT_AUTHOR_EMAIL=bogus@email@address

These values are intentionally bogus. Doesn't this change defeat the
purpose of 43c2325 (am: use get_author_ident_from_commit instead of
mailinfo when rebasing; 2010-06-16)?

> -export GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL
> -
>  test_expect_success 'prepare repository with topic branches' '
>         git config core.logAllRefUpdates true &&
>         echo First >A &&

  reply	other threads:[~2013-05-10 14:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 14:29 [PATCH 0/4] Trivial cleanups to t3400 (rebase) Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 1/4] t3400 (rebase): don't set GIT_AUTHOR_{NAME,EMAIL} Ramkumar Ramachandra
2013-05-10 14:53   ` Eric Sunshine [this message]
2013-05-10 14:56     ` Ramkumar Ramachandra
2013-05-10 17:34     ` Junio C Hamano
2013-05-10 14:29 ` [PATCH 2/4] t3400 (rebase): downcase a couple of test titles Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 3/4] t3400 (rebase): move lone statement into a test Ramkumar Ramachandra
2013-05-10 14:29 ` [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE Ramkumar Ramachandra
2013-05-10 14:38   ` Junio C Hamano
2013-05-10 14:46     ` Ramkumar Ramachandra
2013-05-10 15:42       ` Junio C Hamano
2013-05-10 16:42         ` Ramkumar Ramachandra
2013-05-10 17:51           ` Junio C Hamano
2013-05-10 18:06             ` Ramkumar Ramachandra
2013-05-10 18:08               ` Ramkumar Ramachandra
2013-05-10 19:07               ` Jonathan Nieder
2013-05-10 19:14                 ` Ramkumar Ramachandra
2013-05-10 19:16                   ` Jonathan Nieder
2013-05-10 21:06                     ` Junio C Hamano
2013-05-11 11:37                       ` Ramkumar Ramachandra
2013-05-13 23:05                         ` Jonathan Nieder

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=CAPig+cSW39bnmKOeNDz0H5ZyNzPt3oCLnCUttaMJU9fGuKvJeQ@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=artagnon@gmail.com \
    --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 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).