<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2015-12-22 5:44 GMT+01:00 Sérgio Basto <span dir="ltr"><<a href="mailto:sergio@serjux.com" target="_blank">sergio@serjux.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><div class="h5">On Sáb, 2015-12-12 at 12:56 +0100, Nicolas Chauvet wrote:<br>
> 2015-12-11 23:34 GMT+01:00 Sérgio Basto <<a href="mailto:sergio@serjux.com">sergio@serjux.com</a>>:<br>
> > On Seg, 2015-12-07 at 14:36 +0000, Sérgio Basto wrote:<br>
> > > Hi, <br>
> > ><br>
> > > On Qui, 2015-12-03 at 21:41 +0100, Nicolas Chauvet wrote:<br>
<br>
> I don't have any issue wih people using local branch as f23 to<br>
> separate content targetted for f24 using their master branch.<br>
> But you only need to fetch the content for f23 as the current master<br>
> branch in the git preview. git checkout master && git pull remote<br>
> f23.<br>
> people will need to rebase later when the f23 branch will be created<br>
> from git preview master.<br>
<br>
</div></div>OK , someone have branched f23 in his fork, I also don't see any<br>
problem. <br>
I think, add one branch (f23) or two (f24) in git preview, seems to me<br>
a very ship operation, a rpmfusion much better organized for all, even<br>
if we don't build anything and more simplify communication to<br>
contributors, also I think I can do this branching because is just git<br>
commands . <br>
<br>
I'm thinking do one wiki page with all instructions , we already got<br>
some examples how update things ... <br>
<br>
Today and thinking in a more simpler communication, someone send a pull<br>
request to <a href="https://github.com/rpmfusion" rel="noreferrer" target="_blank">https://github.com/rpmfusion</a> . With my updating method, of<br>
fetch git remote and merge it into preview , it makes that pull request<br>
was closed !, it looks like the pull request was made, when I just<br>
update git preview. So if I could receive the notifications of the pull<br>
requests for rpmfusion, it will be much more simpler communication,<br>
contributor doesn't have to do more , I can update git and block<br>
tracker to request builds , contributor when see his pull request<br>
closed , can consult the tracker of the builds, it easy . <br></blockquote><div> </div></div>It would be fine if we can forward pull request from github to the rpmfusion-commit list indeed. It could be an improvement, but I've found that, so it might not be as easy.<br><a href="http://blog.wikichoon.com/2014/04/github-doesnt-support-pull-request.html">http://blog.wikichoon.com/2014/04/github-doesnt-support-pull-request.html</a><br><br></div><div class="gmail_extra">Can't you subscribe to your personal email yourself to rpmfusion notification instead ?<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Nicolas (kwizart)<br></div></div>