public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jonathan Wakely <jwakely@redhat.com>,
	"libstdc++" <libstdc++@gcc.gnu.org>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] gcc-changelog: Add libstdc++-v3/testsuite to wildcard prefixes
Date: Mon, 30 Nov 2020 11:58:49 +0000	[thread overview]
Message-ID: <CAH6eHdSGa3iHhWEPo7fuAOd80EBAVhY4hqHkCNGPFki_boNqHQ@mail.gmail.com> (raw)
In-Reply-To: <d64e7c70-6049-b336-520c-0a7b086924f9@suse.cz>

On Mon, 30 Nov 2020 at 09:44, Martin Liška <mliska@suse.cz> wrote:
>
> On 11/27/20 5:23 PM, Jonathan Wakely wrote:
> > This allows using "testsuite/*" in libstdc++-v3/ChangeLog entries, which
> > was one of the original motivations for adding wildcard support in the
> > first place:
> > https://gcc.gnu.org/pipermail/gcc/2020-June/232719.html
> >
> > contrib/ChangeLog:
> >
> >       * gcc-changelog/git_commit.py (wildcard_prefixes): Add libstdc++
> >       testsuite directory.
> >
> > OK to push?
>
> Hello.
>
> It's fine, please push it.

Done.

>
> >
> > This still doesn't actually meet my needs, because I'd like to be able
> > to do:
> >
> >       * testsuite/foo/*: Something for foo tests.
> >       * testsuite/bar/baz/*: Something for baz tests.
>
> Fixed by the patch that I've just pushed.
>
> >
> > So it would be nice if wildcards worked for any directory below a
> > wildcard prefix (as long as the directory actually exists).
>
> It works for me now:
>
> $ git show c41c8c19dcc17f319c1306424f8e7de4868ce037 --stat
> commit c41c8c19dcc17f319c1306424f8e7de4868ce037
> Author: Martin Liska <mliska@suse.cz>
> Date:   Mon Nov 30 10:35:05 2020 +0100
>
>      Test me.
>
>      libstdc++-v3/ChangeLog:
>
>              * doc/html/*: All you need is love.
>
>   libstdc++-v3/doc/html/manual/debug.html | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> $ git gcc-verify -p c41c8c19dcc17f319c1306424f8e7de4868ce037
> Checking c41c8c19dcc17f319c1306424f8e7de4868ce037: OK
> ------ libstdc++-v3/ChangeLog ------
> 2020-11-30  Martin Liska  <mliska@suse.cz>
>
>         * doc/html/*: All you need is love.
>
> Does it also work for you now? Or does it still have a limitation?

I can have a commit which only uses wildcards now, thanks.

I still can't use sub-directories with wildcards, but I can live with that.



> Thanks,
> Martin
>
> >
> > It also seems that I can't have a commit where all changes are
> > described by a wildcard entry. It seems to require a non-wildcard one
> > too. But that means I can't make changes to hundreds of tests without
> > also making some other change, or doing something like:
> >
> >       * testsuite/foo/foo-1.cc: A specific change.
> >          * testsuite/*: Likewise.
> >
> > I suppose I can live with the latter, but it would still be nice if
> > this worked:
> >
> >       * testsuite/foo/foo-1.cc: A specific change.
> >          * testsuite/foo/*: Likewise.
> >          * testsuite/bar/baz/*: Likewise.
> >
> > i.e. sub-directories below a wildcard prefix.
> >
> >
>

  reply	other threads:[~2020-11-30 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 16:23 Jonathan Wakely
2020-11-30  9:43 ` Martin Liška
2020-11-30 11:58   ` Jonathan Wakely [this message]
2020-11-30 12:14     ` Martin Liška
2020-11-30 12:23       ` Jonathan Wakely
2020-11-30 12:43         ` Martin Liška
2020-11-30 12:48           ` Jonathan Wakely

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=CAH6eHdSGa3iHhWEPo7fuAOd80EBAVhY4hqHkCNGPFki_boNqHQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).