-
-
Notifications
You must be signed in to change notification settings - Fork 983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add novice/ref/01-shell.md and novice/teaching/02-shell.md #27
Comments
Injecting Check our history:
Replace ccac789 with a cherry-pick:
Check the new commit:
Shift our old history onto the new commit:
Check the history again:
Remove the temporary branch:
We can skip swcarpentry/DEPRECATED-bc@3a38907, since it's just a rename. |
Injecting the change from swcarpentry/DEPRECATED-bc@b66851c: Check our history:
Replace 5aca06b with a cherry-pick:
Check the new commit:
Shift our old history onto the new commit:
Check the history again:
Remove the temporary branch:
We can skip swcarpentry/DEPRECATED-bc@b8c7dc3, since it's just a rename. |
Still to go: swcarpentry/DEPRECATED-bc@b614a72, swcarpentry/DEPRECATED-bc@5705090, swcarpentry/DEPRECATED-bc@94fc345, but I'm out of time at the moment. |
Injecting the change from swcarpentry/DEPRECATED-bc@94fc345: Check our history:
Replace cb1724f with a cherry-pick:
Check the new commit:
Shift our old history onto the new commit:
Check the history again:
Remove the temporary branch:
|
I'd dropped our version of swcarpentry/bc@5705090 in #9, because
We just injected swcarpentry/bc@94fc345, so there's nothing to do |
swcarpentry/DEPRECATED-bc@b614a72 isn't actually part of filter-branch history
We dropped the branch around swcarpentry/bc@5705090, so lets just
While removing the “Conflicts” block from the commit message, I took
Check the new commit:
Shift our old history onto the new commit:
Check the new history:
Remove the temporary branch:
|
That's all the cheat-sheet (
The oldest three commits were in I'll take a close look at swcarpentry/DEPRECATED-bc@171fa48 next. |
Ah, swcarpentry/DEPRECATED-bc@171fa48 just renamed our guide to
Is there any history after the rename?
Yup ;). Do we have any of those commits already? I checked with
I'll figure out where the missing commits fit in and get these all injected next. |
It looks like we do have all the cheat-sheet history though:
I'll push what I currently have:
and get back to the remaining guide history later. |
swcarpentry/DEPRECATED-bc@7d03694 (Adding points from #56 to the teaching guide, 2014-03-13) split directly off bc's master and was merged back in by swcarpentry/DEPRECATED-bc@ba5adc75 (Merge pull request #378 from gvwilson/incorporating-notes-from-issue-56, 2014-03-14) via the dummy merge swcarpentry/DEPRECATED-bc@20cc227 (Merging other changes to teaching notes, 2014-03-14). Our extracted history currently has nothing between a6c41cc (Converting shell lesson Markdown files to use div + fence block, 2014-03-03) and a handfull of Ethan's commits starting with f096091 (Match number of samples and math in novice shell Introduction, 2014-04-02). Here's the local graph of our current branch:
Lets graft the bc fork and merge in, and drop the dummy merge. Recreate the pull-request on top of a6c41cc:
Re-create the merge:
Check our reconstructed merge:
Delete the temporary PR branch:
Take our old history and move everything that used to be on top of a6c41cc over to the new
Check the new history:
Looks good. Remove the temporary branch marker:
|
swcarpentry/DEPRECATED-bc@4baa7efc8 (Moving conclusions of discussion from #140 to the teaching notes, 2014-03-13) split directly off bc's master from the same commit as swcarpentry/DEPRECATED-bc@7d03694. It landed earlier though, in swcarpentry/DEPRECATED-bc@bba4ace (Merge pull request #379 from gvwilson/options-
Re-create the merge:
Check our reconstructed merge:
Delete the temporary PR branch:
We don't want to rebase the reconstructed 2ff2060 (Adding points
Check the new history:
Filter-branch to bake-in the replacement: Check the new history:
Looks good. Remove the replacement:
Remove the temporary branch marker:
|
We already have a version of swcarpentry/DEPRECATED-bc@e2f3f3d (Modifying all raw Markdown files to use class attributes for code blocks, 2014-04-24): 22769b1 (Modifying all raw Markdown files to use class attributes for code blocks). The initial filter-branch seems to have dropped the merge that landed it (swcarpentry/DEPRECATED-bc@9d0e797, Merge pull request #476 from gvwilson/adding-kramdown-alds, 2014-05-03), so I'll leave that out. Do we already have the changes from swcarpentry/DEPRECATED-bc@e2f3f3d? Here's what it did:
And here's what we have:
So we need to cherry-pick our commit again. Create a working branch:
Check our new commit:
Hmm, we're not even starting with the same file hash (a8faefb vs. b1eaf8d). What's going on? Our history:
And bc's history:
So we agree up to the last commit (e.g. on 0d032cf and b1eaf8d), but bc gets to a8faefb, likely with some merge resolution. Lets look at that dummy merge we dropped ;).
Aha! Ok, we need to push this merge resolution into our consolidated “Merge pull request #378 from gvwilson/incorporating-notes-from-issue-56”. Lets abandon our current
Now shift our history onto the fixed
Check the fixed history:
Now lets get back to swcarpentry/DEPRECATED-bc@e2f3f3d. Following our earlier work:
There we go :). Put our branch onto the new
Check the new history:
Looks good. Remove the temporary branch:
|
The next set are a bit easier, because the're in a single series:
That leave bc's master at swcarpentry/DEPRECATED-bc@506a1cc (Merge pull request #577 from r-gaia-cs/mailmap, 2014-07-05) and rejoins at swcarpentry/DEPRECATED-bc@dc050fe (Merge pull request #594 from noamross/master, 2014-07-22). Looking through our extracted history, in that area we have
So the new commits fit somewhere in there ;). |
Looking for the above commits in bc's master:
We can see “Change some anchors to enable EPUB post processor” and “Merge pull request #535 from gvwilson/rewriting-shell-lesson-using-nelle”, both part of our extracted history. Both swcarpentry/DEPRECATED-bc@506a1cc and swcarpentry/DEPRECATED-bc@dc050fe fall between those commits, so we don't have to do anything complicated. Recreate the pull request branch:
Re-create the merge:
Check our reconstructed merge:
Delete the temporary PR branch:
Take our old history and move everything that used to be on top of a6c41cc over to the new wip commit:
Check the new history:
Looks good. Remove the temporary branch marker:
|
Ok, just swcarpentry/DEPRECATED-bc@fb4d59c (Replace bootcamp with workshop, 2014-09-25) to go :). Where was that in bc?
Nice and compact :). What do we have in the viscinity of 2014-09-25?
So it should come between “Merge branch 'shell-filesystem-consistency' of github.com:rbeagrie/bc into shell-filesystem-consistency” and “Small Grammatical Change to List Format”.
Re-create the merge:
Check our reconstructed merge:
Delete the temporary PR branch:
Take our old history and move everything that used to be on top of a6c41cc over to the new wip commit:
Check the new history:
Looks good. Remove the temporary branch marker:
And publish the new history:
|
This novice shell content wasn't in
novice/shell
or the earliershell/novice
orbash/novice
, so we need to graft it in by hand. Looking at its history:Are there side effects to these commits? Let's start with swcarpentry/DEPRECATED-bc@5159f8a:
so this will be a series of fixes like #13, where we need to tweak filter-branch commits to preserve the cheat-sheet changes.
The text was updated successfully, but these errors were encountered: