IRCloggy #git 2016-07-15

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-07-15

nettoweb joined00:00
Darren_ left00:01
nwkj86 left00:01
cdg left00:01
m0viefreak left00:01
mingle__ left00:02
jwarren_ left00:03
f3r70rr35f joined00:03
devbug joined00:03
Peuc joined00:03
Darren_ joined00:04
xall_ joined00:04
f3r70rr35f left00:08
devbug left00:08
yqt left00:08
nnyk_ left00:09
inflames joined00:09
piling_ joined00:10
dilijev joined00:10
knittl joined00:10
knittl left00:10
knittl joined00:10
mika joined00:10
fstd_ joined00:10
dilijev left00:11
Darren_ left00:11
piling left00:11
zacts joined00:12
dilijev_ joined00:13
fstd left00:14
fstd_fstd00:14
ag4ve_ left00:14
kbs left00:16
tristanp left00:19
Orion3k Hi, anyone know how to get a post-receive hook to work in a bare directory when pushing to a remote with a branch and not master? I am getting this error - remote: fatal: You are on a branch yet to be born00:20
romerocesar joined00:20
mischat left00:21
mikecmpbll left00:21
tristanp joined00:22
Masterphi left00:23
mwhooker joined00:23
romerocesar left00:25
LeBlaaanc left00:28
Literphor left00:31
Literphor joined00:32
benwbooth left00:32
foist left00:34
Guest7243murph00:35
Orion3k nevermind, i forgot the branch name on the checkout command in the post-receive hook00:40
harish_ left00:40
romerocesar joined00:40
codebam so I have a 3.4.10 kernel, how can I merge 3.4.12?00:42
Chiko joined00:42
codebam they are tags00:42
dx left00:42
osse codebam: git merge <thing>00:43
codebam but its a tag, how do I merge tags?00:44
osse codebam: git merge <tag>00:44
f3r70rr35f joined00:44
codebam ohh okay00:45
thanks lol00:45
so I would add it as a remote right, like git remote add upstream <url>00:45
romerocesar left00:45
codebam and then git merge upstream/tag?00:45
rominronin joined00:46
osse fetch first00:46
stoopkid left00:46
osse and just git merge tag00:46
because tags are global.00:46
there is no tag versus upstream/tag like with branches00:46
cqi joined00:47
SimonNa left00:47
Vgr_Vgr00:47
rahtgaz left00:48
mrkat left00:49
thiago left00:50
rominronin left00:51
dx joined00:52
xlegoman joined00:52
codebam oh okay00:55
nettoweb left00:56
Duikb00t left00:56
tristanp left00:56
demimeta joined00:57
tristanp joined00:59
romerocesar joined01:01
dsantiago left01:01
demimeta left01:02
xall_ left01:02
dilijev_ hello!01:03
gitinfo dilijev_: 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.01:03
dilijev_ !backup01:04
gitinfo Worried about your data while trying stuff out in your repo? The repository in its entirety lives inside the .git directory in the root of your work tree so to backup everything `cp -a path/to/workdir path/to/backup` or equivalent will suffice as long as the repo is not modified during backup. See also http://sethrobertson.github.com/GitBestPractices/#backups01:04
dilijev_ Ok looks like I can send messages to this channel now thanks to nickserv01:04
I have a question. Do git --pretty="" format strings support date formatting? AFAICT they do not, and I've resorted to using backspace characters to chop off the parts I don't care about01:05
romerocesar left01:05
osse dilijev_: there are a couple of different formats you can pick from, but nothing akin to strftime()01:06
dilijev_: never mind, you can do exactly that :P01:07
xall_ joined01:07
osse dilijev_: --date=format:%c01:07
dilijev_ oh01:07
osse dilijev_: then use the --pretty thingies that says "respects --date option"01:07
dilijev_ ok how can i combine that with [pretty] format in the .gitcongfig?01:08
so i guess I'll need to update my aliases to take the --date option as well as the date pretty format string?01:08
osse i suppose so01:08
dilijev_ is there an eruivalent [date] .gitconfig option so I can refer to those formats by name?01:08
diprotic joined01:09
osse dilijev_: ehh, nope: git config log.date '%c blabla'01:09
dilijev_ equivalent*01:09
netj left01:09
dilijev_ oh that's even better01:09
i think01:09
netj joined01:09
dilijev_ i don't usually care about more than one date format01:09
ome joined01:09
pks left01:10
Sasazuka left01:11
monoprotic left01:12
dilijev_ Using git version 2.8.2.windows.101:13
git log --date=<anything>01:13
fatal: unknown date format01:13
any ideas?01:13
osse: (tagging you)01:13
Sorry; I'm new to IRC01:13
diproticmonoprotic01:13
osse what did you try01:13
dilijev_ git log --date=short01:14
fatal: unknown date format01:14
http://linux.die.net/man/1/git-log01:14
liquidjamm left01:14
osse try rfc01:15
pks joined01:15
dilijev_ git log --date=rfc01:15
fatal: unknown date format01:15
osse well then01:15
i have no clue01:15
dilijev_ osse: user error01:15
osse: I had log.date set incorrectly in .gitconfig01:16
osse heh01:16
dilijev_ it was using that first and failing01:16
osse i would think --date given on the CLI would override that, but...01:16
dilijev_ osse: apparently no?01:17
osse apparently01:17
dilijev_ maybe if the value in log.date was correct in the first place?01:17
I set log.date=rfc and then did git log --date=short and it worked01:17
i guess it validates the .gitconfig and then defers to command line arg first. that seems half broken01:18
osse usually CLI overrides the config files01:18
so this is unexpected to me01:18
dilijev_ right. it did so. but only when the config file was valid01:18
from log given the above: [ a956dde ] 2016-07-1101:19
MattMaker left01:19
dilijev_ it used short from the CLI and not the rfc from the gitconfig01:19
short is generally the format I prefer01:19
but even so01:19
MattMaker joined01:20
dilijev_ how do I use strftime()-like formats?01:20
osse like i said01:20
--date=format:...01:20
dilijev_ looks like it only takes these:{relative,local,default,iso,rfc,short,raw}01:20
happy-dude left01:21
PaulCapestany left01:21
osse maybe it's a new feature01:22
dilijev_ osse: thanks, it works when I use the right flags01:22
git log --date=format:"%Y-%m-%d"01:22
I was expecting to write something like yyyy-MM-dd but this works, too01:22
osse that doesn't work with strftime either01:22
PaulCapestany joined01:23
dilijev_ right -- in truth I've never actually used that API and I assumed incorrectly about it's format. But this style of formatting makes more sense from a c API perspective01:23
osse: Thanks for your help in showing me how to do this; it had been bothering me for months :P01:23
eizua joined01:24
fahadash joined01:24
Guest39441 joined01:25
Noldorin left01:25
mwhooker left01:26
dsantiago joined01:27
relgar joined01:27
nettoweb joined01:29
Ph_ left01:29
dreiss joined01:31
romerocesar joined01:31
xall_ left01:32
Ph_ joined01:32
shaggycat left01:32
cyan__ joined01:33
nettoweb left01:34
LaptopBrain left01:34
reim left01:35
romerocesar left01:36
david007 joined01:38
dreiss left01:39
armenzg left01:41
tcsc left01:41
romerocesar joined01:41
tristanp left01:41
meloc joined01:43
cyan__ left01:43
tristanp joined01:43
meloc left01:44
meloc joined01:44
ilbot3 left01:46
romerocesar left01:46
jamesd left01:46
mehola joined01:47
rominronin joined01:47
cqi left01:47
aspiers joined01:48
jamesd joined01:48
ilbot3 joined01:48
f3r70rr35f left01:49
stantonk joined01:49
unreal joined01:50
NimeshNeema joined01:50
mehola left01:51
shaggycat joined01:52
rominronin left01:52
unreal_ left01:52
BombStrike left01:53
thiago joined01:53
sangy joined01:53
xall_ joined01:54
armenzg joined01:55
ryez left01:55
justanotheruser left01:55
justanotheruser joined01:57
dmj` left01:57
BombStrike joined01:57
martinium joined01:58
l4v2 joined01:58
tcsc joined01:59
Dougie187 joined01:59
f3r70rr35f joined01:59
drbean_ left02:04
drbean joined02:05
p4trix joined02:07
p4trix Is there a channel to talk about bitbucket pipeline?02:07
harish_ joined02:08
jstimm_ left02:09
Goplat joined02:10
TSS_ left02:11
romerocesar joined02:12
Guest39441 left02:12
DeaTheAngel left02:13
hexagoxel left02:13
MattMaker left02:13
Literphor left02:14
tristanp left02:14
Meow-J joined02:14
MattMaker joined02:16
romerocesar left02:16
Guest39441 joined02:16
tristanp joined02:17
danimal2 joined02:18
Noldorin joined02:19
hexagoxel joined02:19
netj left02:19
netj joined02:19
Ankhers joined02:22
inflames left02:22
Ankhers left02:23
Masterphi joined02:24
ShapeShifter499 left02:24
Sadeukko left02:26
Guest39441 left02:27
durham_ joined02:27
Masterphi left02:28
Guest39441 joined02:28
danimal2 left02:29
f3r70rr35f left02:30
durham left02:31
romerocesar joined02:31
durham_ left02:32
Literphor joined02:32
p4trix left02:33
romerocesar left02:36
f3r70rr35f joined02:37
Limes_ joined02:38
stantonk left02:39
zacts left02:41
Lyqyd joined02:42
lotus joined02:42
lotus Hey, how can I leave a single file unmerged?02:42
Guest39441 left02:43
lotus I want to pull in all of the changes on a branch, but one of the plugins is conflicting with my current development. I'd like to keep my plugin file in-tact but leave the option to resolve the conflicts for another time.02:43
Limes_ left02:44
harish_ left02:45
Guest39441 joined02:45
leeN left02:46
MattMaker left02:47
shum left02:48
rominronin joined02:48
thiago lotus: ok, so don't fix the merge02:48
you won't be able to commit the merge until you have, though02:48
just disable the plugin in your tree02:49
and don't make any further changes, because you can't commit anything02:49
lotus I want 99% of the changes in the merge though02:49
MattMaker joined02:49
thiago lotus: ok02:50
lotus I guess I need to resolve the conflict is what you're saying.02:50
thiago anything below 100% resolved can't be committed02:50
lotus makes sense. And leaving a file out doesn't really work because it's part of the HEAD of that branch and if the HEAD was merged that file would be assumed merged also02:51
thiago correct02:51
xlegoman left02:52
lotus gets to resolving the merge conflict...02:52
danimal2 joined02:53
rominronin left02:53
f3r70rr35f left02:55
f3r70rr35f joined02:56
arescorpio joined02:57
azbarcea left02:57
cqi joined02:57
dmj` joined02:57
Dougie187 left02:58
boombatower joined02:58
chachasmooth left03:01
sanketdg joined03:01
chachasmooth joined03:01
stantonk joined03:02
romerocesar joined03:02
MattMaker left03:03
ArchNoob left03:04
theskillwithin left03:04
Literphor left03:05
MattMaker joined03:05
Sasazuka joined03:05
hahuang61 left03:05
Literphor joined03:06
stantonk left03:06
auzty joined03:06
xall_ left03:07
romerocesar left03:07
chrisshattuck joined03:07
xall joined03:07
Noldorin left03:08
Lyqyd left03:09
MattMaker left03:10
shgysk8zer0_ joined03:11
MattMaker joined03:11
danimal2 left03:12
MattMaker left03:13
stantonk joined03:14
Literphor left03:16
MattMaker joined03:16
l4v2 left03:16
kbs joined03:16
hahuang61 joined03:17
d4rklit3 joined03:17
stantonk left03:18
danimal2 joined03:19
theskillwithin joined03:20
romerocesar joined03:22
xelxebar left03:24
pioiytr__ joined03:25
diegoviola left03:26
romerocesar left03:27
treaki__ joined03:27
pioiytr_ left03:28
Guest39441 left03:28
Guest39441 joined03:29
MattMaker left03:31
treaki_ left03:31
stantonk joined03:32
romerocesar joined03:32
MattMaker joined03:33
Garen left03:35
romerocesar left03:37
stoopkid joined03:40
Garen joined03:42
danimal2 left03:46
mehola joined03:48
zacts joined03:48
danimal2 joined03:48
shgysk8zer0_ left03:48
tristanp left03:49
rominronin joined03:49
howdoi joined03:50
Masterphi joined03:52
tristanp joined03:52
mehola left03:52
hk238 joined03:52
Literphor joined03:52
kbs left03:53
rominronin left03:54
MattMaker left03:55
MattMaker joined03:55
Masterphi left03:56
danimal2 left03:57
NimeshNeema left04:01
romerocesar joined04:03
armyriad joined04:03
d4rklit3 left04:03
d4rklit3 joined04:06
FuzzySockets left04:06
zacts left04:06
romerocesar left04:07
Literphor left04:08
Gamecubic left04:08
rscata joined04:10
stantonk left04:11
stantonk joined04:12
drewo joined04:14
Guest39441 left04:15
stantonk left04:16
rchavik joined04:18
sctskw joined04:19
govg joined04:19
nilg joined04:21
xall left04:21
Garen left04:21
theskillwithin left04:22
cd-rum_ left04:22
stonerfish left04:22
fahadash left04:22
romerocesar joined04:22
Rodya_ joined04:24
stonerfish joined04:24
hk238 left04:25
aidalgol In gitk, what is the difference between "Reload" and "Update"?04:25
stantonk joined04:25
sylario left04:26
JanC_ joined04:26
mehola joined04:27
JanCGuest8962904:27
JanC_JanC04:27
romerocesar left04:27
Guest89629 left04:28
drewo left04:29
Literphor joined04:29
rchavik_ joined04:30
rgrinberg left04:30
rchavik_ left04:31
MattMaker left04:33
drewo joined04:34
theskillwithin joined04:34
lordjancso joined04:34
chrisshattuck left04:35
chrisshattuck joined04:36
chrisshattuck left04:37
MattMaker joined04:37
Cabanossi left04:37
chrisshattuck joined04:38
sctskw left04:39
rgrinberg joined04:39
chrisshattuck left04:40
Cabanossi joined04:40
chrisshattuck joined04:42
chrisshattuck left04:43
chrisshattuck joined04:44
FuzzySockets joined04:47
MattMaker left04:47
stantonk left04:48
rominronin joined04:50
xall joined04:50
danimal2 joined04:52
romerocesar joined04:53
xall left04:55
rominronin left04:55
unbalancedparen left04:57
cuebix-wk left04:57
freimatz joined04:57
romerocesar left04:58
Rodya_ left04:58
aidalgol left04:58
mariuscc joined05:01
tristanp left05:02
danimal2 left05:02
chrisshattuck left05:02
chrisshattuck joined05:03
romerocesar joined05:03
Duder9999 joined05:04
arooniarooni__05:05
shgysk8zer0 left05:05
phanimahesh joined05:06
romerocesar left05:08
dmj` left05:11
tristanp joined05:11
Sasazuka left05:12
MZAWeb left05:14
rgrinberg left05:14
phanimahesh left05:15
cd-rum joined05:16
phanimahesh joined05:16
chrisshattuck left05:19
cdown joined05:19
chrisshattuck joined05:21
romerocesar joined05:23
BrianBlaze420 left05:24
arescorpio left05:27
ThomasLocke joined05:27
f3r70rr36f joined05:28
BrianBlaze420 joined05:29
xall joined05:29
chrisshattuck left05:30
ThomasLocke left05:31
f3r70rr35f left05:31
drewo left05:33
Dragon535 joined05:34
milki no clue!05:34
what does it look like?05:34
danimal2 joined05:35
drewo joined05:35
NeverDie left05:36
sangy left05:37
OnBrokenWings joined05:40
jungsubk joined05:41
emPi joined05:42
danimal2 left05:43
danimal2 joined05:43
drewo left05:44
jstimm_ joined05:46
drewo joined05:46
freimatz left05:46
qt-x joined05:46
zeroed joined05:46
jceb joined05:47
OnBrokenWings left05:48
stantonk joined05:49
nilg left05:49
Alienpruts joined05:51
jceb left05:51
rominronin joined05:51
stantonk left05:53
tobiasBora joined05:55
danimal2 left05:55
rominronin left05:56
drewo left05:59
drewo joined05:59
xlegoman joined06:00
mehola left06:01
leeN joined06:01
pioiytr__ left06:02
CheckDavid left06:02
LeBlaaanc joined06:03
pioiytr joined06:04
jceb joined06:05
Darren_ joined06:06
romerocesar_ joined06:06
romerocesar left06:08
zeroed left06:08
DieguezZ joined06:09
ahr3n left06:09
romerocesar joined06:09
ome left06:09
b_rare left06:10
romerocesar_ left06:11
circ-user-foXmx joined06:11
b_rare joined06:12
phanimahesh left06:12
mehola joined06:14
romerocesar left06:14
DieguezZ left06:15
emPi left06:16
zeroed joined06:17
zeroed left06:17
zeroed joined06:17
romerocesar joined06:17
mkoskar_ joined06:21
mkoskar left06:21
mwhooker joined06:21
hendry joined06:23
mwhooker left06:23
Alienpruts left06:23
Khisanth left06:23
zlg joined06:23
hendry hi i am on a branch "foobar" and I want to push that to "aremote" to master. What's the syntax for that?06:24
kimon joined06:24
mwhooker joined06:24
grawity git push aremote foobar:master06:24
pioiytr_ joined06:24
hahuang61 left06:24
hendry grawity: thank you06:25
zlg I have two files with changes that I want to commit, but only after a rebase. I need to commit them one at a time. git-stash seems like the right solution, but don't I need to put both into the index first? If I do that, then 'git stash pop' after my pull, can I remove the second file from the index and commit (with un-added changes) like expected?06:25
phanimahesh joined06:25
grawity stash, rebase, reset, re-add06:26
both `git add` and `git reset` take filenames, and even have -p06:26
alternatively, stash --include-untracked06:26
freimatz joined06:26
zlg grawity: perfect, thanks for the reassurance.06:26
pioiytr left06:26
mkoskar_ left06:27
mkoskar_ joined06:29
hendry grawity: how do i specify the local branch to push in .git/config06:29
tristanp left06:30
ynanm joined06:35
muelli joined06:36
madewokherd left06:36
Khisanth joined06:37
Alienpruts joined06:37
grawity hendry: I think `git branch -u aremote/master` also applies to pushing06:38
hendry: as long as push.default is 'upstream'06:38
see also `man git-config` for branch.*.{remote,pushRemote,merge}06:39
gitinfo the git-config manpage is available at http://jk.gs/git-config.html06:39
grawity also remote.pushDefault06:39
tristanp joined06:41
Literphor left06:42
TomyLobo left06:42
JeroenT joined06:43
usm4n joined06:43
tobiasBora left06:44
drewo left06:44
drewo joined06:45
kimon left06:48
infinite_ joined06:49
romerocesar_ joined06:50
rominronin joined06:52
CausaMortis joined06:53
romerocesar left06:53
usm4n left06:53
Duder9999 left06:53
romerocesar joined06:54
ynanm left06:55
infinite_ left06:55
romerocesar_ left06:55
thiago left06:55
muelli left06:56
d4rklit3 left06:57
tobiasBora joined06:57
rominronin left06:57
qt-x left06:59
qt-x1 joined06:59
JeroenT left06:59
Repox joined07:00
xlegoman left07:00
drewo left07:00
romerocesar_ joined07:01
qt-x1qt-x07:01
romerocesar left07:03
infinite_ joined07:04
ahmed_elgabri joined07:04
djb-irc joined07:04
infinite_ left07:04
_Patrick_ joined07:04
MrWoohoo left07:05
deBase joined07:06
usm4n joined07:06
magicbit left07:07
shaggycat left07:08
gfixler joined07:08
JeroenT joined07:09
jungsubk left07:09
ahmed_elgabri left07:09
rchavik left07:09
lindenle left07:10
lindenle joined07:12
k3rn31 joined07:13
TomyWork joined07:13
stoopkid left07:13
usm4n_ joined07:14
_Patrick_ left07:14
Hounddog joined07:15
_Patrick_ joined07:16
dsrtrck joined07:17
Juri_Agarin joined07:17
Fijit joined07:17
usm4n left07:17
encod3 joined07:17
hahuang61 joined07:21
encod3 left07:21
mwhooker left07:22
JeroenT left07:23
JeroenT joined07:24
hahuang61 left07:25
theskillwithin left07:26
zeroed left07:26
antranigv how can I set the `project name` of a git repo? :) right now it's showing `.git` :)07:27
thekingofbandit joined07:27
Balliad joined07:28
jceb left07:29
OnBrokenWings joined07:30
OnBrokenWings left07:30
usm4n_ left07:31
aswen joined07:34
lindenle left07:34
mkoskar_mkoskar07:34
tobiasBora left07:36
Goplat left07:36
lindenle joined07:38
deBase left07:38
grawity you can try writing it into .git/description07:39
tobiasBora joined07:40
djb-irc left07:40
codebam my last commit was a merge, I messed it up (missed some stuff), fixed that, how do I rewrite the commit with the things I fixed inside?07:40
or well I don't want to change the commit message, just want to add the changes07:41
rominronin joined07:41
grawity git commit --amend07:42
you can add -C/--reuse-message HEAD07:42
lindenle left07:43
codebam oh cool. thank you07:43
romerocesar_ left07:43
jceb joined07:43
djb-irc joined07:44
aswen left07:44
Macaveli joined07:46
devbug joined07:46
mikecmpbll joined07:47
Dragon535 left07:47
zlg left07:48
cyan__ joined07:48
multi_io left07:48
romerocesar joined07:49
kupad joined07:49
drewo joined07:49
codebam if I have a file like a png file, that isn't code. how can I merge those conflicts?07:49
multi_io joined07:50
grawity you can choose one version with `git checkout --ours/--theirs <file>`07:50
theskillwithin joined07:51
codebam oh okay thats cool, thanks07:52
lugzer joined07:53
Darren_ left07:54
romerocesar left07:54
drewo left07:55
kupad left07:55
grawity ah I suppose if you want to keep both there's `git show :2:data/foo.png > data/foo-ours.png; git show :3:data/foo.png > data/foo-theirs.png`07:55
Silenced joined07:57
FuzzySockets left07:57
Silenced left07:58
Silenced joined07:58
mikecmpbll left07:58
ajf- left07:58
mischat joined08:01
Repox_ joined08:02
Repox left08:03
geoff-codes joined08:04
lindenle joined08:04
Repox_ left08:05
mikecmpbll joined08:05
Repox joined08:06
Macaveli left08:06
bongjovi joined08:06
pioiytr_ left08:06
shirty joined08:07
pioiytr joined08:07
Meow-J left08:09
romerocesar joined08:10
kurkale6ka joined08:11
lindenle left08:12
muelli joined08:12
theskillwithin left08:13
stoopkid joined08:14
stoopkid left08:14
stoopkid joined08:14
King_DuckZ joined08:14
LeBlaaanc left08:14
romerocesar left08:15
jceb left08:15
aswen joined08:17
King_DuckZ hi, is there a way to list the remote url of each submodule without initializing them first?08:17
theskillwithin joined08:18
Beams joined08:20
Andrew_K joined08:20
Duikb00t joined08:21
Duikb00t o/08:21
CausaMortis-Work joined08:21
hahuang61 joined08:21
apotry joined08:22
CausaMortis left08:24
theskillwithin left08:24
hahuang61 left08:27
theskillwithin joined08:27
tristanp left08:27
jceb joined08:28
theskillwithin left08:29
f3r70rr36f left08:29
romerocesar joined08:30
f3r70rr35f joined08:30
Jellyg00se joined08:32
t0by joined08:32
tristanp joined08:34
clmsy joined08:34
romerocesar left08:35
kab joined08:35
mikecmpb_ joined08:36
kedare joined08:37
DieguezZ joined08:38
mikecmpbll left08:39
codebam how do I pull in one file from a remote tracking branch?08:39
OnkelTem joined08:40
gitinfo set mode: +v08:40
theskillwithin joined08:41
OnkelTem Hi all. Need urgent help. I wanted to join two last commits and for this I launched: git rebase -i HEAD~208:41
codebam never mind, got it08:41
OnkelTem but for some strange reason it opened editor with a bunch of commits to squash08:42
Now I don't konw what to do! If I exit the editor it would probably fuck up my repository08:42
how to cancel the action? kill the process?08:43
drewo joined08:43
gitinfo set mode: +v08:46
PCatinean joined08:46
kab Just comment lines08:47
it'll do nothing08:47
alcohol OnkelTem: which editor?08:48
drewo left08:48
OnkelTem alcohol: I have mcedit here08:48
alcohol world editor for minecraft? o_O08:49
OnkelTem kab: oh, thanks, I'll try08:49
alcohol: lol08:49
alcohol well thats the first google result.. http://www.mcedit.net/08:49
dreiss joined08:49
OnkelTem alcohol: Midnight Commander08:50
mischat left08:50
alcohol ah08:50
cd-rum left08:51
OnkelTem kab: many thanks it worked!08:51
GenZai joined08:51
kab <OnkelTem> now analyse why it has happened and tell us )08:52
FunkyAss joined08:55
kab left08:56
jceb left08:56
Limes_ joined08:56
Masterphi joined08:58
kab joined08:58
gitinfo set mode: +v08:59
alcohol kab: it happened cause he did an interactive rebase09:01
kab: i think he just didnt read up on how it works09:01
kab his command should show onle two commits for rebase, not a bunch as he has09:01
i use that command every day though09:02
Masterphi left09:02
kab maybe his head was not he expected09:02
tvw joined09:03
alcohol OnkelTem: what did you see exactly?09:03
achadwick joined09:03
alcohol OnkelTem: if you saw 2 commits prefixed with "pick", then that was exactly what you should have expected09:03
kab yep it should be like that in normal state )09:04
alcohol OnkelTem: and you probably would have wanted to change one of those to fixup or squash09:04
pioiytr_ joined09:06
theskillwithin left09:06
ikmaak joined09:06
pioiytr left09:09
JeroenT left09:09
devbug left09:10
kab left09:10
theskillwithin joined09:10
kab joined09:10
chll_ joined09:11
armyriad left09:11
kab left09:13
kab joined09:13
sdothum joined09:13
ikmaak left09:13
dreiss left09:13
jceb joined09:14
ikmaak joined09:14
nnyk_ joined09:15
ncd|leeN joined09:17
troulouliou_div2 joined09:18
gitinfo set mode: +v09:18
JeroenT joined09:19
Beams left09:20
leeN left09:21
pcre_ joined09:22
notebox joined09:22
notebox left09:22
lindenle joined09:22
King_DuckZ I need to get the default remote exactly as asked in this question http://stackoverflow.com/questions/34099451/get-default-remote-push-and-default-remote-branch is there anybody with an answer for it?09:23
Beams joined09:23
King_DuckZ I would also like to avoid any manual splitting, as the guy in that thread asked09:23
hahuang61 joined09:24
notebox joined09:24
durham joined09:26
lindenle left09:27
armyriad joined09:27
johnny56 left09:28
johnny56_ joined09:28
hahuang61 left09:28
solf1re joined09:29
solf1re left09:29
solf1re joined09:30
solf1re left09:30
theskillwithin left09:30
akiva left09:30
solf1re joined09:30
solf1re left09:30
solf1re joined09:31
solf1re left09:31
armyriad left09:31
solf1re joined09:32
solf1re left09:32
liamonade joined09:32
liamonade left09:32
theskillwithin joined09:32
solf1re joined09:33
solf1re left09:33
solf1re joined09:33
solf1re left09:33
mehola left09:35
theskillwithin left09:37
drewo joined09:38
white_gecko joined09:41
drewo left09:42
Silenced left09:43
des_consolado Hey if I use a hard link from a directory within my repo to another directory within my repo, will git be okay with that or no?09:43
white_gecko Hello, I have two questions:09:43
Is there any scientific literature about git, especially something like a formal mathematical model about commits, merges, diffs, rebase, … ?09:43
In which cases is it not enought for a three way merge to take the latest common acestor of two commits? When do you actually need recursive three way merge?09:43
j416 des_consolado: git will treat them as any other file09:44
des_consolado Basically I'm building a repo for a docker build of one of our projects, and there are many dependencies, for this particular dependency there is another repo of ours, so I include the repo as a submodule and it's part of this repo, but for the docker container itself when it is ran, it mounts a dir in the repo called lib/, so I'd like to use a hardlink to have a file in a dir in lib be linked to a09:44
file in the submodule09:45
phanimahesh left09:45
nuc joined09:45
des_consolado but if another user clones this repo and updates the file that is the hard link, will that also update the file in the sub repository?09:45
j416 no09:46
des_consolado: ^09:46
des_consolado (i.e. will the hard link be maintained through push/pull to and from remote, is git aware of inodes and all that?)09:46
ah, okay09:46
j416 des_consolado: git treats it as a regular file, nothing special, it does not care09:46
phanimahesh joined09:46
j416 des_consolado: it does do symlinks, though09:46
des_consolado yeah docker doesn't do symlinks :P09:51
it's cool though, just done some extra docker mounts09:51
stantonk joined09:52
mikecmpb_ left09:53
mikecmpbll joined09:54
stantonk left09:57
cyan__ left09:58
cdown left09:59
CausaMortis-Work left09:59
LiohAu If I do a "git merge develop -X theirs", does it takes "develop" version? or current branch version? develop right?10:01
cqi left10:02
canton7 yes10:02
LiohAu ok, so why does git tells me there's nothing to commit after that?10:02
I should have to commit the changes coming from develop, no?10:02
canton7 because the merge completed, created the merge commit, and you haven't made any changes since the merge?10:02
LiohAu no, only the merge10:03
canton7 ok, so the merge completed. why do you expect there to be uncommitted changes?10:03
'git log' will show it10:03
LiohAu so basically I have a PR open with 1 changed file. That PR cannot automaticlaly merged because someone changed the same file and pushed to develop10:03
I only want to make that PR automatically mergeable agian10:03
again*10:04
canton7 ok, so you'll need to merge develop into your PR branch10:04
you probably don't want to use -X theirs - that will override your changes in the case that there's a conflict10:04
LiohAu ok, so what I did with a "git merge develop -X theirs" + "git checkout --HEAD my_change_file"10:04
cdown joined10:04
LiohAu but I don't have any other change to make, so how do I push that new "state"10:05
canton7 why the checkout? that will just remove an uncommitted changes to my_change_file10:05
*remove any10:05
... but since there shouldn't be any uncommitted changes anyway, it won't do anything10:05
LiohAu because that file I want to keep "ours" version10:05
I read on S.O. that it is the same as "git checkout --ours -- <filename>"10:06
JeroenT left10:06
canton7 1) you don't combine two sets of changes by completely replacing what the other person did, and 2) like I said, that won't have done what you wanted it to do10:06
that checkout only does something if you're stopped in the middle of a conflicted merge10:06
your merge won't have conflicted, because -X theirs automatically resolves all conflicts in favour of them10:06
jceb left10:07
LiohAu Well in this case I want to replace its changes for that file, because he changed things without knowing that the whole file was being refactored..10:07
so, then how do I get all the new things from develop, and keep my changed file?10:07
canton7 then you'll remove all of the changes he made, don't forget10:07
undo your merge, do it again *without* -X theirs, when the merge stops because of a conflict, use 'git checkout --ours <filename>', then 'git commit' to complete the merge10:08
... then you'll have to re-do the changes he made by hand10:08
cyan__ joined10:09
LiohAu "then you'll remove all of the changes he made" => On that specific file yes, but I want to keep all the other changes he did.10:09
ikmaak left10:09
Meow-J joined10:09
LiohAu what? so if he changed 100 files, and we have a conflict on 1 file, I have to redo all the 100 changes?10:09
canton7 yeah, I was refererring to that particular file10:09
no10:09
LeMike joined10:09
canton7 just on that one file10:09
LiohAu oh ok, but as I said i don't get anything from him on that file10:10
ArchNoob joined10:10
GT4066 left10:10
canton7 you're saying he didn't change '<filename>'?10:10
LiohAu he did, but he should have undo when I told him that file was being deeply changed/refactored. And he forgot to undo, and pushed that file with the other changes..10:11
ikmaak joined10:11
canton7 ok10:11
the commands I gave above still apply then10:11
pcre_ left10:11
LiohAu ok so right now, "git reset --hard ORIG_HEAD" to cancel my "invalid merge" right?10:12
and your commands10:12
pcre joined10:12
canton7 yeah, unless you've done something since to reset ORIG_HEAD10:12
do you understand why what you were trying to do was failing?10:12
LiohAu I think that the file I was trying to checkout with --ours, was not in a conflict state, so the checkout was doing nothing, right?10:13
noidea joined10:14
Beams_ joined10:14
canton7 it's not just the file that wasn't in a conflict state: nothing was. If you use -X theirs, the merge will not conflict - the point of -X theirs is to automatically resolve conflicts. So nothing was conflicted. You just run a command to replace the contents of the file with what was in the previous commit (i.e. replace the result of the merge with the result of the merge)10:14
LiohAu actually I think I have a problem in the way conflicts are handled in git.10:15
canton7 I doubt that, but go on10:15
Beams left10:16
p4trix joined10:17
mika left10:18
mika joined10:18
King_DuckZ I want to parse the output of git submodule status to get the current state of each submodule (the +/- first char), is there a more scripting-friendly command to achieve the same? initialized submodules will have a trailing (heads/maste) which is causing extra work10:19
geoff-codes left10:19
indieross left10:19
CrazyBonz joined10:20
indieross joined10:20
romerocesar joined10:21
thalleralexander joined10:21
thalleralexander left10:22
nnyk_ left10:22
msonntag left10:23
thalleralexander joined10:24
hahuang61 joined10:24
thalleralexander left10:24
pcre left10:25
pcre joined10:25
nellicus_ joined10:25
romerocesar left10:26
LiohAu canton7, sorry got a call. So, I was saying that I may have misunderstood something, because when I merge without using ours/theirs what I see in the list of changes always makes me thing that my branch is taken in priority over the develop one.10:26
nnyk_ joined10:26
LiohAu this is why I wanted to use the -theirs10:26
canton7 a merge combines your changes with theirs - neither takes priority10:28
if you reach a case where both yours and theirs make the same change, so there's a question about which has priority, git creates a conflict10:29
ikmaak left10:29
hahuang61 left10:29
boombatower left10:30
msonntag joined10:30
boombatower joined10:31
xall left10:31
drewo joined10:32
waveclaw joined10:32
ikmaak joined10:32
LiohAu oh fuck10:33
netj left10:33
netj joined10:34
LiohAu git made an automatic merge on a file which is automatically generated from the one I told him to take my version10:34
canton7 you probably shouldn't be tracking generated files10:34
... but anyway, you can fix that file up, and git commit --amend to change the outcome of the merge10:34
fahadash joined10:34
LiohAu yeah I know, we are going to generate them in the build process soon :(10:35
canton7 ... but be sure to never edit a merge commit so that it contains changes which didn't come from either parent - those are so-called evil merges, and it's really hard to track down where the change was introduced10:35
mehola joined10:35
pcre___ joined10:36
rchavik joined10:36
pcre left10:36
LiohAu I don't even know how to fix my mistake10:36
canton7 1) run the script which generates the build output, 2) 'git add generatedfile', 3) 'git commit --amend'10:36
drewo left10:36
LiohAu I used the "git checkout --ours -- " as you said10:37
canton7 wait, stop10:37
are you still in the middle of a conflicted merge10:37
wait, you ran 'git checkout --ours --' and not 'git checkout --ours thefile'?10:37
LiohAu git checkout --ours -- thefile10:37
no i'm not in the middle of the conflicted merge anymore10:38
canton7 you scared me there10:38
ok, then the instructions I gave still hold10:38
johnmilton joined10:38
johnmilton left10:40
johnmilton joined10:40
JeroenT joined10:41
mehola left10:41
pcre___ left10:42
johnmilton left10:42
pcre_ joined10:42
LiohAu canton7: https://gist.github.com/LiohAu/4dff682428a92538c857532b85d8a7ce10:42
johnmilton joined10:42
LiohAu this is the log of what I did10:42
canton7 reads10:43
xall joined10:43
canton7 About_Page_Mobile_64256.feature.cs is the file which you both modified?10:43
LiohAu the .feature file is the file we both modified. The .feature.cs is an automatically generated one from the associated .feature10:43
johnmilton left10:43
canton7 ok, but you ran 'git checkout --ours' on the generated file?10:44
johnmilton joined10:44
canton7 hmm, About_Page_Mobile_64256.feature didn't conflict10:44
so you didn't edit the same lines in it10:44
LiohAu that's what is weird, you see, when I pulled with "git pull origin feature_file-about", it was like if the merge I did before was still there10:44
tvw left10:45
canton7 I don't know whether it was...10:45
tvw joined10:45
canton7 output of !lol ?10:45
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all10:45
auzty left10:46
johnmilton left10:46
LiohAu updated gist : https://gist.github.com/LiohAu/4dff682428a92538c857532b85d8a7ce10:46
johnmilton joined10:47
johnmilton left10:47
tristanp left10:47
johnmilton joined10:47
canton7 ok right, so you did the merge twice by the looks of it10:47
LiohAu how do you see it?10:47
oh the two "comments" saying the same thing10:48
what does a star and a line means ?10:48
yqt joined10:49
canton7 stars and commits. the line next to a star is the "commit_hash (branch name) commit message"10:49
Codfection joined10:49
rafalcpp left10:49
mrkat joined10:49
canton7 lines join commits together - they show which commits are the parents and children of which other commits10:49
time begins at the bottom, with the newer stuff on top10:49
so af0387d merges together 6cc1fbf and 167387a10:50
and 9dbcb99 does the same thing10:50
vls-xy joined10:50
canton7 so it looks like you did a merge, pushed it, then undid it locally and did it again10:50
... which is fine10:50
notebox left10:50
Impaloo left10:50
canton7 but merging in origin/feature_file-about (which contains your first attempt to do the merge, which you later undid) would be a mistake10:50
Impaloo joined10:50
canton7 ... being able to visualise git history is the first step to learning how to use git. The ascii output is useful for pasting over IRC, but is slightly cryptic to interpret. There are much better graphicaly tools: gitk is often distributed with git, or there are others10:51
johnmilton left10:51
JeroenT left10:51
JeroenT joined10:51
LiohAu i'm on osx :(10:51
johnmilton joined10:51
romerocesar joined10:52
canton7 I've got gitk on osx - can't remember whether it came pre-installed, with the homebrew git version, or whether it was in a separate homebrew package...10:52
there are other visualisers for mac as well10:52
vls-xy perhaps gitx suits your fancy: http://rowanj.github.io/gitx/10:53
MrWoohoo joined10:53
tristanp joined10:53
LiohAu Just installed the homebrew version, and its comes with it (default apple git does not have it)10:53
CheckDavid joined10:53
acetakwas joined10:54
canton7 cool10:54
LiohAu yeah gitk looks a little bit like 90's software :P10:54
canton7 'gitk --all &' in a git repo is a good way to launch it10:54
yeah, it's not pretty on osx - it's tcl/tk iirc, which gets rendered pretty badly10:55
it's better on windows, or even better on linux :P10:55
bremner it's not _pretty_ anywhere, but mac people seem to care more ;)10:55
canton7 it *is* worse-looking on mac though10:55
bremner haha10:55
justice!10:55
canton7 ><10:55
cdown left10:56
romerocesar left10:56
cdown joined10:56
LiohAu well maybe because we are used to see pretty things :P10:56
Beams joined10:56
LiohAu I would say that linux is for working stuff, windows is for beautilfull stuff, and osx is for having both :P10:56
CussBot left10:58
theskillwithin joined10:59
Beams_ left11:00
acetakwas left11:00
pcre_ left11:01
ArchNoob left11:01
boombatower left11:01
pcre__ joined11:01
CussBot joined11:01
rnsanchez joined11:02
rchavik left11:03
dimi1947 joined11:04
Impaloo left11:04
Impaloo joined11:04
white_gecko left11:08
theskillwithin left11:09
LiohAu canton7: I feel like if I were a variable in an infinite loop :'(11:09
tried to push, was rejected because : hint: Updates were rejected because the tip of your current branch is behind...11:10
ojdo left11:10
canton7 yep, because you changed a commit which you'd already pushed. you !rewrote public history11:10
LiohAu so I pulled, and the same conflict as the one I solved just before11:10
canton7 nooo don't pull here!11:10
bleh, !rewrite11:10
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/waqum11:10
LiohAu :'(11:11
canton7 normally, force-pushing is a bad idea. However it's very useful with PR branches: noone else is working from them, and github knows how to handle them, in order to change which commits are part of the PR11:11
so in this case you want to fix up your local branch so it has just the right merge in, the force-push it11:11
theskillwithin joined11:12
LiohAu so how do I cancel my pull ? without an rm -rf :P11:12
canton7 let's see that !lol output again11:12
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all11:12
canton7 we'll find a suitable commit to reset back to, and reset to it11:12
theskillwithin left11:13
LiohAu https://gist.github.com/LiohAu/4dff682428a92538c857532b85d8a7ce11:13
you have both the previous log, and the new one11:13
canton7 right, so we can see what the merge commit af0387d was merged into the merge commit 9dbcb9911:14
wait, no it doesn't11:14
ignore that11:14
ArchNoob joined11:14
PCatinean left11:15
canton7 right, so merge merged together 167387a and 6cc1fbf to make 9dbcb99, then edited that to make a7a44e4?11:15
LiohAu basically I want to keep 167387a11:15
yeah I want to keep 167387a + 6cc1fbf11:15
ojdo joined11:16
canton7 so what's wrong with a7a44e4?11:16
Beams_ joined11:17
LiohAu I don't know, I don't even know how to know what is inside :(11:18
canton7 I'll reword: is there anything wrong with a7a44e4?11:18
'git show' will show you its diff11:18
the "inside" of it is currently checked out in your working directory11:18
acetakwas joined11:19
LiohAu on the remote repo, there is af0387 which is half of what I wanted. The develop content is correctly integrated in the feature_file-about branch, the .feature file content is ok. Only the .feature.cs file is not.11:19
TomyWork Does the "tag" in "git pull $url tag $tag" make any sense there?11:19
canton7 Tomno11:20
*TomyWork, no11:20
TomyWork Jenkins writes that and I think it's an error on its behalf.11:20
git pull failed11:20
no further info, unfortunately11:20
cdown left11:20
canton7 LiohAu, shall we start over? Get this right first time, no confusion?11:20
Beams left11:21
LiohAu git show of a7a44e4 looks ok (If what is green is what is in this commit, then its what I want)11:21
canton7 what is green is what was introduced in that commit11:21
HoierM joined11:22
romerocesar joined11:22
canton7 anyway, if a7a44e4 contains what you want to keep, then you can replace what's on origin with it, by using 'git push -f origin feature_file-about'11:22
rahtgaz joined11:22
canton7 note that force-pushing is usually a VERY BAD IDEA. But it's fine in some cases, and PR branches is one of those11:22
white_gecko joined11:23
notebox joined11:23
LiohAu ok, but right now I can't push11:24
because my repo is in a conflicted state11:24
(I don't know why git log shows nothing about this)11:24
canton7 wait, you're in the middle of a merge commit? ok11:24
abort that: 'git merge --abort'11:24
LiohAu y11:25
durham left11:25
mkoskar left11:25
LiohAu ok11:25
xpk joined11:25
LiohAu what happens when I do that? ok, it cancel the merge, but what happens to the pull that raised the conflict ?11:25
hahuang61 joined11:25
white_gecko Is there any scientific literature about git?11:26
drewo joined11:26
canton7 LiohAu, hmm? do you know that 'pull' is just shorthand for 'fetch + merge'?11:26
romerocesar left11:26
LiohAu white_gecko: is this scientific : https://git-scm.com/doc ?11:26
canton7 so 'git pull origin master' is shorthand for 'git fetch origin; git merge origin/masteer'11:26
LiohAu canton7: no, but know I do :P11:27
canton7 so the 'git merge --abort' aborts the merge portion, but the fetch portion is left untouched11:27
NeonSynth joined11:27
LiohAu ok, so you tell me to push -f11:28
canton7 yep11:28
LiohAu but git status tells there's no pending commit11:28
canton7 pastebin?11:28
LiohAu $ git status11:28
On branch feature_file-about nothing to commit, working directory clean11:28
canton7 that means you have no uncommitted changes11:29
that means that a 'git commit' would be pointless11:29
but you still have local *commits* which origin doesn't have11:29
so you can push stuff11:29
rchavik joined11:29
LiohAu shouldn't git says something like "my branch is 1 commit ahead" or something like this?11:29
canton7 it'll probably say 2 ahead / 1 behind, if you've got tracking set up11:29
hk238 joined11:29
canton7 but you probably don't have tracking set up for that branch. Don't worry about it11:30
white_gecko LiohAu: It is a technical documentation so for computerscience, yes partially.11:30
hahuang61 left11:30
osse white_gecko: !bottomup11:30
gitinfo white_gecko: 'Git from the bottom up' starts with explaining the building blocks of git and proceeds to tell you how they fit together. http://ftp.newartisans.com/pub/git.from.bottom.up.pdf (http://ikke.info/git.from.bottom.up.pdf)11:30
white_gecko but i was especially looking for something like a formal mathematical model about commits, merges, diffs, rebase, … ?11:30
acetakwasabstract11:31
jatin30 joined11:31
david007 left11:31
drewo left11:31
david joined11:31
LiohAu canton7: https://gist.github.com/LiohAu/4dff682428a92538c857532b85d8a7ce11:31
abstractGuest227411:31
davidGuest4052711:31
canton7 LiohAu, yes?11:31
LiohAu the feature_file-about has no arrow like the HEAD one, this means there's no tracking setup ?11:32
cdown joined11:32
canton7 yes11:32
'git branch --set-upstream-to origin/feature_file-about'11:32
Guest40527 left11:32
canton7 'git branch --set-upstream-to=origin/feature_file-about'11:32
david007 joined11:32
Guest2274whatsapp11:32
LiohAu I thought tracking was automatically setup when you make a "git checkout -b branch_name" and then "git push origin branch_name"11:32
whatsappgoogle11:33
canton7 LiohAu, it's automatically set by 'git checkout -b branch_name origin/branch_name'11:33
'push' doesn't set it unless you pass it -u11:33
googlegoogledocs11:33
jatin30 when I cherry-pick and get merge conflicts I resolve them manually using mergetool, meld. I do not read on the whole code I just add anything which is extra and kindof resolve the merge conflicts randomly which just does not seem right. Any correct way of doing it? Should I use git pull --rebase ?11:33
LiohAu so I should change my habits when I create a feature branch and use "git checkout -b branch_name origin/branch_name" instead of "git checkout -b branch_name" ?11:34
white_gecko osse: I need a password for the newartisans, but is the ikke.info link the official one?11:34
canton7 LiohAu, no! they do completely different things11:34
'git checkout -b branch_name' creates a new local branch, branch_name, based off your currently-checked-out branch11:34
'git checkout -b branch_name origin/branch_name' creates a new local branch, branch_name, based off the remote branch origin/branch_name11:34
you use the former to create a new branch, and the latter to start working on a branch which someone else created11:35
PioneerAxon left11:35
osse white_gecko: I don't know. _ikke_ is the guy hosting it.11:35
but it seems to be the exact same document11:35
PioneerAxon joined11:35
_ikke_ I'11:36
I'm mirroring it because it was down some time ago11:36
mehola joined11:37
_ikke_ The ftp one works for me though11:37
osse it's not a dead link, but I have to log in11:38
_ikke_ Hmm, I don't get a login prompt11:39
jatin30 why does this not work https://bpaste.net/show/82bdda582874 ?11:40
Beams joined11:41
mehola left11:41
_ikke_ You have a conflict11:42
osse jatin30: the patch doesn't apply cleanly11:42
_ikke_ You need to fix the conflict11:42
white_gecko is there a repo with the sources of thei pdf?11:42
osse unfortunate, but not unexpected11:42
jatin30 osse, what should I do to fix this?11:43
osse jatin30: !eek11:43
gitinfo jatin30: [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II11:43
flaguy48 left11:43
osse 'git status' and 'git diff' are good starting points also11:43
raindev joined11:43
MrMojito joined11:44
Beams_ left11:44
JeroenT left11:45
jatin30 osse, there are good chances that I might have randomly resolved some previous merge conflicts by no proper judgement as to which part of file is more relevant. I just made the three copies exactly similar using mergetool and finished the cherry-pick. what is the worst thing that could happen?11:45
mdw joined11:46
Noldorin joined11:46
mdw left11:46
rchavik left11:47
osse jatin30: the worst that could happen is that the source code in the mentioned file won't compile, or will do something else than intended11:47
mdw joined11:47
DieguezZ left11:48
circ-user-foXmx left11:49
jatin30 left11:50
jatin30 joined11:50
jatin30 sorry my system hung. osse, could you please copy your ans to my last question please, if you did ans.11:51
!eek11:51
gitinfo [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II11:51
cdown left11:51
osse jatin30: the worst that could happen is that the source code in the mentioned file won't compile, or will do something else than intended11:51
cdown joined11:51
jatin30 osse, I was afraid of that! any way I could stop that?11:51
osse jatin30: either fix the conflict or abort the cherry-pick11:52
JeroenT joined11:52
stratos joined11:52
white_gecko In which cases is it not enought for a three way merge to take the latest common acestor of two commits? When do you actually need recursive three way merge?11:53
jatin30 osse, conflicts are fixed. cherry picking is done11:54
let me test it on my phone and see what happens11:54
mahendra_ joined11:55
aswen left11:56
bruce_lee joined11:56
bruce_lee left11:56
bruce_lee joined11:56
jatin30 but after every cherry-pick I do a repo sync before the next cherry-pick and it runs fine. as repo sync runs fine I am guessing Its compiling properly right?11:57
rchavik joined11:57
osse whether it compiles properly only javac can tell you11:57
not git, and certainly not me11:58
tvw left11:58
jatin30 oh yes11:58
that was so lame11:58
ok thanks11:58
mahendra_ left11:58
osse i don't know what a "repo sync" is, but why are you doing all these cehrry picks?11:58
synthroid joined11:59
notebox left12:00
akitada left12:00
jatin30 we are building on cyanogenmod for making an OS12:00
so cherry picking basic features for that12:00
synthroi_ joined12:01
kedare left12:01
jatin30 left12:01
notebox joined12:01
flaguy48 joined12:01
tvw joined12:01
DieguezZ joined12:02
yqt left12:02
tomog999_ joined12:03
synthroid left12:03
Andrew_K left12:04
tomog999 left12:06
pioiytr joined12:06
wspider I have two branches with folder 'foo', I deleted that folder from branch A because I want both to have the foo content of B, so I deleted foo from A and tried to merge with B12:06
xall left12:06
wspider mergin A with B or B with A, the result doesn't have the foo folder so i 'git reflog' and reset --hard according and am up to trying new things until I get what I wanted12:07
liquidjamm joined12:07
wspider any hint ?12:07
LiohAu wspider: canton7 will help you :P12:07
pioiytr_ left12:07
rchavik left12:09
canton7 hey, I'm eating lunch: give me a break :)12:09
bremner /kick canton712:09
as requested ;)12:09
wspider LiohAu: haha :>12:09
LiohAu :D12:10
i'm gonna eat too12:10
canton7: are you in CET area ?12:10
canton7 ish - GMT12:10
TestUser joined12:10
jeffreylevesque left12:11
LiohAu hm I see you're on c# and iphonedev channels, are you a xamarin user ?12:11
(or a polyglot :P)12:12
NeverDie joined12:12
tristanp left12:13
NeverDie left12:14
NeverDie joined12:14
wspider halp12:14
xd12:15
NeverDie left12:15
NeverDie joined12:15
maaarghk joined12:15
canton7 LiohAu, I work at a consultancy, so a bit of everything12:16
maaarghk Hello. In 2.9 --allow-unrelated-histories was added as an option to "git merge". The release note below taht says that "git pull" has been taught to pass that option to the underlying git merge. However, git rebase does not appear to have been taught the same thing. Is there a way to pass that option from rebase?12:17
canton7 there's no 'underlying merge' for a rebase12:17
rebase and merge are separate things12:17
M-mistake left12:18
M-meznak left12:18
M-shine left12:18
maaarghk git rebase uses merge, right? hence -s and -X options being passed down.12:18
mdw_ joined12:18
qknight left12:19
rwb joined12:19
canton7 sort of. git rebase takes a set of commits, and one-by-one cherry-picks them onto a branch (well it's not exactly cherry-pick, but close enough)12:19
so rebase doesn't take two histories and creates a single merge commit12:19
it takes a set of commits, and individually merges each one (effectively) onto a given branch12:20
drewo joined12:20
mdw left12:21
Asenar joined12:21
maaarghk yeah, I should have been clearer though and mentioned that I have --preserve-merges as an option to git rebase, which means that merge commits are being created12:21
However they are currently failing with 'refusing to merge unrelated histories' error, and I am trying to work out how to use the git merge --allow-unrelated-histories switch to get past that12:22
romerocesar joined12:22
wspider LiohAu: I already figured out, thanks !!12:24
tristanp joined12:25
jeffreylevesque joined12:25
drewo left12:25
lindenle joined12:25
deadnull joined12:25
raindev left12:25
hahuang61 joined12:26
toogley left12:27
romerocesar left12:27
toogley joined12:27
aswen joined12:28
lindenle left12:29
hahuang61 left12:31
romerocesar joined12:33
tvw left12:33
encod3 joined12:35
romerocesar left12:37
mehola joined12:38
ThomasLocke joined12:38
liquidjamm left12:38
raindev joined12:40
rafalcpp joined12:40
adrianoc joined12:41
AaronF joined12:41
raindev left12:42
rchavik joined12:42
mehola left12:42
umbSublime joined12:43
umbSublime left12:43
umbSublime joined12:43
DieguezZ left12:43
adrianoc hi all ... how i can authenticate git clone http://... with ssh key (git clone ssh://)12:47
BlackMaria joined12:48
liquidjamm joined12:51
rgrinberg joined12:51
spb adrianoc: by using an ssh URL12:51
qpdb left12:51
liquidjamm left12:52
CheckDavid left12:52
adrianoc sbp, ssh is blocked.12:52
Bombe Then you obviously can not use it for authentication.12:53
daniel_rose joined12:53
stantonk joined12:54
adrianoc i want to make with a gitHub12:54
TooLmaN joined12:55
M-shine joined12:55
liquidjamm joined12:55
Eryn_1983_FL left12:56
harish joined12:56
zhbc joined12:57
espindola joined12:57
grawity adrianoc: neither HTTP nor HTTPS uses ssh keys12:57
adrianoc: you can however use ssh://git@ssh.github.com:443/12:57
adrianoc: see https://help.github.com/articles/using-ssh-over-the-https-port/12:57
cuebix-wk joined12:58
Eryn_1983_FL joined12:59
Masterphi joined12:59
adrianoc grawity, it's better.13:00
stantonk left13:00
grawity ?13:00
stantonk_ joined13:00
CalimeroTeknik oh, .git folders are ignored by default? I know this is git abuse, but I'm running incremental backups of folders containing git repos using git13:02
jimi_ joined13:02
zhbc left13:02
CalimeroTeknik using add -Af works even for gitignored files, but not for .git folders13:02
s/folders/directories/13:03
mikecmpb_ joined13:03
david007 left13:04
Masterphi left13:04
tjone270_ joined13:05
grawity they're *always* ignored13:05
tjone270 left13:06
adrianoc grawity, i try this way. thanks.13:06
rgrinberg left13:06
adrianoc no now, because my server have not http configured.13:07
mikecmpbll left13:07
rgrinberg joined13:07
adrianoc and how i can't access ssh, just the night to test.13:07
tchan joined13:08
dimi1947 left13:08
ExoUNX joined13:08
ExoUNX left13:08
ExoUNX joined13:08
grawity what server13:10
daniel_rose left13:10
crose joined13:12
notebox left13:13
dimi1947 joined13:14
notebox joined13:14
drewo joined13:14
livingstn joined13:15
pcre__ left13:17
ThomasLocke left13:17
usm4n joined13:17
adrianoc grawity, my server, deskfacil.com13:18
grawity you were talking about github minutes ago13:18
adrianoc i cant access ssh inside my work.13:18
usm4n left13:18
phanimahesh left13:18
Klipp joined13:18
adrianoc grawity, yes, as example.13:18
ThomasLocke joined13:18
grawity well, if it's not github, then you're out of luck13:19
DieguezZ joined13:19
drewo left13:20
adrianoc grawity, thanks, you helpe much.13:20
later i tell you if worked :)13:20
perlpilot adrianoc: or ... configure your server to handle http(s)13:20
M-mistake joined13:21
M-meznak joined13:21
clmsy left13:23
ash_workz joined13:23
freimatz left13:24
usm4n joined13:24
DieguezZ left13:24
adrianoc perlpilot, bu i want using one password.13:25
raijin left13:25
grawity configure your server to use TLS certificate auth13:25
osse King_DuckZ: the more complex parts of that question are probably best asked on the mailing list. As for the superficial parts it seems he answered his own question in that post13:26
kedare joined13:28
adrianoc left13:29
Dro left13:29
pmst joined13:30
todd_dsm joined13:30
SteffanW joined13:30
daniel_rose joined13:30
aswen left13:31
g105b joined13:31
marc_v92 joined13:32
SteffanW left13:32
circ-user-foXmx joined13:32
g105b I know the answer is going to be "it depends", but I'm struggling to make my own opinion and I'd appreciate it if someone could point me to some recommended reading or their own advice on this. My company automatically deploys the master branch to live, whenever there's a commit. We branch away from master for each issue, or for big changes, introduce13:35
another branch to branch from for sub-issues. My question is whether we should be rebasing the child branch on the parent branch before each merge? I can't make any sense of why this is regarded as beneficial by some people, but there are many people itching to use rebase over simple merging. Thanks.13:35
stratos left13:35
Duikb00t left13:36
cqi joined13:38
GodGinrai joined13:40
rchavik left13:41
rahtgaz left13:41
HanClinto joined13:42
rahtgaz joined13:42
osse !merge_vs_rebase > g105b13:43
gitinfo [!merge_or_rebase] For a detailed discussion of the dis-/advantages of merge and rebase, and when to best use which, see: https://coderwall.com/p/ny1hia -- and here's how Linus explains which one to use: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html13:43
osse g105b: a major part of it is preference. some like the log being a straight line13:43
g105b Thanks!13:44
todd_dsm left13:45
perlpilot I suspect those people come from svn or some svn-like system13:45
hwoarang left13:45
DieguezZ joined13:46
DieguezZ left13:46
arooni__ left13:46
kbs joined13:46
wodim is it possible to push to all remotes at once?13:46
madknight wodim, https://stackoverflow.com/questions/5785549/able-to-push-to-all-git-remotes-with-the-one-command13:47
wodim yeah that's what I was reading. ugly tho13:47
but ok fair enough13:47
perlpilot xargs is ugly?13:48
wodim no, I just thought there would be a git command for it by now--usually stackoverflow answers are outdated13:48
hwoarang joined13:48
raijin joined13:49
madknight wodim, you can alias it, there is also no command "git squash" but cool aliases13:50
pmst left13:55
Gsham joined13:57
Gamecubic joined13:58
notebox left13:58
Rodya_ joined13:58
tristanp left13:59
rscata left13:59
GodGinrai wodim: pushing to all remotes at once is an edge-case, which is probably why there isn't a command for it14:00
marc_v92 left14:00
wodim not an edge case for me :P14:00
but ok14:01
phaleth joined14:01
cdg joined14:02
moriko joined14:03
diegoviola joined14:03
stantonk_ left14:04
usm4n_ joined14:04
unbalancedparen joined14:05
Darren_ joined14:05
marc_v92 joined14:05
tristanp joined14:07
usm4n left14:07
D-Boy left14:07
drewo joined14:08
al-damiri joined14:09
cdg left14:09
qt-x left14:10
gduine joined14:10
ThomasLocke left14:11
fmcgeough joined14:12
drewo left14:13
marc_v92 left14:14
D-Boy joined14:14
circ-user-foXmx left14:14
dreiss joined14:18
qpdb joined14:18
stantonk joined14:19
usm4n_ left14:19
ArchNoob left14:20
Vinnie_win_a joined14:21
Vinnie_win left14:21
johnny56_ left14:22
NeverDie left14:23
stantonk left14:23
Rodya_ left14:23
cdown left14:25
dmj` joined14:25
cdown joined14:26
bremner left14:26
bremner joined14:26
bremner left14:26
bremner joined14:26
moriko left14:26
Passe_a_Manteiga joined14:26
l0rdPE joined14:27
hahuang61 joined14:27
mikecmpbll joined14:28
catag87 joined14:28
Asiajey joined14:29
lugzer left14:31
mikecmpb_ left14:31
LionsMane joined14:32
circ-user-foXmx joined14:32
hwoarang_ joined14:32
hahuang61 left14:32
thiago joined14:32
moriko joined14:33
crose left14:34
Repox left14:34
Rodya_ joined14:34
kbs left14:34
phanimahesh joined14:35
cqi left14:35
lordjancso left14:35
hwoarang left14:35
notebox joined14:35
tvon left14:36
yqt joined14:36
JeroenT left14:36
daniel_rose left14:36
MadHatter42 joined14:37
rominronin left14:37
phanimahesh CalimeroTeknik: Using git to "backup" folders containing git repos is definitely way more than git abuse. please don't do it. :P14:38
CalimeroTeknik well, I can do tarballs14:40
but that's going to be even worse since it uses up a lot of space14:40
phanimahesh Push to a git remote.14:40
daniel_rose joined14:40
phanimahesh And disable gc on server.14:40
You'll have as good a backup as you can get.14:40
mariuscc left14:41
CalimeroTeknik push from what?14:41
ncd|leeN left14:41
CalimeroTeknik what about the gitignored files?14:41
rantic_work joined14:42
CalimeroTeknik and it's not one but dozens of repos that are in there14:42
johnny56_ joined14:43
CalimeroTeknik I know it's a mindset problem, but from your answer I can only derive one, even worse monstrosity: since git won't add all files, I can follow tarballs of that all these files with git14:43
which is highly inconvenient14:43
kbs joined14:43
phanimahesh Oh. so you have multiple git repos, and you want to have backups to be able to restore to the exact state, including ignored files.14:44
CalimeroTeknik yeah, I could do tarballs every day, and even deal with the trouble of making incremental tarballs14:44
but git sounded like a cool revision history tool, except it refuses to follow everything14:44
ribasushi joined14:44
phanimahesh Is some scripting an option?14:45
The contents of .git are not supposed to be version controlled. Trying to do that will end in a monstrosity worse than tarballs.14:45
CalimeroTeknik a tailor-made solution? that's more likely to leave some stuff out than a bulky solution14:45
GodGinrai CalimeroTeknik: dozens of what kind of repos? git repos?14:45
CalimeroTeknik yes14:45
GodGinrai Why not just push all of those repos to another server14:46
phanimahesh Two .git directories can be equivalent even when they are wildly different from the view of file system.14:46
CalimeroTeknik what about ignored files? (data files)14:46
phanimahesh Have you seen !config14:46
gitinfo [!configfiles] It is recommended to store local configuration data in a file which is not tracked by git, but certain deployment scenarios(such as Heroku) may require otherwise. See https://gist.github.com/1423106 for some ideas14:46
ToxicFrog CalimeroTeknik: if you want a backup/sync tool that uses git as the backend/transport format, there are a bunch; bup and sparkleshare come to mind14:46
GodGinrai CalimeroTeknik: if they are ignored, then they don't belong in the repo in the first place, so you shouldn't need to back them up.14:46
cdown left14:47
CalimeroTeknik they don't belong in the repository for sure, but when I backup the whole thing I want them in14:47
GodGinrai CalimeroTeknik: why, what are they? Build Artifacts?14:47
rgrinberg left14:47
CalimeroTeknik config and dictionary data14:47
the code in the multiple repos is the application code for accessing the dictionary, or using that, etc14:48
stantonk joined14:48
bremner the thing about backups is you don't want them to be a special hack only you understamd14:48
CalimeroTeknik absolutely14:48
thanks for the pointers, I'll see if bup/sparkleshare can do that for me14:48
bremner so just use a "normal" backup software, there are many choices14:48
GodGinrai I think you should just backup with rsync or something14:48
lindenle joined14:49
livingstn left14:49
GodGinrai rather than trying to shoehorn git14:49
CalimeroTeknik `rsync log` doesn't exist and makes no sense, right?14:49
git log does14:49
GodGinrai No, your comment just now made no sense14:49
if you want a log of backups, you can easily make that14:50
diegoviola left14:50
GodGinrai git is a source control tool, not a backup tool14:50
ToxicFrog GodGinrai: rsync is a sychronization tool but doesn't really make a good backup tool, although you can hack together one on top of it14:51
CalimeroTeknik: FWIW I've been using bup in production for a few years now, storing 2-300GB of backed up data, without issues14:51
GodGinrai ToxicFrog: it makes for a better one than git does.14:51
bremner sure. But there are still _many_ backup tools.14:51
ShekharReddy joined14:51
ToxicFrog GodGinrai: oh, certainly14:51
baraba joined14:51
bremner duplicity, obnam, bup, ...14:51
maaarghk rsync [...] > /some/git/repo14:52
if you must14:52
but i agree with everyone else just use a proper backup package14:52
lindenle left14:53
Rodya_ left14:53
leeN joined14:54
clemf joined14:56
kbs left14:56
CalimeroTeknik ToxicFrog, do you get functionality equivalent to git diff / git log with bup?14:56
being able to see line by line diffs between snapshots14:57
grawity wonder if you could 'subtree-merge' all the repos you're trying to back up14:57
MrMojito left14:58
thiago left14:58
ToxicFrog CalimeroTeknik: "git log", yes. "git diff" only if your backups are small enough for git to compute the diff without crashing.14:58
In my case they aren't.14:58
(you can access bup repos with normal "git" tools, but a lot of git commands don't work well when the repo is hundreds of GB in size)14:59
CalimeroTeknik nice! I'm not backing up more than a few hundred MBs anyway14:59
tvon joined15:00
ferr joined15:02
drewo joined15:03
catag87 left15:03
GodGinrai grawity: he's trying to backup non-tracked files as well15:04
ferr left15:04
catag87 joined15:04
SwiftMatt joined15:05
googledocsacetakwas15:05
rgrinberg joined15:05
diegoviola joined15:06
drewo left15:07
ferr joined15:09
pcre_ joined15:09
GodGinrai left15:10
apathor left15:10
maaarghk left15:11
chachasmooth left15:12
GodGinrai joined15:12
GodGinrai left15:12
GodGinrai joined15:12
dmj` left15:12
nuc left15:13
GT4066 joined15:13
chachasmooth joined15:14
moriko left15:15
ShekharReddy left15:15
Masterphi joined15:15
pcre_ left15:16
pcre_ joined15:16
MadHatter42 left15:17
Balliad left15:18
King_DuckZ in my script I want to get the full absolute remote address to a git submodule, in a way that git clone understands - so if current branch is tracking origin/master and origin is github:KingDuckZ/blah.git, and the submodule's path is ../foo.git, I want to get github:KingDuckZ/foo.git15:19
AaronF left15:19
King_DuckZ I'm not sure how to handle that in my ruby script, so I'm wondering if git can already provide that info15:19
tristanp left15:20
zivester joined15:20
johnmilton left15:21
ash_workz left15:21
DieguezZ joined15:22
Alienpruts left15:23
MZAWeb joined15:23
romerocesar joined15:24
Asiajey left15:24
gkatsev joined15:25
ash_workz joined15:25
stuh84 joined15:25
Asiajey joined15:26
Asiajey left15:26
Asiajey joined15:26
tristanp joined15:27
hahuang61 joined15:28
pcre_ left15:29
romerocesar left15:29
DieguezZ left15:30
Rodya_ joined15:30
stuh84 left15:31
lugzer joined15:31
BombStrike left15:31
ajf- joined15:32
hahuang61 left15:33
gduine left15:33
romerocesar joined15:34
hmdkny joined15:36
lugzer left15:36
cdown joined15:36
lindenle joined15:36
shinnya joined15:36
chrisshattuck joined15:38
daniel_rose left15:38
TheodoreBe joined15:38
romerocesar left15:39
Masterphi left15:40
InfoTest joined15:40
deadnull left15:40
stantonk left15:40
ferr left15:40
white_gecko left15:40
Masterphi joined15:41
stantonk joined15:41
baraba left15:41
dreiss left15:43
thiago joined15:45
cyan__ left15:45
EvilPenguin joined15:46
cdown left15:46
kpease joined15:46
circ-user-foXmx left15:47
dreiss joined15:49
Passe_a_Manteiga left15:49
cdown joined15:51
hmdkny left15:51
crameth joined15:54
dreiss left15:54
cxybeb joined15:55
dmj` joined15:55
D[4]ni joined15:55
spriz left15:56
Jellyg00se left15:56
hashpuppy joined15:56
UncleCJ joined15:57
drewo joined15:57
Rodya_ left15:57
ArchNoob joined15:58
elosz joined15:58
spriz joined15:58
stantonk left15:59
SteffanW joined16:00
acetakwas left16:00
stantonk joined16:00
drewo left16:01
acetakwas joined16:02
kedare left16:03
mikecmpbll left16:03
sangy joined16:04
acetakwas left16:06
acetakwas joined16:06
circ-user-foXmx joined16:06
jimi_ left16:07
PabloR joined16:08
jimi_ joined16:10
TheodoreBe left16:10
jimi_ left16:10
muelli left16:11
daniel_rose joined16:11
yqt left16:11
arooni_ joined16:12
zeroed joined16:13
Orbitrix left16:13
madewokherd joined16:13
UncleCJ left16:16
xlegoman joined16:17
Vgr left16:17
arooni_ left16:17
Ranhir joined16:18
ImJune joined16:18
arooni joined16:19
NeXTSUN joined16:21
stantonk left16:22
stantonk joined16:23
romerocesar joined16:24
emPi joined16:25
tristanp left16:25
PioneerAxon left16:26
PioneerAxon joined16:28
crameth left16:28
stantonk left16:28
catag87 left16:28
ImJune left16:28
Chiko left16:29
tristanp joined16:29
hahuang61 joined16:29
dmto joined16:29
romerocesar left16:29
chll_ left16:30
LeMike left16:30
PioneerAxon left16:30
kurkale6ka left16:30
PioneerAxon joined16:30
encod3 left16:31
encod3 joined16:32
lugzer joined16:32
ascarter joined16:32
stantonk joined16:32
TomyWork left16:33
preyalone joined16:33
hahuang61 left16:34
Matrixiumn joined16:34
DieguezZ joined16:35
maxb_maxb16:36
catag87 joined16:36
encod3 left16:36
lugzer left16:37
LionsMane left16:37
IWishIKnew joined16:37
OnBrokenWings joined16:38
jwarren_ joined16:39
texinwien joined16:39
achadwick left16:39
DieguezZ left16:40
mrkat- joined16:40
jwarren_ Howdy folks. I'm migrating a heafty repo from GitHub to Bitbucket. Of course migrating the code is easy, but I'm also trying to migrate closed and open pull requests, which seems to be more difficult. I found https://gist.github.com/piscisaureus/3342247 which describes how to pull PRs to your local machine, but is it possible to push PRs to a remote? IE the new Bitbucket repo? I'm guessing that the answer is no, and I probably need to16:41
Thoughts?16:42
PabloR I have git 2.6.2 on my OSX 10.9.5 Somebody helped me and I don’t recall installation method. Should I update thru homebrew or other method is preferable? Should I delete Git and start from scratch?16:42
dangerousdave joined16:42
jwarren_ I prefer to update through Homebrew, but I know others don't care for that method.16:42
mrkat left16:43
drewo joined16:43
PabloR If homebrew wasn't the original method, does it matter if I use it now? Should I delete git altogether and start from scratch?16:43
cdg joined16:46
rgrinberg left16:46
mdw joined16:47
mdw_ left16:47
TheVoid- joined16:48
jwarren_ PabloR If homebrew wasn't the original installation, it'll just install a new Git and add it to the system path, I believe. That's the way I prefer to do it, I don't like writing over system default stuff generally.16:49
thiago left16:49
tango_ joined16:49
PabloR jwarren_ ok thanks16:49
pioiytr left16:50
pioiytr joined16:50
jwarren_ I don't know Homebrew super well, but there's a way you can look up what's been installed with it. Try brew --help or something.16:50
PabloR great. thanks16:50
TomyLobo joined16:51
jwarren_ Looks like the command is "brew list" @PabloR16:51
PabloR Ah, git came up :p16:52
Masterphi left16:52
jimi_ joined16:52
synthroi_ left16:52
jwarren_ PabloR: Then I think you can do something like "brew upgrade git".16:53
PabloR jwarren_ Yes. I got to this page https://github.com/Homebrew/brew/blob/master/share/doc/homebrew/FAQ.md16:54
tristanp left16:54
thiago joined16:55
romerocesar joined16:55
Beams left16:56
jwarren_ PabloR: Awesome, good luck with the upgrade!16:56
PabloR it's upgrading. Thanks16:56
cyan__ joined16:57
ArchNoob left16:58
nwkj86 joined16:58
romerocesar left16:59
aguimaraes1986 left17:00
kab left17:01
Masterphi joined17:01
aguimaraes1986 joined17:02
stantonk left17:02
EvilPenguin left17:02
ajf- left17:03
freimatz joined17:03
troulouliou_div2 left17:03
stantonk joined17:04
stantonk left17:04
cdown left17:04
vls-xy left17:04
cdown_ joined17:04
jwarren_ left17:04
blackwind_123 left17:05
OnBrokenWings left17:05
nwkj86 left17:06
notebox left17:06
blackwind_123 joined17:06
King_DuckZ left17:08
usm4n joined17:08
tristanp joined17:08
OnBrokenWings joined17:09
stuh84 joined17:09
mariuscc joined17:10
OnBrokenWings left17:11
Rodya_ joined17:12
kbs joined17:12
stantonk joined17:12
ascarter left17:13
cdown_ left17:13
usm4n left17:14
tristanp_ joined17:14
nnyk_ left17:15
tristanp left17:15
dunpeal joined17:17
catag87 left17:17
irco joined17:17
dunpeal How do I control the "Committer Name" field of a commit from the command line? I can control the Author with --author, is there anything similar for the committer name?17:18
nnyk_ joined17:18
Doginal joined17:19
pioiytr left17:19
NeXTSUN left17:20
dimi1947 left17:20
pioiytr joined17:21
dimi1947 joined17:21
stuh84 left17:22
FunkyAss left17:22
EvilPenguin joined17:23
pwnz0r joined17:23
NeXTSUN joined17:23
circ-user-foXmx left17:24
sfjohansson joined17:24
mathewdgardner joined17:24
SwiftMatt left17:25
sfjohansson Hey guys, I would like to get rid of alot of old history in my git repo, I’m using sourcetreee as my client17:25
mehola joined17:25
ojacobson Read as: "I would like to author a completely new, shorter history"17:25
romerocesar joined17:26
ojacobson because that's the only way to do that, in Git.17:26
usm4n joined17:26
mathewdgardner left17:27
sfjohansson sounds like that would be it :)17:27
OnBrokenWings joined17:27
mehola left17:28
OnBrokenWings left17:28
durham joined17:28
manizzle joined17:28
manizzle hey guys. I do git remote add $BLAHBLAH17:28
but I only want to add it for fetchs, not push17:29
I dont want to accidentally push to that remote ever17:29
zeroed left17:29
manizzle http://stackoverflow.com/questions/7556155/git-set-up-a-fetch-only-remote17:29
nvm found17:29
hahuang61 joined17:30
romerocesar left17:30
GodGinrai manizzle: you can use quotes to make that url something more legible17:31
so that you get an error message that makes sense17:31
as seen here: http://stackoverflow.com/questions/10270027/can-i-mark-a-git-remote-as-read-only17:31
Silenced_v2 joined17:31
bremner left17:31
blackwind_123 left17:32
PabloR jwarren_ or anybody. I had an issue with updating git thru homebrew. Can anybody help?17:32
upgrade: Error: The `brew link` step did not complete successfully. The formula built, but is not symlinked into /usr/local. Could not symlink bin/git”.17:32
manizzle GodGinrai, thanks!17:32
TheodoreBe joined17:32
bremner joined17:33
bremner left17:33
bremner joined17:33
PabloR Seems that I had git installed with 2 different methods because when I first run “git version” gave me back 2.6.2. However brew list gave me 2.4.3 and upgraded to 2.9.1. There was an error during the brew upgrade: Error: The `brew link` step did not complete successfully. The formula built, but is not symlinked into /usr/local. Could not symlink bin/git”.17:33
circ-user-foXmx joined17:33
lugzer joined17:33
Rodya_ left17:33
troulouliou_div2 joined17:33
usm4n left17:34
Silenced_v2 left17:34
Silenced_v2 joined17:34
Rodya_ joined17:34
TheodoreBe left17:34
jimi_ left17:34
hahuang65 joined17:34
PabloR I have a bit more info. I really appreciate the help17:35
hahuang61 left17:35
kbs dunpeal: dunno about args, but GIT_COMMITTER_NAME='a' GIT_COMMITTER_EMAIL='b' git commit -m 'foo' should work ?17:36
rgrinberg joined17:36
mwhooker joined17:36
usm4n joined17:36
usm4n left17:36
blackwind_123 joined17:36
NeXTSUN left17:37
lugzer left17:38
FunkyAss joined17:39
TheodoreBe joined17:40
PioneerAxon left17:40
tristanp_ left17:40
kulelu88 joined17:40
PioneerAxon joined17:41
troulouliou_div2 left17:42
tristanp joined17:43
sfjohansson ojacobson what would be the workflow for writeing a new shorter history?17:43
bronson joined17:45
arooniarooni__17:45
anth0ny joined17:45
realz left17:45
snowkidind joined17:46
dunpeal kbs: thanks.17:46
snowkidind I have an xcode project which contains two targets: a osx shell and a static library17:46
Repox joined17:46
snowkidind what is the recommended repo structure for something like that17:46
(i'm developing the library from within the workspace)17:47
dunpeal Github question: I'm trying to create a simple PR, but when I review it, I see changes in addition to the ones I made, specifically: CHANGELOG.md is modified. How do I control/prevent these additional changes?17:48
ojacobson sfjohansson: I'd start with man git-filter-branch personally, but there's no easy way to do it17:48
gitinfo sfjohansson: the git-filter-branch manpage is available at http://jk.gs/git-filter-branch.html17:48
ojacobson dunpeal: that change must have been introduced by some commit in `git log origin/target-branch...your-branch`17:48
(three dots)17:48
Rewrite your branch to not include that change (and probably put it on another branch)17:49
PabloR Any help with my git installation issue?17:50
djb-irc left17:50
kbs wonders if git commit-tree is the crude answer for sfjohansson :-)17:50
dmj` left17:50
blackwind_123 left17:52
Repox left17:53
sfjohansson hmm… so I’ve been using git quite basically… what is the idea cocnept with these rewriting of history…how should I look at it?17:54
so now i prettymuch have jsut one ver very long branch17:54
Silenced_v2 left17:55
sfjohansson do I create a new bracnh and sort of copy over “grouped commits” and moving back and forth deleting etc… =O17:55
preaction PabloR: that's a homebrew issue, not a git issue. look for help from the homebrew folks17:55
PabloR preaction ok thanks17:56
kbs sfjohansson: the underlying data model is very simple - a commit is literally a data structure with a pointer to a tree, and zero or more commit objects (its parents.) You can invent a new commit object (for instance) that points to your latest tree and no parent, and this will look like a branch with zero history, but with all the files of interest.17:56
tvon left17:57
MatrixiumnXack17:57
Sasazuka joined17:57
kbs there aren't really any semantics about a commit other than this - all git does is provide (endlelly confusing?) ways to manipulate them ;-)17:58
usm4n joined17:58
sfjohansson kbs it certianly seem to work on confusing me…..=O17:58
dunpeal ojacobson: It doesn't look like it. I just forked origin, made a simple change to master, and now trying to merge back to origin/master.17:58
It looks like some sort of automated change...17:58
rahtgaz left17:59
kbs sfjohansson: haha. I've found much zen in just doing "git cat-file -p HEAD" and looking at what it means17:59
dunpeal autogenerated by the pull request? Is that something Github supports?17:59
mathewdgardner joined17:59
daniel_rose left17:59
LionsMane joined18:00
johnmilton joined18:00
Silenced_v2 joined18:01
Silenced_v2 left18:01
Silenced_v2 joined18:01
ojacobson No.18:01
stantonk left18:02
deBase joined18:02
stantonk joined18:03
sfjohansson kbs hmm..at least I odnt feel closer on how to solve this this…. =O18:03
azbarcea joined18:04
davisonio joined18:05
dunpeal ojacobson: d'oh. I amended a remote commit by mistake :/18:05
johnmilton left18:05
cxybeb left18:05
kaldoran joined18:06
Asenar left18:06
romerocesar joined18:06
mdw left18:06
SwiftMatt joined18:08
InfoTest left18:08
realz joined18:09
rwb left18:09
Doginal left18:09
romerocesar left18:10
mikecmpbll joined18:11
Gsham left18:12
daniel_rose joined18:13
daniel_rose left18:13
daniel_rose joined18:13
kbs sfjohansson: dunno if there's a cookbook tutorial that does exactly what you want. But should you feel that (essentially) you want to invent a commit history that picks selected states of the code in some suitable way, with an invented commit messages - a crude hint might be http://paste.debian.net/hidden/77c2ac19/ but it's probably needs understanding what git does at the low level18:14
(that said, I personally think the only way git makes sense to me is at the low level :)18:14
s/git makes sense to me/I make sense of git/18:14
nnyk_ left18:15
cuebix-wk left18:15
cuebix-wk joined18:15
stantonk left18:17
johnmilton joined18:17
Doginal joined18:18
Silenced_v2 left18:19
sfjohansson kbs I guess thats always the thing with using a GUI for anything =O now it feelsl ike my old solution with just deleting the repo and initializing a new one was pretty straightfroward but I can’t relly do it this time as I already have a few commits…that I need to keep =(18:20
mathewdgardner left18:21
quetz joined18:22
SwiftMatt left18:22
kbs *nod* fwiw, I sorta slowly came realize that dealing with git is actually considerably easier without the guis, and spending an hour or two figuring out the low-level bits (which is actually fairly simple.) Then, the guis and commands made much more sense to me, and I could make git work for me (than vice-versa :)18:22
mariuscc left18:22
jost__ joined18:23
SwiftMatt joined18:23
tristanp_ joined18:24
tristanp left18:24
sfjohansson kbs sounds like the better approach…and is more cross platofrm :)18:24
rwb joined18:24
_ikke_ kbs: could not agree more18:25
stantonk joined18:25
mathewdgardner joined18:26
ArchNoob joined18:26
jost_ left18:27
Rodya_ left18:27
dmj` joined18:28
azbarcea left18:28
Rodya_ joined18:28
jason237 joined18:28
Timvde joined18:28
tristanp_ left18:28
g105b left18:28
hk238 left18:29
Rodya_ left18:29
mikecmpbll left18:30
tristanp joined18:30
Silenced_v2 joined18:30
Silenced_v2 left18:30
Silenced_v2 joined18:30
xall joined18:31
StuartMI left18:31
deBase left18:32
mariuscc joined18:32
drewo left18:32
TheSpiderPig joined18:32
hck89 joined18:32
Rodya_ joined18:32
drewo joined18:32
yohnnyjoe joined18:33
pcre_ joined18:33
ZenWalker joined18:34
ZenWalker hello, how to search a commit ignoring the caps?18:34
lugzer joined18:35
i7c git log -i --grep='pattern'18:35
PabloR left18:36
d4rklit3 joined18:36
mikecmpbll joined18:36
gitinfo set mode: +v18:36
TheSpiderPig grep takex a regex18:36
afaik18:36
f3r70rr35f left18:36
i7c yup18:36
But you'll have a hard time doing --grep='[tT]his [iI]s [wW]hat [iI]m [lL]ooking [fF]or' :)18:37
Dunno if it understands some case insensitive directive like some regex do.18:37
pioiytr_ joined18:37
mathewdgardner left18:37
Silenced_v2 left18:37
TheSpiderPig cant you use a /i18:38
it *is* regex18:38
f3r70rr35f joined18:38
TheSpiderPig oh fuck, yeah use -i18:38
or --ignore-case18:38
wait that's for gitr grep18:39
i7c So --grep='/something/i' does not work if that’s what you meant.18:39
Rodya_ left18:39
lugzer left18:40
ArchNoob left18:40
pioiytr left18:40
bronson left18:41
guampa joined18:41
Literphor joined18:41
stonerfish left18:41
Masterphi left18:42
Masterphi joined18:43
acetakwas left18:43
sargas joined18:44
stonerfish joined18:44
yohnnyjoe left18:44
TheSpiderPig left18:44
mathewdgardner joined18:44
mutex joined18:44
GT4066 left18:45
Rodya_ joined18:46
circ-user-foXmx left18:48
SwiftMatt left18:48
shinnya left18:48
p4trix left18:49
howdoi left18:49
SwiftMatt joined18:50
usm4n left18:50
chachasmooth left18:50
Rodya_ left18:50
Silenced_v2 joined18:51
sfjohansson kbs Im ight have done it…at least it looks like it…but maybe everything is there but hidden =O18:51
Silenced_v2 left18:51
Silenced_v2 joined18:51
elosz left18:51
ekinmur joined18:52
l4v2 joined18:52
chachasmooth joined18:53
eizua left18:53
sfjohansson ojacobson I did try a graft and git filter-branch ..it looks fine in my git client…would this have actually thrown away history too or is it just “represented” in cleaner way18:53
ojacobson Without seeing what you actually did, I have no idea.18:54
EvilPenguin left18:54
Sasazuka__ joined18:54
ojacobson (That wasn't an invitation; I'm busy right now, but if you paste a !transcript I'm sure someone can add commentary. :)18:54
gitinfo Please paste (using https://gist.github.com/ or https://vomitb.in/ ) a transcript ( https://gist.github.com/2415442 ) of your terminal session so we can see exactly what you see18:54
tvon joined18:55
bronson joined18:55
tristanp left18:55
jungsubk joined18:55
govg left18:56
ekinmur left18:56
mischat joined18:57
Sasazuka left18:57
mwhooker left18:57
TooLmaN left18:57
pioiytr__ joined18:58
p4trix joined18:58
mwhooker joined18:58
dimi1947 left18:58
sargas left19:00
NeXTSUN joined19:00
ZenWalker -i works, thanks19:00
ZenWalker left19:00
drewo left19:01
sfjohansson ojacobson Cheers…here is the link http://hastebin.com/letewitifo.vbs :)19:01
drewo joined19:01
catag87 joined19:01
pioiytr_ left19:01
catag87 left19:01
circ-user-8eXFL joined19:01
catag87 joined19:02
tvon left19:02
TheodoreBe left19:03
EvilPenguin joined19:03
jason237 left19:03
tristanp joined19:03
l4v2 left19:05
spudowiar joined19:05
blackwind_123 joined19:05
dunpeal left19:05
pwnz0r left19:06
SteffanW left19:06
Waskeend left19:07
Waskeend joined19:08
Repox joined19:09
mwhooker left19:09
p4trix left19:11
timmu joined19:11
govg joined19:12
preyalone left19:14
IWishIKnew left19:15
paul424 joined19:15
dunpeal joined19:15
timmu left19:16
vF3hNGxc47h8 joined19:17
UncleCJ joined19:18
ynanm joined19:20
nnyk_ joined19:20
NeverDie joined19:20
astrofog joined19:20
Rodya_ joined19:23
dunpeal left19:25
chachasmooth left19:25
catag87 left19:25
jungsubk left19:27
chachasmooth joined19:27
EvilPenguin left19:27
troulouliou_div2 joined19:27
troulouliou_div2 left19:27
phaleth left19:28
muelli joined19:28
editshare-ericf joined19:28
BlaXpirit I want to see whether I can push to a remote without needing -f. is there something like --dry-run and will it do this?19:29
Rodya_ left19:29
troulouliou_div2 joined19:30
Silenced_v2 left19:30
stantonk left19:31
weox joined19:31
BlaXpirit nevermind, I don't really need to check, I can just do it19:31
Darcidride joined19:31
tristanp left19:32
hahuang61 joined19:32
invisbl joined19:32
timmu joined19:33
stantonk joined19:34
stantonk left19:34
jungsubk joined19:34
lugzer joined19:36
jimi_ joined19:36
Rodya_ joined19:36
hahuang61 left19:37
satifant joined19:37
l4v2 joined19:37
slayerjain joined19:38
stantonk joined19:38
tristanp_ joined19:38
hunter2 joined19:39
lugzer left19:40
mwhooker joined19:40
Rodya_ left19:41
gitinfo set mode: +v19:41
hunter2 hello all. i have much to learn. can someone tell me how you identify a file by its revision number?19:41
ojacobson files don't have revision numbers in git19:41
there's a hash for each distinct blob (file contents), but the same blob can appear in multiple paths or in multiple revisions, so asking "what's the path to this blob" is a bit complex19:42
elastix joined19:43
t0by left19:43
Lynxium joined19:44
Bennux joined19:44
hunter2 supposing i commit a.txt and it's hash is 4f9542d.. how do i show that revision?19:44
mikecmpbll left19:44
preaction git show 4f9542d19:45
hunter2 tried, a@4f... a@{4f} ... i'm missing something19:45
mikecmpbll joined19:45
hunter2 i just want a.txt though19:45
GodGinrai left19:45
djensen joined19:45
i7c git show 4f9542d:a.txt19:45
preaction git show 4f9542d -- a.txt19:45
hunter2 oh ffs, it goes after19:45
spudowiar bloob19:46
i7c preaction, that shows the diff.19:46
spudowiar blobby bob19:46
rahtgaz joined19:46
SpeakerToMeatDieInAFire19:46
vF3hNGxc47h8 left19:46
spudowiar i7c: well, that's what that blob is :)19:46
DieInAFireSpeakerToMeat19:46
EvilPenguin joined19:47
i7c Not what hunter2 asked, if I understood him right tho.19:47
shuaib joined19:47
GodGinrai joined19:47
spudowiar well, yeah19:47
but :)19:47
I'm just here to trollll19:48
don't mind me19:48
i7c spudowiar, besides that’s wrong.19:48
hunter2 another question, suppose i'm going round adding a copyright boiler plate, i commit that to a.txt, how do i take that commit's diff and apply that to b19:48
i7c The blob will contain the entire file not just the diff.19:48
shuaib left19:48
djensen left19:48
spudowiar i7c: but that'd be inefficient o_O19:48
i7c Not really.19:48
D[4]ni left19:49
spudowiar well, if you add 1 line to a 100MB file, it'd be two 100MB blobs?19:49
Hounddog left19:49
i7c At first, yes. At some point they'll be delta compressed and whatnot.19:49
ojacobson spudowiar: git's logical model is purely snapshot based, so, initially, yes - there will.19:50
spudowiar :O19:50
TIL19:50
ojacobson however, git optimizes that by delta-encoding similar objects when packing loose objects19:50
spudowiar thanks19:50
ojacobson The encoded deltas have nothing to do with commit diffs, exactly - it's more like "find me the most similar, and diff from that"19:50
i7c And it's not really "inefficient" that way. If it all just were diffs you’d have to apply diffs for hours if the history is long enough.19:51
mwhooker left19:51
sargas joined19:52
bronson left19:52
pcre_ left19:53
TheodoreBe joined19:53
GodGinrai left19:54
GodGinrai joined19:54
mwhooker joined19:54
pcre_ joined19:54
Atrumx left19:55
aguimaraes1986 left19:56
hunter2 so, i was thinking something like this: git merge-file b.txt 4f1af:a.txt 8a8a8a:a.txt19:56
lugzer joined19:57
Bennux left19:58
usm4n joined19:58
hunter2 ... but that doesn't work. i've much to learn so any pointers would be appreciated!19:59
muelli left19:59
thiago left20:00
Asiajey left20:00
lugzer left20:01
Masterphi left20:01
Silenced joined20:01
Masterphi joined20:01
Silenced left20:02
synthroid joined20:02
thiago joined20:02
texinwien left20:03
spudowiar left20:04
Asiajey joined20:04
Asiajey left20:04
Asiajey joined20:04
rpd hunter2: what error does that give?20:05
HoierM left20:05
bongjovi left20:06
rpd I guess merge-file doesn't take a commit-ish argument and doesn't resolve the file20:06
Cooler1 joined20:06
hunter2 Could not stat 4f954...:a20:06
which is fair enough, its not on disk as that name .. but was hoping git would work it out as a point in the repos20:07
rpd yeah, well... you could do something like git cat-file ... > a_file etc20:07
chachasmooth left20:07
rpd and then use merge file to merge the results of those cat-file operations20:07
alexruf_ joined20:08
pcre_ left20:08
tristanp joined20:08
pcre_ joined20:08
usm4n left20:09
rpd yeah, the user-manual gives that as an example for using merge-file to merge files from different trees20:10
ArchNoob joined20:10
tristanp_ left20:11
alexruf joined20:11
TheodoreBe left20:11
alexruf_ left20:11
elastix left20:11
elastix joined20:11
chachasmooth joined20:12
yqt joined20:12
fus joined20:12
usm4n joined20:12
rnsanchez left20:13
fus left20:13
tristanp left20:13
mathewdgardner left20:13
pcre_ left20:13
tristanp joined20:14
pcre joined20:14
DeJoker joined20:14
DeJoker Test ?20:14
usm4n left20:14
DeJoker Any knowledgable folks here ?20:15
selckin just jokers20:15
DeJoker Great :)20:15
preaction also space cowboys. but no gangsters of love20:16
GodGinrai and some battle programmers20:16
romerocesar joined20:17
lugzer joined20:17
mariuscc2 joined20:17
mariuscc left20:18
preaction what about Maurice?20:18
DeJoker Okay I have a Source.pgm in git — that another team works on — and I have some changes that I make to that Source.pgm to turn it into Ultimate.pgm which changes a few lines in a few files, deletes a few files, replaces a few files, and add some new files — can I have a repository of just those alterations that I can then Merge into the Source.pgm to make my Ultimate.pgm ?? Or must I regrettably have all the content in my development repository ???20:18
chrisshattuck left20:19
MaximusColourum joined20:19
xall left20:20
fedya___ joined20:20
Waskeend left20:21
fus joined20:21
jungsubk left20:21
romerocesar left20:21
fedya___ Hi, I made a huge mistake just now. I meant to commit to a new branch, but accidentally committed to master and pushed to remote. I reverted the commit with "git reset HEAD^ --hard" and "git push origin -f" –– now all my work is gone... I wasn't thinking... Is there anyway to restore the commit?20:21
Waskeend joined20:22
lugzer left20:22
preaction fedya___: check the git reflog20:23
or if you remember the sha of the commit, it's likely still there20:23
Cease joined20:23
rwb left20:25
blackwind_123 left20:27
dmj`` joined20:28
fmcgeough left20:28
wagle joined20:28
DeJoker Okay I have a Source.pgm in git — that another team works on — and I have some changes that I make to that Source.pgm to turn it into Ultimate.pgm which changes a few lines in a few files, deletes a few files, replaces a few files, and add some new files — can I have a repository of just those alterations that I can then Merge into the Source.pgm to make my Ultimate.pgm ?? Or must I regrettably have all the content in my development repository ??? Not20:28
looked into SubModules but this did not seem to be the correct tool but then again maybe I did not look deep enough as of yet20:28
Cease left20:29
noidea left20:29
blackwind_123 joined20:29
dmj` left20:31
DeJoker Hmmm okay just Jokers, Smokers and Tokers I guess :) as I was told20:31
usm4n joined20:31
danimal2 joined20:32
muelli joined20:32
texinwien joined20:33
fedya___ preaction: I looked at .git directory and it looks like it's still there:20:33
e4b5738 HEAD@{0}: reset: moving to HEAD^20:33
6ca57e2 HEAD@{1}: commit: [PLAT-2832] Daily cronjob at 10am to send final changes notice for orders shipping in 45 days20:33
how do I restore it? and put it in a new branch? I currently have master checked out20:33
mand0 joined20:33
preaction !reflog20:34
gitinfo The git reflog (`git log -g`) records the SHAs of your HEADs for 2+ weeks. `git checkout -b myrestore OLDSHA` and `git reset --hard OLDSHA` will relink to that state via a new and current branch respectively, see http://sethrobertson.github.com/GitFixUm/ for full details. WARNING: reset --hard will trash any uncommitted changes! Visualize with: gitk --all --date-order `git log -g --pretty=%H`20:34
stantonk left20:35
mathewdgardner joined20:36
fedya___ sorry, I'm a bit confused, worried about doing another hard reset. I'm following the part with checking out into new branch using the SHA I grabbed from reflog, what will the git reset --hard OLDSHA do?20:37
GodGinrai left20:37
stantonk_ joined20:37
stantonk_ left20:38
neurodrone_ joined20:38
lugzer joined20:38
stantonk_ joined20:38
preaction fedya___: those are two different things. one makes a new branch, the other changes the current branch20:40
see the link20:40
pcre left20:42
Orion3k left20:42
fedya___ there's only one file with M flag there, there should be 4...20:43
could I have lost that commit completely since I did a reset --hard?20:43
lugzer left20:43
Doginal left20:45
mwhooker left20:45
bronson joined20:45
preaction no20:45
dunpeal joined20:46
wagle left20:47
TheodoreBe joined20:47
TheodoreBe left20:47
DeJoker Okay I have a Source.pgm in git — that another team works on — and I have some changes that I make to that Source.pgm to turn it into Ultimate.pgm which changes a few lines in a few files, deletes a few files, replaces a few files, and add some new files — can I have a repository of just those alterations that I can then Merge into the Source.pgm to make my Ultimate.pgm ?? Or must I regrettably have all the content in my development repository ??? Not I20:47
looked into SubModules but this did not seem to be the correct tool but then again maybe I did not look deep enough as of yet — So nobody can help me with this ??20:47
TheodoreBe joined20:48
jeffreylevesque left20:48
TheodoreBe left20:49
nnyk joined20:49
mwhooker joined20:49
nnyk_ left20:49
sargas left20:49
ash_workz left20:51
Kulrak joined20:51
Kulrak left20:51
Kulrak joined20:51
DeJoker left20:52
madewokherd left20:54
DeJoker joined20:54
jimi_ left20:54
Sadeukko joined20:55
Klipp left20:55
DeJoker left20:55
DeJoker joined20:55
DeJoker left20:56
tristanp left20:56
drewo left20:57
drewo joined20:57
drewo left20:57
white_gecko joined20:57
drewo joined20:58
Doginal joined20:58
Doginal left20:58
LionsMane left20:59
pioiytr_ joined20:59
apotry left21:00
diogenese left21:00
mariuscc2 left21:01
Rodya_ joined21:01
FuzzySockets joined21:01
tristanp joined21:02
pioiytr__ left21:02
mwhooker left21:03
Silenced joined21:03
nilg joined21:04
sapiens_vector joined21:04
daniel_rose left21:04
daniel_rose joined21:05
Silenced left21:05
Silenced joined21:05
jagob joined21:07
Orion3k joined21:08
Sucks joined21:08
shirty left21:09
daniel_rose left21:10
wagle joined21:10
NeonSynth_ joined21:11
synthroid left21:11
raijin left21:14
NeonSynth left21:14
cyan__ left21:15
xall joined21:17
white_gecko left21:17
tgunr left21:17
gitinfo set mode: +v21:17
freimatz left21:17
sanketdg left21:17
tgunr joined21:18
ynanm left21:19
ajf- joined21:19
FunkyAss left21:19
bunniez joined21:21
hunter2 left21:21
Darcidride left21:22
bunniez hello friends, i need help unsetting an alias. somehow the alias in question("ci") got defined twice, shows up twice in the list "git config --get-regexp alias". when i run "git config --global --unset alias.ci", i get the message "warning: alias.ci has multiple values" and it does not do it. how do i force it to remove this alias?21:22
mathewdgardner left21:22
espindola left21:24
rpd bunniez: you can't manually remove it?21:25
diogenese joined21:25
mwhooker joined21:26
bunniez rpd: i thought that "git config --global --unset alias.ci" was the way to do that. is there another way?21:27
UncleCJ left21:27
rpd I mean, if it's giving you an error because it's defined twice, just edit the file and remove both references to make that command work again21:28
rahtgaz left21:28
bunniez rpd: thanks, sounds like that would work. where do i locate the file containing global aliases?21:28
rpd ~/.gitconfig probably21:28
nilg left21:29
bunniez rpd: thank you. i'm on a windows machine, do you figure ~ would probably be the C:/ drive?21:29
mathewdgardner joined21:29
rpd For windows I'm not sure. You can go look at what HOME is defined as in C:\Program Files\Git. It's probably something like C:\Users\Something\.gitconfig21:31
ahmed_elgabri joined21:31
UncleCJ joined21:31
ShekharReddy joined21:31
synthroid joined21:31
tristanp left21:32
bunniez rpd: you're right, it was in Users, thanks!!21:33
weox left21:33
Asiajey left21:34
bruce_lee left21:34
satifant left21:34
hahuang61 joined21:34
stantonk_ left21:34
Dreamer3 joined21:34
bruce_lee joined21:35
bruce_lee left21:35
bruce_lee joined21:35
bunniez left21:35
EvilPenguin left21:35
mwhooker left21:35
stantonk joined21:36
tristanp joined21:36
editshare-ericf left21:36
spudowiar joined21:37
MaximusColourum left21:37
mwhooker joined21:37
SimonNa joined21:38
hahuang61 left21:39
ahmed_elgabri left21:40
Silenced left21:40
EvilPenguin joined21:41
NeXTSUN left21:42
aidalgol joined21:42
aidalgolGuest296021:42
hashpuppy left21:42
usm4n_ joined21:43
ahmed_elgabri joined21:43
mand0 left21:45
white_gecko joined21:45
usm4n left21:46
danimal2 left21:46
Brain joined21:46
azbarcea joined21:46
jason237 joined21:46
GenZai left21:46
Muzer joined21:48
drewo left21:48
xlegoman left21:49
usm4n_ left21:49
Literphor left21:49
kaldoran left21:50
ExoUNX left21:51
f3r70rr35f left21:51
drewo joined21:52
stantonk left21:52
Guest2960aidalgol21:53
stantonk joined21:53
f3r70rr35f joined21:53
DieguezZ joined21:54
Gsham joined21:54
HoierM joined21:54
Brain left21:54
pneuma joined21:55
ahmed_elgabri left21:55
jagob left21:56
TestUser left21:57
UncleCJ left21:57
davisonio left21:57
romerocesar joined21:58
drewo left21:58
joki left22:00
xpk left22:00
f3r70rr35f left22:01
spudowiar left22:01
raijin joined22:02
romerocesar left22:03
stantonk left22:04
Masterphi left22:04
Literphor joined22:04
joki joined22:05
Masterphi joined22:05
stonerfish left22:06
Gsham left22:07
slayerjain left22:08
stonerfish joined22:09
k3rn31 left22:10
jimi_ joined22:10
tristanp left22:11
tristanp joined22:11
Sucks left22:11
Atrumx joined22:11
nettoweb joined22:13
fedya___ left22:14
Sucks joined22:15
bronson left22:15
romerocesar joined22:18
synthroid left22:19
Rodya_ left22:19
Sucks left22:20
a_n_d_y joined22:20
gitinfo set mode: +v22:21
Guest55 joined22:21
LiohAu left22:21
a_n_d_y i have a usage question. it feels like i'm being stupid22:21
will anyone help?22:21
devbug joined22:21
ojacobson Only one way to find out22:21
a_n_d_y :)22:21
Rodya_ joined22:22
a_n_d_y I'm working with a few guys on a server using git. a lot of the time, changes need to be made live on the server. is there any way to all work ont he server at the same time, using git branches, without conflicting or committing directly to master all the time?22:22
romerocesar left22:23
Darren_ left22:24
azbarcea left22:24
paul424 left22:25
manizzle a_n_d_y, make a branch called dev. Everyone works in their own branches, merging against dev. Then 1 person is in charge of taking dev and merging with master22:25
EvilPenguin left22:26
ojacobson "a lot of the time, changes need to be made live on the server" first things first: _no matter what source control tool you use_, this is going to cause bottlenecks.22:26
EvilPenguin joined22:26
ojacobson Make it possible to run at least a cut-down version of your service locally, or in docker, or in a VM, or something and you will fix a lot of this22:26
thiago left22:26
a_n_d_y thanks manizzle, makes sense. like git flow or something i guess22:27
mwhooker left22:27
a_n_d_y ojacobson, yeah it feels like we're working wrong22:27
astrofog left22:27
ojacobson Second, more specifically, no - git assumes a work tree belongs to a single workflow at a time.22:27
You could _in principle_ have multiple repos, but share a work tree, but it's not worth doing22:28
a_n_d_y i dunno if we can create cutdown servers locally. there's so many it would take a lot of effort. would individual directories on the server for each user work?22:28
Sucks joined22:28
Sucks left22:28
ojacobson you won't get what you want and you will get a bunch of headaches22:28
a_n_d_y andy-dev dir22:28
tristanp_ joined22:28
mwhooker joined22:28
tristanp left22:29
Gamecubic left22:30
FuzzySockets left22:30
bronson joined22:31
Brain joined22:31
mathewdgardner left22:31
sangy left22:32
fahadash left22:32
tristanp_ left22:33
tristanp joined22:35
madewokherd joined22:36
white_gecko left22:36
dreiss joined22:37
Brain left22:39
jstimm_ left22:40
p4trix joined22:40
Jellyg00se joined22:40
Masterphi left22:41
Masterphi joined22:41
FuzzySockets joined22:42
Fijit left22:42
magicbit joined22:42
cd-rum joined22:43
quetz left22:45
cd-rum_ joined22:45
bronson left22:45
kpease left22:46
bronson joined22:47
raijin left22:47
cd-rum left22:47
Vinnie_win joined22:48
xall left22:49
romerocesar joined22:49
Vinnie_win_a left22:49
a_n_d_y left22:51
yqt left22:51
stantonk joined22:51
mischat left22:51
dreiss left22:51
mischat joined22:51
xall joined22:53
romerocesar left22:53
apotry joined22:53
Ahmed90 joined22:57
Ahmed-90 joined22:57
Ahmed-90 left22:57
barteks2x joined22:57
unbalancedparen left22:58
Limes_ left22:58
Masterphi left22:59
Masterphi joined22:59
tristanp left23:00
Masterphi left23:00
drewo joined23:00
tristanp joined23:01
elastix left23:01
Masterphi joined23:01
cdown joined23:02
Literphor left23:02
Literphor joined23:03
nwkj86 joined23:04
dangerousdave left23:05
EvilPenguin left23:06
Masterphi left23:08
Masterphi joined23:08
FuzzySockets left23:08
FuzzySockets joined23:09
HanClinto left23:10
Masterphi left23:11
apotry left23:11
HanClinto joined23:11
stantonk left23:12
nnyk left23:12
stantonk joined23:12
mischat left23:13
m0viefreak joined23:14
Rodya_ left23:16
stantonk left23:17
emPi left23:18
akiva joined23:19
romerocesar joined23:19
cdown left23:21
Cassiopaya joined23:22
mathewdgardner joined23:22
mrBen2k2k2k joined23:23
cdown joined23:23
tristanp left23:23
nettoweb left23:23
romerocesar left23:23
nettoweb joined23:24
sfjohansson left23:25
sfjohansson_ joined23:25
nettoweb left23:25
IlNominePatre joined23:25
thiago joined23:25
tristanp joined23:25
mrBen2k2k2k left23:26
anuxivm1 joined23:28
Gamecubic joined23:29
anuxivm1 left23:30
rgrinberg left23:31
anuxivm joined23:32
stantonk joined23:32
mathewdgardner left23:32
EvilPenguin joined23:33
stantonk left23:33
cuebix-wk left23:33
stantonk joined23:35
sfjohansson_ left23:37
rgrinberg joined23:38
tristanp left23:39
stantonk left23:39
liquidjamm left23:39
mrBen2k2k2k joined23:40
muelli left23:40
synthroid joined23:41
EvilPenguin left23:41
ajf- left23:41
synthroid left23:42
tristanp joined23:42
catag87 joined23:42
ravi joined23:43
devbug left23:47
rahtgaz joined23:47
harish left23:47
romerocesar joined23:49
Rodya_ joined23:50
drewo left23:50
Sadeukko left23:50
FuzzySockets left23:50
mrBen2k2k2k left23:50
romerocesar left23:54
nwkj86 left23:56
FuzzySockets joined23:56
HanClinto left23:57
ravi left23:58
HanClinto joined23:59

Logs Search ←Prev date Next date→ Channels Documentation