Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think this is what you want: </p> <pre><code>git rev-list HEAD -- foo.rb | ( while read rev; do git blame -l -L 1000,+5 $rev -- foo.rb | cut -d ' ' -f 1 done; ) | awk '{ if (!h[$0]) { print $0; h[$0]=1 } }' </code></pre> <p>That'll output the the revision number for each commit that has an edit to the lines you've chosen. </p> <p>Here are the steps: </p> <ol> <li><p>The first part <code>git rev-list HEAD -- foo.rb</code> outputs all revisions in which the chosen file is edited. </p></li> <li><p>Each of those revisions then goes into the second part, which takes each one and puts it into <code>git blame -l -L 1000,+5 $rev -- foo.rb | cut -d ' ' -f 1</code>. This is a two-part command. </p> <ol> <li><code>git blame -l -L 1000,+5 $rev -- foo.rb</code> outputs the blame for the chosen lines. By feeding it the revision number, we are telling it to start from that commit and go from there, rather than starting at the head.</li> <li>Since blame outputs a bunch of info we don't need, <code>cut -d ' ' -f 1</code> gives us the first column (the revision number) of the blame output. </li> </ol></li> <li><code>awk '{ if (!h[$0]) { print $0; h[$0]=1 } }'</code> takes out non-adjacent duplicate lines while maintaining the order they appeared in. See <a href="http://jeetworks.org/node/94">http://jeetworks.org/node/94</a> for more info about this command. </li> </ol> <p>You could add a last step here to get prettier output. Pipe everything into <code>xargs -L 1 git log --oneline -1</code> and get the corresponding commit message for the list of revisions. I had a weird issue using this last step where I had to keep pressing next every few revisions that were output. I'm not sure why that was, which is why I didn't include it in my solution. </p>
    singulars
    1. This table or related slice is empty.
    1. POGit: discover which commits ever touched a range of lines
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJonathan Wren
    1. USJonathan Wren
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COCongratulations! Very nice and concise, the next steps would be to calculate the updated line range automatically. But this is a great start. Would you be interested in solving the next puzzle? Shall I open another bounty? :-)
      singulars
      1. PO
      1. USJoao Tavora
    2. COThat's a very interesting question! I'm, unfortunately, very busy at work this week, so I won't have a chance to play with this. It'll be on my mind, though, and I'll come back to it next week if someone else hasn't solved it by then.
      singulars
      1. PO
      1. USJonathan Wren
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload