From: Patrick Venture <venture@google.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Alexander Amelkin <a.amelkin@yadro.com>,
gmills@linux.vnet.ibm.com, "Tanous, Ed" <ed.tanous@intel.com>
Subject: Re: Proposals for commit log policy
Date: Tue, 4 Sep 2018 16:38:03 -0700 [thread overview]
Message-ID: <CAO=notzk_+Q_Pg4xcxzDL=Ux3gyMb2iE0pfSgygDw32wzBHB=w@mail.gmail.com> (raw)
In-Reply-To: <5755FBD3-3D78-4E3A-8F50-D4976EE3B2B2@fuzziesquirrel.com>
On Tue, Sep 4, 2018 at 1:20 PM Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
>
>
>
> > On Aug 28, 2018, at 6:20 PM, Tanous, Ed <ed.tanous@intel.com> wrote:
> >
> >>
> >> I object too. I don't think the benefit of manual bumps is worth the effort.
> >>
> >
> > Another vote for "I don't think it's worth the effort".
> >
> > Automatic bumps keep us up to date and make breakages happen and get fixed faster. I would actually prefer that every gerrit review creates a manual bump to make sure the complete system builds with their given component change, but I realize this is hard to do.
> >
> > -Ed
>
> The autobump script stopped working when we switched to yocto-style subtrees.
>
> I fixed it up (by re-writing it in python…it was in Perl) and re-deployed, given
> all the objections.
Yay. No more perl!
>
> -brad
next prev parent reply other threads:[~2018-09-04 23:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 12:29 Proposals for commit log policy Alexander Amelkin
2018-08-22 15:01 ` Gunnar Mills
2018-08-23 8:23 ` Alexander Amelkin
2018-08-22 20:39 ` Tanous, Ed
2018-08-23 8:44 ` Alexander Amelkin
2018-08-28 22:40 ` Tanous, Ed
2018-08-22 23:58 ` Joel Stanley
2018-08-28 10:29 ` Brad Bishop
2018-08-28 15:43 ` Andrew Geissler
2018-08-28 16:13 ` Patrick Venture
2018-08-28 17:44 ` Gunnar Mills
2018-08-28 22:20 ` Tanous, Ed
2018-08-28 22:43 ` Kun Yi
2018-09-04 20:20 ` Brad Bishop
2018-09-04 23:38 ` Patrick Venture [this message]
2018-09-06 13:13 ` Alexander Amelkin
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='CAO=notzk_+Q_Pg4xcxzDL=Ux3gyMb2iE0pfSgygDw32wzBHB=w@mail.gmail.com' \
--to=venture@google.com \
--cc=a.amelkin@yadro.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed.tanous@intel.com \
--cc=gmills@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.