Inconsistencies in joda-time's git repositories

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Inconsistencies in joda-time's git repositories

Shivani Rao
I have been mining joda-time software for some research purposes and I am noticing tons of inconsistencies.
My goal is to track what files are changed at what "commitids". I independently

I use the following commands (commitidcurrent, commitidprev_
git checkout commitidcurrent
git diff --name-status -C commitidcurrent..commitid_prev >> changes.txt

then I go through all the files that are modified or added and then copy only those from the current revision.

I find that a majority of the commits have inconsistencies.

Is this expected because of the migration from cvs?
 
Thanks a lot for your help in advance.
Shivani

--
Research Scholar,
School of Electrical and Computer Engineering
Purdue University
West Lafayette IN
web.ics.purdue.edu/~sgrao

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Joda-interest mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/joda-interest
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Inconsistencies in joda-time's git repositories

jodastephen
The repo has been migrated from cvs to svn, then to git. The migration
to git required use of git grafts to change the history and
re-integrate it. I'm not surprised if along the way, some subleties
have got confused!

Stephen


On 8 July 2012 20:10, Shivani Rao <[hidden email]> wrote:

> I have been mining joda-time software for some research purposes and I am
> noticing tons of inconsistencies.
> My goal is to track what files are changed at what "commitids". I
> independently
>
> I use the following commands (commitidcurrent, commitidprev_
> git checkout commitidcurrent
> git diff --name-status -C commitidcurrent..commitid_prev >> changes.txt
>
> then I go through all the files that are modified or added and then copy
> only those from the current revision.
>
> I find that a majority of the commits have inconsistencies.
>
> Is this expected because of the migration from cvs?
>
> Thanks a lot for your help in advance.
> Shivani
>
> --
> Research Scholar,
> School of Electrical and Computer Engineering
> Purdue University
> West Lafayette IN
> web.ics.purdue.edu/~sgrao
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Joda-interest mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/joda-interest
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Joda-interest mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/joda-interest
Loading...