It was my first attempt at using GIT on a Windows machine that I share with a collaborator. The checkout had been done before I got to the machine, and although I saw the 'git log...' command described in the TortoiseGIT documentation, I couldn't get it to work - I've gone soft in this age of GUIs, and since I only wanted a one-off export in the limited time I had sole use of the machine, brute force and ignorance won the day.
>________________________________ > From: Oliver Bock <[email protected]> >To: Richard Haselgrove <[email protected]> >Cc: "[email protected]" <[email protected]> >Sent: Monday, 19 November 2012, 16:24 >Subject: Re: [boinc_dev] GIT migration: integration with user web/BBCode links > >On 11/19/12 16:03 , Richard Haselgrove wrote: >> I have access to a full local GIT checkout. I filtered the commit >> message log to select out (only) the entries containing "svn >> path=/trunk/boinc/; revision=", and copied them to a text file.Once I'd >> extracted the two types of revision numbers, I imported them into a >> database and used a SQL query to find the duplicates - which is why I'm >> sure it's an exhaustive list. > >I see. You could also have done that like this: >(just added the "--all" option) > >git log --all --pretty=format:%H --grep "revision=26128" > > >Regarding the ambiguity of svn revisions: this is because, in the >example of r26128, Rom replayed David's commit manually in his branch >(like a cherry-pick but without retaining meta info). A regular merge >wouldn't have caused a separate commit (with the same commit message). >Anyhow, I agree that this needs to be taken care of by taking into >account the branch name containing the SHA1 in question during lookup. >You can find the branch that contains a given commit like this: > >git branch [-a][-r] --contains SHA1 > >If you only have a single remote you probably want to use the "-r" option. > > >HTH, >Oliver > > > > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
