-
-
Notifications
You must be signed in to change notification settings - Fork 969
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
Restore gen-*.py script history #13
Comments
The initial filter-branch was overly aggressive, dropping
Drop c6ac923 and fill in from swcarpentry/DEPRECATED-bc@f4cc356:
Where the removes drop the copies from the rebased history, and add and mv put the new copies from swcarpentry/DEPRECATED-bc@f4cc356 in the right place. Check that the new commit does the right stuff:
Shift the rest of our earlier extraction from the broken c6ac923 to the new
Check that the history looks the same:
Check that the content matches bc (with HEAD^ because we've landed #1 locally, and that content isn't in bc):
Horray :). |
Blocking out the second lecture
Update navbar.html
These were dropped by one of the earlier filter-branch clones (see #4). Just to be clear about which repositories I'm referring to, here are my remote names for this section:
What's the history for
gen-sequence.py
in bc?Which of those commits are in modular-shell?
Taking a closer look at our breaking commit:
And the bc commit it's based on:
Hmm, so this commit is bumping
gen-nene.py
, and we'll have to look at that too. What's its history in bc?Do we have that first commit in modular-shell?
What's it touching there?
So our filter-branched commit doesn't add
gen-nene.py
, because swcarpentry/DEPRECATED-bc@090b60b had added it to a different directory (bash/util/gen-nene.py
). I don't think we want auto-generated content in the repository anyway, so I might try and refactor this bit of history entirely…The text was updated successfully, but these errors were encountered: