public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/55376] New: [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream Date: Sun, 18 Nov 2012 04:07:00 -0000 [thread overview] Message-ID: <bug-55376-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55376 Bug #: 55376 Summary: [asan] libsanitizer/README.gcc must contain the exact steps to do code changes and to port code from upstream Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassigned@gcc.gnu.org ReportedBy: konstantin.s.serebryany@gmail.com CC: dseketel@redhat.com, dvyukov@google.com, jakub@redhat.com, wmi@gcc.gnu.org We need to document the libsanitizer update process in libsanitizer/README.gcc Few things to cover: - The changes need to be approved by one of the maintainers (or is it obvious)? - Except for *really* trivial changes all patches should go through the upstream tree first. - When updating from upstream, the comment header should be tampered with (oh, my) - Ideally, we need to have a fully automated script to grab the upstream changes (including new/deleted/moved files, etc). Suggestions here? - What is the testing procedure when updating from upstream? (e.g. how do we avoid regressions on the platforms to which the maintainers have no access?)
next reply other threads:[~2012-11-18 4:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-18 4:07 konstantin.s.serebryany at gmail dot com [this message] 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 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@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).