Hi,
Keshav Kini wrote:
The man page for `git svn` describes a situation in which 'git svn'
will not be able to rebuild your .git/svn/**/.rev_map files, but no
mention is made of in what circumstances `git svn` *will* be able to do
so, or how to get `git svn` to do so.
This patch adds some
Jonathan Nieder jrnie...@gmail.com wrote:
Keshav Kini wrote:
+ tracking. If necessary, rebuild the .git/svn/\*\*/.rev_map.*
+ files, given the requisite information exists in commit
+ messages (see the svn.noMetadata config option for more
+ information). The name of the
Jonathan Nieder jrnie...@gmail.com writes:
Taking a step back, the reader might wonder *why* he would want
to run git svn fetch to rebuilt these .rev_map.* files, and what
they are for.
Perhaps there should be a separate REVISION MAP section describing
this in more detail. Something as
Keshav Kini wrote:
I changed the wording of your first paragraph a bit according to what I
thought it meant. Does it still convey what you wanted to convey, and is
it still correct?
Mapping between Subversion revision numbers and Git commit
names. In a repository where the
Jonathan Nieder jrnie...@gmail.com writes:
Keshav Kini wrote:
I changed the wording of your first paragraph a bit according to what I
thought it meant. Does it still convey what you wanted to convey, and is
it still correct?
Mapping between Subversion revision numbers and Git commit
Jonathan Nieder jrnie...@gmail.com writes:
@@ -684,7 +687,7 @@ svn-remote.name.noMetadata::
+
This option can only be used for one-shot imports as 'git svn'
will not be able to fetch again without metadata. Additionally,
-if you lose your .git/svn/**/.rev_map.* files, 'git svn' will not
The man page for `git svn` describes a situation in which 'git svn'
will not be able to rebuild your .git/svn/**/.rev_map files, but no
mention is made of in what circumstances `git svn` *will* be able to do
so, or how to get `git svn` to do so.
This patch adds some language to the description of
7 matches
Mail list logo
