www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <dava...@gmail.com>
Subject Re: Best Practices so far?
Date Fri, 02 May 2008 08:56:18 GMT
Hash: SHA1

Cool. Next steps to complete one scenario (helping new contributors contribute)

- - Suppose i am a prospective committer. How do i make a patch available for review? (what
needs to be mentioned in a
JIRA issue)
- - Switching roles, how does an existing committer, pull the patch and give it a whirl? (before
i check it into Apache 
- - Finally, how do i get this patch from git to svn? with enough information about the JIRA
issue etc.


Jukka Zitting wrote:
| Hi,
| On Fri, May 2, 2008 at 11:22 AM, Davanum Srinivas <davanum@gmail.com> wrote:
|> So, what's the learning so far? Example how does one set up a git-svn for a
|> specific Apache project?
| I've cloned a few smaller projects like this:
|     git svn clone -s http://svn.apache.org/repos/asf/incubator/<project>
| So far I've avoided doing that with TLPs because of the load on the
| svn server, but now that svn.eu.apache.org is in place I'm running the
| following:
|     git svn clone -s http://svn.eu.apache.org/repos/asf/jackrabbit
| Note that these clones take quite a while (hours) to create, but after
| that it's quite easy and fast to keep them up to date with latest
| changes.
| So far I've used these clones for quick browsing and comparing of
| version histories, my actual working copies are still normal svn
| checkouts (mostly due to IDE integration). Thus I haven't yet used
| things like dcommit on Apache projects.
| BR,
| Jukka Zitting
Version: GnuPG v1.4.5 (Cygwin)


View raw message