Yes, that's what the whole thing about git is! This usually works the following:
I see some bug I like to fix, or have some improvement and like to implement it. I then setup a local git repo for this project and fix the issues. I commit the local changes into my git-repo and push them to some public repo (e.g. my private http://ns1.backwork.net/git) The next step is to ping the mailing list or the maintainer of this plugin and tell him to clone/pull my changes. ( e.g. >$ git-clone http://ns1.backwork.net/git/openjpa-maven-plugin.git ) If the changes are ok, he'll merge them into svn and commit it to the main repo. The benefit over svn sandboxes is huge: no authorisation problem, easy merging, other users can come up with an alternate approach/fix for the fix by cloning and changing + pushing to their repos, etc A good and also really amusing overview about how to develop with git (from a google speech by Linus Torvalds himself): http://www.youtube.com/watch?v=4XpnKHJAok8 LieGrue, strub --- Kevin Sutter <[EMAIL PROTECTED]> schrieb am Di, 9.12.2008: > Von: Kevin Sutter <[EMAIL PROTECTED]> > Betreff: Re: [OT] git and Apache's svn? > An: [email protected] > Datum: Dienstag, 9. Dezember 2008, 15:18 > This sounds interesting. It sounds like we could provide > for multiple > "build levels" and only promote changes when they > are really ready. All of > this without requiring the use of sandboxes. Or, am I > reading more into > this? > > Kevin > > On Tue, Dec 9, 2008 at 5:08 AM, Mark Struberg > <[EMAIL PROTECTED]> wrote: > > > Hi Patrick! > > > > In which way do you like to access the apache svn? > > > > Did you already work with git? > > > > Do you only like to manage local branches with git > (git on top of a svn > > checkout)? > > > > Do you like to use the git-svn bridge for doing all > the local management > > with git? > > > > > > The way I use git for Apache projects is the 'git > on top' approach (I'll be > > more verbose since I do not know what you already > know): > > > > 1.) do a svn co > > 2.) create a .gitignore file which contains /target > and .svn > > 3.) modify my .svnignore to contain .git and > .gitignore > > 4.) $> git-init > > 5.) $> git-add src > > 6.) $> git-status to check if the index > doesn't contain crap > > 7.) $> git-commit -m"initial import from > SVN" > > > > I subsequently do some svn update and commit them to > my local git master > > branche. > > In parallel I do test branches with > > $> git-checkout -b mytestbranch > > see git-branch for more info > > > > If the changes work out, you can merge them into > master and afterwards > > perform a svn commit to the Apache repo. > > > > > > Another way would be to use the git-svn bridge. pro: > you'd have the whole > > history in git (so you could do a git-blame for > example) con: you cannot use > > mvn scm (e.g. for releasing), since the > maven-scm-providers-svn relies on > > having a SVN structure locally and the > maven-scm-providers-git relies on > > having a remote git repo... > > > > > > LieGrü, > > strub > > > > > > --- Patrick Linskey <[EMAIL PROTECTED]> schrieb > am Di, 9.12.2008: > > > > > Von: Patrick Linskey <[EMAIL PROTECTED]> > > > Betreff: [OT] git and Apache's svn? > > > An: [email protected] > > > Datum: Dienstag, 9. Dezember 2008, 8:18 > > > Hi, > > > > > > Has anyone had any experience with using git with > > > Apache's svn repository? > > > > > > Thanks, > > > > > > -Patrick > > > > > > --Patrick Linskey > > > 202 669 5907 > > > > > > > >
