[Dev] Qt in Tizen - project proposal

Tomasz Olszak olszak.tomasz at gmail.com
Mon Dec 2 10:20:49 GMT 2013


2013/12/2 Łukasz Stelmach <l.stelmach at samsung.com>

> It was <2013-11-29 pią 07:28>, when Tomasz Olszak wrote:
> > 2013/11/29 Gaurav Kalra <gvkalra at gmail.com>
> >
> >> > From: Tomasz Olszak <olszak.tomasz at gmail.com>
> >> > Date: Thu, 28 Nov 2013 22:21:12 +0100
> >>
> >> > Subject: Re: [Dev] Qt in Tizen - project proposal
> >> > Hello all,
> >> > Yesterday Qt repositories in Tizen have been created. However I don't
> >> have privilige to populate them with upstream sources.
> >> > When I try to git push I get:
> >> >
> >> >
> >> > $ git push origin tizen
> >>
> >> I believe that should be:
> >> git push -f origin tizen
> >>
> >> > Counting objects: 3, done.
> >> > Writing objects: 100% (3/3), 208 bytes | 0 bytes/s, done.
> >> > Total 3 (delta 0), reused 0 (delta 0)
> >> > remote:
> >> > remote: Processing changes: refs: 1, done
> >> > To ssh://review.tizen.org/platform/upstream/qtchooser.git
> >> >  ! [remote rejected] tizen -> tizen (prohibited by Gerrit)
> >> > error: failed to push some refs to 'ssh://
> >> review.tizen.org/platform/upstream/qtchooser.git'
> >> >
> >> >
>
> [...]
> > Sorry, I should have been mentioned that I also tried with force switch
> and
> > the result is the same.
> >
> > git push -f origin tizen
> > Counting objects: 218, done.
> > Delta compression using up to 8 threads.
> > Compressing objects: 100% (88/88), done.
> > Writing objects: 100% (218/218), 61.83 KiB | 0 bytes/s, done.
> > Total 218 (delta 93), reused 208 (delta 90)
> > remote: Resolving deltas: 100% (93/93)
> > remote:
> > remote: Processing changes: refs: 1, done
> > To tizen:platform/upstream/qtchooser
> >  ! [remote rejected] tizen -> tizen (prohibited by Gerrit)
> > error: failed to push some refs to 'tizen:platform/upstream/qtchooser'
> >
> > And here's my:
> > .git/config
> > [core]
> >         repositoryformatversion = 0
> >         filemode = true
> >         bare = false
> >         logallrefupdates = true
> > [remote "origin"]
> >         url = tizen:platform/upstream/qtchooser
> >         fetch = +refs/heads/*:refs/remotes/origin/*
>
> That is because you can't (almost no one can) push directly to branches
> and bypass the review process.

I believe maintainer can.

>

Add:
>
>     push = refs/heads/tizen:refs/for/tizen
>
> to the above remote seciton. I'd recommend creating a script for cloning
> tizen repositories that will do some setup for you (push, commit-msg
> hook etc.)
>
This is normal workflow, when one changes something in tizen branch or
rebases with the upstream. Before that I would like to copy upstream data
into the tizen branch... e.g. qtbases .git directory contains 147MB of
data. I believe it is not recommended to pass it through gerrit. Could you
please correct me if I am wrong?
-- 
regards / pozdrawiam, Tomasz Olszak
Qt for Tizen | http://qt-project.org/wiki/Tizen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131202/6e4f1bbe/attachment-0001.html>


More information about the Dev mailing list