----BEGIN CLASS---- [13:28] #startclass [13:28] realslimshanky, aahh nice thanks [13:28] s/bu/but [13:28] Roll Call [13:28] Saikat Dey [13:28] Amit Kokitkar [13:28] Mohsin Mumtaz [13:28] Anwesha Das [13:28] kumar vipin yadav [13:28] Santosh Kumar Shaw [13:28] hemanth savasere [13:28] Bhavin Gandhi [13:28] Ganesh Nomula [13:28] Vipul Gupta [13:28] Kushal Das [13:28] Niranjana Deshpande [13:28] Ashwani Kumar Gupta [13:28] aryan tripathi [13:28] Soumam Banerjee [13:28] Kshitij [13:28] Mayur khomane [13:28] Deepika Upadhyay [13:28] Onyinye Madubuko [13:28] Robin Schubert [13:28] <__anshul__> Anshul Chauhan [13:28] Chiranjeev Gupta [13:28] Navneet Sharma [13:28] Vipul Siddharth [13:28] Yurii Pylypchuk [13:28] Neha Kandpal [13:28] Anu Kumari Gupta [13:28] Shashank Shekhar [13:28] pooja kumari singh [13:28] Atul kumar [13:28] Aniket uttam [13:28] Anusha Srinivasan [13:28] Abhinav Shirur [13:28] Amarjeet singh [13:28] Pradhvan Bisht [13:28] Samridhi Agarwal [13:28] Anupama Shipurkar [13:28] Jason Braganza [13:28] Adarsh [13:28] Snehil Verma [13:28] Kshithij Iyer [13:28] Rahul Bhattacharjee [13:28] Nikita Kotak [13:28] Himanshu Awasthi [13:28] Shivam Singhal [13:28] Akash pathak [13:28] vishal vijayraghavan [13:29] Shashank Kumar [13:29] Gaurav Sitlani [13:29] Suraj Ghimire [13:29] Akshay Gaikwad [13:29] kushal - should I pose my github merge query after today’s class? [13:29] jasonbraganza: yes [13:29] jasonbraganza, Yes [13:29] Guest38399: change your nick? [13:29] Ranjeet kumar] [13:29] Thank you. [13:30] Seems like a lot of people have joined today :) [13:30] Yash Agarwal [13:30] Jaysinh Shukla [13:30] sayan, yes ;) [13:30] Roll Call: Abhishek Singh [13:30] Before we start of with the class, an important announcement [13:30] Balaji [13:30] Hi thebigj [13:30] People who will do top posting in mailing list will be removed from the mailing list [13:30] sayan, git pull ;) [13:31] So, keep that in mind. [13:31] Roll Call: Mohd Omama [13:31] Any queries from last session? I will just take questions for next 5 mins [13:31] <__anshul__> who will do top posting in mailing list ? [13:31] <__anshul__> "top posting"? [13:32] __anshul__, Read this http://summertraining.readthedocs.io/en/latest/communication.html#mailing-list [13:32] __anshul__: read what ashwanig shared [13:32] Roll call: Deepak Chethan [13:32] __anshul__: it is the time when people reply to a mail, above the main mail [13:32] ! [13:32] next [13:33] Roll call: Devesh Verma [13:33] <__anshul__> okay [13:33] ! [13:33] next [13:33] is their any way to recover a quit with discard changes file in vim like restore session from 2 hours prior /does *.swp files contain those files too in vim or does it just contain those files that we quitted ? [13:33] sayan,I tried implementing markdown in various platforms but it seems it is different in other places ( the syntax). Is it not standard ? [13:34] <__anshul__> vim, has swapfiles, see if you've enabled it [13:34] Example would be wordpress, some elements didn't work [13:34] vipulgupta2048_: there is no clear standard for Markdown, but the basic elements remain the same [13:35] deepika: you can recover as long as there is *.swp file [13:35] vipulgupta2048_, I wrote a blog post using Markdown and it worked completely fine to me [13:35] sayan, So I can refer to the cheat-sheet for each one , I think that would be better [13:35] deepika: when you open a file it's opens a swp file, you can recover from it [13:35] im_moshin, did every element worked the way it should ? [13:35] whatever is in there [13:36] <__anshul__> @deepika http://vimdoc.sourceforge.net/htmldoc/recover.html [13:36] vipulgupta2048_, it worked correctly and i'm using wordpress [13:36] vipulgupta2048_: http://commonmark.org/ [13:36] Roll call: Ravindra Lakal [13:36] Okay starting the class on git [13:36] ok [13:37] sayan okay ,thank you :) ,sorry wasn't able to discuss that day ! [13:37] *- One fine day, you plan to start a project of yours. [13:37] *- But maintaining and building a project is nevertheless a daunting task [13:38] Roll call : Prerna Pandey [13:38] *- You dream that your project would be a big & successful project. [13:38] *- A community of people are be using your project. [13:38] Roll call: Anuja Agarwal [13:38] *- But, you are just a developer and at the end of the day a human. [13:38] Roll Call: deep [13:38] *- You are ought to make mistakes, forget corner cases, make bunch of typos. [13:39] *- and all the other issues that you never even thought of. [13:39] *- But, that's when the community comes to rescue. They start filing up issues. [13:39] *- You solve them one by one. But. slowly, slowly, slowly. [13:39] *- Your issues counter has reached 1000. [13:40] *- Would you be celebrating this milestone? If I were you. I would be tensed. [13:40] roll call:Priyanka Sharma [13:40] *- There so much work years to spend just to fix those pending issues. [13:40] *- You wished you had a helping hand and the community who were just filing the issues [13:41] *- with comments "How can we help?" could just come and help you out. [13:41] *- And with a tensed mind, you mistakenly forcefully delete an important chunk of code. [13:41] *- *And your nightmare dream sequence breaks* [13:42] *- Sweating profusely, You thank your god for the blessing in disguise. [13:42] *- You take an oath for each of your project you will be using a Version Control System a.k.a VCS [13:43] [13:43] *end of prologue* [13:43] Any questions till here? [13:43] ! [13:43] Good prologue. [13:43] next [13:44] why do you keep typing *- [13:44] avik_: to distinguish from rest of the messages :) [13:44] Roll call - Razy Kased [13:44] great idea! ok! [13:44] wow [13:45] moving ahead then [13:45] *- *Chapter 1: Understanding VCS: Commits* [13:45] awesome prologue sayan [13:45] roll call: Sharon [13:45] *- Next day morning you start reading VCS, scratching your head to get around with all the terms [13:46] Roll call - Vamsi Krishna [13:46] *- The first one that you hit is commits, so what is commit (or snapshot?) [13:47] *- So you thought of writing a series analogy stories to learn the concepts better :) [13:47] *- You create a new character, Tux [13:47] *- Tux wants to be photographer, who has just bought a new DSLR. [13:48] *- Tux plan to be the next travel photographer, who would take the best picture from the top of Mt. Everest [13:49] *- But Tux is a newbie, so Tux starts watching for YouTube tutorials for learning to post process the images. [13:49] *- Tux creates a directory named *working* to put all un-processed images. <<-- mind *working* is to be focused here [13:50] *- Then, fires up DarkTable to process the images. [13:50] *- Every time after a set of similar operations (like crop & rotate, shadows & highlights, etc), Tux creates a copy of the *working* directory and names it `snapshot-{n}` [13:51] *- After a couple of operations, Tux stands having "snapshot-1", "snapshot-2", "snapshot-3", .... , "snapshot-100" directories. [13:52] *- This directories is history of how Tux developed the image over time. At any point, Tux can go back to a given snapshot and build again on top of it. [13:52] Roll call : Farhaan Bukhsh [13:52] Any questions till here? [13:52] No [13:52] no [13:52] no [13:52] No [13:52] no [13:52] No [13:52] no [13:52] no [13:52] no [13:52] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] no [13:53] No [13:53] no [13:53] No [13:53] Okay thank you :) [13:53] no [13:53] no [13:53] Moving ahead [13:54] no [13:54] *- *Chapter 2: Understanding VCS: Staging Area* [13:54] no [13:55] *- It's been a month now, Tux have learned a lot on post-processing images. [13:55] *- Tux now mixes and matches multiple images file to create a snapshot directory. [13:56] *- One day, Tux while processing the images, goes into experimental mode. [13:56] *- and only after a while realized that the changes should be going into two [13:57] *- different snapshot directories (`snapshot-139` & `snapshot-140`). [13:57] *- Smart Tux quickly thought of an idea, creates a new staging directory. [13:58] *- A staging directory works as an intermediate between the working directory [13:58] *- and the snapshot directory. [13:58] #attendance Devendra Bhat [13:58] *- So, Tux now works on working directory, and one Tux is happy with the changes [13:59] *- Tux moves all changed files into staging directory, and then creates a copy of the staging directory as new snapshot directory [13:59] Any question till here? [13:59] none [13:59] no [14:00] ! [14:00] Cool [14:00] no [14:00] ! [14:00] next [14:00] next [14:00] no [14:00] is the staging directory is the copy of snap directory [14:00] ? [14:00] ! [14:00] nope [14:00] how many directories are existing distinctly? [14:00] 2 or 3? [14:01] ! [14:01] sayan, or staging directory is an hypothetical directory? [14:01] ! [14:02] asraisingh: soumam007_: you working on the working directory, once done with changes move the changes to staging, and the finally create snapshot from staging [14:02] 3 i guess [14:02] sayan, power cut here. did i miss a lot. I'm getting any messages [14:02] asraisingh: 3 for now [14:02] sayan, got it [14:02] ! [14:02] asraisingh: yes, hypothetical, should be more clear when we do hands-on next [14:02] next [14:02] next [14:03] next [14:03] Is staging area overwrites the existing one or it will create a new one? [14:03] Is this staging area basically like a clipboard/buffer area? [14:03] Does staging area occupy extra space or memory [14:03] ok [14:04] batul: new one, you move your changes in there [14:04] but why not from working to snapshot directly? [14:04] is snapshot final directory? [14:05] saikat_: an area before the final snapshot/or commit creation [14:05] next [14:05] next [14:05] is snapshot final directory? [14:06] soumam007__, There are times when you don't want to commit little changes to directly. Staging act as intermediary where you club all the small commits and then send it from as a one commit [14:06] championshuttler: yes, directory is a hypothetical VCS theory, you will understand more during hands-on [14:07] im_mohsin: I did not answer soumam007__ because soumam007__ was out of turn [14:07] Moving ahead [14:07] People fire up your terminal [14:07] Tell me when done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] ok sayan [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] done [14:07] - mkdir foobar [14:08] done [14:08] done [14:08] - cd foobar [14:08] done [14:08] - vim helloworld.txt # write "Snapshot 1" inside the file [14:08] done [14:08] sayan, it was a continuation of my question :( [14:08] cd [14:08] done [14:08] done [14:08] done [14:08] done [14:08] im_mohsin, thats a good idea [14:08] done [14:08] done [14:08] done [14:09] done [14:09] done [14:09] done [14:09] done [14:09] done [14:09] done [14:09] done [14:09] soumam007__: Ok [14:09] Done [14:09] done [14:09] donw [14:09] done [14:09] done [14:09] done [14:09] - git add helloworld.txt # puts the file into staging area [14:09] done [14:10] done [14:10] done [14:10] - git commit -m "This is Snapshot 1" [14:10] done [14:10] error:fatal: Not a git repository (or any of the parent directories): .git [14:10] People stop writing done now [14:10] sayan, git init [14:10] is missing [14:10] <__anshul> do "git init" [14:10] I missed `git init` [14:11] Done [14:11] username and password is not set [14:11] cant commit [14:11] *- Before git add helloworld.txt [14:11] *- Do git init [14:12] *- People who have not setup username & email [14:12] santoshShaw, https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup [14:13] *- Do this git config --global user.name "" [14:13] *- git config --global user.email "" [14:13] ! [14:13] next [14:13] ! [14:14] lost the connection in between , what are we supposed to do before git add helloworld.txt ? [14:14] ! [14:14] CHOCOS: ask someone in PM to pass the log [14:14] next [14:14] ! [14:14] I finished the set up still it is showing fatal: Not a git repository [14:14] what is the erroe? [14:15] ! [14:15] cignatious: do : git init [14:15] sorry error [14:15] cignatious: did you do `git init`? [14:15] thank you [14:15] cignatious: it's not a git repo, that's why the error [14:15] next [14:15] next [14:15] Is user name and email id should be same as our github user name and mail id? [14:15] sayan, will you please reframe the format to set user name? "git config --global user.email """___Which part to change here? [14:16] just the email in the triangle brackets? [14:16] saikat_, Yes, without the quotes [14:16] saikat_ ,yes [14:16] git config --global user.name "Sayan Chowdhury" [14:16] sayan: yes i figured it [14:16] balaji: not necessary [14:16] git config --global user.email "gmail@yudocaa.in" [14:17] balaji: saikat_: This is how it should be [14:17] Remember there is Git != Github [14:17] git config --global user.email "hcakoff@gmail.com" [14:18] cignatious: cool :) [14:18] next [14:18] sayan: after git add helloworld.txt? [14:18] ! [14:18] poojaencoded: - git commit -m "Snapshot 1" [14:18] okay [14:18] poojaencoded: without the first hyphen [14:18] next [14:18] Why did we do, what we just did ? Like to just sum up, if you were going to explain that,ignore [14:19] vipulgupta2048_: yes, I will explain each and every step in detail [14:19] Moving ahead then [14:19] [14:19] [14:19] *- So, you create a project directory called foobar [14:19] ! [14:20] *- After that you initialize git into it, when you do git init it creates a .git directory inside foobar [14:20] *- You can check using ls -l [14:20] <__anshul> ls -al [14:21] *- This directory contains all the information by Git [14:21] <__anshul> .git is hidden [14:21] __anshul: Error: "git" is not a valid command. [14:21] oops, yes I missed -a [14:21] the correct command is ls -al [14:21] ls -la [14:21] thanks [14:22] tenida: install git [14:22] vivek_: Error: "install" is not a valid command. [14:22] there is some .git. Why can i not see the name? [14:22] oh [14:22] vivek_, tenida is bot [14:22] i understood [14:22] saikat_: that's dotfile [14:23] saikat type ls -al [14:23] ls [14:23] ani, did ls-al [14:23] with space between ls -al [14:23] ls-al command not found [14:23] <__anshul> the "-a" helps in shows hidden files [14:24] tenida : you need to install git not type `install git` [14:24] vishami3: Error: ":" is not a valid command. [14:24] saikat_, it should be ls -al [14:24] bhavin192, yes did ls -al in the console, typo here. [14:24] vipulgupta2048_: bhavin192: __anshul: can you stop helping saikat_? [14:24] <__anshul> okay [14:24] sayan, ok [14:25] ok [14:25] becase seems like saikat_ did raise hand before asking the question [14:25] s/did/did not/ [14:25] sayan, sorry [14:25] right [14:26] *- Next when you do, git add helloworld.txt, it sends the changes to the staging area [14:26] *- and finall git commit -m "Snapshot 1" is where you create the snapsot/commit [14:26] ls .git [14:26] im sorry. [14:27] Vamsi3296, instant messaging? [14:27] *- You specify the message with -m argument [14:27] bhavin192: yes, apologizing to instant messaging :) [14:28] No,This iterm is messing with me. [14:28] So, moving ahead [14:28] - vim helloworld.txt # Add "Snapshot 2" to the file [14:29] - git status [14:29] What do you see? Can some one write what does git status show? [14:30] <__anshul> modified: file.txt [14:30] modified: helloworld.txt [14:30] changes not staged for commit. [14:30] modified helloworld.txt [14:30] <__anshul> no changes added to commit [14:30] untracked file sayan [14:30] modified helloworld.txt [14:30] modified: helloworld.txt [14:30] modified helloworld.txt [14:30] no changes added to commit (use "git add" and/or "git commit -a") [14:30] modified: helloworld.txt [14:31] nothing added to commit but untracked files present [14:31] and modified: helloworld.txt. [14:31] https://pastebin.com/VvxBYUDM [14:31] modified: hello.text [14:31] changes not staged for comit [14:31] Hmm [14:31] Okay [14:31] modified: helloworld.txt [14:32] no changes added to commit (use "git add" and/or "git commit -a") [14:32] ! [14:32] So, you should be having an out like https://pastebin.com/VvxBYUDM [14:32] yes [14:33] yes [14:33] __anshul: poojaencoded: why are you having other filenames? [14:33] im_mohsin: untracked file? [14:33] next [14:33] next [14:33] <__anshul> I named it different, no worries [14:33] changes not staged for commit [14:33] ! [14:34] why is it so? [14:34] i gave my file name hello.txt that's why [14:34] __anshul: It is worries for other people who are learning for the first time [14:34] <__anshul> okay sayan I'll keep that in mind here onwards [14:34] the difference in output can confuse people [14:34] ! [14:35] cignatious: You will understand that after the next step that I tell [14:35] i created with vim hello.txt.sorry [14:35] cignatious: so, basically these changes are not yet in the staging area [14:35] sayan, this: nothing added to commit but untracked files present (use "git add" to track) [14:35] It is giving list of untracked files and not like one in pastebin [14:35] I did it again and now i am getting it as no changes added to commit [14:36] im_mohsin: you probably did not follow all the steps [14:36] am I doing it right? [14:36] anuGupta: you missed a bunch of steps [14:36] sayan, maybe because internet is not working properly [14:36] im_mohsin: anuGupta: ask someone in PM for the logs [14:36] ! [14:36] ok [14:37] cignatious: do you see the output as: https://pastebin.com/VvxBYUDM [14:37] next [14:37] You can use git add --all [14:37] no [14:37] Under untracked files it shows this to ".helloworld.txt.swp". What is this file? [14:37] vipulgupta2048_: you vim session is probably still open, we explained this in last class [14:38] cignatious: can you past the output in pastebin, on what do you see? [14:38] Shruti9520, thanks :) [14:38] ok [14:38] anuGupta: Also wait before you ask you question [14:38] You must have not saved it, i think [14:38] anuGupta: wait for your turn [14:39] next [14:39] ! [14:39] next [14:39] next [14:39] cignatious, just a word of caution to copy from terminal you have to use ctrl+shift+c [14:39] what does "-m" signifies in the git commit -m "hello" ? [14:39] sayan, will recheck. [14:39] santoshShaw: check the log, I explained [14:39] Ok sayan [14:40] santoshShaw It is commit message [14:40] those who are getting "untracked files", you should add a file first using "git add file.ext" [14:40] message that'll explain the changes [14:40] fhackdroid: i know [14:41] vishami3: meamitk : sayan, thanks [14:41] Moving ahead [14:41] - git diff [14:41] santoshShaw: after writing -m , you give any message to your commit. You can write anything within quotes [14:42] *- With this command you can check the diff, basically the changes you've done but not in stage [14:42] - git add -u [14:42] ! [14:43] *- ^^ this moves the changes to the staging area [14:43] ! [14:43] *- git status [14:43] ikshitij, though i am not getting so but why are they getting that message? [14:44] soumam007__: What r u getting ? [14:44] *- Now you would see a different output, as these files are added staging area before the commit [14:44] andodococo, "changes not staged for commit" [14:45] and no message [14:45] language please [14:45] andodococo, r? u? [14:45] ! [14:46] ! [14:46] next [14:46] sayan, git diff compare changes in the working directory and staging area? [14:46] im_mohsin: yes [14:46] next [14:46] What is the meaning of the symbols - and + and a &b in "--- a/helloworld.txt [14:46] +++ b/helloworld.txt [14:46] " after doing git diff? [14:46] [14:47] <__anshul> saikat that means you added some stuff to the said file [14:47] saikat_: - means removed, + means added = this is in code portion [14:48] <__anshul> ! [14:48] sayan, and the a & B act as bullet points? [14:48] saikat_: and --- a/helloworld.txt +++ b/helloworld.txt means you are comparing a/helloworld.txt with b/helloworld.txt [14:48] next [14:48] what does -u means ? [14:49] vishami3: update, moves all the changes from working to staging [14:49] vishami3: and you don't have to add file one by one [14:49] next [14:49] next [14:49] okay [14:50] <__anshul> as I answered some queries here, is that acceptable or should I just not interrupt? [14:50] ! [14:50] ! [14:50] vishami3: The -u tells Git to remember the parameters, so that next time we can simply run git push and Git will know what to do. Link: https://try.github.io/levels/1/challenges/11 [14:50] __anshul: it's okay to answer [14:51] ! [14:51] santoshShaw, it's totally different [14:51] thanks [14:51] santoshShaw: no, we are not discussing git push now [14:51] next [14:51] next [14:51] sayan: Why aren't we doing git add . ? [14:52] cran-cg: that adds all the files which are untracked also [14:52] Plus isn't git push - u different from git add -u [14:52] "@@ -1 +1,3 @@" what does this mean? [14:52] cran-cg: yes, it is totally different [14:52] ! [14:53] ! [14:53] cran-cg: you want to carefully add the untracked files [14:53] And the -u flag is different for both the commands right ? [14:53] cran-cg, yes [14:54] Understood ! Thanks bhavin192 and sayan :)) [14:54] i think every sub-command has there own flags that's why *push -u* is different from *add -u* [14:54] soumam007__: tell you the numbers of lines added & removed and line numbers [14:54] vishami3: yes [14:54] Moving ahead [14:54] - git diff --staged [14:55] My question,sayan ? [14:55] vipulgupta2048_: yes, you will get your chance but we cannot take all the questions at once [14:55] then probably we never going to end the class [14:56] Ok no issues. [14:56] *- If you do git diff --staged, you see all the changes in the staging area [14:56] *- So it's good to check once before you make the final commit [14:57] - git commit -m "Snapshot 2" [14:57] *- You now create your next commit [14:57] - vim hellomars.txt # Add the text "Snapshot 3" [14:57] - git status [14:58] nothing to commit [14:58] *- Now, you will see hellomars.txt in the untracked files, because the file is a git directory [14:58] ! [14:58] *- But the changes of the file are not getting tracked by git yet [14:59] *- To add the file hellomars.txt for git to track what command show we use? [14:59] Think and answer [14:59] git add -u [14:59] git add [14:59] git add [14:59] git add -u [14:59] git add filename [14:59] git add hellomars.txt [15:00] git add hellomars.txt [15:00] <__anshul> soumam007__git add [15:00] git add filename [15:00] git add hellomars.txt [15:00] git add hellomars.txt [15:00] git add hellomars.txt [15:00] <__anshul> oops [15:00] git add hellomars.txt [15:00] git add -u [15:00] git add hellomars.txt [15:00] git add hellomars.txt [15:00] git add -u [15:00] git add hellomars.txt [15:00] right! it's git add hellomars.txt, can somebody tell me why not git add -u? [15:00] or git add . or git add * [15:00] git add hellomars.txt [15:01] <__anshul> because "git add -u" is for files who are already staged once [15:01] sayan because you want be aware of what you’re adding? [15:01] sayan, because it only checks the added file for updates [15:01] *git add -u* will not look for changes in *untracked8 files [15:01] I think git add -u will add all untracked files. [15:01] Because git add -u will add all files to track in the folder. when dealing with more than one file. [15:01] because -u updates the files which are already tracked [15:01] sayan: we are adding, not updating [15:01] that will add all untracked files i think [15:02] ls [15:02] Okay, here is why? [15:02] git add -u update all changes [15:02] git add hellomars.txt [15:02] as the documentation says for `-u` = all tracked files in the entire working tree are updated [15:02] it's does not touch the untracked files [15:03] git add -u moves the diff of the tracked files to staging, and ignore all the untracked files you add [15:03] sayan understood [15:03] so sayan for already existing file in staging area and now if we add a line to this file then we use git add -u? Correct? [15:04] So, you should explicitly use git add to tell git track the file from next time and directly move the changes to stage [15:04] sayan: got it [15:04] <__anshul> im_mohsin correct [15:04] ! [15:04] sayan: OK. :thumbs-up [15:04] im_mohsin: yes :) [15:04] next [15:04] next [15:04] __anshul, thank you. I get confused with parameter [15:05] sayan,Doubt resolved [15:05] next [15:05] git add -u not working [15:06] realslimshanky: you should never use dot (.) or asterisk (*) until and unless you know what you are doing [15:06] ani_: context? [15:06] next [15:06] sayan, got it :) [15:06] git add accepts wild cards? [15:06] jasonbraganza: yes [15:06] Thank you [15:06] ! [15:06] next [15:07] Wild cards ? or should i just google that [15:07] <__anshul> ani_ error message? [15:07] Yeah google :) [15:07] you probably will find a wiki page for it [15:07] - git add hellomars.txt [15:07] sorry it work [15:07] *- So add the hellomars.txt file [15:07] - git commit -m "Snapshot 3" [15:08] *- And then we commit [15:08] ! [15:08] next [15:08] Any questions till here? [15:09] No [15:09] nope. [15:09] No [15:09] no [15:09] ! [15:09] it was producing error nothing to commit, working directory clean [15:09] no [15:09] Wild card is used for adding more than one files for git add [15:09] ! [15:10] vipulgupta2048_, yeah, like dot ( . ) and asterisk ( * ) [15:10] ani_: did you create the hellomars.txt file? [15:10] vipulgupta2048_: not exactly [15:10] ani_ it is not an error [15:10] no [15:10] ok thanks [15:10] realslimshanky, will look that up, thanks. [15:10] realslimshanky: dot is not a wildcard [15:10] cran-cg, then ? [15:11] ! [15:11] vipulgupta2048_: https://www.computerhope.com/jargon/w/wildcard.htm [15:11] ! [15:11] next [15:11] What is this create mode number in "create mode 100644 hellomars.txt"? [15:11] saikat_: ah! nice question [15:12] There is actually a good answer in SO [15:12] ! [15:12] next [15:12] i think it is similar to taking a snapshot for that commit file [15:12] Can we able edit the commit messeges? [15:12] Got the answer [15:12] saikat_: https://stackoverflow.com/questions/737673/how-to-read-the-mode-field-of-git-ls-trees-output/8347325#8347325 [15:12] balaji: yes, you can. git commit --amend -m "New message" [15:12] next [15:13] next [15:13] why we will add (.) ?Is it that . .. you are talking about that are hidden and present in all directories? [15:13] soumam007__: no, this is completely different thing [15:13] sayan, But how can we specify which commit messege we have to edit ? [15:14] ok please elaborate if possible [15:14] balaji: you cannot do that by specifying like a commit id [15:14] ! [15:14] balaji: but there is a way which is out of scope of this class [15:15] soumam007__: yes, when you do git add . it moves all the files from untracked & tracked to stage [15:15] next [15:15] sayan, Okay we will discuss after the class [15:15] next [15:15] sayan, it's for adding hidden files ( which begin with . ) also along with others right? What is it called? [15:15] sayan,not got "create mode 100644 hellomars.txt"? [15:15] ok and what for git add * ? [15:15] soumam007__: same [15:15] ok :) [15:16] what is this and why is this? [15:16] poojaencoded: it's okay, if you don't get it now [15:16] soumam007_, adding all the files except hidden ( starting with . ) files. [15:16] okay [15:16] <__anshul> poojaencoded you would have got this when you committed [15:17] soumam007__: https://stackoverflow.com/questions/16969768/what-does-git-add-git-add-single-dot-command-do . Files present in currentdirectory and subdirectory [15:17] _anshul:thanks [15:17] realslimshanky, cran-cg i will look into it thanks :) [15:17] soumam007__: right git add * does not add the hidden files [15:17] where as git add . does [15:18] ok there is the difference [15:18] but at the end of the day you should not use both [15:18] realslimshanky: I don't know if it is called anything [15:18] next [15:18] sayan, so that we can distinguish right? [15:19] sayan, okay. [15:19] ! [15:19] soumam007__: no, you will mess up if you use that [15:19] soumam007__: you will end up changes that you don't want to add [15:19] oh [15:19] next [15:19] sayan, SO says "1000000110110100 (100664): Regular non-executable group-writeable file." Why is it not executable? I am executing it in git. [15:20] <__anshul> soumam007__ then later you have to sit down and unstage unnecessary files [15:20] <__anshul> for example the local files an IDE generates which are not needed in project repo [15:20] roll call: Razy Kased [15:21] saikat_: you are not executing it with Git [15:21] rkased: ? Why the roll call out of sudden? [15:21] __anshul, yeah thats an issue [15:21] I've been having login issues sorry [15:21] sayan, ohh, i am just commiting a change, right? [15:22] saikat_: I will discuss this after class [15:22] <__anshul> soumam007__, I am guessing sayan will you later about ignoring [15:22] sayan, ok, thanks [15:22] Missed the class. Internet issues :-( [15:22] I am ending the class here. [15:22] ok sayan :) [15:22] I would like to tell a few things [15:23] __anshul, didnot get you please rephrase if possible [15:23] :) [15:23] You cannot become a pro in the very first day [15:23] So, learn to ignore things [15:23] <__anshul> in DMs may be ;) [15:23] okay [15:23] okay sayan [15:23] You don't need to learn each an everything on the very first day [15:24] Stick to the basics, you can build on top of basics [15:24] sayan, I always feel if I don't I need doing enough. However, your advice helps put things into perspective [15:24] soumam007 anshul depends on your gitignore which sayan will tell you later [15:25] <__anshul> , correct [15:25] and people those who know stuff, take care in mind there are people who don't know stuff and are learning [15:25] So, stop throwing random words, it's becomes difficult for those who are just trying to follow and learn [15:26] sayan agreed [15:27] I did not know a lot of things like +++ a/... --- b/, then 100664, until I had been using git for 2-3 years [15:27] sayan,you are right it is difficult for us [15:27] relatable ;) [15:27] And those you are new, try to be often on IRC and ask question. Just doing join in for the class [15:27] And devote more time than just reading logs [15:28] ask for books from people [15:28] sayan, 100% true. I faced issues initially where i wanted to know every stuff the point i start but its a very bad learning habit [15:29] That's all what I want to say, from next time in class I would just tell you too stop if things would be tough for other people [15:29] and I want people to follow that [15:29] understood sayan [15:29] You can ask those questoins after the class [15:29] sayan, nice :) [15:29] sure [15:29] Telling this because things are going to be difficult in next class, so I want cooperation from all of you [15:30] Roll Call [15:30] Santosh Kumar Shaw [15:30] Jason Braganza [15:30] Bhavin Gandhi [15:30] Anupama Shipurkar [15:30] right sayan [15:30] Razy Kased [15:30] Suraj Ghimire [15:30] Vipul Gupta [15:30] Robin Schubert [15:30] <__anshul> Anshul Chauhan [15:30] Vamsi Krishna [15:30] Anu Kumari Gupta [15:30] Saikat Dey [15:30] Abhishek Singh [15:30] Atul kumar [15:30] deep [15:30] Mohsin Mumtaz [15:30] Chiranjeev Gupta [15:30] Balaji [15:30] Deepika Upadhyay [15:30] Priyanka Sharma [15:30] Kshitij [15:30] Amarjeet singh [15:30] Anuja Agarwal [15:30] Amit Kokitkar [15:30] Himanshu Awasthi [15:30] Vipul Siddharth [15:30] pooja kumari singh [15:30] pavan yejare [15:30] Shashank Shekhar [15:30] Ashwani Kumar Gupta [15:30] Nikita Kotak [15:30] Shivani Mehendarge [15:30] Akshay Gaikwad [15:30] Aniket uttam [15:30] Avik Mukherjee [15:30] Mayur khomane [15:30] Shashank Kumar [15:30] yurii pylypchuk [15:30] Onyinye Madubuko [15:30] Samridhi Agarwal [15:30] devendra bhat [15:30] Aryan tripati [15:30] Niranjana Deshpande [15:30] kshithij Iyer [15:30] sayan, sorry on their behalf . Farhaan[m] , __anshul i got the hint. future classes will make my concepts more clear [15:31] Gaurav Sitlani [15:31] Messi Fc [15:31] Soumam Banerjee [15:32] ! [15:32] Jitesh Pabla [15:32] Ravindra Lakal ----END CLASS----