I've got a patch ready for review. It's Bazel code for building the Java/Android targets.
I'll push it as a draft, but should I do it on the 1.4-rel branch or master or ??? Gregg On Mon, Apr 23, 2018 at 12:10 PM, Nash, George <george.n...@intel.com> wrote: > NOTE: when using refs/drafts/master only people that have been added as > reviewers will be able to see the patch. > > > > *From:* iotivity-dev-boun...@lists.iotivity.org [mailto: > iotivity-dev-boun...@lists.iotivity.org] *On Behalf Of *Gregg Reynolds > *Sent:* Monday, April 23, 2018 8:01 AM > *To:* Mats Wichmann <m...@wichmann.us> > *Cc:* iotivity-dev <iotivity-dev@lists.iotivity.org> > *Subject:* Re: [dev] Patch without jenkins > > > > thanks! > > > > On Sun, Apr 22, 2018 at 5:34 PM, Mats Wichmann <m...@wichmann.us> wrote: > > On 04/22/2018 01:35 PM, Gregg Reynolds wrote: > > Is there any way to submit a patch for inspection only, without involving > > Jenkins? > > > > just submit it as a draft. > > I've got an alias for this that I use: > > [aliases] > pushexp = push origin HEAD:refs/drafts/master > > (as opposed to refs/for/master, which kicks off Jenkins) > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > > >
