fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Geiß <markus.ge...@live.de>
Subject RE: Initial code push
Date Thu, 28 Jan 2016 05:23:57 GMT
Hey Keith,
thanks for the links.

I won't push over all branches b/c it would also contain all releases that we already made
and we will change the versioning scheme.

I will proceed with doing an initial push of one branch where all the clean up work has happened.

Best,

Markus

.::YAGNI likes a DRY KISS::.

> Date: Wed, 27 Jan 2016 14:58:44 +0000
> Subject: Re: Initial code push
> From: keithwoodlock@gmail.com
> To: dev@fineract.incubator.apache.org
> 
> Markus,
> 
> Assume you want you bring over the commit history with it also.
> 
> There is a question about what branches you want to bring over? do you want
> to bring them all or just a few special ones.
> 
> - Best apporach is probably to clone the repository in full locally and
> then push up to the new remote apache repository.
> 
> This writeup talks about doing all branches or specific ones depending on
> what  you want to do:
> 
> https://developer.atlassian.com/blog/2016/01/totw-copying-a-full-git-repo/
> 
> Keith.
> 
> On Wed, Jan 27, 2016 at 2:32 PM, Markus Geiß <markus.geiss@live.de> wrote:
> 
> > Hey all,
> >
> > hope this finds you well.
> >
> > Finally we are able to push the code over. How should we proceed with this?
> >
> > 1) Add an additional upstream to a local clone, pull the branch and merge
> > into master,
> > 2) Copy all files over manually and do a initial push,
> > 3) other ways?
> >
> > Best,
> >
> > Markus
> >
> > .::YAGNI likes a DRY KISS::.
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message