IRCloggy #git 2017-02-13

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-02-13

canuk joined00:00
Gravious left00:06
Ranmaru left00:10
finalbeta left00:10
Phylock left00:13
Vampire0 gry, a branch is just a post-it note on a commit. A commit does not belong to a branch. It may be part of the history of the commit a branch pointer currently points at, but a commit can be part of any amount of branches, including none00:14
Serus left00:18
Vampire0 gry, and to pick the commit the branch pointer "vampire" currently points at, simply do `git cherry-pick vampire`00:18
King_Hual left00:23
efeuska left00:25
matoro left00:25
Derperpe1 joined00:27
Nugget_ joined00:27
Oatmeal left00:27
ejnahc left00:28
Nugget left00:29
Derperperd left00:29
olbat left00:29
nunchuck left00:29
clemf_ joined00:29
ejnahc joined00:29
mischat left00:30
olbat joined00:30
clemf left00:30
pur3eval joined00:34
yqt left00:37
yqt joined00:37
pur3eval left00:38
jameser joined00:41
dbl4k left00:43
astrofog left00:43
flashpoint9 joined00:45
om_henners joined00:46
flashpoint9 Hey guys, had a question. I have a remote server that I would like to communicate with repos belonging to a group on github, I also want to push and pull to those repos locally. Im thinking about using deploy keys (not 100% sure) on the server so that I can push and pull from github while on the server and using the same SSH keys for local, is that the best/right way to handle what I want?00:48
gry thanks Vampire0!00:48
jameser left00:49
brent__ joined00:52
m0viefreak left00:52
peterR`` left00:53
yqt left00:53
Goplat left00:53
yqt joined00:54
Brain left00:57
Vampire0 gry yw00:59
gitinfo flashpoint9: Note that git != github. Feel free to ask us about Github-specific features (Forks, Pull Requests, Wikis, etc), but there are no guarantees. There is a #github channel, which might help too (again, no guarantees)01:00
matoro joined01:00
brokensyntax left01:00
watabou left01:01
flashpoint9 gitinfo: Ok, I wondered if I was asking in the wrong channel but thought I would give it a try since it's more of a methodology question (ie. what would you do in my situation)01:02
watabou joined01:02
peterR`` joined01:02
brokensyntax joined01:03
gry left01:07
denimsoft joined01:08
datahead8888 left01:11
ozmage joined01:12
CussBot joined01:14
fatalhalt_ joined01:16
cdown left01:16
nikivi left01:17
Perspicaciosity left01:17
MrWoohoo left01:18
shinnya joined01:18
netj left01:18
nikivi joined01:19
fatalhalt left01:19
__builtin joined01:19
DolpheenDream left01:20
rbjorklin joined01:20
cdown joined01:20
kyan left01:20
iamtakingiteasy joined01:21
Ardethian left01:21
yqt left01:21
netj joined01:21
yqt joined01:22
Saturn812 joined01:22
linuxmodder joined01:22
xlegoman left01:24
newbie joined01:25
xlegoman joined01:25
dsdeiz joined01:27
yqt left01:28
akkad joined01:30
mischat joined01:30
cheater joined01:32
cheater hi01:32
when specifying a revision for something like git diff, is there a way to say "diff between <rev0> and the nearest common ancestor of <rev1> and <rev2>"?01:33
or01:33
"diff between <rev1> and the nearest common ancestor of <rev1> and <rev2>"?01:33
kyan joined01:34
brent__ left01:34
cheater i.e. i am on a branch and i would like to see the complete diff since i branched off from master01:34
e yes01:34
look at ... (as opposed to ..) in git help diff01:35
pur3eval joined01:35
cqi joined01:36
d1z left01:36
mischat left01:38
mikecmpbll left01:39
pur3eval left01:39
dreaddymck left01:44
Levex joined01:45
levex_ left01:45
brent__ joined01:49
gelei007 joined01:50
chipotle left01:50
chipotle joined01:52
Tobbi left01:52
levex_ joined01:53
Levex left01:53
fatalhalt__ joined01:53
d1z joined01:53
howitdo joined01:54
howitdo left01:54
howitdo joined01:54
dwmw2_gone joined01:54
MattMake_ joined01:56
ozmage left01:57
fatalhalt_ left01:57
MattMaker left01:59
brent__ left01:59
elsevero joined02:00
acetakwas joined02:01
MattMake_ left02:01
fatalhalt__ left02:02
sharkz joined02:04
Vgr joined02:04
Vgr left02:04
Vgr joined02:04
Wulf4 joined02:04
ffilozov joined02:05
geoid_ left02:06
geoid_ joined02:06
pbrewczynski left02:06
geoid_ left02:07
Wulf left02:07
Wulf4Wulf02:07
Somelauw If one repo stores a file a and another repo stores a file subdir/subdir/subir/a, is it possible to cherry-pick from subdir/subdir/subdir/a to a or should I just manually copy the changes and give credit in the commit message?02:09
sbulage joined02:11
shinnya left02:13
newbie1 joined02:14
pks left02:15
b1tchcakes left02:15
anuxivm left02:16
newbie left02:17
finalbeta joined02:17
dwmw2_gone left02:17
dwmw2_gone joined02:17
sbulage left02:18
denimsoft left02:18
nettoweb left02:18
MattMaker joined02:19
pks joined02:19
Somelauw left02:21
Naan left02:22
armyriad joined02:23
b3kN joined02:27
nunchuck joined02:28
deduped joined02:30
dcy joined02:31
akkad left02:33
nunchuck left02:33
Goplat joined02:33
CheckDavid left02:34
mischat joined02:35
dreiss joined02:35
pur3eval joined02:35
miczac left02:36
akkad joined02:37
redhedded1 left02:37
nunchuck joined02:39
mischat left02:40
pur3eval left02:40
mizu_no_oto joined02:42
levex_ left02:47
Vampire0_ joined02:48
aavrug joined02:50
Vampire0 left02:51
newbie1 left02:52
d^sh left02:53
d^sh joined02:55
ojdo left02:55
durham left02:57
durham joined03:01
flashpoint9 left03:01
ojdo joined03:02
nckpz_ joined03:04
zzz_ joined03:04
zzz left03:04
Vortex34 left03:05
SwiftMatt joined03:05
raijin joined03:08
dRealm joined03:09
ToBeCloud joined03:11
Nilesh_ joined03:11
gitinfo set mode: +v03:11
dRealm So here's what I've done: I wanted to clean up my webpage by moving all images under the root of the site to '/assets/images/'03:12
shgysk8zer0_ left03:12
dRealm after doing that, I did a: git rm '*.jpg'03:13
not knowing that '*' recurses into directories.03:14
I have not committed my work yet03:14
zivester joined03:15
glspi joined03:16
oaao joined03:16
dRealm so.. what end up happening is git rm '*.jpg' deleted the images I just moved to '/assets/images' as well03:16
Vortex34 joined03:17
dRealm Good thing I did do a commit before I fucked up.03:19
Good thing *is*03:19
so, is "git reset" the command I want?03:19
venmx joined03:20
hexagoxel left03:22
dRealm Okay, so it looks like git does have a record of all the deleted files. But here's the message it printed after I typed "git reset"03:23
http://codepad.org/hCLkY6Tn03:23
hexagoxel joined03:25
dRealm Come on boyz. It's 10:25 EST, I know y'all still up.03:25
chachasmooth left03:25
fstd_ joined03:26
chachasmooth joined03:26
fstd left03:30
fstd_fstd03:30
durham left03:31
glspi drealm, i'm completely unqualified to help you....but i think maybe a 'git reset --hard' would do it....not my fault if not though!03:31
durham joined03:31
dRealm glspi: yay03:33
glspi: it came back03:34
glspi nice :)03:34
pur3eval joined03:36
mischat joined03:36
diogenese left03:37
aavrug left03:37
dRealm I can't believe they (or is it Linus) made '*' recurse into directories.03:38
diogenese joined03:40
pur3eval left03:41
mischat left03:41
duderonomy joined03:42
rgrinberg left03:43
Raed|Mobile left03:45
Limes joined03:45
rgrinberg joined03:46
jstimm joined03:46
brent__ joined03:49
BackEndCoder left03:49
BackEndCoder joined03:49
rgrinberg left03:50
raijin left03:52
svm_invictvs joined03:53
mizu_no_oto left03:58
sunri5e left04:00
raijin joined04:00
aidalgol left04:01
inflames joined04:02
Noldorin left04:02
sunri5e joined04:03
jnewt1 joined04:03
brent__ left04:04
durham left04:04
Andrew_K joined04:04
jnewt1 i can't seem to clone anything using http or https , i get Unable to find remote helper for 'https'04:05
. i just updated curl and git based on some answers from SO.04:05
dRealm Okay, I just read git-rm(1). The answer is: if you want to unstage and delete stuff ONLY from the working directory, DON'T ask git to do the expansion; instead let the shell do it.04:05
sarp joined04:06
sarp_ joined04:06
gelei007 left04:06
ozmage joined04:06
jnewt1 here's the updated --version outputs from git and curl: http://pasted.co/1037e7a504:07
dcy left04:10
qguv left04:11
bumpy joined04:12
qguv joined04:13
qguv left04:14
qguv joined04:15
mohabaks joined04:18
LiftLeft left04:19
shgysk8zer0_ joined04:19
sarp_ left04:22
mohabaks left04:23
LiftLeft joined04:25
webbcam joined04:28
ozmage left04:31
webbcam left04:31
raijin left04:32
fstd left04:33
Kaisyu joined04:33
Cabanoss- joined04:34
venmx left04:35
hexagoxel left04:35
mohabaks joined04:36
VladGh joined04:36
_xor joined04:36
pur3eval joined04:37
mischat joined04:37
dcy joined04:37
Cabanossi left04:37
Cabanoss-Cabanossi04:37
hexagoxel joined04:38
fstd joined04:38
Emperor_Earth joined04:39
mohabaks left04:41
mischat left04:42
pur3eval left04:42
svm_invictvs left04:44
svm_invictvs joined04:45
fstd left04:46
fstd joined04:46
endiruna left04:47
matoro left04:47
endiruna joined04:48
matoro joined04:51
xall joined04:52
sword joined04:55
sittingbear joined04:56
madewokherd left04:58
glspi left05:00
acetakwas left05:01
ayogi joined05:01
xall left05:02
matoro left05:02
canuk left05:03
matoro joined05:04
ElGrandeAmigo joined05:07
xlegoman left05:08
zzz_ left05:09
ElGrandeAmigo left05:11
zzz joined05:11
jnewt left05:12
jimklo joined05:12
lmclinskey joined05:12
nckpz_ left05:14
sarp left05:15
ozmage joined05:17
Lunatrius left05:18
Gsham left05:18
sittingbear left05:19
SiliconDon joined05:25
Lunatrius joined05:25
cheater e: thanks, let me look05:26
chipotle left05:26
cheater e: thanks, but that's not it05:27
robotroll left05:28
SiliconDon left05:28
cheater e: oh but actually .. is what i'm looking for05:28
>> For example, origin.. is a shorthand for origin..HEAD and asks "What did I do since I forked from the origin branch?" Similarly, ..origin is a shorthand for HEAD..origin and asks "What did the origin do since I forked from them?"05:29
SiliconDon joined05:29
l4v2 left05:29
ToBeCloud left05:31
shgysk8zer0_ left05:32
vivuroy left05:37
menip left05:38
pur3eval joined05:38
mischat joined05:38
b3kN left05:40
zivester left05:41
matoro left05:41
MineCoins left05:42
pur3eval left05:42
mischat left05:43
ffilozov left05:44
sarri joined05:44
sarri left05:44
sarri joined05:44
nd joined05:44
sbulage joined05:45
nd_ left05:47
gelei007 joined05:48
Groovin left05:48
jameser joined05:49
matoro joined05:50
Groovin joined05:50
Kulrak left05:52
mohabaks joined05:53
zzz left05:55
fstd left06:01
fstd joined06:01
MattMaker left06:01
lmclinskey left06:02
dec0n joined06:02
MattMaker joined06:04
navidr left06:06
MACscr left06:07
mohabaks left06:07
vivuroy joined06:07
SiliconDon left06:08
brent__ joined06:08
MineCoins joined06:08
MACscr joined06:08
jozwior joined06:10
vivuroy left06:12
rscata joined06:16
nunchuck left06:20
deduped left06:20
mohabaks joined06:21
Gloomy joined06:23
basiclaser left06:30
mohabaks left06:31
brent__ left06:32
Guest82 joined06:36
Kulrak joined06:37
Kulrak left06:37
Kulrak joined06:37
ozmage left06:38
pur3eval joined06:38
mischat joined06:39
dersand joined06:41
mischat left06:43
Guest9 left06:43
pur3eval left06:44
_UniFreak joined06:44
overlord_tm joined06:45
robattila256 left06:49
Raging_Hog joined06:50
MattMake_ joined06:50
lordjancso joined06:50
_xor left06:52
ThomasLocke joined06:53
basiclaser joined06:53
MattMaker left06:54
e01 joined06:56
e01 left06:56
e01 joined06:56
Endorphine joined06:57
ISmithers left06:59
Endorphine left06:59
zeroed joined07:01
zeroed left07:01
zeroed joined07:01
wdfwefewvfgew joined07:01
wdfwefewvfgew left07:01
Endorphine joined07:01
Endorphine left07:01
miczac joined07:02
gitinfo set mode: +v07:02
JeroenT joined07:02
vivuroy joined07:04
Arno joined07:04
ihradek joined07:05
lmat joined07:06
zeroed left07:08
vivuroy left07:09
Lunatrius left07:10
ash_workz left07:10
zeroed joined07:10
zeroed left07:10
zeroed joined07:10
watabou left07:13
Guest82 left07:15
lb1c joined07:16
dcy left07:17
afuentes joined07:18
acetakwas joined07:19
dcy joined07:20
Lc0rE_ joined07:20
dan2k3k4 joined07:20
jstimm left07:23
Arno left07:23
freimatz joined07:24
chele joined07:24
santagada joined07:24
Lc0rE_ left07:25
Lc0rE joined07:26
donught left07:27
Lc0rE left07:29
JeroenT left07:32
JeroenT joined07:33
jimklo left07:36
jimklo joined07:37
JeroenT left07:37
F0rTh3J3st_ joined07:38
dcy left07:38
F0rTh3J3st left07:38
dcy joined07:38
pur3eval joined07:39
mda1 joined07:40
jimklo left07:41
mda1_ left07:42
mohabaks joined07:43
bolino1234 joined07:43
bolino1234 left07:43
jimklo joined07:44
pur3eval left07:44
mohabaks left07:45
JeroenT joined07:45
jimklo left07:46
jimklo joined07:47
repozitor joined07:47
svm_invictvs left07:48
MattMake_ left07:48
jimklo left07:49
jimklo joined07:50
repozitor left07:51
Motoko left07:51
mohabaks joined07:52
JeroenT left07:53
algun_ left07:53
ash_workz joined07:54
qt-x joined07:54
jimklo left07:55
jnavila joined07:57
thiago left07:58
kent\n joined07:58
Guest30 left07:59
cqi left08:01
mischat joined08:02
mischat left08:03
blr joined08:03
_ikke_ jnewt1: what does git --exec-path return?08:05
JeroenT joined08:05
dcy left08:05
dcy joined08:06
mohabaks left08:09
visual joined08:11
visual hey guys08:11
ispn joined08:11
visual how do i add a remote git repository to an existing folder08:11
jagob joined08:12
cqi joined08:14
raynold left08:14
_ikke_ visual: git remote add <name> <url>08:14
rajat joined08:14
aidalgol joined08:16
visual and then how do i 'sync' it?08:19
i cant push, i cant pull08:19
this is really frustrating08:19
Prospero_ joined08:19
Dumblez0r joined08:20
visual Updates were rejected because the tip of your current branch is behind hint: its remote counterpart. Integrate the remote changes (e.g.08:20
hint: 'git pull ...') before pushing again08:20
but i *just* pulled it08:20
_ikke_ You have to specify *what* to pull08:20
theoceaniscool joined08:20
AndChat|607476 joined08:20
visual git pull remote origin08:21
error: The following untracked working tree files would be overwritten by merge:08:21
_ikke_ visual: did you call your remote 'remote'?08:22
Prospero_ left08:22
visual my bad, git pull origin master08:22
_ikke_ ok08:22
visual and i t complains about the files08:22
Prospero_ joined08:22
_ikke_ Right08:22
You have untracked files08:22
I mean08:22
uncomitted changes08:22
visual but i cant commit them because it says my branch is behind08:23
_ikke_ You an alway commit08:23
visual -f ?08:23
_ikke_ No need to08:23
just stage them and commit08:23
Prospero_ left08:23
visual i can't man08:23
hint: Updates were rejected because the tip of your current branch is behind08:23
failed to push some refs to..08:23
so cant push and cant pull08:23
_ikke_ That's when you *push* changes08:23
visual what the hell08:23
venmx joined08:24
_ikke_ visual: You are missing one step08:24
visual what step08:24
_ikke_ visual: First make sure everything locally is comitted08:24
Endorphine joined08:24
visual nothing to commit, working directory clean08:24
_ikke_ visual: What does git status return08:24
AndChat-607476 joined08:24
visual same thing, on branch master, nothing to commit, working directory clean08:25
_ikke_ visual: git status --ignored08:25
visual yeah there,s a bunch of ignored files08:25
i added those to gitignore08:26
_ikke_ Right08:26
I suspect that someone started to track one of those files08:26
visual nobody except me uses this repository, i made it yesterday08:26
_ikke_ ok08:26
and git merge origin/master08:26
visual error: The following untracked working tree files would be overwritten by merge:08:27
_ikke_ What is the name of that file08:27
visual Sitemap.xml both fiels08:27
_ikke_ (Is it one of the ignored files)?08:27
visual no08:27
or maybe08:27
wait08:27
http://prntscr.com/e82jve08:28
AndChat|607476 left08:28
visual i dont know where he gets the dev/tests... part08:28
s/part/folders08:28
_ikke_ visual: try git status --ignored -uall08:29
It should also show each file seperately08:29
venmx left08:29
visual it does, there's a lot of them08:29
Endorphine left08:29
jnewt1 left08:29
_ikke_ They are probably covered by your .gitignore file08:30
askb left08:30
visual yeah08:30
_ikke_ Right, so you track them in your remote, but not locally08:31
AndChat-607476 left08:31
visual how?08:31
_ikke_ The merge would have to overwrite the sitemap.xml, which git refuses08:31
visual right so what's the procedure now? i guess i could just delete those files08:32
_ikke_ Yeah, that's the easiest sollution08:32
GT4066 left08:32
visual after i remove them what do i do08:33
_ikke_ Then merge, then untrack those files08:33
visual which git commands08:33
AndChat607476 joined08:33
_ikke_ git merge origin/master08:33
morfin joined08:33
morfin hello08:34
dvdchr joined08:34
_ng joined08:34
dc5ala joined08:34
morfin git stash contains some things which act as commits?08:34
_ikke_ morfin: Yeah, git stash is implemented as a merged between 2 commits (so 3 commits in total)08:34
dreiss left08:35
_ikke_ a merge*08:35
AndChat607476 left08:35
Endorphine joined08:35
BackEndCoder left08:35
BackEndCoder joined08:35
dcy left08:36
fragMental joined08:38
sbulage left08:39
sbulage joined08:39
pur3eval joined08:40
visual fuckin gchristr08:40
removed the folder, gonna start again08:41
_ikke_ ..08:41
visual every time i get to deal with git i wanna kill somebody :^)08:41
morfin he-he i had merge conflict when popped stash08:42
visual yesterday i made the repo, pushed everything, made an archive that i downloaded here at work08:42
why the fuck does it have to be so complicated to sync it if it's the same files08:42
_ikke_ visual: git trying to protect you against loosing changes08:43
that are not tracked08:43
morfin he-he08:43
byte512 joined08:43
visual where did the changes come from if it's the same files i pushed yesterday and nobody touched it08:43
retarded git08:44
morfin you even can cherry-pick removed commit i think08:44
hussam left08:44
pur3eval left08:44
qt-x visual: have you changed the history (rebase) ?08:45
visual no i havent touched it at all08:45
qt-x morfin: try reflog08:45
freimatz left08:45
_ikke_ visual: did you use git add -f sometime?08:46
visual yes08:46
_ikke_ Well, there you go08:46
git add -f tells git to also add ignored files08:46
visual what a retarded feature08:47
i thought it just adds it despite conflicts08:47
Balliad joined08:47
morfin qt-x i remember08:48
something like git cherry-pick ..HEAD@{2}08:48
without knowing actual id of commit08:49
MattMaker joined08:49
jimklo joined08:51
visual http://prntscr.com/e82sm008:51
fuck it08:51
:^)08:51
git pull08:51
then git push and it says it contains work i do not have08:52
if that's not retarded i dont know what is08:52
_ikke_ visual: It's you trying random things without trying to grasp what is happening08:52
especially adding random -f08:52
morfin git pull failed?08:52
visual >remote: GitLab: You are not allowed to force push code to a protected branch on this project08:52
jesus fucking christ08:52
i need a smoke08:52
morfin because there is local uncommited changes08:53
_ikke_ visual: It tells you why it failed08:53
visual i JUST added . and commited it08:53
morfin Gitlab can protect certain branches from push08:53
so you can only go trought merge request08:53
MattMaker left08:54
morfin pull, create branch, commit, push, create merge request, merge08:54
_ikke_ morfin: I don't think it's the case here08:54
Problem is that his remote contains changes he pushed from another repo08:54
he tries to merge locally, but that fails, because he has untracked files that would've been overwritten08:55
Dumblez0r left08:55
_ikke_ And lastly, he uses push -f, overwriting the commits he pushed from the other branch08:55
MonsterKiller left08:55
_ikke_ from the other repo*08:55
jimklo left08:56
Endorphine left08:56
Goplat left08:57
MonsterKiller joined08:57
visual well not exactly08:57
i added some folders to gitignore because they're cache folders, etc08:58
then pushed to the repo08:58
elsevero left08:58
visual now i downloaded the archive from the server (including the cached folders), added the same gitignore to the folder, and am trying to sync with the repo08:58
and failing miserably :^)08:58
Dumblez0r joined08:59
_ikke_ Well, the files *are* tracked in master on your remote08:59
joshszep joined08:59
_ikke_ even if you have them in .gitignore08:59
That's what causing these errors08:59
joshszep left08:59
visual only 2, out of a few hundred08:59
why08:59
*out of a few hundred that are ignored09:00
_ikke_ visual: git add -f, files were already tracked before you ignored them09:00
visual yeah and i did the -remove all from gitignore thing before pushing yesterday09:00
which reflected in the repo as deletion of those files09:01
fuck it, i'll just pull without the cached files09:01
apotry joined09:01
visual wasted 2 hours already on this, not worth it09:02
git kills09:02
thank you for your time :)09:02
_ikke_ visual: It helps to invest into it a bit, so that you understand what happens. Is a lot less frustrating09:03
visual honestly it's just easier to keep backups than use this piece of shit software09:03
JeroenT left09:03
mohabaks joined09:03
visual i've been a dev for a better part of a decade, and *every* *single* time git is involved it's a nightmare09:04
_ikke_ visual: I was helping you trying to solve it, but you were too impatient09:05
jimsio joined09:05
visual i know, appreciate that09:05
*sigh*09:05
JeroenT joined09:05
visual if you have the time, can you guide me through it again?09:05
_ikke_ sure09:05
visual ill give it one last shot09:05
alright09:05
im unpacking an archive taken from the hosting server; repo doesnt contain a few folders that i need ignored, which are added to the .gitignore09:07
miczacmiczac\away09:07
visual that's the situation09:07
_ikke_ is that archive a full repo?09:07
qt-x visual: git fetch; gitk --all ; # see what is wrong with your history09:07
troulouliou_div2 joined09:07
_ikke_ qt-x: this is a working tree issue, not necessarily a history issue09:08
visual _ikke_: it contains all the files from the repo AND a few folders that need to be ignored09:08
_ikke_ ok09:08
dvdchr left09:08
mikecmpbll joined09:08
_ikke_ visual: so now when you do git pull, you get that error message, right?09:08
visual im still unpacking, 1 moment09:09
well actully 2 minutes 20 seconds )09:09
_ikke_ sure09:09
visual i'll have to start with git init09:09
qt-x :D09:09
visual idk why but the .git folder didnt get archived09:10
qt-x git init will create a new tree history09:10
Dumblez0r left09:10
lss8 joined09:10
lss8 left09:10
lss8 joined09:10
qt-x and all push will fail09:11
_ikke_ right09:11
visual well git clone will ignore those folders09:11
dcy joined09:11
visual so theres' no third option09:11
_ikke_ visual: clone, and copy those folders?09:11
visual it's a lot of folders09:11
_ikke_ you can copy over the entire working tree09:12
visual what if i copy everything [unpacked archive] on top of the cloned folder?09:12
_ikke_ Right ^^09:12
visual oh, ok, one moment09:12
and then logically i should just add . and commit ?09:14
the .gitignore should include the folders that are not to be tracked09:15
jagob left09:15
jagob joined09:18
Snugglebash joined09:20
visual so after copying everything on top of the cloned folder, the next step is git add . ?09:20
Shashikant86 joined09:22
blackwind_123 left09:23
mohabaks left09:23
elsevero joined09:24
acetakwas left09:24
blackwind_123 joined09:24
LiftLeft left09:25
dcy left09:25
vivuroy joined09:26
visual :I09:27
Lunatrius joined09:28
Darcidride joined09:30
vivuroy left09:31
miczac\away left09:31
lss8 left09:33
mischat joined09:33
Raging_Frog joined09:34
Shashikant86 left09:34
HurricaneHarry joined09:37
_ikke_ visual: what does git status say?09:37
visual a lot of modified09:37
clemf_ left09:38
visual even files that arent(and shouldnt be) in gitignore09:38
i guess it looks by the date09:38
_ikke_ Only to see if it should check for changes09:39
if git status says modified, it means it has different contents09:39
Snugglebash left09:40
_ikke_ So I expect that what you have cloned is a different commit09:40
sbulage left09:40
_ikke_ visual: do you see ignored files in there?09:40
sbulage joined09:40
_ikke_ (files that should be ignored)09:40
visual 1 moment09:41
pur3eval joined09:41
visual doesnt seem so09:42
j7k6 joined09:43
visual but im not 100%, the git status displayed more files than im able to scroll09:43
Gloomy left09:43
dsdeiz left09:44
achadwick joined09:44
visual well what now? do i add them?09:44
Shashikant86 joined09:44
_ikke_ git ls-files -c -i --exclude-standard09:45
this shows tracked files that would've been ignored09:45
visual yes the same 2 files from before, Sitemap.xml09:45
Snugglebash joined09:45
dsdeiz joined09:45
_ikke_ right09:45
visual i should maybe write these commands somwhere too.. thx about that )09:45
dcy joined09:45
Raging_Frog left09:45
pur3eval left09:46
_ikke_ You only care about the cachefiles from the archive, correct?09:46
mischat_ joined09:46
Serpent7776 joined09:46
visual yeah09:46
hwoarang joined09:47
_ikke_ git checkout HEAD .09:47
(this would overwrite the 2 sitemap.xml files though)09:48
Derperpe1 left09:48
visual alright did that09:48
_ikke_ So now your working tree should be clean again09:48
correct?09:49
visual http://prntscr.com/e83fj809:49
i dont think so09:49
i mean it stil shows in the --exclude-standard c09:49
mischat left09:49
_ikke_ Yeah, that is the next step09:50
acetakwas joined09:50
_ikke_ git rm --cached <sitemap_files>09:50
dcy left09:50
Shashikant86 left09:50
visual alright done09:51
_ikke_ Now you can commit these changes09:51
visual do i do add . first?09:51
_ikke_ No, that's not necessary. Check git status09:51
visual http://prntscr.com/e83gqa09:52
weird, why does it not show all the modified files from before?09:52
dcy joined09:53
visual wew, the push went through09:53
peterR`` left09:53
visual thanks a lot man, appreciate it :^)09:53
now 2 more repos to go, hopefully the same commands will suffice09:53
_ikke_ visual: that's what the git checkout HEAD . command did09:54
dave0x6d left09:55
King_Hual joined09:55
ocbtec joined09:55
visual i see09:55
thank you09:55
what would one need to do in this situation?09:56
http://prntscr.com/e83iag09:56
it complains that they're untracked, but i cant remove them09:56
_ikke_ They are already untracked09:56
you cannot 'untrack' them if they're not being tracked in the first place09:56
if you want them gone, just rm them09:56
(or add them to .gitignore)09:57
visual got it, thanks man09:57
denisMone joined09:58
borkr joined09:58
marcogmonteiro joined09:59
visual *sigh*09:59
in another repo, doing git checkout HEAD . outputs error10:00
error: pathspec '.' did not match any file(s) known to git.10:00
hussam joined10:00
MattMaker joined10:00
visual my bad, wrong folder10:00
mquin_ joined10:01
Shashikant86 joined10:03
Tobbi joined10:04
jozwior left10:04
m4sk1n joined10:04
MattMaker left10:05
askb joined10:05
IntruderSRB joined10:06
dcy left10:06
jozwior joined10:06
nettoweb joined10:07
mquin_ left10:11
mquin_ joined10:12
Shashikant86 left10:12
cqi left10:12
rnsanchez joined10:13
inbx joined10:14
chll_ joined10:14
TomyLobo joined10:14
elsevero_ joined10:15
elsevero left10:16
elsevero_elsevero10:16
bongjovi joined10:16
Tobbi left10:16
ruxu joined10:17
askb left10:19
aidalgol left10:19
Tobbi joined10:19
troulouliou_div2 left10:23
IntruderSRB left10:23
venmx joined10:25
inbx left10:27
dsdeiz left10:27
Gloomy joined10:28
Snugglebash left10:29
gelei007 left10:29
venmx left10:30
mischat_ left10:33
dcy joined10:33
mischat joined10:33
Snugglebash joined10:34
Anticom joined10:35
gelei007 joined10:36
flaviodesousa joined10:39
tvw joined10:40
dwts joined10:40
BooK joined10:40
IntruderSRB joined10:40
inbx joined10:41
vivuroy joined10:41
IntruderSRB left10:41
pur3eval joined10:41
mehola left10:42
mehola joined10:43
mehola left10:43
Derperpe1 joined10:43
ocbtec left10:43
mehola joined10:45
pur3eval left10:46
vivuroy left10:46
johnny56_ joined10:47
Derperpe1 left10:48
johnny56 left10:48
Spherical joined10:49
mehola left10:50
gelei007 left10:51
zeroed left10:51
King_Hual left10:51
Spherical left10:52
vivuroy joined10:53
zeroed joined10:53
zeroed left10:54
dc5ala left10:57
tvw left10:57
vivuroy left10:57
mquin_mquin10:58
vivuroy joined10:58
ozmage joined10:59
inbx left10:59
ferr1 joined11:01
newbie1 joined11:01
geoid_ joined11:01
tvw joined11:02
bvtton joined11:03
_UniFreak left11:06
kent\n left11:10
kent\n joined11:11
ozmage left11:11
_cyril_ joined11:12
IntruderSRB joined11:12
Gravious joined11:13
vivuroy left11:15
IntruderSRB left11:16
jfr joined11:17
miczac\away joined11:17
gitinfo set mode: +v11:18
inbx joined11:18
jameser left11:20
jnewt1 joined11:25
venmx joined11:26
mohabaks joined11:27
jnewt1 left11:30
mohabaks left11:31
inbx left11:32
venmx left11:32
redeemed joined11:33
IntruderSRB joined11:34
Snugglebash left11:35
finalbeta left11:35
finalbeta joined11:36
re1 joined11:36
re1 left11:37
Snugglebash joined11:37
re1 joined11:37
re1 left11:38
wrouesnel1 joined11:38
freimatz joined11:38
dcy left11:38
re1 joined11:38
re1 left11:39
mischat_ joined11:40
re1 joined11:40
re1 left11:40
re1 joined11:41
re1 left11:41
PioneerAxon left11:42
re1 joined11:42
kyan left11:42
pur3eval joined11:42
swalladge left11:42
mischat left11:43
cebor left11:43
re1 left11:43
re1 joined11:44
cebor joined11:45
MattMaker joined11:46
blackwind_123 left11:47
Andrew_K left11:47
pur3eval left11:47
PioneerAxon joined11:47
blackwind_123 joined11:49
Gloomy left11:49
MattMaker left11:51
Dumblez0r joined11:51
SwiftMatt left11:51
LBV_User joined11:52
Tobbi left11:52
NullableTruth left11:53
Rico joined11:53
Rico hi11:53
_ikke_ hello11:53
Rico wan anybody tell me the way to create a repository from a "git clone" directory backup ?11:54
s/wan/can/11:54
ertesx joined11:54
NullableTruth joined11:54
_ikke_ if you have the .git directory, you already have a complete repository11:55
dsdeiz joined11:55
dsdeiz left11:55
dsdeiz joined11:55
gelei007 joined11:56
Rico _ikke_: yes I have it. I've done a "git init --bare repo.git" in my /home/git folder (that's where my git repos are). then I cd in my local copy and do a "git push [email@hidden.address]11:57
ertes left11:57
ertesxertes11:57
Rico is that the correct way to do it ?11:57
_ikke_ Not understanding what you want to achieve with that11:58
Rico oops, did not see that it's lunch time, I'll be back in 1 hour11:58
sorry11:58
BSAlb joined11:58
theoceaniscool left12:00
Tobbi joined12:00
swalladge joined12:01
ruxu left12:02
BSaboia left12:02
mischat_ left12:03
raijin joined12:04
ferr1 left12:07
mischat joined12:07
ferr1 joined12:07
mischat left12:07
Orbitrix left12:07
mischat joined12:07
Orbitrix joined12:08
JeroenT left12:09
deinspan- joined12:09
JeroenT joined12:12
JeroenT left12:13
dsdeiz left12:13
Gloomy joined12:13
gelei007 left12:15
gitinfo set mode: +v12:15
deinspan- Hey folks, could someone help me figure out something I'm doing wrong please? I have a clone of a project begriffs/postgrest. Some time ago I made a pull request for it in a branch named feature/stack-docker-build. I want to update and rebase that patch.12:15
my problem is, I left my local clone of it with some trash so I did a "git reset —hard deinspanjer feature/stack-docker-build" and that looks fine. "git status" says it is clean and up to date.12:15
raijin left12:15
deinspan- next I try to do a "git pull origin master", and it does a rewind and replay, but that leaves me in an unusual state.12:15
sophiag joined12:15
deinspan- after the pull of master, "git status" reports that my branch and deinspanjer/feature/stack-docker-build have diverged. How could they have diverged?12:15
sophiag hi. on here as usual because i did something weird and am freaking out over a lost file :(12:16
my situation is i seem to have too instances of git...one in the outer project folder and one in an inner src directory12:17
JeroenT joined12:17
JeroenT left12:17
sophiag i tried committing and pushing my change and it overwrote *everything* except what was in the inner src directory12:17
so i did a hard reset back one commit and pushed that12:18
JeroenT joined12:18
YuGiOhJCJ joined12:18
sophiag now the file in question is back to some really *really* old version12:18
reflog obviously allows me to see everything, but i can't seem to be able to just open the version i saved by resetting it back12:18
can anyone help me troubleshoot this?12:18
the outer instance of git is clearly the correct one12:21
i think i just need to figure out how to pull the file i saved this morning from the inner instance from the commit i see in reflog and can't seem to figure out how to do that :(12:21
theoceaniscool joined12:22
alexandre9099 left12:22
deinspan- @sophiag did you try diffing or reseting that file when you were in the directory where your nested .git exists?12:22
sophiag yes12:23
ash_workz left12:23
deinspan- @sophiag when you end up with nested .git folders, the git commands use the first one they find starting at the current working directory and going up.12:23
sophiag the problem seems to be i did a hard reset in the nested .git and htat brought it way back several months12:23
deinspan- oh, so the nested one is the old one?12:23
sophiag yes12:24
treia joined12:24
deinspan- hmm12:24
sophiag except that was where i committed the file i'm trying to recover12:24
deinspan- and before the reset, had you ever done a commit of the file?12:24
sophiag no12:24
deinspan- hmm12:24
sophiag what's confusing me is why i can't just reset the inner .git to after i committed that file and copy it12:25
right now the outer one is correct except for that file...which is very very old12:25
salamanderrake left12:25
deinspan- wait, but you just said you hadn't committed it12:25
sophiag you asked if i reset it12:26
tsdev joined12:26
deinspan- okay, let me ask something different.. are there *any* changes you made to that file that would be lost if you just blew everything away and worked with only the repo that is in the outer .git?12:26
sophiag yes12:26
that's my problem12:26
deinspan- okay.12:27
sophiag and right now i have the outer git pushed to remote and it's displaying the super old version of that one file12:27
what i need is to just recover it from the inner .git12:27
then copy it and commit to the outer one12:27
alexandre9099 joined12:27
deinspan- so at some point, you made changes to the file, you committed those changes to the inner .git repo, and then you did a reset of the inner .git, right?12:27
sophiag yes12:27
but i can see everything in reflog obviously12:27
deinspan- what does "git fsck —lost-found" tell you?12:28
sophiag in the inner one?12:28
deinspan- yes12:28
sophiag i have three dangling blobs12:28
deinspan- we need to deal exclusively in the inner one until we get that file back since the outer doesn't have the changes you need12:28
sophiag yes12:28
deinspan- how far back did you reset? multiple commits or just one?12:29
sophiag just one12:29
waveclaw left12:29
sophiag but then tried resetting it forward once as well12:29
deinspan- ew12:29
so can you see the SHA1 of the commit you want in "git reflog"?12:29
sophiag yeah...from my bad troubleshooting the commit i actually need is 3 right now12:29
the one i need is HEAD@{3}12:30
JeroenT left12:30
sophiag for that one file12:30
JeroenT joined12:30
waveclaw joined12:30
deinspan- okay, so try "git merge <SHA1>" of head 312:30
sophiag but i already tried resetting to that12:30
and that screwed it up wrose12:30
oh ok12:30
lemme see12:30
eroux joined12:30
jab416171 joined12:31
sophiag it says already up to date...12:31
_ikke_ ls12:31
Bizkit left12:31
sophiag i did ls and cat and it's the super old file tho...12:32
deinspan- hmm.. so either the second reset you did put you in a state I don't understand, or the SHA1 you used is actually the old version...12:32
try deleting the file and then doing the merge again?12:32
sophiag already up to date...12:33
ChiLL_SurF joined12:33
netj left12:33
netj joined12:33
sophiag altho now the file is gone12:34
don't i need to commit after merging12:34
?12:34
l4v2 joined12:34
sophiag like i deleted it, merged again, now it's still gone12:34
deinspan- after the merge, you should have the file in your current working state which is all you need12:34
okay, try doing just a checkout of that SHA1 instead12:34
sophiag :D12:35
rajat left12:35
deinspan- good12:35
nowhereman left12:35
deinspan- So are you sure this is the only file you care about from this inner .git?12:35
nowhereman joined12:36
deinspan- And your team isn't doing anything with git subtrees or git submodules?12:36
JeroenT left12:36
sophiag yes. if i could just swap this with the one that's currently in my remote i'd be golden12:36
JeroenT joined12:36
eroux left12:37
sophiag altho i have a ton of old formerly deleted junk in that folder too12:37
deinspan- If yes to the second question as well, then what I would recommend is doing a mv of that inner .git to some safe out of the way place just in case12:37
when the inner .git isn't there any more, the outer one will be in charge again12:37
JeroenT left12:38
deinspan- as soon as the inner is gone, you should be able to do a git status and see that one file is waiting for an add12:38
eroux joined12:38
sophiag hmmm12:38
ok. i copied it to a gist anyway to be safe12:38
deinspan- of course. :)12:38
Groovin left12:39
deinspan-deinspanjer12:39
l4v2 left12:39
sophiag ok moved it12:40
and status in the right one has it waiting for me12:40
deinspanjer and git diff still shows it being the changes you want?12:40
JeroenT joined12:40
sophiag yes12:41
deinspanjer then commit that and you should be good to go. If everything continues to look good after a while, you can throw away that spurious .git folder.12:41
sophiag but i should probably roll back one commit in the outer git?12:41
deinspanjer ah12:41
sophiag there was one stupid one made12:41
deinspanjer So in this git, you have a commit of the old version?12:41
sophiag yes12:41
i think i should reset back one and manually copy it?12:42
deinspanjer one sec12:42
have you pushed that change?12:42
the one with the bad version?12:42
sophiag yes12:42
deinspanjer hum12:42
sophiag i think best to act like i never edited the file and then paste it in12:43
deinspanjer so a revert is basically just a new commit of an older version with a fancy message.12:43
sophiag frankly12:43
pur3eval joined12:43
sophiag yup12:43
deinspanjer since you pushed, that bad commit will still be in people's history12:43
sophiag but really really old12:43
people is just me12:43
deinspanjer So I'd just commit the new version with the same explanatory message12:43
sophiag yeah you're right12:44
Derperpe1 joined12:44
sophiag btw the shitty old files are there12:44
just untracked12:44
i suppose i can rm them12:44
deinspanjer If you hadn't pushed, then you could do a git commit —amend instead, but oh well. :)12:44
after you commit that important file, you can just do a git clean -fd12:45
visual left12:45
Tobbi left12:46
vivuroy joined12:47
salamanderrake joined12:47
m4sk1n left12:47
F0rTh3J3st joined12:47
F0rTh3J3st_ left12:47
mischat left12:47
mischat joined12:48
pur3eval left12:48
mischat left12:48
deinspanjer Now then.. back to my problem I have to figure out. :)12:48
sophiag haha12:49
thanks so much12:49
tbh i only come on this channel in panic mode12:49
deinspanjer Very happy to pay it forward.12:49
Same here.12:49
sophiag i should try to learn more and then come here and help out12:49
deinspanjer well, right now I'm not panicing, just annoyed12:49
JeroenT left12:49
deinspanjer stackoverflow is a goldmine for learning the inner mysteries of git12:50
JeroenT joined12:50
Derperpe1 left12:51
vivuroy left12:51
mischat joined12:51
nowhereman left12:53
sophiag i always feel like i know it until things go wrong :/12:53
tobiasvl you'll get the hang of it12:54
sophiag mainly i did stupid things when i started out that carried over12:54
like moving directories the wrong way12:54
that's a huge one12:54
al-damiri joined12:54
Rr4sT joined12:55
Somelauw joined12:58
str_ joined12:58
JeroenT left12:58
Rico _ikke_: hi again12:59
re1 left12:59
Somelauw Am I bit disoriented by rebasing. When in an interactive rebase, does head refer to the commit I'm editing or the HEAD of not rebasing?12:59
str_ left12:59
str joined12:59
_ikke_ Somelauw: You mean in case of a merge conflict?12:59
Somelauw no, if just doing 'edit'13:00
_ikke_ HEAD is then the commit you want to edit13:00
Somelauw then i don't know where i am, because git log shows the full tree of commits13:00
inbx joined13:01
Somelauw even though i thought i would be editing an old one13:01
netj left13:01
plos joined13:01
netj joined13:02
Rico somebody sent me a .tgz containing a local copy of a git repo. I need to create a repo from this tgz. I have "git push" to an empty repository (created with git init --bare). when I wan to clone this repo, I have the following error :13:03
warning: remote HEAD refers to nonexistent ref, unable to checkout.13:03
Somelauw okay, i'll abort the rebase and start again. I want to edit commit C, so I start by doing git rebase -i C; then replacing the line by 'edit'13:03
then when i press git lg, I see my full commit history13:04
ayogi left13:06
tobiasvl Rico: if the .tgz contains a git repo, why do you need to create a repo from it?13:06
Somelauw okay, i now understand i should have done "git rebase -i C~", so the ~ is important13:06
JeroenT joined13:07
Rico tobiasvl: because I need to work on this repository, apply bundles to it, create diffs, keep an history, ...13:07
tobiasvl Somelauw: yes, you want to rebase ONTO the base, which is C~ (the parent of C)13:07
Rico: I still don't understand. if the .tgz file contains a git repo, you can do all of that without creating a new repo.13:07
Rico other people have to work on this copy and get copies of that13:08
Wind0r joined13:09
Rico tobiasvl: is this the right way ? http://fpaste.scsys.co.uk/55199813:09
JeroenT left13:10
cousteau joined13:11
JeroenT joined13:11
tobiasvl Rico: that looks OK, but the only branch you pushed to [email@hidden.address] was 13.9.1-ambe-edmr? is HEAD supposed to be that?13:11
Rico tobiasvl: yes13:11
I think I'm missing a step13:12
cousteau a branch is just a pointer (head) in the commit tree, right? Not quite like a physical tree branch (i.e. a *set* of commits made while on a certain branch)13:12
tobiasvl Rico: run "git symbolic-ref HEAD refs/head/13.9.1-ambe-edmr" inside asterisk-ambe-full.git13:12
selckin !compsci13:13
cousteau or do commits "know" which branch they belong?13:13
tobiasvl cousteau: correct, a branch is a pointer to a ref. it's not a physical tree branch in itself, but by traversing the ref's parents it kind of is one13:13
selckin cousteau: !cs13:13
gitinfo cousteau: "Git for Computer Scientists" is a quick introduction to git internals for people who are not scared by phrases like Directed Acyclic Graph. http://eagain.net/articles/git-for-computer-scientists/ See also !concepts !bottomup13:13
_ikke_ cousteau: nope13:13
Rico tobiasvl: in the "git clone" copy (/usr/local/src/...à ?13:13
_ikke_ cousteau: a commit can be seen from numerous branches13:13
cousteau I see13:13
thanks!13:13
jeffreylevesque_ left13:13
ash_workz joined13:13
cousteau (I'm no computer scientist but thanks for the link)13:14
GodGinrai joined13:14
_ikke_ cousteau: You don't really need to be one13:14
tobiasvl Rico: no, in /home/git/asterisk-ambe-full.git13:14
Rico ok13:14
cousteau (well, I'm the kind of non-computer scientist who may get scared by words like "Directed Acyclic Graph"...)13:14
_ikke_ Sounds more complicated than it really is13:14
cousteau ok if "Directed Acyclic Graph" is the strongest word I'm going to find then ok13:14
e it doesn't sound complicated13:15
cousteau I mean, I know what that is13:15
Somelauw tobiasvl: thanks, do professional git users rebase their commits all the time or do they just let them be?13:15
_ikke_ commits are nodes on a graph13:15
Rico tobiasvl: still have the same warning, and onli have '.git' folder after cloning13:15
codedmart joined13:15
_ikke_ the edges are the references to the parent(s) of commits13:15
e anyway, the point i suppose is that there is a set of commits, but it depends only on where the branch points13:16
commits don't know which branch they "belong to"13:16
Somelauw: it varies. i rebase all the time13:16
cousteau tries to read § "Storage" and gets discomforted by the UML-like charts... let's see if § "History" is friendlier13:16
e some people hate merge commits (which are the alternative, generally speaking) and some people for some reason really like them13:16
tobiasvl Rico: what does "git rev-parse HEAD" say inside the bare repo?13:16
gpkfr joined13:17
sophiag left13:17
cousteau e: thanks, I somehow was expecting that when I made the branch "change this", it'd somewhat be a "group of related commits"13:17
Rico tobiasvl: http://fpaste.scsys.co.uk/55199913:17
santagada left13:18
miczac\awaymiczac13:18
tobiasvl Rico: that doesn't seem right. that's, like, an infinite loop. what about "git rev-prase 13.9.1-ambe-edmr"13:19
Rico d0fa05b9e0af303c94b9064da0782a6932d4bcac13:20
marcogmonteiro left13:20
Rico tobiasvl: ^13:20
tobiasvl Rico: oof, sorry. "git symbolic-ref HEAD refs/heads/13.9.1-ambe-edmr"13:20
should work. I had refs/head instead of refs/heads.13:21
CheckDavid joined13:21
cousteau I had seen git tree charts that used different colors for different ramifications. I thought that represented different branches, but I guess that was actually different authors.13:21
Gloomy left13:21
e you can visualise a concept a bit like branches13:22
Rico tobiasvl: thank you ! can you explain me what was wrong / what I did wrong ?13:22
jameser joined13:22
tobiasvl Rico: by default, HEAD points to master, at least it seems like it from man git-symbolic-ref. you do not have a master branch, so you had to tell git that you had your own, non-standard default branch13:25
gitinfo Rico: the git-symbolic-ref manpage is available at http://jk.gs/git-symbolic-ref.html13:25
Gloomy joined13:25
Rico tobiasvl: so a "git clone [email@hidden.address] -b 13.9.1-ambe-edmr" would have work ?13:26
mozzarel1 joined13:26
Rico (not sure about the "would have work" ...)13:26
puff` joined13:27
tobiasvl Rico: that would probably have worked (but is cumbersome to do every time someone wants to clone)13:28
venmx joined13:28
Rico ok13:28
thank you13:28
ronskisika joined13:28
IntruderSRB left13:29
jtfidje joined13:29
boshhead_ joined13:29
tanuki_ joined13:30
Jan- joined13:30
BinGOs_ joined13:30
Renter_ joined13:30
milki_ joined13:30
hegge joined13:30
vals_ joined13:30
arand_ joined13:30
gusnan_ joined13:30
maxb_ joined13:30
timewalk1r joined13:30
GodGinra1 joined13:30
RichiH_ joined13:30
jj-_ joined13:30
Ariadeno joined13:30
Ramen_ joined13:30
DistantS1ar joined13:30
Gaga joined13:30
CEnnis91 joined13:30
ec\_ joined13:31
tier2villain_ joined13:31
INSANU_ joined13:31
tazle__ joined13:31
KMaia2 joined13:31
mikap joined13:31
chll__ joined13:31
beuker_ joined13:31
timewalk1r left13:31
timewalk1r joined13:31
timewalk1r left13:32
GT4066 joined13:32
Ramen left13:32
tazle_ left13:32
Juri_Agarin left13:32
KekSi left13:32
maxb left13:32
covey left13:32
danielmahon left13:32
arunpyasi left13:32
SCHAAP137 left13:32
timewalk1r joined13:32
JeroenT left13:32
mozzarella left13:32
Karazhan left13:32
Nilesh_ left13:32
tanuki left13:32
chll_ left13:32
imMute joined13:32
GodGinrai left13:32
beuker left13:32
arunpyasi joined13:32
ajpiano_ joined13:32
imMute left13:32
imMute joined13:32
mikapmika13:32
mozzarel1mozzarella13:32
PasiFist_ joined13:32
hide joined13:32
parasite_ joined13:32
ollien joined13:32
Jupelius_ joined13:32
ngladitz joined13:32
ngladitz left13:32
ngladitz joined13:32
Snugglebash left13:32
venmx left13:32
Karazhan joined13:32
cwillu_at_work joined13:32
madknight joined13:32
rt joined13:33
Snugglebash joined13:33
ddavidd joined13:34
jeffreylevesque joined13:34
JeroenT joined13:34
Perspicaciosity joined13:35
tonyj joined13:35
Ranhir left13:35
ismithers joined13:36
Raging_Hog left13:36
Ranhir joined13:36
esc joined13:37
rajat joined13:37
marcogmonteiro joined13:38
Impaloo joined13:41
qt-x left13:41
SCHAAP137 joined13:42
pur3eval joined13:44
vivuroy joined13:45
MattMaker joined13:47
pur3eval left13:48
timewalk1r left13:49
BinGOs_ left13:49
timewalker joined13:49
vivuroy left13:49
BinGOs joined13:50
MattMaker left13:51
IntruderSRB joined13:51
plasticle left13:52
jfr left13:52
jfr joined13:54
dikiaap left13:55
mizu_no_oto joined13:55
skered joined13:57
overlord_tm left13:58
alexandre9099 left14:00
vivuroy joined14:00
alexandre9099 joined14:00
theoceaniscool left14:01
BSab joined14:01
algun_ joined14:01
finalbeta left14:01
_xor joined14:02
finalbeta joined14:02
theoceaniscool joined14:02
BSab left14:02
rajat left14:03
nickabbey joined14:03
BSab joined14:03
Eryn_1983_FL joined14:04
BSAlb left14:05
Joel joined14:05
Joel does anyone know of/have a link to/thoughts on - how to handle a change log in git? it's like a non stop conflict factory14:05
ubuntu_ left14:06
cdg joined14:06
raijin joined14:06
gpkfr left14:06
averell joined14:06
cdg left14:06
plasticle joined14:07
Taikibansei left14:07
cdg joined14:07
masuberu joined14:07
tsdev left14:08
cdg left14:08
cdown left14:08
tsdev joined14:08
Taikibansei joined14:08
ubuntu joined14:08
cdg joined14:08
gpkfr joined14:08
ubuntuGuest7960914:09
jameser_ joined14:09
gitinfo set mode: +v14:10
jameser left14:12
RichiH_RichiH14:15
qqx joined14:15
Snugglebash left14:17
xall joined14:17
raijin left14:18
raijin joined14:18
WayToDoor joined14:20
_xor left14:20
ikelso joined14:20
INSANU_ left14:20
cdg left14:20
Snugglebash joined14:20
cdg joined14:21
raijin left14:21
raijin joined14:21
cdg_ joined14:22
Wulf left14:22
raijin left14:22
ddavidd left14:22
ddavidd joined14:22
ddavidd left14:22
ddavidd joined14:22
WayToDoor left14:22
raijin joined14:22
raijin left14:23
raijin joined14:23
cdg_ left14:23
basdb joined14:23
ShekharReddy joined14:25
cdg left14:26
raijin left14:26
reliability joined14:26
raijin joined14:26
cdg joined14:27
HedgeMage Joel: Most of my projects do the Changelog at release time, rather than per commit, and generate it from commit messages between that release and the previous (with a chance for human to edit)14:27
cdg_ joined14:28
HedgeMage Joel: Of course, this means that if your team writes shitty commit messages, you have to cane them until they cooperate.14:28
IntruderSRB left14:28
gpkfr left14:28
venmx joined14:28
marcogmonteiro left14:28
basdb left14:28
mischat_ joined14:29
skered When merging from another branch that has N number of commits does git rollup all those commits on the merge or would you see N number of extra commits when looking at the log?14:29
mischat_ left14:29
_ikke_ skered: git just creates a new commit tying both branches together14:30
mizu_no_oto left14:30
Joel HedgeMage, either way you have to deal with shitty commit messages :)14:30
mischat_ joined14:30
raijin left14:30
raijin joined14:30
Joel generating was what I was looking at, wasn't sure if there some magical other way people have come up with14:31
cdg left14:31
wrouesnel1 left14:32
Taikibansei left14:33
mischat left14:33
raijin left14:33
sbeller joined14:33
raijin joined14:33
venmx left14:34
mischat_ left14:34
HedgeMage Joel: Other projects I've been on have tried other methods, but nothing that's excited me, especially since you always end up having to human-edit before release anyhow: the important bit is not missing anything you might want to include or should be telling users about.14:34
chipotle joined14:34
mischat joined14:34
Wulf joined14:35
Joel HedgeMage, Yeah, I have a group of dev's who don't understand the difference between an internal changelog, and an external changelog. They scream against automating it, but it doesn't go public. I think public facing should be made by hand off of tickets. They also want one entry per commit, which is funny, because git already has a pretty list...14:35
ShekharReddy left14:35
Gloomy left14:35
HedgeMage facepalms.14:36
gpkfr joined14:36
HedgeMage Your internal changelog should be "git log" ....if that isn't working for you, your devteam needs training in how to handle commit messages.14:36
ResidentBiscuit joined14:36
Joel "Yeah but people don't write good commit messages!" - and you think they will do a better job when they duplicate it into a changelog?14:36
Murrito left14:36
HedgeMage So, this is where I say something horrible and politically incorrect and mean.14:37
Murr joined14:37
wrouesnel1 joined14:37
_ikke_ HedgeMage: Usually a commit log is a bit higher level than each commit message14:37
Joel what's a commit log?14:37
^not a troll question, seriously, do you mean change log?14:38
_ikke_ yes. I meant a change log14:38
Joel _ikke_, when externally facing, I agree, an internal log for other dev's to follow though?14:38
I think for higher level that's why you include an issue #.14:38
raijin left14:38
HedgeMage When the lead dev and/or software security lead (my usual roles) is a cute but slightly scary 34yo female hacker with a tendency to thwart people with things like pre-receive hooks that reject commits that are >10% profanity, or >5% punctuation, or < 3 words... people tend to behave eventually.14:39
raijin joined14:39
thethorongil joined14:39
mindfart left14:39
armyriad left14:40
HedgeMage "this commit is not tagged as a security patch and lacks a reference to our public issue tracker, cannot accept"14:40
armyriad joined14:40
_ikke_ Well, the log is as usefull as its commit messages14:40
HedgeMage Joel: If you can train them to write in the changelog like grownups, you can train them to write commit messages like grownups.14:41
Derperpe1 joined14:41
HedgeMage Starting by showing them that you are reducing their workload through automation is a good thing.14:41
reliability Hi. Why does git-flow suggest deleting release branches? What about fixes that need to be backported to older releases?14:41
nettoweb left14:42
nettoweb1 joined14:42
IntruderSRB joined14:42
_ikke_ reliability: That's what you have tags for14:42
Gsham joined14:42
thorongil joined14:42
thorongil left14:42
_ikke_ You can just create a new branch starting from a specific tag14:42
eroux left14:43
Joel people can put crap onto a branch that's never been released14:43
another good reason to use tags14:43
_ikke_ right14:43
That's why I never understood svn's tag model14:44
raijin left14:44
elsevero_ joined14:44
F0rTh3J3st_ joined14:44
Murrito joined14:44
tsdev_ joined14:44
pur3eval joined14:44
JanC_ joined14:45
marcogmonteiro joined14:45
reliability _ikke_, Joel: true, thanks for your answers.14:45
tsdev left14:45
elsevero left14:45
F0rTh3J3st left14:45
mikecmpbll left14:45
nikivi left14:45
elsevero_elsevero14:45
mikecmpb_ joined14:45
canuk joined14:45
JanC left14:46
eroux joined14:46
ugglan joined14:46
Derperpe1 left14:46
Tanfrieze joined14:46
JanC_JanC14:46
Murr left14:47
SporkWitch joined14:48
nikivi joined14:48
MuffinMedic joined14:48
daynaskully joined14:48
Joel left14:48
pur3eval left14:49
mizu_no_oto joined14:50
cdown joined14:50
plos left14:50
reynierpm joined14:50
reynierpm hi there, let's suppose I am on a branch "branch1" and I want to checkout a file from "branch2" the right way to do it is git checkout branch2 path/to/file.ext, if I want to checkout all the file under /path/to the right command should be git checkout branch2 path/to/* ??14:51
jameser_ left14:52
shinnya joined14:53
jimi_ joined14:53
_ikke_ reynierpm: no need for an asterisk14:53
reynierpm _ikke_, good thx14:54
_ikke_ reynierpm: checking out a directory equals to checking out all the files in there (recursively)14:54
dcy joined14:54
gpkfr left14:54
Dougie187 joined14:54
skered left14:55
Gloomy joined14:57
rgrinberg joined14:57
Intruder_ joined14:58
reynierpm _ikke_, ummm I am doing something wrong: `git checkout esd /application/views/scripts/company/` ==> "fatal: ambiguous argument 'esd': both revision and filename Use '--' to separate paths from revisions"14:58
rscata left14:58
_ikke_ git checkout esd -- /application/..14:59
Snugglebash left14:59
dec0n left14:59
reynierpm _ikke_, is complaining about the path it says doesn't exists how do I find the right path?14:59
mischat_ joined15:00
_ikke_ reynierpm: git ls-tree -r esd15:00
IntruderSRB left15:00
mohabaks joined15:00
mischat_ left15:00
skered joined15:00
ocbtec joined15:00
cousteau left15:00
noecc joined15:01
mischat_ joined15:01
uwe joined15:01
e14 joined15:01
miczac left15:02
marcogmonteiro left15:03
gitinfo set mode: +v15:03
gitinfo set mode: +v15:03
reynierpm _ikke_, thx it works15:03
uwe greetings, I'm seeking advise on getting code that has not been maintained in git in sync with a vanilla version of that software (roundcube) ... my question is very generic, and maybe this is the wrong place to ask, so please enlighten me15:03
mischat left15:03
Intruder_ left15:05
miczac\away joined15:06
ismithers left15:06
gitinfo set mode: +v15:07
miczac\awaymiczac15:07
btyne79 joined15:07
IntruderSRB joined15:07
ferr1 left15:07
_ikke_ uwe: not maintained in what sense?15:08
LeBlaaanc joined15:09
marcogmonteiro joined15:10
AaronMT joined15:10
masuberu left15:10
xissburg left15:11
mohabaks left15:12
_ADN_ joined15:13
d1z left15:15
xissburg joined15:16
Remramm left15:17
Remramm joined15:17
Remramm left15:17
Remramm joined15:17
str left15:17
sbulage left15:18
dendazen joined15:18
IntruderSRB left15:18
IntruderSRB joined15:18
jj-_ left15:19
str joined15:20
mischat_ left15:20
mischat joined15:20
IntruderSRB left15:22
uwe _ikke_: i mean was not in any versioning system15:23
King_Hual joined15:23
dcy left15:23
Dumblez0r left15:23
sostenuto joined15:24
IntruderSRB joined15:25
mizu_no_oto left15:25
uwe i.e.; I imagine something along the lines of finding the closest version by looking up version or date, then fetch the whole code, and roll back to that version, fork, add the new code, and go one commit at a time checking the changes with vanilla somehow getting the changes from there to the fork until I'm at head ... then try to encapsulate those changes in lets say a skin or module if possible ...15:27
staafl joined15:27
staafl Does the recursive merge strategy consider intermediate commits or is it just base/ours/theirs?15:28
Tobbi joined15:28
jj- joined15:28
qqx staafl: Just base/ours/theirs.15:28
ToBeCloud joined15:28
gitinfo set mode: +v15:28
Gravious left15:29
staafl qqx, doesn't sound very recursive to me :-)15:29
dikiaap joined15:29
qqx It's recursive with respect to the trees being merged, not history.15:29
moritz it's job isn't to sound recursive :-)15:30
axilaris joined15:30
axilaris hi.... anyone can tell me how to force a merge from master to a branch ?15:30
moritz axilaris: git checkout yourbranch; git merge --no-ff master15:31
axilaris master overwrites everything on the branch15:31
ok thanks @moritz15:31
moritz axilaris: that doesn't override; it just merges15:31
axilaris how can i override ?15:31
jagob left15:31
kba So this seems to hapen quite often. I have two branches, master and devel. They were both at commit X. Then I create a commit on devel Y and push it. Now the branch is at Y.15:31
moritz axilaris: why not just start a new branch?15:32
Noldorin joined15:32
kba Then I switch to master, chery-pick Y and push Y, but now master is at Z.15:32
d1z joined15:32
axilaris i prefer to maintain this branch for the customer15:32
kba master and devel were both at X. I pushed Y to both of them. Now they're not on the same commit. What's happening?15:32
https://github.com/Webstrates/Webstrates/commits/devel and https://github.com/Webstrates/Webstrates/commits/master15:33
axilaris otherwise its confusing, so much has been done on master, i dont care the merge, just want to override master to the branch and make the config changes15:33
kba Why is that happening?15:33
Does that make sense? Am I misunderstanding something?15:34
vibhavp joined15:34
axilaris @moritz you know how to do the override ?15:34
miczac left15:34
miczac joined15:35
KMaia2 left15:35
jast kba: cherry-picking copies commits and, in the process, creates a new committer/commit time entry, so the resulting commit ID is different even if the diff is exactly identical15:35
axilaris git checkout dev_branch, git reset --hard master ?15:35
gitinfo set mode: +v15:35
Gravious joined15:35
kba jast: I see! So what's the correct way to do it?15:35
If I don't want the branches to diverge15:35
moritz kba: merge15:35
jast kba: well, if both branches were identical before, you can use 'git merge'15:36
merge will automatically 'fast forward' (make the branch identical) the target branch is still at the base version15:36
moritz axilaris: after a git reset, you have to push with --force, which won't preserve history15:36
jast *if the target branch15:36
moritz axilaris: so that's basically the same as deleting the branch, and starting a new branch with the same name as before15:37
axilaris @moritz oh thats not good15:37
djh joined15:37
kba Won't that create an ugly commit with "Merge branch" commit message?15:37
Or can I just change that to the other commit messages, and both branches will look identical again?15:37
jast that's if the target branch has had new commits in the meantime15:37
kba Ah, otherwise not? Great15:37
jast if you're not sure, you can use --ff-only to make it abort if fast-forwarding is impossible15:37
moritz axilaris: you can git checkout otherbranch; git checkout master .; git commit -m 'bring files to the state of the master branch' # or something along those lines15:38
kba That's perfect! Thanks, moritz and jast15:38
gugah joined15:38
jast anyway, now that you've already pushed the cherry-picked commit, the only way to get the two branches identical again is to rewrite history, using force push15:38
gugah left15:38
moritz or to merge them, and have the nearly identical commits twice in the history15:38
al-damiri left15:38
jast technically you can get them identical using a merge commit, but I got the impression you'd rather avoid that15:38
gugah joined15:38
patarr joined15:39
Electrometro left15:39
IntruderSRB left15:41
IntruderSRB joined15:42
Gravious left15:43
Gloomy left15:45
mischat_ joined15:45
pur3eval joined15:45
mischat_ left15:46
mischat_ joined15:46
mischat left15:46
TheDcoder joined15:47
cdown left15:47
TheDcoder Hi, how do I sign existing commits and tags?15:47
MattMaker joined15:47
cdown joined15:47
pur3eval left15:50
elsevero left15:50
shgysk8zer0_ joined15:51
e14 left15:51
MattMaker left15:52
moritz TheDcoder: if it happens to be the newest commit, and not yet pushed, probably with git commit --amend15:53
git commit --amed --gpg-sign15:53
TheDcoder no, its neither the newest nor un-pushed15:53
actually, I was planning to sign ALL of my commits15:54
moritz TheDcoder: then signing amounts to rewriting history, afaict15:54
Murii joined15:54
moritz somebody please correct me if I'm wrong15:54
dreiss joined15:54
morfin when unreachable nodes are removed?15:55
TheDcoder hmm...15:55
morfin only when you manually start gc?15:55
redeemed left15:55
_ikke_ morfin: unreferenced objects are not removed before 14 days, and the reflog keeps a reference for 90 days15:55
morfin: some git commands automatically run gc15:55
Gravious joined15:55
peeps[lappy] left15:58
IntruderSRB left15:58
gpkfr joined15:58
morfin hmm15:59
mischat joined16:00
gpkfr left16:00
TheDcoder left16:00
_ikke_ TheDcoder: Note that signing each commit has not much added benefit than signing a tag16:01
gpkfr joined16:01
gpkfr left16:01
lb1c left16:02
gpkfr joined16:02
gpkfr left16:02
rewt left16:02
rewt`` joined16:02
rewt``rewt16:03
mischat_ left16:03
gpkfr joined16:03
gpkfr left16:03
timvisher is there any way to disable a remote for fetch/push purposes but to keep it for historical reference?16:04
Snugglebash joined16:04
Snugglebash left16:04
perlpilot timvisher: you could rename it so that it's not easy to use.16:05
lss8 joined16:06
lss8 left16:06
lss8 joined16:06
inflames left16:06
BlessJah _ikke_: no benefit from end-user perspective, there are certain scenarios though where you might not want to truct code you downloaded from server unless signed16:06
gpkfr joined16:07
amagawdd joined16:07
BlessJah timvisher: remotes are tied to particular clone (i.e. it exists only on your hard drive)16:07
j7k6 left16:07
morfin i created second commit, reset --hard, then changed file, commited again and checked reflog16:08
BlessJah timvisher: you might go to $REPOSITORY/.git/config and comment-out certain lines, it's pointless though - it's better to keep such information somwhere under doc/ if it's important16:08
Murii left16:08
thethorongil left16:09
morfin it was looking like Initial -> second -> reset: moving to HEAD~1 -> third(which is second again)16:09
mischat left16:10
_ikke_ BlessJah: If the tag is signed, it covers the commits16:10
Murii joined16:10
mischat joined16:10
BlessJah _ikke_: are you sure that tag~ is ok to be signed? :>16:11
ThomasLocke left16:11
boshhead_boshhead16:11
gugah left16:12
Peetz0r joined16:12
bvtton left16:12
_ikke_ ok in what sense?16:12
zivester joined16:13
btyne79 left16:13
JeroenT left16:14
Derperpe1 joined16:15
vals_tango_16:15
inbx left16:16
tribly joined16:16
BlessJah _ikke_: malicious root user, some lines slipped in during rebase, server-side merges or rebases, "please apply this patch" sociotechnic16:17
raijin joined16:18
Raed|Mobile joined16:19
mrVandermare joined16:20
_ikke_ BlessJah: Then a signed commit is not going to help you too16:20
At least, not going to guarantee that something has slipped in16:20
dcy joined16:20
_ikke_ has not*16:20
uwe left16:21
Nilesh_ joined16:21
ronskisika left16:21
_ikke_ rebases necessitate resigning of commits, and I doubt everyone is examining what they sign closely16:21
IntruderSRB joined16:21
gpkfr left16:22
BlessJah yeah, rebase isn't best example16:22
_ikke_ a gpg signature means that the commit came from someone, not that what they signed is benign16:23
lordjancso left16:23
Rr4sT left16:23
clemf joined16:23
diogenese left16:24
BlessJah but root won't sign a commit and victim of soctiotechnic cannot deny he/she applied the patch16:24
_ikke_ (even if someone examines what they sign properly, the signature does not capture that16:24
)16:24
jagob joined16:24
IntruderSRB left16:26
thiago joined16:26
inbx joined16:26
marcogmonteiro left16:28
troulouliou_div2 joined16:28
mgver joined16:28
xall left16:29
inbx_ joined16:29
Peetz0r left16:29
venmx joined16:29
jimklo joined16:30
raijin left16:30
inbx_ left16:31
ShekharReddy joined16:31
Peetz0r joined16:32
diogenese joined16:32
Endorphine joined16:32
inbx left16:32
marcogmonteiro joined16:33
Glooomy joined16:33
raijin joined16:33
Murii left16:34
venmx left16:34
Murii joined16:34
Endorphine left16:35
Tobbi left16:36
kavilraj joined16:37
Darcidride left16:37
IntruderSRB joined16:38
rivarun left16:39
rivarun joined16:39
ocbtec left16:39
inbx_ joined16:40
basiclaser left16:40
troulouliou_div2 left16:41
jnewt1 joined16:41
eroux left16:41
crose joined16:42
Peetz0r left16:42
Ryanar joined16:42
Balliad left16:43
jnewt1 left16:43
brent__ joined16:43
Murii left16:45
Murii joined16:45
Peetz0r joined16:45
flashpoint9 joined16:45
vuoto joined16:46
ShekharReddy left16:46
mgver how to create/restore backup from Gitlab?16:46
robattila256 joined16:46
pur3eval joined16:46
flashpoint9 mgver: https://docs.gitlab.com/omnibus/settings/backups.html16:47
flashpoint9 left16:47
_ikke_ whow16:48
Did flashpoint9 join just to answer that?16:48
sofly joined16:49
mgver maybe haha16:49
Electrometro joined16:49
Somelauw left16:50
pur3eval left16:51
Electrometro left16:51
mgver but still not understand16:52
Ozymandy joined16:52
mgver All configuration for omnibus-gitlab is stored in /etc/gitlab. To backup your configuration, just backup this directory.16:52
where are those files16:52
Electrometro joined16:53
Electrometro left16:54
lmclinskey joined16:55
jason237 left16:55
Murii left16:55
xall joined16:55
sbulage joined16:56
Murii joined16:56
IndigoTiger left16:57
kristofferR left16:57
lmclinskey left16:58
Tobbi joined16:59
EricPoe joined16:59
xissburg left16:59
EricPoe left17:00
mgver how to access /etc/gitlab folder in windows?17:00
by cmd?17:00
or gitlab.com ?17:00
clemf left17:00
svm_invictvs joined17:00
clemf joined17:01
jnavila left17:01
lss8 left17:01
ihradek left17:01
_ikke_ You have to login to that server17:02
ssh probly17:02
newbie1 left17:02
_ikke_ probably17:02
newbie1 joined17:03
xall left17:03
madewokherd joined17:03
IndigoTiger joined17:05
geoid_ left17:06
Jellyg00se joined17:08
reliability left17:08
Darcidride joined17:09
Snugglebash joined17:10
sbeller left17:11
Serpent7776 left17:11
Motoko joined17:13
dRealm left17:14
vibhavp left17:14
raijin left17:14
axilaris left17:14
thiago left17:16
Peetz0r left17:18
MineCoins left17:19
Anticom left17:19
Murii left17:19
KMaia2 joined17:19
IntruderSRB left17:19
clemf_ joined17:20
Murii joined17:20
clemf left17:20
Murii left17:20
Murii joined17:20
chele left17:22
reconx86_ joined17:22
crose left17:25
reconx86 left17:25
NaN joined17:26
duderonomy left17:26
NaN what will happen if I do a rebase in my branch that someone has already merged into their own?17:27
jstimm joined17:27
NaN I want to do a clean merge from my branch (not clean, lots of commits) to master17:28
Phil-Work NaN, not a lot17:28
if/when they merge/rebase it'll dedup17:29
might get some conflicts if you have to change the commits you're rebasing to resolve conflicts17:29
bennigraf_ joined17:29
theoceaniscool left17:29
marcogmonteiro left17:30
venmx joined17:30
ToBeCloud left17:31
Peetz0r joined17:31
Murii left17:31
NaN so my coworker will have conflicts if I do a rebase to clean my branch?17:31
what about if I do a new branch, clean it an merge with master?17:31
Murii joined17:31
btree joined17:32
BSAlb joined17:32
marcogmonteiro joined17:32
mikecmpb_ left17:32
MineCoins joined17:32
Murii left17:32
Murii joined17:32
BSAlb left17:33
BSAlb joined17:33
Naan joined17:33
Kaisyu left17:34
ajpiano_ajpiano17:35
BSab left17:35
xissburg joined17:36
sbulage left17:37
jost__ joined17:37
Peetz0r left17:37
shinnya left17:38
danemacmillan left17:38
durham joined17:39
jost_ left17:39
venmx left17:40
Snugglebash left17:41
hahuang65 joined17:41
Guest85 joined17:43
Peetz0r joined17:43
Murii left17:44
Murii joined17:44
nixjdm joined17:44
Murii left17:45
xissburg left17:45
Murii joined17:45
xissburg joined17:46
Derperpe1 left17:46
rgrinberg left17:46
pur3eval joined17:47
kavilraj left17:47
chipotle left17:48
mischat left17:48
MattMaker joined17:48
Tobbi left17:48
mischat joined17:49
NaN squach or rebase to master?17:49
pur3eval left17:51
danemacmillan joined17:51
dviola joined17:53
MattMaker left17:53
robotroll joined17:54
thiago joined17:54
mischat left17:54
King_Hual left17:54
dsantiago left17:55
apotry left17:55
Murii left17:55
Murii joined17:56
Murii left17:56
gugah joined17:57
gugah left17:57
Murii joined17:58
tyreld joined17:58
rgrinberg joined17:58
dcy left17:58
King_Hual joined17:59
King_Hual left17:59
King_Hual joined17:59
kristofferR joined17:59
Jellyg00se left17:59
freimatz left18:00
navidr joined18:00
publio joined18:01
ikelso left18:02
tristanp left18:03
j7k6 joined18:03
jstimm left18:04
bennigraf_ left18:06
sbeller joined18:07
achadwick left18:07
Glooomy left18:07
j7k6_ joined18:08
mar77i left18:08
Glooomy joined18:08
jnavila joined18:08
Murii left18:08
Glooomy left18:08
reliability joined18:08
j7k6 left18:08
Glooomy joined18:08
Murii joined18:09
Glooomy left18:09
Levex joined18:09
Glooomy joined18:09
orzo left18:09
Glooomy left18:09
Glooomy joined18:10
Glooomy left18:10
Glooomy joined18:11
Glooomy left18:11
jstimm joined18:13
Brain joined18:14
ratdeptrai joined18:14
khisanth_ left18:15
orzo joined18:17
danemacmillan left18:18
bennigraf_ joined18:18
tang^ joined18:19
danemacmillan joined18:19
g105b joined18:19
inbx__ joined18:20
inbx__ left18:20
mda1_ joined18:20
brent__ left18:21
flaviodesousa left18:21
gugah joined18:22
gugah left18:22
mda1 left18:22
inbx_ left18:23
boombatower joined18:23
Murii left18:24
sbeller left18:24
xissburg_ joined18:24
sbeller joined18:24
Murii joined18:24
_ADN_ left18:25
overlord_tm joined18:25
xissburg left18:25
matoro left18:26
ChiLL_SurF left18:26
MattMaker joined18:27
inbx__ joined18:27
xissburg joined18:29
xissburg_ left18:29
Nilesh_ left18:29
inbx__ left18:29
brent__ joined18:31
dreiss left18:32
zzz joined18:33
jason237 joined18:33
duderonomy joined18:34
bongjovi left18:34
j7k6 joined18:34
satifant joined18:35
mar77i joined18:36
j7k6_ left18:37
chardan joined18:37
matoro joined18:37
theoceaniscool joined18:40
joshszep joined18:41
chardan left18:41
jstimm left18:42
fcas joined18:42
mohabaks joined18:43
chardan joined18:43
eroux joined18:43
Murii left18:44
baastrup joined18:44
baastrup hey18:44
gitinfo baastrup: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.18:44
Murii joined18:44
bennigraf_ left18:45
e01 left18:45
baastrup hey any ideas how to run git push origin from crontab with ssh18:45
I need it for a backup job18:45
e01 joined18:45
e01 left18:45
e01 joined18:45
e01 left18:45
baastrup but the ssh-wont allow it18:46
raynold joined18:46
HurricaneHarry left18:46
e01 joined18:46
e01 left18:46
e01 joined18:46
e01 left18:46
acetakwas left18:46
e01 joined18:47
e01 left18:47
e01 joined18:47
e01 left18:47
Vampire0_Vampire018:47
pur3eval joined18:47
e01 joined18:48
e01 left18:48
e01 joined18:48
e01 left18:48
e01 joined18:48
e01 left18:48
e01 joined18:48
e01 left18:49
Vampire0 baastrup, What do you mean by "won't allow it"? I guess authentication fails which is most probably because the cron job is run as root while your SSH key is in your user configuration. Either let the cron job run as your user, or use `sudo -u youruser command` or `su -c command youruser` or specify the identity file (key for authentication) exlpicitly, e. g. by using SSH config files.18:49
e01 joined18:49
e01 left18:49
e01 joined18:49
e01 left18:49
kasual joined18:51
vdv joined18:51
flavius joined18:52
pur3eval left18:52
dreiss joined18:54
treia left18:55
Murii left18:56
baastrup Vampire0: its a user called rancid and it will run in crontab as that user, but still dont work, I think it has something to do with ssh-agent only working in the current terminal18:56
Murii joined18:56
raynold ahh it's a wonderful day18:58
matoro left18:58
dsantiago joined18:58
hfkhjgjhgkjhbyug joined18:59
_ng left19:01
chll__ left19:01
mohabaks left19:01
dsantiago left19:02
gugah joined19:02
Murii left19:02
jstimm joined19:03
Murii joined19:05
reynierpm left19:05
Sasazuka joined19:06
Vampire0 baastrup, of course, if your key is challenge-protected it cannot work as you cannot unlock the key19:07
Darren_ joined19:09
Darren_ left19:09
Gravious left19:09
j7k6 left19:09
Darren_ joined19:10
marcogmonteiro left19:10
robotroll left19:12
jstimm left19:13
emg joined19:14
fcas left19:16
fcas joined19:17
matoro joined19:17
marc_v92 joined19:18
tsdev_ left19:18
hfkhjgjhgkjhbyug left19:18
btree left19:20
muldover joined19:20
jstimm joined19:21
jimi_ left19:22
Raed|Mobile left19:22
fcas left19:22
peterR`` joined19:23
theoceaniscool left19:23
shgysk8zer0__ joined19:25
shgysk8zer0_ left19:26
cjohnson baastrup: you would need to figure out what "doesn't allow it " specifically means19:28
to solve the issue19:28
bocaneri left19:28
cdg joined19:28
efeuska joined19:29
kst123 joined19:29
Levex left19:29
Doow joined19:30
mischat joined19:30
efeuska left19:30
BackEndCoder left19:30
shgysk8zer0__ left19:31
BackEndCoder joined19:32
gk-1wm-su joined19:32
cdg_ left19:32
cdg left19:33
NullableTruth left19:34
danemacmillan left19:35
venmx joined19:35
nettoweb1 left19:35
gk-1wm-su left19:35
ecuanaso joined19:35
jstein_ joined19:36
jstein_ left19:37
chardan left19:37
nettoweb joined19:37
Vampire0_ joined19:38
pbrewczynski joined19:38
crose joined19:39
sgen joined19:39
Vampire0 left19:39
ash_workz left19:40
mar77i left19:40
mar77i joined19:40
nckpz joined19:42
BackEndCoder left19:42
Levex joined19:42
reznord joined19:42
LBV_User left19:42
BackEndCoder joined19:43
scoobertron left19:43
reznord hi, I want to make xhr call to the github API so, I can fetch the data of an user from github and render it in my application.19:43
How can i do that?19:43
danemacmillan joined19:44
venmx left19:44
reznord when I try to make normal API call, it is throwing me an error saying,19:44
https://www.irccloud.com/pastebin/2MnJzIvW/19:44
KMaia2 left19:44
j7k6 joined19:44
btyne79 joined19:45
g0th joined19:46
g0th hi19:46
how do I revert the commited change on one file so that the push doesn't see anything of it?19:46
the rest of the commit is fine19:46
borkr left19:47
Derperpe1 joined19:47
solarfly joined19:48
scoobertron joined19:48
pur3eval joined19:48
g0th or simpler: can I transform a commit back to staged or unstaged?19:49
git reset --soft HEAD^ ?19:49
LiftLeft joined19:49
e01 joined19:49
e01 left19:49
e01 joined19:49
solarfly Hi! I have a question. I have a branch with a new feature on it that is done and awaiting PR approval. I have a second feature that builds on top of that one. If I base the new feature B off of feature A, what do I do in the B branch when A is finally merged to master? Do I just git merge master into B to update my branch?19:49
HuskyApocalypse joined19:49
Jupelius_Jupelius19:50
shgysk8zer0_ joined19:50
jnewt joined19:52
pur3eval left19:53
raijin joined19:54
e01 left19:54
Eugene solarfly - how much do you / the project care about the prettiness of the history?19:54
solarfly Not much. I was just looking at maybe I can git merge Feature A into my feature B, as long as A gets PR'd into master first, will eveyrthing be clean?19:55
Eugene Basically, yes19:55
jstimm left19:55
Eugene merging from master back to B before merging B into master(or rebasing B upon new-master) is something that you "can do", but not must19:56
If you don't care what the log looks like then just go for it and stop worrying - git will merge things together exactly how it sounds like, and so long as the result works then you're good19:56
solarfly So I could merge A into B, work, then A get merged into master, and I can update my branch B with the changes from master to reduce the chance of diverging19:57
Yep, don't care what it looks like as long as we can read the logs19:57
Eugene If master has diverged by the time you merge B then yes, you'll need to resolve differences19:57
This is only an issue if any conflicts have happened - if you're the only one working on a given portion of the repo then it would be darned hard for that to happen....19:58
rgrinberg left19:58
Eugene I would go ahead and start B directly from A: eg `git checkout -b B A`19:59
If there's anything new in master that B needs then yes, merge it in19:59
solarfly I've run into this type of thing repeatedly for years, but decided today I need to try to understand things better. I found https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging and http://stackoverflow.com/questions/8963375/how-does-one-work-on-a-new-git-branch-that-depends-on-another-git-branch-that-is19:59
IntruderSRB joined19:59
Balliad joined19:59
solarfly Now that I'm a core developer and not managing engineers anymore (first time in 8 years)20:00
Eugene !flow is a great read20:00
gitinfo [!gitflow] The description of the gitflow branch workflow model is at http://nvie.com/posts/a-successful-git-branching-model/ while a tool to help implement this workflow is at https://github.com/petervanderdoes/gitflow See http://sethrobertson.github.com/GitBestPractices/#workflow for other workflow suggestions/references20:00
Eugene Make up a flowchart that works for your project and stick to it20:01
solarfly the team uses some semblence of git-flow. Very loosely defined though; there's feature branching and master. That's about it so far20:01
reznord can anyone help me with that?20:01
Eugene I think that is just fine for $MADE_UP_PERCENTAGE of users20:01
reznord - !github20:01
gitinfo reznord: Note that git != github. Feel free to ask us about Github-specific features (Forks, Pull Requests, Wikis, etc), but there are no guarantees. There is a #github channel, which might help too (again, no guarantees)20:01
solarfly nice :) Thank you for your help Eugene20:01
much appreciated20:02
Eugene g0th - !fixup20:02
gitinfo g0th: So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!20:02
UrsoBranco joined20:02
concerti joined20:02
timvisher perlpilot, BlessJah: i'm thinking more in terms of `git fetch --all` etc. which i use a lot.20:03
aidalgol joined20:03
timvisher i basically don't want the remote to be considered for pushing or pulling when generic commands are used20:03
j7k6_ joined20:04
Dougie187 left20:05
BSab joined20:05
Guest4891 joined20:06
crose left20:06
Guest4891 left20:07
Guest4891 joined20:07
Guest4891 left20:07
YuGiOhJCJ left20:09
j7k6_ left20:09
SwiftMatt joined20:09
BSAlb left20:09
dviola left20:12
gijga joined20:14
byte512 left20:15
alexandre9099 left20:17
amagawdd left20:18
Darcidride left20:19
jimi_ joined20:21
marc_v92 left20:21
marc_v92 joined20:22
amagawdd joined20:22
austin987 left20:22
alexandre9099 joined20:24
gijga left20:24
Sasazuka_ joined20:27
Sasazuka left20:28
jdl joined20:28
g105b left20:28
sveinse joined20:28
sveinse Is there a way I can update/fetch all new updates, including all new branches, into a bare mirror?20:30
kasual left20:30
finalbeta left20:31
zzz left20:31
finalbeta joined20:31
sveinse I thought git remote update --prune did, but it does not20:33
durham left20:33
bernardio joined20:34
guest joined20:34
Levex left20:35
rnsanchez left20:36
bernardio left20:36
_ikke_ What are you missing?20:37
sveinse _ikke_: A new remote branch that have come into existence since the mirror was created20:38
I'd like to create a script that can inspect the origin and completely mirror it (that is include all branches and their refs)20:39
durham joined20:39
ribasushi left20:39
clemf_ left20:41
Vampire0 joined20:41
clemf joined20:41
Vampire0_ left20:41
ilpanda joined20:42
BackEndCoder left20:43
sveinse The horrible, inefficient naive approach is to delete the mirror and git clone --mirror --bare whenever you'd need to sync the repos20:45
BackEndCoder joined20:45
mda1_ left20:46
m0viefreak joined20:46
guest left20:47
Emperor_Earth_ joined20:47
NaN left20:47
_ikke_ git remote update or git fetch origin should wrok20:47
work20:47
Emperor_Earth left20:48
pur3eval joined20:49
sveinse _ikke_: no, it does not pick up a new remote branch. I see it with git branch -av thou20:49
_ikke_ Then you have it20:49
sveinse _ikke_: Have what?20:50
e01 joined20:50
IntruderSRB left20:51
sveinse _ikke_: I need a cron-job tool to keep our mirrors in completely sync with the remote origin. If a remote branch is created, then it needs to be picked up and fetched automatically20:51
qqx sveinse: Was your "mirror" actually created as a mirror?20:51
sveinse qqx: Created with git clone --bare --mirror20:52
UrsoBranco left20:52
pur3eval left20:54
chipotle joined20:54
e01 left20:55
navidr left20:56
sveinse Think I solved it. Some repos wasn't properly mirroring. Their remotes were showing up as remotes/origin/.. instead of having only one like you do for mirror repos20:56
raijin left20:58
Peetz0r left20:58
Motoko left20:59
Motoko joined20:59
ribasushi joined20:59
Peetz0r joined21:00
baastrup left21:00
tyreld left21:00
mda1 joined21:01
jeffreylevesque left21:02
xissburg_ joined21:03
xissburg left21:03
durham left21:05
chardan joined21:06
durham joined21:06
tyreld joined21:09
Murii left21:10
algun_ left21:10
algun_ joined21:11
mmlb left21:11
Murrito left21:12
Murr joined21:12
Levex joined21:12
kst123 left21:13
masuberu joined21:13
vuoto left21:13
cdg joined21:14
RxMcDonald joined21:15
Balliad left21:15
RxMcDonald how do you find when a file got deleted in the commit history?21:15
mrVandermare left21:15
kadoban git log -- the_file should give you a good idea21:16
crayon joined21:16
durham_ joined21:18
Sasazuka joined21:19
Sasazuka_ left21:19
dsdeiz joined21:20
durham left21:21
durham_ left21:22
Sasazuka_ joined21:22
Sasazuka left21:24
Vampire0 left21:25
morfin left21:25
jeffreylevesque joined21:25
treehug88 joined21:26
Vampire0 joined21:26
theoceaniscool joined21:28
Alienpruts joined21:28
durham joined21:28
joshszep left21:28
aidalgol left21:29
durham left21:30
tvw left21:31
joshszep joined21:32
nettoweb left21:32
nettoweb1 joined21:32
bgerber left21:34
Levex left21:35
levex_ joined21:35
LaptopBrain joined21:36
Ozymandy left21:36
viktor4 joined21:37
marc_v92 left21:37
masuberu left21:37
reliability left21:37
shgysk8zer0_ left21:37
ecuanaso left21:38
durham joined21:38
levex_ left21:39
marc_v92 joined21:39
l4v2 joined21:39
Guest55 joined21:40
cdg_ joined21:40
e01 joined21:40
e01 left21:40
e01 joined21:40
LaptopBrain left21:41
clemf left21:41
BSab left21:41
BSaboia joined21:41
RxMcDonald kadoban: well, it's not enough21:43
j7k6 left21:43
RxMcDonald now showing when the file got deleted to be honest21:43
not ^21:43
cdg left21:43
j7k6 joined21:43
kadoban Should just be the first commit you see usually ... can't imagine a case it wouldn't be.21:44
dviola joined21:44
clemf joined21:44
invisbl_ joined21:44
RxMcDonald oh maybe because its a diff branch21:44
yea that's it21:44
invisbl_ left21:45
invisbl_ joined21:45
Dil3mm4 left21:45
ilpanda left21:48
newbie1 left21:48
newbie1 joined21:49
Tobbi joined21:49
durham left21:50
pur3eval joined21:50
durham joined21:52
marc_v92 left21:52
madewokherd left21:53
jimi_ left21:54
BackEndCoder left21:54
pur3eval left21:54
m4sk1n joined21:55
jnavila left21:55
BackEndCoder joined21:56
durham left21:56
flavius left21:56
durham joined21:57
durham left21:57
texasmynsted joined21:57
satifant left21:57
shgysk8zer0_ joined21:57
durham joined21:57
texasmynsted if somebody rebases a branch and pushes it and I try to pull and am unable to ff. How can I force my local to match the remote?21:57
Karazhan left21:58
RxMcDonald texasmynsted: rm -rf && git clone21:58
Karazhan joined21:58
mutex joined21:58
kst123 joined21:58
solarfly He would lose local changes doing that21:58
texasmynsted I ended up git branch -D foo21:59
joshszep left21:59
heroux_ joined21:59
texasmynsted then git checkout foo21:59
I am sure there is a better way21:59
RxMcDonald if you don't have any stashed stuff or anything22:00
heroux left22:00
Levex joined22:00
heroux_heroux22:00
kadoban texasmynsted: Probably 'git checkout the_branch && git reset --hard @{u}' or something22:01
texasmynsted @{u}22:01
what is that? The upstream HEAD?22:02
invisbl_ left22:02
invisbl joined22:02
kadoban It's short for upstream, ya22:03
joshszep joined22:03
kadoban man gitrevisions22:03
gitinfo the gitrevisions manpage is available at http://jk.gs/gitrevisions.html22:03
kadoban It's in there22:03
olivetree joined22:03
elsevero joined22:04
blackwind_123 left22:04
Derperpe1 left22:05
j7k6_ joined22:05
Gsham left22:06
jdl left22:06
blackwind_123 joined22:06
noecc left22:06
kst123 left22:07
l4v2 left22:07
viktor4 left22:07
kst123 joined22:08
olivetree left22:09
nickabbey left22:09
kst123 left22:09
Levex left22:09
nettoweb joined22:10
nickabbey joined22:10
j7k6_ left22:10
nettoweb1 left22:10
afuentes left22:13
Endarked joined22:13
ThiefMaster joined22:13
mischat left22:14
nickabbey left22:14
mischat joined22:15
ISmithers joined22:15
l4v2 joined22:15
vdv left22:16
dersand left22:16
SwiftMatt left22:17
M-ou-se joined22:17
mischat left22:19
tanuki_tanuki22:21
Alienpruts left22:21
inflames joined22:23
l4v2 left22:26
treehug88 left22:26
hdon joined22:27
hdon hi all :) if i want to get an overview of the anatomy of my branches and heads, is there a way to use log --graph but filtering to only see heads and nearest common ancestors of heads?22:27
Karazhan left22:28
Karazhan joined22:28
CarlFK joined22:28
todd_dsm joined22:29
Limes left22:30
Eugene hdon - man git-log; see --all, --branches, --tags, etc22:30
gitinfo hdon: the git-log manpage is available at http://jk.gs/git-log.html22:30
Eugene Or you can manually specify anything you want for <revision range>22:31
ThiefMaster left22:31
ThiefMaster joined22:31
chardan left22:31
Doow left22:31
ThiefMaster left22:31
hdon hm22:32
Eugene, but these options do not filter out the boring intervening revision history that i don't want to see22:33
Eugene "History Simplification" section in the same man page22:34
hdon looks22:35
Khep joined22:38
kappy joined22:39
NeverDie left22:42
NeverDie joined22:43
Levex joined22:44
mischat joined22:44
ThiefMaster joined22:44
Levex left22:45
RxMcDonald left22:46
Levex joined22:46
Levex left22:46
chipotle left22:46
hdon maybe i'm not literate enough in git but i'm not seeing what i want here :C22:49
i thought --dense would do it22:50
actually i should test this in an isolated repo. this repo may not be a great test case22:50
SwiftMatt joined22:50
pur3eval joined22:50
l4v2 joined22:51
peeps[lappy] joined22:52
hdon yeah i'm not seeing what i want22:53
fstd_ joined22:53
nowhereman joined22:54
hdon 11608 newchicagoproperties.com22:54
11889 philhornback.com22:54
11945 jeffbrumfieldrealestate.com22:54
11954 gregoryreecesmith.org22:54
fstd left22:54
fstd_fstd22:54
pur3eval left22:55
hdon 11944 dclenterprisesinc.com22:55
12069 hollowayrealtyus.com/22:55
john lvm on 1206922:56
11954 grsglobalenterprisesinc.com22:56
11646 hallmarkproperties.net john lvm22:56
bremner please stop.22:56
hdon oh shit22:56
Vampire0 Don't spam hdon22:56
hdon sorry bremner wrong chan22:56
Vampire0 Use pastebin if it is real conten22:56
bremner okie dokie22:56
hdon :322:56
Tobbi left22:56
gk--1wm- joined22:56
Vampire0 mmh, eyes with tits?22:57
jimsio left22:57
chardan joined22:59
fmeerkoetter left23:01
fmeerkoetter joined23:01
gk--1wm- left23:01
MonsterKiller left23:01
dsdeiz left23:02
denis_M joined23:02
hdon is it perhaps simply the case that git does not have the history simplification mode that i want? i want to filter out any revisions that are neither: explicitly listed on the command line (or with --branches or similar) nor are the nearest common ancestors of such revisions23:03
newbie1 left23:03
denisMone left23:03
newbie1 joined23:04
MonsterKiller joined23:04
aidalgol joined23:05
cdown left23:07
henriquev joined23:08
chardan left23:08
xissburg_xissburg23:08
jimi_ joined23:09
gugah left23:10
zivester left23:10
Derperpe1 joined23:11
Gloomy joined23:12
gugah joined23:14
BSAlb joined23:16
BSaboia left23:17
durham_ joined23:17
durham_ left23:18
venmx joined23:19
scoobertron left23:19
scoobertron joined23:19
Khep left23:19
Raed|Mobile joined23:19
chardan joined23:21
durham left23:21
Guest79609 left23:21
Khisanth joined23:24
CheckDavid left23:24
Endarked left23:24
elsevero left23:24
durham joined23:26
rivarun left23:27
rivarun joined23:28
patarr left23:28
Kaisyu joined23:28
mischat left23:29
j7k6 left23:31
askb joined23:33
gugah left23:34
Somelauw joined23:35
dsdeiz joined23:35
dsdeiz left23:35
dsdeiz joined23:35
chachasmooth left23:36
BackEndCoder left23:37
BackEndCoder joined23:37
ubuntu joined23:38
ubuntuGuest3423423:38
gitinfo set mode: +v23:39
Guest34234_Marek_23:39
captain joined23:40
chachasmooth joined23:40
Gloomy left23:40
Darren_ left23:42
clemf left23:43
venmx left23:44
matoro left23:44
svm_invictvs left23:45
muldover left23:45
ResidentBiscuit left23:46
matsaman joined23:49
matoro joined23:50
Mindi joined23:50
utrack joined23:50
AaronMT left23:50
pur3eval joined23:51
_jaysen joined23:52
lauren joined23:53
Wulf left23:53
lauren hallo! anyone know if there's an already written way to do sub-file "rename"-style tracking of hunks in git blame?23:54
or something like git blame23:54
rgrinberg joined23:54
peeps[lappy] left23:55
lauren what I want is a git-blame-like-thing that shows me when a hunk was copied between files23:55
or just git log, but blame would be more useful23:55
pur3eval left23:56
TomyLobo left23:56
_jaysen left23:56
pbrewczynski left23:56
Onionnion joined23:57

Logs Search ←Prev date Next date→ Channels Documentation