| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Without this, I always got a "refs/heads/origin is an invalid SHA1"
error. From the git-cvsimport manual:
-a
Import all commits, including recent ones. cvsimport by
default skips commits that have a timestamp less than 10
minutes ago.
|
|/
|
|
|
|
|
|
| |
lorry was failing to cope with missing or relative
working directory. After fix if no directory is
given it will show a message that no working directory
in path and will use "workd" directory. It will also
create the directory if it isn't present.
|
| |
|
|
|
|
| |
the exit code will be number of mirror failed
|
| |
|
|
|
|
|
|
|
| |
Lorry fails as soon one mirror encounters exception.
Resolve:
Exception handled when some thing goes wrong with mirror and
move to the other mirror.
|
|
|
|
|
|
|
|
| |
A bundle policy and destination can be specified in settings
It will bundle up tags and branches
Some changes to fetching were required, now it only fetches origin and expects that
the refspec fetches into local refs. svn support has been altered to support this
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The branches generated by git-svn appear to be lightweight tags
These are just a reference to a commit, the script to convert these
into full tags may not create the same sha1 for each tag.
This shows that git-svn is not properly handling tags
there is no such thing as a remote tag, so they have to be fetched
into refs/tags
I could change the refspecs to do this, but given this is just an
intermediate stage before they are pushed to another repository it
would only be visible to people poking their noses in the working area
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
git push defaults to pushing matching branches, this will not push new branches
git push --all will push all local branches, but not every repo has all the remote
branches mirrored by local branches
refspecs can be configured to give better control over what git push does
So now when gitorious is added as a remote its refspecs can be changed
it defaults to pushing branches and tags but it can be changed to give finer control
git-svn uses refspecs to push the remote branches
it could have been made to fetch svn refs as local refs, but that may have
introduced bugs and would require altering the trunk fetch refpec
when currently it is ok to add new refspecs for tags and branches
|
|
|
|
|
| |
the svn-remote is called svn, have the branches in refs/remotes/svn for consistency
with normal remotes
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Glob expressions can be used to specify branches, but git svn clone/init will append /* to
them unless they have a * in them. It is possible to have globs without.
netpbm has branches in its root directory, so the glob
{advanced,stable,super-stable} should select only those directories
as branches, but they become {a,s,ss}/*, so subdirectories of each become
branches
The workaround is to manually add the glob expression to config
so it is cloned then branches are added, then re fetched
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
git svn fetch updates the remote tracking branch
it does not alter the master branch to include the changes
so git svn rebase must be used to do this
It may be possible to just push the remote tracking branch to gitorious
but other imports push the working branches, so this keeps it simpler
without that much extra overhead as the rebase should be cheap
This also adds a couple of extra options, to get command output before
the program finishes, useful for long programs
|
|
|
|
| |
So it is cloned into $project/git rather than $project/git/$url
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds a layout field to the lorry spec
if it is omitted it is assumed that the url points to the trunk
if layout is "standard" then url/trunk url/tags and url/branches
point to the trunk, tags and branches
if layout is a dict then the trunk, branches and tags fields
are the corresponding paths
Strange layouts can be handled by a wildcard * in the path
So if there are branches in branches, but the Build/source is
the only part wanted then "branches": "branches/*/Build/source"
will only pull that
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
adds a repack setting so if it is too expensive an operation it can be turned off
run git-repack after the gitify step, maybe it should check whether it needed updating
but that may not be simple
|
| |
|
|
|
|
|
| |
adds the marks files when converting, I don't know what they are all for
This also fixes lorry importing bzr repos
|
| |
|
| |
|
|
|
|
| |
I think --mirror is --all but also deletes and --tags is just the tags
|
|
|
|
| |
added by other sources
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It seems fast-export suffers greatly from any lag to the bzr repository,
so this way we eliminate that.
|
|
|
|
| |
That's a good way to DoS yourself.
|
| |
|
|
|