IRCloggy #git 2015-09-21

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.

2015-09-21

daito left00:00
kre10s_ joined00:02
jmpp left00:02
kre10s_ normally I clone a repo from somewhere, then push changes back... This time I created a new one, added a remote and pushed some changes. How can I get the familiar and helpful HEAD is ahead of origin my n commits message in status?00:04
newman left00:04
newman joined00:04
Ahmed90 left00:05
phroa kre10s_: git fetch00:06
cerulean__ joined00:06
daito joined00:06
mizu_no_oto joined00:08
kre10s_ phroa, I just did this, but I do not get any hints in status. I should be 2 commits ahead. Is there anything I need to specify when I add the remote?00:09
qsuscs man git branch -u00:09
gitinfo the git-branch manpage is available at http://jk.gs/git-branch.html00:09
phroa ohh perhaps you didn't include -u. run git branch --set-upstream-to=00:09
yeah00:09
that00:09
jalnt joined00:10
jalnt left00:11
jalnt joined00:11
endiruna left00:11
kre10s_ thanks!00:12
daito left00:12
tbowman94 joined00:12
kre10s_ just out of curiosity is it possible to have more than one upstream00:13
rgb-one kre10s_: upstream is an alias00:13
I think you can have multiple remotes00:14
sctskw joined00:14
cerulean__ left00:15
rgb-one origin is usually the alias used to refer to the url for the main repository you push to.00:15
cerulean__ joined00:15
choki left00:16
jalnt left00:16
leeN left00:16
rgb-one "upstream" is usually an alias for a repo you fork from and would like to keep your repository in sync with00:18
you could name it anything00:18
cdown left00:18
otter768 joined00:20
spriz left00:20
skorgon left00:20
spriz joined00:22
r4zz91 joined00:22
michael_mbp left00:22
mellernoia joined00:23
tbowmanag joined00:23
r4zz91r4zz00:24
tbowmanag left00:24
otter768 left00:24
jalnt joined00:25
r4zz left00:25
r4zz joined00:25
harish left00:25
shuaib joined00:26
sctskw left00:28
sctskw joined00:28
michael_mbp joined00:28
bitkiller left00:30
spriz left00:31
tyoc213 joined00:32
tyoc213 working with gitflow, should I delete remote features when done??? it affect the history in some way? or it only delete the ref?00:32
sctskw left00:32
shuaib tyoc213, you mean remote feature branches?00:34
tyoc213 yep00:34
shuaib You can delete them once merged00:34
tyoc213 feature/mything00:34
shuaib Infact you should00:34
tyoc213 OK, thx00:34
shuaib I hate having too many branches in repo that aren't worked on anymore00:35
harish joined00:38
s8321414 left00:41
Milos sorry for the noob question but I don't want to get it wrong00:42
SonikBoom left00:42
Milos I've tagged a commit in dev as v1.0.1, now I want to push it to my test remote, how do I do this?00:42
git push test +v1.0.1~0:master ?00:43
diegoviola left00:43
phroa git push --tags00:43
harish left00:43
Milos doesn't that *just* push tags?00:43
I want to push the actual stuff that the tag points to00:43
nemix_ left00:43
phroa ah I didn't realize you were pushing both at once00:43
Milos that's ok00:44
nemix_ joined00:44
phroa er, I think it should push both00:44
Milos I was hoping there's a way to do it without a +, ~ or 0 in addition...00:44
phroa "All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line. "00:44
from man git push00:44
gitinfo the git-push manpage is available at http://jk.gs/git-push.html00:44
Milos ooh00:44
shuaib left00:44
Milos so can I specify a tag to push rather than --tags?00:45
I'll check the man page again00:45
phroa you can, yes.00:46
mizu_no_oto left00:46
nemix__ joined00:48
fairuz joined00:48
fairuz left00:48
Milos phroa, hmm I got "remote: fatal: No tags can describe <commit_id>", but it said [new tag] v1.0.1 -> v1.0.1 underneath00:48
when I re-run it says everything up-to-date00:48
phroa beats me00:49
Milos I'll have a play00:49
tbowman94 left00:50
r3g3x joined00:51
nemix_ left00:51
cerulean__ left00:52
toothrot left00:52
Guest48 joined00:52
Noldorin left00:54
Ingenia left00:54
KsChoice left00:55
ril joined00:58
SimonNa left00:59
yohnnyjoe left00:59
jmpp joined01:00
yohnnyjoe joined01:02
holodoc left01:02
jmpp left01:04
Guest53916 left01:07
_tgunr joined01:07
daito joined01:09
tyoc213 left01:09
diego1 joined01:10
diego1 left01:10
diego1 joined01:10
diego1diegoviola01:10
sparetire_ left01:10
DolpheenDream joined01:12
devoldmx joined01:12
daito left01:13
otter768 joined01:14
otter768 left01:14
devoldmx_ left01:15
otter768 joined01:15
colona left01:18
colona joined01:19
pks left01:19
dreiss left01:21
pks joined01:21
blobbagus joined01:21
mizu_no_oto joined01:23
oojacoboo left01:24
oojacoboo joined01:25
rchavik joined01:26
dreiss joined01:27
nnyk_ left01:29
newman left01:31
blobbagus left01:32
spriz joined01:32
dreiss left01:33
blobbagus joined01:33
ril left01:36
Vampire0_ joined01:38
thomasreggi left01:39
msonntag left01:39
leprechau joined01:41
msonntag joined01:41
Vampire0 left01:41
stee joined01:43
allcentury joined01:44
Phoenixz joined01:47
Guest48 left01:48
AridBullet joined01:48
pandeiro left01:49
blobbagus left01:52
CKyle left01:55
GoddeR joined01:55
mellernoia left01:56
Hink left01:58
harish joined02:00
bb010g left02:03
Atrumx left02:04
scarabx joined02:06
triuba left02:06
Milos so I made a few modifications, no commits, but I want those modifications on a new branch rather than master02:07
do I just make a new branch and it will carry the changes over?02:07
macabre left02:07
Rodya_ left02:07
mikiones left02:09
MarkyC left02:10
Eugene Milos - !float02:11
gitinfo Milos: If you have made a change in your working directory and have NOT YET COMMITTED, you may "float" that change over to another (`git checkout oldbranch`) or new (`git checkout -b newbranch`) branch and commit it there. If the files you changed differ between branches, the checkout will fail. In that case, `git stash` then checkout, and `git stash apply` and go through normal conflict resolution.02:11
Milos great!02:11
Rodya_ joined02:14
hasket joined02:16
ajpiano joined02:17
p1k joined02:17
penna__ joined02:17
stee left02:18
cyphase left02:21
penna_ left02:21
rchavik left02:21
cyphase joined02:21
vF3hNGxc47h8 left02:21
cyphaseGuest4176302:21
hasket left02:23
flavio_ joined02:26
mezod left02:26
hasket joined02:26
hasket left02:27
Hellacio joined02:29
jeffreylevesque joined02:30
jeffreylevesque_ joined02:31
Guest41763 left02:31
cyphase_ joined02:32
cyphase_ left02:32
cyphase_ joined02:32
stee joined02:33
alexwaters joined02:33
jeffreylevesque left02:34
toothrot joined02:35
Hellacio left02:40
livingstn left02:40
allcentury left02:43
strayPuppy left02:44
_tgunr left02:44
CKyle joined02:45
cerulean__ joined02:47
mizu_no_oto left02:48
xcesariox joined02:49
philophil joined02:50
cerulean__ left02:52
tanath left02:56
tgunr joined02:57
Nikhil_D left02:59
Padawan joined03:00
linuxmint2 joined03:00
Nikhil_D joined03:00
Guest48 joined03:01
linuxboytoo left03:01
mizu_no_oto joined03:02
linuxboytoo joined03:02
irwiss` joined03:02
tanath joined03:03
shinnya left03:04
linuxboytoo left03:06
linuxboytoo joined03:07
cyphase__ joined03:08
Guest48 left03:08
cyphase_ left03:08
cyphase__Guest3803403:08
Motoko joined03:09
daito joined03:10
nettoweb joined03:14
daito left03:14
_tgunr joined03:15
nettoweb left03:15
nsuke joined03:15
Padawan left03:16
tgunr left03:16
dreiss joined03:18
m0ltar left03:18
diegoviola left03:19
otter768 left03:20
dEPy joined03:21
oojacoboo left03:21
diego1 joined03:22
darkbasic left03:22
diego1 left03:22
diego1 joined03:22
diego1diegoviola03:23
darkbasic joined03:23
Guest38034 left03:25
cyphase joined03:26
cyphase left03:26
cyphase joined03:26
HeroYoojin left03:27
dsdeiz joined03:29
weyanus left03:30
jmpp joined03:31
dreiss left03:33
CKyle left03:33
mizu_no_oto left03:34
bishopj left03:36
bishopj joined03:36
Sleepy63 joined03:36
rchavik joined03:37
_tgunr left03:37
kadoban left03:38
jmpp left03:39
michael_mbp left03:39
lindenle left03:41
dreiss joined03:41
Atrumx joined03:41
Luming joined03:41
michael_mbp joined03:42
chupacab1a left03:42
r4zz left03:43
cagedwisdom joined03:50
hasket joined03:52
hasket left03:52
dreiss left03:52
m0viefreak left03:55
boner joined03:55
diego1 joined03:57
diego1 left03:57
diego1 joined03:57
diegoviola left03:57
diego1diegoviola03:57
dimi1947 joined03:57
GoddeR left03:58
GoddeR joined03:58
Meow-J joined03:59
kristjansson left04:00
Dougie187 joined04:06
Milos_ joined04:06
mikiones joined04:10
Milos left04:10
dimi1947 left04:11
Sly left04:11
Milos__ joined04:12
GoddeR left04:12
toothrot left04:12
mikiones left04:14
Milos_ left04:16
Phoenixz left04:17
Phoenixz joined04:18
xcesariox left04:20
Es0teric left04:22
sinknode joined04:24
daito joined04:25
jalnt left04:29
pungi-man joined04:29
Padawan joined04:30
pungi-man left04:30
daito left04:30
dreiss joined04:30
Padawan Why would a change/commit into a recently created branch would go into my master branch?04:30
phroa you created the branch with `git branch <name>` didn't you04:30
bendangelo left04:31
Padawan phroa: git checkout -b name04:31
phroa ah :C04:31
Padawan phroa: is this wrong?04:31
phroa well, I can't tell you the cause, but you can use `git cherry-pick` to copy it over, then just reset --hard master down by one04:31
no that's right.04:31
dEPy left04:31
Padawan phroa: the thing is, while i was at this new branch, i went bach in time to origin/master(and so my master branch). Now i gotta go ahead in time with my master branch to left things as they were04:32
What i mean is: i wanted to revert my new branch to origin, but then when i went to my master, this was also reverted to origin04:33
i guess i lost my work04:34
phroa you can find commits with the reflog, see man git reflog04:34
gitinfo the git-reflog manpage is available at http://jk.gs/git-reflog.html04:34
Phoenixz left04:35
jceb joined04:36
Padawan I mean, the things i lost were the ones it wasnt commited yet. My most recent commit is in the orign04:36
phroa mm.04:37
Padawan I just wish i knew why the hell things i did in a branch went into master as well04:37
So that did not happen again04:37
phroa I don't think I'm qualified to help you.04:37
Padawan no problem, thanks for the help anyway04:37
HeroYoojin joined04:39
Hink joined04:42
cagedwisdom left04:44
allcentury joined04:44
jceb left04:45
alexwaters left04:45
zacts left04:45
michael_mbp left04:45
jeffreylevesque_ left04:46
jonmorehouse joined04:47
alexwaters joined04:48
zacts joined04:48
michael_mbp joined04:48
IanWizard left04:48
allcentury left04:48
alexwaters left04:50
allcentury joined04:51
allcentury left04:56
cagedwisdom joined04:57
boner left04:57
kristjansson joined05:00
kristjansson left05:01
pantsman- joined05:01
yeu joined05:02
kristjansson joined05:02
yeu left05:02
Gvjia joined05:04
Gvjia left05:04
kristjansson left05:06
sdothum left05:06
kristjansson joined05:06
zoso joined05:07
MechtiIde joined05:08
teran joined05:08
kristjansson left05:08
kristjansson joined05:09
Rodya_ left05:09
Raging_Hog joined05:10
boombatower joined05:11
ayaz joined05:11
Wetmelon left05:12
jalnt joined05:12
teran left05:12
UmbraMalison left05:12
ckruczek joined05:16
smw joined05:17
allcentury joined05:17
eme left05:17
PCatinean joined05:18
otter768 joined05:21
endiruna joined05:21
allcentury left05:21
jmpp joined05:22
Manikandan joined05:22
otter768 left05:26
jmpp left05:27
kristjansson left05:28
jalnt left05:28
endiruna left05:29
sinkensabe joined05:32
sinkensabe left05:32
sinkensabe joined05:32
joako left05:33
alexwaters joined05:33
alexwaters left05:34
joo-_ left05:36
alexwaters joined05:36
dreiss left05:37
jceb joined05:37
alexwaters left05:37
pantsman- left05:38
Milos__ left05:38
kre10s__ joined05:38
Milos joined05:38
Milos left05:38
Milos joined05:38
xcesariox joined05:39
kre10s_ left05:41
vikas027 joined05:43
gambl0re left05:45
ThomasLocke joined05:47
philophil left05:48
NeverDie left05:51
DolpheenDream left05:51
philophil joined05:51
madduck joined05:53
freimatz joined05:56
pcypher joined05:57
Motoko left05:58
osse Padawan: if you didn't commit it when it never went into any branch05:58
Padawan: when you have uncomitted changes Git lets you switch branches as long as it doesn't have to touch any of the files you have changed05:59
V9O joined06:00
Padawan oh, so... if i have uncommited changes in false A and B, and create a branch, and then i start touching A and B, git add/commit in new branch. Then it overlaps it in main branch osse?06:00
ayaz left06:01
ahr3n left06:01
osse Padawan: define "overlap"06:01
jmpp joined06:01
howdoi left06:02
Padawan I did o that. and from what i have seen i experienced that the main branch got the changes i did in new branch. It looked like as if whatever i did in new branch went directly into main branch06:03
dsdeiz_ joined06:03
Padawan i tried to reset new branch at one time and main branch got reseted to06:03
joufflu left06:03
osse either you are mistaken or they never went into the new branch to begin with06:03
dsdeiz left06:04
Padawan Lemme see if i can reproduce it06:04
osse Padawan: !lol with help06:04
gitinfo Padawan: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all06:04
joako joined06:07
gopar left06:08
jackeroo_marc joined06:09
MechtiIde left06:09
osse !repro06:09
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://gist.github.com/2415442 ) of your terminal session.06:09
rscata joined06:09
curiousmansi left06:09
Padawan So osse, suppose i have file A and B in main branch and they are being modified, when i create a new branch git notifies me that. In this new branch i create another file called C and i git add it and then i try to git commit it. But git commit will commit the changed that came "pendent" from master.06:10
will it pass it through master after this new branch commit?06:10
mikiones joined06:10
dreiss joined06:10
Hink left06:11
Padawan yeah it went to master as well06:11
fracting1 joined06:11
eGGsha joined06:12
nisseni joined06:13
osse Lies!06:13
philophil left06:14
Padawan how can i prove?06:14
osse Padawan: !lol06:14
gitinfo Padawan: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all06:14
tpollard left06:14
osse !repro06:14
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://gist.github.com/2415442 ) of your terminal session.06:14
mikiones left06:15
go1111111 joined06:16
Amandil joined06:16
Gamecubic left06:18
Padawan https://gist.github.com/202bc19b518aebf6768206:18
Amandil left06:19
acolson joined06:19
Padawan It started at : 1a6fc73 Head06:19
osse is fix/one your "new branch" ?06:19
temmi_hoo joined06:19
roelmonnens joined06:20
Padawan yeah it showed me this when i crerated: https://i.imgur.com/27pVISL.png06:20
osse everyone looks normal06:20
Padawan then i did this: https://i.imgur.com/Kg3dT7P.png06:20
osse *everything06:20
160d443 is not part of master06:20
Amandil joined06:20
Padawan ok, but now, when i went back in master06:21
my vimrc06:21
my zshrc06:21
files i was modifying in master06:21
osse but you never committed them06:21
Padawan yeah exactly06:21
but in branch i had to commit06:22
lemme reddo06:22
it06:22
jrahmy left06:22
Padawan and show the commit messages06:22
osse Padawan: commit them now, then rerun the log command06:22
Padawan i commited it in new branch06:22
lemme log the new branch06:22
daito joined06:26
dsdeiz_ left06:27
philophil joined06:28
jrahmy joined06:28
dsdeiz joined06:29
pcypher left06:30
Juzzika joined06:30
daito left06:31
Padawan Okay, here is what i did: https://gist.github.com/anonymous/9061faed80d9e186da1206:31
Here is the commit message in newbranch after add a hello.txt file: https://gist.github.com/anonymous/1ab4e4ea58504504994106:32
when i go back to master and tail my vimrc, its not the same i was working before i create the new branch06:32
NordiQ_ joined06:33
skorgon joined06:33
skorgon left06:33
skorgon joined06:33
Padawan i am just lost06:34
NordiQ_ Hi. Let's say I went crazy tonight and restructured the directories of one of my repos locally as well as copied and deleted a bunch of files. What is the best way to reflect the new structure I have remotely?06:34
Do I have to delete all the files off the tracking tree and then readd everything by hand?06:35
diegoviola left06:37
grawity git add --all06:38
Amandil left06:38
diegoviola joined06:38
diegoviola left06:39
diegoviola joined06:39
CEnnis91 left06:39
NordiQ_ How do I get the deleted files out of the remote tree though?06:40
Tried doing git reset HEAD06:41
crap06:41
I just understood what I did06:41
declanqian joined06:43
osse Padawan: on line 25 you commited vimrc and zshrc too, not just hello.txt06:43
Padawan i know, but it was in new branch06:44
Alienpruts joined06:44
osse Padawan: so when you checkout master then those files will be changed to reflect how they appear in mater06:44
NordiQ_ left06:46
jost joined06:46
jonmorehouse left06:46
Padawan Like, the files were modified-state right? When i went into new-branch and commited them, they were commited there to last commited state, not to master-modified state. And worse than that, when i checkout to master the files were not modified anymore, they were at my last commit state.06:47
_ikke_ Padawan: Uncomitted changes don't belong to any branch06:47
skullcrasher joined06:47
osse Padawan: no, they were committed in their modified state06:47
and when you checkout master those changes won't show anymore06:48
howdoi joined06:49
Ingenia joined06:49
arup_r joined06:50
xintron joined06:52
Nizumzen joined06:53
Padawan osse, how do you explain this to me: https://i.imgur.com/7bNtXtW.png06:53
curiousmansi joined06:54
ashnur left06:54
scarabx left06:54
jaafar left06:54
Padawan so ok, i commited the modified files in new branch, but when i got back to master... the modified files were lost?06:54
grawity they're in that other branch...06:55
osse the modifications now belong to the new branch06:55
when you checkout master the nyou see the files as they are in master06:55
_ikke_ What do you expect when you switch branches?06:55
Padawan i see06:55
grawity yeah, that's kinda what branches are *for*06:55
so that each could hold different series of changes06:55
bmilesp joined06:56
xolubi joined06:56
grawity you want some change in both, you merge / cherry-pick / manually copy the commits06:56
xolubi left06:56
Padawan I was using them when i could think before, this is great then. Ok06:56
Well, thanks for the patience osse06:56
And sorry for my stupidity.06:57
ahr3n joined06:58
mkoskar joined06:58
TomyWork joined06:59
Goplat left06:59
devoldmx left07:01
aretecode left07:02
skynxnex joined07:02
ktosiek joined07:02
lb1a joined07:03
durham left07:03
addshore joined07:04
ahr3n left07:05
encod3 joined07:05
encod3 left07:05
WAAO3ME joined07:06
ilmgb joined07:07
bmilesp left07:08
encod3 joined07:09
stee left07:09
skorgon left07:10
wiky joined07:10
jrahmy left07:11
declanqian left07:12
Neozonz|Disc left07:12
dreiss left07:12
User458764 joined07:13
pungi-man joined07:16
arup_r_ joined07:17
User458764 left07:18
Efof joined07:18
Efof left07:18
nerd_ joined07:18
boombatower left07:20
nerd_ left07:20
nerd joined07:20
arup_r left07:21
otter768 joined07:22
pantsman- joined07:23
pungi-man left07:24
Balliad joined07:26
otter768 left07:27
thiago left07:29
snonez joined07:30
maxorator left07:31
maxorator joined07:31
snonez left07:33
ProT-0-TypE left07:34
diegoviola left07:34
ilmgb left07:34
ilmgb joined07:35
u26 joined07:38
tinajohnson joined07:38
allcentury joined07:39
Padawan left07:40
jrahmy joined07:40
nerd left07:41
u27 joined07:41
ilmgb left07:42
u26 left07:42
nerd joined07:42
Dragooon joined07:42
ilmgb joined07:43
DuckMaestro left07:44
allcentury left07:44
arjun_ joined07:44
linuxmint2 left07:45
jmpp left07:45
u27 left07:46
ilmgb left07:46
Hounddog joined07:47
ProT-0-TypE joined07:47
ilmgb joined07:48
nicechap joined07:48
tonyj joined07:48
mac_ified left07:49
BSaboia joined07:50
rasto left07:51
joo-_ joined07:55
rasto joined07:55
Dragooon left07:58
Dynetrekk1 joined07:59
Dynetrekk1 is it possible to get tmux in mintty/git-bash on windows?07:59
arjun_ left08:01
codesing joined08:01
bongjovi joined08:01
reim left08:03
_ikke_ No clue08:03
Dynetrekk1 _ikke_: too bad. if git-bash came with tmux I would be happy as can be08:04
arjun_ joined08:04
Dynetrekk1 I wouldn't miss linux at all, except when I'm working08:04
_ikke_ Just switch to linux :P08:05
j/k08:05
Linux has all the cool tools08:06
aswen joined08:06
allcentury joined08:07
endiruna joined08:08
Dynetrekk1 _ikke_: I'm working on linux when I can. sometimes I can't08:09
that is, sometimes I have to windows08:09
just because other people haven't seen the light08:09
_ikke_ I have to use use windows at work, but I have linux in a VM08:09
Dynetrekk1 I do that too08:09
reim joined08:10
allcentury left08:11
Dynetrekk1 compiling for windows has to be done on windows though08:12
_ikke_ .net?08:13
harish left08:13
Dynetrekk1 Fortran08:13
_ikke_ ok08:14
arup_r_ left08:15
stealthii I've two branches, `master` and `develop`, with the proviso that `master` cannot deviate from `develop` in commits, but is merely a less up-to-date version linearly. (Fast forwards to `develop` should always be possible.08:18
What would be the best practice to enforce this with commit hooks?08:18
_ikke_ Just curious, what if you need to do hotfixes?08:18
reim left08:19
_ikke_ commit hooks are optional, ie, they can be easily skipped, and users need to explicitly add it to their hooks08:19
u26 joined08:19
stealthii That issue came up today. Hotfixes were pushed to `master`, and later a pull request was merged into `develop`. `master` can no longer be fast-forwarded to `develop` as a result of this08:20
Dynetrekk1 you could put hooks if you've got a "blessed repo", e.g. stash, bitbucket, github, ...08:20
_ikke_ And why is that a problem?08:20
stealthii: (just curious)08:20
Just trying to understand your workflow08:21
stealthii To make absolutely sure that the site container running on our test domain (deployed from develop), is exactly what we will deploy to the live site (from master)08:22
arup_r joined08:22
_ikke_ But apparently you still want to do hotfixes?08:22
stealthii There has been issues in the past where poor developer merge commits have had the branches deviate whilst matching on commit content08:22
You raise a good point. I'd like to update those rules to allow for hotfixes, so master doesn't necessarily have to be fast-forwardable08:24
my requirement then would be that master doesn't contain any commits that aren't in develop as well08:24
_ikke_ stealthii: Do you use some kind of release based workflow? ie, you have a stage where you prepare something to release?08:25
andyr joined08:25
King_Hual joined08:26
King_Hual left08:26
King_Hual joined08:26
u26 left08:26
_ikke_ stealthii: perhaps you might want to look into !gitflow, which describes a workflow a bit more extensive as you currently have, but the formalization might be benneficial08:28
gitinfo stealthii: The description of the gitflow branch workflow model is at http://nvie.com/posts/a-successful-git-branching-model/ while a tool to help implement this workflow is at https://github.com/petervanderdoes/gitflow See http://sethrobertson.github.com/GitBestPractices/#workflow for other workflow suggestions/references08:28
Darcidride joined08:28
SimonNa joined08:30
stealthii Gitflow could work - this project isn't complex (static site, repo containing code and content) but I wanted to keep things a little simpler08:30
_ikke_ ok08:30
Note that we use gitflow here for small projects too08:30
jrahmy left08:31
_ikke_ But it might be a bit overkill08:31
stealthii I'll have a think, I'd agree on Gitflow being ideal - enforcing with commit hooks may not be the best idea, which was what I was investigating08:31
reim joined08:31
_ikke_ stealthii: Well, commit hooks is wrong place for enforcing things, they can at most be used for warning08:32
stealthii: The thing you want to protect is the 'blessed' repository08:32
What also can help in some cases is to devide roles08:32
vikas027 left08:33
nnyk_ joined08:33
_ikke_ ie, 1 or 2 people responsible for integrating into master08:34
Dragooon joined08:35
_ikke_ stealthii: This is a social problem in the first place, not a technical problem08:37
jrahmy joined08:37
dimi1947 joined08:37
osse a problem perpetuated by the welfare state08:37
elsevero joined08:37
Amandil joined08:38
SimonNa left08:38
liamkeily joined08:38
_ikke_ hehehe08:38
noisebleed joined08:40
doener joined08:40
Ju287ju2917 joined08:43
noisebleed left08:43
tvw joined08:44
noisebleed joined08:45
liamkeily left08:46
jmpp joined08:46
arup_r left08:47
cebor joined08:47
p4trix joined08:48
wiky left08:49
jmpp left08:51
a3Dman left08:53
howdoi left08:53
Meow-J left08:53
aretecode joined08:54
elementalest left08:55
nsuke left08:55
elementalest joined08:56
elementalest left08:56
elementalest joined08:56
Juzzika left08:56
Dragooon left08:56
srcerer joined08:57
a3Dman joined08:57
vikas027 joined08:57
howdoi joined08:57
osse _ikke_: why it am the funny?08:57
jackero__ joined08:58
King_Hual` joined08:58
King_Hual` left08:58
[diecast] joined08:59
mariorz joined08:59
kapowaz joined08:59
nnyk_ left08:59
codesing can anyone tell me what the benefits are of having a develop branch in gitflow over developing on master and tagging the releases?08:59
ELLIOTTCABLE joined09:00
jackeroo_marc left09:00
yrashk joined09:00
osse codesing: someone probably can, but that would make them LIARS. It makes no sense09:00
fracting1 left09:00
codesing i agree with you09:01
but i'm trying to find holes in the reasoning09:01
ahr3n joined09:01
osse !flow09:01
gitinfo [!gitflow] The description of the gitflow branch workflow model is at http://nvie.com/posts/a-successful-git-branching-model/ while a tool to help implement this workflow is at https://github.com/petervanderdoes/gitflow See http://sethrobertson.github.com/GitBestPractices/#workflow for other workflow suggestions/references09:01
SimonNa joined09:01
tobiasvl well I use master as bleeding edge, so it should always be stable (enough) even between releases. kind of a nightly09:01
Outsider__ joined09:02
osse hmm09:02
codesing: maybe it's because the flow thing expects you to merge hotfixes and features and such into multiple branches09:02
codesing i guess doing what tobiasvl does means that you never have to know what version is released..09:02
osse both master (=> a new release) and develop09:02
neersighted joined09:03
endiruna left09:03
codesing well getting rid of develop would just mean you had less merging to do no?09:03
noisebleed left09:03
sparetire_ joined09:03
endiruna joined09:03
tobiasvl sure09:04
"developing on master" is ambiguous though09:04
you'll still use topic branches?09:04
if so, knock yourself out09:04
codesing yeah you still have feature branches09:04
they just get merged into master09:04
arup_r joined09:04
noisebleed joined09:05
evanc joined09:05
m0viefreak joined09:05
tobiasvl sounds cool by me09:05
codesing too cool09:05
ahr3n left09:05
_ikke_ osse: You're funny because you made a joke?09:05
osse _ikke_: It was very serious!!!!1109:06
_ikke_ osse: In the context it was still funny09:06
trig-ger joined09:06
quackgyver joined09:06
MaceBewley left09:06
pcarrier joined09:06
tirengarfio__ left09:07
akitada joined09:08
yena joined09:08
jiz joined09:08
jonha joined09:09
Thorax2015 joined09:10
Ju287ju2917 left09:10
dsteplight___ joined09:11
noahsussman joined09:11
ethanol joined09:11
lacrosse joined09:11
ethanolalcohol09:11
Zariel joined09:12
bongjovi left09:12
penna__ left09:13
noisebleed left09:13
xcesariox left09:14
noisebleed joined09:15
reim left09:15
endiruna left09:16
endiruna joined09:16
joo-_ left09:18
preyalone joined09:19
ValicekB joined09:19
MLM joined09:20
jagob joined09:20
liamonade joined09:21
clone1018 joined09:21
tirengarfio__ joined09:21
faheem__ joined09:21
freestyl3r joined09:22
michele joined09:23
otter768 joined09:23
da5id joined09:24
michele hi! I have a 'develop' with 20+ commits. I want to create a new branch based on HEAD^1 commit on develop. I am thinking on a way to do it. First that comes to mind is: git checkout HEAD^1 && git checkout -b "new_branch" . what do you think about it?09:24
gitinfo set mode: +v09:24
dsdeiz left09:24
osse michele: that's fine but you can also do git checkout -b new_branch HEAD^1 directly09:24
jast michele: or just git checkout -b new_branch HEAD~09:24
michele yay :) thanks09:25
jast all of these options will do the same thing09:25
dsdeiz joined09:26
mikiones joined09:27
otter768 left09:27
ignas joined09:31
SimonNa left09:31
tanuck joined09:35
alanwill joined09:35
dimi1947 left09:36
nettoweb joined09:36
darkbasic left09:38
darkbasic joined09:38
freestyl3r left09:39
iamdevnul joined09:40
aswen left09:40
Meow-J joined09:40
wiky joined09:41
rex_lee_ joined09:42
aard joined09:42
sublimate joined09:42
Zariel left09:43
cebor left09:44
codeitagile joined09:45
lindenle joined09:45
Zariel joined09:45
scarcry joined09:45
cebor joined09:46
ryoshu left09:46
Amandil left09:46
arup_r_ joined09:49
boxrick1 joined09:49
lindenle left09:50
maxorator left09:50
michele left09:51
noisebleed left09:52
arup_r left09:52
maxorator joined09:53
codesing left09:55
codesing joined09:56
noisebleed joined09:57
joo-_ joined09:57
stamina joined09:58
daito joined09:58
zoso left09:58
zoso joined09:59
Neozonz|Disc joined10:00
newbie123 joined10:00
allcentury joined10:01
devoldmx joined10:02
daito left10:03
Zariel left10:04
Amandil joined10:05
Neozonz|Disc left10:05
devoldmx left10:06
allcentury left10:06
Amandil left10:09
newbie123 left10:10
ms7 joined10:10
Zariel joined10:12
Salehi joined10:13
noisebleed left10:13
zadock joined10:14
noisebleed joined10:15
Neozonz|Disc joined10:16
bernardio joined10:18
s8321414 joined10:18
zadock left10:18
bernardio left10:19
joo-_ left10:20
Neozonz|Disc left10:21
Zariel left10:21
joo-_ joined10:22
Thr3d_ left10:22
noisebleed left10:23
SimonNa joined10:24
Zariel joined10:24
Zariel left10:24
Zariel joined10:24
Zariel left10:24
noisebleed joined10:25
Zariel joined10:25
jeffreylevesque joined10:27
Zariel left10:29
freestyl3r joined10:30
Zariel joined10:31
Zariel left10:31
Zariel joined10:31
Kallis joined10:31
Kallis left10:32
Neozonz|Disc joined10:32
noisebleed left10:34
reim joined10:35
jmpp joined10:36
noisebleed joined10:36
allcentury joined10:36
Neozonz|Disc left10:36
Kallis joined10:37
jmpp left10:41
noisebleed left10:43
sdothum joined10:44
BSaboia left10:44
agis- joined10:44
noisebleed joined10:45
agis- if the sole reference of a commit in a repo is in another (refenreced - not to be GCed) commit's message (by it's SHA1), is it still going to be collected by git-gc?10:46
tobiasvl I believe so10:47
not aware of any magic in commit message references10:47
agis- I would assume this answer is "no", but just want to verify this. In other words: does git looks at SHA1s inside commit messages to see if it should GC a commit?10:47
tobiasvl highly doubt it10:48
Neozonz|Disc joined10:48
Neozonz|Disc left10:48
Neozonz|Disc joined10:48
howlymowly joined10:49
vikas027 left10:50
_ikke_ agis-: git uses so called roots to start to find reachability10:50
jrahmy left10:50
_ikke_ refs, reflog10:50
If a commit is reachable via one of these roots, then it's not going to be collected10:51
reim left10:51
agis- _ikke_: yep I know about this, so you are too implying that it does *not* reads at commit messages?10:51
_ikke_ agis-: It has to of course10:51
because only one commit per ref would be reachable10:52
otherwise10:52
AnnaSweden joined10:52
Neozonz|Disc left10:53
noisebleed left10:53
Zariel left10:53
agis- _ikke_: not sure I understand here. So if I write a commit message like "this is a follow-up commit to <sha1-of-commit-unreferenced-commit>"10:54
darkbasic_ joined10:54
agis- git will understand and keep that commit?10:54
AnnaSweden left10:54
Zariel joined10:54
osse no10:54
darkbasic left10:54
dsdeiz left10:54
t4nk703 joined10:54
Zariel left10:55
t4nk703 left10:55
noisebleed joined10:55
AnnaSweden joined10:55
mizu_no_oto joined10:56
linuxmint2 joined10:57
Mega joined10:58
CheckDavid joined10:58
mizu_no_oto left10:59
p1k left10:59
AnnaSweden left11:00
_ikke_ agis-: Ah that way, no11:01
agis-: Only parents will be followed11:01
agis- ok cool11:01
cdown joined11:02
noisebleed left11:03
anna86swe joined11:04
anna86swe left11:04
Neozonz|Disc joined11:04
jalnt joined11:04
anna87sweden joined11:04
noisebleed joined11:05
anna87sweden left11:05
anna87swe_ joined11:06
anna87swe_ left11:06
BullHorn joined11:06
BullHorn im trying to do 'git config --global credential.helper wincred' to save my github login information but it tells me "git: 'credential-wincred' is not a git command."11:07
rgb-one left11:07
BullHorn what am i doing wrong11:07
anna87swe_ joined11:07
anna87swe joined11:07
anna87swe Hello11:07
gitinfo anna87swe: 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.11:07
Neozonz|Disc left11:08
anna87swe I've been trying to figure out how to get updates from a remote repo but only fetch from a certain directory. Any ideas?11:09
_ikke_ What do you mean, fetch from a certain directory?11:10
Thr3d_ joined11:10
cavallari joined11:11
anna87swe_ Im not very good with the terminology.11:12
Let see if I can try describe what I want to do instead.11:12
kre10s__ probably means fetch only the files bellow repo/path/foo ...11:13
anna87swe_ yes something like that.11:13
noisebleed left11:13
anna87swe_ I'm not sure if that is best practice, I'm new to git.11:13
I want to try out the new bootstrap, but only use the files from a certain folder. https://github.com/twbs/bootstrap/tree/v4-dev/scss11:15
noisebleed joined11:15
anna87swe_ First i initialized a new git repo, then i did this: git remote add --track v4-dev --no-tags baz [email@hidden.address]11:16
I also tried git clone [email@hidden.address] --branch v4-dev --single-branch scss/scss which gets the files I need.11:17
Altreus left11:20
Neozonz|Disc joined11:20
jeffreylevesque left11:20
holodoc joined11:21
anna87swe_ When someone updates the remote directory I want to be able to sync it with my local repo.11:21
ilmgb left11:21
Guest30 joined11:21
ilmgb joined11:22
ValicekB left11:22
Guest30 left11:22
jalnt left11:22
Guest48 joined11:23
noisebleed left11:23
tgunr joined11:24
otter768 joined11:24
Kallis left11:24
Neozonz|Disc left11:24
noisebleed joined11:25
kre10s__ left11:25
ilmgb left11:26
ManikM joined11:26
otter768 left11:28
arup_r_ left11:29
fracting1 joined11:29
V9O left11:31
DolpheenDream joined11:31
rnsanchez joined11:32
noisebleed left11:33
arup_r joined11:34
paulweb515 left11:34
Neozonz|Disc joined11:36
fracting1 left11:37
bishopj left11:37
aswen joined11:37
bishopj joined11:37
mezod joined11:38
Zifre_ joined11:39
qsuscs anna87swe_: what you describe is—in the way you describe it—impossible11:40
Zifre left11:40
Neozonz|Disc left11:40
ilmgb joined11:41
osse qsuscs: would you go so far as to say it's "impossibru!!!" ?11:42
qsuscs osse: yes11:44
intellix joined11:44
sshine joined11:45
negaduck joined11:46
jeffreylevesque joined11:46
sshine I have a file that I'm trying to .gitignore, but it keeps showing in 'git status'11:46
qsuscs sshine: !ignore_tracked11:46
gitinfo sshine: Git only applies ignore patterns to untracked files. You can't use ignore patterns to ignore changes to files that are already tracked by git. To remove files only from git, but keeping them on disk, use git rm --cached <file>. Still, see https://gist.github.com/1423106 for ways people have worked around the problem.11:46
arup_r_ joined11:47
sshine qsuscs, aha! clearly. thank you.11:47
cagedwisdom left11:47
devoldmx joined11:48
Kallis joined11:50
arup_r left11:50
Kallis left11:50
BullHorn left11:51
Kallis joined11:51
Mega Hi guys! May I move a directory from my-repo to new my-repo.child?11:51
Neozonz|Disc joined11:52
devoldmx left11:52
osse Mega: what do you mean?11:52
darnir Mega: Do you want to split a repository into two?11:53
qsuscs anna87swe_: do NOT pm people without asking their consent first.11:54
tarkus left11:55
jalnt joined11:55
Neozonz|Disc left11:56
bonswouar joined11:56
ilmgb left11:56
Mega osse: darnir: I have a repository with a site, and there's a dir called helpers, I've got that dir in separate repository, and now I have no clue what should I do to add the new repo as a directory in old repo?11:56
reim joined11:57
veganista joined11:57
daito joined11:59
fstd left11:59
endiruna left11:59
CKyle joined11:59
fstd joined11:59
dionysus69 joined12:00
skullcrasher_ joined12:00
wiky left12:00
AyushKesu joined12:00
_tgunr joined12:01
skullcrasher left12:01
dionysus69 left12:01
dsdeiz joined12:01
daito left12:03
tgunr left12:03
dionysus69 joined12:03
ValicekB joined12:04
Zariel_ joined12:06
Zariel_ left12:06
Zariel_ joined12:07
Neozonz|Disc joined12:07
_ikke_ !subproject12:08
gitinfo [!subprojects] So, you want to add git repositories inside of other git repositories? Well, you have four main options. First is to just do it, add the repo to the outer project's .gitignore, and treat them entirely separately. Best if they are entirely separate. Otherwise your best options are "!submodule", "!gitslave", and "!subtree". Try those commands in this channel, or in a PM to avoid flooding.12:08
drbean left12:08
Walex joined12:09
drbean joined12:10
darkbasic joined12:11
darkbasic_ left12:12
SimonNa left12:12
Neozonz|Disc left12:12
retroj joined12:12
gitinfo set mode: +v12:12
Darcidride left12:13
retroj what is the difference between 'git annex get' and 'git annex sync --content'?12:13
lb1a retroj, that's not a git core functionality. see the man page at https://git-annex.branchable.com/git-annex/12:14
retroj ok, thanks12:14
DolpheenDream left12:16
ilmgb joined12:16
Smurfas joined12:17
sarri left12:17
sgambino joined12:18
sarri joined12:19
Manikandan left12:20
dimi1947 joined12:20
p1k joined12:20
Zariel_ left12:21
krawchyk left12:21
dgutierrez1287 joined12:22
victortyau joined12:22
bronson left12:23
Neozonz|Disc joined12:23
asfdfdfd joined12:24
dwmw2_gone left12:24
bmilesp joined12:24
deepy I have accidentally done something terrible, my git repository has lost the git parts12:24
Can I recreate it and get it up to sync without ruining my working copy?12:25
krawchyk joined12:25
qsuscs deepy: option a: restore your backup12:26
_ikke_ Do you have that repository somewhere else?12:26
deepy I have the repo in gitlab12:26
_ikke_ clone it somewhere, and the copy your working tree over it12:26
deepy but the correct state of it is on the harddrive and severely out of sync12:26
qsuscs deepy: option b: create a backup, git init, git remote add, git fetch, git reset --soft $commit12:26
or --mixed? reset is a beast.12:27
rgb-one joined12:27
HeroYoojin left12:27
Neozonz|Disc left12:28
dwmw2_gone joined12:28
CEnnis91 joined12:29
Raging_Hog left12:30
Hanumaan joined12:30
noisebleed joined12:30
Raging_Hog joined12:31
cbonobo joined12:31
Salehi left12:31
Darcidride joined12:33
harish joined12:34
curiousmansi left12:34
tinajohnson left12:35
Thorax2015 left12:36
dimi1947 left12:37
negaduck left12:38
halas joined12:38
macabre joined12:38
flavio_ left12:39
Neozonz|Disc joined12:39
nettoweb left12:39
mizu_no_oto joined12:40
bongjovi joined12:40
Raging_Hog left12:43
paulweb515 joined12:43
eme joined12:43
Neozonz|Disc left12:43
dsilva joined12:44
mission712[AFK]mission71212:45
allcentury left12:45
krawchyk left12:45
sybariten how does git handle folders, if i add "all" ... and they dont contain any whitelisted files?12:46
i.e. do they become empty folders in a repo12:46
osse then the folder won't be added12:46
no12:46
sybariten alrite12:46
diget left12:46
Thorax2015 joined12:48
wrouesnel3 joined12:48
noisebleed left12:48
liamonade left12:48
negaduck joined12:49
paulweb515 left12:49
MarkyC joined12:50
sanketdg joined12:50
noisebleed joined12:50
cvanball joined12:50
yohnnyjoe left12:50
cbonobo left12:51
LBV_User joined12:51
dougsland joined12:52
j416 poll: name of release preparation branch for version 0.1 of project: release-0.1 or release-v0.1 ?12:53
mellernoia joined12:53
retroj left12:53
Impaloo j416: master/develop?12:53
_ikke_ j416: I don't care :P12:54
osse MASTER12:54
MASTER12:54
j416 ... this was very helpful guys.12:54
Impaloo WE MUST GO FASTER12:54
j416 thanks..12:54
:P12:54
I know I should have never asked12:54
Impaloo j416: a new branch for a release doesn't make sense12:54
osse MASTER OF PUPPETS, I'M PULLING YOUR STRINGS12:54
j416 Impaloo: why?12:54
Impaloo unless you're maintaining multiple major versions at the same time12:55
but then you'd have 1.x, 2.x, 3.x branches12:55
Neozonz|Disc joined12:55
Impaloo since it's a 0.x release you should just keep everything in master/develop branch and tag releases as you go12:55
_ikke_ Impaloo: Why not?12:55
j416 point is that we do review _everything_, even release preparation stuff, so it makes sense in our workflow that master only has merges and all work is done in branches12:56
_ikke_ Impaloo: Do you stop all integration before release?12:56
agis- left12:56
allcentury joined12:56
j416 branch reviewed -> gets merged to master12:56
wrouesnel3 left12:56
Impaloo temporary branches are fine if you have some sort of freeze time for releases12:57
if you tag release as `v0.1` then I'd go for `release-v0.1`, `0.1` would be `release-0.1`12:57
cdown left12:57
_ikke_ Impaloo: If you are testing a release, you don't want new features to be merged into there12:58
but you want bugfixes12:58
Depending on the size of the project, you want integration to go on, while still working on the release12:58
noisebleed left12:58
liamonade joined12:59
cdown joined12:59
Neozonz|Disc left12:59
noisebleed joined13:00
CKyle left13:00
bongjovi left13:00
settermjd joined13:01
arjun_ left13:01
Hanumaan getting a validation error in git server when I do git gc what could be the problem? http://paste.ubuntu.com/12514126/?13:01
paulweb515 joined13:02
tristanseifert left13:03
jceb left13:03
tanuck_ joined13:03
bongjovi joined13:04
holodoc left13:04
reim left13:05
pratikmallya joined13:06
Noldorin joined13:06
tanuck left13:07
s00pcan joined13:08
fracting joined13:08
pratikma_ joined13:08
livingstn joined13:09
nerd left13:09
livingstn left13:09
andyrs joined13:10
Neozonz|Disc joined13:11
settermjd left13:11
pratikmallya left13:12
aswen left13:12
Chill_Surf joined13:13
jceb joined13:14
cvanball left13:15
settermjd joined13:15
rchavik left13:15
Neozonz|Disc left13:15
krawchyk joined13:16
cebor left13:16
black_silence joined13:17
bernardio joined13:17
tanuck_ left13:17
leeN joined13:18
cebor joined13:18
ManikM left13:18
Wetmelon joined13:18
charlesr joined13:18
charlesr left13:19
ManikM joined13:19
bernardio left13:21
newbie123 joined13:22
chitopunk joined13:22
bernardio joined13:23
settermjd left13:23
SimonNa joined13:23
bronson joined13:24
wxg left13:24
s00pcan_ joined13:25
otter768 joined13:25
jmpp joined13:25
reim joined13:26
charlesr joined13:26
charlesr left13:26
crose left13:27
Neozonz|Disc joined13:27
bernardio left13:27
crose joined13:27
Zariel joined13:27
jeffreylevesque when i try to `ssh -vT [email@hidden.address] i get "key_parse_private2: missing begin marker" - https://travis-ci.org/jeff1evesque/machine-learning/builds/81387012#L127, what does that mean, and how can i fix this?13:27
p1k left13:28
_ikke_ This is more of an ssh question than git..13:28
bronson left13:28
Impaloo left13:28
nettoweb joined13:29
Zariel left13:29
Impaloo joined13:29
linuxboytoo left13:29
otter768 left13:29
s00pcan_ left13:29
linuxboytoo joined13:30
jmpp left13:30
tinajohnson joined13:30
NeverDie joined13:31
cdown left13:31
Neozonz|Disc left13:31
Wetmelon left13:32
mbrzuzy joined13:32
jceb left13:32
Darcidride_ joined13:34
linuxboytoo left13:34
diget joined13:34
krawchyk left13:35
noisebleed left13:35
newbie123 left13:35
Dougie187 left13:35
platzhirsch joined13:35
platzhirsch I did a git merge which I didn't want to execute, how can I abort it now where the text editor is open?13:36
Even wit quiting the editor it will savei t13:36
reim left13:36
osse platzhirsch: empty the editor completely13:36
canton7 platzhirsch, did the merge conflict, or did it complete successfully?13:36
osse then quit13:36
_ikke_ :qc13:36
Gamecubic joined13:36
_ikke_ :cq *13:36
That will quit with an eror13:37
:cq<enter>13:37
platzhirsch ah nice, now I only need to get rid of what I merged in13:37
cdown joined13:37
osse after that you can git merge --abort methinks13:37
Darcidride left13:37
dickdaley joined13:37
anna87swe_ left13:37
canton7 only if you're in the middle of the merge - i.e. it conflicted13:37
qsuscs alternatively, just save and close and delete the merge afterwards13:37
platzhirsch well done, thanks for the help13:38
jaafar joined13:39
halas left13:39
oojacoboo joined13:40
luksaur joined13:40
CKyle joined13:41
noisebleed joined13:41
anna87swe left13:41
Neozonz|Disc joined13:43
malavv joined13:44
krawchyk joined13:44
jceb joined13:44
krawchyk left13:45
AaronMT joined13:45
krawchyk joined13:45
rchavik joined13:45
darkbasic left13:46
maply joined13:46
maply left13:46
noisebleed_ joined13:47
noisebleed left13:47
Neozonz|Disc left13:47
reim joined13:48
leeN left13:48
darkbasic joined13:48
devoldmx joined13:48
SimonNa left13:49
AridBullet left13:49
kristofferR joined13:49
kristofferR left13:50
Ikc joined13:50
Ikc left13:50
Guest48 left13:50
Ahmed90 joined13:50
Dro__ joined13:51
amwa joined13:51
Ahmed90 left13:51
amwa left13:51
voodo joined13:51
Ahmed90 joined13:51
BigWillie joined13:52
marlinc_ joined13:52
devoldmx left13:53
Vou joined13:53
Vou left13:53
laszlof joined13:55
ckruczek left13:55
Luming left13:55
krawchyk left13:55
marlinc_marlinc13:55
krawchyk joined13:56
madduck left13:56
madduck joined13:56
ms7 left13:56
Luming joined13:56
moyam01 left13:56
laszlof is there a way to do a sparse-checkout with submodules and have it reproducable for anyone who clones said repository? Specifically, i want to clone certain files/directories from various projects into my own private repo13:56
qsuscs laszlof: no13:57
Uvpi joined13:57
Uvpi left13:57
platzhirsch left13:58
laszlof ok. so this isnt doable even with subtrees?13:58
lindenle joined13:58
Neozonz|Disc joined13:59
crose left13:59
reim left13:59
qsuscs dunno13:59
daito joined13:59
darkbasic_ joined14:00
qsuscs submodules at least fit a very narrow usecase and attempts to use them otherwise will usually fail sooner or later14:00
lindenle left14:00
darkbasic left14:00
laszlof I was following this: https://github.com/git/git/commit/6cb5728c43f34a7348e128b44b80d00b9417cb19 and hoped it may let me do what I want.14:00
mkoskar left14:00
negaduck left14:01
cdown_ joined14:01
em2local joined14:01
Smurfas left14:01
kevwil joined14:02
qsuscs hmm14:02
halas joined14:02
laszlof I want to link the various javascript vendor dependencies I have for a project, but I cant just pull down the whole project, as my autoloader will just grab all the .js files it can find.14:02
qsuscs use some package manager14:02
laszlof right, that was the other option14:02
qsuscs and the better one.14:02
laszlof I was hoping to solve it with git alone, so I didnt have to add another dependency manager14:02
Neozonz|Disc left14:03
laszlof meh, better is relative. I'm trying to simplify deployment and development, and adding another task (bower update, or whatever), is one more thing I have to pipeline into my developers work flow.14:03
darkbasic joined14:04
daito left14:04
oojacoboo left14:04
darkbasic_ left14:04
oojacoboo joined14:05
fakingfantastic joined14:07
fakingfantastic Hey guys, how do you move all of your files in your repo root, into a subfolder, maintaining all the history14:07
eGGsha left14:07
_ikke_ git filter-branch14:07
arup_r_ left14:08
ms7 joined14:08
dsdeiz left14:09
m0ltar joined14:12
ayaz joined14:12
voodo left14:13
Raging_Hog joined14:13
Neozonz|Disc joined14:14
fracting left14:15
darkbasic left14:15
Es0teric joined14:15
ManikM left14:16
Phoenixz joined14:17
darkbasic joined14:18
Dougie187 joined14:19
Neozonz|Disc left14:19
cbonobo joined14:20
s8321414 left14:20
Es0teric left14:20
RockLee joined14:21
d10n-work joined14:21
nsuke joined14:22
AyushKesu left14:23
RockLee Hey guys I did a force push of some of my code because I wanted the changes in my code to take precedence over the same code a group member wrote. So in order to be able to submit my code without fast-forwarding was to force push. However, I lost all the old commits of my other team members. Is there any way to fix this or do they have to repush the code they have stored locally?14:23
jceb left14:24
_ikke_ RockLee: The latter14:24
jast I'm not sure you understood force push correctly14:24
when you push -f you're saying: make everything on the server that I don't have go away14:25
darkbasic left14:25
dionysus69 left14:25
joo-_ left14:25
darkbasic joined14:25
jast in collaboration scenarios that's usually a fool's errand because another collaborator will push it back up there again, possibly without even noticing your force push14:25
Gsham joined14:26
mikecmpbll joined14:26
boxrick1 Is there any reason a git add -A . would miss a change within a file?14:26
jmpp joined14:26
_ikke_ no14:26
jast not that I know of14:26
RockLee First time using git this semester, so I'm sure I didn't understand it correctly. Hopefully those guys see my email and resubmit their code. In the future, how can I prevent this next time? Submitting my code, merging with some parts, but not accepting the fast-forward that overwrites my code?14:27
qsuscs assume-unchanged perhaps?14:27
rpage joined14:27
qsuscs RockLee: learning git.14:27
RockLee: a fast-forward does not overwrite code14:27
jast fast-forwards don't overwrite code14:27
_ikke_ RockLee: Make sure everything is correct localy (including the commits others have pushed), and then push that (always use --force-with-lease instead of just -f)14:27
axl_ joined14:27
jast if you change a bit of code, and someone else changes it, too, at some point git will ask you to combine the two sets of changes, and how you do that is up to you14:28
Avuqo joined14:28
Avuqo left14:28
Es0teric joined14:28
mkoskar joined14:28
rscata left14:28
jast unless you force push, which allows you to skip over the combining and just discard the other person's stuff :)14:28
potatoes joined14:28
iota_pi joined14:28
Phoenixz left14:28
bernardio joined14:29
boxrick1 Would a tag cause me issues perhaps?14:29
jast with adding files? don't see how it possibly could14:29
_ikke_ boxrick1: no, a tag has nothing to do with this14:29
boxrick1 I got this14:29
1 file changed, 13 insertions(+)14:29
create mode 100644 manifests/base_utilities.pp14:29
Which indicates it finds my change14:29
_ikke_ You added a new file14:30
boxrick1 Then when I tried to commit14:30
Branch master set up to track remote branch master from origin.14:30
Everything up-to-date14:30
rscata joined14:30
_ikke_ That is not the result of commit14:30
Neozonz|Disc joined14:30
Uuis joined14:30
Uuis left14:31
Zariel joined14:31
jmpp left14:31
boxrick1 Oddly further up it says "[detached HEAD 1bccd0e]"14:32
jast it seems like you've been doing rather weird things14:33
elsevero left14:33
jast !repro14:33
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://gist.github.com/2415442 ) of your terminal session.14:33
negaduck joined14:33
gitinfo set mode: +v14:34
black_silence maybe using alias co for checkout but you think it's for commit?14:34
skul joined14:34
boxrick1 I have a script which literally does these 3 lines14:34
http://pastebin.com/AeVaYYxG14:34
FrostyX joined14:35
Neozonz|Disc left14:35
boxrick1 Then pushes a tag14:35
http://pastebin.com/ATFN6w7R14:35
EricPoe joined14:36
FrostyX Please, how to delete commit (not pushed), which is not HEAD?14:36
EricPoe left14:36
lxi joined14:36
victortyau left14:37
osse FrostyX: git rebase -i commit^ ; delete it from the editor14:37
save and quit14:37
rchavik left14:37
boxrick1 http://pastebin.com/cSN2GWjM is the output I get14:37
lxi left14:38
victortyau joined14:38
_ikke_ You are working in a detached HEAD14:39
!detached14:39
gitinfo A detached HEAD(aka "no branch") occurs when your HEAD does not point at a branch. New commits will NOT be added to any branch, and can easily be !lost. This can happen if you a) check out a tag, remote tracking branch, or SHA; or b) if you are in a submodule; or you are in the middle of a c) am or d) rebase that is stuck/conflicted. See !reattach14:39
theCole joined14:39
sshine left14:39
FrostyX osse: thank you very much. But when I do git rebase -i <hash> , I don't see that mentioned commit here14:40
_ikke_ FrostyX: You forgot the ^ or ~114:40
You need to select the parent14:40
FrostyX ah14:40
okey14:40
osse: _ikke_: yeah, thank you very much. Solved14:41
jalnt left14:41
darkbasic_ joined14:42
boxrick1 How do I end up working on a detached head?14:42
darkbasic left14:42
boxrick1 If I am literally doing the same thing each time14:42
_ikke_ Don't know what you have done14:43
mbrzuzy left14:43
_ikke_ checked out a tag perhaps14:43
veganista left14:43
qsuscs reflog might tell14:43
boxrick1 Checking out a tag sounds potential problem14:43
victortyau left14:43
boxrick1 I am using r10k which pulls based on a git tag14:44
Kicer86 joined14:44
boxrick1 Then sometimes I am modifying it and pushing it back14:44
_ikke_ right14:44
that's the problem14:44
boxrick1 So, how *should* I be doing this?14:44
_ikke_ You first have to checkout a branch before commiting14:44
boxrick1 Or rather I just do a git clone, make my changes and push it back ?14:45
_ikke_ No need for that14:45
GoddeR joined14:45
_ikke_ But that's possible14:45
victortyau joined14:45
_ikke_ work in local clones instead of the module directory directly14:45
pratikma_ left14:46
michael_mbp left14:46
boxrick1 Its usually like this, I use r10k. It pulls all my git repos based on tag14:46
I notice a problem and jump into the puppet module change it and try and push it back using my script14:46
Neozonz|Disc joined14:46
victortyau left14:46
black_silence you can create a new branch based on that tag, work there and push it.14:47
boxrick1 Is there a line I can add to basically fix it, and to check it out before pushing it back14:47
rpage left14:47
islalobo joined14:47
michael_mbp joined14:47
Dumle29 joined14:49
NeverDie left14:49
victortyau joined14:51
Neozonz|Disc left14:51
NeverDie joined14:51
EdwardIII hey14:52
_ikke_ hello14:52
EdwardIII i've got like 4-5 commits on master that should really be on a separate branch (we tend to use master for our prod stream)14:52
harish left14:52
_ikke_ boxrick1: check out a branch before you make the changes14:52
LBV_User hi all, for server-side git, is there any hook I can use to create a bare repository if there is none on the pointed location?14:52
harish joined14:52
EdwardIII what's the best approach? i did git checkout <sha_before_changes>, then rebase -i master so i could pick the commits i wanted, but it just says "noop"?14:53
jackero__ left14:53
EdwardIII should i just do the same but cherry-pick the commits i want that are in between the incorrect, new feature stuff?14:54
_ikke_ Because master is ahead of the commit you checked out, so there is nothing to do14:54
bl4ckpajamas joined14:54
_ikke_ Do you already have this branch, or do you want to create a new branch?14:54
EdwardIII hrm should i be doing the rebase the other way around as it's 'onto'? tbh i tend not to use rebase14:54
i just merge everywhere14:54
rscata left14:54
EdwardIII i figured i'd create a new "prod" branch as that would be easier than meddling with master's history14:54
(quite a few people now have that branch)14:54
t4nk363 joined14:54
flashpoint9 joined14:54
t4nk363 left14:54
chamunks left14:55
NeverDie_ joined14:55
_ikke_ Did you push these commits already?14:55
shachaf joined14:55
EdwardIII yes they're all pushed14:55
black_silence EdwardIII: you created the new branch from master with the commits you wanted there, so that branch is ready. But you want to remove them from master?14:55
EdwardIII black_silence: i want a few commits that are nestled in between14:55
reim joined14:55
zz_ag4ve joined14:56
mbrzuzy joined14:56
NeverDi__ joined14:56
gargola joined14:56
dimi1947 joined14:56
NeverDie_ left14:56
EdwardIII so maybe i should cherry pick?14:56
darkbasic joined14:56
SleePy joined14:56
darkbasic_ left14:57
_ikke_ cherry-picking just copies these commits14:57
msm joined14:57
chamunks joined14:57
black_silence ok, then rebase -i still works to remove the commits you don't want from both branches. Though it's not perfect that you pushed already14:57
EdwardIII well if i do that in a separate branch14:57
should i be OK?14:57
_ikke_ Sure, but it would be confusing if you merge that branch in again14:57
EdwardIII so checkout another branch of master, rebase from HEAD back to before the features, then pick the commits i want?14:57
hmm14:58
yeah we almost certainly will end up doing work on that branch14:58
_ikke_ EdwardIII: You seem to use rebase, when you mean reset14:58
EdwardIII ponders14:58
EdwardIII but reset won't let me choose which commits i want?14:58
NeverDie left14:58
_ikke_ Correct14:58
You have to do it in multiple steps14:58
EdwardIII but that's what i need (i think)14:59
_ikke_ The first step is that you reorder the commits14:59
EdwardIII hrm with rebase -i on master?14:59
_ikke_ So that all the ones you want to move are on top14:59
michael_mbp left14:59
Zariel left14:59
_ikke_ EdwardIII: rebase -i <parent-of-last-commit-you-want-to-have>14:59
NeverDi__NeverDie15:00
alexwaters joined15:00
lindenle joined15:00
EdwardIII hrm so i'm still rewriting history on master though?15:00
nisseni left15:01
bmilesp left15:01
black_silence if you pushed the commits you don't want to master, there's no other way15:01
michael_mbp joined15:01
_ikke_ EdwardIII: yes15:01
fubi_ joined15:01
EdwardIII when happens when i push?15:01
_ikke_ Though, you can use a temporary branch too15:01
so you leave master alone15:02
Zariel joined15:02
_ikke_ !rewrite15:02
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/waqum15:02
EdwardIII i guess a temp branch is the best move... as long as i don't have to change it (and then thus merge it back in)15:02
Zariel left15:02
black_silence you can undo the changes with an anti-commit too15:02
Neozonz|Disc joined15:02
davidkrauser joined15:02
acolson left15:02
Zariel joined15:02
EdwardIII i guess i can just make changes to the master branch then er... do rebase/cherry pick onto this temp prod branch anyway if i really need it15:03
lb1a left15:03
EdwardIII then once it's ok for those features to go in just delete prod and switch back to your normal model (master = prod)15:03
it's just for a week. basically someone implemented a change to comply with a BC breaking change on an upstream vendor, but their changes don't go into prod until monday15:04
dimi1947 I am facing the following situation...I have added 2 rules in a css file...but I want one of them to be commited in a separate branch15:04
what should I deal it?15:04
EdwardIII and we need to do a prod release before then which is still on the old upstream api15:04
dgutierrez1287 left15:04
lindenle left15:05
black_silence dimi1947: commit one rule, stash the other and move to the other branch, unstash there15:05
davidkrauser left15:06
flashpoint9 left15:06
davidkrauser joined15:06
Neozonz|Disc left15:06
rpage joined15:07
skynxnex left15:07
flashpoint9 joined15:07
dimi1947 how am I going to commit one rule and leave the other out?...commits are made at per file basis15:07
grawity no they aren't: `git add -p`15:07
dimi1947 grawity, what is git add??15:08
-p15:08
jast patch mode. you can choose individual patch hunks to stage for committing15:08
grawity how the hell have you been committing things without `git add`15:08
bonswouar left15:08
jast presumably the "I don't want any flexibility" mode, git commit -a15:09
rivarun left15:09
grawity yes but adding new files...15:09
dimi1947 there was never a need to before to commot individual patch hunks15:09
rivarun joined15:09
grawity what about committing individual files15:10
jast alternatively, in git gui you can right-click on individual lines to stage them15:10
black_silence you can use a gui like git-cola if you like that better. there you have a graphical overview and can stage blocks or even lines if required15:10
dimi1947 I use git gui15:10
jast what I said, then :)15:10
marlinc left15:11
dimi1947 git cola is a different gui and the question is which is better? sincde you brought the subject15:11
dionysus69 joined15:11
reim left15:11
jast I've never looked at git-cola15:12
black_silence git gui uses tcl/tk, that doesn't look very nice in my gtk desktop ^^15:12
dimi1947 so you suggest git cola15:12
?15:12
marlinc joined15:13
bmilesp joined15:13
jast git gui does the job. if you don't mind the somewhat dated visual aesthetic, there may be no need to switch15:13
black_silence for me, yes. I don't know your environment. Basic functionality seems to be the same15:13
roelmonnens left15:13
dimi1947 Ok...this another discussion I am going to focus on the subject at hand now...staging hunks15:14
aswen joined15:14
dionysus70 joined15:14
lindenle joined15:14
dimi1947 one question..what is a hunk...how do you define it?15:15
alexwaters left15:15
Hink joined15:16
dionysus69 left15:16
grawity something like "a contiguous chunk of changed lines"15:16
dimi1947 ok..got it15:16
black_silence A set of changes, may be multiple lines. A certain number of unchanged lines between changes splits them into hunks15:16
dionysus70dionysus6915:16
potatoes left15:16
grawity the @@ ... @@ lines are hunk headers/separators15:16
if that helps15:17
pratikmallya joined15:17
dionysus69 left15:17
eme left15:17
dionysus69 joined15:17
dimi1947 got it15:17
Neozonz|Disc joined15:18
chamunks left15:18
Neozonz|Disc left15:18
Neozonz|Disc joined15:18
thiago joined15:18
black_silence left15:19
FrostyX left15:19
shinnya joined15:20
chamunks joined15:20
inspec joined15:21
strayPuppy joined15:21
inspec hi, i just installed git-2.5.3-64-bit for windows. i can't seem to find the ssh-keygen executable anywhere in it's program files dir, tho. has it been removed? it was in with the older version i had prior.15:22
Hink_ joined15:22
Neozonz|Disc left15:23
mchelen1 joined15:24
Alienpruts left15:24
mchelen1 is there any shorthand to push a new local branch to the default remote using the local branch name?15:24
sinkensabe left15:24
alexwaters joined15:24
mchelen1 basically want to do "git push -u remotename branchname" without having to specify remotename & branchname15:24
Hink left15:25
Hink_ left15:25
p1k joined15:25
otter768 joined15:26
eme joined15:27
zoso left15:27
_ikke_ There is no default remote15:27
alexwaters left15:27
mchelen1 ah ok, well i only have 1 remote configured15:27
linuxmint2 left15:28
_ikke_ I don't think there is a way for git to automatically assume that currently15:28
howlymowly left15:28
mchelen1 oh well thanks anyway, i'll live with the extra keystrokes :)15:29
Gama11 joined15:29
IWishIKnew joined15:30
pratikma_ joined15:30
otter768 left15:30
fakingfantastic left15:30
Amandil joined15:31
intellix left15:32
NeverDie left15:32
dimi1947 is there a way I can rename a branch?15:33
pratikmallya left15:33
_ikke_ sure15:33
git branch -m <old> <new>15:33
open_defiance joined15:34
Neozonz|Disc joined15:34
beaconwriter joined15:34
open_defiance is there some simple way of quantifying something like the hamming distance between commits?15:34
(or another bytestring metric)15:34
scoobertron joined15:35
grawity if you mean git built-in tools, then no, afaik there is only a basic addition/removal count15:35
(diff --stat or --numstat)15:35
TomyWork left15:36
open_defiance yes, I've been using --numstat.15:36
for tracking productivty. but some of my files are binaries.15:37
deepend joined15:37
open_defiance thanks anyway15:37
ilmgb left15:37
ilmgb joined15:38
sinkensabe joined15:38
ayaz left15:38
scarabx joined15:38
Neozonz|Disc left15:38
allcentury left15:38
Balliad left15:39
freimatz left15:39
tang^ joined15:39
linuxboytoo joined15:39
linuxboytoo left15:41
dfaught joined15:42
ilmgb left15:42
Raging_Hog left15:42
dionysus69 left15:42
mbrzuzy left15:42
Amandil left15:43
Noldorin left15:44
dfaught left15:44
flashpoint9 left15:44
_rgn not sure if i would consider lines added and removed a good metric for productivity15:45
bremner lines removed - lines added ;)15:45
open_defiance it's funny that searching the web for "git commit hamming distance" gives me numerous unrelated github packages. and -site:github.com is probably a bad move instead.15:45
Eugene Mmmm ham15:45
qsuscs indeed15:45
open_defiance _rgn: this particular repos is all text. so there's no "reexpressing in a more concise way" in a first pass. in a second pass, in revision, that's messier.15:46
ayaz joined15:46
qsuscs Eugene: is it already time for a new topic?15:46
open_defiance also: "lines" = paragraphs. that's really noisy.15:46
ThomasLocke left15:46
Eugene By jove, it is!15:46
gfixler left15:46
ChanServ set mode: +o15:46
qsuscs good.15:46
petersr joined15:46
Noldorin joined15:47
qsuscs changed the topic to: Welcome to #git, the place for git help and ham | Current stable version: 2.5.3 | Start here: http://jk.gs/git | Getting "cannot send to channel"? /msg gitinfo .voice | Submit, or there will be fresh ham! https://madeitwor.se/git-jokes15:47
qsuscs set mode: -o15:47
petersr left15:47
ayaz left15:47
Hounddog left15:48
islalobo left15:49
Neozonz|Disc joined15:50
nnyk_ joined15:50
jagob left15:50
RockLee left15:51
abacuspowers joined15:51
davispuh joined15:53
Neozonz|Disc left15:54
dreiss joined15:55
reim joined15:57
DuckMaestro joined15:57
The_Phoenix joined15:57
skullcrasher_ left15:58
jost left15:58
ProT-0-TypE left15:58
T3ng` joined15:59
Darcidride_ left16:00
sq-one joined16:00
Internet13 joined16:01
aswen left16:01
davispuh left16:04
dgutierrez1287 joined16:04
eme left16:04
Caius joined16:04
Caius left16:04
Caius joined16:04
ashnur joined16:05
Noldorin left16:05
curiousmansi joined16:05
reim left16:05
Noldorin joined16:05
Neozonz|Disc joined16:06
flashpoint9 joined16:07
m0ltar left16:09
ilmgb joined16:09
allcentury joined16:09
p4trix left16:09
Guest48 joined16:09
kristjansson joined16:10
Neozonz|Disc left16:10
nnyk_ left16:10
nfk joined16:13
bronson joined16:13
Guest48 left16:13
hyperair left16:14
allcentury left16:14
inspec left16:14
NeverDie joined16:15
jmpp joined16:15
jteneyck joined16:16
Phoenixz joined16:16
maletor joined16:16
snowcycle joined16:18
xiaotong joined16:20
jmpp left16:20
ilmgb left16:20
skynxnex joined16:21
skynxnex left16:21
Neozonz|Disc joined16:21
Neozonz|Disc left16:21
Neozonz|Disc joined16:21
basiclaser joined16:22
maletor left16:22
bernardio left16:23
p1k left16:23
reim joined16:23
fubi_ left16:24
allcentury joined16:24
FrostyX joined16:24
darkbasic_ joined16:25
jteneyck_ joined16:26
halas left16:26
Neozonz|Disc left16:26
darkbasic left16:26
bernardio joined16:26
sinkensabe left16:26
jteneyck left16:26
axl_ left16:27
jteneyck joined16:27
jteneyck left16:27
jteneyck joined16:27
bernardio left16:27
dreiss left16:28
bernardio joined16:28
axl_ joined16:29
akiva joined16:29
nuck joined16:29
bilb_ono joined16:30
xiaotong left16:30
jteneyck_ left16:31
cvanball joined16:31
NeverDie left16:32
nerd joined16:32
skapunker joined16:33
NeverDie joined16:35
Guest48 joined16:35
ms7 left16:35
p1k joined16:36
bernardio left16:37
Neozonz|Disc joined16:37
Neozonz|Disc left16:37
Neozonz|Disc joined16:37
MechtiIde joined16:38
jeffreylevesque why does travis successfully ssh into github, yet errors on that succsess - https://travis-ci.org/jeff1evesque/machine-learning/builds/81422050#L84?16:38
freestyl3r left16:38
nsuke left16:38
dimi1947 left16:39
liamonade left16:39
alfism joined16:39
Guest48 left16:39
Gsham left16:39
dimi1947 joined16:40
qsuscs jeffreylevesque: that’s still an SSH issue, not a git one16:40
Seveas jeffreylevesque: because ssh exits with code 1 as not being able to start a session is an error. Whether authentication succeeded or not.16:41
dionysus69 joined16:41
devoldmx joined16:41
Neozonz|Disc left16:42
it_tard joined16:42
nfk left16:42
it_tardnfk16:42
Thorax2015 left16:44
tag joined16:45
Nevik !crosspost16:45
gitinfo Note: The above question was posted in both #git and #github16:45
Guest48 joined16:46
devoldmx left16:46
Nevik (i have also answered it in #github)16:46
bernardio joined16:46
imachuchu joined16:46
shad left16:47
durham joined16:47
rwb joined16:48
githogori_ left16:48
bernardio left16:49
tvw left16:51
abacuspowers left16:51
mikiones left16:52
Nizumzen left16:53
Neozonz|Disc joined16:53
bernardio joined16:54
holodoc joined16:55
DuckMaestro_ joined16:55
foist_ joined16:55
abacuspowers joined16:55
blob joined16:55
blobGuest8771316:56
Hanumaan left16:56
joo-_ joined16:56
thiago left16:56
prefixed joined16:57
tyreld joined16:57
hyperair joined16:57
noisebleed_ left16:57
Neozonz|Disc left16:58
hahuang61 joined16:58
foist_ left16:59
bernardio left16:59
bilb_ono left17:00
theCole_ joined17:01
bernardio joined17:02
petersaints left17:02
curiousmansi left17:03
Zariel left17:03
theCole left17:03
petersaints joined17:04
aard left17:04
codesing left17:05
bernardio left17:05
T3ng` left17:06
bernardio joined17:06
MinetestForFun joined17:07
bilb_ono joined17:07
farn joined17:08
ProT-0-TypE joined17:08
reim_ joined17:09
Neozonz|Disc joined17:09
jbondhus_ joined17:09
reim left17:09
stamina left17:12
rgb-one left17:12
Neozonz|Disc left17:14
beaconwriter left17:14
meLon joined17:15
Impaloo How does one remove a worktree?17:16
oh, you have to do it manually17:17
jedix I recall someone once gave me a git repo in one file, but I don't recall the key word to find the command17:17
Impaloo jedix: you mean a tarball or something?17:17
jedix no, I could clone directly from the file17:17
Nevik jedix, man git-bundle17:17
gitinfo jedix: the git-bundle manpage is available at http://jk.gs/git-bundle.html17:17
jedix thanks17:17
bilb_ono left17:18
Olipro left17:19
andyrs left17:19
bernardio left17:19
Lyqyd joined17:21
mbrzuzy joined17:21
Gsham joined17:22
CussBot left17:22
CussBot joined17:22
bernardio joined17:23
Jackneill joined17:23
catsup left17:24
kl3 joined17:25
Neozonz|Disc joined17:25
bilb_ono joined17:26
negaduck left17:26
The_Phoenix left17:26
otter768 joined17:27
dionysus69 left17:27
Sasazuka joined17:27
thedodd joined17:28
voodo joined17:28
gopar joined17:28
bernardio left17:29
eme joined17:29
youser joined17:29
Neozonz|Disc left17:29
mac_ified joined17:29
liamkeily joined17:30
beaconwriter joined17:31
otter768 left17:31
Guest48 left17:32
gfixler1 joined17:32
cdown left17:32
mjt left17:32
ilmgb joined17:32
voodo left17:32
tvw joined17:32
cdown joined17:33
bernardio joined17:33
eme left17:34
kpease joined17:34
andyrs joined17:35
luksaur left17:35
abacuspowers left17:35
ilmgb left17:36
dimi1947 left17:37
dreiss joined17:39
jmpp joined17:42
dionysus69 joined17:42
mbrzuzy left17:42
theCole_ left17:43
gamename joined17:44
cvanball left17:45
kpease left17:45
kpease joined17:45
adgtl joined17:46
catsup joined17:47
Gsham left17:47
jstimm joined17:47
shinnya left17:48
Gsham joined17:49
thiago joined17:50
luksaur joined17:52
gamename Hi guys. I'm trying to figure out a way to deploy code to a test machine before I do a git push to master (on github). That is to say, I have newly-written code on my local box, and I want to send it to a test box (on aws in this case) to verify all of it works. Then, when it has been tested, I will commit/push to github master. I'm told that there is a way to use my local box as a repo for the test machine on aws. Make sense?17:53
Possible?17:53
Or, even a good idea?17:53
Hedgework Testing before deploying is always good :)17:53
gamename Hedgework ...and I have the scars to prove it. :)17:53
Hedgework I don't have time to walk you through possible implementations, but check out !deploy and !workflow for starting points.17:53
gitinfo Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html17:53
Finding the right workflow for you is critical for the success of any SCM project. Git is very flexible with respect to workflow. See http://sethrobertson.github.com/GitBestPractices/#workflow for a list of references about choosing branching and distributed workflows.17:53
gamename Hedgework U da man. Thanks.17:55
Hedgework np17:56
howdoi left17:57
DuckMaestro_ left17:57
intellix joined17:59
mbrzuzy joined18:01
theCole joined18:02
SJr left18:03
bongjovi left18:06
Gsham left18:06
T3ng` joined18:07
Chill_Surf left18:07
bb010g joined18:08
gitinfo set mode: +v18:08
negaduck joined18:08
nour joined18:08
aard_ joined18:09
bernardio left18:10
darkbasic joined18:10
darkbasic_ left18:11
T3ng` left18:11
cdown left18:12
gfixler1 left18:12
andyrs left18:13
bilb_ono left18:13
Lunatrius left18:15
aard_ left18:15
theCole left18:15
kl3 left18:16
lg188 joined18:16
joki left18:16
abacuspowers joined18:17
andyrs joined18:17
jagob joined18:17
darkbasic left18:18
nour left18:18
darkbasic joined18:18
encod3 left18:19
mihaicris joined18:19
tarkus joined18:21
joki joined18:21
FrostyX left18:22
hyperair left18:23
hyperair joined18:24
youser left18:26
nisseni joined18:27
rockstar__ joined18:28
rockstar_ joined18:28
pandeiro joined18:28
liamkeily left18:28
gamename left18:34
IWishIKnew left18:36
dickdaley left18:36
blimpse joined18:38
phantombeta left18:38
yqt joined18:39
sazed joined18:39
phantombeta joined18:40
SimonNa joined18:40
theCole joined18:41
oremanj joined18:42
devoldmx joined18:42
andyrs left18:42
jstimm left18:43
liamkeily joined18:44
oremanj Hi folks! I have two git repositories, and am trying to import the second as a subtree of the first. We're using a git<->svn mirroring system that doesn't deal well with multiple root commits, so I'm trying to do this using rebase.18:44
_ikke_ You don't want to use rebase in combination with svn18:44
enzob joined18:44
jstimm joined18:45
Guest48 joined18:45
oremanj People with checkouts of the second repository are going to switch to using the first - that's not the issue.18:45
The svn thing is mostly not relevant to my problem except that it explains why I can't just use git merge -Xsubtree=foo to solve my problem.18:46
kpease left18:46
Ingenia left18:46
kpease joined18:46
oremanj git rebase -Xsubtree=foo is working well with linear history but producing conflicts when there's branching/merging, and git rebase -p -Xsubtree=foo stops with an error at the first merge commit ("fatal: Unknown option for merge-recursive: -X'subtree=foo'")18:46
gfixler1 joined18:47
devoldmx left18:47
oremanj Is there something else I want to be using instead (filter-branch maybe?) or am I out of luck?18:47
jstimm left18:47
joo-_ left18:47
kahmalo joined18:47
kpease left18:48
kpease joined18:48
joo-_ joined18:49
_ikke_ I wonder how you would merge two repositories without getting multiple roots..18:50
joo-_ left18:50
kpease left18:50
gitinfo set mode: +v18:50
oremanj The repo-A equivalent of repo-B's root gets the prior tip of repo-A as its parent18:50
adgtl left18:50
kpease joined18:51
Guest48 left18:51
oremanj Basically I'm trying to take the entire history of repo-B, put it all in a subtree, and tack it onto the end of repo-A's development18:51
bl4ckpajamas left18:51
nettoweb left18:51
nnyk_ joined18:51
_ikke_ sounds like grafts + filter-branch18:51
kahmalo In gitk, how can I make the date column show committer dates rather than author dates? (I don't care whether the names and email addresses are affected.)18:51
oremanj I'll look up grafts, thanks!18:51
shinnya joined18:52
bango2 joined18:52
nerd left18:53
Guest48 joined18:53
thomasreggi joined18:54
jstimm joined18:55
jstimm left18:56
mikiones joined18:56
nerd joined18:57
jrahmy joined18:57
darkbasic_ joined18:57
Balliad joined18:57
darkbasic left18:58
deepy left18:58
kolobyte left18:58
dickdaley joined18:59
Guest48 left18:59
deepy joined19:00
mbrzuzy left19:01
mchelen1 left19:01
kahmalo I guess that, if such a feature existed, it would be in proc drawcmittext. But it isn't.19:01
bunniez joined19:01
sazed left19:02
bunniez left19:03
DuckMaestro left19:04
editshare-ericf joined19:05
noisebleed joined19:06
freestyl3r joined19:06
lg188 left19:07
andyrs joined19:07
T3ng` joined19:07
hahuang61 left19:08
NeckBeardPrince joined19:08
ilmgb joined19:08
luksaur left19:10
darkbasic_ left19:10
darkbasic joined19:10
kpease left19:10
andyrs left19:10
slash77 joined19:10
andyrs joined19:10
kpease joined19:11
andyrs left19:11
thomasre_ joined19:11
thomasreggi left19:12
andyrs joined19:12
T3ng` left19:12
kevwil left19:12
andyrs left19:13
adgtl joined19:13
ilmgb left19:13
kpease left19:15
darkbasic left19:15
paulweb515 left19:15
kpease joined19:15
adgtl left19:15
DXR_ joined19:15
darkbasic joined19:16
mbrzuzy joined19:16
p1k left19:18
dionysus69 left19:19
strayPuppy left19:20
enzob left19:20
Dro__ left19:20
rockstar__ left19:20
kahmalo left19:21
rockstar__ joined19:21
tristanp joined19:22
nisseni left19:22
noisebleed left19:24
dgutierrez1287 left19:24
shuaib joined19:24
sazed joined19:26
Maroloccio joined19:27
otter768 joined19:28
winegoddess left19:28
darkbasic_ joined19:29
nisseni joined19:29
darkbasic left19:29
jottr joined19:29
Maroloccio left19:29
kristjansson left19:30
boombatower joined19:31
settermjd joined19:31
otter768 left19:32
liamkeily left19:33
darkbasic_ left19:33
liamkeily joined19:33
cagedwisdom joined19:34
darkbasic joined19:35
gamename joined19:36
DXR_ left19:36
gamename hi guys. How can I get the toplevel directory (as in "git rev-parse --show-toplevel") when I'm somewhere outside the git-controlled dirs? Put another way I need to find out the toplevel dir for 'bar' is 'foo' (/foo/bar), but I'm calling the git rev-parse command from /baz (i.e. another place in the filesystem outside git's control). Make sense?19:36
settermjd left19:37
settermjd joined19:37
DXR joined19:37
qsuscs gamename: git -C /foo/bar rev-parse --show-toplevel19:37
rockstar__ left19:38
gamename qsuscs kewl! Thanks.19:38
rockstar_ left19:38
winegoddess joined19:38
adgtl joined19:38
gamename qsuscs Hmmm... my git exec does not like the '-C'19:39
qsuscs I'm on git 1.8.3.119:39
adgtl_ joined19:39
sanketdg left19:40
sentriz joined19:40
thomasreggi joined19:42
temmi_hoo left19:43
thomasre_ left19:43
adgtl left19:43
sazed left19:43
liamkeily left19:44
adgtl_ left19:45
alfism left19:45
tomog999_ joined19:45
donnib_ joined19:45
darkbasic left19:46
jrahmy left19:46
darkbasic joined19:46
paulweb515 joined19:47
tomog999 left19:48
_tgunr left19:48
temmi_hoo joined19:48
tgunr joined19:49
t4nk734 joined19:49
tgunr left19:49
shad joined19:50
MinetestForFun left19:50
gitinfo set mode: +v19:50
t4nk734 Hi everyone, I recently submitted a PR by creating a branch off of my master, when acutally I was supposed to submit a PR by creating a branch off of another branch that is not master19:50
how can I fix my PR so that I put my new branch on top of the branch I was supposed to extend19:51
I hope that makes sense19:51
iveqy t4nk734: sounds strange, usually your PR should be based on master19:51
t4nk734 I know we have a weird set up19:51
iveqy anyhow, the command is rebase, see man git rebase19:51
gitinfo the git-rebase manpage is available at http://jk.gs/git-rebase.html19:51
iveqy and then you've to do a forced push see man git push (look for -f)19:51
gitinfo the git-push manpage is available at http://jk.gs/git-push.html19:51
flashpoint9 left19:51
t4nk734 What if I just resubmit a new PR19:52
tgunr joined19:52
iveqy t4nk734: then you don't have to do a forced push, but you still need to rebase to get your branch based on "another branch" instead of on master19:53
t4nk734 okay19:53
PCatinean left19:53
tgunr left19:53
tgunr joined19:53
tgunr left19:54
tgunr joined19:54
dgutierrez1287 joined19:55
tgunr left19:55
tgunr joined19:56
tgunr left19:57
settermjd left19:57
miosx joined19:58
thomasreggi left20:01
winegoddess left20:01
pandeiro left20:02
Hink joined20:03
Guest48 joined20:04
SJr joined20:04
dgutierrez1287 left20:04
Guest48 left20:05
dgutierrez1287 joined20:05
tgunr joined20:05
liamonade joined20:05
tinajohnson left20:05
tgunr left20:05
ahr3n joined20:05
Lunatrius joined20:06
liamonade left20:06
Hink left20:07
beaconwriter left20:07
bishopj left20:08
bishopj joined20:08
adgtl joined20:08
T3ng` joined20:08
mbrzuzy left20:09
nisseni left20:10
ahr3n left20:10
fullstack is there a better way to do 'git diff HEAD HEAD^' and then 'git diff HEAD^ HEAD^^' and then ^^ ^^^ and then ^^^ ^^^^?20:10
tristanp left20:10
theCole left20:11
eme joined20:11
MasterPiece joined20:11
_ikke_ fullstack: git log -p20:11
fullstack _ikke_, thanks20:12
gfixler1 left20:12
T3ng` left20:13
devoldmx joined20:13
asfdfdfd_ joined20:14
d10n-work left20:14
jrahmy joined20:15
eme left20:16
joo-_ joined20:16
nerd left20:17
devoldmx left20:17
asfdfdfd left20:17
liamonade joined20:19
miosx left20:19
basiclaser left20:19
Phoenixz left20:20
liamonade left20:20
Phoenixz joined20:20
ecraven joined20:21
slash77 left20:21
MasterPiece left20:21
Takumo joined20:22
Takumo left20:22
Takumo joined20:22
Gianormagantrous joined20:22
Gianormagantrous left20:22
Gianormagantrous joined20:22
mbrzuzy joined20:22
maletor joined20:22
grawity joined20:23
paul424 joined20:24
stamina joined20:24
biertie joined20:24
tristanp joined20:25
dgutierrez1287 left20:25
nettoweb joined20:25
Guest59784 joined20:26
jrahmy left20:26
z0idBerger joined20:27
Guest59784 left20:27
EvilJStoker_ joined20:27
gufertum joined20:28
mihaicris left20:29
noisebleed joined20:30
Mega _ikke_: Thank you man!20:30
_ikke_ You're welcome20:31
DXR left20:31
paul424 How should I return to the top commit when the working direcotry is modified ?20:33
by reset --hard HEAD , right ?20:33
shuaib left20:33
_ikke_ right20:35
Note that you cannot undo it20:35
t4nk734 left20:35
nfk left20:35
Gianormagantrous You are at that commit paul424, if you want your working folder and files to represent that commit, yes, you do git reset --hard hence losing your not committed changes20:36
dougsland left20:36
jagob left20:37
tristanp left20:38
tristanp joined20:39
tobyx joined20:40
Gianormagantrous On another topic: I do not mean to say that detached HEAD is wrong in anyway. I just want you guys opinion on how one should checkout a commit for, say, reviewing purposes. Currently, I do 'git checkout myCommitHash'. Then I do tests, edits, tests and what not and then going back to my current branch HEAD using 'git checkout myBranchPlease'.20:41
biertie left20:41
jteneyck left20:41
darkbasic left20:41
Takumo left20:41
strayPuppy joined20:42
grawity left20:42
antispaceman joined20:42
_ikke_ Nothing wrong with that20:42
Gianormagantrous How could I make my working directory reflect a given commit *without* changing the .git/HEAD file20:42
biertie joined20:43
_ikke_ Why would that be a problem?20:43
HEAD reflects what you currently have checked out20:43
theCole joined20:43
sunny256 joined20:43
_ikke_ That's its definition20:43
darkbasic joined20:43
Gianormagantrous Yes I you are right, let me explain:20:44
ahf joined20:44
bjornars joined20:44
myme1 joined20:45
canton7 joined20:45
canton7 left20:45
canton7 joined20:45
weox joined20:45
Gianormagantrous If I checkout an old commit, I am in detached head. If I want to commit those changes to the tip of my branch (for some reason) I am not sure it is that right way to go20:45
_ikke_ AS long a they don't conflict, there would be no problem20:45
Takumo joined20:46
Takumo left20:46
Takumo joined20:46
synchronous joined20:46
_ikke_ And otherwise you'd stash, checkout, apply, fix conflicts20:46
donnib_ left20:46
grawity joined20:46
NeverDie left20:46
winegoddess joined20:46
Gianormagantrous Ain't there a way to make a working directory reflect a given commit without checking that commit out?20:47
rpage left20:47
Gianormagantrous ^As if I had edited those file manually to reflect said commit?20:47
sgambino left20:47
BigWillie left20:47
_ikke_ Gianormagantrous: git checkout <commit> .20:47
including the dot20:48
BigWillie joined20:48
_ikke_ Note that it will overwrite any uncomitted changes20:48
So make sure your working tree is clean20:48
rwb left20:48
Gianormagantrous wow thanks _ikke_20:48
_ikke_ But note that in this case it becomes much harder to commit the changes you want to make20:49
cdown joined20:49
EvilJStoker_EvilJStoker20:50
mizu_no_oto left20:50
Gianormagantrous Yes, I can see why, but obviously, it depends.20:50
g0th joined20:52
Gianormagantrous Do you know why this gets automatically added to the staging area?20:52
NeverDie joined20:52
_ikke_ That's how checkout works20:53
Gianormagantrous hmm20:53
rockstar_ joined20:53
rockstar__ joined20:53
Gianormagantrous I am not sure why though.20:54
In the man it says "Updates files in the working tree to match the version in the index or the specified tree."20:54
tvw left20:55
IWishIKnew joined20:56
sq-one left20:56
Gianormagantrous So, lets say you want to revert to an old function you wrote 5 commits ago and commit that to your branch, how would you guys go about doing that?20:56
sarri left20:56
Gianormagantrous I find it odd to have to checkout something and then having to unstage that stuff out.20:57
tang^ left20:57
cdown left20:57
Balliad left20:58
Ornacia joined20:58
choki joined20:59
sarri joined20:59
davidkrauser left20:59
jeffreylevesque left21:00
nemix__ left21:00
nemix_ joined21:00
nemix__ joined21:01
Gianormagantrous Maybe "revert" is what I am looking for.21:01
druidd joined21:02
Gianormagantrous is reading the man page for revert for the first time in years using git…21:02
MarkyC left21:02
rodrigograca31 joined21:03
cavallari left21:04
jrahmy joined21:04
druidd left21:04
nemix_ left21:04
gfixler1 joined21:05
Gianormagantrous Or maybe not : "If you want to extract specific files as they were in another commit, you should see git checkout, specifically the git checkout <commit> -- <filename> syntax."21:05
mbrzuzy left21:09
adgtl left21:09
T3ng` joined21:09
ilmgb joined21:09
ahr3n joined21:09
Dirkson joined21:12
Dirkson Hey all. I screwed up my working copy, and want to go back to my last commit. How do I do that?21:12
Gamecubic left21:12
jottr left21:12
Gianormagantrous git checkout HEAD21:12
git reset --hard21:13
T3ng` left21:14
ilmgb left21:14
winegoddess left21:14
BigWillie left21:14
j416 Gianormagantrous: "git checkout HEAD" does nothing21:15
Balliad joined21:15
Dirkson Thanks21:15
Gianormagantrous yes, j416 I got confused21:15
tpollard joined21:15
j416 Gianormagantrous: perhaps you mean "git checkout HEAD ."21:15
Gamecubic joined21:16
FrostyX joined21:17
jottr joined21:18
pantsman- left21:18
winegoddess joined21:19
rnsanchez left21:20
allcentury left21:20
bmilesp left21:20
mbrzuzy joined21:21
abacuspowers left21:21
jmpp left21:21
jrahmy left21:21
BigWillie joined21:21
chitopunk left21:22
winegoddess left21:23
liamonade joined21:23
winegoddess joined21:23
BigWillie left21:24
shad left21:24
tristanseifert joined21:24
otter768 joined21:28
BBBThunda left21:30
CKyle left21:30
wEs joined21:32
wEs left21:32
wEs joined21:32
winegoddess left21:32
mbrzuzy left21:32
bb010g left21:33
otter768 left21:33
Balliad left21:33
negaduck left21:34
adgtl joined21:34
LBV_User left21:35
dsdeiz joined21:35
jmpp joined21:35
ok4n joined21:36
elux joined21:36
bishopj left21:37
bishopj joined21:38
gamename left21:41
gopar left21:41
mchelen1 joined21:41
mchelen1 when i do `git stash` does it go to the end (highest number) or beginning (lowest number)?21:42
tag left21:42
Jackneill left21:43
theCole left21:43
bmilesp joined21:44
spaceone gr, i always end up in this error:21:44
Your branch and 'upstream/fix_ssl_handshake#114' have diverged,21:44
and have 37 and 36 different commits each, respectively.21:44
(use "git pull" to merge the remote branch into yours)21:44
I don't know how to fix this / what i am doing wrong21:44
duckmaestro joined21:44
jottr left21:45
spaceone if i make a diff of the branches i only get my local changes.21:45
i also fixed the order of the commits with rebase -i21:46
still the same error21:46
FernandoBasso joined21:47
jrahmy joined21:48
SonikBoom joined21:50
axl__ joined21:51
negaduck joined21:51
elux left21:52
FernandoBasso I have a repository foo on a local drive. I want to do git clone /path/to/foo /path/to/bar, to create copy of foo locally, change bar and push back to foo, always locally. Is that possible?21:52
axl_ left21:52
axl__axl_21:52
FernandoBasso I read about bare repos, but I am still uncertain.21:54
T3ng` joined21:55
gufertum left21:55
z0idBerger left21:55
gufertum joined21:55
bremner FernandoBasso: is there some reason you don't just try it? what seems to be the actual difficulty?21:55
gufertum left21:55
FernandoBasso bremner: I will later update the files of this "bare" repo to an ftp server, which is the deploy method for this particular project. But then, the bar repo has git directories scattered in that directory.21:56
toothrot joined21:57
FernandoBasso Perhaps this is not the right approach, that is why I ask.21:57
jrahmy left21:57
bremner I see. well I guess you've read the standard deploy blurb, I don't have anything to add to that.21:57
FernandoBasso I want to test locally, in a "copy" of the main project, push back to that main project, and then upload through ftp.21:57
Gama11 left21:57
FernandoBasso bremner: Okay. Thanks.21:58
bango2 left21:58
m0ltar joined21:58
sentriz left21:58
malavv left21:58
Dougie187 left21:58
daito_ joined21:59
blimpse left22:00
macabre left22:00
mizu_no_oto joined22:00
jeffreylevesque joined22:01
jeffreylevesque left22:01
jeffreylevesque joined22:01
victortyau left22:02
Mega left22:03
nerium joined22:03
nerium How can I check if a branch/tag exists?22:04
daito_ left22:04
tjm_jimmy joined22:05
nerd joined22:06
mchelen1 left22:08
Es0teric left22:08
CKyle joined22:09
Gianormagantrous nerium, you can check in .git/refs/tags and .git/branches22:10
jml32ljl2 joined22:10
Gianormagantrous also 'git tag -l' and 'git branches -al'22:10
vikas027 joined22:10
Gianormagantrous *branch*22:11
intellix left22:12
nettoweb left22:14
devoldmx joined22:14
IWishIKnew left22:15
preaction there's also git show-ref22:15
aucecil joined22:16
sssilver joined22:17
devoldmx left22:18
BigWillie joined22:18
gargola left22:18
adgtl left22:20
NeckBeardPrince left22:20
anoob joined22:20
editshare-ericf left22:20
CKyle left22:21
mizu_no_oto left22:22
Kicer86 left22:23
tgunr joined22:24
anoob i've not added my files to index and removed then with git reset --hard ... is it possible to recover them? :(22:24
aeo1ackn joined22:24
pratikma_ left22:24
Eugene Nope; they're gone. Sorry.22:24
matthiaskrgr you might be lucky with extundelete22:25
(if you run ext as a FS)22:25
markelite left22:26
aeo1ack left22:26
stamina left22:27
whitby joined22:28
s8321414 joined22:29
anoob left22:30
wrouesnel2 left22:32
madewokherd joined22:32
BigWillie left22:32
NeverDie left22:35
noisebleed left22:36
skirk joined22:36
strayPuppy left22:36
choki left22:37
nate_c joined22:37
markelite joined22:37
thedodd left22:37
nerium Is there a way to specify a branch when using git ls-files?22:37
jmpp left22:39
StuartMI left22:39
WaReZ joined22:40
NeverDie joined22:42
gfixler1 left22:42
ignas left22:43
axl_ left22:43
jottr joined22:43
aeo1acks joined22:44
adgtl joined22:44
endiruna joined22:44
hc123 joined22:45
WaReZ left22:45
aeo1ackn left22:45
hc123 hi, i have a quick question, i have 2 branches (master and experiment), and master just got a bug fix that i want in experiment. is the best choice to do a rebase?22:46
SonikBoom left22:46
hc123 i still want to keep both branches22:46
phroa your options are to merge the branches or copy the commit with cherry-pick22:47
adgtl_ joined22:47
phroa I suggest merge unless you have features you don't want in both; cherry-pick is often confusing to look at later22:48
hc123 ok thanks22:49
gfixler1 joined22:50
phroa merging hotfixes back to develop & master is how git-flow recommends you do it, if that matters.22:51
adgtl left22:51
jottr left22:51
nemix joined22:53
nemix__ left22:53
weox left22:55
btree joined22:57
pratikmallya joined22:57
ASOLAr joined22:57
jmpp joined22:58
CEnnis91 left22:59
D-Boy left23:00
nnyk_ left23:00
dsdeiz left23:01
multi_io left23:02
multi_io joined23:03
btree left23:05
diegoviola joined23:06
D-Boy joined23:06
druidd joined23:07
ASOLAr left23:08
adgtl_ left23:08
ilmgb joined23:10
allcentury joined23:11
m0ltar left23:11
cagedwisdom left23:12
ilmgb left23:14
fracting joined23:14
nerium left23:15
nerium joined23:16
Padawan joined23:19
rockstar_ left23:19
fracting left23:19
rockstar__ left23:20
prefixed left23:20
yqt left23:20
paul424 left23:23
Guest48 joined23:24
cagedwisdom joined23:24
cbonobo left23:26
WaReZ joined23:28
druidd left23:28
otter768 joined23:29
jasom joined23:30
hexagoxel left23:30
cdown joined23:30
jasom I ran out of disk space during a repack; how do I clean up my .git directory?23:30
phroa man git fsck man git gc man git clean depending on definitions of "clean"23:31
gitinfo the git-fsck manpage is available at http://jk.gs/git-fsck.html23:31
the git-gc manpage is available at http://jk.gs/git-gc.html23:31
the git-clean manpage is available at http://jk.gs/git-clean.html23:31
jasom phroa: thanks23:31
hexagoxel joined23:31
fracting joined23:33
otter768 left23:34
Kallis left23:36
jasom phroa: hmm, that still seems to leave tmp_pack* files around, is it safe to delete those?23:36
AaronMT left23:37
phroa I don't think I'm qualified to answer that23:37
Eugene I say go for it, but I'm a bit reckless23:37
allcentury left23:37
jasom I have another clone of the repo elsewhere, so not a big deal if I lose it23:37
Eugene If you get missing objects, just fetch23:37
r4zz joined23:37
tjm_jimmy left23:38
Eugene Yup. git doesn't care if half the repo is missing, it'll figure ito ut23:38
NeckBeardPrince joined23:38
tjm_jimmy joined23:38
bishopj left23:41
tachoknight left23:41
bishopj joined23:42
dsdeiz joined23:42
dsdeiz left23:42
dsdeiz joined23:42
nettoweb joined23:42
snowcycle left23:42
WaReZ left23:43
rarepreppe joined23:44
jml32ljl2 left23:44
asfdfdfd_ left23:44
kpease left23:46
s00pcan left23:50
s00pcan joined23:52
tjm_jimmy left23:52
the_cybersphinx left23:52
cdown left23:53
GoddeR left23:53
NeckBeardPrince left23:54
pratikmallya left23:55
r4zz left23:56
the_cybersphinx joined23:56
oojacoboo left23:56
Star_ joined23:58
fstd left23:59
fstd joined23:59

Logs Search ←Prev date Next date→ Channels Documentation