From: Christian Couder <christian.couder@gmail.com>
To: Ron Isaacson <isaacson.ljits@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: RPM spec file broken by README.md
Date: Fri, 1 Apr 2016 13:23:19 +0200 [thread overview]
Message-ID: <CAP8UFD101cKKMcTOxARnWkoNWp-waUMo3B4RH+Co9D9fkpQdfg@mail.gmail.com> (raw)
In-Reply-To: <CADrzLrOaeQXjWeCnZSJfWWyfr3kzgm59QvR6SeTiw_E2Xg7ugQ@mail.gmail.com>
Hi!
On Fri, Apr 1, 2016 at 7:35 AM, Ron Isaacson <isaacson.ljits@gmail.com> wrote:
> Hi everyone,
>
> I've noticed that "make rpm" is failing for 2.8.0 because README was
> replaced with README.md. This line in git.spec is the culprit:
>
> %doc README COPYING Documentation/*.txt
>
> Would it be possible to change this to README.md to match the source
> tree? The rpm packages build just fine with that change. Thank you
> very much!
Thanks for this bug report.
Would you care to send a patch?
next prev parent reply other threads:[~2016-04-01 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 5:35 RPM spec file broken by README.md Ron Isaacson
2016-04-01 7:10 ` [PATCH] git.spec: use README.md, not README Matthieu Moy
2016-04-01 11:23 ` Christian Couder [this message]
2016-04-01 11:24 ` RPM spec file broken by README.md Christian Couder
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=CAP8UFD101cKKMcTOxARnWkoNWp-waUMo3B4RH+Co9D9fkpQdfg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=isaacson.ljits@gmail.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 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.