Hi Tomas,
I am feeling ok now with this mechanism, but I forgot to include one small
repository from svn so the chain is not yet complete.
now in order to insert a bunch of commits in between other commits, is it
enough to connect top and bottom via grafts and that's it ? can I do it in
one step
looks like it's my mistake here. I was looking at my repo with gitk --all
so saw also the rewritten history.:-)
On Wed, Jul 25, 2012 at 1:43 AM, Gabby Romano wrote:
> Hi Tomas - it appears to be working fine with grafting. thanks a lot for
> that.
>
> there is one issue though : seems like I
Hi Tomas - it appears to be working fine with grafting. thanks a lot for
that.
there is one issue though : seems like I have duplicate commits. these are
the latest ones and not the old ones I fetched from the older repository.
one part of the commits starts at remote/origin/master, and the oth
Thanks for the advice. really helps.
One more thing if I may - if I want to distinguish the old file versions
prior to stitch the data, should I be using tags for it ? is it like a
label in other systems and it need to be applied on all
files participating in the process.
On Fri, Jul 20, 2012 a
On Friday, July 20, 2012 2:36:07 PM UTC+2, Gabby Romano wrote:
>
> Thanks Tomas.
> I have decided to do it the "right way" now as described in your site. I
> have cloned svn from an earlier revision and will try to make my way up
> from there.
> anything I should be aware of before stitching all
Thanks Tomas.
I have decided to do it the "right way" now as described in your site. I
have cloned svn from an earlier revision and will try to make my way up
from there.
anything I should be aware of before stitching all together ? I am only
~ month with git so not sure yet about where all the t
Git-svn cannot trace history outside the given trunk and branches in the
standardlayout (trunk and branches). You need to analyze these junctions
and figure out where in the SVN tree the history comes from. Then you have
to make a new clone for each junction and splice them using grafting, as I
It doesn't work.
it seems there are junctions in the svn tree which git-svn don't know what
to do and hence stop. since the follow-parent option is turned on
by default according to the docs, I need to search for other options. new
ideas are welcomed.
On Thu, Jul 19, 2012 at 1:50 PM, Thomas Ferris
On Thursday, July 19, 2012 12:46:16 PM UTC+2, Gabby Romano wrote:
>
> Thanks.
>
> Can I run it with -s but still to start at some revision as in
> -r:HEAD ?
>
>
You sure can.
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To view this
Thanks.
Can I run it with -s but still to start at some revision as in -r:HEAD
?
On Thu, Jul 19, 2012 at 11:36 AM, Thomas Ferris Nicolaisen wrote:
>
>
> On Thursday, July 19, 2012 8:34:50 AM UTC+2, Gabby Romano wrote:
>>
>> Thanks Tomas.
>>
>> my svn structure is trunk/branches/tags based, alt
On Thursday, July 19, 2012 10:36:20 AM UTC+2, Thomas Ferris Nicolaisen
wrote:
>
>
> You can delete the other branches afterwards if you don't want to keep
> them. If they contain history of the trunk, you have to include them if you
> want the entire history, of course.
>
Correction: You have
On Thursday, July 19, 2012 8:34:50 AM UTC+2, Gabby Romano wrote:
>
> Thanks Tomas.
>
> my svn structure is trunk/branches/tags based, although I don't need it
> like that in git.
>
> lets say I am pulling from
> https://svn.isr.hp.com/rg0202/alm/horizon/trunk(since I need only trunk's
> histo
Thanks Tomas.
my svn structure is trunk/branches/tags based, although I don't need it
like that in git.
lets say I am pulling from
https://svn.isr.hp.com/rg0202/alm/horizon/trunk(since I need only
trunk's history and not all other branches). that gives
me history only as far as May 2012, when th
Note that git-svn will not follow history outside the paths you specify for
it. I believe it is restricted to a trunk and branches in a set location.
If at some point, the whole trunk/branches/tags was moved to a different
place in the repository, you have to splice together two git-svn clones t
first I used the regular git svn clone command - git svn clone .
then tried with -r:HEAD but that didn't work for me
either. probably tried a few more options but to no avail. I am sure git
knows how to "follow" the history despite the branching but didn't find the
right way to do it.
On Wed, Jul
15 matches
Mail list logo
