1 / 14

CS 241 Section Week #1

CS 241 Section Week #1. August 25, 2011. Topics This Section. SVN (…by the command line!) HW #1 Overview Due six days from now (Wed, Aug 31 st ) Due at 11:00am on SVN (NOT IN CLASS) No late submissions! Code Examples. svn.

tess
Télécharger la présentation

CS 241 Section Week #1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 241Section Week #1 August 25, 2011

  2. Topics This Section • SVN (…by the command line!) • HW #1 Overview • Due six days from now (Wed, Aug 31st) • Due at 11:00am on SVN (NOT IN CLASS) • No late submissions! • Code Examples

  3. svn • Each week, there will be files we provide for us to use in section. • Create a directory in your space to checkout svn: mkdir cs241 cd cs241

  4. svn • To create a local “working copy” of the SVN, you need to run an svn checkooutcommand: svn checkout https://subversion.ews.illinois.edu/svn/fa11-cs241/ (Link on the course website for you to copy and paste)

  5. svn • Make sure your checkout worked: $ ls netid $ cdnetid $ ls ds hw1 $ cdds $ ls ds1 $ cd ds1 $ ls 1.c 2.c 3.c 4.c 5.c

  6. svn • You only need to checkout files once! • From now on, you can get the latest changes from the server by running an svn update. svn up svn update

  7. svn • When you’ve got something working, you will want to commit the changes you made back to the server with an svn commit: svn ci -m "" svn commit -m "some message"

  8. svn • When you’ve got something working, you will want to commit the changes you made back to the server with an svn commit: svn ci -m "" svn commit -m "some message" We will grade your latest committed version of each MP!

  9. svn • Often, you will only need to modify the files we provide to you on the svn. However, you will occasionally need to add a new file to your svn with svn add: svn add FILENAME

  10. svn • Lets add a file, and verify we added it: (You should probably be in your ds1 directory for this.) cat "Hello World" >hello.txt svn add hello.txt svn ci -m "First SVN commit!"

  11. svn • Finally, what time did you make the submission? Did you make it in on time? svn log hello.txt ------------------------------------------------------------------------ r3866 | netid | 2011-22-08 22:07:59 -0600 (Mon, 22 Aug 2011) | 1 line First SVN commit! ------------------------------------------------------------------------

  12. Homework #1 • Two parts: • [Part 1]: 16 questions on finding a problem with a provided snippet of code • [Part 2]: 2 questions on using binary and bit-level operators to accomplish a task

  13. Homework #1 • Two parts: • [Part 1]: 16 questions on finding a problem with a provided snippet of code • [Part 2]: 2 questions on using binary and bit-level operators to accomplish a task

  14. Discussion Section Practice • Five different files, each having code snippets similar to HW1. • In your svn: ds/ds1/ • 1.c, 2.c, 3.c, 4.c, 5.c • To compile: gcc 1.c • To run: ./a.out

More Related