Displaying 2 results from an estimated 2 matches for "labgc".
2016 May 17
2
[RFC] Helping release management
...'s just malformed or ignored, so you have to
reject *all* non-conforming), people with good intention will be the
ones hurt the most.
I don't think we want to start rejecting commits because of the
messages... or we'd have done by now.
cheers,
--renato
[1] http://arep.med.harvard.edu/labgc/jong/Fetch/SwissProtAll.html
[2] https://www.bugzilla.org/docs/4.4/en/html/api/Bugzilla/WebService/Bug.html
2016 May 17
2
[RFC] Helping release management
On 17 May 2016 at 02:07, Quentin Colombet via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Basically, the high-level status is:
> 1. Commits should state when they are fixes.
> 2. Bugs should be tracked in a PR.
Yup.
> None of these is a hard requirement but instead, best practices that we
> should remind to the contributors.
> For #1, I propose the attached patch for