IRCloggy #git 2016-02-03

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.

2016-02-03

phroa` check out the master branch locally then run "git checkout -b newbranchname" then "git checkout master" then "git reset --hard <commit-hash-you-want-to-reset-to>" then "git push -f origin master"00:00
!rewrite applies but it looks like you're past that anyway00:01
gitinfo Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum00:01
MattMaker joined00:01
Rodya_ joined00:01
pewu joined00:02
BeatrixKiddo joined00:04
jwmann left00:04
diegoaguilar left00:05
raijin left00:06
tottiq left00:06
tzero joined00:06
victor- kadoban: ah, you’re right. it was a pre-commit hook. thanks!00:07
kpease left00:08
davidosomething left00:09
hexagoxel_ joined00:10
mischat joined00:11
tzero left00:11
jimi_ left00:12
jtri phroa`: thanks! that worked great00:12
hexagoxel left00:14
hexagoxel_hexagoxel00:14
mischat left00:16
kaiza left00:17
kaiza joined00:18
Noldorin joined00:18
jteneyck joined00:20
diegoaguilar joined00:20
jteneyck left00:20
jteneyck joined00:21
livingstn joined00:21
nettoweb joined00:22
tzero joined00:22
mrk left00:23
chitopunk left00:25
jfelchner left00:25
rominronin joined00:26
astockton left00:27
raijin joined00:27
Primer joined00:27
s8321414 joined00:29
Primer Hi, I occasionally commit to a dev branch (git commit -am "WIP") in order to get updates in that branch from one development environment to another. Thing is, git seems to lose track of renamed files when I sometimes reset those commit. I'm on Debian Stale which has git 1.9 and I'm wondering if I'm missing out on this "feature".00:29
blckbit10 left00:29
Primer By having such an old version of git00:30
blckbit10 joined00:30
tzero left00:30
Primer Actually, I'm on Debian 7, which is close to EOL00:30
rominronin left00:31
uri_ left00:32
Primer So for example, on machine 1 I: git mv file1 file2, git commit -am "WIP", git push (-f as needed), then on machine 2 I: git co -b branch origin/branch, git reset HEAD~1, and the mv is now deleted: file1, untracked: file200:32
nikio_ left00:32
tzero joined00:35
hahuang65 joined00:35
jbudz_ left00:36
mostlybadfly joined00:37
nikio_ joined00:37
uber left00:38
uber joined00:38
Jusle joined00:38
nikooio joined00:38
t0by left00:38
jtri left00:39
tanimislam joined00:39
tanimislam left00:39
hahuang65 left00:40
tanimislam joined00:40
nikooio left00:41
nikio_ left00:42
mwhooker left00:42
jaguarmagenta2 left00:43
nitin_ joined00:45
King_Hual left00:45
samw joined00:47
douglascorrea left00:48
kaiza left00:49
victor- left00:49
livingstn left00:49
douglascorrea joined00:50
codeman left00:50
nickadam joined00:52
avgn5 joined00:53
madebymarkca joined00:54
undRzr joined00:54
jaguarmagenta joined00:55
arooni left00:55
Outsider__ joined00:58
fstd left00:59
fstd joined00:59
LeeXiaolan joined00:59
kilo_bravo left00:59
AtnevRed joined00:59
nitin_ left00:59
mattfoo left01:00
douglascorrea left01:00
LeeXiaolan left01:00
hyperair left01:01
lolmac left01:01
jottr_ left01:01
Garibaldi0 left01:03
AtnevRed left01:04
imachuchu left01:04
mattfoo joined01:05
The_Woodsman left01:06
jaguarmagenta left01:06
nitin__ joined01:06
jaguarmagenta joined01:08
Gsham left01:09
al-damiri left01:09
bronson joined01:09
kfoonamalik left01:09
Poppa|2 joined01:10
bitkiller left01:11
dances-with-cats left01:11
dances-with-cats joined01:12
mischat joined01:12
harish left01:12
Rodya_ left01:12
Rodya_ joined01:13
bronson left01:14
Poppabear left01:14
arooni joined01:15
Sucks joined01:15
Gsham joined01:16
dfrey joined01:16
gfixler1 left01:17
Rodya_ left01:17
Poppa|2 left01:17
clemf_ left01:17
Rodya_ joined01:18
Gsham left01:18
nettoweb left01:18
dfrey Hi. I am trying to build git from source (long story) and I have noticed that contrib/completion/git-prompt.sh never ends up in my installation target directory. I ran make all doc && make install install-doc install-html. Is there something I missed? Or are these scripts never installed?01:18
dances-with-cats left01:19
jfelchner joined01:19
MattMaker left01:19
Rodya_ left01:20
Rodya_ joined01:21
keltvek left01:22
Rodya_ left01:23
jam_ joined01:24
TobyP left01:24
Rodya_ joined01:24
Gsham joined01:25
astockton joined01:27
rominronin joined01:27
mizu_no_oto left01:27
lambainsaan_ joined01:27
jam_ left01:28
SimonNa left01:28
Lyqyd joined01:29
felixjet left01:29
nitin__ left01:30
felixjet joined01:30
astockton left01:31
rominronin left01:31
EvilPenguin left01:32
jaguarmagenta left01:33
jaguarmagenta joined01:33
uri_ joined01:34
PryMar56 dfrey, /usr/share/git-core/contrib/completion/git-prompt.sh01:34
jacksparrow007 joined01:35
msonntag left01:35
invisbl left01:35
invisbl joined01:36
PryMar56 it show up twice in my package set. I rebuilt the Fedora src rpm01:36
hahuang65 joined01:36
jkoudys left01:36
Rodya_ left01:38
jaguarmagenta left01:38
Rodya_ joined01:39
uri_ left01:39
mezod left01:39
jacksparrow007 left01:39
hahuang65 left01:41
devth_ joined01:41
jteneyck left01:42
Puhe joined01:42
devth left01:43
shinnya left01:43
ferr left01:44
UptimeDowntime01:44
mkelly joined01:47
blackwind_123 left01:48
livingstn joined01:51
kolobytekolobyte_01:53
gfixler1 joined01:53
lmatteis left01:53
uri_ joined01:53
uri_ left01:56
colwem joined01:56
ajm203_ left01:57
gfixler1 left01:57
jottr_ joined01:58
MassiveSubtlety left01:58
MassiveSubtlety joined01:58
diogenese left01:59
hahuang65 joined01:59
diogenese joined01:59
douglascorrea joined02:00
jaafar left02:01
undRzr left02:01
livingstn left02:01
livingstn joined02:02
michelangelo joined02:02
tottiq joined02:02
dances-with-cats joined02:02
MassiveSubtlety left02:02
thiago left02:04
uri_ joined02:05
douglascorrea left02:05
donmichelangelo left02:05
bb010g joined02:07
gitinfo set mode: +v02:07
uri_ left02:08
samw left02:09
Sample left02:10
milki dfrey: contrib probably needs manual steps to move to the correct places02:10
jottr_ left02:10
daito joined02:11
King_Hual joined02:11
Gsham left02:11
Gsham joined02:11
harish joined02:12
tottiq left02:13
livingstn left02:16
ilmgb_ joined02:17
drodger_ joined02:18
livingstn joined02:18
drodger left02:19
ilmgb left02:20
BeatrixKiddo left02:22
Garibaldi0 joined02:22
TobyP joined02:23
uri_ joined02:24
tyll_ joined02:24
King_Hual left02:26
uri_ left02:26
TobyP left02:26
tyll left02:27
astockton joined02:27
rominronin joined02:28
Vampire0_ joined02:28
mischat left02:28
blckbit10 left02:29
radsy left02:29
clemf joined02:29
rpdprd left02:30
rpdprd joined02:30
King_Hual joined02:31
King_Hual left02:31
King_Hual joined02:31
Vampire0 left02:31
jfelchner left02:32
astockton left02:32
rominronin left02:33
Treio left02:33
rkazak joined02:34
Wetmelon joined02:34
blckbit10 joined02:36
jkoudys joined02:37
King_Hual left02:38
govg left02:38
clemf left02:38
nilsi joined02:38
mablae__ joined02:39
vkngpmhc joined02:40
mablae_ left02:42
kazantip left02:43
skorgon joined02:43
dfrey left02:44
arescorpio joined02:45
Noldorin left02:45
dfrey joined02:45
kfoonamalik joined02:45
wpkegkegstr02:45
kegstrkegster02:45
kegster left02:45
kegster joined02:45
tanimislam left02:46
pks left02:46
codedmart left02:46
Garibaldi0 left02:46
vkngpmhc left02:46
jteneyck joined02:47
vkngpmhc joined02:47
kfoonamalik left02:47
mizu_no_oto joined02:48
pks joined02:49
Ahmed90 left02:50
ome joined02:50
mellernoia-work left02:50
skorgon left02:51
xnull left02:51
mallocthis left02:52
radsy joined02:52
weox left02:53
jaguarmagenta joined02:55
mallocthis joined02:56
durham left02:56
thiago joined02:57
kaiza joined02:57
livingstn left02:58
donmichelangelo joined03:00
AtnevRed joined03:00
netj left03:00
netj joined03:01
michelangelo left03:02
clemf joined03:03
Goplat joined03:03
AtnevRed left03:05
[Saint] left03:05
mkelly left03:07
Jusle left03:07
[Saint] joined03:07
d4rklit3 left03:09
jteneyck left03:09
livingstn joined03:09
rafalcpp left03:10
rafalcpp joined03:11
yqt left03:11
yrter_ joined03:11
yrter left03:12
frem left03:12
terminal_echo joined03:14
Limes_ joined03:15
harleypig Is there an android client for git that allows for ssh passkey push/pull?03:15
elementalest left03:16
m0viefreak left03:16
radsy left03:17
livingstn left03:17
thiago besides git + ssh?03:19
livingstn joined03:21
uri_ joined03:21
drupald joined03:21
Limes_ left03:23
dreiss left03:24
jam_ joined03:24
dances-with-cats left03:25
reim joined03:26
chachasmooth left03:26
kegster left03:26
uri_ left03:27
samw joined03:27
kegster joined03:27
uri_ joined03:27
chachasmooth joined03:27
arooni left03:28
astockton joined03:28
jam_ left03:29
rominronin joined03:29
uri_ left03:31
tkeith left03:32
astockton left03:33
rominronin left03:34
uri_ joined03:35
jacksparrow007 joined03:36
watabou joined03:36
uri_ left03:37
uri_ joined03:37
jackspar_ joined03:40
jacksparrow007 left03:40
dances-with-cats joined03:41
rkazak left03:41
dreiss joined03:41
presto left03:42
[Saint_] joined03:43
[Saint] left03:43
gfixler1 joined03:43
Sasazuka left03:44
BeatrixKiddo joined03:44
presto joined03:44
jeffreylevesque joined03:45
harleypig thiago: no, git+ssh is fine, I was just wondering if there was a git client for the android that could be used to develop. I use termux, so I'm happy with my setup. But my son wants to use a more gui centric environment.03:46
thiago why would you develop *on* Android, as opposed to a laptop?03:48
diegoaguilar left03:48
nilsi left03:48
uri_ left03:49
davidosomething joined03:50
mallocthis left03:50
livingstn left03:52
michaelrice joined03:52
Gsham left03:52
tmcmahon joined03:53
mallocthis joined03:53
nnyk_ joined03:53
ShapeShifter499 joined03:54
mizu_no_oto left03:55
tinajohnson__ joined03:56
tmcmahon left03:57
tmcmahon joined03:57
tmcmahon left03:57
s8321414 left03:57
xaxxon joined03:58
Mentos left03:58
clemf left03:58
michaelrice left03:59
xaxxon I added some really big binary files to my repo and later realized I didn't need them ever again. but they still get downloaded every time there's a clone, right? any way to completely remove them? I understand that there are hashes in the tree that rely on those things existing, so this may not be possible, but I figured I'd ask03:59
diegoaguilar joined04:00
xaxxon http://dalibornasevic.com/posts/2-permanently-remove-files-and-folders-from-git-repo <== maybe this?04:01
michaelrice joined04:01
dreiss left04:02
xaxxon git-filter-branch.. sounds right, but make a backup first, right?04:03
douglascorrea joined04:03
harish left04:03
vkngpmhc left04:03
harish joined04:03
|node left04:05
jottr_ joined04:06
nnyk joined04:06
douglascorrea left04:07
dopeddude joined04:07
lindenle left04:08
nnyk_ left04:09
aidalgol left04:11
jottr_ left04:12
User458764 joined04:12
hyphenated left04:13
presto left04:13
Manikandan joined04:13
michaelrice left04:14
nbdy joined04:15
d4rklit3 joined04:16
arooni joined04:16
nbdy left04:16
daito left04:17
diegoaguilar left04:17
d4rklit3 left04:18
Rodya_ left04:19
d4rklit3 joined04:19
d4rklit3 left04:19
clemf joined04:19
PryMar56 left04:21
King_Hual joined04:23
Lyqyd_ joined04:24
Lyqyd left04:24
mischat joined04:25
terminal_echo left04:25
mallocthis left04:26
dreiss joined04:26
colwem left04:26
jackspar_ left04:27
jacksparrow007 joined04:28
astockton joined04:29
mischat left04:29
rominronin joined04:30
harleypig j!nx4#vmt04:32
jacksparrow007 left04:32
Silenced joined04:32
Silenced left04:32
Silenced joined04:32
Pulp joined04:33
astockton left04:34
bbbthunda left04:35
samw left04:35
User458764 left04:35
rominronin left04:35
mallocthis joined04:35
harish left04:37
xaxxon harleypig, time to change your passwor04:42
I suggest hunter204:42
harleypig it certainly is04:42
harish joined04:42
harleypig O04:43
I'll go to ***********04:43
codedmart joined04:43
modocache left04:43
vkngpmhc joined04:43
xaxxon ghost harleypig j!nx4#vmt04:44
Invalid password for HarleyPig04:44
rats04:44
harleypig heh ... separate passwords for every account04:45
xaxxon oh.. I usually end up saying my password when I'm trying to identify and a new window pops up.. so it IS my irc apss04:45
jkoudys left04:46
harleypig I have too many windows open ...04:47
squiddle joined04:48
Silenced left04:49
ensyde joined04:49
codedmart left04:50
dfrey left04:52
nnyk left04:54
17WABPBLQ left04:54
eli joined04:55
eli left04:55
samw joined04:57
squiddle left04:57
fracting left04:58
ygeLN left04:58
vkngpmhc left04:58
xaxxon left04:58
vkngpmhc joined04:58
fracting joined05:00
Silenced joined05:00
AtnevRed joined05:01
jam_ joined05:02
xaxxon joined05:02
Sucks left05:02
dfrey joined05:03
mkelly joined05:03
joki left05:03
douglascorrea joined05:03
mkelly left05:04
arescorpio left05:05
ygeLN joined05:05
AtnevRed left05:05
sparetire left05:06
Sucks joined05:07
mkelly joined05:07
ome left05:07
circ-user-TFDGm joined05:07
dfrey left05:07
joki joined05:08
douglascorrea left05:08
lindenle joined05:09
sdothum left05:09
bronson joined05:10
s00pcan left05:11
nilsi joined05:11
Silenced left05:11
Silenced joined05:11
circ-user-TFDGm left05:11
elementalest joined05:12
elementalest left05:12
elementalest joined05:12
hahuang65 left05:12
croc joined05:13
rchavik joined05:13
lindenle left05:13
bronson left05:15
jwmann joined05:17
daito joined05:17
daito left05:19
CheckDavid left05:19
daito joined05:19
astockton joined05:19
Lyqyd_ left05:19
dfrey joined05:21
duderonomy joined05:22
fscala left05:23
michaelrice joined05:23
rkazak joined05:25
fscala joined05:25
mischat joined05:26
ensyde left05:26
ensyde joined05:27
Sample joined05:27
blckbit10 left05:28
rkazak left05:28
arooni left05:30
blckbit10 joined05:30
mischat left05:30
rominronin joined05:31
dfrey left05:33
ensyde left05:35
rominronin left05:36
mkelly left05:37
Sucks left05:37
Cabanossi left05:38
banana_pancakes joined05:39
apotry joined05:39
Pulp left05:39
Xethron joined05:39
Cabanossi joined05:39
Sucks joined05:41
rossome left05:41
moei joined05:42
mniipphy17Z905:42
kadoban left05:45
phy17Z9mniip05:45
dances-with-cats left05:47
msonntag joined05:47
astockton left05:48
dfrey joined05:50
Sucks left05:51
Sucks joined05:54
nilg joined05:55
mohabaks joined05:56
kazantip joined05:56
rossome joined05:56
astockton joined05:57
thomastdubellz05:58
xaxxon left05:58
banana_pancakes left05:58
mallocthis left05:59
Sample left06:00
kiloreux joined06:01
kiloreux left06:01
mallocthis joined06:02
kiloreux joined06:02
daito_ joined06:02
astockton left06:02
kiloreux left06:02
mariuscc joined06:03
samw left06:04
jam_ left06:04
daito left06:05
Silenced left06:05
jaguarmagenta2 joined06:05
douglascorrea joined06:07
dfrey left06:07
mohabaks left06:07
jaguarmagenta left06:08
dsantiag_ left06:08
Sample joined06:08
jottr_ joined06:08
freimatz joined06:09
nidr0x joined06:09
dsantiago joined06:09
RobertWindows joined06:09
terminal_echo joined06:09
RobertWindows is this for git as in github/git revision?06:09
is it possible here to ask for help with git in another project?06:10
douglascorrea left06:11
vkngpmhc left06:11
s8321414 joined06:12
rodarmor left06:12
MutantMahesh joined06:12
thiago RobertWindows: you can ask for help with git, whichever project you're using it for06:12
nidr0x left06:13
RobertWindows thank goodneeds06:13
i was trying to branch this project called lateralgm and start a stable branch06:13
jottr_ left06:13
RobertWindows but oddly enough, the history is wildly different06:13
https://github.com/IsmAvatar/LateralGM/commits/master?page=2306:13
4fa0748 is what i checked out in my new branch06:13
thiago how did you try to do it?06:14
RobertWindows but instead of giving me the history of the master branch behind that time06:14
govg joined06:14
RobertWindows git checkout 4fa which was a pr from someone else06:14
and instead i got his history on the branch instead of master's history06:14
n00bdev joined06:14
thiago is 4fa the name of the branch or a SHA-1?06:14
RobertWindows yes i didn't feel like typing it out again, i typed the whole06:15
https://github.com/IsmAvatar/LateralGM/commits/master?page=2406:15
https://github.com/IsmAvatar/LateralGM/commits/stable?page=206:15
we can see the wildly different history of the two branches i created06:15
thiago which one is it?06:15
the SHA-1 or the name of the branch?06:15
RobertWindows the sha-106:15
thiago ok, so you are at that SHA-106:16
RobertWindows but the worse thing is i added all my fixes on this wrong history, so what i want to do is take my stack of changes on stable06:16
thiago then you ran git log. What did you expect to see? And what did you see?06:16
RobertWindows and rebase it to the same point, except from master and not some random contributors commit history06:16
BekN left06:16
xaxxon joined06:16
thiago ok, so let's address that problem06:16
RobertWindows thiago, currently i'm actually at stable head, after all my recent changes06:16
nidr0x joined06:16
RobertWindows and i want to do this carefully to not lose my changes06:17
thiago are you at your most recent commit?06:17
RobertWindows yes i am06:17
thiago and you want to rebase those changes onto a different branch, correct?06:17
RobertWindows i aborted a rebase though because i'm certain i'm not sure how to do it06:17
yes06:17
again i tried with that same sha-1 from that pr and it was still rebasing on the same history too06:17
thiago you need to identify two things for this:06:17
RobertWindows thus why i aborted06:17
rinwa_ joined06:17
RobertWindows ok06:17
rscata joined06:18
thiago the first commit in your current history that you don't want to rebase. That's your current base.06:18
and the new base06:18
dfrey joined06:18
RobertWindows ok06:18
nidr0x left06:18
rodarmor joined06:18
RobertWindows the new base i want to be right when the pr #36 was pulled to master06:18
thiago if you said you worked on stable, the first commit you don't want to rebase is the stable branch (probably origin/stable or upstream/stable)06:18
daito joined06:19
thiago don't tell me, just find them06:19
when you're done, run: git rebase --onto newbase currentbase06:19
nnyk joined06:19
RobertWindows https://github.com/IsmAvatar/LateralGM/commits/master?page=2306:20
https://github.com/IsmAvatar/LateralGM/commits/stable?page=106:20
at the verry bottom of these two pages, can you see where #36 is merged?06:20
i want the history on stable before #36 to look exactly like master06:20
thiago, how do i find them?06:20
thiago git log or a web tool06:20
it's up to you06:20
RobertWindows see cuz all i was doing was grabbing the sha-1 of #606:20
ok hrm06:20
nidr0x joined06:20
RobertWindows thiago, would i rewind to #36?06:20
thiago why do you want to do that?06:21
and what's "#36" ?06:21
RobertWindows at the very bottom, it's a pr from an early dev who isn't around anymore06:21
from that point, is when i want all the stable changes i retroactively imported06:21
thiago the command line does not understand "some commit I can see in a web page"06:21
and nor can I06:22
RobertWindows i want to take the top of the stable page and stick on the bottom of master's page basically if that makes sense?06:22
rkazak joined06:22
RobertWindows hang on06:22
https://github.com/IsmAvatar/LateralGM/pull/3606:22
thiago you need either the commit's SHA-1 or the name of a branch/ref that might be pointing to it06:22
don't give me the link06:22
RobertWindows 4fa0748 is in there too06:22
thiago ok06:22
RobertWindows yeah like i said i tried using that but it gave me his forks history instead of masters06:22
which i find really odd?06:22
daito_ left06:23
thiago why do you find it odd?06:23
rinwa_ left06:23
RobertWindows i guess i don't because i guess the sha-1's are based off of his commits which start in his fork06:23
thiago if that's not the correct commit, then find the correct one06:24
RobertWindows oh it is06:24
thiago why do you want to start off a particular commit? Most people start on top of a branch.06:24
RobertWindows what else would i use? the thing is the sha-1 there gives me his history06:24
thiago explain why you don't want to start on top of one of your project's branches06:24
RobertWindows it didn't have very many branches haha, and this master was the only one being maintained06:24
so i retroactively decided to create a stable branch06:24
thiago ok, so your project has only one branch06:25
why do you want to start your work from anything other than the upstream's only branch?06:25
meloc left06:25
RobertWindows technically it has 4 but it's complicated, the one branch is for a threading problem but both of those two are too far outdated06:25
thiago, i am the only upstream contributor basically06:25
and i hate most of my changes06:25
i was rather inexperienced when i started working on it06:25
thiago choose the branch that will have the changes once you're done06:25
RobertWindows that's what i plan on doing long into the future not right now though06:26
squiddle joined06:26
RobertWindows i'm planning on overwriting master with stable, once i get there06:26
thiago why not?06:26
so your target branch is stable06:26
RobertWindows well there's quite a few people using master that like a lot of my changes but06:26
mischat joined06:27
RobertWindows i didn't even follow the projects styleguide because i didn't know what one was06:27
thiago I need simply the name of the branch or the SHA-1 on top of which your new changes should appear06:27
RobertWindows so the code is a complete mess, i really didn't know what i was doing06:27
govg_ joined06:27
thiago find it or choose it06:27
RobertWindows that's where i'm stuck because i want it to be right after #3606:27
govg left06:27
RobertWindows but #36 gives me someone else's history if i use it's sha-106:27
thiago find the last commit that is good06:27
RobertWindows that's why i suggested to rewind06:27
ok06:27
thiago sorry, to be clear: in git log, that's the *first* commit06:28
youngest, most recent06:28
RobertWindows ok that would be06:28
https://github.com/IsmAvatar/LateralGM/pull/25106:28
this one that i just pulled which is06:28
jacksparrow007 joined06:28
RobertWindows 8d0d90306:28
thiago ok, git log. Confirm that it is the commit you want.06:29
dgaleano left06:29
RobertWindows and the oldest on stable by me that is good is 7a1acc106:29
thiago make sure that it has everything you want and that nothing you want is missing06:29
michaelrice left06:29
Sucks left06:29
RobertWindows git log is not showing me any sha-1's but the description of the commit is correct06:30
i know it's good06:30
blckbit10 left06:30
BeatrixKiddo left06:30
thiago git log shows SHA-1s06:30
blckbit10 joined06:30
RobertWindows i can't see it, it's also verbose06:30
when i typed it a second ago it wasn't... odd06:30
thiago it's always visible06:30
durham joined06:30
RobertWindows oh sorry git-bash i couldn't see it in poop brown haha06:30
xaxxon left06:31
mischat left06:31
RobertWindows 91f3fe0a06:31
is the start of it06:31
thiago do a git log 91f3fe0a06:31
confirm that everything you see, you want06:31
then do a git log 91f3fe0a.. (including the two dots)06:31
confirm that everything you see you want to discard06:31
RobertWindows hold up first06:31
https://github.com/IsmAvatar/LateralGM/pull/25106:31
thiago, can you tell me why it shows a different sha-1 than the pr?06:32
thierryp joined06:32
thierryp left06:32
RobertWindows even though the description is correct06:32
thiago no, I cannot. That's a webpage.06:32
it can show anything it wants06:32
RobertWindows oh hang on06:32
RobertBColton merged commit 8d0d903 into IsmAvatar:stable 4 hours ago06:32
rominronin joined06:32
RobertWindows i guess a separate sha-1 is made for pr's?06:32
it looks like it06:32
rkazak left06:33
RobertWindows ok now to do what you said06:33
thiago I don't like github's workflow, so I don't use it06:33
I don't like it *because* it always creates a merge, for each PR06:33
Puhe left06:33
thiago not to mention that their interface is horrible if you want to review a PR that was changed. Horrible as in "impossible, not supported"06:33
so when you use their web interface, you get their commits, plus one06:34
durham left06:34
samw joined06:34
ThomasLocke joined06:34
RobertWindows yeah i understand linus torvalds hates it too06:34
thiago you may need to choose that "plus one" commit (the merge commit), depending on what the state of the contribution was before being merged06:34
RobertWindows heh either way git is pretty complicated06:34
durham joined06:35
RobertWindows thiago, git log with the two dots.. shows me nothing06:35
just exactly like that06:35
do i need the full sha-1?06:35
squiddle left06:35
thiago no06:35
tpollard left06:35
thiago empty means there's nothing to show06:36
Raging_Hog joined06:36
thiago that means you're not excluding anything from your current position06:36
RobertWindows i don't want to just take all my commits and throw them on masters history06:36
*i want to just06:37
rominronin left06:37
thiago are you in the exact state you want master to be?06:37
RobertWindows no06:38
i am on stable, i want to go back and take masters history and replace it with the history on stable06:38
so stable will look like i had masters history and was building on it06:38
thiago rephrasing the question:06:38
if the current state were in master, would you be done?06:38
RobertWindows if all these commits i did in stable were in stable, but with master's history06:39
scoobertron joined06:39
RobertWindows i'd be done06:39
samw left06:39
squiddle joined06:39
thiago ok06:39
so there is a number of commits that are in stable and you want to transfer them to master06:39
is there anything on master you don't want?06:39
RobertWindows no i want master left completely alone06:40
just to import its history to stable06:40
stable is where i want stuff gone06:40
thiago plus your current commits06:40
correct?06:40
RobertWindows yup06:40
exactly06:40
thiago I need you to find the first of the commits you want transplanted06:40
first as in "oldest"06:40
RobertWindows 4fa0748 is the first i made06:41
thiago git log 4fa0748~..06:41
do you see *only* the commits you want transplanted?06:41
atmosx joined06:42
RobertWindows i want between those translate on masters history06:42
thiago yes or no?06:42
zeroed joined06:42
RobertWindows yeah i see the one's i want REPLACED06:43
what i see with that git log is what i want to be replaced with master's history06:43
thiago did you include the dots?06:43
RobertWindows sorry i did git log 4fa0748-06:43
hang on06:43
thiago copy/paste the command exactly06:44
don't forget the dots or the tilde06:44
RobertWindows i see all of my commits plus #36 from that guy06:44
so all of the one's i want transposed to the head of master06:45
thiago so there is one commit you don't want, correct?06:45
RobertWindows yeah that guys that was merged06:45
there's two, the commit and the merge06:45
rchavik left06:45
RobertWindows i want them gone so we have just mine06:45
rchavik joined06:45
thiago did you merge his PR after you began your work?06:45
RobertWindows because #36/his will also be in masters history, there's no reason for us to copy that06:46
thiago, BEFORE06:46
not after06:46
and i didn't merge it someone else did, that's just the part wher ei started in master06:46
thiago it's showing up in your git log, so git says it was after06:46
salamanderrake_ left06:46
RobertWindows decided i didn't want my changes, created a branch and started trying to work at that same point again06:46
thiago do you see any merge commits in that git log?06:46
RobertWindows yes by author ismavatar the repo owner06:47
merged #3606:47
thiago what's the Merge line?06:47
RobertWindows 987b108 b74036a06:47
Merge: 987b108 b74036a06:47
thiago neither is 4fa074806:48
anyway, git says you merged after you began your work, not before06:48
RobertWindows it says 4fa on Commit06:48
thiago here's what you'll do instead:06:48
RobertWindows in poopy brown just the line before Merge06:48
thiago git checkout -b newstable master06:48
localuser- joined06:48
ecELLIOTTCABLE06:48
thiago find the SHA-1 of each of the commits you want to transplant. Then in the order of oldest to most recent, run:06:48
git cherry-pick <sha1>06:49
one by one06:49
hahuang65 joined06:49
squiddle left06:52
foobarn1 joined06:52
hahuang65 left06:54
durham left06:54
durham joined06:55
osse FYI you can do cherry-pick <sha1> <sha1> <sha1>...06:55
Layzie joined06:55
osse I was pretty close to writing cherry-pretty <sha1> <sha2> <sha3>06:55
thiago osse: I'm not sure if that won't reorder the commits basedon actual order06:56
freimatz left06:56
harish left06:57
Layzie left06:57
TomyLobo joined06:57
thiago not to mention that sha2 and sha3 are different algorithms :-)06:57
mohabaks joined06:57
LucaTM joined07:00
osse it doesn't reorder07:01
AtnevRed joined07:02
zarubin left07:02
astockton joined07:03
harish joined07:03
troulouliou_div2 joined07:03
thiago right, thanks07:04
jyjon joined07:04
harish left07:05
localuser- left07:05
localuser- joined07:05
durham left07:05
tvw joined07:05
dfrey left07:06
durham joined07:06
jolts left07:07
AtnevRed left07:07
PCatinean joined07:08
daito left07:08
astockton left07:08
durham_ joined07:09
durham left07:09
blackwind_123 joined07:10
foobarn1 left07:10
zarubin joined07:12
zarubin left07:12
lamppid joined07:13
nnyk left07:13
roelmonnens joined07:14
infra-red joined07:14
dopeddude left07:14
daito joined07:14
squiddle joined07:14
daito left07:14
daito joined07:15
thierryp joined07:15
thierryp left07:16
thierryp joined07:16
terminal_echo left07:16
SimonNa joined07:17
vkngpmhc joined07:18
acolson joined07:18
samw joined07:19
twb joined07:20
foobarn1 joined07:20
twb You know how git log --stat gives a line like .../wobble/gator.algol | 10 +-07:20
rchavik left07:20
twb Is there a way to say "give the full path please, I don't care if it's long"07:20
sheilong joined07:21
mohabaks left07:22
freimatz joined07:22
rchavik joined07:23
samw left07:24
muthu joined07:28
JeroenT joined07:29
foobarn1 left07:29
Wetmelon left07:30
circ-user-TFDGm joined07:30
infra-red left07:32
infra-red joined07:32
Gamecubic left07:32
dfrey joined07:33
Alienpruts joined07:33
mallocthis left07:33
Sceorem joined07:33
rominronin joined07:33
mohabaks joined07:34
TomyLobo left07:35
jnavila joined07:35
raijin left07:37
Goplat left07:38
rominronin left07:38
tdubellzthomas07:39
squiddle left07:39
jacksparrow007 left07:40
foobarn1 joined07:40
jacksparrow007 joined07:40
mischat joined07:42
durham_ left07:44
pantsman- joined07:44
durham joined07:44
ShapeShifter499 left07:46
mischat left07:46
JeroenT left07:47
JeroenT_ joined07:47
pantsman- left07:47
StormLrd joined07:48
p1k joined07:48
nnyk joined07:49
heftig left07:49
heftig joined07:50
petersr joined07:50
eGGsha joined07:50
petersr left07:50
howdoi joined07:53
rominronin joined07:53
roelmonnens left07:53
akmoilt joined07:54
pewu left07:54
osse twb: --stat-name-width=999999907:56
or --stat=45,45 or whatever. see the man07:56
rominron_ joined07:57
baris_ joined07:57
ShapeShifter499 joined07:57
fees joined07:58
rominronin left07:58
akmoilt left07:58
justanotheruser left07:58
tomog999 joined08:00
akmoilt joined08:00
scoobertron left08:00
xaa joined08:01
dan2k3k4 joined08:02
daito left08:02
tomog999_ left08:03
David1977 joined08:03
Zenrium joined08:03
astockton joined08:04
pewu joined08:05
akmoilt left08:05
jam_ joined08:05
dfrey left08:06
irqq joined08:06
StormLrd left08:06
kfunk left08:06
mohabaks left08:07
dreiss left08:07
exarch joined08:07
rchavik left08:08
douglascorrea joined08:08
astockton left08:09
rchavik joined08:09
TomyWork joined08:09
jottr_ joined08:09
tinajohnson__ left08:09
jam_ left08:09
nilsi_ joined08:11
rominron_rominronin08:12
flobin joined08:12
roelmonnens joined08:12
douglascorrea left08:13
twb Thanks08:13
PHPanos joined08:13
jottr_ left08:14
alanwill joined08:14
eijk joined08:14
jnavila left08:14
n00bdev left08:15
nilsi left08:15
hyphenated joined08:16
cripsy joined08:18
rMdes left08:20
cripsy left08:21
cripsy joined08:21
thomas left08:21
durham left08:21
cripsy hi i need help with understanding how tags are used in projects08:21
mrkat joined08:21
RobertWindows left08:21
twb depends on the project08:22
tagging each release is common08:22
daito joined08:22
kfunk joined08:22
nnyk left08:23
nilsi joined08:23
dfrey joined08:24
User458764 joined08:24
harish joined08:24
cripsy are tags specific to branches? Right now im working on lets say development branch and want to create a tagged release and at some point I want to merge this branch to my master branch. I want to know what happens to the tags that I make in development branch08:25
jceb joined08:25
Balliad joined08:25
osse tags don't belong to branches08:25
they are global08:25
twb AIUI a tag is just a name for a particular commit hash08:25
cripsy ok08:26
twb like v4.3~alpha4 = gDEADBEE08:26
_noblegas joined08:26
twb Because humans suck at memorizing hashes08:26
osse a tag can also have its own "author" (tagger) and its own timestamp08:27
and be signed08:27
twb ohhhh yeah08:27
foobarn1 left08:27
cripsy like annoted tags?08:27
nilsi_ left08:27
cripsy annotated*08:27
osse they're called annotated tag,s yes08:28
flobin left08:28
ronny hi08:28
boombatower left08:29
ronny is there a good way to prevent me from commiting to certain branches and/or have pull only remotes?08:29
nnyk joined08:29
cripsy ok thanks osse, twb i got my doubts clear :D08:29
osse ronny: the git:// protocol is read-only so you can use that as the URL08:30
grawity ronny: gitolite has per-branch access control08:30
Macaveli joined08:30
alanwill left08:31
mauricio joined08:31
ronny grawity: im not looking at remote, but local08:31
grawity man githooks08:31
gitinfo the githooks manpage is available at http://jk.gs/githooks.html08:31
ronny osse: does that fit with github?08:31
grawity or, don't create local branches – check out the remote-tracking branches only08:32
thiago ronny: are you pushing to this repository?08:32
alanwill joined08:32
thiago ronny: or do you mean you want to prevent a commit?08:32
osse ronny: i think so08:33
thiago ronny: or do you mean you want github to prevent pushing to certain branches?08:34
dfrey left08:36
sim642 left08:36
clemf left08:36
ronny thiago: i want to prevent local comit to certain branches, and i want to disable pushing branches to a certain repo from my side08:37
dfrey joined08:37
ronny (i still wanto to push tags, jusst no branches)08:37
thiago ronny: ok, two things08:38
ronny we adapted a workflow where all cahnges are brought in via pull requests, and i want to remove the possibility of making misstakes (since i did make one on occasion)08:38
thiago to prevent commits to local branches, you can use the pre-commit hook08:38
just make it fail if the branch is prohibited08:38
if you want to disable pushing to certain branches, you need to configure the remote server08:39
since you said it's github, your question is answered in #github08:39
ronny thiago: is not a feature of the service, bascially i want to restrict git on certain remotes to only push tags08:40
circ-user-TFDGm left08:40
thiago ronny: so, a feature of the service08:40
ronny: if you want to restrict what the server accepts, it's a server config08:40
ronny i want to restrict what my client does, since i dont have enough control over the server and its not sustainable to make a own server08:41
thiago you cannot08:41
mischat joined08:43
circ-user-TFDGm joined08:46
watabou left08:47
alanwill left08:47
mauricio left08:47
alanwill joined08:48
Corosus joined08:49
bjoe2k4_ left08:50
mischat left08:50
acetakwas joined08:51
Corosauce left08:51
sheilong left08:51
Kicer86 joined08:51
jacksparrow007 left08:51
nettoweb joined08:53
bjoe2k4 joined08:53
lindenle joined08:56
circ-user-TFDGm left08:57
squiddle joined08:58
gfixler1 left08:59
Macaveli left08:59
t0by joined09:00
lindenle left09:00
aleksandar2810 joined09:01
encod3 joined09:01
thierryp left09:01
circ-user-TFDGm joined09:01
luke_penn joined09:01
sagittarian joined09:02
thierryp joined09:02
Macaveli joined09:02
AtnevRed joined09:03
alanwill left09:03
astrofog joined09:03
doener joined09:04
alanwill joined09:04
Jellyg00se joined09:04
astockton joined09:05
dfrey left09:06
lmat joined09:06
arnatal joined09:06
Sample left09:06
lmat When I 'git status;', I get "fatal: Not a git repository"09:07
AtnevRed left09:07
kurkale6ka joined09:07
lmat when I ls -d .*; it shows "./ ../ .git/"09:07
The repository worked within the last couple days. the .git folder looks convincing...09:08
moritz do other git commands work?09:08
lmat branches/ COMMIT_EDITMSG config description HEAD hooks/ index info/ logs/ objects/ refs/ ...09:08
moritz: no.09:08
dfrey joined09:08
ShapeShifter499 left09:08
moritz lmat: restore from backup?09:08
osse lmat: env | grep GIT09:08
moritz oh, good thinking09:08
lmat osse: nothing.09:08
TalkToMe joined09:09
squiddle left09:09
astockton left09:10
ahmedelgabri joined09:11
tinajohnson__ joined09:12
lmat I wonder for what git is looking...09:12
PinkPonyOfDeath joined09:12
harish left09:12
Viewtiful joined09:12
lmat I would assume it's just looking for .git/. I would think that if anything in there was amiss, the error would be different.09:12
moritz lmat: you can always run "strace git status" to find out what it tries09:13
Xethron left09:13
lmat moritz: not a bad idea! Installing strace. I'm on archlinux, so that means I'm updating the whole system...I'll let you know in 5 minutes how it went :-/09:15
nnyk left09:15
thomas joined09:17
moritz lmat: 5 miinutes for a whole-system update doesn't sound too bad :-)09:17
alanwill left09:19
TalkToMe left09:19
alanwill joined09:20
ShapeShifter499 joined09:21
daito left09:21
rvsjoen_ left09:23
rvsjoen joined09:24
lmat :-)09:24
User458764 left09:24
lmat ah...09:25
cat .git/HEAD; says "Input/output error"!09:25
elisa87 joined09:25
lmat moritz: (got that from strace)09:25
zadock joined09:26
elisa87 why do I receive this error after git status? fatal: Not a git repository (or any parent up to mount point /afs)09:26
lmat elisa87: DUDE!09:26
moritz lmat: so, broken disk or corrupted file system09:26
lmat moritz: yup. I'll try remounting. as should elisa8709:26
thiago left09:26
circ-user-TFDGm left09:26
elisa87 lmat: moritz I am not really following can you help please?09:26
lmat elisa87: It's because you use Apple Macintosh!09:26
elisa87 I am running this command in Red Hat Linux machines using SSH lmat09:27
luke_penn left09:28
JeroenT joined09:29
JeroenT left09:30
JeroenT_ left09:30
lmat elisa87: Iza just kiddin!09:30
JeroenT joined09:30
sylario joined09:30
marcogmonteiro joined09:31
sbasso joined09:31
localuser joined09:33
clmsy joined09:34
alanwill left09:35
alanwill joined09:36
localuser- left09:37
dsantiago left09:39
blckbit10 left09:39
blckbit10 joined09:39
ftoulemon joined09:39
clmsy left09:40
neunon left09:42
luke_penn joined09:43
fees left09:43
mkoskar joined09:44
madduck left09:44
sgambino joined09:47
mezod joined09:48
quenode left09:48
alexex joined09:48
s8321414 left09:48
alexex Hey guys, can I configure a difftool for git add -p? or is that impossible? And if I can: how?09:48
I researched a little, but I couldnt find anything about this09:49
quenode joined09:49
t4nk873 joined09:49
madduck joined09:50
neunon joined09:51
alanwill left09:51
scoobertron joined09:52
alanwill joined09:52
Seveas alexex: interesting idea, but I don't think you can09:52
User458764 joined09:53
lmat elisa87: oh yeah09:53
elisa87: Try something like cat .git/HEAD; ?09:53
Seveas lmat: no. Never poke in .git manually.09:53
lmat you're joking...?09:54
hyphenated left09:54
Seveas I'm not. The contents of .git are an implementation detail that's subject to change. Use git's commands to get to the data you want (e.g. git rev-parse HEAD)09:54
lmat It seems like a joke, but you're a moderator here? And it might be believable that someone would say that...09:54
Seveas: The data I'm seeking is whether .git/HEAD is readable ^_^09:55
mischat joined09:55
lmat Seveas: And maybe what the error is when attempting to read it.09:55
mase-tech joined09:56
alexex Seveas: too bad, because it also presents you diffs, right? Why shouldnt they display in your favorite tool?09:56
guampa joined09:56
lmat elisa87: I did strace git status; and it suggested that the files aren't readable. I'm re-mounting my mount point09:56
Seveas lmat: it having become unreadable can only be a result of poking in .git manually, so don't do that :)09:56
alexex: that's why I said "interesting idea" :)09:57
osse or file system corruption, or hardware faults, or...09:57
lmat Seveas: Not at all! I think my mounted drive had a problem, or the mount failed or something09:57
jacksparrow007 joined09:57
squiddle joined09:57
lmat Seveas: I just removed some drywall in that room... perhaps I git the drive (which is pretty close to the ceiling) :-o09:57
leonarth joined09:58
Seveas git drywall --crumble09:58
n00bdev joined09:58
osse if cat can't read .git/HEAD then Git probably can't eiter09:58
lmat Seveas: ^_^09:59
Seveas: In short, I would agree with you if you said "never modify anything 'manually' in .git". since cat is only reading, no problem.09:59
rnsanchez joined10:00
victortyau joined10:00
Guest96230 joined10:01
alexex Seveas: okay, so thanks anyways :-)10:01
Guest96230 left10:01
Guest96230 joined10:01
TalkToMe joined10:02
Guest96230aidalgol`10:02
aidalgol`aidalgol10:02
alexex left10:02
mezod left10:03
Urcju joined10:04
Urcju left10:05
spinningarrow joined10:05
astockton joined10:05
gitinfo set mode: +v10:06
ferr joined10:06
jam_ joined10:06
localuser- joined10:07
sgambino left10:07
alanwill left10:07
alanwill joined10:08
josue joined10:10
vkngpmhc left10:10
jottr_ joined10:10
Hounddog joined10:10
astockton left10:10
douglascorrea joined10:10
localuser left10:10
jam_ left10:10
woev joined10:11
woev left10:11
jnavila joined10:12
flavi0 joined10:14
fees joined10:14
User458764 left10:14
douglascorrea left10:15
blackwind_123 left10:15
jottr_ left10:15
josue left10:15
josue joined10:16
josue left10:16
totte joined10:16
hyphenated joined10:17
Macaveli left10:17
squiddle left10:17
dsdeiz left10:18
josue joined10:18
nilsi left10:19
n00bdev left10:19
jyjon left10:20
jnavila_ joined10:20
josue left10:21
jnavila left10:21
Atm0spher1c left10:21
daito joined10:22
josue joined10:22
thierryp left10:23
circ-user-JJNIJ joined10:23
alanwill left10:24
alanwill joined10:25
notebox joined10:25
josue left10:26
daito left10:27
madebymarkca left10:27
josuebrunel joined10:29
josuebrunel left10:31
samskiter joined10:32
dancinggrass joined10:33
gitinfo set mode: +v10:33
powered joined10:33
ferr left10:34
Hounddog left10:36
Peng_ joined10:36
josuebrunel1 joined10:37
josuebrunel1 left10:37
bollullera joined10:38
astrofog left10:38
josuebrunel joined10:38
josuebrunel left10:38
Talk_To_Me joined10:40
spinningarrow left10:40
alanwill left10:40
tlaxkit joined10:40
bitkiller joined10:40
josuebrunel joined10:40
Peng_ left10:40
alanwill joined10:41
durham joined10:41
TalkToMe left10:41
nettoweb left10:44
nettoweb joined10:45
Talk_To_Me left10:45
sgambino joined10:46
TalkToMe joined10:46
TalkToMe left10:47
victortyau left10:47
TalkToMe joined10:48
dsantiago joined10:50
TalkToMe left10:50
dgriffi joined10:50
clmsy joined10:50
junw joined10:51
t4nk873 left10:51
muthu_ joined10:51
muthu left10:52
aidalgol left10:52
harish joined10:53
Wetmelon joined10:54
courrier joined10:55
tvw left10:55
alanwill left10:56
acetakwas left10:56
dan2k3k4 left10:56
ac3takwas joined10:56
diogenese left10:57
alanwill joined10:57
lindenle joined10:57
ac3takwas left10:58
Jellyg00se left10:58
ac3takwas joined10:58
aleksandar2810 left10:58
ac3takwas left10:59
ac3takwas joined11:00
marscher joined11:00
aleksandar2810 joined11:01
ac3takwas left11:01
dgriffi I've used git rebase to remove some commits, but even after doing git push origin -f, those commits are still being referenced in a Github issue. how do I delete those once and for all?11:01
ac3takwas joined11:02
lindenle left11:02
ac3takwas left11:02
AtnevRed joined11:04
powered these commits are removed from the repository, but still referenced by the github issue?11:04
sounds like a github issue11:04
a issue issue11:04
samw joined11:05
hyphenated left11:06
aleksandar2810 left11:06
astockton joined11:06
dfrey left11:07
elisa87 left11:07
AtnevRed left11:08
fees left11:08
twb left11:09
fees joined11:09
samw left11:09
harish_ joined11:09
harish left11:09
harish_ left11:09
infra-re_ joined11:09
harish joined11:10
Zenrium left11:11
User458764 joined11:11
denn1s_ joined11:12
alanwill left11:12
astockton left11:12
infra-red left11:13
JeroenT left11:13
bronson joined11:13
jorj joined11:13
xvx joined11:13
StormLrd joined11:14
fracting left11:14
fracting joined11:15
interrobangd joined11:16
cannonball left11:17
aleksandar2810 joined11:18
bronson left11:18
kristofferR joined11:18
diogenese joined11:18
dfrey joined11:19
mkoskar left11:19
akushner joined11:19
m0ltar joined11:20
n00bdev joined11:20
codeman joined11:21
infra-red joined11:22
zadock left11:22
leeN left11:23
raijin joined11:24
akushner left11:24
denn1s_ left11:24
n00bdev left11:24
infra-re_ left11:24
denn1s_ joined11:24
akushner_ joined11:25
et0r joined11:25
leonarth left11:25
dgriffi powered: is there a way I can also remove these commits from my local repo without simply deleting it and doing "git clone" of my stuff on github?11:25
leonarth joined11:26
osse dgriffi: if you did what you said then they are gone from your local repo11:26
powered didn't you delete these commits in the local repo to begin with?11:26
or a different local repo?11:26
akushner joined11:29
akushner_ left11:29
akushner__ joined11:29
Guest59176 left11:30
akushner__ left11:30
dgriffi osse: I can still get to them by their SHA111:30
osse dgriffi: git gc11:30
infra-re_ joined11:30
dgriffi osse: didn't get rid of them11:30
osse gti reflog expire --all --expire=all && git gc --prune=all11:30
_ikke_ Note that you loose your reflog with this11:31
osse but I don't see the point. Either they will go away eventually, or they will and should never go away11:31
Fijit joined11:31
atmosx left11:31
akushner_ joined11:31
aleksandar2810 left11:32
powered yes only if you deliberately bring them back11:32
_ikke_ and git clone will not send those objects11:32
neither will git fetch11:32
scoobertron left11:33
infra-red left11:33
dgriffi can someone deliberately clone or fetch those SHA1s?11:33
osse no11:33
powered but you said they were referenced from github? that means they're already out there in the wild11:34
osse depends on how github references them11:34
acetakwas joined11:34
dgriffi at this point being referenced from github is a minor irritation.11:34
_ikke_ Executing gc locally will not expire them on github either11:34
osse if there is an actual ref (in git terms) for the issue then it won't go away.11:34
blckbit10 left11:34
_ikke_ I think it's just a link11:35
osse if it's just a direct link to a blob or whatever then that link might become invalid soon11:35
dgriffi I imagine this is something the github admins can manually fix11:35
osse I assume github purges crap quite often11:35
zarubin joined11:35
dgriffi well, here's the issue that's annoying me: https://github.com/DavidGriffith/inform6lib/issues/2511:35
powered I meant there was a point in time where these commits were in the public repository, so anyone could've downloaded them11:36
aleksandar2810 joined11:36
dfrey left11:36
dgriffi powered: there's no security problem. I just don't want people asking me about those commits.11:36
_ikke_ I don't know whether github sees that as an active reference11:36
acetakwas left11:37
powered ok in that case you've got nothing to worry about anymore11:37
Jusle joined11:37
acetakwas joined11:37
dgriffi so I'll just do the fix the Right Way locally and then wait for the github admins to fix the mess in my commit?11:38
osse i cloned the repo and that commit is not in it11:38
dgriffi osse: right. I want to avoid the potential annoyance of you looking at Issue 25 and pestering me about commit 33255271f5aca093597f080f12df7d03ca12882311:39
et0r left11:39
osse can't you delete that comment fro mthe issue thread or something like that?11:39
_ikke_ dgriffi: That you have to arrange with github11:39
dgriffi osse: tried already11:40
osse: like _ikke_ suggested, I sent a message to the admins to help me out.11:40
I guess I'm done11:41
thanks guys.11:41
osse my guess is that link will be a 404 pretty soon11:41
_rgn left11:41
blckbit10 joined11:41
User458764 left11:42
_ikke_ The link to the comment you mean?11:42
hackel left11:42
_ikke_ commit*11:42
https://github.com/DavidGriffith/inform6lib/commit/33255271f5aca093597f080f12df7d03ca12882311:42
osse yes11:43
pewu left11:43
kristofferR left11:44
akushner left11:44
acetakwas left11:45
HanClinto__ left11:46
User458764 joined11:46
lambainsaan_ left11:46
pewu joined11:47
neanderslob left11:48
JeroenT joined11:48
KennosiS left11:48
akushner_ left11:48
akushner_ joined11:49
samskiter left11:49
akushner joined11:50
tvw joined11:51
Vile left11:52
dfrey joined11:52
cxz joined11:53
askhat joined11:54
Vile joined11:54
cxz left11:54
Vile left11:55
sgambino left11:57
KennosiS joined11:57
mauricio joined11:59
samskiter joined11:59
askhat left12:00
lambainsaan_ joined12:00
HanClinto__ joined12:01
lambainsaan_ left12:01
lambainsaan_ joined12:02
KennosiS left12:02
lambainsaan_ left12:02
dsdeiz joined12:03
mellernoia joined12:04
zzz joined12:04
zzzGuest5230512:04
cxz joined12:05
lambainsaan_ joined12:05
dfrey left12:05
lambainsaan_ left12:06
jottr_ joined12:06
lambainsaan_ joined12:07
jam_ joined12:07
raijin left12:07
lambainsaan_ left12:07
lambainsaan_ joined12:08
lambainsaan_ left12:09
lambainsaan_ joined12:09
StormLrd left12:10
lambainsaan_ left12:10
lambainsaan_ joined12:11
jam_ left12:11
User458764 left12:11
lambainsaan_ left12:11
Viewtiful left12:15
_rgn joined12:16
_rgn left12:16
_rgn joined12:16
blckbit10 left12:17
blckbit10 joined12:17
fracting left12:19
deltab left12:20
Viewtiful joined12:20
n00bdev joined12:20
acetakwas joined12:21
fracting joined12:22
dfrey joined12:22
localuser joined12:23
daito joined12:23
Juzzika joined12:23
ferr joined12:24
ahmedelgabri left12:24
acetakwas left12:25
Manikandan left12:25
n00bdev left12:25
localuser- left12:27
deltab joined12:27
daito left12:27
Viewtifu_ joined12:28
sbasso_ joined12:29
localuser left12:29
sylario_ joined12:30
oliva left12:30
s8321414 joined12:30
jottr joined12:30
codedmart joined12:30
KaibaCorp joined12:30
justanotheruser joined12:31
mohabaks joined12:33
mostlybadfly_ joined12:33
sylario left12:34
nidr0x left12:34
kaiza left12:34
Viewtiful left12:34
sbasso left12:34
davidosomething left12:34
mase-tech left12:34
Sceorem left12:34
mostlybadfly left12:34
iera left12:34
SirCmpwn left12:34
jottr_ left12:34
Guest52305 left12:34
mariuscc left12:34
sylario_sylario12:34
iera joined12:34
SirCmpwn joined12:34
mase-tech joined12:34
mostlybadfly_mostlybadfly12:34
SimonNa left12:34
davidosomething joined12:35
oliva joined12:36
KennosiS joined12:37
dfrey left12:37
Arsonide joined12:39
Raging_Hog left12:39
cagedwisdom left12:40
dfrey joined12:40
mariuscc joined12:41
cebor left12:41
HanClinto__ left12:41
David1977 left12:41
KennosiS left12:42
acetakwas joined12:42
David1977 joined12:43
Raging_Hog joined12:43
ahmedelgabri joined12:43
KennosiS joined12:44
cebor joined12:45
simonlinj joined12:47
Arsonide left12:48
rnsanchez_ joined12:50
mizu_no_oto joined12:50
dsdeiz left12:50
dsdeiz joined12:50
jottr left12:51
MutantMahesh left12:52
jottr joined12:52
FunkyAss joined12:52
rnsanchez left12:53
ki0 joined12:54
douglascorrea joined12:54
Juzzika left12:54
Juzzika joined12:54
diogenese left12:56
durham left12:56
zzz joined12:58
zzzGuest1107012:58
fstd left12:59
mohabaks left12:59
fstd joined13:00
fahadash joined13:01
fahadash left13:01
fahadash joined13:01
fahadash left13:01
fahadash joined13:01
clmsy left13:02
hobodave joined13:03
raijin joined13:04
AtnevRed joined13:05
localuser- joined13:05
dfrey left13:06
jacksparrow007 left13:06
rclanan joined13:06
jacksparrow007 joined13:06
Juzzika left13:07
jnavila_ left13:07
mahendra_ joined13:08
rwb joined13:09
astockton joined13:09
AtnevRed left13:09
localuser- left13:09
localuser- joined13:09
mizu_no_oto left13:10
rclanan left13:11
jeffreylevesque left13:13
astockton left13:14
mkoskar joined13:14
nilsi joined13:17
dfrey joined13:18
Viewtifu_ left13:20
n00bdev joined13:21
the_cybersphinx left13:21
the_cybersphinx joined13:22
Viewtiful joined13:22
Viewtiful left13:22
Viewtiful joined13:22
synthroid joined13:23
hyperair joined13:24
Jellyg00se joined13:24
n00bdev left13:27
jkoudys joined13:27
aleksandar2810 left13:28
tomog999_ joined13:28
tomog999 left13:31
cbruegge joined13:31
circuitCarre joined13:31
jeffreylevesque joined13:32
mezod joined13:33
AndChat|262656 left13:33
notebox left13:34
oxsyn left13:34
sonOfRa left13:35
BtbN left13:35
Sephyros left13:35
denn1s_ left13:35
BtbN joined13:35
sonOfRa joined13:35
cbruegge left13:36
dfrey left13:36
croc left13:36
bloony left13:36
croc joined13:36
ahmed_elgabri joined13:37
ferr left13:37
ash_workz joined13:37
croc left13:38
denn1s_ joined13:38
croc joined13:38
presto joined13:39
denn1s_ left13:39
luke_penn left13:39
ahmedelgabri left13:39
jaguarmagenta joined13:43
samskiter left13:44
fscala left13:44
denn1s_ joined13:44
samskiter joined13:44
liranp joined13:45
jaguarmagenta2 left13:45
fscala joined13:46
sdothum joined13:46
circuitCarre left13:46
denn1s_ left13:46
bellxs joined13:46
mblack joined13:47
StormLrd joined13:49
Rodya_ joined13:50
samskiter left13:51
s8321414 left13:51
denn1s_ joined13:51
circ-user-JJNIJ left13:52
jimi_ joined13:52
circ-user-15GfU joined13:52
infra-red joined13:52
dfrey_ joined13:52
algae joined13:52
samskiter joined13:52
jimi_ left13:53
mohabaks joined13:53
shekhar_ joined13:53
cachwir joined13:53
denn1s_ left13:54
infra-re_ left13:54
ag4ve joined13:55
acetakwas left13:55
cachwir Hi ! I'm new on git and I'm trying to clone a project using ssh. I created my public key and a config file in the .ssh directory with the informations about the host where I want to clone the repository from. However, when I try to use git clone repositoryurl, I get the error ssh: connect to host **************** port 22: Connection timed out13:56
fatal: Could not read from remote repository.13:56
eGGsha left13:56
Rodya_ left13:56
jimi_ joined13:57
Juzzika joined13:57
cachwir The project manager told me he created an account for me on git, gave me the login and added that I didn't need any password because the key would authenticate me. However, I don't really know what he means by creating an account on git (did he mean github ?) and I don't know what to do to connect to that account through git. :/13:57
canton7 cachwir, your repositoryurl is wrong13:58
... or something's blocking port 2213:58
m0ltar left13:58
linfaimom joined13:58
chris_wotchris_wot_away13:59
cachwir Don't I need to connect somewhere ? Or give a login ? :/13:59
Are you sure it's a problem with the repositoryurl or the port ?14:00
canton7 "ssh: connect to host"14:00
localuser- left14:00
canton7 ssh could not establish a connection with the machine you specified14:00
lindenle joined14:00
canton7 git's completely irrelevant at this point14:00
localuser- joined14:00
canton7 bit like saying "google's broken" because your wifi's died and you can't connect to the internet :P14:00
cachwir lol ok. That's before even checking account permissions. ^^14:01
canton7 yep. it couldn't even establish a connection14:01
cachwir Thanks canton7, I understand a bit more now. :)14:02
canton7 :)14:02
cripsy left14:03
cachwir canton7, I just realized something14:03
in the config file, the writte port isn't 2214:03
notebox joined14:04
cachwir written*14:04
Rodya_ joined14:04
jbudz joined14:04
cachwir How come git clone uses the port 22 ?14:04
jabular joined14:04
lindenle left14:04
canton7 I'll need to see both the config file and the 'git clone' command you're using14:04
(edit out stuff if you need to)14:04
Juzzika left14:05
Raging_Hog left14:05
cachwir Well, I can't show you everything, but I can at least show you what it looks like14:05
rchavik left14:05
denn1s_ joined14:05
cachwir Host *************14:05
User git14:05
HostName **********14:05
Port ****14:05
PreferredAuthentications publickey14:05
IdentityFile /home/cachwir/.ssh/id_rsa14:05
canton7 pastebin, please14:05
jacksparrow007 left14:05
cachwir oh sorry, yes14:05
canton7 please don't just use *'s for everything - I'm looking for if particular strings in the config file and 'git clone' match14:06
and it's hard to do that with '*'s :P14:06
oxsyn joined14:07
mohabaks left14:07
zenpac joined14:07
jam_ joined14:08
cachwir Well, I can tell you that the git clone command looks like something like that : sudo -i git clone git@Host:games/somegame.git14:08
lj1102 joined14:08
jbudz left14:08
cachwir where Host is the same as the Host name in the config file14:08
canton7 where 'Host' is literally 'Host', and not 'some.host.com'?14:08
livingstn joined14:08
cachwir it's writtent like some.host.com14:08
dfrey_ left14:08
cachwir written*14:08
Tropit joined14:08
canton7 this is hopeless14:09
zenpac In a feature/xyz branch created by user Joe, Then Joe creates a Pull Request on github. Can another user add to that feature and have it show up in the PR?14:09
dsdeiz left14:09
zenpac I suppose that is Github-centric question?14:09
canton7 cachwir, the 'Host' line in the ssh-config file needs to match the url you're cloning from. Does it?14:09
cachwir yes, it does14:09
tinajohnson__ left14:09
astockton joined14:10
canton7 and in the error " error ssh: connect to host **************** port 22: Connection timed out", is the *********** equal to the HostName value in the ssh-config file?14:10
daito joined14:10
denn1s_ left14:10
cachwir yes, but not the port. However, the file is just called config, not ssh-config14:11
canton7 .ssh/config, yeah14:11
blckbit10 left14:11
cdg joined14:11
canton7 is it a debian-based system?14:12
cachwir Yes14:12
I'm on Linux Mint14:12
canton7 ah no, the bug I found wasn't relevant14:12
try 'ssh Host' - does that connect?14:12
blckbit10 joined14:12
jam_ left14:13
denn1s_ joined14:13
sgambino joined14:13
acetakwas joined14:13
cachwir yes, it does14:13
hobodave left14:13
dances-with-cats joined14:13
Code_Bleu left14:14
canton7 ooh I missed the sudo14:14
why sudo?14:14
denn1s_ left14:14
canton7 does 'sudo -i ssh Host' work?14:14
daito left14:15
cachwir Oh, that's because I'm in a protected folder14:15
astockton left14:15
rkazak joined14:15
Code_Bleu joined14:15
chll joined14:16
canton7 ..?14:16
interrobangd left14:16
t4nk190 joined14:16
cachwir Weird. When I go sudo -i ssh Host, it does nothing14:17
do*14:17
powered left14:17
canton7 yeah, 'cos that sudo command runs the login shell of the target user14:17
which changes $HOME, which changes where it looks for .ssh/config14:18
jottr left14:18
cachwir Ooooh I see14:18
mizu_no_oto joined14:18
canton7 So the answer to "<canton7> and in the error " error ssh: connect to host **************** port 22: Connection timed out", is the *********** equal to the HostName value in the ssh-config file?" is probably actually "no", not "yes"14:18
bbbthunda joined14:19
cachwir Well, I just tried in another folder with just git clone (no sudo -i) and I still get the same error14:19
wait no14:19
canton7 so we've got to a point where 'git clone user@Host' fails to connect, but 'ssh user@Host' does connect?14:20
cachwir I get this error this time14:20
GitLab: The project you were looking for could not be found.14:20
fatal: Could not read from remote repository.14:20
Please make sure you have the14:20
canton7 right, completely different14:20
it's now connected, but either you don't have access to that repo, or the repo doesn't exist14:20
rkazak left14:20
canton7 (I can't tell since you truncated the message)14:20
cachwir (and the repository exists.14:20
)14:20
canton7 "Please make sure you have the (and the repository exists)"?14:21
Joel left14:21
cachwir oh sorry14:21
dfrey_ joined14:21
cachwir The correct access rightds14:22
canton7 ok, so like I said14:22
wrong repo, or bad key14:22
cachwir When you say key, would it be my public key I gave him ?14:22
tropit_ joined14:23
canton7 so you're not providing the private part to the public key you gave him. or you're giving the wrong repo name. or he set things up wrong.14:23
n00bdev joined14:23
rnsanchez_rnsanchez14:24
qpdb left14:25
modocache joined14:26
Ph_ left14:26
gitinfo set mode: +v14:26
moriko joined14:26
sparetire joined14:27
localuser- left14:27
subhojit777 joined14:28
qpdb joined14:28
tropit_ Hey, somone maybe know how i can apply stash and pass over conflicts?14:28
n00bdev left14:28
cachwir Ok. Thanks a lot canton7. :)14:28
You helped a bunch14:28
canton7 one trick is to run 'ssh -vvv git@Host' and see what keys it gives14:29
ChanServ set mode: +o14:29
qsx set mode: +v14:29
qsx you have the same amount of letters in your nick and get the same color here. i can’t distinguish you.14:29
+v-o qsx qsx14:30
qsx set mode: +v14:30
qsx set mode: -o14:30
ChanServ set mode: -v14:30
victortyau joined14:30
canton7 I don't like being marked as one of those non-registered peasants ;)14:31
codeman left14:31
CheckDavid joined14:32
eijk left14:32
qsx :<14:32
happy-dude joined14:33
ChanServ set mode: +v14:34
ChanServ set mode: +v14:34
Joel joined14:35
dfrey_ left14:36
Ph_ joined14:36
mostlybadfly left14:37
JohnBat26 joined14:38
jwmann left14:39
ruskie left14:39
PaulCapestany left14:40
PaulCapestany joined14:41
samw joined14:41
Dougie187 joined14:41
al-damiri joined14:41
Gsham joined14:42
dfrey_ joined14:42
Treio joined14:42
IdanM joined14:43
samw left14:46
cyan__ joined14:46
Gsham left14:46
codeman joined14:48
Gamecubic joined14:48
simonlinj left14:49
Juzzika joined14:49
xvx left14:49
squiddle joined14:51
sbasso_ left14:52
codeman left14:52
localuser- joined14:52
simonlinj joined14:52
dances-with-cats left14:52
acetakwas left14:53
ruskie joined14:54
ianclark joined14:54
AaronMT joined14:56
squiddle left14:57
grc joined14:57
achadwick joined14:58
marscher left14:58
nettoweb left14:58
rscata left15:00
MeltedLux left15:00
mauricio left15:01
alanwill joined15:02
David1977 left15:03
mohabaks joined15:03
starsinmypockets joined15:03
BigWillie joined15:03
Code_Bleu left15:04
JanC left15:05
ag4ve left15:05
AtnevRed joined15:05
glebihan left15:06
dances-with-cats joined15:06
starsinmypockets I have kaleidoscope set up with ksdiff which is great but... does anyone know if there is a way to see merge conflicts (>>>> ==== <<<<) in a single file in a comparison view?15:06
Code_Bleu joined15:07
Gsham joined15:07
s00pcan joined15:07
jacksparrow007 joined15:08
lmatteis joined15:08
infra-red left15:08
hyperair left15:09
starsinmypockets Oh fu%k it I'm just gonna learn vimdiff15:10
localuser joined15:10
AtnevRed left15:10
githogori left15:10
j416 starsinmypockets: in a single file? just open the conflicted file.15:11
astockton joined15:11
JeroenT left15:11
hyperair joined15:13
localuser- left15:14
jottr joined15:15
astockton left15:15
douglascorrea left15:15
RedShift joined15:16
JeroenT joined15:16
alanwill left15:17
nofacade joined15:18
alanwill joined15:18
dixvagon joined15:18
freimatz left15:18
bb010g left15:18
sgambino left15:19
phaleth joined15:19
sgambino joined15:19
JanC joined15:20
The_Phoenix joined15:21
lj1102 left15:21
ki0 left15:22
freimatz joined15:23
nilg left15:24
n00bdev joined15:24
dixvagon left15:25
jottr left15:26
samskiter_ joined15:27
samskiter left15:27
samskiter_samskiter15:27
dixvagon joined15:28
acetakwas joined15:29
n00bdev left15:29
User458764 joined15:29
jeffreylevesque left15:30
cachwir left15:30
dixvagon left15:30
dixvagon joined15:31
coderMe joined15:31
jeffreylevesque joined15:31
dances-with-cats left15:31
rominronin left15:32
acetakwas left15:32
starsinmypockets left15:32
diegoaguilar joined15:33
alanwill left15:33
acetakwas joined15:33
alanwill joined15:34
acetakwas left15:34
douglascorrea joined15:35
diegoaguilar left15:35
diegoaguilar_ joined15:35
linfaimom left15:35
t4nk190 left15:36
tropit_ left15:36
GaboFDC joined15:36
MissWeb joined15:36
Tropit left15:37
shinnya joined15:38
dixvagon left15:38
sgambino left15:42
sgambino joined15:42
aleksandar2810 joined15:42
cbonobo joined15:44
aleksandar2810 left15:44
italoacasas joined15:44
jacksparrow007 left15:44
mohabaks left15:45
italoacasas left15:45
Alienpruts left15:45
jacksparrow007 joined15:45
geoid joined15:45
italoacasas joined15:46
aleksandar2810 joined15:46
ferr joined15:46
coderMe left15:46
ash_workz left15:46
endiruna joined15:47
alanwill left15:49
Ahmed90 joined15:49
jacksparrow007 left15:49
Treio left15:49
linfaimom joined15:50
alanwill joined15:50
nd left15:51
The_Phoenix left15:51
mase-tech left15:51
hackel joined15:51
muthu_ left15:53
MissWeb left15:53
MisterWeb joined15:54
in3xes joined15:54
JohnBat26 left15:54
lamppid left15:54
bellxs left15:55
gitinfo set mode: +v15:55
MisterWeb Instead of submodules, can I just have a repository within a repository, and ignore the "sub-repository" using .gitignore of the parent repository? Then I could just maintain the two repositories separately, and use Gulp tasks to install the sub-repository as necessary when deploying. Thoughts?15:55
Noldorin joined15:55
osse it's doable15:55
I have done so in the past15:55
squiddle joined15:55
JeroenT left15:56
sheilong joined15:56
nofacade left15:56
Sucks joined15:57
kilo_bravo joined15:57
devth joined15:58
kpease joined15:59
jacksparrow007 joined15:59
IdanM left15:59
weox joined16:00
acolson left16:00
dmto joined16:00
devth_ left16:01
bango2 joined16:03
bango2 left16:03
Guest72094 left16:03
Guest72094 joined16:03
Guest72094kenansulayman16:03
bango2 joined16:04
leprechau left16:04
aleksandar2810 left16:04
reim left16:04
alanwill left16:05
dixvagon joined16:05
editshare-ericf joined16:06
alanwill joined16:06
mkoskar left16:07
denisMone joined16:07
jason237 joined16:08
jam_ joined16:08
acetakwas joined16:09
kazantip left16:09
leprechau joined16:10
Eugene MisterWeb - yup, just gitignore the inside one. !subrepos even suggests it ;-)16:10
gitinfo MisterWeb: [!subprojects] So, you want to add git repositories inside of other git repositories? Well, you have four main options. First is to just do it, add the repo to the outer project's .gitignore, and treat them entirely separately. Best if they are entirely separate. Otherwise your best options are "!submodule", "!gitslave", and "!subtree". Try those commands in this channel, or in a PM to avoid flooding.16:10
nnyk joined16:10
infra-red joined16:11
daito joined16:11
shinnya left16:12
eijk joined16:12
astockton joined16:12
aranea joined16:13
jam_ left16:13
keltvek joined16:13
blackwind_123 joined16:13
pjh joined16:13
pjh left16:14
acetakwas left16:14
pjh joined16:14
daito left16:15
roelmonnens left16:16
p1k left16:16
beerandpizza left16:17
Es0teric joined16:17
mrkat left16:17
ferr left16:17
IrishPrime joined16:18
dreiss joined16:18
pjh Hi all, I'm trying to use tags for different versions of my co-workers source code. This paragraph of the git-scm docs is confusing me. "Of course if you do this and do a commit, your version2 branch will be slightly different than your v2.0.0 tag since it will move forward with your new changes, so do be careful."16:18
leprechau left16:19
pjh Does anyone know what that means? If I tag a commit as version2, I wont ever get that version back?16:19
osse yes16:19
but *that* commit will become version216:19
aleksandar2810 joined16:19
pjh So what are the point of tags in that case?16:19
osse if you make further commits those will version3-beta16:20
UTAN_dev_ left16:20
pjh Hmm, sorry I must have the context in my head wrong. I'm still not understanding.16:20
osse tags are for when you are done. the code is released. the CDs made. the manual written. the packaging shipped.16:20
don't create a tag named version2 until version2 is done.16:21
squiddle left16:21
alanwill left16:21
osse tags work this way so that in ten years when you're working on version14 and the app has been rewritten five times you can still get version2 *exactly* the way it was way back when.16:22
pjh Lets say I have a commit ed1235, I tag that v1.0. then I make a number of commits later and I want to call commit 3dxh1, v2.0. Can I ever reach the same commit state as the tag v1.0? As in if I checkout v1.0, I will have the same files as I did in that commit?16:22
qyjxmx joined16:22
alanwill joined16:22
pjh I see.16:22
osse if you git checkout v1.0 you get the files as they are in ed123516:23
pjh okay. thanks for confirming.16:23
that line I quoted threw me off16:23
Juzzika left16:23
osse pjh: it sounds like the quote is talking about a *branch* named version2 and then you at some point create a tag v2.0.016:24
leprechau joined16:24
mrkat joined16:24
osse and it's completely true that if you create the tag, and then *afterwards* create new commits they won't be part of the contents that were tagged16:24
pjh +osse: Ah, sorry. The context of that quote was at the bottom of this page. https://git-scm.com/book/en/v2/Git-Basics-Tagging16:24
nofacade joined16:25
cagmz joined16:25
osse yeah if you create a branch at the point of an existing tag the usual case is for when you need to fix a bug or create some sort of hotfix16:25
n00bdev joined16:25
pjh so its essentially saying " If you checkout a tag into a new branch, make changes to that branch. the new branch will still have the tag but it wont be the original commit"16:25
so the tag will stay attached to the branch?16:26
osse no16:26
tags aren't attached to branches16:26
you attach them directly onto commits16:26
pjh sorry, I meant commits. but I assume the answer is still no.16:26
osse there is no way to modify a tag or modify what is tagged once the tag has been created16:27
clemf joined16:27
pjh lets say the commit is ed1235 tagged v1.0. I checkout a new branch from that tag, make a commit. the tag v1.0 is still on commit ed1235 right?16:27
osse yes16:27
pjh okay. thanks!16:27
osse forever and ever16:27
unless you delete it of course16:28
pjh my coworker has never used git. he asked me to put his project into a git repo.16:28
MisterWeb left16:28
pjh it looks like this:16:28
madewokherd left16:28
pjh Folder/16:29
version 1/16:29
version 1.1/16:29
nd joined16:29
pjh all the way to 2.40/16:29
=(((((((((((16:29
synthroid left16:29
osse I have only once in my life seen anything worse than that. I believe it was called "tubgirl"16:29
mallocthis joined16:30
samw joined16:30
pjh haha16:30
n00bdev left16:30
osse Just kidding. git init; copy all files from 1, commit it, tag it. then wipe the dir. copy files from 1.1. commit it, tag it. repeat.16:30
no biggue16:30
User458764 left16:30
hobodave joined16:31
pjh i was thinking tags are the best way of doing this. but he was telling me about using a branch for each version16:31
osse yeah... no.16:31
pjh I wonder if I could write a bash script for tagging it.16:31
Balliad left16:33
EdwardIII joined16:34
grc` joined16:34
osse mkdir repo; cd repo; git init; for v in 1 1.1 1.2 ... 2.40; do cp -R "/somewhere/Folder/version $v"/* .; git add --all; git commit -m "Import of version $v"; git tag -a "$v" -m "Version $v"; git rm -r .; done; git checkout master16:34
pjh: you mean like that?16:34
EdwardIII hrm i'm going nuts. i can do 'git format-patch sha1^..sha1' and it works fine. i do 'git format-patch sha1..sha1^' it outputs nothing16:34
samw left16:34
EdwardIII i just want to reverse a change from a commit ages ago, temporarily16:35
pjh +osse: yes, but I have to grab the correct version numbers they dont increment consistently, there is version 1.1 then 1.15 then 1.2 then 1.316:36
things like that16:36
very strange16:36
aranea left16:37
jceb left16:37
osse pjh: no problem. for x in a b 453 hello world sgfaeg cupboard 69 1337; do echo "$x"; done16:37
pjh so I have to store the folder name in some variable then grep it for the version number16:37
gmichael left16:37
grc left16:37
pjh sorry, regex16:37
osse ah. I think i'd "hard-code" that part16:37
thiago joined16:37
osse unless there are 250 of them16:37
pjh there are almost that number16:37
courrier left16:37
alanwill left16:38
courrier joined16:38
courrier left16:38
jacksparrow007 left16:38
courrier joined16:38
leeN joined16:38
jacksparrow007 joined16:38
UTAN_dev joined16:38
NeverDie joined16:38
osse all_versions=("/somewhere/Folder/version "*); version_numbers=( "${all_versions[@]##*version }" ); for v in "${version_numbers[@]]}"; do cp ... git ...; done16:38
grc` left16:39
osse ask #bash for more16:39
pjh will do, thanks +osse16:39
frem joined16:39
osse if you ls | grep so help me god I will hunt you down16:39
gmichael joined16:39
pjh hahahaha, noted!16:39
chitopunk joined16:40
geoid left16:40
osse pjh: anyway, I guess you don't have any more meaningful history of the project than this, so I'd create one commit for each chunk of code. Then I would create a tag for each. For the tag message I guess you can put in some useful information if you have any16:41
chris2 would changing GIT_WORK_TREE and using git -A be easier?16:42
osse if you really want to pour your heart into it you can even make it so the commits have sensible dates and author and such16:42
michelangelo joined16:42
brandonw left16:42
osse chris2: that is the best idea I've heard in mylife16:42
that's MUCH easier16:42
courrier Hey guys, I'm using the command below to get rid definitely of the history of some files (pruning resulting empty commits):16:42
joki left16:42
joki joined16:42
chris2 osse: untested16:42
courrier git filter-branch --tag-name-filter cat --index-filter "git rm -r --cached --ignore-unmatch $FILES_TO_DELETE" --prune-empty -f -- --all16:43
chris2 osse: but i wanted such a script too for a long time16:43
courrier but how to also delete the history of files already deleted? --ignore-unmatch should avoid returning an error but then filter-branch does not suppress the history of the old file...16:43
osse chris2: could even use a temporary GIT_INDEX so there's no need to do the git rm mess to clean either.16:43
diegoviola joined16:43
yrter_ left16:43
SirFunk left16:43
nnyk left16:43
osse my code isn't tested to begin with either. I wrote it on the spot16:43
PHPanos left16:43
pjh chris2: what is that?16:43
Novitsh left16:44
synthmeat left16:44
spriz left16:44
yrter_ joined16:44
mallocthis left16:44
osse pjh: it's an env var to make git consider a different location as the working directory16:44
leeN left16:45
liamonade joined16:45
brandonw joined16:45
Novitsh joined16:45
cybersphinx joined16:45
pjh ah, so its skips the whole deleting and copying part16:45
karstensrage left16:45
pjh thats pretty cool!16:45
leeN joined16:45
SirFunk joined16:45
diegoviola left16:45
spriz joined16:45
donmichelangelo left16:45
chris2 https://github.com/git/git/blob/master/contrib/fast-import/import-directories.perl looks a bit clumsy, but perhaps nicest idea16:46
endiruna left16:46
sgambino left16:46
the_cybersphinx left16:46
Ranhir left16:46
toogley joined16:47
osse all hail16:47
chll left16:47
chll joined16:47
ahmed_elgabri left16:47
MutantMahesh joined16:48
srcerer left16:48
moriko left16:48
Kobaz left16:49
synthmeat joined16:49
Ranhir joined16:49
ChrisWarrick left16:49
Kobaz joined16:49
ChrisWarrick joined16:50
srcerer joined16:51
osse this is brilliant16:51
ki0 joined16:51
ash_workz joined16:51
baris_ left16:52
infra-re_ joined16:53
osse courrier: !sensitiv16:54
gitinfo courrier: [!filter_sensitive] You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/articles/remove-sensitive-data/16:54
PinkPonyOfDeath left16:55
mkoskar joined16:55
mallocthis joined16:55
infra-red left16:56
joshc_ left16:56
courrier osse: this is exactly what I do, read the question again :)16:56
Gsham left16:57
courrier in their case the sensitive file is stille in the working tree16:57
GaboFDC left16:57
courrier in my case a lot of files have been deleted in old commits16:57
I want to clean all the them16:57
all of them*16:57
madewokherd joined16:58
nilsi left16:58
osse i don't see why it shouldn't work16:58
git rm operates through the index filter. shouldn't matter whether it already exists or not16:58
ehh, whether it still exists I mean16:59
jaafar joined16:59
samw joined17:00
courrier I get a lot of warnings like these /usr/lib/git-core/git-filter-branch: 980: eval: domains/blocks/blocks_reward.s: not found while the file existed in the path and I can actually find a revision where it exists, and then git show still returns the file :/17:01
bollullera left17:01
Tropit joined17:01
s00pcan left17:03
osse hmm17:03
astockton left17:03
osse !repro17:03
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://gist.github.com/2415442 ) of your terminal session.17:03
infra-red joined17:03
tlaxkit left17:04
subhojit777 left17:04
s00pcan joined17:04
Viewtiful left17:05
astockton joined17:05
AtnevRed joined17:06
infra-re_ left17:06
leprechau left17:07
jottr joined17:08
courrier Ok I'm trying to produce a transcript speaking for itself :P17:08
Guest11070 left17:08
User458764 joined17:09
leprechau joined17:09
d4rklit3 joined17:10
mahendra_ left17:11
AtnevRed left17:11
kadoban joined17:12
scorphus left17:12
scorphus joined17:12
alanwill joined17:13
jottr left17:13
PCatinean left17:13
David1977 joined17:15
notebox left17:15
Timvde|Timvde17:15
tomog999_ left17:15
bronson joined17:16
imachuchu joined17:16
imachuchu left17:16
Code_Bleu left17:16
Tropit left17:17
sgambino joined17:18
Code_Bleu joined17:19
imachuchu joined17:19
subhojit777 joined17:20
bronson left17:21
dreiss left17:22
t0by left17:22
t0by joined17:23
liamonade left17:24
ThomasLocke left17:25
diegoviola joined17:25
iLembus joined17:25
dixvagon left17:26
localuser left17:26
n00bdev joined17:26
thiago left17:27
jteneyck joined17:27
The_Phoenix joined17:27
Code_Bleu left17:28
alanwill left17:28
d4rklit3 left17:28
Code_Bleu joined17:29
alanwill joined17:29
alanwill left17:29
User458764 left17:29
Sucks left17:30
Sucks_ joined17:30
mscia joined17:30
synthroid joined17:30
mscia left17:30
notebox joined17:30
n00bdev left17:31
kurkale6ka left17:31
IWishIKnew joined17:32
cagmz left17:33
madebymarkca joined17:34
d4rklit3 joined17:34
localuser- joined17:35
synthroid left17:35
astockton left17:35
ferr joined17:36
Forkk_Forkk17:36
fees left17:37
courrier osse: OK, so by writing the transcript I understood than some \r\n polluted the list of files I was passing to git rm, so this is fixed and filter-branch works17:37
now I have to understand how it is possible that some files are not present on disk (i.e. deleted) without any "delete" entry in the history, cause I'm using this to tell filter-branch what files to forget17:37
encod3 left17:37
courrier DELETED=`git log --find-renames --diff-filter=D --summary | grep delete | cut -d' ' -f 5|sed ':a;N;$!ba;s/\n/ /g'`17:37
colwem joined17:38
courrier This is how I get the list of files to pass to filter-branch17:38
TomyWork left17:38
courrier I ask it to delete the history of all previously deleted files17:38
osse some delete entries might be obscured by the --find-renames17:38
courrier but some deleted files are not returned in this list17:38
osse: but even with git log I have no track from the deletion :/17:39
vkngpmhc joined17:39
courrier Ah, wait17:39
For the specific file I'm watching the last git log entry was a renaming17:39
osse there you go17:40
courrier osse: mmmmh but I've added this cause I'm afraid to delete the entry of a file that has been renamed but still in my working tree :/17:41
osse yes17:42
so don't delete it then17:42
what's the problem?17:42
You have taken care to avoid deleting files that shouldn't be deleted ,but is then surprised when they aren't deleted17:42
tomog999_ joined17:43
ahmed_elgabri joined17:43
fedexo joined17:44
courrier This file has actually been moved, causing git to record a delete, and later on actually deleted, so it must be present in the DELETED var17:44
But other files have also been moved, causing git to record a delete, and are still present in the working tree, so they must not be in the DELETED var17:44
For the second case I've added --find-renmaes, but then I miss some files in the first case :/17:44
Code_Bleu left17:44
Code_Bleu joined17:45
lindenle joined17:45
osse to fix the first you have to run several times...17:46
freimatz left17:48
geoid joined17:48
geoid left17:48
MutantMa_ joined17:49
courrier This distrurbs me: if I delete a file on purpose it should have a "delete" entry as well, right? While in my case the last entry of this deleted file is a renaming, so where is the "delete" entry of the actual deletion, then? This one shoudl have caused filter-branch to forget this file17:49
alanwill joined17:50
osse there is no delete entry17:51
because you asked git to detect renames17:51
samw left17:51
MutantMa_ left17:52
MutantMahesh left17:52
osse courrier: if a file has been renamed *then* deleted, then the new file name will have a "deleted" entry. so that file is gone when you run git filter-branch. After that, the old file name will have a "deleted" entry, because the new one has been removed from the history17:53
your case is weird. either handle special cases by hand, or run filter-branch multiple times17:53
ttbakiatwoam joined17:54
tang^ joined17:54
denis_M joined17:55
ttbakiatwoam left17:55
samw joined17:55
dfrey_ left17:55
fscala left17:56
pikajude left17:57
xnil joined17:57
gfixler left17:57
courrier osse: Ah yeah, I guess I get it, and running multiple times ensures that the second pass won't recognize the old file as a renaming...17:58
So I should run this n times, with n being the maximal number of renamings for a single file =)17:58
denisMone left17:58
fscala joined17:59
karstensrage_ joined17:59
rwb left17:59
samw left18:00
josuebrunel left18:00
phaleth left18:01
mohabaks joined18:01
IWishIKnew left18:01
devhost I have a new hire who made commits before I could see her diff (over the shoulder review); all I want to do is review those commits on my computer before she pushes.18:02
Is it easy to send a patch for review via email?18:02
grawity yeah, git send-email18:02
devhost I'll check it out18:02
_ikke_ yes, but do read the submittingpatches doc first18:02
grawity but you could 'git fetch' the branch as well18:02
freimatz joined18:03
devhost She didn't make a branch.18:03
grawity could make one now18:03
pfloyd Is it possible in pre-commit or another hook to annotate/update a commit message? I want to pre-pend information each time a commit is made automatically and would like to avoid having to call git commit --amend if possible18:03
devhost We can't delete branches we publish to origin.18:03
grawity wut18:03
devhost (yeah)18:03
phaleth joined18:03
kadoban For me doing git via email is kind of a last resort when there's no other workflow that'll work. But it is possible, and it vaguely works okay.18:03
devhost There is a lot wrong with how we use git here.18:03
grawity a bit silly, that18:03
devhost And I don't want to get into the specifics.18:04
kadoban pfloyd: Yeah there's a hook for that, it's not pre-commit, one of the other ones *looks*18:04
devhost It kills me inside anyways.18:04
pfloyd kadoban: thanks!18:04
roelmonnens joined18:04
subhojit777 left18:04
kadoban pfloyd: 'prepare-commit-msg', it's documented in man githooks18:04
gitinfo pfloyd: the githooks manpage is available at http://jk.gs/githooks.html18:04
pfloyd kadoban: thanks, will do some reading18:05
rwb joined18:05
kadoban It looks a tiny bit complicated in terms of the inputs you get, but … not too bad hopefully. Good luck.18:05
sgambino left18:05
mohabaks left18:05
samw joined18:05
mohabaks joined18:06
thiago joined18:06
EvilPenguin joined18:06
karstensrage_ left18:07
pfloyd kadoban: hmm looks like commit-msg might be promising, too18:07
maxxe joined18:08
mariuscc someone in my team commit some changes on master. over those we commit it other changes.what would be the easiest way to remove those changes ?18:09
jam_ joined18:09
astockton joined18:09
_ikke_ rebase18:09
or revert18:09
dfrey_ joined18:10
localuser joined18:10
mariuscc ok but without losing those changes. I mean I want to keep those changes in another branch for fixing bugs and releasing later18:10
mahendra_ joined18:11
maxxe a question on tags: if I tagged something as v1.2 and pushed it to a remote repo. can I re-tag it?, delete the v1.2 tag, and tag a later commit as v1.2, and push it?18:11
daito joined18:12
_ikke_ With difficulty18:12
tags are not supposed to change18:12
postsneakernet joined18:12
maxxe ok. then I know.18:12
elastix joined18:13
squiddle joined18:13
_ikke_ What you describe is just a branch18:13
ferr left18:13
jam_ left18:13
roygbiv joined18:14
kadoban pfloyd: Ah, yes does look like it.18:14
_ikke_ maxxe: I solve this by using rcs18:14
rc18:14
localuser- left18:14
Jellyg00se left18:16
zeroed left18:16
daito left18:16
maxxe _ikke_: ok. I better include the changes in the next release, nothing fatal anyways. just wanted to know if it was possible, but since tags aren't supposed to change, I don't care :)18:16
ahmed_elgabri left18:17
grawity releasing different code under the same version tends to incur the wrath of packagers and users18:17
"is this the old 1.2 or the new 1.2?"18:18
maxxe ye18:18
Guest63991 joined18:18
grawity do a 1.2.1 and be done with jt18:18
_ikke_ Someone speaks out of experience18:18
qyjxmx left18:18
nofacade left18:18
maxxe grawity: yes. that's better18:18
EvilPenguin left18:19
flavius joined18:19
astockton left18:19
Karkus joined18:20
liranp left18:20
salamanderrake joined18:20
chll left18:21
Guest63991 left18:21
pfloyd kadoban: I'm just full of crazy questions today, but what about a way via a hook to merge to master automatically? i.e. if someone is on branch X and makes a commit what would be the easiest way to ensure that commit is merged to master, too withot them having to do it manually?18:21
SimonNa joined18:22
pfloyd client side, not server side18:22
_ikke_ What's the goal of that?18:22
Why have a separate branch then?18:22
mezod left18:22
pfloyd it's a long story18:22
roygbiv left18:23
n00bdev joined18:23
TalkToMe joined18:23
_ikke_ automatic mering only causes pain for the uses18:24
merging*18:24
synthroid joined18:24
xvx joined18:24
hahuang65 joined18:25
sgambino joined18:25
TomyLobo joined18:25
mischat_ joined18:25
nofacade joined18:25
nofacade left18:25
roelmonnens left18:26
astockton joined18:27
diego2 joined18:27
The_Phoenix1 joined18:27
diego2 left18:27
diego2 joined18:27
kadoban pfloyd: That's a pretty bad idea unfortunately. Merging is a manual process and has to be.18:27
EvilPenguin joined18:28
The_Phoenix left18:28
diegoviolaGuest3184818:28
squiddle left18:28
diego2diegoviola18:28
madebymarkca left18:28
mischat left18:28
Guest31848 left18:28
Sasazuka joined18:29
AtnevRed joined18:29
notebox left18:29
mischat_ left18:29
flavi0 left18:29
shekhar_ left18:30
Noldorin left18:32
pfloyd yeah true18:33
freimatz left18:34
vise890 joined18:34
localuser left18:35
localuser- joined18:36
jjensen joined18:36
mezod joined18:37
ianclark left18:38
troulouliou_div2 left18:40
lungaro joined18:40
jjensen left18:40
lungaro I got a weird one here. I'm renaming a repo and its a submodule. I jsut edited .gitmodules in the workspace and renamed the directory and repo. Now when I git status it is trying to chdir to the old name18:41
roygbiv joined18:41
scoobertron joined18:42
fedexo left18:44
Es0teric left18:44
EvilPenguin left18:45
EvilPenguin joined18:45
n00bdev left18:45
baris_ joined18:47
milki you probably missed a step. maybe its easier to remove the submodule completely and then add it18:47
milki shrugs18:47
Andre_work left18:48
howdoi left18:48
imachuchu left18:49
mallocthis left18:49
ojacobson the way submodules are glued together is kind of terrible, milki's suggestion is the best way to do it18:49
AndreSomers joined18:49
durham joined18:49
ojacobson (the work tree for the submodule contains a ref to a repo inside the outer work tree's .git dir, which in turn contains config pointing at the directory of the submodule's work tree)18:50
arooni joined18:50
crose left18:51
vkngpmhc left18:52
vkngpmhc joined18:52
madebymarkca joined18:52
Darcidride joined18:53
HelloAtMega left18:53
HelloAtMega joined18:53
achadwick left18:53
nettoweb joined18:54
irqq I have a big object file in my .git/objects and its contents printed by git cat-file -p shows me that it is an unnecessary stuff, committed just accidentally and no longer existing in my workspace.How can I identify its filename and with which commit it was commited?18:55
Pulp joined18:55
infra-re_ joined18:55
leonarth left18:55
_ikke_ There is no easy way to do that18:55
squiddle joined18:55
irqq ... and how to remove it from .git ?18:56
leonarth joined18:56
irqq does the object represent just one file?18:56
yrter_ left18:56
madewokherd left18:57
Eugene irqq - !filter_sensitive applies to big files as well as Secret ones18:57
gitinfo irqq: You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/articles/remove-sensitive-data/18:57
osse irqq: git rev-list --all | while read -r commit; do if git ls-tree -r $commit | grep $blob; then echo found in commit $commit; break; fi; done18:57
infra-red left18:57
madewokherd joined18:57
AtnevRed left18:58
Gitzilla left18:58
osse irqq: blob=abc123245218:58
where that thing in .git/objects is .git/objects/ab/c123245218:58
iota_pi joined18:59
Treio joined18:59
ki0 left18:59
r00tWearsRedHats left19:00
astockton left19:00
crose joined19:00
leonarth left19:00
gpyh joined19:01
gpyh Hi19:01
gitinfo gpyh: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.19:01
User458764 joined19:02
bollullera joined19:02
govg_ left19:02
gpyh Say I want to squash two commits in a branch "mybranch", but I have already merge mybranch into master, how can I squash those commits in the two branches and make sure they stay the same?19:02
italoacasas left19:02
diegoaguilar_ left19:03
infra-red joined19:04
mohabaks left19:04
EvilPenguin left19:04
bb010g joined19:05
gitinfo set mode: +v19:05
myhau left19:05
myhau joined19:06
infra-re_ left19:06
Code_Bleu left19:06
neanderslob joined19:06
roygbiv left19:06
mahendrak joined19:06
JohnBat26 joined19:07
Code_Bleu joined19:07
mariuscc left19:08
karstensrage_ joined19:08
infra-re_ joined19:08
jottr joined19:10
mahendra_ left19:10
italoacasas joined19:10
colwem_ joined19:11
infra-red left19:12
squiddle left19:12
paddyez joined19:12
arnatal left19:12
faheem joined19:13
EvilPenguin joined19:13
David1977 left19:13
colwem left19:13
elsevero joined19:13
jost joined19:14
raijin left19:14
jottr left19:14
Code_Bleu left19:14
irqq osse: ooops! the object in question does not seem to be referenced by any commit. What then?19:15
osse irqq: try adding --reflog to the rev-list command19:16
diegoaguilar_ joined19:17
Code_Bleu joined19:18
ronny hi19:18
how can i make git use gpg2 ?19:18
milki ronny: man git config gpg.program19:18
gitinfo ronny: the git-config manpage is available at http://jk.gs/git-config.html19:18
irqq osse: still nothing ...19:19
iLembus left19:20
_kfpratt joined19:20
irqq osse: ... but git fsck lists this as a dangling blob19:20
osse ugh19:20
irqq: git gc19:20
gone19:20
irqq: in fact. you can just delete it by hand probably19:21
ronny milki: i did set gpg.program is set to gpg2 - i have a key in gpg2, but git seems to run gpg19:21
mallocthis joined19:21
Talk_To_Me joined19:21
Talk_To_Me left19:22
kfpratt left19:23
milki shrugs19:23
mallocthis left19:23
ronny milki: when i run gpg2 --clearsign it uses my key, if i run git -S i get a gpg error telling me there is no secret key19:23
TalkToMe left19:25
sdothum left19:25
mallocthis joined19:26
irqq osse: done. But my corresponding origin des have the same errors too. How do I deal with that?19:26
localuser joined19:27
cdg left19:27
editshare-ericf left19:27
sdothum joined19:27
Code_Bleu left19:28
ojacobson Unless you have a pressing reason to fiddle with it (low on disk space, eg.) just leave it19:28
Code_Bleu joined19:29
ojacobson as you push to the repo, it'll get periodically repacked and garbage-collected; the offending object will disappear eventually19:29
doener left19:29
editshare-ericf joined19:30
nettoweb left19:30
irqq can I eventually go directly to the origin (bare repo) directory location and do git gc there?19:30
uri_ joined19:30
mallocthis left19:30
localuser- left19:30
diegoaguilar_ left19:30
User458764 left19:32
tyreld left19:32
mwhooker joined19:33
Jackneill joined19:33
User458764 joined19:33
FunkyAss left19:34
yrter joined19:34
nettoweb joined19:34
Code_Bleu left19:34
courrier left19:35
ianclark joined19:35
ojacobson If you have shell access to it, yes, you can manually expire the reflog, repack the repository, and gc any remaining loose objects.19:35
irqq ... the origin seems to be the one which accumulated gatbage whixh then got propagated to clones. Seems I shold have git gc my initial local repo before cloning it as bare master origin.19:35
Code_Bleu joined19:36
ahmed_elgabri joined19:36
irqq Yes, I have shekk access19:36
s/shekk/shell/19:36
ojacobson You generally don't have to, though; the default behaviour repacks the repo whenever there are more than 10 pack files, and discards loose objects that aren't reachable after a while19:36
tyreld joined19:39
ianclark left19:39
jkoudys left19:40
ianclark joined19:41
fahadash left19:41
baris_ left19:42
Jackneill left19:42
MacWinne_ joined19:42
mischat joined19:44
radsy joined19:44
devth left19:46
namikr joined19:46
irqq ojacobson: but should git clone behave in the way that it clones dangling objects too?19:46
ojacobson no19:46
alanwill left19:46
irqq I just checked it does19:47
ojacobson it does that locally (since it uses hard links)19:47
alanwill joined19:47
neanderslob left19:47
leonarth joined19:47
ojacobson when clone has to pass through upload-pack, though, it gets a fresh back containing only the interesting objects19:47
JSharpe joined19:47
mallocthis joined19:47
raijin joined19:48
irqq yes, the origin is in the same filesystem in my case19:48
avaz joined19:48
namikr left19:48
lactose left19:49
avaz left19:49
Pulp left19:49
infra-red joined19:49
squiddle joined19:49
arooni left19:50
sgambino left19:50
mallocthis left19:50
localuser left19:51
cagedwisdom joined19:52
infra-re_ left19:52
simonlinj left19:52
arooni joined19:53
irqq ... but I just tried cloning to another filesystem on the same machine with the same result, and hardlinks do not work across different filesystems19:53
NeverDie left19:53
aranea joined19:53
nilg joined19:54
mizu_no_oto left19:55
algae left19:55
badLuckJoe joined19:55
MattMaker joined19:57
knownasilya joined19:57
simonlinj joined19:58
Sucks_ left19:58
ojacobson It still copies the repo rather than using upload-pack in that case. Try file://localhost/path/to/repo instead of /path/to/repo19:59
neanderslob_ joined19:59
ojacobson (file:// URLs are handled via upload-pack)19:59
neanderslob_ left19:59
neanderslob joined20:00
astockton joined20:01
EvilPenguin left20:01
sgambino joined20:01
gfixler1 joined20:04
Viewtiful joined20:04
Karkus left20:04
diogenese joined20:05
elsevero left20:05
ribasushi left20:05
elsevero_ joined20:05
m0viefreak joined20:05
astockton left20:05
rnsanchez_ joined20:06
aidalgol joined20:06
geekbri joined20:07
jottr joined20:07
devth joined20:08
rnsanchez left20:08
astockton joined20:09
circ-user-15GfU left20:09
ribasushi joined20:09
jam_ joined20:10
ahmedelgabri joined20:10
italoacasas left20:10
italoacasas joined20:11
Viewtiful left20:11
Treio left20:11
synthroid left20:12
daito joined20:12
ahmed_elgabri left20:13
lmatteis left20:13
circ-user-15GfU joined20:13
mizu_no_oto joined20:14
jam_ left20:15
marcogmonteiro left20:15
daito left20:17
Imek joined20:18
badLuckJoe left20:18
gfixler1 left20:21
ki0 joined20:21
mkelly joined20:21
Treio joined20:22
NeverDie joined20:22
arooni left20:23
mkelly left20:27
hyphenated joined20:28
Limes_ joined20:28
mkelly joined20:28
denn1s_ joined20:28
rnsanchez_ left20:29
astockton left20:29
samw left20:33
localuser- joined20:34
Gitzilla joined20:36
devth_ joined20:37
mkelly left20:37
lmek joined20:37
devth__ joined20:38
mkelly joined20:38
baris_ joined20:38
Imek left20:39
devth left20:40
felixn joined20:40
jkoudys joined20:41
devth_ left20:41
zeroed joined20:42
Sod joined20:42
toothe joined20:42
toothe after doing a commit, do I merge it back into head (if its good) ?20:43
astockton joined20:43
madebymarkca left20:43
flavi0 joined20:44
_ikke_ HEAD is the current commit20:44
Es0teric joined20:44
_ikke_ You usually don't merge after every commit20:44
toothe: read a bit about !workflow20:45
gitinfo toothe: Finding the right workflow for you is critical for the success of any SCM project. Git is very flexible with respect to workflow. See http://sethrobertson.github.com/GitBestPractices/#workflow for a list of references about choosing branching and distributed workflows.20:45
Faylite joined20:46
toothe yeah....i totally forgot what my workflow was20:46
blah20:46
MattMaker left20:46
toothe i haven't coded or used git in about 6 months.20:46
arooni_ joined20:47
samw joined20:47
vkngpmhc left20:47
yoh_ joined20:48
arooni_ left20:48
jkoudys left20:48
yoh_ is there a way to force a new merge commit to be generated even if regular merge attempt results in "Already up-to-date"?20:48
cdg joined20:48
_ikke_ no20:48
jkoudys joined20:49
toogley left20:49
yoh_ :-/ pity... there must be some lower level though I bet20:49
_ikke_ yoh_: It usually means you have to verify that there actually is something to merge20:49
yoh_: why do you want to 'force' a merge?20:49
yoh_ ;-) I agree usecase is obscure...20:50
crose left20:50
_ikke_ You can perhaps create a commit yourself having 2 parents20:50
yoh_ it is to complement my other obscure strategy -- "theirs", where I have git merge -s ours --no-commit $1 && git read-tree -m -u $120:50
to initiate a merge from another branch, content of which I filter out, and then commit20:51
simonlinj left20:51
yoh_ then imagine I decided to correct out the cleanup I have done in previous 'merge'20:51
samw left20:51
yoh_ so I need to initiate another merge but it wouldn't work out since according to git "up-to-date"20:52
_ikke_ yeah, git needs diverged history for having something to merge20:52
arooni_ joined20:52
mkelly left20:52
mkelly joined20:53
yoh_ so hence the question -- what low operation actually creates 'merge' commit (pretty much just stating that this commit has those multiple parents)?20:53
arooni_ left20:53
IWishIKnew joined20:53
yoh_ I guess, besides all the merge resolutions etc magic which I don't need in this case, merge is just a call to that low level command20:54
irqq left20:54
jast there's always git commit-tree20:54
pjh left20:54
Darcidride left20:55
synthroid joined20:55
ribasushi yoh_: git branch mynewbranch $( echo "my commit msg" | git commit-tree some_commit_whose_contents_you_want: -p <parent1> -p <parent2> .... )20:55
infra-re_ joined20:55
crose joined20:55
ribasushi yoh_: the ':' at the end of "commit you want" is importnat20:55
yoh_ jast: thanks... I Guess it is the one... thanks ribasushi ! ;)20:55
jast still, if a merge tells you "already up-to-date", the resulting merge won't actually have any effect20:55
mohabaks joined20:55
jast *resulting merge commit20:55
yoh_ I will make it have an effect by having different content ;)20:56
geekbri left20:56
jast oh, you're creating an evil merge20:56
may FSM have mercy on your soul20:56
qsx and eris.20:56
yoh_ amen20:57
jast I'm not entirely certain who all is responsible for souls20:57
arooni_ joined20:58
infra-red left20:58
AtnevRed joined20:58
jteneyck left20:59
kpease left20:59
qsx jast: your mother.21:00
astockto_ joined21:00
jagob joined21:00
jast I... don't think so21:00
jteneyck joined21:00
kpease joined21:01
yoh_ ok -- everyone hide from the next question of a git-insides newbee!21:01
raijin left21:02
elsevero_ left21:02
yoh_ for that commit-tree I need a tree associated with a commit21:02
mostlybadfly joined21:02
mahendrak left21:03
_ikke_ of course21:03
elsevero joined21:03
AtnevRed left21:03
jast given commit abc123: git rev-parse abc123^{tree}21:03
Ademan joined21:03
yoh_ jast: thanks!21:03
jast see man git-rev-parse :)21:04
gitinfo the git-rev-parse manpage is available at http://jk.gs/git-rev-parse.html21:04
astockton left21:04
elsevero left21:05
yoh_ yeay!!! everything worked out21:05
thanks guys! now just need to code it in ;)21:05
jnavila joined21:06
mkelly left21:06
ferr joined21:06
denis_M left21:06
steve left21:06
elsevero joined21:07
ferr My git freezes on git push command, any advices?21:07
_ikke_ check your network21:07
Where are you pushing to? What protocol?21:07
What OS are you on?21:07
ferr I'm pushing to bitbucket, arch linux21:07
strayPuppy joined21:08
t0by left21:08
yoh_ bear with me a bit mroe -- is there a 'tree' for current index (so if I added changes to index and want to commit-tree it)?21:08
ferr Network is fine since it works with heroku but not bitbucket21:08
Ademan I have a file generated by git format-patch which contains the information corresponding to a single commit. I tried to apply it using git am foo.patch but git reports "patch does not apply". What is baffling me is as best I can tell, the parent commit of my patch is identical to the current HEAD where I'm applying the patch, and there are no unstaged or staged changes...21:08
liranp joined21:08
_ikke_ yoh_: There actually, is, although, I cannot remember how to refer to it21:08
ferr: same protocol?21:08
unreal left21:08
jrm left21:09
ferr _ikke_: I believe so21:09
jrm joined21:09
_ikke_ git remote -v show21:09
verify it21:09
t0by joined21:09
ferr Nope, heroku is https and bitbucket ssh21:09
_ikke_ ferr: can you try ssh -T [email@hidden.address] ?21:10
ferr Freezes as well21:10
_ikke_ So it's an ssh issue21:11
Have you checked your firewall?21:11
years joined21:11
_ikke_ freezing usually indicates blocked ports21:11
jnavila left21:12
mkelly joined21:12
phaleth left21:12
arooni_ left21:12
infra-re_ left21:12
arooni_ joined21:13
vkngpmhc joined21:13
localuser- left21:13
monk12 joined21:13
ferr _ikke_: thanks, somehow it worked, it might be the issues with the network21:13
_ikke_ :-)21:14
monk12 hey all, have a git question... I didn't feel comfy messing with our main git bitbucket repo. so i copied a project and worked on it on git hub (i didn't clone it, just checking in the files into github as a new repo, so lost revision history)... I made a 10 commits to that github repo... but I'21:15
but I'd like to merge them into the main rep (and preserve the 10 commit history appended onto the hundreds of commits of the main bitbucket repo)21:15
unreal joined21:15
_ikke_ monk12: !git_graft21:15
!graft21:15
gitinfo [!grafts] Grafts are an obscure feature allowing distinct histories to be joined together; see https://git.wiki.kernel.org/index.php/GraftPoint21:15
JSharpe left21:16
monk12 cool thanks _ikke_. I'll take a look, sounds already promising based on desc21:16
_noblegas left21:16
TomyLobo left21:16
TomyLobo joined21:16
kadoban Wouldn't a rebase be less obscure, and still work?21:16
_ikke_ grafts aren't obscure21:16
squiddle left21:16
_ikke_ Don't know why somebody would describe them as obscure21:17
kadoban: rebase might result in lots of conflicts21:17
a3Dman left21:17
samw joined21:17
kadoban _ikke_: That seems kind of inevitable based on the goal, but maybe I'm missing something.21:18
liranp left21:18
JohnBat26 left21:18
Ademan If anyone's curious, git am --keep-cr foo.patch succeeded21:18
_ikke_ kadoban: not with grafts21:18
a3Dman joined21:18
_ikke_ Ademan: Ah, so a line-ending issue?21:18
astockto_ left21:19
astockton joined21:19
_ikke_ kadoban: With grafts, you just place the commits on top of another commit, without merging anything21:19
Ademan _ikke_: apparently so, I've run into a couple of issues with CRLF in this project already, but I didn't expect it with git-am *shrug*21:19
kadoban Hmm, interesting. I'll have to look at how that works I guess.21:20
infernix left21:20
_ikke_ kadoban: Just a simple text-file saying this commit has that parent or these parents21:20
You have to use filter-branch to make it permanent / sharable though21:20
steve joined21:21
jast grafts are a pretty convenient, if slightly archaic way, to do exactly this kind of thing21:21
mblack left21:21
vise890 left21:21
jast never really got into git-replace (which was meant to replace them)21:21
dsdeiz joined21:21
a3Dman left21:22
samw left21:22
_ikke_ For this case, git grafts is good and simple enough21:22
Mono2000 joined21:22
alanwill left21:22
mkelly left21:23
a3Dman joined21:23
_ikke_ git replace creates a special ref that tells git it should look at object y instead of object x21:24
with the right refspec, these can be shared I guess21:25
samskiter left21:27
ensyde joined21:27
samw joined21:27
denn1s_ left21:27
monk12 yeh i did see a reference to also look at 'git replace' but would you say git grafts are easier to use?21:27
rwb left21:28
bb010g left21:28
EvilPenguin joined21:30
mkelly joined21:30
_ikke_ I think it's comparable21:30
mkelly left21:30
_ikke_ git replace --graft <commit> <parent>21:31
NeverDie left21:31
cyrus_mc_ joined21:31
Nes_To left21:32
nwkj86 joined21:32
ensyde left21:33
Code_Bleu left21:33
Code_Bleu joined21:33
cyrus_mc_ left21:35
baxx joined21:35
squiddle joined21:36
tpollard joined21:36
zumba_addict joined21:36
baxx if i have a repo that I've forked so that i can implement changes what's the best way to ensure that next time I come to make a change I've got the latest code from the main repo (rather than the repo on my github)?21:36
clemf left21:37
clemf joined21:37
astockton left21:38
astockton joined21:38
NeverDie joined21:38
akushner left21:39
akushner_ left21:39
akushner joined21:40
akushner_ joined21:40
BigWillie left21:40
cbonobo left21:40
astockton left21:40
BigWillie joined21:40
astockton joined21:40
squiddle left21:40
Eugene baxx - !upstream_pull21:41
!pull_upstream21:41
gitinfo To pull changes from an "upstream" repository(or any other repo that is not "origin") into your repo, use: git remote add upstream $URL; git fetch upstream; git merge upstream/$BRANCH21:41
zeroed left21:41
Eugene .trigger_edit upstream_pull @!pull_upstream21:41
gitinfo Eugene: Okay.21:41
junw left21:42
s00pcan left21:42
devth__ left21:42
squiddle joined21:43
devth joined21:43
Ademan ergh, I can't seem to get this third patch applied with the same SHA1, I'm providing --keep-cr --committer-date-is-author-date (which has made the first two patches SHA1 match the patch provider's)21:43
nilg left21:43
BigWilli_ joined21:44
jost left21:44
akushner left21:44
akushner_ left21:44
ojacobson (that may be a fluke.)21:44
If the original patch was ever rewritten or had a committer date different from its author date for any other reason (rebase being the most likely), then you'd need to set the committer date to that exact second to get the same SHA121:45
BigWillie left21:45
ojacobson since it's not included in the patch, that's likely impossible21:45
or at least wildly impractical21:45
jeffreylevesque left21:46
RedShift left21:46
bronson joined21:47
d4rklit3 left21:47
Ademan ojacobson: hrm, fair enough, thanks21:47
squiddle left21:47
synthroid left21:50
IrishPrime left21:51
arooni_ left21:52
rossome left21:52
User458764 left21:54
elsevero left21:54
Es0teric left21:54
baris_ left21:54
dfrey_ left21:54
hosttor joined21:55
jteneyck left21:55
ferr left21:55
alanwill joined21:56
lhunath joined21:56
lhunath left21:56
lhunath joined21:56
infernix joined21:56
ahr3n joined21:56
jimi_ left21:57
bollullera left21:57
dsdeiz left21:58
lhunath I have two commits, A and B, I know somewhere in the future, the branches that these commits are on get merged together. How can I find the last commit in a branch B that has both A and B as ancestor?21:58
junw joined21:58
mallocthis joined21:58
lhunath s/branch B/branch/21:59
ojacobson git-am doesn't promise to retain hashes anyways (it's meant for patch-based workflows, where contributors may not have anywhere to publish a git repo containing their changes)21:59
Es0teric joined21:59
BigWilli_ left21:59
crose left21:59
_ikke_ lhunath: git merge-base A B21:59
lhunath _ikke_: that sounds like it'll give me the common ancestor of A and B.22:00
the ancestor of A and B doesn't have A or B as ancestor.22:00
astockton left22:00
mallocthis left22:00
_ikke_ lhunath: Confusing when using the same letter for a commit and branch22:00
ojacobson the last commit in a branch that has both A & B as an ancestor is either the branch itself (if it contains both commits) or nothing (if the branch doesn't contain both)22:01
lhunath Yeah, I shouldn't have named the branch.22:01
ojacobson: last as in, first :-)22:01
AaronMT left22:01
lhunath as in, the farthest back in time. since I can't English well.22:01
astockton joined22:02
lhunath s/time/git commit ordering/22:02
victortyau left22:02
ahr3n left22:03
ojacobson I don't think there's a built-in tool for that class of topology problem22:03
you can script it with rev-list or bisect, though22:04
_ikke_ Doesn't that also have to do that you can only travel to parents, not to children?22:04
lhunath http://ix.io/o7k22:04
I know A, B and E. I want to find C, not D.22:04
lmatteis joined22:04
_ikke_ What direction is history going?22:05
Sod left22:05
lhunath E is the (tip of the) branch.22:05
_ikke_ right22:05
unreal left22:05
_ikke_ There is no easy way to find this out through git22:05
mallocthis joined22:05
PsionTheory joined22:05
BRODUS joined22:05
_ikke_ because from A and Bs point of view, C does not exist22:06
lhunath I guess I could do a git log B..E and A..E and find the first common commit.22:06
kpease left22:06
dfrey_ joined22:06
clemf left22:06
BRODUS i want my blog in a git repo, i want to "ignore" the output directory, but I want the output directory to be its own git repo that I can push to my github pages repo. Are submodules the easiest solution to this?22:07
yoh_ eh -- can't find how to get the tree object for the index. thought to avoid going through some temporary commit for my evil merge via commit-tree22:07
clemf joined22:07
BRODUS I tried symlinking the output folder but git doesn't track changes in that22:07
jast yoh_: git write-tree22:08
unreal joined22:08
yoh_ jast: awesome!22:08
thanks!22:09
rossome joined22:09
leonarth left22:09
strayPuppy left22:10
jam_ joined22:11
ferr joined22:11
astockton left22:11
_ikke_ BRODUS: correct22:11
junw_ joined22:11
_ikke_ BRODUS: is there a connection between the blog and the output dir?22:12
mizu_no_oto left22:12
yoh_ just for the record -- full recipe to "fake" a merge of branch b2 with content of current index is : git reset --hard $(echo "doing merge via write-tree" | git commit-tree `git write-tree` -p HEAD -p b2)22:12
BRODUS the blog compiles templates and dumps it into the output dir22:12
tobias left22:13
akushner_ joined22:13
apotry left22:13
daito joined22:13
_ikke_ Do you want to tie versions of the blog together with the output dir?22:13
Balliad joined22:14
akushner joined22:14
junw left22:14
BRODUS _ikke_: hmm, i dont think so. Why would that be useful ?22:15
jam_ left22:15
_ikke_ BRODUS: That's what submodules do22:15
Cihan left22:15
Es0teric left22:15
italoacasas left22:15
leonarth joined22:16
jkoudys left22:16
BRODUS so if I tag a version to the parents most recent submodule gets tagged at the most commit too?22:16
*most recent commit22:16
Kicer86 left22:16
a3Dman left22:16
elastix left22:17
Cihan joined22:17
_ikke_ Nothing to do with tags22:17
daito left22:18
leonarth left22:19
EvilPenguin left22:20
s00pcan joined22:20
jottr_ joined22:21
vkngpmhc left22:21
madewokherd left22:21
namikr joined22:21
vkngpmhc joined22:22
a3Dman joined22:22
IWishIKnew left22:22
astockton joined22:23
jkoudys joined22:23
glebihan joined22:23
jottr left22:23
phree joined22:24
ash_workz left22:25
TomyLobo left22:25
baris_ joined22:26
t0by left22:28
arooni_ joined22:29
jeffreylevesque joined22:29
s00pcan left22:29
years left22:30
years joined22:30
mizu_no_oto joined22:31
dsdeiz joined22:31
s00pcan joined22:32
zequence_zequence22:33
xnil left22:33
xnil joined22:33
The_Phoenix1 left22:34
ki0 left22:34
namikr left22:34
j416 ooh there's finally recursive theirs!22:35
hm wait.. was that always there22:35
_ikke_ yes22:35
it was the merge strategy theirs that is 'missing'22:35
j416 aaah, right22:35
_ikke_ not the recursive option theirs22:35
j416 _ikke_++22:36
_ikke_ You had surprised for a sec :P22:36
j416 :D yes22:36
revolutionary, I thought22:36
aranea left22:37
jast as it is, poor man's '-s theirs' is still three lines22:38
livingstn left22:38
j416 fortunately there are few use-cases for it22:38
nettoweb left22:39
govg joined22:40
_ikke_ non I would say :P22:41
But who am I22:41
nnyk joined22:43
kazantip joined22:44
samw left22:44
years left22:44
mohabaks left22:44
cbonobo joined22:44
Dougie187 left22:44
jast I've missed it a few times22:44
mkelly joined22:45
sargas joined22:45
nnyk_ joined22:47
thiago wonders how to solve a rename/rename conflict that isn't about renaming22:48
nnyk left22:48
thiago it's a copy/rename conflict that Git is confused about: one file was copied, the other was renamed. It doesn't know how to apply the change.22:48
_ikke_ so one file copied from A to B, and another moved from B to C?22:49
thiago there was a file called A, which I renamed to B22:49
in the meantime, someone copied A to C22:49
when I rebased, Git is complaining about rename/rename conflict22:49
sargas left22:50
t0by joined22:50
thiago no, bad diagnosis. The problem is slightly different.22:51
I'm rebasing some changes on top of the same changes...22:52
akiva joined22:52
tvw left22:52
lenovouser joined22:52
Wetmelon left22:52
uri_ left22:53
hobodave left22:54
_ikke_ hmmm22:54
SimonNa left22:55
thiago the correct fix was git rebase --skip22:55
years joined22:55
mallocthis left22:56
MattMaker joined22:56
aleksandar2810 left22:56
Fijit left22:57
victortyau joined22:57
madewokherd joined22:58
cbonobo left22:58
clemf left22:59
lmek left22:59
_ikke_ let's ignore it22:59
thiago yes22:59
AtnevRed joined22:59
yqt joined23:01
devth left23:02
jstimm joined23:02
devth joined23:03
strayPuppy joined23:03
diegoaguilar joined23:03
samw joined23:04
AtnevRed left23:05
t0by left23:05
Balliad left23:05
bango2 left23:05
cdg left23:07
Es0teric joined23:09
zumba_addict left23:09
mwhooker left23:10
jstimm left23:10
Che-Anarch joined23:10
diegoviola left23:12
cagedwisdom left23:13
s00pcan left23:13
eijk_ joined23:13
s00pcan joined23:14
Treio left23:14
Atm0spher1c joined23:14
jstimm joined23:16
eijk left23:16
astockton left23:16
Faylite left23:17
editshare-ericf left23:17
gpyh left23:17
raijin joined23:17
[Saint_][Saint]23:18
MrWoohoo left23:20
IWishIKnew joined23:20
astockton joined23:20
nnyk_ left23:21
sgambino left23:22
astockton left23:24
astockton joined23:25
Es0teric left23:25
cagedwisdom joined23:25
gfixler1 joined23:26
Treio joined23:27
m1dnight1 joined23:27
m1dnight_ left23:28
EvilPenguin joined23:28
LucaTM left23:28
clemf joined23:28
paddyez left23:29
monk12 another quick question... is there a way for Eclipse to ignore changes in Line Endings/whitespace? I tried Team->General->Compare/Patch->Ignore WS setting, Team->Workspace->New text line delimiter setting to Unix, Team->Git->Config->core.autocrlf=true and false and i still see line ending issues in my Git Staging area23:30
m1dnight1m1dnight_23:30
monk12 I'd like to commit these files without them showing up in Git Staging, was hoping I dont need to individually check and change the line ending (dos or unix) file, and Eclipse/Git can just smartly know and not ask to check it in23:31
jottr_jottr23:31
nwkj86 left23:31
jteneyck joined23:32
thiago monk12: Eclipse questions don't belong in #git23:32
monk12 thiago: gotcha. just thought it was something git people also familiar with and could help out with. Line Endings seems to be a very common issue in git so thought i'd ask based on articles I've googled23:33
thiago yes, line endings are a problem23:33
which is why I don't program on Windows and, whenever I do, I force everything to LF23:34
ianclark left23:34
astockton left23:34
astockton joined23:35
Limes_ left23:36
NeverDie left23:37
monk12 eh, i'll do that now via dos2unix and maybe check those files in as unix line endings.23:37
sitaram_sitaram23:37
modocache left23:38
astockton left23:38
modocache joined23:38
samw left23:40
KaibaCorp left23:41
dsdeiz_ joined23:42
samw joined23:42
baris_ left23:42
dsdeiz left23:44
squiddle joined23:44
MattMaker left23:44
ICantCook joined23:45
pwnz0r joined23:45
years_ joined23:45
pwnz0r anyone here good at manipulating history? i have a pull request merge commit in history, that was later reverted by using the pull request revert feature. now I need to merge that code back again, but since it is already in history, i cannot merge. I am not sure how to fix this, and the branch is public23:45
diogenese left23:45
years left23:45
preaction pwnz0r: revert the revert23:46
pwnz0r it won't revert automatically23:46
due to another much larger merge commit taking place23:46
i want to revert the revert now and fix conflicts but I'm not sure how23:47
samw left23:47
preaction git revert <revert commit id>; then !eekaconflict23:47
gitinfo Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II23:47
squiddle left23:49
ICantCook I need some help with reverting a merge. Someone merged a different repository into master and pushed, and I am trying to undo this.23:50
mizu_no_oto left23:50
ICantCook I understand the merge has 2 parents23:50
Eugene ICantCook - !fixup23:50
gitinfo ICantCook: 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!23:50
devth left23:50
Treio left23:50
pwnz0r preaction: ill read the man page on revert23:51
NeverTired joined23:51
preaction pwnz0r: it's literally that command, that's it. if it fails, it's like any other merge fail, and it dumps you out into the working tree with an admonishment to resolve the conflicts23:51
pwnz0r ok cool23:52
astockton joined23:53
astockton left23:53
ghoti I've got a working gitolite environment where I'd like devs to be able to create and delete branches, but I don't want to grant RW+ to everyone. Is there a way to permit branch deletion only, or perhaps to permit RW+ to branches that are *not* master?23:53
diegoviola joined23:53
ICantCook Eugene: What I'm trying to do isn't on that page23:53
I'm trying to revert to a specific parent (I think)23:54
but I've tried both parents, and neither looks right23:54
(as per http://stackoverflow.com/questions/3240230/git-revert-merge-to-specific-parent)23:54
Eugene You've got something merged+pushed that shouldn't have?23:54
mkelly left23:54
ICantCook Eugene: yeah23:54
pwnz0r preaction: since it was a merge commit i need the -m option23:54
Eugene You're trying to "go back to" the parent then, not revert it23:54
ICantCook and when I revert or reset to just before that merge, I lose ~1 year worth of commits23:54
Eugene !revert23:54
gitinfo That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?23:54
pwnz0r do i give a branch name or a hash?23:54
Eugene You want e)23:55
preaction pwnz0r: you're reverting a revert. that revert wasn't a merge commit23:55
pwnz0r well there are two commits23:55
there is the revert23:55
and the merge commit for the revert23:55
el_seano left23:55
IWishIKnew left23:55
Eugene You don't want a new, "undo" commit(which is what revert does), you want to rewind to a point where the merge didn't ever exist23:55
pwnz0r should i just revert the commit and leave the merge commit as is?23:56
preaction pwnz0r: the revert reverted the merge commit. so the merge commit is A, the revert is the opposite of A, which means reverting the opposite of A is A again23:56
Eugene Because this is going-back-in-time you will need to `git push -f` the new point23:56
pwnz0r awesome haha thnaks so much23:56
el_seano joined23:57
samw joined23:57
ghoti Can I configure gitolite with only RW permissions on "master", but still permit devs full access to their branches (to rebase or delete them) with this?23:57
repo @repolist23:57
RW master = @devs23:57
RW+ . = @devs23:57
astockton joined23:57
dmto left23:57
Eugene You should put it under a namespace/, rather than a regex at the top-level like that(which won't work, incidentally. That will grant + ro master, I believe)23:58
NeverDie joined23:58
leonarth joined23:58
Eugene The special USER keyword bay be of interest23:58
ghoti Eugene, doesn't the word between permissions and '=' get matched to the branch?23:59
Eugene master would match .23:59

Logs Search ←Prev date Next date→ Channels Documentation