IRCloggy #git 2017-03-30

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2017-03-30

morgan_Guest1856800:00
Guest18568 left00:00
steeze left00:00
de-facto left00:01
de-facto joined00:01
dvaske_ left00:01
chipotle left00:01
dvaske joined00:02
systemovich left00:02
zumba_addict left00:02
trulycool joined00:02
systemovich joined00:02
peterbec` joined00:03
dsdeiz_ joined00:04
dsdeiz left00:04
chipotle joined00:05
s2013 joined00:06
aw1 joined00:06
Derperperd left00:07
aw1 left00:07
bdonnahue joined00:07
aw1 joined00:07
cam27 joined00:07
Derperperd joined00:08
aw1 left00:08
chardan left00:08
lavalamp left00:08
aw1 joined00:08
amdi_ left00:08
aw1 left00:09
Cabanossi left00:09
aw1 joined00:09
a_thakur left00:10
Cabanossi joined00:10
aw1 left00:10
drodger left00:10
a_thakur joined00:10
cyphase left00:11
Rodya_ joined00:11
ispn left00:11
cyberz left00:13
jtoy left00:14
nd- left00:14
cyphase joined00:15
Rodya_ left00:15
Lyqyd left00:16
nd joined00:16
drodger joined00:16
cqi joined00:17
porsche944 joined00:17
planigan joined00:17
bulletmark left00:17
porsche944 left00:18
LeBlaaanc joined00:18
cyberz joined00:19
hashtagstrashtag left00:19
Rodya_ joined00:19
holodoc left00:21
holodoc joined00:22
Guest55 left00:22
cyphase left00:23
boombatower left00:24
mizu_no_oto joined00:24
luke_nukem left00:25
systemovich left00:25
luke_nukem joined00:26
peterbec` left00:26
systemovich joined00:26
cyphase joined00:28
ronin_work joined00:29
mizu_no_oto left00:30
wxg joined00:31
Chinggis6 left00:32
dreiss left00:33
jstimm joined00:34
planigan left00:35
Chinggis6 joined00:36
luke_nukem left00:36
orbyt_ left00:37
luke_nukem joined00:37
a_thakur left00:39
cyphase left00:39
sunrunner20 joined00:40
Sasazuka_ joined00:40
a_thakur joined00:40
planigan joined00:41
Sasazuka left00:42
brent__ left00:43
cyphase joined00:44
a_thakur left00:44
chitopunk left00:49
gugah joined00:50
svm_invictvs left00:51
planigan left00:51
cyphase left00:52
marianina8 joined00:54
wxg left00:55
steeze joined00:57
cyphase joined00:57
planigan joined00:58
theiostream joined00:59
marianina8 left00:59
ahrs left01:00
jimklo_ joined01:00
ahrs joined01:00
planigan left01:01
sunrunner20 left01:01
orbyt_ joined01:02
ronin_work left01:03
jimklo left01:03
dsdeiz joined01:04
zumba_addict joined01:04
jimklo_ left01:04
svm_invictvs joined01:04
molgrum joined01:05
molgrum left01:05
molgrum joined01:05
gopar left01:05
cyphase left01:05
dsdeiz_ left01:05
matoro left01:07
tvw left01:08
wxg joined01:09
zumba_addict left01:10
cyphase joined01:10
jtoy joined01:12
zumba_addict joined01:14
lavalamp joined01:14
zumba_addict on a shared repo where few devs are working, what will happen if someone pushes a tag that already exist?01:14
Oatmeal left01:15
kadoban zumba_addict: Should get rejected, especially if it's different. Not sure if you can -f or not, never tried.01:15
zumba_addict thanks01:16
TbobbyZ joined01:16
cyphase left01:18
afuentes left01:19
matoro joined01:19
duderono_ left01:19
rnsanchez left01:20
Kaisyu joined01:22
chipotle left01:22
TbobbyZ left01:22
peterbec` joined01:22
ThiefMaster left01:23
cyphase joined01:23
gugah left01:25
Wulf4 joined01:26
peterbec` left01:27
lmatteis left01:28
Wulf left01:29
Wulf4Wulf01:29
XenophonF left01:29
fstd_ joined01:30
trulycool left01:31
fstd left01:34
fstd_fstd01:34
BenderRodriguez left01:34
s2013 left01:41
sunri5e left01:42
nevodka joined01:43
gugah joined01:43
sunri5e joined01:44
pks left01:45
ilbot3 left01:45
navidr left01:46
pks joined01:46
Oatmeal joined01:46
dglambert left01:47
Guest55 joined01:47
a_thakur joined01:48
ilbot3 joined01:49
XenophonF joined01:49
dmarr joined01:50
Sasazuka_ left01:50
Sasazuka joined01:50
cam27 left01:51
dmarr I was in a branch and made several changes, then (dumbly) without committing I stashed. I checked out master and pulled, created a new branch and `stash pop`, thinking i would just add a single change i wanted to add to master until going back to my original branch. now my conflicts are in a branch off of master due to the stash pop, and im not sure how to reapply the stash pop to my original branch again01:51
rchavik joined01:52
a_thakur left01:53
Cabanossi left01:53
AlHafoudh left01:54
Cabanossi joined01:55
Nothing4You left01:55
jtoy left01:56
dmarr if i git stash again, that will try to stash the conflicted changes right?01:57
thebope left01:57
tmsmith joined01:58
steeze left01:58
dave0x6d joined01:58
d^sh left01:58
dsdeiz left01:58
Gustavo6046 left02:00
ronin_work joined02:00
AlHafoudh joined02:00
MacGyver joined02:01
roflin joined02:01
Nickeeh joined02:01
s2013 joined02:01
d^sh joined02:01
Sasazuka left02:02
peacememories left02:02
kbeflo joined02:04
dmarr phew, git is smart enough to know not to drop a stash if it doesn't apply cleanly02:04
cqi left02:05
tmg joined02:06
mikecmpbll left02:06
kadoban dmarr: Yep, thankfully. Glad you figured it out, was just going to suggest that.02:07
dsdeiz joined02:07
dsdeiz left02:07
dsdeiz joined02:07
Nothing4You joined02:08
Goplat joined02:08
dmarr crisis avoided :)02:09
i did have to move some files that would have been overwritten, and re-delete some stuff but things worked out02:10
dedondesta left02:11
nevodka left02:11
raspado left02:15
cyberz left02:17
Nilesh_ joined02:17
cyberz joined02:18
trulycool joined02:18
askb left02:18
roelmonnens joined02:19
peterbecich joined02:20
lagothri1 joined02:20
hexagoxel left02:21
jtoy joined02:21
roelmonnens left02:23
trulycool left02:23
durham left02:23
lagothrix left02:23
durham joined02:23
durham left02:24
peterbec` joined02:24
durham joined02:24
durham left02:25
hexagoxel joined02:26
raspado joined02:26
peterbec` left02:29
steeze joined02:31
SuperLag left02:32
Rodya_ left02:32
cyberz left02:33
sz0 left02:34
cyberz joined02:35
ronin_work left02:35
sunrunner20 joined02:36
a_thakur joined02:37
boombatower joined02:38
alexandre9099 left02:38
kbeflo left02:38
alexandre9099 joined02:39
HoierM left02:40
zerow|afk joined02:41
Emperor_Earth joined02:42
LeBlaaanc left02:43
a_thakur left02:43
CheckDavid left02:44
lb1c left02:44
wagle left02:44
lb1c joined02:44
wagle joined02:45
thebope joined02:45
zerow|afk left02:46
ljc joined02:49
s2013 left02:49
mischat joined02:50
thebope left02:50
Gsham left02:51
Cabanossi left02:53
sunrunner20 left02:54
Vortex35 joined02:54
Cabanossi joined02:54
mischat left02:55
gugah left02:56
andrew710 joined02:57
mazeinmaze joined02:57
sunrunner20 joined02:57
Vortex34 left02:58
hyperair left02:58
chachasmooth left02:58
hyperair joined02:58
ojdo left02:59
jstimm left02:59
chachasmooth joined03:00
ljc left03:01
Darren_ joined03:02
Anja_ left03:03
ShapeShifter499ShapeShifter50003:06
ojdo joined03:06
jimi_ joined03:06
aavrug joined03:06
Darren_ left03:07
Cabanossi left03:07
jtoy left03:07
gugah joined03:07
ShapeShifter500ShapeShifter49903:08
al-damiri left03:08
Cabanossi joined03:08
marianina8 joined03:10
hhee joined03:11
inflames joined03:11
chipotle joined03:13
snowkidind joined03:14
cyberz left03:14
mazeinmaze left03:14
mehola joined03:14
marianina8 left03:14
raspado left03:15
s2013 joined03:16
raspado joined03:16
ohcibi joined03:16
raspado left03:16
raspado joined03:17
hhee left03:17
LeBlaaanc joined03:19
cyberz joined03:20
raspado left03:21
cyberz left03:25
peterbec` joined03:25
robotroll joined03:26
tyreld left03:26
TbobbyZ joined03:26
cqi joined03:29
peterbec` left03:30
planigan joined03:31
cyberz joined03:31
ronin_work joined03:32
safe joined03:32
dreiss joined03:32
Darren_ joined03:32
Pseudocrat joined03:34
dirtyroshi left03:35
cyberz left03:35
allen23 joined03:36
cyberz joined03:36
TbobbyZ left03:36
allen23 left03:37
chipotle left03:37
thebope joined03:39
cyberz left03:42
Guest55 left03:43
fakenerd joined03:43
thebope left03:44
cyberz joined03:45
xall joined03:45
trulycool joined03:46
kusznir joined03:48
khfeng joined03:48
alexandre9099 left03:49
kusznir Hi all: I'm trying to make my first contribution to a project, but it appears to me that somehow git got out of sync and "lost" my contributions...03:49
Work flow: some time ago, I cloned the project's repo to my workstaton. Over the past few months, made some changes. Ran git status, and saw the changes I made. Ran git add <files> (as they were new files). Git status showed them in green now.03:50
Ran git commit -m "my message". It responded positively.03:50
Ran git push, and it failed as it should (I don't have permissions to direclty pus to project repo)03:51
chipotle joined03:51
mischat joined03:51
Cabanossi left03:51
alexandre9099 joined03:51
kusznir So I went online to github, forked it, then git add myrepo <url>03:52
Git commit myrepo origin/4.2.03:52
It reported successful, that it uploaded the files and such.03:52
kadoban "git add myrepo <url>" is hopefully missing a word. "git remote add ..." ?03:52
kusznir But then I go back to github, under my account/my fork, branch 4.2, and nothing is there, and github says my branch is identical to the upstream project.03:52
kadoban "Git commit myrepo origin/4.2" ... what?03:53
thiago what do you mean by this: kusznir> Git commit myrepo origin/4.2.03:53
that is not a Git command03:53
kusznir Sorry, typo. Here's the cut and paste: git push myrepo origin/4.203:53
Cabanossi joined03:54
thiago so you pushed origin's 4.2 to myrepo03:54
but since you said that push to origin failed, that command did not push your commit03:54
kusznir https://pastebin.com/YeAqkVuf <- cut and paste from my terminal of the steps taken.03:55
peterbecich left03:56
thiago you need to push 4.2, not origin/4.203:56
kadoban Ya, that ^03:56
kusznir git status showed origin/4.2, and until I added origin/4.2, I got errors.03:56
leeN joined03:56
mischat left03:56
kusznir thiago: that's what I thought, but when I try, I get this: error: src refspec 4.2 matches more than one.03:56
When I specified origin/4.2, then it actually uploaded my files (at least, it reported uploading the same number of files I expected it to)03:57
kadoban 4.2 is a bit of a weird branch name. You maybe have a tag of that name as well?03:57
Noodlewitt left03:57
kusznir No idea...all this started with a clone of fusionpbx branch 4.203:57
kadoban origin/4.2 is the 4.2 branch *from origin*, it's not the local one you've been doing stuff in.03:58
kusznir git status currently shows this: Your branch is ahead of 'origin/4.2' by 1 commit.03:58
mizu_no_oto joined03:58
justan0theruser joined03:58
kadoban kusznir: Try uhm ... 'git push myrepo refs/heads/4.2:4.2'03:59
kusznir git push myrepo refs/heads/4.2:4.203:59
error: dst refspec 4.2 matches more than one.03:59
justanotheruser left03:59
thiago refs/heads/4.2 after the colon too03:59
kadoban Oh the destination is ambiguous, interesting. Ya that ^04:00
thiago you probably do have a tag called "4.2" too04:00
gugah left04:00
kadoban 4.2 is really just a bad branch name, that's why this is tedious. It's not a great idea to have a branch with the same name as a tag usually. Though ya, it sounds like that wasn't your choice.04:00
prions left04:00
kusznir ! [rejected] 4.2 -> 4.2 (fetch first) error: failed to push some refs to 'git@github.com:kusznir/fusionpbx.git'04:00
kadoban Sounds like you have different history compared to origin/4.2 then04:01
kusznir There is no other users pushing to my branch. There are no changes on my branch other than the changes I want to commit/push.04:01
My github account says my 4.2 is identical to upstream 4.2 (origin, in this case)04:01
kadoban Do you just want to nuke what's already on myrepo's 4.2 branch and make it equal to your current one? That changes published history, but it sounds like you're just setting this thing up, so usually you don't care.04:02
peeps[lappy] joined04:02
thiago 4.2 is a good branch name04:03
it's a bad tag name, though04:03
kusznir Not sure I fully understand...I do NOT want to change the files on my local box (its actually running in production; I was uploading my changes made from my production environment)04:03
thiago kusznir: push -f04:03
kusznir I don't care about killing any references this has to myrepo, or destroying the fork on github or anything that doesn't change the actual project files on my system's disk.04:03
thiago: that appears to have taken (same response I got the first time I was successful); checking online now.04:04
Ok, now it is showing online too!04:04
kadoban Huzzah04:05
orbyt_ left04:06
ronin_work left04:06
Blkt left04:07
roelmonnens joined04:07
s2013 left04:07
ryxxed left04:08
safe left04:08
Blkt joined04:08
alexandre9099 left04:09
de-facto left04:10
GodGinrai left04:10
BenderRodriguez joined04:11
roelmonnens left04:11
alexandre9099 joined04:11
de-facto joined04:11
fakenerd left04:12
freimatz joined04:12
steeze left04:13
ryxxed joined04:14
MutantMahesh joined04:14
bocaneri joined04:15
bocaneri left04:15
bocaneri joined04:18
forrestv joined04:18
maroloccio left04:18
steeze joined04:20
ShapeShifter499 left04:20
cyphase left04:20
MutantMahesh left04:21
alexandre9099_ joined04:22
trulycool left04:22
snowkidind left04:23
safe joined04:23
peterbec` joined04:24
alexandre9099 left04:24
alexandre9099_alexandre909904:24
mizu_no_oto left04:25
Noodlewitt joined04:25
robotroll left04:27
Chinggis6 left04:27
bocaneri left04:28
bocaneri joined04:28
bocaneri left04:28
Chinggis6 joined04:29
a_thakur joined04:30
zerow|afk joined04:31
jnewt joined04:32
nevodka joined04:32
thebope joined04:33
a_thakur left04:34
a_thakur joined04:34
Chinggis6 left04:34
kbeflo joined04:34
alexandre9099 left04:35
freimatz left04:36
alexandre9099 joined04:37
qmr joined04:37
thebope left04:38
Cabanossi left04:38
notebox joined04:38
dustinm joined04:38
Cabanossi joined04:38
notebox left04:39
TbobbyZ joined04:39
Timvde| joined04:43
bocaneri joined04:43
cyphase joined04:43
TbobbyZ left04:45
wxg left04:45
cyberz left04:46
ayogi joined04:47
cyberz joined04:48
trulycool joined04:49
steeze left04:51
jimi_ left04:52
cyphase left04:52
jimi_ joined04:52
mischat joined04:52
jimi_ left04:53
jimi_ joined04:53
jimi_ left04:53
janat08 joined04:54
jimi_ joined04:54
jimi_ left04:54
jimi_ joined04:55
fakenerd joined04:55
jimi_ left04:55
aidalgol left04:56
cyphase joined04:57
mischat left04:57
oleo left05:01
trulycool left05:01
rscata joined05:01
SteffanW joined05:02
pwnz0r joined05:03
cyberz left05:03
cyberz joined05:03
MutantMahesh joined05:04
safe left05:04
Endarked joined05:05
SteffanW left05:07
lavalamp left05:08
BlueMatt left05:08
cyberz left05:09
dsdeiz left05:09
dec0n joined05:09
BlueMatt joined05:09
cyphase left05:10
dsdeiz joined05:10
cyberz joined05:10
dsdeiz left05:10
dsdeiz joined05:10
GT4066 left05:12
UTAN_dev_ joined05:12
Darren_ left05:12
salios left05:12
LeBlaaanc left05:13
sbulage joined05:13
skered left05:14
hfp_work left05:14
hfp left05:14
robnester left05:14
UTAN_dev left05:15
cyphase joined05:15
[sarri] joined05:15
bambams_ joined05:15
cydrobolt_ joined05:15
sarri left05:15
cydrobolt left05:15
TheOrangeOne left05:15
umbSublime left05:15
jerrcs joined05:16
umbSublime joined05:16
umbSublime left05:16
umbSublime joined05:16
salios joined05:16
TheOrangeOne joined05:16
__builtin joined05:16
hfp_work joined05:16
zerow|afk left05:17
cyberz left05:17
zerow joined05:17
pwnz0r left05:18
robnester joined05:20
Noodlewitt left05:20
cyberz joined05:20
bdonnahue left05:20
hfp joined05:21
g0d355__ left05:21
salios left05:21
darkbit left05:22
jameser joined05:23
inflames left05:24
XenophonF left05:24
inflames joined05:25
marianina8 joined05:26
XenophonF joined05:26
thebope joined05:27
kristofferR left05:28
cyphase left05:29
ashnur left05:29
marianina8 left05:31
BlueMatt left05:33
MuffinMedic left05:33
darkbit joined05:33
cyphase joined05:33
ashnur joined05:33
ashnur left05:33
ashnur joined05:33
yan joined05:33
thebope left05:33
forgot left05:33
qt-x joined05:34
inflames left05:34
inflames joined05:35
AlgorithmWizard joined05:35
pelegreno_ joined05:35
salios joined05:35
forgot joined05:35
cyphase left05:36
bodie_ joined05:36
cyphase joined05:37
BlueMatt joined05:37
MuffinMedic joined05:39
cyberz left05:40
jameser left05:41
regedit joined05:43
cyberz joined05:43
brent__ joined05:44
watom- joined05:45
fakenerd left05:45
fakenerd joined05:46
TikityTik left05:46
chardan joined05:47
nckpz left05:47
Aaron1011 left05:48
brent__ left05:49
Aaron1011 joined05:49
Aaron1011 left05:49
Aaron1011 joined05:49
cyberz left05:51
Cabanossi left05:52
cyberz joined05:53
mischat joined05:53
Cabanossi joined05:54
roelmonnens joined05:55
Andrew_K joined05:55
ThiefMaster joined05:56
diogenese left05:56
mischat left05:58
cyphase left05:58
cyberz left05:58
qt-x left05:59
roelmonnens left05:59
cyberz joined05:59
Raging_Hog joined05:59
peterbec` left06:00
diogenese joined06:01
Assault joined06:02
zefferno joined06:02
cyphase joined06:02
cyberz left06:03
ronin_work joined06:03
Shahzad left06:04
elementalest joined06:05
cyberz joined06:06
chardan left06:09
peterbec` joined06:09
wxg joined06:10
cyphase left06:10
lb1c left06:13
visual morning fellas06:14
darkbit left06:15
cyphase joined06:15
roelmonnens joined06:17
roelmonnens left06:18
masuberu joined06:18
roelmonnens joined06:18
cyphase left06:20
thebope joined06:21
Sleepy63 left06:22
TomyLobo2 left06:24
darkbit joined06:25
cyphase joined06:25
lb1c joined06:25
thebope left06:26
pietv joined06:26
dvaske left06:26
User4587_ joined06:28
fbwnd joined06:29
drodger left06:29
hagabaka left06:29
dysfigured i want to put my weechat config in my dotfiles repo, buut i don't want to track my server listing in vcs.. so i'm wondering, is there a way to make sure i never commit a chunk of a file? or, is there a way i can automate staging up to a certain point in a file? for instance, i could sed '/^\[servers/q' and get the relevant portion i'd want to commit, but idk how to stage a file by stdin like that..06:29
Pseudocrat left06:29
drodger joined06:30
trulycool joined06:30
drodger left06:30
User458764 left06:31
osse dysfigured: man gitattributes, look at clean and smudge filters06:31
gitinfo dysfigured: the gitattributes manpage is available at http://jk.gs/gitattributes.html06:31
dysfigured hm cheers06:31
Silmarilion joined06:31
hagabaka joined06:32
cyphase left06:33
t0by joined06:35
drodger joined06:36
dreiss left06:36
inflames left06:37
buzzLightBeer joined06:37
seitensei joined06:38
cyphase joined06:38
ronin_work left06:38
cyberz left06:38
cyberz joined06:41
rokups joined06:43
nckpz joined06:43
roentgen left06:44
bambams_bambams06:44
TbobbyZ joined06:45
luke_nukem left06:46
menip left06:46
roelmonn_ joined06:47
dysfigured so, i woudl add something like irc.conf filter=strip_server to .gitattributes? and then use clean = sed.. but where do i put the [filter..] block? in the .gitattributes file as well?06:48
luke_nukem joined06:48
thiago left06:49
TbobbyZ left06:49
cyphase left06:49
wxg4irc joined06:51
roelmonnens left06:51
Cabanossi left06:51
imack joined06:53
osse dysfigured: .git/config06:53
wxg left06:54
Cabanossi joined06:54
smiiley joined06:54
mischat joined06:54
cyphase joined06:54
ogny joined06:55
dysfigured ahh. hmm but changes to that don't get saved to remote do they? so when i clone i have to re-create the filter?06:56
osse yes06:56
fbwnd left06:56
fbwnd joined06:56
dysfigured bummer. oh well, still better than manually reviewing commits to make sure i didn't accidentally add secrets06:57
Forlorn joined07:00
systemovich left07:00
dglambert joined07:01
mischat left07:02
jnavila joined07:02
buzzLightBeer left07:03
Raging_Hog left07:05
Raging_Hog joined07:05
Tobbi joined07:05
JeroenT joined07:05
borkr joined07:06
overlord_tm joined07:07
Raging_Hog left07:07
Raging_Hog joined07:07
dysfigured what..the.. so apparently clean = sed 's/^\[servers\]/q' creates invalid syntax in .git/config07:08
cyphase left07:09
osse dysfigured: but if the filter was in the repo then nothing would have been achieved07:10
peterbec` left07:10
leeN left07:11
cyberz left07:12
chardan joined07:12
catch22 joined07:13
wxg4irc left07:13
cyberz joined07:14
fbwnnd joined07:14
cyphase joined07:14
thebope joined07:16
trulycool left07:16
trulycool joined07:17
royiv left07:17
dersand joined07:17
nowhere_man left07:17
TomyWork joined07:17
lucasem left07:17
Guest54 joined07:18
royiv joined07:19
lb left07:19
lucasem joined07:20
thebope left07:20
skered joined07:21
t0by left07:21
PHPanos joined07:21
oskarkv left07:22
Silenced joined07:23
flaviodesousa joined07:24
cyphase left07:24
fbwnnd left07:24
thomas-oneill joined07:24
thomas-oneill hey I got a bunch of unstaged/untracked changes that I want to get rid of, except for one or two files. And for fun, let's say in those one or two files maybe I only want to use some of the changes, so like -p. What's your workflow for this? Vaguely re-call that git-stash might be the thing for this... Will read that man now actually...07:25
Silenced left07:26
Silenced joined07:26
janat08 left07:26
jn__ left07:26
nckpz left07:27
osse thomas-oneill: i would git checkout -p -- partialfiles to get rid of the changes you want. so now you have a couple of files you want to keep whole, and garbage07:27
thomas-oneill: then I'd stage those files you want to keep with git add. after that you can do 'git checkout -- .' on the whole lot07:28
Guest54 left07:28
roelmonn_ left07:29
cyphase joined07:29
osse git checkout -p lets you say yes ro no on a file-basis too, so if it's not *too* much you can use that all the way07:29
roelmonnens joined07:29
lb joined07:29
achadwick joined07:29
lbGuest3022507:29
Goplat left07:30
thomas-oneill oh yeah sweet07:30
elementalest left07:31
Endarked left07:32
Silenced left07:32
dsdeiz left07:33
Silenced joined07:33
Silenced left07:33
Silenced joined07:33
ronin_work joined07:35
gtristan left07:36
sea-gull joined07:36
memfrob joined07:37
boombatower left07:37
ertes joined07:38
Cabanossi left07:38
memfrob Hey everyone! I just wanted to thank this channel again for helping me out so much, I've been able to backport 125 kernel patches from 4.9 to 4.4 so far and I'm making great progress.07:38
I started over again recently as my development plan before was a mess, but after learning about git cherry-pick it's a heck of a lot easier.07:39
chele joined07:39
Cabanossi joined07:39
memfrob A few members said they were interested in what I was working on, the patch series (incomplete) is hosted here: https://github.com/NTULINUX/kernel-patches/tree/master/security_backports07:39
a full kernel repo will be available once it's tested and ensured that's working properly, thank you all again so much!07:40
Gloomy joined07:40
memfrob KASLR, hardened usercopy, tons of kernel hardening techniques developed in kernel 4.9 and 4.10 will be backported to 4.4 and I couldn't have done it without you #git07:41
drodger left07:41
cyberz left07:41
cyberz joined07:43
cyphase left07:45
Gloomy left07:45
royiv left07:46
drodger joined07:46
JeroenT left07:47
schleppel joined07:47
JeroenT joined07:47
chigang joined07:48
royiv joined07:48
King_Hual joined07:49
dvaske joined07:49
Silenced left07:49
masuberu left07:50
Silenced joined07:50
Silenced left07:50
Silenced joined07:50
cyphase joined07:50
memfrob left07:52
masuberu joined07:52
trulycool left07:53
grayjoc joined07:53
shinnya joined07:54
regedit left07:54
mikecmpbll joined07:56
manuelschneid3r joined07:57
Murii joined07:58
marcvangend joined07:59
kurkale6ka joined08:00
deanc joined08:01
ronin_work left08:01
deanc Hi. I want to interactively view the diffs of individual files that are currently not in staging (haven't been git added)08:01
ronin_work joined08:01
deanc git add -i doesn't seem to do what i would hope. it only allows me to view the diffs from things i have already git added08:01
zeroed joined08:02
zeroed left08:02
zeroed joined08:02
cqi left08:02
marcvangend Hi, we're getting a segmentation fault on Windows 10 when doing a git status. Where do I start debugging?08:02
elect_ joined08:03
jtoy joined08:04
tvw joined08:04
gtristan joined08:05
cyphase left08:06
osse deanc: i think you're misunderstanding08:07
peterbec` joined08:07
Silenced left08:08
deanc osse: yes i think i misunderstood what git add -i will do also. What workflow could I use to to see a diff on a whole file and either add it or ignore and then interactively move on to the next file?08:08
Right now I have to type git diff <path> and then git add <path> and then go back to git status from time to time when my buffer is full etc.08:08
jim_carry joined08:08
Cabanossi left08:08
jtoy left08:08
Silenced joined08:08
jim_carry Any one use vim-fugitive? What is Gblame? how to use it?08:09
Cabanossi joined08:09
Silenced left08:09
osse deanc: add -i will let you view the diffs of files that are modified. not sure what you mean08:09
jim_carry I understand it shows who changes last time line by line08:09
osse jim_carry: type :Gblame when editing a file. that's it.08:09
jim_carry what is reblame08:09
svm_invictvs left08:10
osse reblame = running git blame over again from that point in history08:10
thebope joined08:10
cyphase joined08:10
immae deanc: try "git add -p" ?08:10
jim_carry osse: That means who changes that line before the last user08:11
deanc osse: right now in git status i have about 10 files changed. some are staged, some are not. If I type in git add -i and then 6 i would expect it to let me see diffs of files that are not added to staging to decide whether to stage or not. It only shows a list of files that are staged08:11
octo8_ joined08:11
noctux`noctux08:11
deanc immae: git add -p is too granular. i am not interested in breaking down a diff on a file into smaller commits. All i want to do is see a diff on a file and say y/n and move on to the next until complete08:11
osse deanc: strange. it shows both here08:12
peterbec` left08:12
osse jim_carry: it means run git blame as if that was the newest version of the file08:12
deanc osse: on ad different repo where i have not run git add at all on the changed I've made - if i type git add -i and then type 6 to do the diff, there is nothing int he list. it just shows me a list of commands08:13
osse deanc: git add -p lets you select "stage this hunk and all later hunks in the file"08:13
zumba_addict left08:13
deanc osse: at least when i tried git add -p earlier it would show one hunk at a time so it would not be safe to stage later hunks as they are not on my screen08:13
osse deanc: these files you don't see, are they utnracked?08:14
zerow left08:14
thebope left08:14
mikecmpbll left08:14
cyphase left08:15
deanc no, they are tracked08:15
mar77i left08:17
osse add -i's diff subcommand shows diff between HEAD and index08:17
aka. what is set to be committed08:17
seems there is no equivalent for working tree and index08:17
deanc okay then it doesn't do what i would want08:18
i wonder if there is a third-party tool i could run to aid with this workflow08:18
i don't like the idea of adding everything and then using git add -i to undo things08:19
jim_carry left08:19
osse what is it that you want, exactly?08:19
answer yes or no to each file, and if yes the whole file is added?08:19
clmsy joined08:20
sarbs left08:21
sarbs joined08:22
osse deanc: git diff --name-only | while read -r file; do git diff -- "$file"; read -p "Add $file ?" </dev/tty; if [[ $REPLY = [Yy]* ]]; then git add "$file"; fi; done08:23
deanc what on earth.. :D08:24
let's see...08:24
very impressive :) mind if i add this to my personal git tips blog post?08:25
I mainly use it as a personal reference, nobody goes there08:25
madewokherd left08:26
kexmex joined08:26
marcogmonteiro joined08:26
deanc In fact, I'm not entirely sure how to make that into an alias08:27
osse deanc: please don't. write it to a file named 'git-foo' where foo is what you'd alias it to, and put it in $PATH08:32
deanc check08:32
crater2150 hi, since updating to 2.12 I get perl syntax errors on git add -i: https://paste.pound-python.org/show/EIruOT8FSHCgxHY1efuC/08:32
as other users of the same distro (voidlinux) can't reproduce it, could there maybe be some new dependency that I'm missing?08:33
osse that said, I think you can do git config alias.foo '!git diff --name-only | while read -r file; do git diff -- "$file"; read -p "Add $file ?" </dev/tty; if [[ $REPLY = [Yy]* ]]; then git add "$file"; fi; done && :'08:33
cqi joined08:33
osse but at some point you gotta admit that it's not longer an alias, it's a new subcommand08:33
ispn joined08:33
eahmedshendy joined08:33
mikecmpbll joined08:34
sveinse left08:36
notebox joined08:37
buzzLightBeer joined08:37
Timvde|Timvde08:38
sotoz joined08:39
netroxen joined08:41
bwn left08:41
Silenced joined08:43
sbasso joined08:46
matoro left08:48
TbobbyZ joined08:48
scoobertron left08:48
scoobertron joined08:48
jagob joined08:48
drodger left08:49
drodger joined08:51
royiv left08:51
molgrum left08:52
royiv joined08:52
TbobbyZ left08:52
Silenced left08:53
mischat joined08:53
molgrum joined08:53
molgrum left08:53
molgrum joined08:53
King_Hual left08:55
notebox left08:57
ThomasLocke joined08:57
sbasso left08:58
sbasso joined09:00
zefferno left09:00
matoro joined09:01
zeroed left09:01
dorian_ joined09:01
bwn joined09:02
gitinfo set mode: +v09:03
sbasso left09:03
deanc I see you point osse, but as it's git specific it's nice to have as an alias. big thank you :)09:04
osse deanc: git-rebase is git specific, and yet it's a script and not an alias :O09:05
at a point the aliases become so large and unwieldly that they're a pain to deal with09:05
molgrum left09:07
peterbec` joined09:08
exotime joined09:09
King_Hual joined09:10
King_Hual left09:10
King_Hual joined09:10
molgrum joined09:10
molgrum left09:10
molgrum joined09:10
zefferno joined09:13
peterbec` left09:14
fees joined09:17
marcvangend left09:17
MineCoins joined09:17
Gloomy joined09:23
sbasso joined09:23
dyce[m] left09:24
am2on left09:24
Retropikzel[m] left09:24
elwan7[m] left09:24
unclechu left09:24
hiq[m] left09:24
monomon[m] left09:24
keks[m] left09:24
UncleCJ left09:24
dikiaap left09:24
patrickr[m] left09:24
aviraldg left09:24
KevinMGranger left09:24
musicmatze[m] left09:24
M-meznak left09:24
heftig left09:24
SpEcHiDe left09:24
saintaquinas[m] left09:24
Remramm left09:24
flo[m] left09:24
spinningarrow[m] left09:24
jascot[m] left09:24
logos[m] left09:24
Elliott[m]1 left09:24
Asenar joined09:25
theiostream left09:26
pietv left09:26
zefferno left09:28
D4R5C0D3 joined09:29
dsdeiz joined09:29
smiiley left09:29
aviraldg joined09:30
jagob left09:31
mischat_ joined09:32
jagob joined09:32
nevodka left09:33
ShapeShifter499 joined09:34
raynold left09:34
mischat left09:35
dsdeiz left09:35
marcvangend joined09:35
MineCoins left09:35
D4R5C0D3 left09:37
D4R5C0D3 joined09:39
Ice_Strike joined09:40
maroloccio joined09:40
zefferno joined09:40
zefferno left09:40
zefferno joined09:40
IRQ` joined09:43
luke_nukem left09:44
dglambert left09:45
btree joined09:47
Silenced joined09:48
andrew710 left09:50
sarbs left09:51
monomon[m] joined09:51
spinningarrow[m] joined09:51
flo[m] joined09:51
saintaquinas[m] joined09:51
elwan7[m] joined09:51
heftig joined09:51
am2on joined09:51
Elliott[m]1 joined09:51
dyce[m] joined09:51
dikiaap joined09:51
unclechu joined09:51
jascot[m] joined09:51
M-meznak joined09:51
KevinMGranger joined09:51
musicmatze[m] joined09:51
keks[m] joined09:51
logos[m] joined09:51
Remramm joined09:51
UncleCJ joined09:51
SpEcHiDe joined09:51
patrickr[m] joined09:51
hiq[m] joined09:51
Retropikzel[m] joined09:51
Jaiss joined09:53
th_ left09:53
sarbs joined09:55
feodaron left09:56
YuGiOhJCJ joined09:56
TomyWork left09:56
PHPanos left09:57
thebope joined09:58
dsdeiz joined09:59
feodaron joined09:59
Gotham25 joined10:00
masuberu left10:01
fletom left10:01
TbobbyZ joined10:01
brent__ joined10:01
Tobbi left10:02
b100s joined10:03
thebope left10:03
dsdeiz left10:03
Gotham25 Hi, I'm using eclipse git plugin. I have cloned a repo from bitbucket account. It was working fine since yesterday. Now there was a change done and committed in one branch yesterday. And today when I used the fetch from upstream option, it fetched the changes done in that branch. But in Git perspective under Remote Branch I'm not able to find it....10:04
Can anyone guide me in resolving this issue10:04
dorian_ Hey, I set "gvimdiff" as my diff tool in git. But git opens an instance of vim instead. And my configuration of vim (not gvim) make it very hard to read the diffs. Can I tell git to use gvim instead of vim ?10:04
jtoy joined10:04
Gotham25 The remote branch is still behind 2 commits.....10:05
But fet from upstream shows that the remote branch is up to date10:05
fetch*10:05
brent__ left10:05
TbobbyZ left10:06
sbasso left10:08
marcvangend left10:08
jtoy left10:09
marcvangend joined10:09
peterbec` joined10:10
sbasso joined10:10
[sarri] left10:10
zxd joined10:11
Browser left10:11
peeps[lappy] left10:11
zxd how to return from detached head back to having HEAD point to a branch10:11
kexmex left10:11
zxd ah10:12
checkout branch :)10:12
rokups there are two projects, Upstream and Fork. Fork was "forked" by copying source code and just making new repository, so they do not share any history. Fork has some stuff removed, some stuff moved, bunch of stuff added. Currently merges are done by comparing relevant folders and moving changes manually. Is there maybe a better way to merge from Upstream using10:12
git?10:12
sarri joined10:12
sarri left10:12
sarri joined10:12
osse dorian_: does git mergetool --tool=gvimdiff work ?10:13
troulouliou_div2 joined10:14
theoceaniscool joined10:14
kexmex joined10:14
ronskisika joined10:15
peterbec` left10:15
Raging_Hog left10:15
osse rokups: fetch the Upstream repo into the Fork repo. Next time you do a manual comparision, commit the result as a merge commit10:15
after that you can continue to merge10:15
rokups will try, thank you osse10:16
ferr1 joined10:18
D4R5C0D3 left10:19
dorian_ osse, I can't launch it because git keeps telling me that no file need merging. I'm not too sure how I can make a need for merge happen.10:19
sotoz left10:20
osse dorian_: heh, my bad. I mean git difftool --tool=gvimdiff10:20
dorian_ osse, Yes it works: git starts gvimdiff as requested.10:22
marcvangend left10:22
dorian_ I see in my configuration file that there "tool = gvimdiff" under the [diff] section.10:22
D4R5C0D3 joined10:22
dorian_ maybe it should be in the difftool section ?10:23
Well it did not work :/10:24
osse dorian_: git config --show-origin -l | grep diff.tool10:24
ToBeCloud joined10:25
gitinfo set mode: +v10:25
dorian_ osse, good thinking! My local git configuration was overriding my global configuration.10:25
It works fine now10:25
Silenced left10:25
peacememories joined10:25
osse my thinking is the best10:26
sotoz joined10:26
finalbeta joined10:26
osse dorian_: btw did that command show both values?10:26
dorian_ yes10:27
osse \o/10:27
peacememories left10:27
catch22 left10:28
andrew710 joined10:30
peacememories joined10:30
sbasso left10:32
Silenced joined10:32
kbeflo_ joined10:33
kbeflo_ left10:35
Olipro left10:35
timlyo[m] joined10:35
sbasso joined10:35
kbeflo left10:36
msonntag left10:36
Cabanossi left10:36
msonntag joined10:36
bongjovi joined10:37
Silenced left10:38
Cabanossi joined10:39
peacememories left10:41
Olipro joined10:41
quizzi joined10:42
fakenerd left10:43
Silenced joined10:43
CussBot left10:44
CussBot joined10:45
tmsmith left10:47
Gloomy left10:48
xall left10:50
mar77i joined10:50
pinkkis left10:50
thebope joined10:52
_August_ joined10:53
aw1 joined10:53
_August_ im trying to merge my branches and the branch I am trying to merge I keep getting an conflict error "Auto-merging javascript/common.js10:54
CONFLICT (content): Merge conflict in javascript/common.js10:54
Automatic merge failed; fix conflicts and then commit the result.10:54
" any suggestions?10:54
tobiasvl _August_: !eek10:54
gitinfo _August_: [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II10:54
zerow joined10:54
pbrewczynski joined10:56
thebope left10:57
onehrxn joined10:57
darkbit left10:58
sbasso left10:58
barduck joined10:59
Gloomy joined10:59
tlaxkit joined10:59
chipotle left11:00
_August_ left11:02
deanc left11:05
darkbit joined11:05
Atm0spher1c left11:05
sbasso joined11:07
pinkkis joined11:07
Tobbi joined11:08
borkr left11:08
peterbec` joined11:10
afuentes joined11:15
peterbec` left11:15
chardan left11:15
lugzer joined11:16
lugzer afternoon11:16
onehrxn left11:17
onehrxn joined11:18
lugzer i have a simple question i think - i made changes to source files of a submodule (which is in /node_modules) - and now i want to revert those changes. since /node_modules are ignored, i have to do it some other way.. what's the simplest?11:18
sbasso left11:18
sbasso joined11:18
masuberu joined11:18
mischat_ left11:19
chardan joined11:19
mischat joined11:20
b100s left11:21
marcoslater joined11:21
borkr joined11:23
chachasmooth left11:28
Tatou joined11:28
dsdeiz joined11:28
dsdeiz left11:28
dsdeiz joined11:28
alexandre9099 left11:29
ogny left11:30
ogny joined11:30
chachasmooth joined11:32
dsdeiz left11:32
sbasso left11:37
dtbn joined11:37
lugzer ok figured out.. it wasn't a submodule. it was npm package.. so a different channel first of all ;)11:37
rnsanchez joined11:38
dsdeiz joined11:38
nowhere_man joined11:38
flopsec left11:40
MrMojit0 joined11:41
octo8_ left11:41
lmat How do I point a remote branch to a commit?11:43
fakenerd joined11:43
lmat git push origin 6284e8:master; doesn't work11:43
or a tag... git push origin tag-name:master; gives odd output: " * [new tag] tag-name -> master" It looks like it created the tag anew on the remote? Not what I'm going for.11:44
osse lmat: git push origin 6284e8:master should work just fine. what doesn't work about it?11:45
Vampire0 lmat, !repro11:45
gitinfo lmat: [!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 see11:45
tymczenko joined11:45
lmat osse: hmm, now it says "non-fast forward"...researching11:46
osse: You know... I bet the problem was that that commit didn't exist on the server...11:46
chipotle joined11:46
lmat no, that should be okay11:46
it just just upload it11:46
thebope joined11:46
lmat it should just upload it11:46
osse lmat: if amster didn't already exist then you get an error11:46
otherwise it should work11:46
MutantMa_ joined11:47
sbasso joined11:47
lmat osse: okay, thanks11:47
osse: ... but why wouldn't it work if master didn't first exist?11:47
MutantMahesh left11:47
kristofferR joined11:47
osse lmat: because it doesn't know what you want master to be11:47
a tag? a branch? something else?11:48
lmat osse: dude, you're awesome.11:48
osse the solution is to write the full name: git push origin 6284e8:refs/heads/master11:48
lmat bows11:48
ionl joined11:48
ionl left11:48
lmat osse: I have asked this question several times and never received a good answer. I will sleep very well tonight11:48
Vampire0 lmat, and if you push a tagname, it "works" as it assumes that you want to push to a tag if you push a tag11:48
lmat, hence you created the tag master when you pushed with tag name11:49
lmat, and after that you did get the non-fast-forward warning, as now there is a thing called "master" it is just not a fast-forward11:49
lmat, hence the error did change after you pushed the tag to the newly created tag master11:49
HoierM joined11:50
lmat Vampire0: That sounds like great reasoning, but master *did* exist when I pushed the tag ^_^11:50
dtbn Hey boys & girls. Got a question - I have a pull request that require rebasing to master - how to do it in easiest way? `git checkout branch-name`, `git rebase master` and then?11:51
thebope left11:51
Vampire0 lmat, hm, then it is strange that it created a new tag called master instead of updating the branch. osse, did I remember wrongly?11:51
cqi left11:51
lmat Ah, I see thath it created a *local* "master" tag!11:51
_ikke_ dtbn: 2. fix possible conflicts. 3. ???, 4. profit11:51
grayjoc left11:52
osse Vampire0: afaik it uses the source to see what type the destination is11:52
dtbn there is not really a conflict, just rebase to follow master branch11:52
Vampire0 lmat, I don't think it created a local master tag on push. But if your push created a tag in remote and you then fetch the tags, you get the local one from the remote11:52
marianina8 joined11:52
marianina8 left11:52
_ikke_ dtbn: You possible have to force push te rebased branch11:52
marianina8 joined11:52
_ikke_ git push --force-with-lease origin branch-name11:53
lmat Vampire0: Ah, I should make sure it didn't create a master tag on remote :-o11:53
Vampire0 osse, even if it exists already? hm, must remembering wrongly then11:53
osse Vampire0: if it already exists then I don't think it would11:53
lmat dtbn: I don't think you can do non-fast forward pull requests.11:53
dtbn: yeah, force push like _ikke_ says.11:54
zulutango joined11:54
osse Vampire0: I don't think that's what happened here either.11:54
I think master didn't exist at the time he did tag-name:master11:54
bariscant joined11:55
lmat osse: local or remote?11:55
Vampire0 osse, lmat, yep, I just tried11:55
osse lmat: remote11:55
Vampire0 osse, lmat, if you push tag-name:master and master branch exists, the master branch is pushed to11:55
lmat osse: master existed as a branch for many months now.11:55
Vampire0: ... pushed to what?!11:56
Vampire0 osse, lmat, if you push tag-name:master and master branch does not exists, the master tag is pushed to (created if not exists)11:56
osse lmat: then 'git push origin 6284e8:master' would have worked in the first place.11:56
lmat osse: Yeah, but i did that tag thing first :-(11:56
flopsec joined11:56
selckin left11:57
osse that too sholud have worked, instead of getting "new tag"11:57
lmat okay, time to research: what does git push remote <tag-name>:<existing-remote-branch> do ^_^11:57
lugzer left11:57
lmat <tag-name> is an existing tag on remote.11:57
Vampire0 lmat, you said 6284e8:master did fail, then tag-name:master created a tag called master and then 6284e8:master said it is not a fast-forward11:57
osse it makes the remote branch point to the same commit as the local tag does11:57
Vampire0 lmat, this definitely means that there was no branch called master on the remote11:57
lugzer joined11:57
lmat Vampire0: Sorry, I said "git push origin 6284e8:master; doesn't work" I was working from faulty memory at that point.11:58
Vampire0: I hadn't done it :'(11:58
Vampire0 lmat, whether the tag-name exists on remote is not relevant, it is only relevant whether existing-remote-branch exists11:58
lmat Vampire0: makes sense.11:58
Vampire0 lmat, and if it exists, it gets updated11:58
lmat, I just tried it here to make sure not saying non-sense11:58
synthroid joined11:59
Vampire0 lmat, even if you didn't do 6284e8:master first, as tag-name:master created a tag called master, this is proof enough already that there is no remote branch called master11:59
WizJin joined12:00
lmat hmm12:00
mar77i left12:00
mar77i joined12:00
Urbany joined12:01
chardan left12:02
synthroi_ joined12:02
scoobert1on joined12:02
chardan joined12:03
theoceaniscool left12:03
Vampire0 lmat, and what I also just tried, if there is both a tag called master and a branch called master and you use an explicit refspec like 123abc:master or tag-name:master or even master:master, Git will complain that the dst refspec is ambiguous and will not work unless you explicitly state which of the two you want to update. `git push origin master` though works and updates the master branch12:04
TbobbyZ joined12:04
zulutango left12:04
synthroid left12:04
scoobertron left12:06
Andrew_K left12:07
Cabanossi left12:07
jimi_ joined12:07
dtbn I think believe it worked, thank you!12:07
ShapeShifter499 left12:08
Cabanossi joined12:09
TbobbyZ left12:09
gitinfo dtbn: This channel tracks karma based on who has gotten lots of thanks for being helpful. If you want to help someone reach karmic nirvana, please mention their name when thanking them with "thank you", "thankyou", "thanks", "thx", "ty" or "cheers". Try ".karma <nick>" or ".topkarma" to show karma status of a person.12:10
cousteau joined12:11
peterbec` joined12:11
cousteau is `git commit --ammend` equivalent to fixup?12:11
osse no12:11
unreal joined12:12
darkbit left12:12
Vampire0 osse not?12:12
cousteau er, amend12:13
Vampire0 osse, assuming cousteau meant amending the latest commit vs doing a fixup commit and using rebase to integrate it12:13
drodger left12:13
osse --amend modifies the existing commit. --fixup creates a *new commit* which is intended to be used with git rebase --autosquash12:13
ok, then I just interpretend the question to literally12:14
*too12:14
cousteau osse, sorry, I meant creating a new commit and then doing fixup with rebase12:14
osse Yes, they sort of serve the same purpose12:14
Vampire0 cousteau, then yes, it is the same12:14
cousteau I assume the responsibility12:14
osse, Vampire0, thanks!12:14
Vampire0 yw12:14
osse as in: --fixup is for when you want to --amend but you can't :p12:14
cousteau then I'll stop doing rebases; they're rather inconvenient12:14
(compared to --amend)12:15
Vampire0 cousteau, if it is not the latest commit you want to amend, you need to do it with fixup. If it is the latest, amending is the most convenient way to go, yes12:15
osse cousteau: you cannot use --amend to fix any commit except the current one12:15
mehola left12:15
peterbec` left12:15
cousteau right12:16
Jaiss left12:16
cousteau I mena, that's what I used rebase for12:16
*mean12:16
Vampire0 well, yeah, "current one" hits it better than "latest one"12:16
mehola joined12:16
cousteau another thing, what was the command to tell git to forget staged changes? git reset --soft?12:16
osse cousteau: so now you'll stop doing that and isntead get things right the first time? :p12:16
just 'git reset'12:17
Vampire0 cousteau, no, just "git reset"12:17
cousteau ah12:17
brent__ joined12:17
cousteau that doesn't touch the files, right?12:17
Vampire0 cousteau, soft reset will update the branch head, but leave the index and worktree untouched12:17
marscher joined12:17
cousteau ah wait, actually reverting files was checkout, not reset12:18
Vampire0 cousteau, a mixed reset (the default if not --soft, --hard or --mixed is given explicitly) will reset the index and probably repoint the branch pointer, but will not touch your worktree12:18
cousteau, checkout with path and without commit-ish will update your worktree files to match what is in the index12:19
cousteau I see, thanks!12:19
Vampire0 cousteau, a --hard reset will also update your worktree files to the given state12:19
snowalpa_ left12:19
scoobert1on left12:19
chachasmooth left12:19
drodger joined12:19
chachasmooth joined12:20
mehola left12:20
Eryn_1983_FL left12:22
brent__ left12:22
trulycool joined12:22
cousteau I see12:23
gugah joined12:23
marianina8 left12:24
scoobertron joined12:25
Cavallari joined12:25
marianina8 joined12:25
XenophonF left12:26
cousteau hm, commit --amend seems to create a fork. Ugly...12:26
(guess that's easy to remove though)12:26
osse And that, kids, is why you don't push immediately12:27
manuelschneid3r left12:27
lugzer left12:27
lugzer joined12:28
marianina8 left12:29
XenophonF joined12:30
jtoy joined12:30
itavero joined12:30
a_thakur left12:31
ToBeCloud left12:31
itavero left12:31
GodEater left12:31
aavrug left12:31
JeroenT_ joined12:31
cousteau osse, I'm not pushing anyway; I'm honestly just using git as a log of changes12:31
and just in case I want to undo something12:32
osse cousteau: then where do you see the fork?12:32
cousteau (I also have an external repository as a backup, but last time I pushed was 2 weeks ago)12:32
osse, gitk12:32
osse cousteau: and what are the tips of the work?12:32
fork12:32
cousteau the old commit that was amended12:33
osse I mean why is it visible in the first place?12:33
cousteau it's a one-node ramification12:33
osse does it not say "HEAD" or "master" or "feature" or "origin/master" next to it?12:33
Brski joined12:34
JeroenT left12:34
cousteau So I closed gitk and opened it again and the branches disappeared. Duh...12:35
osse, so never mind I guess; it was a glitch in the gitk12:35
JeroenT_ left12:35
Eryn_1983_FL joined12:35
JeroenT joined12:36
sbasso left12:36
cousteau had closed gitk and opened it again with the English locale in order to take a screenshot. One of the cases when trying to diagnose the problem actually fixes it.12:36
osse \o/12:36
grayjoc joined12:36
Guest54 joined12:39
sbasso joined12:40
tmsmith joined12:40
Vampire0 cousteau, well, it is not so much a glitch. If you press F5, it just updates and adds stuff that was added. But commits that are already shown stay shown even if they are dangling.12:40
AstralStorm left12:40
AStorm joined12:40
thebope joined12:40
cousteau I see, so that's what Reload does (rather than Refresh)12:40
Guest54 left12:40
Vampire0 cousteau, if you want to get those away do Shift+F5 and the repo will be reread completely and the graph rebuilt, then the dangling commit also is not shown anymore12:40
Guest54 joined12:41
cousteau Ctrl-F512:41
Vampire0 cousteau, unless of course you restart gitk with the SHA of that old commit additionally, then it will again be shown as long as it is still present in the repository12:41
gibbocool joined12:41
jeffreylevesque left12:42
Vampire0 cousteau, or Ctrl+F5, I always forget which of the two modifiers it was, I have it in mechanical memory of my hand, was a 50:50 chance to mention the right one. :-D12:42
AStormAstralStorm12:42
Vampire0 But yes, that is Reload vs Refrsh12:42
cousteau, ah, no, I was right. At least here it is Shift+F512:42
Guest54 left12:43
Vampire0 And it is Update vs. Reload here12:43
osse TIL12:43
Vampire0 TIL?12:43
gibbocool left12:43
tobiasvl Today I Learned12:43
paissad_ joined12:44
Vampire0 ah, ok12:44
brent__ joined12:44
canton7 TYL what TIL means ;)12:45
thebope left12:45
aapaaal joined12:45
ToBeCloud joined12:45
osse MFW12:45
gitinfo set mode: +v12:45
_ikke_ MRW12:45
khfeng left12:45
tymczenko left12:46
cousteau Vampire0, yes, here too12:46
it is mislabeled on the menu12:46
eahmedshendy left12:47
kbeflo joined12:47
cousteau also, I said "Reload" because I had it in Spanish and just guessed the translation12:47
khfeng joined12:47
roelmonn_ joined12:47
cousteau wonders how it is possible to mislabel a shortcut in a menu12:48
ankit01ojha joined12:48
brent__ left12:49
Vampire0 cousteau, the menu says it is Ctrl+F5 while it is Shift+F5? For me also the menu says Shift+F5. Are you on OS X?12:49
perlpilot left12:49
cousteau no, Linux, but probably a super old version of gitk12:49
IRQ` left12:50
tmsmith left12:50
roelmonnens left12:51
osse It's not inconceivable that soemthing is lsot in translation when you translate "update" and "reload"12:51
perlpilot joined12:51
buffal0 joined12:52
cbegin joined12:52
SlashLife^m left12:52
osse Or someone could submit a patch and hide "El impuesto es el robo" somewhere in a huge translation update12:52
cbegin left12:53
Vampire0 cousteau, it is the one from 2.9.3.windows.1 here12:53
tymczenko joined12:54
webguynow joined12:54
marianina8 joined12:55
cousteau I'm still trying to figure out how to get the version of gitk12:56
Tatou left12:56
cousteau 1:1.7.9.5-1ubuntu0.3 ...probably old-ish12:56
basiclaser joined12:56
cousteau I think it's like a year old or so12:56
tymczenko left12:56
tymczenko joined12:57
aw1 left12:58
jeffreylevesque joined12:58
osse ♫ ♪ Fiiiiive yeeeaaars ♪12:58
and four days12:59
JeroenT left12:59
JeroenT joined12:59
osse RIP David Bowie12:59
marianina8 left13:00
skalpin how can I push to a new remote branch and not set the upstream?13:00
osse skalpin: leave out the -u13:00
marianina8 joined13:01
Vampire0 cousteau, 1.7.9.5 is from march 2012, so not quite a year. :-D13:01
skalpin git push origin newbranchname gave me 'error: src refspec newbranchname does not match any.'13:01
pinkkis left13:01
Vampire0 cousteau, maybe you should update, at least your Git, on a very old Ubuntu I simply compile Git myself and have the latest and greatest, not very problematic13:01
osse skalpin: do you have a local branch named newbranchname ?13:01
skalpin no13:02
iamthad left13:02
osse skalpin: so I guess you want to push the current one =13:02
git push origin HEAD:refs/heads/newbranchname13:02
andrew710 left13:04
Vampire0 cousteau, actually it is the single-liner `make prefix=/usr all doc info && sudo make prefix=/usr install install-doc install-html install-info` to install it to the system locations if the needed tools like dobook2x and so on are installed already13:04
skalpin osse: ty that's exactly what I wanted13:04
cousteau ok, maybe it was ...ah, that must be the date when I installed it, duh m(13:04
Vampire0 cousteau, probably13:05
leeN joined13:06
Cabanossi left13:07
iamthad joined13:07
porsche944 joined13:08
Gsham joined13:08
Cabanossi joined13:09
Darcidride joined13:09
bannakaffalatta left13:11
ExoUNX joined13:12
peterbec` joined13:12
buffffal00 joined13:12
buffal0 left13:14
mehola joined13:16
peterbec` left13:17
pinkkis joined13:18
buffffal00 left13:19
theoceaniscool joined13:19
GT4066 joined13:20
raspado joined13:21
mehola left13:21
kbs joined13:22
chachasmooth left13:23
bumpy left13:24
dglambert joined13:25
dglambert yo13:25
chachasmooth joined13:25
raspado left13:25
tmg left13:25
karols146 joined13:26
GT4066 left13:26
snowalpaca joined13:26
theiostream joined13:27
buffal0 joined13:27
netj left13:27
netj joined13:27
nilg joined13:28
gtifbv joined13:29
ayogi left13:29
jnavila left13:30
h12o joined13:30
DarkPsydeLord joined13:31
octo8 joined13:31
theiostream left13:31
mda1 left13:32
dsdeiz left13:32
mda1 joined13:32
chachasmooth left13:33
dsdeiz joined13:33
dsdeiz left13:33
dsdeiz joined13:33
octo8 Hello, what does *~ mean in .gitignore files ?13:33
osse octo8: all files that end with a tiled13:34
tiled13:34
fuck13:34
chachasmooth joined13:34
skalpin lol13:34
octo8 osse: thanks, got the idea13:34
thebope joined13:34
octo8 and this folder1/folder2/* ....13:35
it will ignore all the folders in folder2 ? what about the subfolders of folder2 ?13:35
i can't see good documentation for .gitignore :(13:36
smokeysea joined13:36
ronskisika left13:37
skalpin https://git-scm.com/docs/gitignore ?13:37
Elzington joined13:38
smokeysea Hello all, I have a mongodb backup based on git; so we do hourly mongodump to files and they are pushed on git. Data is not huge; less than a GB. But .git size has piled up because all the push histroy is maintained; Is there any way to reduce .git size ?13:38
chachasmooth left13:39
thebope left13:39
mischat_ joined13:40
arooni left13:40
Dougie187 joined13:41
GodGinrai joined13:42
osse octo8: they are regular patterns like *.txt etc. for the most part. man gitignore13:42
gitinfo octo8: the gitignore manpage is available at http://jk.gs/gitignore.html13:42
dsdeiz left13:42
Murii left13:42
octo8 is reading13:42
steeze joined13:42
rchavik left13:43
mischat left13:43
theiostream joined13:44
steeze left13:44
kbs smokeysea: I assume git-gc isn't a panacea for your particular situation :-)?13:46
Ice_Strike left13:46
Ice_Strike joined13:48
lugzer left13:48
oleo joined13:48
lugzer joined13:49
arooni joined13:50
lugzer left13:50
plasticle joined13:50
fbwnd left13:50
Cabanossi left13:51
jagob left13:53
aapaaal left13:53
Cabanossi joined13:54
octo8 osse: skalpin: i have read both pages, I still want to to know if 'folder1/folder2*' will exclude all files in folder2 and sub folders of folder2, right ?13:55
snowalpaca left13:55
dglambert left13:57
kbeflo left13:58
kbeflo joined13:58
Assault_ joined13:59
crose joined13:59
GodGinrai left14:00
GodGinrai joined14:00
bocaneri left14:00
rscata left14:00
paissad_ left14:01
Assault left14:02
hiwk joined14:02
robattila256 left14:03
demize smokeysea: Other than removing history, switch to a non-binary backup format that diffs well and git will pack them up rather nicely.14:03
bannakaf_ joined14:03
eahmedshendy joined14:03
cousteau left14:03
hiwk I have a bunch of tags, and I have a file A with a number of commits. How can I list, per tag, which version of file A is refered to by the tag?14:04
inflames joined14:05
watom- left14:05
hiwk or, alternatively, how can I in the log for file A list which tag checkout would yield which commit of file A?14:05
git log --decorate -- A does not help me, because the commits that are listed for file A are not the ones the tags reffer to14:06
octo8 osse: skalpin: i made an experiment myself, it does exclude sub folders all files...14:07
menip joined14:07
TbobbyZ joined14:08
snowalpaca joined14:08
dec0n left14:09
Brski left14:10
holodoc left14:11
Assault_ left14:11
TbobbyZ left14:12
LeBlaaanc joined14:12
peterbec` joined14:13
publio joined14:13
kbs left14:13
matoro left14:13
holodoc joined14:13
lavalamp joined14:13
chachasmooth joined14:13
dvaske left14:16
inflames left14:19
peterbec` left14:19
Murii joined14:20
kbeflo left14:20
h12o left14:20
bitmod joined14:20
cdg joined14:20
aw1 joined14:21
GodGinrai left14:21
cdg left14:24
kbeflo joined14:24
ronin_work left14:24
cdg joined14:24
ronin_work joined14:24
Starky joined14:25
osse octo8: Ahh.14:25
I like your attitude14:25
matoro joined14:26
manuelschneid3r joined14:26
jagob joined14:27
Starky left14:27
kbs joined14:28
theoceaniscool left14:28
Starky joined14:28
thebope joined14:28
ronin_work left14:29
ferr1 left14:31
mischat_ left14:31
oskarkv joined14:31
addf joined14:32
zefferno left14:32
thebope left14:33
Eryn_1983_FL left14:34
peacememories joined14:34
h12o joined14:34
gtristan left14:35
Gianormagantrous joined14:36
Gianormagantrous left14:36
Gianormagantrous joined14:36
ash_workz joined14:37
bariscant left14:37
addf left14:40
tymczenko left14:40
mischat joined14:41
yehowyada joined14:42
ferr1 joined14:42
kbs left14:43
theiostream left14:43
AaronMT joined14:44
Gloomy left14:45
chardan left14:47
Eryn_1983_FL joined14:47
mischat left14:49
mischat joined14:49
dendazen joined14:51
ToBeCloud left14:51
ferr1 left14:52
CustosLimen hi14:53
I have a bunch of utter nawbs here14:53
where is a good course for git ?14:53
that is free ?14:53
interactive will be awesome14:54
dglambert joined14:54
Hedgework CustosLimen: Depends... newbs to git with experience at other SCMs, newbs to git who prefer very mathy things with graphs of the internals, or newbs to git who think everything sounds terrifying and want to learn by rote?14:54
CustosLimen https://try.github.io/14:55
that is actually good14:55
Hedgework CustosLimen: That's good for the third group mentioned, but it will give them NO idea of what git is doing. It's purely rote learning.14:55
steeze joined14:55
Gloomy joined14:56
Silmarilion left14:57
netroxen left14:57
snowalpaca left14:57
chele left14:59
MutantMa_ left15:00
visual well have a good day guiz!15:00
Cavallari left15:00
overlord_tm left15:01
exarch joined15:01
roelmonn_ left15:01
cdg left15:02
cdg joined15:03
CustosLimen Hedgework, rote ?15:04
Hedgework, nawbs nawbs like in probbably should not be using a computer15:04
lavalamp left15:04
JeroenT left15:04
JeroenT joined15:04
ogny left15:05
mischat_ joined15:06
Hedgework CustosLimen: rote means drilling them until they memorize the steps, without caring whether they understand why they are doing it15:06
masuberu left15:06
CustosLimen Hedgework, rote is then the best I can hope for I guess15:07
Hedgework CustosLimen: in that case...stick with the rote method until they have some clue, but have 1-2 of the smarter ones learn how git actually works so they can unscrew everyone else's merges when they break stuff15:07
CustosLimen TIL a new word though ;)15:07
holodoc left15:07
Hedgework :D15:08
CustosLimen Hedgework, I will just give them a copy pasta to throw away local changes on merge conflicts15:09
mischat left15:09
s2013 joined15:10
Hedgework CustosLimen: Just please tell me you are not a CS prof15:10
I have to deal with the people you schmucks give degrees to...15:11
CustosLimen Hedgework, no15:11
holodoc joined15:11
theiostream joined15:11
menip left15:11
CustosLimen Hedgework, I'm just a poor developer working at a dying company :/15:11
JeroenT left15:12
bitmod left15:12
bitmod_ joined15:12
Hedgework awww :(15:13
My condolences, then.15:13
moei joined15:13
moei left15:13
moei joined15:14
sathed left15:14
_Vi left15:14
troulouliou_div2 left15:15
mohan_ joined15:15
peterbec` joined15:15
drodger left15:15
mohan_ left15:16
TbobbyZ joined15:17
mehola joined15:17
kbeflo left15:18
nobitanobi joined15:18
mohan_ joined15:18
smokeysea left15:19
Gustavo6046 joined15:19
trulycool left15:19
sbasso left15:19
trulycool joined15:19
Forlorn left15:20
kbs joined15:20
jimklo joined15:20
peterbec` left15:20
drodger joined15:21
mehola left15:22
andrew710 joined15:22
sotoz left15:22
thebope joined15:22
andrew710 left15:23
nobitanobi Is there a way to find the logs of a specific method in Ruby? I am trying to use `git log -L` with funcname option, but I am getting a `fatal: -L parameter 'initialize' starting at line 1: no match` . I am in 2.3.8 version and according to https://git-scm.com/docs/git-log/2.3.8 I have that feature15:23
I am doing this: `git log -L :initialize:my_filename.rb`15:23
I am basically trying to find the logs specific to that `initialize method in that file15:24
mohan_ left15:24
Khisanth left15:24
mohan_ joined15:24
selckin joined15:25
synthroi_ left15:25
ronin_work joined15:25
troulouliou_div2 joined15:26
kbs left15:26
eahmedshendy left15:26
marianina8 left15:26
schleppel left15:27
FrozenFire Is it possible to have a submodule not be cloned by git submodule update in its parent repo?15:27
thebope left15:27
FrozenFire That is, require it to be specifically targeted15:27
marianina8 joined15:27
Dougie187 FrozenFire: Isn't the the default? I thought you needed to specify `git submodule update --recursive` to get sub-submodules.15:28
kbeflo joined15:28
kbeflo left15:28
FrozenFire Dougie187, I'm asking about a submodule, not recursive15:29
thiago joined15:29
FrozenFire I have a submodule in this repo which is only accessible to specific people15:29
kbeflo joined15:29
Dougie187 Oh, sure. `man git submodule`15:29
gitinfo the git-submodule manpage is available at http://jk.gs/git-submodule.html15:29
Dougie187 Look at update.15:29
It takes a path.15:29
bongjovi left15:29
elect_ left15:29
Dougie187 So, you can specify which you want to update, and which you don't want to.15:29
I'm also pretty sure that if they don't init the repo, update won't do anything.15:30
err, init the submodule.15:30
sz0 joined15:30
drodger left15:31
nobitanobi left15:32
drodger joined15:32
ResidentBiscuit joined15:32
schleppel joined15:32
Elzington left15:33
mohan_ left15:33
Droolio joined15:33
brent__ joined15:33
mohan_ joined15:33
shgysk8zer0 joined15:33
buffffal00 joined15:34
buffal0 left15:35
FrozenFire Great. Thank you. :)15:36
synthroid joined15:36
Khisanth joined15:37
synthroi_ joined15:37
grayjoc left15:37
jagobdue joined15:37
Gsham left15:38
bouncy joined15:38
xall joined15:39
brent__ left15:39
synthroid left15:40
nowhere_man left15:42
drodger left15:43
dreiss joined15:44
grayjoc joined15:44
raspado joined15:45
sea-gull left15:47
clmsy left15:47
xanadu_ left15:47
netroxen joined15:48
hiwk left15:48
drodger joined15:49
GT4066 joined15:50
jimi_ left15:51
theoceaniscool joined15:51
digidog joined15:54
grayjoc left15:54
sbulage left15:54
_Vi joined15:55
xanadu_ joined15:55
xall left15:55
smokeysea joined15:55
brent__ joined15:57
svm_invictvs joined15:57
Gsham joined15:58
ronin_work left15:59
buzzLightBeer left16:00
JanC_ joined16:00
JanCGuest2350016:02
Guest23500 left16:02
JanC_JanC16:02
Hanumaan joined16:02
mda1 left16:02
bouncy left16:03
darkmist joined16:03
Hanumaan is it good to keep files of sizes above 25 MB in git?16:03
dtbn left16:03
nowhere_man joined16:03
mda1 joined16:03
onehrxn left16:03
FrozenFire Is it good? No16:03
Can you do it? Yeah16:04
synthroid joined16:04
h12o left16:04
Hanumaan FrozenFire, what would be max size you recommend in git?16:04
FrozenFire It's more about what the file is16:04
Do you need to version that file?16:04
Is it a format which can be intelligibly diffed?16:05
dtbn joined16:05
Hanumaan yes it might change in 6 every months and it is not a binary file16:05
FrozenFire In that case, sure, put it in git.16:05
Hanumaan its a text file16:05
FrozenFire But you might want to break that file up into pieces instead16:05
drodger left16:05
FrozenFire That is, use include syntax in the relevant language16:06
tlaxkit left16:06
s1scha joined16:06
synthroi_ left16:06
Hanumaan is there any in-built technique that breaks file in git?16:06
roelmonnens joined16:07
FrozenFire Don't think so16:07
The purpose of breaking the file up would be to make it easier to manage changes16:07
henriknj joined16:08
Silenced left16:09
dreiss left16:10
matoro left16:11
roelmonnens left16:11
drodger joined16:11
durham joined16:12
gtifbv left16:12
dtbn left16:14
xall joined16:15
PaoloP joined16:15
al-damiri joined16:15
mohan_ left16:16
PaoloP left16:16
faLUCE joined16:16
peterbec` joined16:16
thebope joined16:17
tang^ joined16:17
hashtagstrashtag joined16:17
mehola joined16:18
dvaske joined16:18
drodger left16:19
tyreld joined16:20
pks left16:21
peacememories left16:21
thebope left16:21
peterbec` left16:21
pks joined16:22
LionsMane joined16:22
mehola left16:23
vhscrb joined16:23
madewokherd joined16:25
drodger joined16:25
fuzzzerd joined16:26
iehl joined16:26
imack left16:26
xanadu_ left16:27
mischat_ left16:27
mischat joined16:28
jstimm joined16:28
netroxen left16:29
bkeys joined16:29
bkeys How do I fetch a remote branch?16:29
Running `git fetch --all' does nothing16:29
TomyLobo2 joined16:30
tvw left16:30
ayogi joined16:30
whitby "fetch a remote branch"?16:30
Do you mean checkout?16:30
bkeys I guess?16:31
orbyt_ joined16:31
bkeys I just want to download a remote branch16:31
maroloccio left16:31
fbwnd joined16:32
Fallen0223 joined16:32
drodger left16:32
whitby Ah, yeah, so it's (kind of) a two step process. `git fetch $remote` will download it. `git checkout $branch` will check it out..16:32
bkeys So say my branch is called foo_bar16:32
a_thakur joined16:32
bkeys It would be git fetch origin/foo_bar16:32
mischat left16:33
whitby (That might work, I'm not sure off-hand, but) `git fetch origin && git checkout foo_bar` would work.16:33
kexmex left16:33
orbyt_ left16:33
bkeys git fetch origin does nothing16:33
drodger joined16:33
whitby It does something :)16:34
It might have done it already16:34
aielima joined16:34
bkeys I do git branch -l and it just shows master16:34
whitby Yes, you need the 2nd half of the command: `git checkout foo_bar`16:34
drodger left16:35
bkeys error: pathspec 'binary_map' did not match any file(s) known to git.16:35
achadwick left16:35
fxrs joined16:35
whitby Is that after trying to checkout?16:36
bkeys Yes16:36
smokeysea left16:36
xanadu_ joined16:37
iehl left16:37
whitby Weird, are you sure that you have the correct branch name?16:37
jab416171 if I add a file on the master branch, make a new branch, delete the file, and then re-add the same file, is git now tracking two version of that file (taking up twice as much space) or is it smart enough to only store one copy?16:37
bkeys whitby: I am just on master on a freshly cloned repo16:37
jab416171 this is a binary file16:38
orbyt_ joined16:38
a_thakur left16:38
bwn left16:38
Cabanossi left16:38
matoro joined16:38
whitby bkeys: `git branch -vv --all` show the branch in the list (it should show up as `origin/$name`16:38
Does*16:38
Hanumaan left16:39
Cabanossi joined16:39
bkeys It shows local master, remotes/origin/master, and remotes/origin/HEAD16:39
But not my branch16:39
mikecmpbll left16:39
whitby Then the branch doesn't exist. I'm not sure why.16:40
Are you sure it's on the remote?16:40
drodger joined16:40
bkeys https://notabug.org/bkeys/DMUX/src/binary_map16:40
Given this is the branch I am trying to fetch, yes16:40
kexmex joined16:41
freexand joined16:41
sbasso_ joined16:41
whitby Weird, and you said you've run `git fetch origin`?16:41
bkeys Yes16:42
https://share.riseup.net/#yoZcim1gXcNj464WZLdtVA16:42
whitby I've got nothing16:43
That's weird16:43
bkeys Yeah all stack overflow questions tell me to do basically the same as you did16:44
whitby Unless it's a shallow clone?16:44
bkeys Yes it is16:44
You mean git clone --depth=116:44
?16:44
whitby Yeah16:44
bkeys Yeah this is a shallow clone16:44
kbeflo left16:45
whitby Yeah, that's the problem16:45
It's fixable though16:45
http://stackoverflow.com/q/23708231/1267663 is what you're talking about16:46
Cavallari joined16:47
bkeys Seems like there are workarounds16:47
But not really worth it; I will just reclone with the git history16:47
bwn joined16:47
whitby Yep, I would recommend not using shallow clones (unless you're aware of the trade-offs)16:48
Eryn_1983_FL left16:49
kurkale6ka left16:50
bkeys Yep that worked16:50
raynold joined16:51
dtbn joined16:51
whitby jab416171: maybe, I think so (if the file is exactly the same the blob should have the same hash)16:52
Though someone else may be able to confirm16:52
dviola joined16:54
flaviodesousa left16:54
rmbeer joined16:54
rmbeer hello16:54
bkeys left16:55
marscher left16:55
rmbeer what command can show all diff about of a commit? i not found where show from the gitg. (I want view from terminal why gitg is very low)16:55
ronin_work joined16:56
theoceaniscool left16:57
dysfigured rmbeer: git show <commit> perhaps?16:57
Gianormagantrous left16:57
octo8 a bit urgent question, is this note really series ? https://paste.ofcode.org/3227wYCjiw2sCJNiGEgfRvN16:59
rmbeer dysfigured, yes, thank! I was using it in error 'git diff [SHA]'..16:59
LionsMane left16:59
LionsMane joined17:00
Eryn_1983_FL joined17:02
theiostr_ joined17:02
lavalamp joined17:02
jstimm left17:02
dysfigured rmbeer: i use this with fzf.. https://u.teknik.io/uKnGQ.webm17:03
jstimm joined17:03
dysfigured git log --graph --color --format="%C(auto)%h%d %s %C(black)%C(bold)%cr" | fzf --ansi --preview='git show --color=always "$(grep -m1 -o "[a-f0-9]\{7\}" <<< {})"' --bind='Enter:execute:LESS=-R PAGER=less git show --color=always "$(grep -m1 -o "[a-f0-9]\{7\}" <<< {})"'17:03
sunrunner20 left17:05
bocaneri joined17:05
[twisti] left17:05
fees left17:05
rmbeer dysfigured, nicee. you have a good term. :)17:06
sequence joined17:06
theiostream left17:06
LionsMane left17:06
rmbeer dysfigured, i can view you PS1?17:07
dysfigured i use zsh https://github.com/DanielFGray/dotfiles/blob/master/zsh/themes/agnoster.zsh-theme17:07
myhau joined17:07
eahmedshendy joined17:08
rmbeer i see. Only work for zsh.17:10
cjohnson you can usually make something similar happen in bash17:10
but really you should just use zsh ;)17:10
jast left17:10
lavalamp left17:10
xall left17:10
cjohnson where does fzf come from dysfigured?17:10
no package called fzf17:10
aw1 left17:11
thebope joined17:11
cagomez joined17:11
jast joined17:12
xall joined17:12
rmbeer now test zsh17:12
zxd left17:12
troulouliou_div2 left17:13
octo8 if the current branch is live, and i want to push to live, then the command is 'git push origin live' ?17:13
cd-rum joined17:13
j416 octo8: that should work.17:14
peterbec` joined17:14
j416 (if your remote is called "origin")17:14
shgysk8zer0 left17:14
dysfigured https://github.com/junegunn/fzf17:15
thebope left17:15
dysfigured fzf is a lot like dmenu, it takes stdin, lets you interactively pick lines, and then prints the result to stdout. it does have a few more bells and whistles though, like --preview and --bind17:15
cjohnson thanks, installing17:16
s1scha left17:16
vhscrb left17:16
dysfigured that commit viewer is actually part of a script i'm writing https://github.com/DanielFGray/fzf-scripts/blob/master/fzgit17:16
dreiss joined17:16
grayjoc joined17:17
kbeflo joined17:17
kbeflo left17:17
kbeflo joined17:17
faLUCE hello does myfile pass to stage area when I do git add myfile?17:18
Gianormagantrous joined17:18
Gianormagantrous left17:18
Gianormagantrous joined17:18
cyberz left17:18
faLUCE sorry for the stupid question. just checked17:18
cjohnson yes, that's what add does17:19
add it to the staging area17:19
then commit takes your staged changes and bundles them as a commit17:19
rts-sander I type git rebase -ip HEAD~4, resolve a conflict17:19
now a commit is missing17:19
faLUCE cjohnson: ok thanks17:19
rmbeer left17:19
cyberz joined17:20
matoro left17:20
synthroid left17:21
fbwnd left17:23
Learath2pragma217:23
synthroid joined17:23
jrnieder left17:24
eahmedshendy left17:24
pragma2Learath217:25
brent__ left17:25
peacememories joined17:27
bocaneri left17:28
choki joined17:28
marcogmonteiro left17:29
gitinfo set mode: +v17:29
choki What is the difference between a bare git repo and git clone --separate-git-dir ?17:29
jast the one cloned with --separate-git-dir still contains an index and is marked as a non-bare repo17:30
ronin_work left17:30
Gotham25 left17:31
choki hmm i don't understand yet :/17:31
gopar joined17:31
qqx choki: A bare repo doesn't have an associated working tree where the content is readily accessible. Using --separate-git-dir still has one, just has the repo in a different location than usual.17:31
nixjdm joined17:31
darkmist left17:32
xall left17:33
a_thakur joined17:34
choki i dont know why op is using --bare but in the comments below they recommend --separate-git-dir https://news.ycombinator.com/item?id=1107079717:34
kpease joined17:35
theiostr_ left17:36
theiostream joined17:37
shinnya left17:37
kpease left17:38
a_thakur left17:38
gopar left17:39
dn1987p joined17:39
bvtton joined17:39
gopar joined17:39
hahuang65 left17:41
theiostream left17:41
matoro joined17:41
hhee joined17:42
drodger left17:43
myhau left17:44
drodger joined17:44
cjohnson so basically it lets you simulataneously do a bare clone and get a detached working copy?17:45
would you be able to switch branches on that working copy?17:46
or is this just a one-off copy17:46
just curious, never heard of this flag17:46
dtbn left17:47
Starky left17:48
choki me too, i just wanna improve the way i deal with ma dotfiles :v17:49
cdleonard joined17:50
qqx cjohnson: It is not a bare clone. It's a normal clone, just with a different layout.17:51
You can use it as you would any other non-bare repo.17:51
synthroid left17:53
sequence I have an interesting problem related to "missing necessary objects" on push: https://pastebin.com/E03yBeUz17:54
I'd appreciate any help on this, totally stuck.17:54
theiostream joined17:54
Kaisyu left17:54
sequence `git fsck --full` returns one dangling blob, but is otherwise ok17:54
mroth_ joined17:55
Onionnion_ joined17:55
aleb_ joined17:55
nitemare joined17:55
ec_ joined17:55
Travis-42_ joined17:56
aendrew_ joined17:56
reznord_ joined17:56
martin_g_ joined17:56
huhlig_ joined17:56
dddaviddd joined17:56
diogenese left17:56
theoceaniscool joined17:56
unixdork joined17:56
thekingofbandit joined17:56
mikap joined17:56
jbondhus joined17:56
cjohnson_ joined17:57
d1b_ joined17:57
grantrul1s joined17:57
likewhoa- joined17:57
djh_ joined17:57
Soliton_ joined17:58
jagobdue left17:58
Soliton_Soliton17:58
Ratler_ joined17:58
cjohnson_cjohnson17:58
LeBlaaanc left17:58
sbasso_ left17:59
Matsv- left17:59
saintaquinas[m] left17:59
monty left17:59
ghormoon left17:59
pepijndevos left17:59
Nevik_ left17:59
EvilJStoker left17:59
marvi left17:59
freekevin left17:59
trobotham left17:59
likewhoa left17:59
d1b left17:59
nitemaretrobotham17:59
mikapmika17:59
Onionnion_Onionnion17:59
marvi joined17:59
cdleonard left18:00
Matsv joined18:00
aendrew_aendrew18:00
ghormoon joined18:00
ayogi left18:00
niax joined18:00
gruetzkopf joined18:00
EvilJStoker joined18:00
choki left18:00
Joost joined18:00
Nevik joined18:00
gruetzkopfGuest8588118:00
mroth_mroth18:00
imack joined18:00
jagobdue joined18:01
traxo-xx joined18:01
vrishab joined18:01
aleb_aleb18:01
monty joined18:02
reznord_ left18:02
huhlig_huhlig18:02
saintaquinas[m] joined18:02
freekevin joined18:03
pepijndevos joined18:03
acetakwas left18:03
Eragon joined18:03
ac3takwas joined18:03
Darcidride_ joined18:03
TbobbyZ_ joined18:03
cdg left18:03
Darcidride left18:03
choki joined18:04
Sasazuka joined18:04
dtbn joined18:04
s1scha joined18:04
ec_ec18:05
thebope joined18:05
reznord joined18:05
choki left18:05
Krenair joined18:05
reznord left18:06
TbobbyZ left18:06
myhau joined18:08
TbobbyZ_ left18:08
Cabanossi left18:08
Sound joined18:08
SoundGuest7295118:09
chigang left18:09
Guest72951 left18:09
thebope left18:09
Sound_ joined18:10
dtbn left18:10
Sound_ left18:10
myhau left18:10
plasticboy joined18:10
Cabanossi joined18:12
heinrich5991 joined18:12
BSaboia joined18:12
ertesx joined18:12
LionsMane joined18:13
matoro left18:13
lmat In github, how can I tell what the HEAD of the repository there is?18:13
Discovery joined18:13
sequence lmat: use `git ls-remote` with the name of the github remote18:13
afuentes left18:14
lmat sequence: excellent. Thank you.18:14
bgerber left18:14
svm_invictvs left18:15
ertes left18:15
ertesxertes18:15
lmat Is it possible for git version 2.11.0 to output the following message: "warning: Remote branch ... not found in upstream origin, using HEAD instead" ?18:15
hs8136 joined18:15
lmat in http://stackoverflow.com/questions/20280726 , this happens when he supplies a "tag" to git clone --branch. But that appears to only be for an old version of git?18:16
LeBlaaanc joined18:17
faLUCE I have someproject cloned into someproject-cloned dir; if I enter into someproject-cloned dir, how can sync it with the modifications done meanwhile with upstream?18:17
synthroid joined18:17
peacememories left18:18
matoro joined18:18
hs8136 left18:18
mehola joined18:19
dtbn joined18:20
Rodya_ joined18:20
joki joined18:20
faLUCE (sorry for the previous question, it was not for the channel)18:20
bgerber joined18:21
dvaske_ joined18:22
roelmonnens joined18:23
mehola left18:24
trulycool left18:24
lmat faLUCE: git fetch --all...sort of18:25
lavalamp joined18:25
lmat faLUCE: It's a separate repository. If you want it completely synchronized, re-clone using --mirror.18:25
faLUCE: If you want the commits from the "upstream" repositories, git fetch --all; should do the trick.18:25
dvaske left18:25
faLUCE thnks lmat, I'm reading docs about the difference between pull and fetch18:26
dtbn left18:27
roelmonnens left18:27
ronin_work joined18:28
Eragon left18:28
ThomasLocke left18:29
theiostr_ joined18:30
scoobertron left18:30
theiostream left18:31
freexand left18:33
scoobertron joined18:35
nitric joined18:35
crose left18:36
drodger left18:39
drodger joined18:40
saintaquinas[m] left18:40
Sasazuka left18:40
drodger left18:40
chachasmooth left18:40
imack left18:40
Sleepy63 joined18:41
Sasazuka joined18:42
theoceaniscool left18:43
matoro left18:43
chipotle left18:43
barduck left18:43
chachasmooth joined18:43
GT4066 left18:44
bvtton left18:44
hhee left18:44
hahuang65 joined18:44
drodger joined18:45
cagomez left18:45
saintaquinas[m] joined18:46
nachopolyzen18:49
jimi_ joined18:49
freexand joined18:50
karols146 left18:50
freexand left18:50
basiclaser left18:51
freexand joined18:51
freexand left18:51
xper0 joined18:51
marianina8 left18:52
chachasmooth left18:53
marianina8 joined18:53
marianina8 left18:53
freexand joined18:53
marianina8 joined18:53
freexand left18:53
Cabanossi left18:54
gopar left18:54
kfoonamalik joined18:55
gopar joined18:55
freexand joined18:55
freexand left18:55
Cabanossi joined18:56
freexand joined18:56
freexand left18:56
dhollinger left18:57
freexand joined18:58
freexand left18:58
jimi_ left18:58
kyan joined18:58
peterbec` left18:58
thebope joined18:59
mikecmpbll joined19:00
freexand joined19:00
freexand left19:00
freexand joined19:01
freexand left19:01
freexand joined19:02
freexand left19:02
grayjoc left19:02
BSaboia left19:02
ronin_work left19:03
freexand joined19:03
freexand left19:03
thebope left19:04
Emperor_Earth_ joined19:05
hahuang61 joined19:06
peterbec` joined19:06
chachasmooth joined19:06
hahuang65 left19:07
Emperor_Earth left19:08
nilg left19:09
hahuang65 joined19:09
borkr left19:10
jimi_ joined19:11
hahuang61 left19:11
chachasmooth left19:11
robotroll joined19:12
tang^ left19:12
Brski joined19:13
Acerific joined19:13
hahuang61 joined19:14
dtbn joined19:14
archaic joined19:14
hahuang65 left19:15
chachasmooth joined19:15
robotroll left19:16
kyan left19:17
kexmex left19:18
borkr joined19:18
Cavallari left19:21
kexmex joined19:22
Ice_Strike left19:23
Brski left19:24
PaulCapestany left19:24
sz0 left19:24
molgrum left19:24
tvw joined19:24
Groscheri joined19:24
pedahzur joined19:26
dhollinger joined19:26
TbobbyZ joined19:26
Eragon joined19:27
PaulCapestany joined19:27
pedahzur I found this e-mail thread from 2009, which describes a feature that would be really handy right now: http://git.661346.n2.nabble.com/PATCH-format-patch-add-prefix-to-prepend-a-prefix-to-output-file-names-td3048920.html It's quite the discussion, but it seems the feature was never actually added. Anyone know what happened to it?19:27
porsche944 left19:27
mkoskar left19:27
mkoskar joined19:28
cagomez joined19:28
damsel joined19:29
damsel Hello I was just wondering git reg-list --count origin counts unique commands that are on local but not on remote, EXCLUDING merge-commits(merged on local) how can I count them as well?19:30
bannakaf_ left19:30
bannakaffalatta joined19:30
ThiefMaster left19:30
damsel because git status tells me that my branch is 12 commits ahead while git rev-list --count origin only tells me there are 6 commits19:31
ThiefMaster joined19:31
Eragon left19:31
Eragon joined19:31
cagomez left19:31
PaulCapestany left19:32
MutantMahesh joined19:33
ac3takwas left19:34
Eragon left19:34
qqx damsel: `git rev-list --count origin` would tell you how many commits are in "origin", nothing related to your current branch. Try `git rev-list --count origin..`.19:34
ugjkaxyk19:34
Eragon joined19:34
xykugjka19:34
PaulCapestany joined19:34
damsel qqx it tells me 59,19:35
roelmonnens joined19:35
damsel btw what is up with the ..suffix?19:35
cagomez joined19:35
qqx damsel: That specifies a range, with nothing after it defaults to using HEAD as the end.19:35
It specifies commits in HEAD that aren't also in origin.19:36
damsel ths19:36
qqx To get even closer to what status would be doing you could use `git rev-list --count @{u}..`.19:36
cagomez left19:37
qqx @{u} specifies the upstream branch for your current branch.19:37
damsel ok how come I do not see that in the documentation? besides ref@{u}19:38
or to formulate it differently how can I know?(for me for future learning19:39
@{u}.. did the trick. I count 12.19:39
how come --count HEAD is not counting merge-commits?19:39
PaulCapestany left19:39
qqx It's listed in man git-rev-parse.19:39
gitinfo the git-rev-parse manpage is available at http://jk.gs/git-rev-parse.html19:39
roelmonnens left19:40
damsel ok I was only looking at rev-list19:40
alexandre9099 joined19:41
damsel thank you very much19:41
qqx For me --count includes merges unless I specifically say --no-merges19:41
chipotle joined19:41
damsel ok that is strange ... when I specify --merges nothing changes for me19:42
rokups left19:42
damsel where did your changes occure? local or remote?19:42
askb joined19:42
regedit joined19:42
skypuke_ left19:43
damsel hmm in the manpages it states for rev-list ... omit patch equivalent commits ....19:43
gtristan joined19:44
qqx That's only when used with --cherry-mark.19:44
Perhaps try !graph to help figure out what is being included.19:46
gitinfo [!lol] A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all19:46
PaulCapestany joined19:46
octo8 left19:47
damsel ok.. then I do not know, I can only say how I arrived there, remote branch dev and abc, changes made in dev pushed by me, merged into dev, and then I merged from dev directly into abc locally19:47
and only the merge-commits are excluded19:47
all dedicated commits are counted19:47
MutantMahesh left19:48
cagomez joined19:48
damsel on the note of git rev-parse, it reads like it contains all the "funky" expressions one would need for some nifty scripts if necessary, and that are understood by most/all git-commands. good to know was always wondering where some find these paramters in the SO-answers19:49
grayjoc joined19:49
UrsoBranco joined19:50
damsel anyways thanks for all the help qqx :D19:52
Eugene It also slices, dices, and collates double-sided printing19:53
damsel especially the rev-parse thing19:53
thebope joined19:53
satifant joined19:53
damsel Eugene, probably but I don't wanna find out quite yet, wouldn't know when I would need to actually call reg-parse anyways19:54
gitinfo set mode: +v19:54
sorenb_soerenb19:54
damsel scared to actually kill the companies repo :D19:54
_Vi left19:54
damsel as powerfull as git is19:54
Eugene rev-parse doesn't modify anything19:54
damsel ok I thought your answer was related sry bout that19:54
digidog left19:55
damsel left19:55
Eugene Nah, this is just BS funny because its my lunchtime19:55
tang^ joined19:55
richardlitt joined19:55
perrier-jouet left19:55
david-e joined19:56
qqx You generally wouldn't call rev-parse directly. It's mainly for use by other scripts.19:56
schleppel left19:57
Rodya_ left19:57
kbeflo left19:57
thebope left19:57
Rodya_ joined19:58
Rodya_ left20:00
drodger left20:01
s1scha left20:01
madduck left20:02
miczac joined20:06
HurricaneHarry left20:06
gitinfo set mode: +v20:06
madduck joined20:06
drodger joined20:06
Murii left20:08
mischat joined20:09
HurricaneHarry joined20:09
chardan joined20:11
darkmist_ joined20:12
me__ joined20:12
cydrobolt_ left20:13
cydrobolt joined20:13
cydrobolt left20:13
cydrobolt joined20:13
dendazen left20:14
maroloccio joined20:14
darkmist_ left20:15
matoro joined20:15
xper0 left20:15
theoceaniscool joined20:15
Discovery left20:16
luke_nukem joined20:17
cdg joined20:17
Eragon left20:18
pks left20:19
mehola joined20:20
me__ left20:21
cd-rum left20:23
Groscheri left20:23
cd-rum joined20:24
me__ joined20:24
mehola left20:24
NeverDie left20:24
Nicmavr left20:26
NeverDie joined20:27
jstimm left20:27
bejeb left20:27
shgysk8zer0 joined20:28
j08nY joined20:28
faLUCE I don't understand the meaning of this image: https://git-scm.com/book/en/v2/images/basic-rebase-2.png (from: https://git-scm.com/book/en/v2/Git-Branching-Rebasing) It says that there's a merge between C3 and C4, but the picture still shows C3 and C4 as separated nodes. Why? Should they be grouped into one node called "C3+C4", instead?20:29
Nicmavr joined20:29
bejeb joined20:29
NicmavrGuest8065220:29
sea-gull joined20:30
m0viefreak joined20:30
synthroi_ joined20:30
kadoban faLUCE: No, that's not what merge does in git20:30
aidalgol joined20:31
g0d355__ joined20:31
g0d355__ left20:31
kadoban faLUCE: That would change history, if C3 and C4 didn't exist anymore or something. Instead, a merge commit is created, with the parents of that commit being everything that's being merged into one. C5 is a merge commit that merges C3 and C420:31
PaulCape_ joined20:32
synthro__ joined20:32
orbyt_ left20:33
PaulCapestany left20:33
synthroid left20:34
faLUCE kadoban: I see, so the actual merge is C520:34
thanks20:34
dave0x6d left20:35
theoceaniscool left20:35
synthroi_ left20:35
faLUCE kadoban: so the idea of the rebase is to group multiple commits into one, instead of merging separate nodes?20:36
crose joined20:37
j08nY left20:37
kadoban That's certainly not how I think about rebase, that doesn't sound correct unless you're talking about some specific usage.20:37
jimi_ left20:38
kadoban Rebase usually involves "cutting" a branch out of the existing tree of commits and attaching it somewhere else20:39
peterbec` left20:39
dglambert left20:39
preaction squash is grouping multiple commits into one. rebase is rewinding the tape and then replaying it20:39
kadoban Where in this case we treat a commit as a set of changes from the parent. So it tries to create a new history that includes all of the same changes that happened in an old history.20:39
hahuang61 left20:41
faLUCE kadoban: I have to contribute to a project with a git repo and many developers. hey told me to use rebase when I have to send ONE global modificiation for multiple files with inter-dependencies.20:41
jeffreylevesque left20:42
svm_invictvs joined20:42
_Vi joined20:42
theiostream joined20:44
theiostr_ left20:44
Gsham left20:46
LionsMane left20:47
snits left20:47
thebope joined20:47
synthro__ left20:47
orbyt_ joined20:48
TheOrangeOne left20:51
thebope left20:52
ExoUNX left20:53
snits joined20:53
mmattice left20:54
bdonnahue joined20:54
MineCoins joined20:54
TheOrangeOne joined20:55
dviola left20:55
jimi_ joined20:56
mmattice joined20:58
ronin_work joined21:01
diogenese joined21:03
gtristan left21:05
aielima left21:05
rnsanchez left21:06
me__ left21:07
grayjoc left21:08
AnimeLife joined21:08
AnimeLife Hi devs, when I send an email to git public inbox [email@hidden.address] from hotmail it is not seen at http://public-inbox.org/git/. Can somebody help?21:09
salamanderrake left21:09
Cabanossi left21:09
mmattice left21:09
grayjoc joined21:09
salamanderrake joined21:10
gunnaro joined21:10
tymczenko joined21:11
Cabanossi joined21:11
mmattice joined21:11
hahuang61 joined21:13
MineCoins left21:13
jagobdue left21:14
chipotle left21:15
jost__ joined21:15
Silenced_v2 joined21:15
j416 AnimeLife: it'll take a while.21:16
cd-rum left21:16
AnimeLife ah, thnx for confirmation21:17
cd-rum joined21:17
j416 AnimeLife: what's the subject line?21:17
jost_ left21:18
manuelschneid3r left21:18
AnimeLife [RFC/PATCH] Make “git tag --contains <id>” less chatty if <id> is invalid expand.png print.png thread-popout.png You Hi git developers. I am a student interested for Gsoc. With my patch I am able to produce following output. $ git tag --contains qq error: malformed object name qq $ git tag --contains HEAD q Mar 30, 8:26 pm sending-spinner.gif March 30, 2017, 8:54 PM 1 open ic-dropdown-replyall.pngicon-thread-disclosure.png messag21:18
Sorry21:19
it is [RFC/PATCH] Make “git tag --contains <id>” less chatty if <id> is invalid21:19
buffffal00 left21:19
AnimeLife I just heard from other channel that vger automatically drops html messages, is that trye?21:19
ash_workz left21:20
j416 I can't find your message in my mailbox, at least.21:21
bariscant joined21:21
j416 but don't send html messages.21:21
I wouldn't be surprised if it dropped those21:21
Qdo joined21:21
AnimeLife Thnx, I am fixing the html problem.21:22
dsdeiz joined21:22
AaronMT left21:22
moei left21:23
YuGiOhJCJ left21:23
roelmonnens joined21:24
cd-rum left21:27
AnimeLife j416: Can you please check it again, I sent it in plain text this time21:27
j416 AnimeLife: Varun?21:27
AnimeLife Yes21:28
j416 :)21:28
AnimeLife btw, are you a git contributer?21:28
t0by joined21:28
Silenced_v2 left21:29
bannakaffalatta left21:29
roelmonnens left21:29
keks[m] left21:30
Silenced_v2 joined21:31
j416 technically yes, but not really, no.21:31
todd_dsm left21:31
crose left21:32
j416 I have contributed 1 character to the project.21:32
XD21:32
AnimeLife haha, but thaanks for helping me ;)21:32
j416 o/21:32
bomb-on joined21:35
grayjoc left21:35
grayjoc joined21:35
ronin_work left21:36
grayjoc left21:36
juvenal joined21:36
Darcidride_ left21:37
jimi_ left21:37
davidfetter_ge joined21:39
davidfetter_ge hi21:40
jtoy left21:40
davidfetter_ge if i move and edit a file in a commit, is there any way to record that it's been "renamed" instead of a delete/create21:40
Peng No, but if you adjust the rename detection settings, it'll probably noticde21:41
davidfetter_ge how do i do that?21:41
kbs joined21:41
thebope joined21:41
WeiJunLi joined21:42
TheHelper joined21:42
WeiJunLi i have a super slow connections there's any option i can add on git clone cmd to prevent time outs?21:42
Chinggis6 joined21:43
jast davidfetter_ge: some of the operations in which rename detection is relevant let you specify a detection threshold, e.g. git log -M80. however, if you have too many edits in a renamed file you probably won't find a threshold that doesn't also detect renames where there actually weren't any. :)21:43
TheHelper left21:43
TikityTik joined21:43
danboid joined21:43
danboid How would I go about creating a patch that represents a branch?21:45
crippleye joined21:45
thebope left21:46
molgrum joined21:46
molgrum left21:46
molgrum joined21:46
dtbn left21:46
danboid Is my question clear, I wonder?21:46
kevy0 joined21:46
Es0teric|Work left21:46
davidfetter_ge as in the patch that represent the diff from another branch?21:47
cyberz left21:47
jtoy joined21:48
danboid I have a branch against linux git. I want to create a 'diff' of that branch so that I can create a patch for rc4 that does what the branch does21:48
I don't own the branch21:48
cagomez left21:48
danboid I have requested the maintainer of that branch do this for me but surprisingly he's not responded :)21:49
btree left21:49
cjohnson git diff master...branch21:49
should show you changes introduced in branch since the diverging point21:49
cagomez joined21:49
dersand left21:50
tanuki joined21:50
cyberz joined21:50
danboid cjohnson, That's part of what I need - thanks21:50
cjohnson what is the rest?21:51
danboid cjohnson, Is there an easy way to dump that into a regular diff patch file?21:51
cjohnson it outputs in patch format21:51
just write the output to a file21:51
danboid Oh OK :)21:51
cjohnson git diff master...branch > my.patch21:51
Cabanossi left21:54
borkr left21:54
Dougie187 left21:54
satifant left21:55
mmattice left21:55
juvenal left21:55
eb0t left21:56
masuberu joined21:56
jtoy left21:56
Cabanossi joined21:56
AnimeLife left21:57
jtoy joined21:57
juvenal joined21:59
Atm0spher1c joined22:00
cyberz left22:00
WeiJunLi left22:00
Atm0spher1cGuest6320722:00
buffal0 joined22:01
de-facto left22:01
de-facto joined22:01
bomb-on left22:01
jtoy left22:02
Guest63207 left22:02
cyberz joined22:02
crippleye left22:03
Atm0sphe1 joined22:04
Atm0sphe1 left22:05
blackwind_123 left22:05
dave0x6d joined22:05
Atm0sphe1 joined22:05
bariscant left22:06
mmattice joined22:07
mar77i left22:07
blackwind_123 joined22:07
FrozenFire Does anyone know of a decent resource on pointing submodules to the tip of a remote branch? I've read http://stackoverflow.com/a/9189815/1069833 and it's more of a how-to than information about the pros/cons and underlying implementation.22:08
tvw left22:08
buffal0 left22:08
t0by left22:08
FrozenFire In particular, I have a dependency as a submodule which should preferably always be at a branch's HEAD.22:08
sim642 joined22:09
habbasi joined22:09
myhau joined22:10
tanuki left22:10
tanuki joined22:11
mda1 left22:12
masuberu left22:12
mda1 joined22:13
tanuki left22:13
danboid cjohnson, Actually, I need to diff against a specific tag in a branch22:13
manuelschneid3r joined22:14
tanuki joined22:14
cjohnson danboid: that's fine, replace branch with the tag22:17
the tag just refers to a specific commit in the branch whcih means it will share the same history up to that point with the branch22:17
b0nn joined22:17
cjohnson and thus, the same common ancestor22:17
kegster left22:18
b0nn hi all, I've got a bit of a mess I want to clean up; I am in a branch, and I am getting a message about being ahead of a different branch by n commits. All I want to do is scratch and git clone, without causing any issues for anyone else22:18
How do I do that?22:19
gugah left22:19
cjohnson to me the easiest way to do that is to just delete the local copy and re-clone22:19
but if you have some untracked local files22:20
b0nn les, that's what I want to do22:20
cjohnson oh then yeah, just do that22:20
delete the dir22:20
danboid cjohnson, So if this is the branch command `git fetch https://git.pengutronix.de/git/pza/linux.git tags/v4.10-ipu-dp-plane-fix`22:20
b0nn Are you saying, just rm -rf the tree?22:20
cjohnson git clone22:20
yeah that's what I do if I don't have important untracked files/changes22:20
danboid cjohnson, How does that translate into a branch/tag22:20
ankit01ojha left22:20
b0nn good, I'll give it a go.22:21
mehola joined22:21
cjohnson danboid: well normally if you are specifically wanting to compare with a remote22:21
I would set it as an actual remote instead of hard specifying the URL22:21
LeBlaaanc left22:21
cjohnson git remote add upstream https://git.pengutronix.de/git/pza/linux.git22:22
then you can just use upstream/tags/v4.10-ipu-dp-plane-fix22:22
bannakaffalatta joined22:22
cjohnson to refer to that upstream tag22:22
danboid cjohnson, OK - thanks!22:22
juvenal left22:23
darkmist_ joined22:23
jagob left22:24
myhau left22:25
sea-gull left22:25
mehola left22:25
danboid cjohnson, Nah I'm lost :)22:27
druonysus joined22:27
danboid cjohnson, I want to diff https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git aagainst that branch and tag above22:27
cjohnson which branch of the linked repo are you diffing against22:28
you can't diff a branch against a whole repo22:28
zerocua joined22:29
jimi_ joined22:29
danboid cjohnson, I want to diff againt Linux 4.11rc422:29
cjohnson that's the name of the branch?22:29
or what22:29
danboid 4.11-rc422:29
Its a test release22:30
cjohnson git remote add upstream https://git.pengutronix.de/git/pza/linux.git22:30
gugah joined22:30
cjohnson git diff upstream/tags/4.11-rc4..tags/v4.10-ipu-dp-plane-fix22:30
two dots gives you a complete diff22:30
three dots will tell you differences from one side only22:31
danboid that first command: `fatal: Not a git repository (or any of the parent directories): .git`22:32
cagomez left22:32
ronin_work joined22:32
cjohnson you can't run git commands in a dir that isn't a git repo22:33
danboid cjohnson, I need to clone the repo I'm diffing against first do I?22:33
gopar left22:33
Fallen0223 left22:33
cjohnson Wait, you just want to diff two branches on the same remote repo?22:34
zerocua left22:34
cjohnson I thought you wanted to diff your local changes to the remote22:34
FrozenFire If I've used `git submodule update --remote`, how can I reset an affected submodule's superproject commit back to what it was?22:34
gugah left22:34
aidalgol left22:34
cjohnson from the super project, you can just git reset HEAD path/to/submodule22:35
FrozenFire Thanks22:35
Fallen0223 joined22:35
danboid cjohnson, No. I want to diff a tag on one repo (the latest Linux 4.11 rc4) against a tag in a different repo/tag22:35
thebope joined22:35
david-e left22:36
cjohnson when you say repo, do you mean branch?22:36
you can't compare across two repositories22:36
unless they are clones of one another of course22:36
sorry I see now. You have two remotes, presumably one is a clone of the other22:36
danboid cjohnson, Yes, they are all clones of the Linux kernel22:36
shgysk8zer0 left22:37
cjohnson I would clone the authoritative master, then add each one as a remote22:37
then use the diff command using the remote name in the path for each22:37
manuelschneid3r left22:37
cjohnson git remote add official //git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git22:37
zerocua_ joined22:37
cjohnson woops22:37
ResidentBiscuit left22:38
cjohnson git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git22:38
git remote add pengutronix https://git.pengutronix.de/git/pza/linux.git22:38
git diff tags/4.11rc4...pengutronix/tags/v4.10-ipu-dp-plane-fix22:38
darkmist_ left22:38
cjohnson something like that22:38
Cabanossi left22:39
Qdo left22:39
danboid cjohnson, OK - I should be able to work it out from here :)22:39
I've only ever used the most basic features of git22:39
thebope left22:40
b0nn hm, so, the clone went well (ish) but I'm missing code locally that exists remotely22:41
Cabanossi joined22:41
darkmist_ joined22:41
chipotle joined22:42
b0nn I can see the code remotely ( bitbucket) but it doesn't exist locally22:43
ideas22:43
?22:43
cjohnson different branch?22:44
anuxivm joined22:45
Tatou_ joined22:49
Fallen0223 left22:50
shgysk8zer0 joined22:50
darkmist_ left22:50
Tatou_ left22:51
Fallen0223 joined22:51
Tatou joined22:51
Tatou test22:51
Acerific left22:51
gunnaro_ joined22:53
gunnaro left22:53
Guest30225 left22:55
matoro left22:55
Tatou I want to mirror all my gitlab repos to local. Is this doable?22:56
publio left22:56
cagomez joined22:57
Guest30225 joined22:57
kbs dunno much about gitlab, but curious - what does mirror'ing mean in this context (presumably not just cloning all repos :-)22:57
Tatou Cloning all repos and keeping htem up to date!22:57
cagomez left22:57
Tatou I'm not sure how much I trust gitlab.. They have some sketchy approaches to keeping their service running22:58
Guest30225 left22:58
Guest30225 joined22:58
Guest30225lb22:58
kbs oh :-) in my naive thinking, I might just have a cron job to periodically run git update, but maybe you're looking for something different...22:58
lb Tatou seen gitea already?22:58
Tatou gitea?22:59
lb Tatou gitlab/github alternative http://gitea.io/22:59
Tatou ok cool, so here is what I need: I need private repos for me alone, for code I won't have on any machine potentially..23:00
getxsick joined23:00
Tatou Like I keep puppet manifests on there to setup my machines23:00
lb Tatou bitbucket offers free private repos?23:00
Tatou bitbucket is altassian?23:01
theiostream left23:01
lb yes23:01
juvenal joined23:01
Tatou Ok, that works for me!23:01
lb there you go :)23:01
matoro joined23:02
Tatou haha, what.. I have code on there from 201223:03
Why the hell did I use git in 2012..23:03
Sasazuka_ joined23:03
bdonnahue left23:04
zerocua_ left23:04
bdonnahue joined23:04
Sasazuka left23:04
miczac left23:05
jimi_ left23:05
aidalgol joined23:05
tmg joined23:06
eb0t joined23:06
Chinggis6 left23:07
zerocua_ joined23:07
ronin_work left23:07
freexand joined23:07
freexand left23:07
safe joined23:08
freexand joined23:08
freexand left23:09
finalbeta left23:10
freexand joined23:11
nixjdm left23:11
freexand left23:11
unbalancedparen joined23:12
unbalancedparen left23:12
freexand joined23:13
roelmonnens joined23:13
freexand left23:13
cdg left23:14
freexand joined23:15
freexand left23:15
cheesegits joined23:15
zerocua joined23:15
zerocua_ left23:17
freexand joined23:17
gugah joined23:17
freexand left23:17
roelmonnens left23:17
cyberz left23:18
joki left23:18
todd_dsm joined23:18
robattila256 joined23:18
freexand joined23:19
freexand left23:19
Emperor_Earth_ left23:20
cyberz joined23:21
gugah left23:26
kexmex left23:26
DarkPsydeLord left23:27
maroloccio left23:28
zerocua left23:28
anuxivm left23:28
juvenal left23:28
scoobert1on joined23:29
mischat left23:29
thebope joined23:29
cyberz left23:30
zerocua joined23:30
D4R5C0D3 left23:32
cyberz joined23:33
scoobertron left23:34
thebope left23:34
danboid left23:34
danboid joined23:34
tterrag so I have a bit of an odd problem to solve. someone has made 2 PRs of *about* the same content to two different branches. however, I'm trying to keep branch B purely ahead of branch A so I can merge easily.23:35
the PR only consists of adding one file. so I essentially just want to diff the file in branch B against the one in branch A and apply it as a change instead of a new file23:36
is that doable? or will I have to do it manually23:36
henriknj left23:36
overlord_tm joined23:36
holodoc left23:36
tang^ left23:37
albel727 left23:39
crose joined23:42
curtii joined23:42
cyberz left23:42
albel727 joined23:43
gitinfo set mode: +v23:46
curtii Hello everyone! I got something I've been struggling with throughout the day, regarding git permissions23:46
cyberz joined23:46
curtii Wondering if anyone here has advice. I'm setting up an Icinga monitoring server, and a good recommendation I found is to make the root directory for it's configurations a git repository23:46
Been working great, doing all the stuff git is supposed to do23:47
crose left23:47
zerocua left23:47
curtii The issue I'm running into is I'd like to make backups, by cloning (pushing, really) this repository into a mounted NFS share, and it's been problematic due to permissions23:47
TbobbyZ_ joined23:49
curtii Problem is I can't really monkey with the file permissions in the original location without screwing up the monitoring server, and without changing the permissions, I get denied permission to write to the NFS mounted backup share23:49
Tobbi left23:49
zerocua joined23:50
curtii Files in the original location are owned by root, and due to the way my NFS server is setup, I can't really make the share accessible to root.23:50
sbeller left23:52
TomyLobo2 left23:52
shgysk8zer0 left23:52
TbobbyZ left23:52
shgysk8zer0 joined23:52
TbobbyZ_ left23:53
hashtagstrashtag left23:54
darkmist_ joined23:54
holodoc joined23:54
curtii So I'm kind of stuck in one of three scenarios: I'm logged in as root, and can't write to the NFS share - Logged in as normal user, and can't access the git repo - I change the file permissions/owner, and my monitoring configuration is broken23:54
gunnaro joined23:55
j08nY joined23:56
shgysk8zer0_ joined23:56
darkmist_ left23:56
overlord_tm left23:57
danboid left23:57
matoro left23:57
danboid joined23:58
tymczenko left23:58
sbeller joined23:58

Logs Search ←Prev date Next date→ Channels Documentation