Perl 6 - the future is here, just unevenly distributed

IRC log for #git, 2016-12-04

| Channels | #git index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:06 fragMental joined #git
00:07 boombatower joined #git
00:08 cyphase joined #git
00:09 chachasmooth joined #git
00:15 nettoweb joined #git
00:16 pothepanda joined #git
00:17 sharkile joined #git
00:22 nettoweb joined #git
00:23 a3Dman joined #git
00:25 TikityTik How am I able to go through all the changes I made and make a commit for each change describing what was done?
00:25 pks joined #git
00:26 bn0t joined #git
00:27 lindenle joined #git
00:31 texinwien_ joined #git
00:31 dreiss joined #git
00:33 masak TikityTik: have you found `git commit -p` yet?
00:34 TikityTik masak: What does it do?
00:35 rewt man git commit
00:35 gitinfo the git-commit manpage is available at http://jk.gs/git-commit.html
00:35 ws2k3 joined #git
00:35 kaldoran joined #git
00:36 TikityTik And it's always a good idea to have small commits aka patches?
00:40 msonntag joined #git
00:43 masuberu joined #git
00:45 masuberu joined #git
00:46 kyan joined #git
00:50 SpeakerToMeat joined #git
00:52 ramsub07 joined #git
00:52 rwb joined #git
00:55 fahadash joined #git
00:55 tmcmahon joined #git
00:56 jaguarmagenta joined #git
01:03 masak TikityTik: "small" isn't an end goal in itself -- rather, try to look for the smallest possible change that makes sense independently.
01:05 masak TikityTik: the smallest possible change might still involve something like 5 or 50 or 500 files. just as long as it takes the project from one working state to another. (hopefully a better one along some axis.) and preferably it shouldn't be possible to break it up into smaller steps.
01:05 dirtyroshi joined #git
01:07 chachasmooth joined #git
01:10 TikityTik It's just that it's hard to remember all the changes that were made.
01:10 TikityTik so I never know what I forget what to put in the commit message
01:10 TikityTik Can commit messages be multiline? Should they be multine line with likes dashes infront of each change?
01:11 j416 TikityTik: "git diff" to show the changes; "git add -p" to add changes separately, "git commit -v" to show the diff as a help when writing your message and read http://tbaggery.com/2008/04/19/a-n​ote-about-git-commit-messages.html
01:11 TikityTik what the difference between git commit -v and git diff?
01:11 j416 one is an apple the other is an orange
01:12 j416 one commits, the other produces a diff
01:13 j416 also, strive to commit often to avoid ending up with a ton of unrelated changes
01:15 gfixler joined #git
01:18 buffal0 joined #git
01:21 netj joined #git
01:21 Rodya_ joined #git
01:22 ResidentBiscuit joined #git
01:26 masak what's a way to check whether a given ref exists? I know about `git update-ref`, but that doesn't seem to be it.
01:27 steelsw0rd joined #git
01:30 NeverDie joined #git
01:30 smithbone joined #git
01:31 BlessJah masak: would git-rev-parse do?
01:35 kaldoran joined #git
01:38 jnewt joined #git
01:39 telephone joined #git
01:39 telephone joined #git
01:40 stevenbenner joined #git
01:44 brokensyntax joined #git
01:46 idr0p joined #git
01:49 Literphor joined #git
01:51 mizu_no_oto joined #git
01:53 ajpiano joined #git
01:58 TikityTik I haven't pushed, how do I undo my last commit but not get rid of the changes? I accidentally deleted my changed with git reset --hard HEAD~1 before.
01:59 giraffe joined #git
01:59 kadoban TikityTik: Same thing without --hard
01:59 TikityTik I'm scared
01:59 kadoban TikityTik: !backup
01:59 gitinfo TikityTik: Worried about your data while trying stuff out in your repo? The repository in its entirety lives inside the .git directory in the root of your work tree so to backup everything `cp -a path/to/workdir path/to/backup` or equivalent will suffice as long as the repo is not modified during backup. See also http://sethrobertson.github.c​om/GitBestPractices/#backups
02:00 kadoban TikityTik: You can recover from git reset --hard  usually too, by the way, with the reflog
02:00 kadoban 'git reflog' or 'git reflog thebranch' will typically allow you to see the commit(s) you've nuked that way.
02:01 TikityTik read the man page, but I still don't understand git reflog
02:04 Vampire0 joined #git
02:05 buffal0 joined #git
02:07 finalbeta joined #git
02:11 Limes_ joined #git
02:12 pks joined #git
02:12 peeps[lappy] joined #git
02:15 arescorpio joined #git
02:16 Celelibi I just did a git commit --fixup, but put the wrong commit id.
02:16 Celelibi I know I can rebase by hand, but is there a way to fix the fixup commit?
02:19 adymitruk joined #git
02:20 ment0s joined #git
02:20 ment0s hi
02:20 gitinfo ment0s: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.
02:21 steelsw0rd joined #git
02:21 ment0s does git affect files in repository in any way as with some sort of headers etc like svn ?
02:22 atrus joined #git
02:22 pikajude joined #git
02:23 anonymuse joined #git
02:26 SegFaultAX joined #git
02:26 isysd joined #git
02:27 d^sh joined #git
02:35 Rodya_ joined #git
02:36 kaldoran joined #git
02:37 diogenese joined #git
02:37 venmx joined #git
02:39 ResidentBiscuit joined #git
02:48 ilbot3 joined #git
02:48 Topic for #git is now Welcome to #git, the place for git help and serious business | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.11.0 | Getting "cannot send to channel"? /msg gitinfo .voice | The git-jokes project has been suspended for lack of contribution. Help revive it! https://madeitwor.se/git-jokes
02:49 mario_ joined #git
02:50 EmeraldExplorer joined #git
02:50 zerorax joined #git
02:51 zerorax how do i make a file update? when i did git commit -m "changes here" it said 2 files were updated, but when I did git push -u origin master it said everything is up to date, and the file is not updated in the repo
02:52 Sigma joined #git
02:55 ResidentBiscuit joined #git
02:57 g5pw joined #git
02:58 idr0p joined #git
02:58 brokensyntax joined #git
03:02 ResidentBiscuit joined #git
03:06 hexagoxel joined #git
03:08 bocaneri joined #git
03:08 chachasmooth joined #git
03:09 ochorocho__ joined #git
03:09 sunri5e joined #git
03:09 bn0t_ joined #git
03:12 cbegin joined #git
03:14 bn0t joined #git
03:14 Sigma joined #git
03:16 nedbat zerorax: hi :)  Did you add the files?
03:16 zerorax yes nedbat:D
03:16 zerorax I actually figured it out
03:16 zerorax I don't know why it didn't work the first time
03:16 nedbat zerorax: ok, carry on :)
03:17 red82 joined #git
03:17 zerorax thanks though
03:17 Sigma joined #git
03:18 ResidentBiscuit joined #git
03:19 Sigma joined #git
03:19 cbegin left #git
03:21 spriz joined #git
03:22 cxreg joined #git
03:23 dodobrain joined #git
03:23 dodobrain joined #git
03:27 tmsmith_ joined #git
03:29 JamesBaxter joined #git
03:31 red82 joined #git
03:32 dreaddymck joined #git
03:34 texinwien_ joined #git
03:35 anonymuse joined #git
03:38 Nilesh_ joined #git
03:41 padde_ joined #git
03:41 padde_ joined #git
03:41 xwid joined #git
03:41 dooglius joined #git
03:43 unreal joined #git
03:45 slappymcfry joined #git
03:46 cmn joined #git
03:46 Atm0spher1c joined #git
03:51 finalbeta joined #git
03:53 jgrasser joined #git
03:54 ghostlight joined #git
03:55 sargas joined #git
03:55 sargas joined #git
03:55 Ryanar joined #git
03:55 svm_invictvs joined #git
03:56 peeps[lappy] left #git
04:00 sdothum joined #git
04:00 Sleepy63 joined #git
04:02 bn0t_ joined #git
04:04 bn0t__ joined #git
04:06 kaldoran joined #git
04:08 venmx joined #git
04:08 hexagoxel joined #git
04:09 Rodya_ joined #git
04:09 ochorocho__ joined #git
04:12 Thorn joined #git
04:14 jmpp joined #git
04:14 Vortex35 joined #git
04:15 sdothum joined #git
04:15 lindenle joined #git
04:16 xo_odin joined #git
04:16 davix[matrix] joined #git
04:17 fmcgeough joined #git
04:17 tmz joined #git
04:18 azerus joined #git
04:19 tehtraveler2321 joined #git
04:25 qws-user-1228 joined #git
04:25 mizu_no_oto joined #git
04:25 acr4 joined #git
04:26 atomi joined #git
04:26 alyptik joined #git
04:28 Goplat joined #git
04:28 Synthead joined #git
04:28 patrickr[m] joined #git
04:28 Tiaan[m] joined #git
04:28 kineticrootkit[m joined #git
04:28 Sheogorath[m] joined #git
04:28 M-nated joined #git
04:28 unclechu joined #git
04:28 Remramm joined #git
04:28 Start[m] joined #git
04:28 kikijiki[m] joined #git
04:28 WillianPaiva[m] joined #git
04:28 saintaquinas[m] joined #git
04:28 hallogallo[m] joined #git
04:28 samwise[m] joined #git
04:28 M-shine joined #git
04:28 malo[m] joined #git
04:28 fstd joined #git
04:28 Dhanya[m] joined #git
04:28 M-meznak joined #git
04:28 mtso[m] joined #git
04:28 M-mistake joined #git
04:28 monomon[m] joined #git
04:28 mei[m] joined #git
04:29 am2on joined #git
04:29 aviraldg joined #git
04:29 Ineentho[m] joined #git
04:29 musicmatze[m] joined #git
04:29 warrantyvoid joined #git
04:29 alaeri[m] joined #git
04:29 srkrishna[m] joined #git
04:29 timlyo[m] joined #git
04:29 Carlos[m] joined #git
04:29 kjsage[m] joined #git
04:29 daopu[m] joined #git
04:29 M64137[m] joined #git
04:29 eltopo[m] joined #git
04:30 tax joined #git
04:32 Karazhan joined #git
04:38 tristanp joined #git
04:40 yanome joined #git
04:41 yohnnyjoe joined #git
04:41 rwp joined #git
04:41 slappymcfry joined #git
04:41 NeverDie joined #git
04:45 umpc joined #git
05:01 KL4JC joined #git
05:05 govg joined #git
05:09 venmx joined #git
05:10 ochorocho__ joined #git
05:12 NeverDie joined #git
05:14 sssilver joined #git
05:15 johnny56 joined #git
05:16 a3Dman joined #git
05:19 ResidentBiscuit joined #git
05:20 leprechau joined #git
05:21 anonymuse joined #git
05:26 kaldoran joined #git
05:33 pks joined #git
05:34 blackwind_123 joined #git
05:34 harleypig left #git
05:46 blackwind_123 joined #git
05:47 languitar joined #git
05:50 xall_ joined #git
05:51 Rr4sT joined #git
05:53 Learath2 joined #git
05:54 anonymuse joined #git
05:56 reverse_light joined #git
05:59 Cabanossi joined #git
06:10 venmx joined #git
06:11 ochorocho__ joined #git
06:13 Rodya_ joined #git
06:16 fatalhalt joined #git
06:18 Nikitaw99 joined #git
06:18 allaroundArtist joined #git
06:19 MrWoohoo joined #git
06:27 shinnya joined #git
06:30 PioneerAxon joined #git
06:30 vuoto joined #git
06:32 aihika joined #git
06:39 bket joined #git
06:40 qguv joined #git
06:40 larrybolt joined #git
06:41 d0nn1e joined #git
06:41 Naan left #git
06:45 snowinferno joined #git
06:46 dsantiago joined #git
06:48 snufft joined #git
06:50 breezy_ joined #git
06:54 valkyr2e joined #git
06:58 mda1 joined #git
07:00 venmx joined #git
07:01 Garen joined #git
07:01 LucaTM joined #git
07:05 xall joined #git
07:11 vuoto joined #git
07:14 User458764 joined #git
07:20 chamow joined #git
07:20 Vortex35 joined #git
07:22 xall joined #git
07:22 ochorocho__ joined #git
07:25 YuGiOhJCJ joined #git
07:26 crayon joined #git
07:27 chamow left #git
07:27 dreiss joined #git
07:28 Khisanth joined #git
07:28 xall joined #git
07:28 chamow_ joined #git
07:32 xall i'm curious about tags. i'm working through a design patterns book and was thinking tagging commits by chapter to better navigate them
07:33 xall so i have a starting tag, but should i make an ending tag as well?
07:33 xall does this seem like a reasonable use of tags?
07:37 Andrew_K|2 joined #git
07:39 Oebele joined #git
07:43 Nikitaw99 joined #git
07:45 Nikitaw99 joined #git
07:49 User458764 joined #git
07:50 iliv joined #git
07:54 dsdeiz joined #git
07:54 dsdeiz joined #git
07:55 krillr joined #git
08:00 venmx joined #git
08:03 tango_ joined #git
08:07 Random832 joined #git
08:07 TomyLobo joined #git
08:08 bn0t_ joined #git
08:09 Literphor joined #git
08:10 bmahe joined #git
08:10 bn0t joined #git
08:15 ToBeCloud joined #git
08:16 howitdo joined #git
08:17 mkoskar joined #git
08:18 ToBeCloud joined #git
08:19 ToBeCloud joined #git
08:20 Ardethian\work joined #git
08:20 Ardethian\work joined #git
08:20 ToBeCloud joined #git
08:23 Nikitaw99 hm?
08:25 aollier joined #git
08:27 AfroThundr joined #git
08:28 tnecniv joined #git
08:31 realz joined #git
08:34 jost_ joined #git
08:35 ak5 joined #git
08:35 Orbitrix joined #git
08:35 Orbitrix joined #git
08:37 flavius joined #git
08:37 ak5 hi, is there a way I can do the reverse of git add -p so take unstaged changes and revert them (instead of staging them)
08:37 spacelord_ joined #git
08:39 ak5 ok as soon as I wrote that, I figured I should check the git checkout manpage for a -p option - lo and behold it's there... thanks irc :)
08:40 j416 ak5: git reset -p
08:41 ak5 hm I don't know of reset actually, will look that up, for me git checkout -p -- filename was what I was looking for
08:41 j416 ak5: "git checkout -p" is not the opposite of "git add -p".
08:42 j416 ak5: "git status" will give you some hints about how to do things to the index.
08:42 ak5 j416: yeah it's how i learned about checkout: (use "git checkout -- <file>..." to discard changes in working directory)
08:43 j416 ak5: yes. discard changes is not the same as "un-adding" them
08:44 j416 ak5: be sure to !backu
08:44 gitinfo ak5: [!backup] Worried about your data while trying stuff out in your repo? The repository in its entirety lives inside the .git directory in the root of your work tree so to backup everything `cp -a path/to/workdir path/to/backup` or equivalent will suffice as long as the repo is not modified during backup. See also http://sethrobertson.github.c​om/GitBestPractices/#backups
08:44 j416 p
08:44 ak5 right, ok, messed up terminology, my bad :) In my mind I think of levels worktree->staging->committed so I wanted a step down from worktree if that makes sense...
08:45 j416 worktree->staging->committed makes sense
08:45 j416 which means that there is nothing below "worktree"
08:45 j416 so "stepping down" from there means throwing away your change
08:45 ak5 discarded, yeah
08:46 User458764 joined #git
08:46 ak5 reset looks like a better way to do what I do with git stash and git checkout, thanks for that
08:46 ak5 git is pretty cool :)
08:46 venmx joined #git
08:47 boombatower joined #git
08:48 alyptik joined #git
08:49 LucaTM joined #git
08:51 overlord_tm joined #git
08:55 alyptik joined #git
08:55 t-mart joined #git
08:59 codebam joined #git
09:04 babilen joined #git
09:05 vuoto joined #git
09:14 vuoto joined #git
09:15 ochorocho__ joined #git
09:18 King_Hual joined #git
09:18 King_Hual joined #git
09:19 aw1 joined #git
09:21 bn0t_ joined #git
09:21 PioneerAxon joined #git
09:24 floatingman joined #git
09:30 meZee joined #git
09:31 eivarv joined #git
09:33 j416 I'm having trouble understanding the use of this project. Can anyone give an example of a situation where it might be useful? http://www.procode.org/stgit/
09:33 Dragonbird joined #git
09:33 SteffanW joined #git
09:33 jmleo joined #git
09:35 ResidentBiscuit joined #git
09:40 muelli joined #git
09:45 jaguarmagenta joined #git
09:49 seishun joined #git
09:50 vrlx joined #git
09:52 SourTrout joined #git
09:52 j416 is there a difference between "git log 1234abcd^-1" and "git log 1234abcd^.."?
09:53 ahmedelgabri joined #git
09:54 grawity yes, the former is more like 1234abcd^..1234abcd
09:54 grawity while the latter is 1234abcd^..HEAD
09:54 alyptik joined #git
09:54 grawity so one only gets you commits brought in by that merge
09:54 j416 ah, nice.
09:54 grawity the other gets you commits *ever since* that merge happened
09:55 j416 thanks
09:55 frobnic joined #git
09:56 alyptik joined #git
09:57 t0by joined #git
09:57 t0by joined #git
09:58 bn0t__ joined #git
10:00 robotroll joined #git
10:01 bn0t joined #git
10:04 lindenle joined #git
10:07 eivarv joined #git
10:09 vdv joined #git
10:10 AfroThundr joined #git
10:10 bn0t_ joined #git
10:10 jnavila joined #git
10:11 gigq joined #git
10:13 m0viefreak joined #git
10:13 bmahe joined #git
10:14 User458764 joined #git
10:15 courrier joined #git
10:16 King_Hual` joined #git
10:16 m1dnight_ joined #git
10:21 nikivi joined #git
10:22 inovas joined #git
10:23 rolha joined #git
10:26 toogley joined #git
10:28 catsup joined #git
10:28 catsup joined #git
10:30 texinwien_ joined #git
10:31 cyphase joined #git
10:32 satifant joined #git
10:35 darkbit joined #git
10:36 SteffanW joined #git
10:38 cxreg joined #git
10:41 fugiman left #git
10:45 mar77i joined #git
10:50 sobersabre joined #git
10:50 sobersabre I think I did something stupid and I'm tracking with my local master branch 2 remotes.
10:51 sobersabre I want to track origin/master with master and upstream/master with upstream-master
10:51 netj joined #git
10:51 sobersabre how do I see what my current branch is tracking and how do I remove them bad remote branches I don't like ?
10:54 sobersabre I think I figured this out: I did git branch --unset-upstream, and then git branch --set-upstream-to=origin/master
10:57 rominronin joined #git
10:57 DrRobotic joined #git
10:59 j416 sobersabre: and the answer to the first question would be "git branch -vv"
10:59 j416 sobersabre: (or just "cat .git/config")
11:00 pikajude joined #git
11:00 raatiniemi joined #git
11:02 thesha joined #git
11:04 irqq_ joined #git
11:06 thesha i added a file using git add <filename> then i use git diff ,it was showing difference but i thought some mistake in doing changes so i use git diff -cached and now when i am doing git diff for other files still the previous one appear on the screen
11:06 thesha if i commit will it create problem
11:07 cyphase joined #git
11:07 bcc joined #git
11:07 bcc joined #git
11:08 rivarun joined #git
11:08 thesha http://paste.fedoraproject.org/498220/
11:09 thesha please answer
11:09 ramsub07 joined #git
11:10 yohnnyjoe joined #git
11:12 rominronin joined #git
11:14 seishun joined #git
11:14 vdv how can i add files which do not have specific extension to gitignore? i need something like "!*.java", i.e. ignore all files except with extension *.java
11:16 complain_ joined #git
11:16 bcc joined #git
11:16 bcc joined #git
11:17 vdv ah, found it here: http://stackoverflow.com/questions/987142/make-​gitignore-ignore-everything-except-a-few-files
11:26 ShekharReddy joined #git
11:28 SourTrout joined #git
11:29 muelli joined #git
11:29 cyan__ joined #git
11:31 subhojit777 joined #git
11:32 Learath2 joined #git
11:32 rolha joined #git
11:38 jarnos joined #git
11:38 d0nn1e joined #git
11:41 ShekharReddy joined #git
11:47 rolha joined #git
11:51 afuentes joined #git
11:54 chachasmooth joined #git
11:54 aard_ joined #git
11:56 ispn joined #git
11:56 Emperor_Earth joined #git
12:02 jottr joined #git
12:05 lineinthesand joined #git
12:06 vrlx joined #git
12:06 Rodya_ joined #git
12:07 vuoto joined #git
12:07 bn0t__ joined #git
12:08 pks joined #git
12:09 jarnos I wonder, if it is good to place executable/scripts in usr/bin/ under working directory? Or right under working directory? Can the directory structure under working directory be changed afterwards?
12:09 lineinthesand I'm bisecting the kernel to find a regression. Now I had to skip several steps because the kernels built would not boot. The skips go back in the history towards the good kernels. Sometimes its only one commit, then again a large jump. When it's a large jump, once the kernel boots again, its a good kernel. Is there a way I can direct the bisection to go towards the bad kernel to limit the range?
12:12 lineinthesand I forgot to mention: it goes back in history from the last good commit into the direction of another good commit.
12:13 robotroll joined #git
12:14 ment0s joined #git
12:22 seishun joined #git
12:23 King_Hual joined #git
12:25 King_Hual` joined #git
12:27 diri joined #git
12:28 ramsub07 joined #git
12:29 frobnic joined #git
12:34 King_Hual joined #git
12:34 mseyne joined #git
12:36 Rodya_ joined #git
12:37 jfr_ joined #git
12:37 mindriot101 joined #git
12:38 Rodya__ joined #git
12:38 King_Hual` joined #git
12:42 jaguarmagenta joined #git
12:43 mindriot101 joined #git
12:45 cqi joined #git
12:46 jaguarmagenta joined #git
12:46 chachasmooth joined #git
12:47 cqi joined #git
12:48 mar77i_ joined #git
12:49 LucaTM joined #git
12:56 frobnic joined #git
12:58 cqi joined #git
13:01 blackwind_123 joined #git
13:02 shiriru joined #git
13:03 Rodya_ joined #git
13:04 shashin joined #git
13:04 Learath2 joined #git
13:05 Nikitaw99 joined #git
13:07 diogenese joined #git
13:07 lucido joined #git
13:08 lucido Is source branch of the merged in commits recorded in the log of my master branch?
13:08 lucido the*
13:13 HoierM joined #git
13:13 rorro joined #git
13:14 Rodya_ joined #git
13:16 leeN joined #git
13:16 chachasmooth joined #git
13:18 shashin joined #git
13:22 Mikerhinos joined #git
13:25 re1 joined #git
13:27 ams__ joined #git
13:29 SteffanW joined #git
13:34 j416 lucido: not its name.
13:34 j416 lucido: but the commits.
13:34 chachasmooth joined #git
13:34 lucido j416, hmm, then I have to manually insert the relevant fature name in my commits
13:35 lucido instead of using the branch name
13:35 buffal0 joined #git
13:35 j416 lucido: the name of the branch is normally populated for you in the commit message of the merge.
13:36 lucido I don't see that in git log
13:36 lucido maybe it's in a detaild log output
13:37 ResidentBiscuit joined #git
13:40 Limes_ joined #git
13:43 GavinMagnus joined #git
13:44 sdothum joined #git
13:44 anonymuse joined #git
13:50 seishun joined #git
13:52 manuel joined #git
13:53 Rodya_ joined #git
13:56 texinwien_ joined #git
13:56 mindriot101 joined #git
13:58 Gsham joined #git
14:01 ]-snake-[ joined #git
14:02 Rodya_ joined #git
14:02 SaberArthur joined #git
14:02 SaberArthur hello
14:02 gitinfo SaberArthur: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.
14:03 pks joined #git
14:04 synthroid joined #git
14:05 Rodya_ joined #git
14:06 rominronin joined #git
14:11 ShekharReddy joined #git
14:13 youser joined #git
14:15 xrfang joined #git
14:15 xrfang hello, how can I make the current DETACHED head my master?
14:25 snowkidind joined #git
14:26 youser joined #git
14:27 breezy_ joined #git
14:28 SaberArthur joined #git
14:29 nwkj86 joined #git
14:30 sdothum joined #git
14:31 mizu_no_oto joined #git
14:32 KevinDF joined #git
14:33 Tanfrieze joined #git
14:34 mayank98 joined #git
14:35 rominronin joined #git
14:36 Rodya_ joined #git
14:37 mayank joined #git
14:38 linuxmodder joined #git
14:39 nwkj86 joined #git
14:39 lucasem joined #git
14:39 shashin joined #git
14:39 King_Hual joined #git
14:40 bket joined #git
14:40 ment0s joined #git
14:42 nd joined #git
14:46 Vangelis joined #git
14:47 bn0t_ joined #git
14:48 KevinDF joined #git
14:53 User458764 joined #git
14:53 aw1 joined #git
15:01 isysd joined #git
15:03 ResidentBiscuit joined #git
15:12 Limes_ joined #git
15:13 akr_ joined #git
15:16 m0viefreak joined #git
15:17 vrlx joined #git
15:17 akr_ help! how to use git with gnupg 2.1?
15:17 Orbitrix joined #git
15:19 akr_ i'm using gpg 2.1 to sign git commits, but error: gpg failed to sign the data
15:21 davimore__ joined #git
15:24 moritz akr_: !repro please
15:24 gitinfo akr_: [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://git.io/viMGr ) of your terminal session so we can see exactly what you see
15:27 Naan joined #git
15:28 zacts joined #git
15:37 akr_ moritz: thx https://gist.github.com/anonymous​/eb9681b6b34363db5cac82ac6ac7601d
15:37 akr_ moritz: gpg (GnuPG) 2.1.16
15:39 nidr0x joined #git
15:39 elsevero joined #git
15:43 buffal0 joined #git
15:46 bernardio joined #git
15:47 canton7 akr_, that gist doesn't show you actually reproducing the issue
15:47 kadoban joined #git
15:47 canton7 ah, no it does, ignore me
15:48 canton7 akr_, 'which gpg2' ?
15:49 buffffal00 joined #git
15:49 akr_ canton7: /opt/local/bin/gpg2
15:50 canton7 akr_, https://medium.com/jubianchi-f​r/mac-osx-and-gpg2-d5f719fc596#.n1tg9zh8p implies you should set gpg.program to gpg1, not gpg2
15:51 Schrostfutz joined #git
15:51 SourTrout joined #git
15:53 grawity akr_: first, are you able to *directly* sign stuff with the same gpg2
15:54 LucaTM joined #git
15:55 msonntag joined #git
15:56 chachasmooth joined #git
15:57 akr_ grawity: yes, still can sign (gpg2 --sign file)
15:58 akr_ canton7: yep, but gpg 2.1 use a new format for key files, and it says it is very hard to go back :(
15:58 canton7 akr_, so the issue is that your git version doesn't support gpg 2?
15:58 msonntag_ joined #git
15:59 aafsi joined #git
15:59 akr_ canton7: seem so, have the devs known this issue?
16:00 canton7 I haven't been following the mailing list recently - take a look
16:00 canton7 !list
16:00 gitinfo [!mailing_list] The mailing list can be reached via git@vger.kernel.org. You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist
16:01 pypi_ joined #git
16:01 grawity the new format is not for key files; it's for keyrings
16:01 grawity if you want to go back, you just export them
16:03 complain_ left #git
16:04 moritz does git commit -S try to sign with the email address that's used for the commit?
16:04 stuh84 joined #git
16:06 canton7 "GPG-sign commits. The keyid argument is optional and defaults to the committer identity"
16:06 canton7 (from the man page)
16:06 davimore joined #git
16:06 canton7 so yeah, it'll default to finding a key from your committer identity (user.name and user.email)
16:07 Qxuz joined #git
16:07 akr_ grawity: ok, let me see
16:07 dendazen joined #git
16:09 f4 joined #git
16:09 moritz akr_: have you checked if your secrect key matches the name and email addresses known to git?
16:10 lindenle joined #git
16:10 akr_ moritz: both matches
16:11 ojdo joined #git
16:13 GavinMagnus left #git
16:13 grawity not that gpg cares about it
16:13 bobby___ joined #git
16:13 Shentino joined #git
16:14 ShapeShifter499 joined #git
16:14 grawity akr_: gpg.program = gpg --debug 255
16:14 grawity gpg2*
16:16 TomyWork joined #git
16:17 cyan__ joined #git
16:17 PresidentBiscuit joined #git
16:17 jimi_ joined #git
16:18 aw1 joined #git
16:19 mizu_no_oto joined #git
16:19 sla3k_ joined #git
16:20 akr_ grawity: the --debug option has no effect, the same output
16:20 robattila256 joined #git
16:20 moritz can you confirm with strace that it actually executes the right gpg executable?
16:21 moritz also, GIT_TRACE=1
16:22 seishun joined #git
16:22 sla3k_ left #git
16:23 Endarked joined #git
16:24 mindriot101 joined #git
16:26 Gsham joined #git
16:28 akr_ moritz: https://gist.github.com/anonymous​/e2188f6e6ad533f05e18d4f230289566
16:28 akr_ no strace on osx
16:28 nicksloan joined #git
16:29 ^7heo nope but there's dtrace
16:31 moritz the command looks correct to me
16:33 ReptilianBrain joined #git
16:37 iliv joined #git
16:37 ixian joined #git
16:40 Domhack joined #git
16:40 jaguarmagenta joined #git
16:40 Igu joined #git
16:43 YuGiOhJCJ joined #git
16:43 potatoes_ joined #git
16:44 Jellyg00se joined #git
16:45 frobnic_ joined #git
16:45 texinwien_ joined #git
16:46 sunri5e joined #git
16:48 Rodya_ joined #git
16:49 dviola joined #git
16:51 bn0t__ joined #git
16:52 Rodya_ joined #git
16:52 georgewhite joined #git
16:53 akr_ moritz: back to gpg1 but still can't git sign, i guess there are problems with my ~/.gnupg folder, investigating
16:59 Rodya_ joined #git
16:59 nettoweb joined #git
17:00 rominron_ joined #git
17:06 Ryanar joined #git
17:06 Oebele joined #git
17:06 snowkidind joined #git
17:08 Gsham joined #git
17:10 cdg joined #git
17:12 jottr joined #git
17:14 tnecniv joined #git
17:19 NeverDie joined #git
17:19 dreiss joined #git
17:22 manuel joined #git
17:24 buffal0 joined #git
17:24 agnoe joined #git
17:25 afuentes joined #git
17:27 cdown joined #git
17:27 madewokherd joined #git
17:30 jstein_ joined #git
17:31 jnavila joined #git
17:32 robattila256 joined #git
17:33 User458764 joined #git
17:34 User458764 joined #git
17:36 baed joined #git
17:41 nidr0x joined #git
17:41 romerocesar joined #git
17:41 cdown_ joined #git
17:44 cdown_ joined #git
17:45 PsionTheory joined #git
17:45 Rodya_ joined #git
17:45 vrlx joined #git
17:47 sunri5e_ joined #git
17:49 bn0t_ joined #git
17:52 anonymuse joined #git
17:54 nidr0x joined #git
17:55 seishun joined #git
17:55 chachasmooth joined #git
17:55 xall joined #git
17:58 anonymuse joined #git
17:59 elsevero joined #git
17:59 kaldoran joined #git
18:00 mrnuke joined #git
18:02 FilipNortic joined #git
18:02 akr_ moritz: i think i find out the problem, "name <mail>" is not a good format for "gpg2 -u"
18:04 akr_ moritz: "name" or "email" separately works, "name <email>" doesn't
18:07 SteffanW joined #git
18:13 Domhack_ joined #git
18:13 jaguarmagenta joined #git
18:15 chachasmooth joined #git
18:16 Goplat joined #git
18:17 SourTrout joined #git
18:17 Learath2 joined #git
18:20 hahuang65 joined #git
18:21 ramsub07 joined #git
18:22 eeeprom joined #git
18:23 cagedwisdom joined #git
18:24 Rodya_ joined #git
18:24 Cassiopaya joined #git
18:27 IlNominePatre joined #git
18:28 akr_ moritz: ah, my gpg key has comments, so "name <email>" does not match "name (comment) <email>", so i just need to update my key
18:28 hp joined #git
18:31 peepsalot joined #git
18:33 ouyx joined #git
18:35 buffal0 joined #git
18:35 mayank98 joined #git
18:36 akr_ moritz: ah, finally "git config --global user.signingKey KEYID", but it failed for not going through pinentry and unlock the key with passphrase
18:38 JanC joined #git
18:39 dreamfighter joined #git
18:43 mayank98 joined #git
18:44 akr_ moritz: export GPG_TTY=$(tty)  # done: https://superuser.com/questions/691395/gi​t-tag-with-gpg-agent-and-pinentry-curses
18:45 babilen joined #git
18:49 mario_ joined #git
18:49 BenderRodriguez joined #git
18:50 akr_ left #git
18:50 mayank98 joined #git
18:51 JanC joined #git
18:52 mizu_no_oto joined #git
18:52 mayank98 joined #git
18:52 mayank98 left #git
18:54 DrRobotic joined #git
18:54 wrouesnel joined #git
18:55 mayank98 joined #git
18:57 User458764 joined #git
18:58 cdown joined #git
19:00 tnecniv joined #git
19:04 mayank98 joined #git
19:04 romerocesar joined #git
19:04 jaguarmagenta joined #git
19:04 mayank98 hi
19:04 gitinfo mayank98: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.
19:05 mayank98 hello there!
19:08 breezy_ joined #git
19:08 robotroll joined #git
19:08 f4 joined #git
19:09 bn0t__ joined #git
19:11 GitNewbieSi joined #git
19:12 apitheia joined #git
19:13 fbwnnd joined #git
19:13 chachasmooth joined #git
19:13 apitheia I'm trying to merge some commits way back in history and even tho my history is flat with only --no-ff merges, I get a lot of conflicts when trying to rebase --onto the new merge.  Any suggests on merging history or rebasing onto it?
19:13 sunri5e joined #git
19:15 mayank98 joined #git
19:15 Cabanossi joined #git
19:15 ebnou joined #git
19:17 mayank98 hi all, i'm new to open source and wanted to know how to start contributing
19:17 geoid joined #git
19:18 preaction pick a project, read its documentation, and make sure the documentation is clear and readable. report bugs if it is not
19:20 davimore joined #git
19:20 mayank98 i tried reading the documentation of git but it was huge and i didn't know what to read
19:20 acetakwas joined #git
19:21 bremner step 0 to contributing to git, learn how to use git. perhaps with !book
19:21 gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable
19:22 aollier joined #git
19:22 preaction if you're new to open source, git might not be the project you want to contribute to. try a project you already use
19:22 mayank98 oh! thanks
19:22 Shakeel_ joined #git
19:22 PCatinean joined #git
19:23 mayank98 how to find that kind of project
19:23 seishun is there a shorter version of "git push --set-upstream seishun fix-short-circuit"? specifying the remote branch name feels redundant when I just want it to be the same as the local branch
19:23 mayank98 actually i want to participate in Google Summer of Code 2017
19:24 preaction so apply for Google Summer of Code 2017
19:26 Perturbed joined #git
19:26 rominronin joined #git
19:26 buffffal00 joined #git
19:27 _coll joined #git
19:28 preaction mayank98: so say what you said to me in here so that everyone can see...
19:29 prg3 joined #git
19:30 chachasmooth joined #git
19:30 mayank98 for an application to be selected one needs to do a microproject in git
19:30 cyan__ joined #git
19:31 maroni joined #git
19:31 preaction so you need to demonstrate that you can use git. do they have recommendations of microprojects? or, go back to what i said: send in some documentation fixes
19:31 SourTrout joined #git
19:31 [0xAA] joined #git
19:32 mayank98 they have given a list of ideas but i don't know which idea  to select
19:32 mayank98 yeah they have given some recommendations
19:33 preaction so just pick one that seems possible or interesting...
19:33 preaction otherwise, build a random number generator and use that to pick one
19:33 rewt do they mean "work on git itself" or "demonstrate your understanding of how to use git"
19:34 preaction is there some GSoC IRC channel or forum you can ask these questions?
19:34 preaction rewt: i assume the latter so that mentors don't need to handle that, which can take time away from the real project
19:34 Atm0spher1c joined #git
19:34 mayank98 the latter
19:35 grawity joined #git
19:36 rewt that's what i figured, so you could contribute to any software that you already use that has a git repo
19:36 mayank98 for an example they have given an idea like "Allow “-“ as a short-hand for “@{-1}” in more places."
19:36 preaction uh... that's a git thing. that's working on git itself
19:36 preaction also, that's not a good idea
19:36 rewt you don't have to contribute to git itself in order to /use/ git
19:37 mayank98 like this they have given many ideas
19:38 mayank98 i just wanted to know which part of documentation to read for implementing or knowing ablut a particular thing
19:38 mayank98 *about
19:38 shpew12 joined #git
19:39 preaction you have to read the code, not the docs. the docs are for using git, not for changing git. and i really don't recommend git as a first foray into open-source. there are plenty of other projects that need a lot more help
19:39 rewt that's the first step in the process... that "in more places" implies it's already there somewhere (have to find it), and not there in others (have to find those)
19:40 mayank98 ok
19:40 shpew12 if you clone a repository as bare are you able to get the status of your bare directory in relation to the repository you cloned it from?
19:40 preaction and who submitted the one you picked out? because that's about to break a few unix conventions
19:41 mayank98 idk
19:41 mayank98 many ideas like these on "https://git.github.io/SoC-2016-Microprojects/"
19:42 preaction ... so all the documentation you need is listed here...
19:43 mayank98 u mean the "documentation" folder in "https://github.com/git/git"?
19:43 dzho joined #git
19:43 preaction "To complete a microproject, you will have to go through approximately the following steps:"
19:44 de-vri-es joined #git
19:44 P4nther joined #git
19:45 glebihan joined #git
19:47 dzho joined #git
19:47 venmx joined #git
19:48 mayank98 i have read the things like "submittingPatches" and codingGuidelines
19:49 grawity joined #git
19:49 mayank98 "make the actual change" is the part where i'm stuck
19:50 mayank98 i'm having difficulty in knowing which part of the code to change to implement a particular change
19:52 manuel joined #git
19:52 einnjo joined #git
19:55 einnjo joined #git
19:56 preaction mayank98: that's the whole thing about being a software developer. look for the code related to the thing you want to work on, and then look for the code related to the code related to the thing you want to work on. if you have questions, you can try asking here, or you can ask the mailing list
19:57 cagedwisdom joined #git
19:57 mayank98 ok
19:58 mayank98 thanks a lot! i'll give it a shot!
19:58 Rodya_ joined #git
19:58 hahuang65 joined #git
19:59 sword joined #git
20:02 ram16 joined #git
20:02 venmx joined #git
20:03 mayank98 left #git
20:04 re1_ joined #git
20:04 mayank98 joined #git
20:04 mayank98 left #git
20:05 Learath2 joined #git
20:05 sssilver joined #git
20:05 mayank98 joined #git
20:06 ram16 Hello everyone !
20:06 mayank98 left #git
20:06 ram16 I have a question .. :), can anybody help ?
20:06 YuGiOhJCJ joined #git
20:07 preaction !ask
20:07 gitinfo Yes, it's okay to ask questions here.... in fact, you just asked one! ;-) Pretty much any question is fine. We're not terribly picky, but we might be asleep. Please be patient and you should get an answer soon.
20:07 johnny56 joined #git
20:07 mayank98 joined #git
20:07 re1 joined #git
20:08 uwlo joined #git
20:08 bn0t_ joined #git
20:10 ram16 Cool ! :) , well i have an idea to start a local community in order to encourage an train developers to use git and contribute to open source projects.
20:11 jnavila joined #git
20:11 ram16 Do i need to ask for permission to do this ?
20:12 preaction no
20:13 otpx joined #git
20:13 apitheia I'm trying to merge some commits way back in history and even tho my history is flat with only --no-ff merges, I get a lot of conflicts when trying to rebase --onto the new merge.  Any suggests on merging history or rebasing onto it?
20:13 preaction ram16: at least, you don't need permission from git. the license basically says as much. also, the idea of "permission from git" is kind of weird, as "git" is owned by all the people who hold copyright on it, which is everyone who has written a line of code or docs that get shipped with the git distribution
20:15 Perturbed left #git
20:16 ram16 :)  I see, do you know if there is any community experience made in the world ?
20:17 jnavila joined #git
20:18 venmx joined #git
20:18 MrWoohoo joined #git
20:19 preaction ram16: there are lots of communities in the world. you might want to see if there are ones already in your area on sites like Meetup.com
20:21 cxreg joined #git
20:21 ixian joined #git
20:22 aidalgol joined #git
20:25 TomyWork joined #git
20:26 TomyWork joined #git
20:27 pothepanda joined #git
20:29 [cust] joined #git
20:29 SwiftMatt joined #git
20:29 maroni left #git
20:31 NONE joined #git
20:33 timmu joined #git
20:36 venmx joined #git
20:39 Darcidride joined #git
20:45 Darcidride joined #git
20:45 Gsham joined #git
20:48 rominronin joined #git
20:51 mizu_no_oto joined #git
20:52 steelsw0rd joined #git
20:54 nettoweb1 joined #git
20:54 fiete joined #git
20:54 e14 joined #git
20:56 shiriru joined #git
20:56 ramsub07 joined #git
20:57 cyan__ joined #git
20:58 spacelord_ joined #git
20:59 re1_ joined #git
20:59 fiete joined #git
20:59 kulelu88 joined #git
21:00 nidr0x joined #git
21:00 chachasmooth joined #git
21:03 ramsub08 joined #git
21:05 JanC_ joined #git
21:06 msonntag joined #git
21:11 chachasmooth joined #git
21:14 fiete joined #git
21:15 darkcar joined #git
21:16 mizu_no_oto joined #git
21:16 jmpp joined #git
21:18 mdw joined #git
21:19 Anthaas Can someone help me with my repo
21:19 Anthaas I had a repo on github that I was pushing to, but I deleted it.
21:19 Anthaas I now want to push the project back to it.
21:20 mda1 joined #git
21:21 Rodya_ joined #git
21:22 BlessJah Anthaas: create new repository (it's up to you to pick the same name), add new repo as remote (you don't need to if you pick the same name), and then simply push all branches
21:23 BlessJah you might need to fetch after adding new repo
21:23 meZee joined #git
21:23 Anthaas git remote -v shows the push and fetch addresses as correct.
21:23 Anthaas and I have just re-created the repo on GH
21:23 BlessJah the fetch and push all branches
21:23 Anthaas Im getting error: refs/heads/master does not point to a valid object
21:24 Anthaas refs/remotes/origin/master does not point to a valid object.
21:24 Anthaas and like 4 others
21:24 BlessJah what does git fetch --all say?
21:24 Anthaas http://pastebin.com/MM1h34Lg
21:25 Anthaas this one at least said fetching origin, hasn't said that previously
21:25 jast hmm. does 'git fsck' complain similarly?
21:25 mdw joined #git
21:26 Anthaas http://pastebin.com/CfssJsDC
21:26 geoid joined #git
21:27 steelsw0rd joined #git
21:27 mdw_ joined #git
21:27 BlessJah it's interesting it complains about loose object
21:27 jast okay, that has nothing to do with github. your local git data is corrupted
21:27 Anthaas I created it on Windows, and am now running Ubuntu - would this cause it?
21:28 jast it shouldn't, the format is platform-independent
21:28 Anthaas Im quite happy to remote all git things, and then start again
21:28 Anthaas I just wouldnt know how
21:28 jast as in losing your history?
21:28 Anthaas Yeah
21:28 Anthaas This is a learning thing
21:28 jast okay, that's very simple actually
21:28 jast in your repo, just rm -rf .git
21:28 BlessJah whoah hold your horses
21:28 jast that removes everything git knows about your project :)
21:28 jast it might be possible to fix this and keep your history, though
21:29 Anthaas Nah, honestly, the history up to this point isn't important.
21:29 jast depends on what kind of object got broken here
21:29 Anthaas Im going to remove and change all of what is in there.
21:29 Anthaas OK, I ran rm -rf .git
21:29 Anthaas (I know its not a smart idea to remove all history, however as I said, it really doesn't matter for this project)
21:30 BlessJah git init; git add -A;git commit -m init; git add remote origin git@github.com/A/B.git; git fetch --all
21:30 BlessJah the regular stuff
21:30 buffal0 joined #git
21:32 Anthaas isnt it git remote add origin https://github.com/ME/PROJECT.git ?
21:32 Anthaas or does the order of add and remote not matter?
21:32 BlessJah oh, it matters
21:33 Anthaas my way or yours?
21:33 BlessJah yours
21:33 Anja joined #git
21:33 BlessJah my would try to add remote and origin files to staging
21:33 ram16 left #git
21:33 Anthaas Ok done all those commands
21:33 Anthaas now git push?
21:33 Anthaas ls
21:33 Anthaas oops
21:33 BlessJah after fetch and commit, yep
21:34 BlessJah it will complaing about upstream branches
21:34 Anthaas yep
21:34 BlessJah and print the correct command
21:34 Anthaas Ahhh done
21:34 Anthaas Thanks!
21:35 alburaq joined #git
21:35 alburaq left #git
21:38 SourTrout joined #git
21:40 SourTrout joined #git
21:42 sssilver joined #git
21:42 buffal0 joined #git
21:44 Learath2 joined #git
21:46 manuel joined #git
21:46 GavinMagnus joined #git
21:50 darkcar joined #git
21:52 ramsub07 joined #git
21:53 apitheia Is there a way to do $ git rebase --strategy=recursive -X theirs --onto master some-start branch?  It keeps saying fatal: Unknown option for merge-recursive: -X'theirs'
21:53 buffal0 joined #git
21:53 Cathy joined #git
21:54 Gsham joined #git
22:03 mukeil joined #git
22:07 bmahe joined #git
22:09 yohnnyjoe joined #git
22:13 lindenle joined #git
22:18 mda joined #git
22:24 matsaman joined #git
22:25 mellernoia joined #git
22:26 mukeil joined #git
22:28 geoid joined #git
22:31 Rodya_ joined #git
22:31 ams__ joined #git
22:36 SourTrout joined #git
22:37 re1 joined #git
22:38 SourTrout joined #git
22:39 i7c joined #git
22:40 texinwien_ joined #git
22:42 cyan__ joined #git
22:46 netj joined #git
22:49 daurnimator joined #git
22:51 bn0t__ joined #git
22:52 quackgyver joined #git
22:52 venmx joined #git
22:52 chachasmooth joined #git
22:53 re1_ joined #git
22:54 aw1 joined #git
22:56 rdavila joined #git
22:58 rbern joined #git
22:58 GavinMagnus left #git
23:01 fmeerkoetter joined #git
23:03 n-st joined #git
23:05 fgygi joined #git
23:06 n-st joined #git
23:07 Vinnie_win_b joined #git
23:09 chachasmooth joined #git
23:10 re1 joined #git
23:13 tmsmith_ joined #git
23:14 alyptik joined #git
23:17 Vinnie_win joined #git
23:21 darkcar joined #git
23:21 fmcgeough joined #git
23:22 dan2k3k4 joined #git
23:24 bn0t_ joined #git
23:24 dan2k3k4 joined #git
23:25 askb joined #git
23:26 rorro joined #git
23:27 nowhereman joined #git
23:28 aidalgol joined #git
23:28 geoid joined #git
23:32 dreiss joined #git
23:33 bn0t__ joined #git
23:39 alyptik joined #git
23:39 dikiaap joined #git
23:40 alex1a joined #git
23:40 shiriru joined #git
23:40 prg3 joined #git
23:42 peepsalot joined #git
23:44 arescorpio joined #git
23:46 moei joined #git
23:48 nidr0x joined #git
23:51 zerorax joined #git
23:51 jnewt_ joined #git
23:52 zerorax when I try do go 'git commit -m "comment"' it says there are changes not staged for commit. then when i push nothing gets updated on the repo. how do i make these changed files part of the commit?
23:53 zerorax I'm a git noob, i just started yesterday
23:53 rewt git add <file>
23:53 kadoban zerorax: You should really read one of the books or something, but yes first you have to 'stage' changes with 'git add'
23:53 zerorax i have to re-add them every time i change them?
23:53 netj joined #git
23:53 kadoban Yes
23:53 zerorax ohhhh
23:53 zerorax ok thanks guys!
23:54 bn0t_ joined #git
23:54 rdavila zerorax: you can also use 'git commit -a -m "message"', that will commit all the modified files, you need to be careful to not commit files that you don't want to
23:55 rdavila if you're updating a single file I think that's useful
23:55 zerorax okay, thank you
23:55 vlt zerorax: If you know what you’re doing you can also either `git commit -a`, `git commit my_file` or `git commit dir_with_file`.
23:55 zerorax awesome
23:56 rdavila now I have one question :)
23:56 rdavila I'm wondering if is there a way to make 'git rev-parse' to lookup only on local refs, by default it searches for refs under refs/remotes too. What I want to know is if a commit exists only in the local refs and not in the remote refs

| Channels | #git index | Today | | Search | Google Search | Plain-Text | summary