[ensembl-dev] Chasing changes in Git history, Re: how to sort the GO objects hierarchically.

[Matthew Astley]

On Tue, Apr 01, 2014 at 03:23:42PM +0100, mag wrote:

> The ontology scripts have been moved into our production directory
> https://github.com/Ensembl/ensembl-production/tree/release/75/scripts/ontology/scripts

I hope it is relevant & useful to demonstrate some Git history delving
here:

The Github page Pablo mentioned

> On 01/04/2014 06:21, pmg wrote:
>
> > P.S.: By the way, where are now located the "ensembl/misc-scripts/ontology/scripts/"
> > in the git repo https://github.com/Ensembl/ensembl/tree/release/75/misc-scripts/ontology
> > there is only the README that mention this scripts folder and the
> > SQL folder but not the scripts.

has a "History" link from
  https://github.com/Ensembl/ensembl/tree/release/75/misc-scripts/ontology
  to
  https://github.com/Ensembl/ensembl/commits/release/75/misc-scripts/ontology


The commit with the relevant comment is buried half-way down the page
  https://github.com/Ensembl/ensembl/commit/66dd95e244b95a97cd8813aeac1e976ca18130af


If you know the name of the script you need, you can hack the URL
above to make
  https://github.com/Ensembl/ensembl/commits/release/75/misc-scripts/ontology/scripts/demo2.pl
or just
  https://github.com/Ensembl/ensembl/commits/release/75/misc-scripts/ontology/scripts

which is fairly clear.

For myself, I usually prefer to use "gitk --all HEAD &" on a local
checkout.  It has similar abilities.



Because this is a cross-repository move you then have to find the
destination in the other repo.

You have the date (misleading in this case) and maybe can guess the
filename
  https://github.com/Ensembl/ensembl-production/commits/release/75/scripts/ontology/scripts

otherwise you have to look for matching filenames or known string
contents.


hth,
-- 
Matthew