Is it politically possible to keep using git as always, and have the main
git branch/repo automatically commit to the apache svn repo the latests
changesets?

I mean, in the end, nothing prevents one developer to internally use git,
and commit to an official svn repo.
Or 2 developers to internally use git in order to share changesets more
easily.
Or all the developers to internally use git, even if in the end the trunk
branch arrives at the svn repo.


On Mon, May 23, 2011 at 18:34, Ali Lown <[email protected]> wrote:

> Unfortunately, I don't see anyway for apache to setup a git repository.
> Their whole system is based around SVN. The best they seem to be able
> to offer is a git mirror[0]
>
> [0]:http://git.apache.org/
>
> 2011/5/23 Daniel Danilatos <[email protected]>:
> > I like the hg->git part! :)
> >
> > Στις 23 Μαΐου 2011 2:43 π.μ., ο χρήστης Yuri Z <[email protected]>
> έγραψε:
> >> Regarding hg->svn migration:
> >> I was lately investigating how to proceed with It and it seems like the
> best
> >> way is first to convert from mercurial to git, and then from git to svn.
> >> Here are the links: hg->git
> >> http://hivelogic.com/articles/converting-from-mercurial-to-git/
> >> <http://hivelogic.com/articles/converting-from-mercurial-to-git/>git ->
> svn
> >> : http://code.google.com/p/support/wiki/ImportingFromGit
> >>
> >>
> >>
> >> 2011/5/22 Michael MacFadden <[email protected]>
> >>
> >>> All,
> >>>
> >>> Now that we are rolling on Jira, I think it's time to start thinking
> about
> >>> migrating to the apache SVN.  Can we set a goal timeframe for this?  To
> do
> >>> this I would recommend any one who is working on a large outstanding
> project
> >>> in their own workspace to try to wrap those up.  We probably want a
> fairly
> >>> stable and complete snapshot to move over to avoid disrupting peoples
> work.
> >>>
> >>> We'll also need to think about how we handle code reviews since apache
> has
> >>> ReviewBoard set up by default.  Some have voiced a preference for
> sticking
> >>> with Rietveld.  I suppose this is an option, however we might need to
> move
> >>> the review site off of waveprotocol.org since that site will
> eventually
> >>> not be for WiaB development.  We should compare and contrast Review
> Board as
> >>> well.  Thanks.
> >>>
> >>> ~Michael
> >>
> >
>



-- 
Saludos,
     Bruno González

_______________________________________________
Jabber: stenyak AT gmail.com
http://www.stenyak.com

Reply via email to