OK,

I found what I needed anyway so not a biggie.

Cheers

On 24/10/2010 3:58 PM, Mauricio Scheffer wrote:
Even so it would require a rewrite of all history up to the point of the split, thus breaking all clones/forks. IMHO not worth it...

--
Mauricio



2010/10/24 Krzysztof Koźmic <[email protected] <mailto:[email protected]>>

    ok thanks.

    Would you care to see which one was that (not possible or hard)
    and if the latter if perhaps it is easier to do in latest version
    of Git?
    It would be really useful sometimes...

    cheers,
    Krzysztof


    On 24/10/2010 2:47 PM, Mauricio Scheffer wrote:
    All history is there, down to the very first commit (see
    
http://github.com/castleproject/Castle.Windsor/commit/a3e2a134e830fb839b4ad6e7e38e8b877c393ca4
 )

    Just the file move in the split isn't tracked by git, as you
    noticed. I don't remember if it just wasn't possible or it was
    very complicated to do it.
    If you need a blame across the split, move to the the split (i.e.
    git reset or create a branch and checkout) and repeat the blame.

-- Mauricio



    2010/10/24 Krzysztof Koźmic <[email protected]
    <mailto:[email protected]>>

        Hi,

        I was trying to do blame on something today in Windsor, and I
        noticed that our history goes back only a year.
        More precisely, it looks like when we did split out Windsor
        (potentially other projects as well) into their own
        repositories we didn't migrate history.

        Was that a concious choice? (to save space or whatever). If
        so - how can I access the old history? Should I pull the old
        svn dump
        (http://github.com/castleproject/castle-READONLY-SVN-dump)
        and look there?

        cheers,
        Krzysztof

-- You received this message because you are subscribed to the
        Google Groups "Castle Project Development List" group.
        To post to this group, send email to
        [email protected]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:castle-project-devel%[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/castle-project-devel?hl=en.


-- You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" group.
    To post to this group, send email to
    [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-devel?hl=en.

-- You received this message because you are subscribed to the Google
    Groups "Castle Project Development List" group.
    To post to this group, send email to
    [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:castle-project-devel%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-devel?hl=en.


--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

--
You received this message because you are subscribed to the Google Groups "Castle 
Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/castle-project-devel?hl=en.

Reply via email to