public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: rjohnston@sgi.com
Cc: shhuiw@gmail.com, xfs@oss.sgi.com
Subject: Re: [PATCH] Fix typo from commit 0c5e67e4 "xfstests 273: fix a typo"
Date: Thu, 07 Mar 2013 08:56:34 -0600	[thread overview]
Message-ID: <5138AAA2.70308@sgi.com> (raw)
In-Reply-To: <20130307124125.435047948@sgi.com>

On 03/07/13 06:41, rjohnston@sgi.com wrote:
> When updating the patch, the redirect was incorrect.
>
> Reported-by: Wang Sheng-Hui<shhuiw@gmail.com>
> Signed-off-by: Rich Johnston<rjohnston@sgi.com>
>
> ---
>
>   273 |    2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: b/273
> ===================================================================
> --- a/273
> +++ b/273
> @@ -92,7 +92,7 @@ _porter()
>   		exit
>   	fi
>
> -	cp -r $SCRATCH_MNT/origin $SCRATCH_MNT/sub_$_suffix>$seq.full 2>>&1
> +	cp -r $SCRATCH_MNT/origin $SCRATCH_MNT/sub_$_suffix>>$seq.full 2>&1
>   	if [ $? -ne 0 ]
>   	then
>   		echo "_porter $_suffix not complete"
>


The original patch looked okay:

    http://oss.sgi.com/archives/xfs/2013-02/msg00518.html

Should the bad patch be reverted and the original one put in?

--Mark.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-07 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130307124102.821208303@sgi.com>
2013-03-07 12:41 ` [PATCH] Fix typo from commit 0c5e67e4 "xfstests 273: fix a typo" rjohnston
2013-03-07 14:56   ` Mark Tinguely [this message]
2013-03-07 15:48     ` Rich Johnston

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=5138AAA2.70308@sgi.com \
    --to=tinguely@sgi.com \
    --cc=rjohnston@sgi.com \
    --cc=shhuiw@gmail.com \
    --cc=xfs@oss.sgi.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