Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <pre><code>git log --format="pick %h %s" --reverse -- dir1/ dir2/ </code></pre> <p>could be written</p> <pre><code>git log --format="pick %h %s" --no-walk \ $(git rev-list --reverse -- dir1/ dir2/) </code></pre> <p>That is, using</p> <pre><code>git rev-list HEAD -- dir1/ dir2/ </code></pre> <p>to get the list of 'raw' revision ids. Now to get the complementary set of revision ids, I suggest something like </p> <pre><code>sort &lt;(git rev-list HEAD) &lt;(git rev-list HEAD -- dir1/ dir2/) | uniq -u </code></pre> <h3>Integrating it all</h3> <p>the complementary set would become</p> <pre><code>git log --format="pick %h %s" --no-walk \ $(git rev-list --no-walk --reverse \ $(sort &lt;(git rev-list HEAD) \ &lt;(git rev-list HEAD -- dir1/ dir2/) | uniq -u)) </code></pre> <p><sub>note both <code>--no-walk</code> parameters there, they are crucial</sub></p> <h3>Recommendations</h3> <ol> <li>I highly recommend making bash functions or scripts to implement the substeps here</li> <li><strong>If you are just looking for a way to split repositories, <a href="http://git-scm.com/docs/git-filter-branch" rel="nofollow">look into git-filter-branch</a></strong> instead! <ul> <li>it will enable you 'mask' (remove) the unwanted part of the tree for each revision</li> <li>allows you to skip <em>effectively empty</em> revisions, like you want</li> <li>the man page contains samples for just that</li> <li>it will work (<em>correctly</em>) if a single commit edited both parts of the repo</li> <li>remember the <code>--tag-name-filter cat</code> option</li> </ul></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POShow only commits that don't affect any of the specified paths
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsehe
    1. USsehe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShow only commits that don't affect any of the specified paths
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COadded a pointer to git-filter-branch just in case...
      singulars
      1. PO
      1. USsehe
    2. COAwesome, thanks! I'll try that. And no, I don't want to split repos. What I do is basically cleaning up, splitting up the project's upstream and downstream work that was done on that particular branch.
      singulars
      1. PO
      1. USManuela Hutter
    3. COGit Bash doesn't support process substitution it seems, but otherwise that solution worked for me (using temporary files).
      singulars
      1. PO
      1. USManuela Hutter
 

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