public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebpop at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37372] [graphite] SCoP detection splits bbs / Define SCoPs with single entry and exit edge
Date: Mon, 29 Sep 2008 14:48:00 -0000 [thread overview]
Message-ID: <20080929144648.2832.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37372-15673@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from sebpop at gmail dot com 2008-09-29 14:46 -------
Subject: Re: [graphite] SCoP detection splits bbs / Define SCoPs with single
entry and exit edge
> ------- Comment #7 from grosser at gcc dot gnu dot org 2008-09-29 13:14 -------
> Committed SVN 140746.
I see that in http://gcc.gnu.org/viewcvs?view=rev&revision=140746
you forgot to include in the changelog a line like this:
PR tree-optimization/37372
that would have automatically included the commit message in the bugzilla bug.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37372
prev parent reply other threads:[~2008-09-29 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 16:04 [Bug middle-end/37372] New: " grosser at gcc dot gnu dot org
2008-09-04 16:06 ` [Bug middle-end/37372] " grosser at gcc dot gnu dot org
2008-09-05 16:21 ` spop at gcc dot gnu dot org
2008-09-11 16:48 ` spop at gcc dot gnu dot org
2008-09-11 16:53 ` spop at gcc dot gnu dot org
2008-09-18 16:27 ` grosser at gcc dot gnu dot org
2008-09-18 16:35 ` grosser at gcc dot gnu dot org
2008-09-26 7:00 ` grosser at gcc dot gnu dot org
2008-09-29 13:16 ` grosser at gcc dot gnu dot org
2008-09-29 14:46 ` Sebastian Pop
2008-09-29 14:48 ` sebpop at gmail dot com [this message]
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=20080929144648.2832.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).