A few quick pointers to get started...
The first thing to understand is that Git is distributed and as such
there is no one true repository. When you use git you actually create a
full independent clone of the repository that is just as valid as the
original.
That said, the different clones are maintained by different people, so
there can be repositories that you trust more than others. In this case,
there is a git repository (or actually several) that is a mirror of the
SVN repository, created and maintained by the ASF (see
http://git.apache.org/), e.g. git://git.apache.org/uima-uimaj.git and
you could clone the repository from there and use the one at
git.apache.org as the official version (read-only so far).
However, there is also an official mirror on github, e.g.
https://github.com/apache/uima-uimaj that is also maintained by the ASF
and is always an exact copy of the one at git.apache.org (and thus an
exact copy of the SVN repository).
For people who want to work with the UIMA git repositories I would
strongly recommend starting from the version on Github. In addition to
giving you the possibility to checkout/clone the repository it gives you
an excellent web interface that allows you to explore the code. But the
main feature is that with one click you can fork the repository and have
your own *public* copy where you can work on the code and people can
review your changes.
E.g. I have a repository at https://github.com/jgrivolla/uima-addons
that is forked from https://github.com/apache/uima-addons and that is
where people will be able to see any changes I make before I push them
back to the official SVN repository. People can fork from my version of
the repository or just follow some of my branches within their fork of
the official repository, etc.
On https://help.github.com/ you get a good introduction to using git,
specifically with the typical github workflow of creating public forks
of existing repositories. On http://git.apache.org/ you can find some
more documentation, in particular on how to push changes back to SVN
when working in git.
Hope that helps to get you started, and don't hesitate to ask for more
details.
-- Jens
On 10/12/13 16:25, Marshall Schor wrote:
Hi Jens,
For those not (yet) in the Git world, can you post info and/or links to how to
use this new resource?
-Marshall
On 12/10/2013 9:05 AM, Jens Grivolla (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Grivolla resolved UIMA-3456.
---------------------------------
Resolution: Fixed
appears to be all ok (for the parts I checked) and can be forked e.g. on github
ask for git mirror
------------------
Key: UIMA-3456
URL: https://issues.apache.org/jira/browse/UIMA-3456
Project: UIMA
Issue Type: Task
Reporter: Jens Grivolla
Assignee: Jens Grivolla
Priority: Minor
file ticket on INFRA to ask for git mirror -- proposed text:
We would like to have a git mirror of the Apache UIMA SVN. As the project has
many submodules with individual trunk/branches/tags structure we would like the
following mapping:
uimaj uima-uimaj.git
uimacpp uima-uimacpp.git
uima-as uima-as.git
addons uima-addons.git
sandbox uima-sandbox.git (ignore sandbox/uima-ducc)
ruta uima-ruta.git
sandbox/uima-ducc uima-ducc.git
uimafit uima-uimafit.git
site uima-site.git
build uima-build.git (ignore build/archive)
ignore eclipse-packagings
All of these follow the standard SVN layout.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
