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 <omerik...@gmail.com> wrote:

> 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 other one
> starts at master. sha1 nums are different ones of course. since I followed
> the instructions I was wondering how it happened and if should I remove the
> duplicated ones with rebase -i now.
>
>
> On Saturday, July 21, 2012 12:29:47 AM UTC+3, Gabby Romano wrote:
>>
>> 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 at 10:22 PM, Thomas Ferris Nicolaisen <
>> tfn...@gmail.com> wrote:
>>
>>> 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 together ?  I am
>>>> only ~ month with git so not sure yet about where all the traps may lie.
>>>> if it's as simple as you describe in your site I might be OK.
>>>>
>>>>
>>> Well, just try it out and see how it goes.
>>>
>>> Maybe it will save you some time if you take care and plan exactly which
>>> svn revisions you have to stitch together.
>>>
>>> Also, before you start grafting and filter-branching, make an extra
>>> clone of the repository you are working on, in case you have to start over.
>>>
>>> And note down the commands you are using, in case you want to trace back
>>> your steps.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Git for human beings" group.
>>> To view this discussion on the web visit https://groups.google.com/d/**
>>> msg/git-users/-/VR3rhB5LonEJ<https://groups.google.com/d/msg/git-users/-/VR3rhB5LonEJ>
>>> .
>>>
>>> To post to this group, send email to git-users@googlegroups.com.
>>> To unsubscribe from this group, send email to git-users+unsubscribe@**
>>> googlegroups.com <git-users%2bunsubscr...@googlegroups.com>.
>>> For more options, visit this group at http://groups.google.com/**
>>> group/git-users?hl=en <http://groups.google.com/group/git-users?hl=en>.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/git-users/-/owyM-LoZsEQJ.
>
> To post to this group, send email to git-users@googlegroups.com.
> To unsubscribe from this group, send email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/git-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to