Re: Tree-Maintenance: current/devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: * Slava Zanko slavaza...@gmail.com schrieb: Hi, Enrico, please don't hurry. Wait please a few days (may be, after New Year). All existing patches need to be collected in one place. This place will git (browse: http://www.midnight-commander.org/browser). It contains the How can I checkout/clone it ? ssh-keygen -f mc-devel mkdir -p ~/.ssh/keys chmod 0700 ~/.ssh/keys mv -f mc-devel ~/.ssh/keys/mc-devel.key mv -f mc-devel.pub ~/.ssh/keys/mc-devel.pub chmod 0600 ~/.ssh/keys/mc-devel.key [ ! -f ~/.ssh/config ] touch ~/.ssh/config cat ~/.ssh/config EOF host www.midnight-commander.org IdentityFile ~/.ssh/keys/mc-devel.key host midnight-commander.org IdentityFile ~/.ssh/keys/mc-devel.key EOF mail ~/.ssh/keys/mc-devel.pub to Patrick Winnertz Then: git clone ssh://www.midnight-commander.org:/git/mc.git Or may be anonymous r/o access: git clone git://midnight-commander.org/git/mc.git Then simply to work: # to view all local branches git branch # to view all branches ( included from parent(s) git ) git branch -a # make remote branch as local git branch --track stable origin/stable # switch to branch 'stable' git checkout stable # get changes from parent git git pull # push changes to parent git git push P.S. I'm not a professional in git... Thanks to Patrick Winnertz - he my teacher in git :) WBR, Slavaz. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFJWysVb3oGR6aVLpoRApyUAJ4jbRjeP4bGyxJbYW/BnIYWYPruBwCffA4q 3htj5y6ANIYSHG4ofeDyIoI= =e7G0 -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: Or may be anonymous r/o access: git clone git://midnight-commander.org/git/mc.git Initialized empty Git repository in /home/crosstool/XXX/mc/.git/ remote: fatal: Out of memory, realloc failed remote: aborting due to possible repository corruption on the remote side. fatal: early EOF fatal: index-pack failed The machine still/again seems to run out of memory :(( Hm... try again. :( To Patrick Winnertz: Is time now for migrate to much powerfull server? WBR, Slavaz. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFJWzkUb3oGR6aVLpoRAjUKAJ9mKgw4Y5czAyrDfGMDVvOCdMV4CQCcCvi3 U0HMKFLjc4ICOtk1EA2EYeM= =rm2B -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
On Wed, 31 Dec 2008 10:19:33 +0200 Slava Zanko wrote: Or may be anonymous r/o access: git clone git://midnight-commander.org/git/mc.git Is it possible to make an anonymous r/o http access to git for those people who lives behind the corporative proxy? git clone http://midnight-commander.org/git/mc.git Regards, Andrew. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
* Slava Zanko slavaza...@gmail.com schrieb: Hm... try again. :( Okay, got it now. I'm already in process of preparing patches from rhclub to git tree. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
Hey folks, As I thought that this is a great idea I set it up in the git. the master branch is the branch where development should go into and there is a stable branch which shouldn't be touched while working on patches/new features. After a patch is tested well enough this patch can be cherry-picked from the mater branch into the stable branch in order to make a release from this branch. There should be only some people who moves patches out from master into stable, but this should be also discussed in the ticketsystem (e.g. the ticket will only be closed when the patch is finally in the stable branch). As I'm intrested in this part and Enrico is also I would suggest that we two works on this. Is this okay for everybody? Greetings Winniie -- . '' ` . Patrick Winnertz win...@debian.org : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~winnie - http://www.der-winnie.de `- Debian - when you have better things to do than fixing systems signature.asc Description: This is a digitally signed message part. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
* Slava Zanko slavaza...@gmail.com schrieb: Hi, Enrico, please don't hurry. Wait please a few days (may be, after New Year). All existing patches need to be collected in one place. This place will git (browse: http://www.midnight-commander.org/browser). It contains the How can I checkout/clone it ? What I need is always the latest status of the next release candidate and perhaps some (semi-)automatic way to synchronize it into my local svn repository. I'd like to base my patches on either the latest release (currently 4.6.2) or the next release candidate (=current-tree). Perhaps we could write a few lines about that in the wiki. latest cvn changes (plus in near future http://mc.redhat-club.org/svn/trunk as branch). Just wrote a little script which fetches that tree and merges it into my local svn ... there're *huge* changes - let's see what we can take over next ;-o Therefore, your job, Enrico is very important (All existing patches are to gather in one place, not only from Gentoo). And I think that the best place to patches is a trac - it was better suited for monitoring the implementation of the work than the mailing list ;) Ok, having the xmlrpc interface would be a great help. cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Tree-Maintenance: current/devel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Weigelt wrote: is anyone already maintaining the current development tree (becoming 4.6.2) ? Enrico, please don't hurry. Wait please a few days (may be, after New Year). All existing patches need to be collected in one place. This place will git (browse: http://www.midnight-commander.org/browser). It contains the latest cvn changes (plus in near future http://mc.redhat-club.org/svn/trunk as branch). The main branch (master) will change the existing patches. Along with the changes will be made from a branch mc.redhat-club.org. This is necessary for the restoration of the history of the applyingg of patches - many patches in our branch(mc.redhat-club.org) were applyed in one revision, sorry for inconvenience. That will be corrected. Therefore, your job, Enrico is very important (All existing patches are to gather in one place, not only from Gentoo). And I think that the best place to patches is a trac - it was better suited for monitoring the implementation of the work than the mailing list ;) If yes, please provide a short description how to check out and how to submit patches. yes, but don't hurry, I ask again :) Just add tickets with patches in trac, please. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklVXYkACgkQb3oGR6aVLpo2+ACfaghKGxXdfjw7OnOkje7AnB+i YTYAnjsVuqcN8JkStMSfUDpyHSWaGVTg =saCh -END PGP SIGNATURE- ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
