Re: Re: Updates to gitolite progress

Am Donnerstag, 29. März 2012 um 00:53:28, schrieb Pavel Sanda sa...@lyx.org Abdelrazak Younes wrote: On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the

Re: Re: Updates to gitolite progress

Am Donnerstag, 29. März 2012 um 00:53:28, schrieb Pavel Sanda > Abdelrazak Younes wrote: > > On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: > >> Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : > >>> There is also a 2.0.x branch in your first clone, so you can just > >>>

Re: Updates to gitolite progress

On Thu, Mar 29, 2012 at 12:53 AM, Pavel Sanda sa...@lyx.org wrote: Abdelrazak Younes wrote: On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master

Re: Updates to gitolite progress

On Thu, Mar 29, 2012 at 12:53 AM, Pavel Sanda wrote: > Abdelrazak Younes wrote: >> On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: >>> Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the

Re: Updates to gitolite progress

On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both the

Re: Updates to gitolite progress

Abdelrazak Younes wrote: On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I

Re: Updates to gitolite progress

On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both the

Re: Updates to gitolite progress

Abdelrazak Younes wrote: > On 21/03/2012 17:44, Jean-Marc Lasgouttes wrote: >> Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : >>> There is also a 2.0.x branch in your first clone, so you can just >>> cherry-pick the commit to master directly onto this 2.0.x branch, and >>> push from there.

Re: Updates to gitolite progress

Lars Gullik Bj?nnes wrote: | 1. Checkout full repo | git clone g...@git.lyx.org:lyx trunk | 2. Full mirror of branch as well, not through clone | cp -r trunk branch; cd branch No... (perhaps... it does not seem optimal, does not take advantage that things are on same fs f.ex.))

Re: Updates to gitolite progress

Le 22/03/12 09:44, Pavel Sanda a écrit : It seems to me absurd that people who are not sure how to commit or even use ssh keys are adviced to read about git internals or play with git remote. Please, be polite with me! I may be an older person, but I know how to use ssh keys :) JMarc

Re: Updates to gitolite progress

