All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: RFT withdrawn (was Re: [RFT PATCH 0/5] Another round of build script tweaks)
Date: Tue, 3 May 2016 21:55:51 +0900	[thread overview]
Message-ID: <dfd9ba68-6653-d26e-65ed-01d098327417@gmail.com> (raw)
In-Reply-To: <9f8a3c0d-75fe-0b6f-733f-2134f67ccd6f@gmail.com>

On 2016/05/03 7:47, Akira Yokosawa wrote:
>>From 4ce174f3c72367fed945fb4448e294d205b8d88a Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiysw@gmail.com>
> Date: Tue, 3 May 2016 00:18:53 +0900
> Subject: [RFT PATCH 0/5]  Another round of build script tweaks
> 
> This series restructures build scripts rather radically. 
> My initial feeling was that [5/5] would be the most controversial,
> and placed at the end of the series.
> But in hindsight, [1/5] seems to be the most controversial one.
> 
> Anyway, I'd like people to try them and give feedback.
> 
> In commit 4038e781ed56 ("Improve behavior of build scripts"),
> I caused some regressions.  They were fixed soon after,
> but I think changes in build scripts need to be heavily tested
> before being pulled in.
> 
> Any feedback is welcome. Thanks.
> 
> Akira Yokosawa (5):
>   Further improvement of build scripts
>   Add font installation check
>   Add short name targets in Makefile
>   Add explanation of short name target in FAQ.txt
>   Make default target of Makefile overridable
> 
>  .gitignore            |   10 +-
>  FAQ.txt               |   23 +
>  Makefile              |  322 +--
>  contrib.tex           |   60 -
>  count/sig-theft.dot   |   19 +-
>  count/sig-theft.eps   |  457 ---
>  origpub.tex           |    8 -
>  qqz.tex               | 7707 -------------------------------------------------
>  utilities/eps2pdf.sh  |   12 +
>  utilities/runlatex.sh |    9 +
>  10 files changed, 181 insertions(+), 8446 deletions(-)
>  delete mode 100644 contrib.tex
>  delete mode 100644 count/sig-theft.eps
>  delete mode 100644 origpub.tex
>  delete mode 100644 qqz.tex
> 

As I reported in another mail, this series causes painful side-effects.
Please refrain from trying this series.

I'll resubmit v2 of this series soon.

Sorry for the trouble.

                                                  Thanks, Akira


  parent reply	other threads:[~2016-05-03 12:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 22:47 [RFT PATCH 0/5] Another round of build script tweaks Akira Yokosawa
2016-05-02 22:49 ` Akira Yokosawa
2016-05-02 22:56   ` [RFT PATCH 1/5] Further improvement of build scripts (was Re: [RFT PATCH 0/5] Another round of build script tweaks) Akira Yokosawa
2016-05-03 12:24     ` Akira Yokosawa
2016-05-02 22:57 ` [RFT PATCH 2/5] Add font installation check Akira Yokosawa
2016-05-02 22:59 ` [RFT PATCH 3/5] Add short name targets in Makefile Akira Yokosawa
2016-05-02 23:01 ` [RFT PATCH 4/5] Add explanation of short name target in FAQ.txt Akira Yokosawa
2016-05-02 23:03 ` [RFT PATCH 5/5] Make default target of Makefile overridable Akira Yokosawa
2016-05-03 12:55 ` Akira Yokosawa [this message]
2016-05-03 13:04   ` RFT withdrawn (was Re: [RFT PATCH 0/5] Another round of build script tweaks) Paul E. McKenney

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=dfd9ba68-6653-d26e-65ed-01d098327417@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=perfbook@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.