| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
It completely screws up KDevelop's highlighting...
|
|\
| |
| |
| | |
merge-requests/14
|
| |
| |
| |
| |
| |
| | |
The patch add --add-metadata-notes command line option which is similar to
--add-metadata except rather embedding svn commit info into the commit message,
it is added as a note for the respective commit.
|
|/
|
|
| |
Its value is used to fill in repository/description file used by gitweb.
|
|
|
|
|
|
| |
Git seems to always output +0000, so when filter-branching,
every single commit changes hash because dates are changed
from - to +0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The branch is first created properly and then deleted
(line "progress SVN r77 branch config-header = :0 # delete")
- Jehan's post-1.0.3 commit 584005f2e26149282aa12c4a0367d250caaf3918
writes a backup of the branches latest ref to refs/backup/
on deletion. Many thanks for that commit!
However, in my opinion the problem with the current code is that it
makes it much too easy to lose history during the conversion to Git.
Without a tag or branch pointing to it the commits will fall off easily,
especially if people use "git clone" on the bare Git repository created
by svn2git.
It would be safer and useful to create visible tags for this, e.g.
refs/tags/branch-bugfix17-deleted.
My attached patch changes Jehan's code to do just that.
Please consider application - this patch really matters to me.
If you'd rather have both a ref in refs/backup/ and in refs/tags/ or
require a command line option for it I can adjust the patch for you.
Thanks for listening,
|
|
|
|
|
|
| |
Ensure that the backup reference is created before deleting the original
branch. As it was, the deletion was executed earlier causing the backup
reference to point to a non-existing branch so was not created.
|
|
|
|
|
|
| |
Author names were being properly passed through fromUtf8(),
but then sent to a QTextStream using the system's locale.
This patch forces the text stream to always use UTF-8.
|
| |
|
|
|
|
|
|
|
| |
In Repository::commit, don't call startFastImport() if we have nothing to
write to the fastImport stream. startFastImport() may start new
git-fast-import processes if they were previously killed, so it may be
extremely slow to call it frequently if it's not necessary.
|
| |
|
|
|
|
| |
Might still need some logic for detecting the correct from branch.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
commit()
Prepare for handling cvs2svn borked tags/branches
|
|
|
|
|
| |
[FastExport]Repository
Some minor reordering
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This fixes importing large svn commits that get imported into a large number
of git repositories. It happened that a process was closed (in ProcessCache::touch)
before commit() and so the commit wasn't imported correctly.
And remove the touch() call as that is done now in startFastImport()
|
|
|
|
|
|
|
| |
This is needed to make sure that not too many processes are running and
we run out of ressources.
Calling touch only in commit is not enough as startFastImport is called in other
functions as createBranch too - and that can result in too many processes.
|
|
|
|
| |
closed fast-import
|
| |
|
|
|
|
|
|
| |
a branch as deleted.
Thanks Raja R Harinath for spotting it.
|
| |
|
|
|
|
| |
"--debug-rules" flag is active.
|
| |
|
| |
|
| |
|
|
|
|
| |
Creation is already printed at the bottom.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The conflict was mainly around two different approaches to fixing the linear
commitMarks issue. The precise tracking of commit marks per branch is better,
and that's how I resolved the merge conflict.
While at it, I also removed the "revision-*" files, since the "log-*" files
already have the same information, and the branch information too.
Conflicts:
src/repository.cpp
src/repository.h
|
| |\
| | |
| | |
| | | |
git://gitorious.org/~marcguenther/svn2git/marcguenther-svn2git into integration
|
| | |\ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
from path then fallback to using the latest version and issue a warning
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Suppose you have multiple repositories in SVN that you want to merge into
a single one in GIT, it can get very messy to handle all the special-case
rules.
Instead, we introduce a new "forwarding repository" concept, which looks like
repository subordinate
repository unified
prefix foo/
end repository
This forwards all commits on the "subordinate" SVN tree to the "unified" GIT
tree, with each file prefixed with "foo/".
|
| | |
| | |
| | |
| | | |
Rename Repository to FastImportRepository. We will be introducing new types soon.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The naming scheme is
refs/backups/r<svn-revision>/(heads|tags)/<branch>
Where <svn-revision> is the revision where the branch is being reset:
either for deletion or to be overwritten.
We use a separate namespace so that we don't clutter up branch-name lists
and tag lists with deleted tags. These refs will keep the commits alive
as far as 'git gc' is concerned, but will be fairly unobstrusive otherwise.
|
| | |
| | |
| | |
| | | |
Put the slightly tricky qUpperBound logic in only one place.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
While at it, make progress message for the "unknown from" case similar
to the normal progress message. This ensures that any reconstructed
branch data-structure will not lose any information.
|
| | |
| | |
| | |
| | | |
Only deleteBranch uses it for now.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Allow graceful exit of all fast-import processes when createBranch fails.
For consistency, add return value to deleteBranch, even though it always
returns EXIT_SUCCESS.
|