On Thu, Mar 22, 2012 at 9:44 AM, Pavel Sanda sa...@lyx.org wrote: Lars Gullik Bj?nnes wrote: | 1. Checkout full repo | git clone g...@git.lyx.org:lyx trunk | 2. Full mirror of branch as well, not through clone | cp -r trunk branch; cd branch No... (perhaps... it does not

Re: Updates to gitolite progress

Jean-Marc Lasgouttes wrote: Le 22/03/12 09:44, Pavel Sanda a écrit : It seems to me absurd that people who are not sure how to commit or even use ssh keys are adviced to read about git internals or play with git remote. Please, be polite with me! I may be an older person, but I know how to

Re: Updates to gitolite progress

Lars Gullik Bj?nnes wrote: > | 1. Checkout full repo > | git clone g...@git.lyx.org:lyx trunk > | 2. Full mirror of branch as well, not through clone > | cp -r trunk branch; cd branch > > No... > (perhaps... it does not seem optimal, does not take advantage that > things are on same fs

Re: Updates to gitolite progress

Le 22/03/12 09:44, Pavel Sanda a écrit : It seems to me absurd that people who are not sure how to commit or even use ssh keys are adviced to read about git internals or play with git remote. Please, be polite with me! I may be an older person, but I know how to use ssh keys :) JMarc

Re: Updates to gitolite progress

On Thu, Mar 22, 2012 at 9:44 AM, Pavel Sanda wrote: > Lars Gullik Bj?nnes wrote: > > | 1. Checkout full repo > > | git clone g...@git.lyx.org:lyx trunk > > | 2. Full mirror of branch as well, not through clone > > | cp -r trunk branch; cd branch > > > > No... > >

Re: Updates to gitolite progress

Jean-Marc Lasgouttes wrote: > Le 22/03/12 09:44, Pavel Sanda a écrit : >> It seems to me absurd that people who are not sure how to commit or >> even use ssh keys are adviced to read about git internals or play >> with git remote. > > Please, be polite with me! I may be an older person, but I know

Re: Updates to gitolite progress

Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in home/lyx, you can clone this with git clone -s -b 2.0.x home/lyx home/lyx20x This will clone your repo, but it will reuse the objects.

Re: Updates to gitolite progress

Op 21-3-2012 15:51, Jean-Marc Lasgouttes schreef: Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in home/lyx, you can clone this with git clone -s -b 2.0.x home/lyx home/lyx20x This

Re: Updates to gitolite progress

There has to be a simple way to commit a patch to branch (please tell me there is!). I forgot to mention: Ideally, if we do it the git-way completely, you would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x will automatically be merged into the master. This can be

Re: Updates to gitolite progress

Le 21/03/2012 16:56, Vincent van Ravesteijn a écrit : There has to be a simple way to commit a patch to branch (please tell me there is!). I forgot to mention: Ideally, if we do it the git-way completely, you would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x will

Re: Updates to gitolite progress

Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both the master and the branch without doing a full rebuild

Re: Updates to gitolite progress

Now you can push your branch to lyx: $ git push lyx 2.0.x How come I have to specify lyx 2.0.x. Isn't it possible to setup the branch so that git push will do the right thing? git push will by default push to the remote which is tracked by the current branch. If the current branch does

Re: Updates to gitolite progress

Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both the master and the branch

Re: Updates to gitolite progress

Il 21/03/2012 16:44, Jean-Marc Lasgouttes ha scritto: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: There has to be a simple way to commit a patch to branch (please tell me there is!). | I forgot to mention: Ideally, if we do it the git-way completely, you | would only have to commit a patch to the 2.0.x branch. Later, the | 2.0.x will

Re: Updates to gitolite progress

Pavel Sanda sa...@lyx.org writes: | Jean-Marc Lasgouttes wrote: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to

Re: Updates to gitolite progress

Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in /lyx, you can clone this with git clone -s -b 2.0.x /lyx /lyx20x This will clone your repo, but it will reuse the objects. This means

Re: Updates to gitolite progress

Op 21-3-2012 15:51, Jean-Marc Lasgouttes schreef: Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in /lyx, you can clone this with git clone -s -b 2.0.x /lyx /lyx20x This will clone

Re: Updates to gitolite progress

There has to be a simple way to commit a patch to branch (please tell me there is!). I forgot to mention: Ideally, if we do it the git-way completely, you would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x will automatically be merged into the master. This can be

Re: Updates to gitolite progress

Le 21/03/2012 16:56, Vincent van Ravesteijn a écrit : There has to be a simple way to commit a patch to branch (please tell me there is!). I forgot to mention: Ideally, if we do it the git-way completely, you would only have to commit a patch to the 2.0.x branch. Later, the 2.0.x will

Re: Updates to gitolite progress

Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both the master and the branch without doing a full rebuild

Re: Updates to gitolite progress

Now you can push your branch to "lyx": $ git push lyx 2.0.x How come I have to specify "lyx 2.0.x". Isn't it possible to setup the branch so that "git push" will do the right thing? "git push" will by default push to the remote which is tracked by the current branch. If the current

Re: Updates to gitolite progress

Jean-Marc Lasgouttes wrote: > Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : >> There is also a 2.0.x branch in your first clone, so you can just >> cherry-pick the commit to master directly onto this 2.0.x branch, and >> push from there. > > But If I want to compile both the master and the

Re: Updates to gitolite progress

Il 21/03/2012 16:44, Jean-Marc Lasgouttes ha scritto: Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : There is also a 2.0.x branch in your first clone, so you can just cherry-pick the commit to master directly onto this 2.0.x branch, and push from there. But If I want to compile both

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: >>> There has to be a simple way to commit a patch to branch (please >>> tell me there is!). >> > | I forgot to mention: Ideally, if we do it the git-way completely, you | would only have to commit a patch to the 2.0.x branch. Later, the | 2.0.x will

Re: Updates to gitolite progress

Pavel Sanda writes: | Jean-Marc Lasgouttes wrote: >> Le 21/03/2012 16:14, Vincent van Ravesteijn a écrit : >>> There is also a 2.0.x branch in your first clone, so you can just >>> cherry-pick the commit to master directly onto this 2.0.x branch, and >>> push from there. >> >> But

Re: Updates to gitolite progress

On 03/14/2012 07:13 PM, Lars Gullik Bjønnes wrote: Vincent van Ravesteijnv...@lyx.org writes: | How can you make your repo public ? (without the need of specifying | all devs in the setperms) The special user @all, gives every one with ssh keys access. daemon enables anon access through

Re: Updates to gitolite progress

Richard Heck rgh...@comcast.net writes: | On 03/14/2012 07:13 PM, Lars Gullik Bjønnes wrote: Vincent van Ravesteijnv...@lyx.org writes: | How can you make your repo public ? (without the need of specifying | all devs in the setperms) The special user @all, gives every one with ssh keys

Re: Updates to gitolite progress

On 03/14/2012 07:13 PM, Lars Gullik Bjønnes wrote: Vincent van Ravesteijn writes: | How can you make your repo public ? (without the need of specifying | all devs in the setperms) The special user "@all", gives every one with ssh keys access. "daemon" enables anon access through

Re: Updates to gitolite progress

Richard Heck writes: | On 03/14/2012 07:13 PM, Lars Gullik Bjønnes wrote: >> Vincent van Ravesteijn writes: >> >> | How can you make your repo public ? (without the need of specifying >> | all devs in the setperms) >> >> The special user "@all", gives every one

Re: Updates to gitolite progress

Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in home/lyx, you can clone this with git clone -s -b 2.0.x home/lyx home/lyx20x This will clone your repo, but it will reuse the objects.

Re: Updates to gitolite progress

Op 14-3-2012 14:59, Jean-Marc Lasgouttes schreef: Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in home/lyx, you can clone this with git clone -s -b 2.0.x home/lyx home/lyx20x This

Re: Updates to gitolite progress

| How can I assign rewrite or forced updates right to me for my own clone ? You can't. But that you can't is a misconfiguration on my side. The creator of that clone should have all rights. I'll fix this. Thanks, it's ok now. You can give basic write and read access to others, but no

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: | How can I assign rewrite or forced updates right to me for my own clone ? You can't. But that you can't is a misconfiguration on my side. The creator of that clone should have all rights. I'll fix this. | Thanks, it's ok now. You can give

Re: Updates to gitolite progress

Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in /lyx, you can clone this with git clone -s -b 2.0.x /lyx /lyx20x This will clone your repo, but it will reuse the objects. This means

Re: Updates to gitolite progress

Op 14-3-2012 14:59, Jean-Marc Lasgouttes schreef: Le 12/03/2012 19:56, Vincent van Ravesteijn a écrit : If you want a tree for both 2.0.x and 2.1.0svn, you can do the following: Assume you have a git clone in /lyx, you can clone this with git clone -s -b 2.0.x /lyx /lyx20x This will clone

Re: Updates to gitolite progress

| How can I assign rewrite or forced updates right to me for my own clone ? You can't. But that you can't is a misconfiguration on my side. The creator of that clone should have all rights. I'll fix this. Thanks, it's ok now. You can give basic write and read access to others, but no

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: >> | How can I assign rewrite or forced updates right to me for my own clone ? >> >> You can't. But that you can't is a misconfiguration on my side. The >> creator of that clone should have all rights. >> >> I'll fix this. > | Thanks, it's ok now. >

Re: Updates to gitolite progress

Am 12.03.2012 um 19:56 schrieb Vincent van Ravesteijn: Op 11-3-2012 22:43, Richard Heck schreef: On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at

Re: Updates to gitolite progress

First, you have to do git checkout 2.0.x This will create the branch from the upstream branch. Vincent Op 13 mrt. 2012 07:26 schreef Stephan Witt st.w...@gmx.net het volgende: Am 12.03.2012 um 19:56 schrieb Vincent van Ravesteijn: Op 11-3-2012 22:43, Richard Heck schreef: On 03/11/2012

Re: Updates to gitolite progress

| After that I will gradually make the new repo more and more accessiable: | - add to gitweb added, viewable at http://git.lyx.org/ | - add to daemon (enable + add) added, anon access to close with git clone git://git.lyx.org/lyx is now enabled. How can I assign rewrite or forced updates

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: | After that I will gradually make the new repo more and more accessiable: | - add to gitweb added, viewable at http://git.lyx.org/ | - add to daemon (enable + add) added, anon access to close with git clone git://git.lyx.org/lyx is now

Re: Updates to gitolite progress

Am 12.03.2012 um 19:56 schrieb Vincent van Ravesteijn: > Op 11-3-2012 22:43, Richard Heck schreef: >> On 03/11/2012 05:37 PM, Richard Heck wrote: >>> On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel

Re: Updates to gitolite progress

First, you have to do git checkout 2.0.x This will create the branch from the upstream branch. Vincent Op 13 mrt. 2012 07:26 schreef "Stephan Witt" het volgende: > > Am 12.03.2012 um 19:56 schrieb Vincent van Ravesteijn: > > > Op 11-3-2012 22:43, Richard Heck schreef: > >> On

Re: Updates to gitolite progress

| After that I will gradually make the new repo more and more accessiable: | -> add to gitweb added, viewable at http://git.lyx.org/ | -> add to daemon (enable + add) added, anon access to close with git clone git://git.lyx.org/lyx is now enabled. How can I assign rewrite or forced

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: >> | After that I will gradually make the new repo more and more accessiable: >> | -> add to gitweb >> >> added, viewable at http://git.lyx.org/ >> >> | -> add to daemon (enable + add) >> >> added, anon access to close with >> >> git clone

Re: Updates to gitolite progress

Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: lar...@gullik.org (Lars Gullik Bjønnes) writes: | lar...@gullik.org (Lars Gullik Bjønnes) writes: | | - write access for developers (this might be moved up in the queue) | I'll enable write access now, but with some limitations: you are not |

Re: Updates to gitolite progress

On Mon, Mar 12, 2012 at 1:03 PM, Vincent van Ravesteijn v...@lyx.org wrote: Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: First of all, thank you for this work Lars, this is a truly great achievement :-) If we want to introduce a staging repo and can also be done, but we shouldn't change to

