OK I will read up on adding another upstream(1) for https://git-wip-us.apache.org/repos/asf/struts.git for direct commits and the egit logic for keeping the stuff in sync (upstream/upstream(1)/origin).
On 3 August 2016 at 11:28, Lukasz Lenart <lukaszlen...@apache.org> wrote: > 2016-08-03 12:15 GMT+02:00 Greg Huber <gregh3...@gmail.com>: > > Not that I understand much, if I try a push to my remote "upstream" it > says > > > > https://github.com/apache/struts: git-receive-pack not permitted > > > > Remote Fetch Specification: +refs/heads/*:refs/remotes/upstream/* > > Remote Fetch URL: https://github.com/apache/struts > > > > The way I think I have it set is to pull from upstream, merge, make > > changes, commit and push to my origin and create a pr for upstream. > > > > I can do a pr as its in by git repo now? > > You cannot push into "upstream", the upstream is a readonly repo you > have forked from, you should push into "origin" which is origin of > your fork not Struts' origin ;-) > > As you're a committer you should clone > https://git-wip-us.apache.org/repos/asf/struts.git and push small > changes there directly > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
