public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55376] [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream Date: Tue, 20 Nov 2012 07:23:00 -0000 [thread overview] Message-ID: <bug-55376-4-limc4iMAg2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55376-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 --- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-11-20 07:23:26 UTC --- > === > All changes in this directory should be pre-approved by one of the maintainers. > Trivial and urgent fixes (portability, build fixes, etc) may go directly to the > gcc tree. All non-trivial changes, functionality improvements, etc should go > through the upstream tree first and then be merged back to the gcc tree. > > === The first sentence is odd, since all changes must already be approved as per the GCC rules, but the rest is reasonable. And it's GCC, not gcc, like LLVM. > I also want to have a semi-automated way to pull the updates from upstream. > What is the preferred scripting language? Is bash (python, perl) ok? If it runs on your machine, why asking? > When pulling a new update, what text do we expect in the ChangeLog? > Is the upstream SVN revision enough, or we want to copy all commit messages? Ideally a script could parse the commit messages on the LLVM side and yield a GNU-compatible ChangeLog; the granularity could be the file instead of the function. That being said, I don't know what LLVM commit messages look like, so this might not really work.
next prev parent reply other threads:[~2012-11-20 7:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-18 4:07 [Bug other/55376] New: " konstantin.s.serebryany at gmail dot com 2012-11-18 5:18 ` [Bug other/55376] " xinliangli at gmail dot com 2012-11-18 9:30 ` ebotcazou at gcc dot gnu.org 2012-11-18 18:47 ` konstantin.s.serebryany at gmail dot com 2012-11-19 22:58 ` ebotcazou at gcc dot gnu.org 2012-11-20 5:41 ` konstantin.s.serebryany at gmail dot com 2012-11-20 7:23 ` ebotcazou at gcc dot gnu.org [this message] 2012-11-20 10:17 ` manu at gcc dot gnu.org 2012-11-21 4:24 ` konstantin.s.serebryany at gmail dot com 2012-11-23 10:57 ` [Bug sanitizer/55376] " konstantin.s.serebryany at gmail dot com 2012-11-23 12:45 ` konstantin.s.serebryany at gmail dot com 2012-11-23 12:57 ` konstantin.s.serebryany at gmail dot com
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=bug-55376-4-limc4iMAg2@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).