Re: Updates to gitolite progress

On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote: The main repo would be automatically synchronized (only the 2.0 and 2.1 branches); either via a git hook or a cron script at server side. The cron idea is better if only we had some automatic regression testing in place. Then only those

Re: Updates to gitolite progress

Op 11-3-2012 22:43, Richard Heck schreef: On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to

Re: Updates to gitolite progress

Op 12-3-2012 18:15, Rob Oakes schreef: On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote: The main repo would be automatically synchronized (only the 2.0 and 2.1 branches); either via a git hook or a cron script at server side. The cron idea is better if only we had some automatic

Re: Updates to gitolite progress

Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: - fork the lyx repo: $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx My personal repo does not appear in gitweb. Is it supposed to ? Vincent

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: | Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: - fork the lyx repo: $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx | My personal repo does not appear in gitweb. Is it supposed to ? It will only appear there if you give

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: | Op 11-3-2012 22:43, Richard Heck schreef: On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org.

Re: Updates to gitolite progress

Op 12-3-2012 20:17, Lars Gullik Bjønnes schreef: Vincent van Ravesteijnv...@lyx.org writes: | Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: - fork the lyx repo: $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx | My personal repo does not appear in gitweb. Is it

Re: Updates to gitolite progress

Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: lar...@gullik.org (Lars Gullik Bjønnes) writes: | lar...@gullik.org (Lars Gullik Bjønnes) writes: | | -> write access for developers (this might be moved up in the queue) | I'll enable write access now, but with some limitations: you are not |

Re: Updates to gitolite progress

On Mon, Mar 12, 2012 at 1:03 PM, Vincent van Ravesteijn wrote: > Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: First of all, thank you for this work Lars, this is a truly great achievement :-) >> If we want to introduce a staging repo and can also be done, but we >> shouldn't

Re: Updates to gitolite progress

On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote: > The main repo would be automatically synchronized (only the 2.0 and > 2.1 branches); either via a git hook or a cron script at server side. > The cron idea is better if only we had some automatic regression > testing in place. Then only

Re: Updates to gitolite progress

Op 11-3-2012 22:43, Richard Heck schreef: On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to

Re: Updates to gitolite progress

Op 12-3-2012 18:15, Rob Oakes schreef: On Mar 12, 2012, at 10:59 AM, Abdelrazak Younes wrote: The main repo would be automatically synchronized (only the 2.0 and 2.1 branches); either via a git hook or a cron script at server side. The cron idea is better if only we had some automatic

Re: Updates to gitolite progress

Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: - fork the lyx repo: $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx My personal repo does not appear in gitweb. Is it supposed to ? Vincent

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: | Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: >>- fork the lyx repo: >> $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx > | My personal repo does not appear in gitweb. Is it supposed to ? It will only appear there if you

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: | Op 11-3-2012 22:43, Richard Heck schreef: >> On 03/11/2012 05:37 PM, Richard Heck wrote: >>> On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo

Re: Updates to gitolite progress

Op 12-3-2012 20:17, Lars Gullik Bjønnes schreef: Vincent van Ravesteijn writes: | Op 12-3-2012 0:44, Lars Gullik Bjønnes schreef: - fork the lyx repo: $ ssh g...@git.lyx.org fork lyx developers/larsbj/lyx | My personal repo does not appear in gitweb. Is it

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | Lars Gullik Bjønnes lar...@gullik.org writes: | | 3. Cleanup and verify the svn-git conversion that I already have in place. | | - Unless I have to redo anything this will be quite easy. | | 4. Make the subversion repo read-only | I am

Re: Updates to gitolite progress

As of now the subversion repo is read-only. (the lyx-devel part of it.) I'm waiting to see the lyx repo to appear on gitolite:).. Vincent

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and forks. Developers that have registered their public

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. | After that I will gradually make the new repo more and more accessiable: | - add to gitweb added, viewable at http://git.lyx.org/ | - add to daemon (enable + add) added, anon access to

Re: Updates to gitolite progress

On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and

Re: Updates to gitolite progress

On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for

Re: Updates to gitolite progress

On 11/03/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and

Re: Updates to gitolite progress

Julien Rioux jri...@physics.utoronto.ca writes: | On 11/03/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | - add to trac Trac also made available now. Might require some more work. -- Lgb

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | - write access for developers (this might be moved up in the queue) I'll enable write access now, but with some limitations: you are not allowed to create new branches nor delete them. Also history rewind is not allowed. Also: try to avoid

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | lar...@gullik.org (Lars Gullik Bjønnes) writes: | | - write access for developers (this might be moved up in the queue) | I'll enable write access now, but with some limitations: you are not | allowed to create new branches nor delete them.

Re: Updates to gitolite progress

Vincent van Ravesteijn v...@lyx.org writes: | Op 5-3-2012 1:03, Lars Gullik Bjønnes schreef: I have added some more gitolite functionality. (only viewable for the people that has sent me their ssh public key.) ssh g...@git.lyx.org help You will not be able to fork anything yet, but as you

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | Lars Gullik Bjønnes writes: > | | 3. Cleanup and verify the svn->git conversion that I already have in place. | | - Unless I have to redo anything this will be quite easy. >> | | 4. Make the subversion repo read-only > |

Re: Updates to gitolite progress

As of now the subversion repo is read-only. (the lyx-devel part of it.) I'm waiting to see the lyx repo to appear on gitolite:).. Vincent

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and forks. Developers that have registered their public

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. > | After that I will gradually make the new repo more and more accessiable: | -> add to gitweb added, viewable at http://git.lyx.org/ | -> add to daemon (enable + add) added, anon access

Re: Updates to gitolite progress

On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and

Re: Updates to gitolite progress

On 03/11/2012 05:37 PM, Richard Heck wrote: On 03/11/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for

Re: Updates to gitolite progress

On 11/03/2012 12:59 PM, Lars Gullik Bjønnes wrote: lar...@gullik.org (Lars Gullik Bjønnes) writes: | | 5. Enable the new lyx-devel git repo at git.lyx.org. The new repo has been made available to developers, and the git installation has opend up for developers to create their own repos and

Re: Updates to gitolite progress

Julien Rioux writes: | On 11/03/2012 12:59 PM, Lars Gullik Bjønnes wrote: >> lar...@gullik.org (Lars Gullik Bjønnes) writes: >> >> | | 5. Enable the new lyx-devel git repo at git.lyx.org. >> >> The new repo has been made available to developers, and the git >>

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | -> add to trac Trac also made available now. Might require some more work. -- Lgb

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | -> write access for developers (this might be moved up in the queue) I'll enable write access now, but with some limitations: you are not allowed to create new branches nor delete them. Also history rewind is not allowed. Also: try to avoid

Re: Updates to gitolite progress

lar...@gullik.org (Lars Gullik Bjønnes) writes: | lar...@gullik.org (Lars Gullik Bjønnes) writes: > | | -> write access for developers (this might be moved up in the queue) > | I'll enable write access now, but with some limitations: you are not | allowed to create new branches nor delete them.

Re: Updates to gitolite progress

Vincent van Ravesteijn writes: | Op 5-3-2012 1:03, Lars Gullik Bjønnes schreef: >> I have added some more gitolite functionality. >> (only viewable for the people that has sent me their ssh public key.) >> >> ssh g...@git.lyx.org help >> >> You will not be able to fork anything

Re: Updates to gitolite progress

Lars Gullik Bjønnes lar...@gullik.org writes: | 2. See if we can get the trac connection setup. | - Should just be config, and a another hook to get updates to | the repo signaled to trac. I have added the git testing repo to trac. It seems to work fine. I have not added any trac specific

Re: Updates to gitolite progress

Lars Gullik Bjønnes lar...@gullik.org writes: | 3. Cleanup and verify the svn-git conversion that I already have in place. | - Unless I have to redo anything this will be quite easy. | 4. Make the subversion repo read-only I am pretty much ready to do this now. From the moment I turn off

  1   2   >