Skip to content
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

Bits of history we've found and grafted on #2

Closed
6 of 9 tasks
wking opened this issue Oct 24, 2014 · 10 comments
Closed
6 of 9 tasks

Bits of history we've found and grafted on #2

wking opened this issue Oct 24, 2014 · 10 comments

Comments

@wking
Copy link
Contributor

wking commented Oct 24, 2014

This is a meta issue for laying out which history we've found for bc's novice/shell, and whether or not it's been grafted into this repository's master branch:

@wking
Copy link
Contributor Author

wking commented Oct 25, 2014

I've marked the shell/novice item closed, and added a new item for bash/novice (see #3).

@wking
Copy link
Contributor Author

wking commented Oct 25, 2014

I've marked the bash/novice item closed, and added a new item for the gen-*.py scripts (see #4).

@wking
Copy link
Contributor Author

wking commented Nov 6, 2014

I've marked the commit-message cleanup item closed (via #9), but:

  • We're still waiting for acks from Bernhard and Meg on the changes. Greg said the changes to his commits were fine in an off-list email.
  • We may have more commit messages that need rewriting as we graft on additional history.

@twitwi
Copy link
Contributor

twitwi commented Nov 21, 2014

I've been working on this for some time now. I learnt a few things and made (little) progress.

My goal was to recover the history of gen-*.py.
Toward this goal, I ended up starting "from scratch" meaning from the bc/master.
I also wanted to have something reproducible and easier to update.

In the end it is there: https://github.com/twitwi/swc-modular-shell-bootstrap

I managed to keep the history from the 3 folders (successive names) and to clean the commit messages. In addition, I managed to keep gen-*.py but the history (given by git log --follow) is incomplete… and I'm not sure to understand why. Overall the produced history looks quite like swc-modular-shell/master (as of today).

It is not a big/real progress but it might be easier to update, e.g. to remove generated files.
NB: the first step is time consuming (rewriting history) and is better off on a ram drive.

@wking @gvwilson I'll stop working on it for now. I wish I had made more progress.

@wking
Copy link
Contributor Author

wking commented Nov 21, 2014

On Fri, Nov 21, 2014 at 04:41:31AM -0800, Rémi Emonet wrote:

Toward this goal, I ended up starting "from scratch" meaning from
the bc/master. I also wanted to have something reproducible and
easier to update.

Have you posted your procedure somewhere? I'd like to figure out how
the gen-*.py bit worked so we can reuse the approach if we find a
similar situation later.

@twitwi
Copy link
Contributor

twitwi commented Nov 21, 2014

It's in the repo linked above

https://github.com/twitwi/swc-modular-shell-bootstrap

I guess it's not a 100% git clean approach.

@wking
Copy link
Contributor Author

wking commented Nov 22, 2014

On Fri, Nov 21, 2014 at 01:03:11PM -0800, Rémi Emonet wrote:

It's in the repo linked above

https://github.com/twitwi/swc-modular-shell-bootstrap

I guess it's not a 100% git clean approach.

I see your rebuilt history, I'm just looking for your notes on how you
rebuilt it (see for example, the “commands used” links in the topic
message for this issue).

@twitwi
Copy link
Contributor

twitwi commented Nov 22, 2014

These commands are in the README.md of the repo linked in my previous message.
They use the script from the repo.
Let me know if I misunderstood your question.

@wking
Copy link
Contributor Author

wking commented Nov 22, 2014

On Sat, Nov 22, 2014 at 11:34:29AM -0800, Rémi Emonet wrote:

These commands are in the README.md of the repo linked in my
previous message. They use the script from the repo. Let me know
if I misunderstood your question.

Oh, I'd thought that repo was your extracted history, sorry for the
confusion. I shoud have time to look through your repository in the
next few days.

@wking
Copy link
Contributor Author

wking commented Dec 18, 2014

We're now live with additional post-bc history, so the window for fixing these issues has closed.

@wking wking closed this as completed Dec 18, 2014
iglpdc pushed a commit to iglpdc/shell-novice that referenced this issue Mar 22, 2015
rgaiacs pushed a commit to rgaiacs/swc-shell-novice that referenced this issue May 6, 2017
rgaiacs pushed a commit to rgaiacs/swc-shell-novice that referenced this issue May 6, 2017
Bringing a second example of PCK in initial def'n
fmichonneau pushed a commit to fmichonneau/shell-novice that referenced this issue Sep 9, 2021
fmichonneau added a commit to fmichonneau/shell-novice that referenced this issue Sep 9, 2021
Bring in latest changes to styles repository
wood-chris referenced this issue in edcarp/shell-novice-esces Jan 11, 2023
zkamvar pushed a commit that referenced this issue May 2, 2023
Adding a note to remind authors to say what learners are supposed to do in lessons.
zkamvar pushed a commit that referenced this issue May 2, 2023
The  command should reflect the directory structure. In Lesson #2, the data-shell/ directory is placed inside Desktop/ 
Even if it was placed inside the home directory, at least data-shell/ should be in the path.
zkamvar pushed a commit that referenced this issue May 2, 2023
Add a 'commit --amend' exercise

What changed?: Revised Learning Objective #2 to reflect that the "find" command can also be used for directories (one of the examples in the lesson uses the "$ find . -type d" command)

What specifically changed?:
Revised:
"Use `find` to find files whose names match simple patterns." 
to:
"Use `find` to find files and directories whose names match simple patterns."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants