IRCloggy #git 2015-10-07

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

m0ltar joined00:00
calamari but it doesnt push the change00:00
cspotcode joined00:00
andersoldahl joined00:00
calamari ah I found a stackoverflow.. git push --delete is the only option for now00:00
or git push origin :branchname00:01
cdg left00:01
Eugene That's what the bot factoid says, too ;-)00:01
And :branch is just a cheaty non-obvious syntax00:02
cdg joined00:02
calamari ah -rd is just deleting the tracking branch00:02
that makes sense00:02
howitdo joined00:02
howitdo left00:02
howitdo joined00:02
m0ltar left00:02
howitdo left00:03
calamari well bummer, this means I need to support auth in my app, was hoping to avoid it :)00:03
howitdo joined00:03
Oog left00:04
oojacoboo left00:05
sfan786 left00:06
d4rklit3 joined00:06
d4rklit3 hi00:06
what is the command to push to a remote and completely nuke whats there00:06
and replace it with my local repo00:06
cdg left00:07
oojacoboo joined00:07
ojacobson There isn't exactly one00:08
strayPuppy joined00:08
ojacobson You can approximate it by force-pushing with --mirror, but read man git-push _in detail_ first00:08
gitinfo the git-push manpage is available at http://jk.gs/git-push.html00:08
strayPuppyGuest7883100:08
Guest78831 left00:09
oojacoboo left00:09
andersoldahl left00:09
AaronMT left00:09
jteneyck left00:09
andersoldahl joined00:09
oojacoboo joined00:11
m0ltar joined00:11
s8321414 left00:11
whitby left00:11
lewellyn joined00:11
mingwandroid_ joined00:12
sulky joined00:13
oojacoboo left00:14
mingwandroid left00:14
skasturi joined00:14
oojacoboo joined00:15
andersoldahl left00:15
lewellyn left00:16
paulweb515 left00:16
zumba_ad_ joined00:17
Padawan left00:17
zumba_ad_ left00:17
daito joined00:17
Celelibi Is there a syntax to denote the descendent commit of a given commit?00:18
eka joined00:22
daito left00:22
anth0ny left00:22
anth0ny joined00:23
dreiss left00:23
calamari Celelibi: what do you mean by denote? do you mean tag?00:23
Padawan joined00:23
Celelibi I mean HEAD~ is the ancestor of HEAD.00:24
I would like to do the opposite.00:24
fordcars joined00:24
jonmorehouse left00:26
lewellyn joined00:26
calamari see if this gets you close: git branch --contains COMMIT00:26
wymillerlinux left00:26
eka left00:27
Celelibi Not really.00:27
I want to compile and test every commit I made.00:28
modocache joined00:28
Celelibi I could do it by going backward in time. Always checking out HEAD~ but I prefer to do it the other way.00:28
fordcars left00:28
mwhooker_ left00:29
nanga left00:29
jmpp left00:29
nicechap left00:29
nKulo joined00:30
sfan786 joined00:30
whomp joined00:30
royalty joined00:31
tomog999_ joined00:31
royalty hello00:31
nanga joined00:32
nanga left00:32
nanga joined00:32
sfan786 left00:32
royalty so me and a coworker both were working on the same thing, we had a remote repo we were both pulling from pushing to00:32
modocache left00:32
whomp so i put a sensitive key into my code by accident, did a git add, then removed the key. now, when i do a git diff, it shows me some red lines with the key, indicating that i deleted it, but this file didn't exist in the previous commit! how does git store this information, and if i commit and push, will it cause problems?00:32
if i do a git rm, will that fix the issue?00:32
lewellyn left00:33
royalty one time after pulling, i saw that a lot of changes of mine were undone00:33
diogenese left00:33
royalty i know my changes were pushed remotely first though since there was record of it00:33
diogenese joined00:33
royalty it showed he had "merged" the remote repo with his00:33
tomog999 left00:34
royalty in a merge what exactly happens00:35
if the merge had caused me to lose all my changes after a pull, what could that mean?00:35
i reverted my repo to an earlier commit but now am "2 commits behind origin/master"00:36
i got annoyed and created a new branch and force pushed my current repo there00:36
wad left00:36
mwhooker joined00:37
jonmorehouse joined00:37
znabavi left00:37
hck89 left00:37
znabavi joined00:38
stantonk left00:41
nicechap joined00:42
Joseph_Silber left00:44
Joseph_Silber joined00:45
mellernoia left00:45
imachuchu left00:46
mwhooker left00:46
gopar left00:46
willardg joined00:47
boombatower joined00:48
hyperair left00:48
sfan786 joined00:49
Hello71 left00:49
LaptopBrain left00:49
jteneyck joined00:50
harish_ left00:50
snthsnth left00:51
LaptopBrain joined00:52
Hello71 joined00:52
d10n-work left00:52
linuxmint2 joined00:52
geek joined00:53
geek I changed my home username and now git says fatal: '/home/test/build/wine-git/wine-git' does not appear to be a git repository when (git pull origin), how can I update the user?00:55
jonmorehouse left00:55
duckmaestro left00:56
whomp left00:57
eka joined00:58
geek left00:58
eka left00:58
sfan786 left00:59
redabhr joined01:01
jteneyck left01:01
redabhr left01:02
whomp joined01:02
gfixler left01:02
whomp so i put a sensitive key into my code by accident, did a git add, then removed the key. now, when i do a git diff, it shows me some red lines with the key, indicating that i deleted it, but this file didn't exist in the previous commit! how does git store this information, and if i commit and push, will it cause problems?01:02
further, i see that git seems to know about this key because it shows up in git diff, but when i grep for a section of the key in the .git folder, i don't get any matches. is this simply because git compresses things? is there any way to determine if a string exists in git history?01:03
Vampire0_ joined01:03
royalty left01:04
LaptopBrain left01:04
jonmorehouse joined01:05
hyperair joined01:05
andersoldahl joined01:05
Vampire0 left01:06
ahr3n_ joined01:09
LBV_User left01:10
Noldorin joined01:10
jmpp joined01:11
maletor left01:11
maletor joined01:11
jonmorehouse left01:12
ahr3n left01:12
leeN left01:13
User458764 joined01:14
heroux joined01:14
m0ltar left01:14
Remram left01:14
CMOTD joined01:15
CMOTD left01:15
Atrumx joined01:16
jmpp left01:16
Remram joined01:16
daito joined01:16
Remram left01:18
hyperair left01:18
rchavik joined01:18
User458764 left01:18
mingwandroid_ left01:18
maletor left01:19
BullHorn joined01:21
harish_ joined01:22
BullHorn anyone got a guide on how to use git? what i mean is when to branch out, when/why to merge branches, whats the release feature and how to use it01:22
i usually just do basics of adding/committing/pushing/pullrequesting/fetching/merging01:23
sssilver joined01:24
Remram joined01:24
stantonk joined01:25
Motoko joined01:26
lewellyn joined01:27
dinobytes joined01:27
ojacobson !workflow !flow !githubflow01:28
gitinfo 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.01:28
[!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/references01:28
[!github_flow] This is the workflow followed by github: http://scottchacon.com/2011/08/31/github-flow.html01:28
SimonNa joined01:29
mikeBr left01:30
oojacoboo left01:32
jteneyck joined01:33
oojacoboo joined01:33
zumba_ad_ joined01:33
moreirapontocom joined01:36
vikas027 joined01:38
harish_ left01:38
dstarh joined01:39
moreirapontocom left01:39
bmilesp joined01:41
yarnfive8 left01:44
foul_owl left01:45
m0ltar joined01:46
Lyqyd joined01:47
pks left01:47
Wulf left01:48
pks joined01:49
dstarh left01:49
jteneyck_ joined01:50
D-Boy left01:50
TomyLobo left01:50
nKulo left01:50
jteneyck left01:52
d4rklit3 left01:53
harish joined01:54
Wulf joined01:55
Thorax left01:55
devoldmx joined01:55
scarabx joined01:57
msonntag left01:57
foul_owl joined01:57
moei left01:58
msonntag joined01:58
zumba_ad_ left01:59
nachoman joined02:00
devoldmx left02:00
leprechau left02:03
Goplat joined02:04
leprechau joined02:04
ValicekB left02:04
s00pcan left02:05
dinobytes left02:06
machan left02:07
rodrigograca31 left02:07
ValicekB joined02:09
cagedwisdom left02:10
MarkyC left02:12
gfixler joined02:12
m0ltar left02:13
m0ltar joined02:14
mizu_no_oto joined02:14
johnnyfive left02:18
impliednude joined02:19
gunnaro joined02:19
snthsnth joined02:19
impliednude how do you update your local copy from a remote git or is there a FAQ in regards to this?02:19
theskillwithin is this a magento repo?02:22
be careful if you are using repo as files for local server, dont want to mess up local.xml and other things you may have done to get working on local vm/server so a reset might be harmful02:23
is your local copy a repo you cloned from the remote git?02:23
tpollard left02:23
theskillwithin if not why not just do a new clone02:24
I recognize you impliednude02:24
showaz joined02:24
theskillwithin =]02:24
you probably know more than me02:24
impliednude nah theskillwithin and I was just looking to be lazy and not worry about conflicts02:25
Roger_ joined02:25
SimonNa left02:25
theskillwithin sometimes I just reclone the whole repo if i get into too much trouble now02:25
dinobytes joined02:25
theskillwithin it used to be everything was soo touchy that i was afraid to do this because of so much setup, weather it be mamp or vagrant. cuz of special server shit02:26
hyperair joined02:26
theskillwithin but now it is getting better idk why haha02:26
kgadek left02:26
theskillwithin so i just reclone sometimes02:26
rename old one, then copy over the files in a new commit02:27
johnnyfive joined02:27
daivyk left02:27
theskillwithin rename old repo, reclone, copy files over from old repo to new and stagecommit*02:27
sagerdearia joined02:28
gunnaro left02:28
sagerdearia How can I search through all commits looking for a specific string that was modified in any file?02:29
nm http://stackoverflow.com/questions/18749211/how-to-find-all-commits-with-a-specific-string-on-the-insertions-and-deletions02:30
\toothrot joined02:30
murgi left02:32
samw joined02:33
jalnt left02:33
bitkiller left02:35
stantonk left02:38
thewoolsinator left02:39
bmilesp left02:40
jnewt left02:42
FIQ left02:42
jmpp joined02:43
watabou joined02:43
lewellyn left02:44
penna_ joined02:47
jmpp left02:48
lewellyn joined02:50
penna left02:51
ajf- left02:51
sid281 joined02:52
Guest63277 joined02:53
sid28 left02:54
marienz joined02:54
watabou left02:56
ahr3n joined02:58
dEPy joined02:58
nowhere_man left03:00
nowhereman joined03:00
indistylo joined03:00
LBV_User joined03:00
ahr3n_ left03:00
andersoldahl left03:04
mizu_no_oto left03:05
skorgon joined03:05
andersoldahl joined03:06
znabavi left03:08
andersoldahl left03:10
znabavi joined03:10
Maple__ left03:11
dEPy left03:12
ome joined03:13
User458764 joined03:14
SpeakerToMeat left03:15
sparetire_ left03:15
Egyptian[Home] joined03:15
Egyptian[Home] hi - i am using git to backup my config files on my 2 servers. i am following the same process on both and one works but the other doesnt; i get "sh: 1: git-receive-pack: not found" - google gave me tips to try but none have worked.. any ideas on what i can try/03:16
?03:16
nachoman left03:17
User458764 left03:18
sssilver left03:19
thewoolsinator joined03:22
Diitto left03:26
jalnt joined03:26
xcesariox joined03:26
darkbasic left03:26
LBV_User Egyptian[Home]: are you trying to push or to pull? seems like you have a broken installation03:27
crisumi left03:27
kegster left03:27
darkbasic joined03:27
thewoolsinator left03:28
crisumi joined03:28
Egyptian[Home] LBV_User: i figured it out - after 2 hours - i notcied i had 2 ssh keys on my git account.03:28
Diitto joined03:28
kegster joined03:28
Egyptian[Home] in my .ssh/authorised_keys file03:28
thanks03:28
dreiss joined03:29
LBV_User ;)03:29
Egyptian[Home] when i wake up i will come back and ask about fast forwards03:29
variable joined03:31
gopar joined03:32
Sasazuka left03:32
sagerdearia left03:33
Egyptian[Home] left03:34
m0ltar left03:34
howdoi joined03:35
Padawan left03:36
Padawan_ joined03:37
oojacoboo left03:37
oojacoboo joined03:38
elote joined03:40
jalnt left03:41
bap1313 left03:42
Xing joined03:43
SpeakerToMeat joined03:43
joako joined03:43
sagerdearia joined03:46
jonmorehouse joined03:46
LBV_User left03:46
Roger_ left03:48
stantonk joined03:49
smaudet joined03:49
durham joined03:53
xudongz joined03:54
strayPuppy joined03:55
thewoolsinator joined03:55
metaory joined03:55
mezod left03:55
devoldmx joined03:56
durham__ left03:56
stantonk left03:56
durham left03:57
metaory on an ubuntu server git not respecting the config file in .ssh/03:59
kp666 joined04:00
devoldmx left04:00
Rym7 joined04:00
thiago joined04:01
devoldmx joined04:01
kermit left04:03
daito left04:03
dEPy joined04:04
zacg left04:07
snowcycle left04:07
variable left04:10
suprano joined04:10
jonmorehouse left04:11
durham joined04:11
durham left04:13
CheckDavid left04:13
durham joined04:13
M4renz left04:13
whomp left04:14
knownasilya left04:15
snthsnth left04:16
blackpajamas joined04:19
ag4ve left04:20
Rym7 left04:20
elote left04:20
jonmorehouse joined04:20
elote joined04:21
joufflu joined04:21
dreiss left04:21
scarabx left04:21
ag4ve_ joined04:22
cagedwisdom joined04:24
znabavi left04:27
znabavi joined04:27
dreiss joined04:27
boombatower left04:27
ahr3n left04:28
jeffreylevesque left04:28
sssilver joined04:29
cagedwisdom left04:31
jonmorehouse left04:32
kermit joined04:32
sssilver left04:33
jonmorehouse joined04:33
faux___ left04:36
ormaaj left04:38
tanath_tanath04:38
lindenle left04:40
psk17_ joined04:40
psk17_ left04:40
dr_bibble joined04:40
sdothum left04:42
cagedwisdom joined04:43
joufflu left04:43
faux___ joined04:43
dr_bibble left04:44
mcbreez joined04:45
gitinfo set mode: +v04:45
mcbreez Is it difficult to get into git contributions? As in contributing to git itself?04:46
jstimm left04:46
mcbreez .04:47
sssilver joined04:47
milki mcbreez: probably04:47
mcbreez: theres already a bar of submitting patches via mailing list04:48
>.>04:48
mcbreez milki: really?04:48
nerd joined04:48
aesinv left04:49
samw left04:49
mcbreez left04:50
Kicer86 joined04:51
Xing left04:52
Guest26865 joined04:52
MechtiIde joined04:55
snowcycle joined04:56
ploopkazoo left04:57
daito joined04:58
jceb joined04:58
samw joined04:59
jmpp joined05:00
snowcycle left05:00
sssilver left05:00
bb010g joined05:00
gitinfo set mode: +v05:00
metaory left05:00
sid28 joined05:00
ploopkazoo joined05:01
sid281 left05:02
lolmac joined05:02
fscala left05:02
ayaz joined05:03
jxete joined05:03
fedexo joined05:03
m0ltar joined05:04
samw left05:04
jxete left05:04
aesinv joined05:04
fscala joined05:05
devoldmx_ joined05:05
jmpp left05:05
devoldmx left05:07
dreiss left05:10
dEPy left05:10
pR0Ps left05:11
\toothrot left05:13
nilg left05:14
_9dan joined05:15
User458764 joined05:15
_9dan Hello, is it actually possible to delete a commit? Basically I want to remove all commits, changes, ect after a certain point05:16
therealGent joined05:17
pR0Ps joined05:17
tmokros left05:18
pantsman- joined05:18
Phoenixz left05:18
milki _9dan: that sounds like just a regular git reset05:19
_9dan: !fixup05:19
gitinfo _9dan: So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!05:19
User458764 left05:20
scarabx joined05:20
tmokros joined05:20
dinobytes left05:21
eli joined05:22
nilg joined05:22
Gamecubic left05:23
_9dan milki: I have tried doing git reset —hard 7a3521e, it seem like it reverted to 7a3521e but the changes are still there and there is still a “Detached HEAD” and “Pending Changes”05:23
milki _9dan: !detached05:23
gitinfo _9dan: 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 !reattach05:23
milki _9dan: changes are different from commits05:24
_9dan What does !detached and !attached mean?05:25
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 !reattach05:25
metaory joined05:25
petersr joined05:26
Lyqyd left05:28
modocache joined05:30
jteneyck_ left05:30
petersr left05:30
zhodge joined05:31
strayPuppy left05:31
Raging_Hog joined05:31
_9dan milki: gitinfo: I don’t understand what you mean be either !detached or !attached05:32
gitinfo milki: 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 !reattach05:32
strayPuppy joined05:32
multi_io left05:34
modocache left05:34
multi_io joined05:36
willardg left05:36
fracting left05:36
ilmgb joined05:37
jmpp joined05:38
Junior left05:38
Junior joined05:38
zhodge left05:39
_9dan milki: How would I remove pending changes05:39
pantsman- left05:40
lindenle joined05:40
happy-dude left05:41
Manikandan joined05:41
Wetmelon left05:41
milki git status will probably tell you05:41
znabavi left05:43
_9dan milki: git status just lists untracked files05:43
dreiss joined05:44
milki then theres no "pending changes"05:44
i dont know what you are referring to05:44
bendangelo left05:44
znabavi joined05:44
lindenle left05:45
willardg joined05:46
Nick-S joined05:46
_9dan I meant to say pending commits, i have its hash but i just cant figure out how to remove it05:48
jrahmy left05:48
jrahmy joined05:48
scarabx left05:50
_9dan Been at this for 3+ hours reading though the documentation05:50
ThomasLocke joined05:51
milki _9dan: if the hash has no references to it, then it will be deleted in the next gc. you can manually run git gc if you want05:52
_9dan: by default, objects dont get gc'ed for 2 weeks05:53
_9dan milki: git gc didnt remove it05:54
milki _9dan: you need to tweak the settings05:55
showaz left05:55
milki _9dan: man git gc, see prune05:55
gitinfo _9dan: the git-gc manpage is available at http://jk.gs/git-gc.html05:55
sandGorgon joined05:55
milki _9dan: if its still reachable by other branches and tags, it wont be removed05:55
_9dan: and reflog05:55
_9dan Thank you for the help05:56
aesinv left05:57
milki _9dan: an excert from !sensitive has the right flags05:57
gitinfo _9dan: [!filter_sensitive] You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/articles/remove-sensitive-data/05:57
milki git reflog expire --expire=now --all05:57
git gc --prune=now05:57
from step 905:57
eGGsha joined05:57
thiago left05:58
Ceber left05:58
neanderslob joined05:59
mostlybadfly left05:59
fracting joined05:59
_9dan That worked05:59
m0ltar left05:59
skorgon left06:00
CalimeroTeknik joined06:00
thiago joined06:00
sandGorgon left06:00
samw joined06:00
gopar left06:00
Motoko left06:01
Saturn812 joined06:01
ilmgb left06:02
rscata joined06:02
neanderslob__ joined06:02
neanderslob__ left06:02
ilmgb joined06:04
Vgr left06:04
zoso joined06:04
ilmgb left06:04
Vgr joined06:04
Vgr left06:04
Vgr joined06:04
boombatower joined06:05
samw left06:05
willardg left06:05
Pseudocrat left06:05
fedexo left06:05
Ceber joined06:07
PCatinean joined06:07
MechtiIde left06:08
CEnnis91 left06:08
User458764 joined06:09
arup_r joined06:09
[cust] left06:09
pR0Ps left06:11
pR0Ps joined06:12
TomyLobo joined06:12
sandGorgon joined06:12
foul_owl left06:12
Ryanar left06:12
moei joined06:13
thewoolsinator left06:13
ckruczek joined06:13
therealGent left06:13
Vgr_ joined06:13
foul_owl joined06:13
Vgr left06:14
ahr3n joined06:16
calamari left06:16
acolson joined06:16
[cust] joined06:16
courrier_ joined06:17
nerd left06:17
ome left06:20
courrier left06:20
eli` joined06:21
eli` left06:21
freimatz joined06:22
Guest63277 left06:22
Guest63277 joined06:22
Guest63277FIQ06:22
dionysus69 joined06:22
arunbhawna joined06:22
nerd joined06:23
indistylo left06:24
aruns23 joined06:26
arunbhawna left06:29
azuri5 joined06:29
nnyk_ left06:29
thiago left06:31
znabavi left06:33
rubyonrailed joined06:35
leeN joined06:38
wwwald joined06:39
benbergman left06:40
rubyonrailed left06:40
benbergman joined06:40
TomyLobo left06:41
jceb left06:41
dreiss left06:44
gfixler1 joined06:45
nnyk_ joined06:45
tuor joined06:46
benbergman left06:46
impliednude shouldn't git add * actually add all files that were added to the project?06:47
benbergman joined06:47
IanV0rn2341 joined06:48
pm90_ joined06:49
User458764 left06:51
goTAN joined06:52
osse impliednude: no. the shell takes care of turing * into a list of files.06:53
git adds those, if they're not ignored06:53
milki what does "added to the project" mean o.O06:53
Sceorem joined06:55
gua_ould joined06:56
dionysus69 left06:56
tuor Where do I find documentation about 'HEAD^^' or 'HEAD..' or 'HEAD"whatever"'? I just want to know how this HEAD stuff works.06:57
milki tuor: thats man gitrevisions06:57
gitinfo tuor: the gitrevisions manpage is available at http://jk.gs/gitrevisions.html06:57
znabavi joined06:58
_9dan left06:58
tuor milki, thx.06:59
shadej joined06:59
nnyk_ left06:59
lewellyn left07:00
shadej Hey guys07:00
osse tuor: pro-tip: most (if not all) of the "HEAD stuff" even works when it says something other than HEAD \o/07:00
shadej I create a tag on a branch and switched to a different branch but when run the "git tag" command I still see the new tag, is that expected?07:00
osse yes07:00
tags are "global" in that sense07:00
tags don't belong on branches07:01
shadej okay but I saw somewhere that states "tags are related with a specific commit unless you intentionally move them"07:01
osse that is also true07:01
IanV0rn2341 left07:01
tuor osse, I don't understand what you meen. But maybe I should read the man doc first. :)07:02
osse tuor: yeah, do. What I mean is that the stuff you describe as "HEAD stuff" are more genereal/flexible than you maybe think07:03
shadej osse: if that is true, when I switched to a different branch the commit is not there why is the tag still showing?07:03
znabavi left07:03
osse shadej: i think the misunderstanding is relatived to this: "the commit is not there". What do you mean?07:03
shadej By that I mean the commit is not on the new branch I switched into07:04
The commit the tag is pointing to is not on the current branch07:04
does that make sense?07:04
znabavi joined07:04
osse yup07:04
but it doesn't matter07:05
not sure how to explain it.07:05
SuzieQueue left07:05
cdown joined07:05
arunbhawna joined07:05
osse git branch lists branches that point to commits that "are not there"07:05
shadej okay got it. :-) a new bee07:06
aruns23 left07:07
nilg left07:07
shadej so is there any "git tag branchname" command to show list of tag on a branch07:08
durham left07:08
osse no07:09
but I think someone is working on it07:09
there are commands to do the opposite: list tags that contain a certain commit07:10
(to see which releases are affected by a certain bug for example)07:10
encod3 joined07:10
aruns23 joined07:10
shadej aha, ok thanks07:11
osse: I never used them, I am just starting to use them now07:11
arunbhawna left07:12
mac_ified left07:13
jonmorehouse left07:13
D-Boy joined07:14
scarcry joined07:16
TomyWork joined07:16
nilg joined07:16
lewellyn joined07:17
tuor osse, I see now. There is lot more then only "HEAD stuff". I think I got the idea, but have to use it for realy understanding.07:18
grbe joined07:19
Vgr joined07:20
Vgr left07:20
Vgr joined07:20
pm90_ left07:20
Vgr_ left07:20
codesing joined07:20
mark3 joined07:21
moritz_s left07:23
bond joined07:23
eka joined07:24
wwwald left07:24
wwwald joined07:25
jknetl joined07:25
azuri5 left07:26
Balliad joined07:27
IanV0rn2341 joined07:30
modocache joined07:31
Shentino left07:31
maxorator left07:32
darkbasic_ joined07:33
rishi left07:33
darkbasic left07:34
IanV0rn2341 left07:34
Shentino joined07:34
rishi joined07:34
maxorator joined07:35
modocache left07:35
jceb joined07:35
IanV0rn2341 joined07:35
alienaut joined07:37
jknetl left07:38
darkbasic_ left07:38
darkbasic joined07:40
DWestCoast joined07:41
simesy joined07:41
lindenle joined07:43
raven-au left07:43
syegres joined07:43
simesy left07:43
fracting left07:45
cdown left07:46
EXID123 left07:46
weaksauce left07:46
eka left07:46
aruns23 left07:46
bonswouar joined07:47
EXID123_ left07:47
lindenle left07:47
eka joined07:47
eka left07:47
IanV0rn2341 left07:47
IanV0rn2341 joined07:48
KekSi joined07:49
daito left07:49
raven-au joined07:49
nnyk_ joined07:52
KekSi hi, i'm a total newbie with git and here's my situation (i have no clue about git lingo so the correct words will probably help me a lot in googling): we're switching from svn to git and someone imported the most recent trunk into master - however my (svn) branch and the trunk both have a lot of changes since i branched it07:52
machan joined07:52
KekSi now i disconnected my svn branch and made a new git branch and committed & pushed my changes into it - how do i merge the differences between the two?07:52
kurkale6ka joined07:52
_9dan joined07:53
KekSi what is it called (the two don't have any shared commit stamps/ids in their history)07:54
mikiones left07:57
fracting joined07:57
versa left07:57
ckruczek !merge07:57
gitinfo 'git merge' takes two diverged lines of history (series of commits, e.g. on different branches), and recombines them with a "merge commit" on top. This creates an explicit record of you doing the merge, unless there were no local changes (which does a !fast_forward merge instead). If you don't need to keep a record like that, !rebase may produce easier-to-read history, but the two don't always mix well... see also !merge_vs_r07:57
wrouesnel joined07:58
JanC left07:58
DWestCoast left07:59
cust_ joined07:59
[cust] left07:59
darkbasic left07:59
DWestCoast joined08:00
reim left08:00
m0ltar joined08:00
strayPuppy left08:01
darkbasic joined08:02
m0ltar left08:02
{0xc6} joined08:04
nnyk_ left08:05
alienaut left08:07
Anaunymau5 joined08:07
darkbasic_ joined08:07
marcogmonteiro joined08:07
metaory oh git oh git ,,, i have ssh-agent running, ssh-add rsa, ~/.ssh/config is set proparly ,08:07
tirengarfio_ joined08:07
metaory but it get permission denied08:07
is on remote ubuntu server that i ssh to08:08
gitinfo set mode: +v08:08
bongjovi joined08:08
darkbasic left08:08
Anaunymau5 hi everyone08:08
gitinfo Anaunymau5: 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.08:08
ilmgb joined08:08
devoldmx_ left08:08
ahr3n left08:09
tirengarfio left08:09
osse metaory: does regular ssh work =08:09
alienaut joined08:09
metaory osse, yes08:09
daito joined08:09
Anaunymau5 where do i get the github helmet? Just installed irc to ask that question :P08:09
ilmgb left08:09
metaory same keys setup on my local works fine,08:09
osse metaory: how do you normally ssh? the command08:09
ilmgb_ joined08:09
IanV0rn2341 left08:09
penna_ left08:10
metaory ssh -i ~/.ssh/key08:10
ssh -i ~/.ssh/key user@ip08:10
penna joined08:10
metaory shoudl i do ssh -A to pass my agent08:10
osse so it doesn't say in .ssh/config that ~/.ssh/key should be used for ip ?08:10
filisko joined08:10
User458764 joined08:10
metaory yes config hv the key path08:10
osse so does 'ssh user@ip' work without the -i ?08:11
darkbasic_ left08:11
ahr3n joined08:11
Kartagis Anaunymau5: #github08:11
boombatower left08:11
Anaunymau5 oops sry08:11
metaory no i hvnt setup my local.. the config is on remote server08:11
i want to setup config on server, for git actions08:12
on remote server: ssh -T [email@hidden.address] works fine08:12
darkbasic joined08:12
Guest69018 left08:12
JanC joined08:13
cyphase joined08:13
versa joined08:13
osse if ssh works then git will work.08:13
znabavi left08:14
User4587_ joined08:14
grbe left08:14
znabavi joined08:15
User458764 left08:15
IanV0rn2341 joined08:17
lg188 joined08:19
mquinevilmquin08:19
mkoskar left08:19
jantje any way I can get tag changes in (some) reflog?08:20
I just removed and re-added a bunch of tags, and it would have been nice if that was tracked08:20
groolot joined08:23
groolot left08:23
Suzeanne joined08:26
p4trix joined08:26
oojacoboo left08:27
reim joined08:28
Muntaner joined08:28
Muntaner hey guys08:28
gitinfo Muntaner: 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.08:28
KekSi !rebase08:29
gitinfo 'git rebase' takes away your local commits, updates your branch with new stuff from <upstream> (argument), then re-applies your local commits on top. This makes it look like your commits were created "after" the new stuff, and it can look cleaner than doing a !merge. Beware of !rewriting_public_history, though. Not to be confused with !interactive_rebase.08:29
FabTG_ left08:30
KekSi !rebase_vs_r08:30
!merge_vs_r08:30
gitinfo [!merge_or_rebase] For a detailed discussion of the dis-/advantages of merge and rebase, and when to best use which, see: https://coderwall.com/p/ny1hia -- and here's how Linus explains which one to use: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html08:30
tristanp_ left08:31
Chill_Surf joined08:31
vikas027 left08:31
metaory osse, i feel the config in ~/.ssh/config is not being load at all, the file authorized_keys could be culprit !? or /etc/ssh/ssh_config08:32
bvi joined08:32
jmpp left08:34
adgtl joined08:35
soc42 joined08:36
bvi left08:37
joseph_86 joined08:37
BullHorn left08:37
shadej1 joined08:38
tvw joined08:38
KekSi !interactive_rebase08:39
gitinfo Interactive rebase sounds similar to rebase but has completely different abilities. It can do this to commits: change the order, squash some of them together, remove some, add random existing commits from other branches, split them, and more... it's very powerful. Documentation is in the section "Interactive Rebase" in 'man git-rebase'.08:39
adgtl left08:39
jalnt joined08:39
shadej left08:40
metaory !gitcredentials08:40
gunnaro joined08:41
achadwick joined08:44
joseph_86 left08:44
joseph_86 joined08:45
keroro520 joined08:45
sid281 joined08:46
sarri left08:46
moritz metaory: "man gitcredentials"?08:47
gitinfo metaory: the gitcredentials manpage is available at http://jk.gs/gitcredentials.html08:47
sid28 left08:47
Goplat left08:47
sarri joined08:48
sarri left08:48
sarri joined08:48
fandi left08:49
qsuscs Celelibi: not possible easily. each commit records its parents and that's it. to find the commits that have $foo as a parent, you just have to scan _all_ commits.08:49
bvi joined08:49
qsuscs if you want to do something on certain commits, man git rev-list08:49
gitinfo the git-rev-list manpage is available at http://jk.gs/git-rev-list.html08:49
arup_r left08:50
SpeakerToMeat left08:50
leeN left08:51
jost joined08:51
subscope joined08:51
drbean_ left08:52
onov joined08:52
drbean joined08:53
qwebirc45852 joined08:54
chris64_ joined08:54
jalnt left08:55
gitinfo set mode: +v08:57
qwebirc45852 hello08:57
gitinfo qwebirc45852: 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.08:57
qwebirc45852 I have a quesion about git clean08:57
ckruczek DO IT08:57
I am sorry, I am kind of excited08:58
qwebirc45852 according to manpage git clean: If an untracked directory is managed by a different git repository, it is not removed by default08:58
altough in my env subdir that contains different git repo is deleted if performing 'git clean -dxf' in rootdir that is also a subdir08:59
for now I do not want git submodules for this subrepo08:59
acolson_ joined08:59
reim left08:59
siwyi joined08:59
acolson left08:59
m0ltar joined08:59
m0ltar left08:59
qwebirc45852 correction: in rootdir that is also a subdir > in rootdir that is also a repo09:01
pluffsy joined09:01
qwebirc45852 my setup toplevelrepo/.git ; toplevelrepo/src/subrepo/.git > git clean -dxf deletes 'toplevelrepo/src/subrepo' where according to manpage I wouldn't expect it09:03
saidi joined09:03
saidi left09:03
saidi joined09:03
ixian left09:04
sparetire_ joined09:04
pluffsy Hi! I understand this probably is very basic. I have just switched from hg to git and I have a merging problem. In hg if multiple people made changes in a file and hg couldn’t resolve it I got a merge conflict, now in git I just seem to get a random automatic merge where someones changes are removed. I have gotten a few merge conflicts in git, but more often than not it just make incorrect guesses of how to merge.09:05
fandi joined09:05
ixian joined09:05
bond left09:05
qsuscs pluffsy: in doubt, you can always git merge --no-commit and inspect everything before you commit09:06
neanderslob left09:07
Anticom joined09:07
tristanp joined09:07
sdsd joined09:10
User4587_ left09:10
sdsd git branch -d the_local_branch // should i be standing on master or the locla branch when i do that?09:10
qwebirc45852 you can only dlete branches where not not currently on09:11
so master09:11
and you can force deletion using '-D'-param see manpage git help branch09:11
mkoskar joined09:12
jost left09:12
darkbasic_ joined09:12
darkbasic left09:12
SimonNa joined09:12
jrahmy left09:13
qwebirc45852 according to manpage git clean: If an untracked directory is managed by a different git repository, it is not removed by default09:13
geoid joined09:13
qwebirc45852 altough in my env subdir that contains different git repo is deleted if performing 'git clean -dxf' in rootdir that is also a subdir09:13
alienaut left09:13
jonmorehouse joined09:14
qwebirc45852 correction: in rootdir that is also a subdir > in rootdir that is also a repo09:14
bvi left09:14
Godfather_ joined09:14
Godfather_ hi09:14
sdsd left09:15
fscala left09:15
Godfather_ I want as a default behaviour when i push (git push origin) push to the origin the current branch which matches the origin branch ( testing )09:15
i set "git config --global push.default simple"09:16
SpeakerToMeat joined09:16
{0xc6} left09:16
Godfather_ and now when i try "git push origin" in the testing branch i get "The current branch testing has no upstream branch"09:16
should i set also "git push --set-upstream origin testing" ?09:17
i don't want to mess it up09:17
tobiasvl yes, set that09:17
fscala joined09:18
qwebirc45852 or initially use 'git push -u origin <local_branch_to_push_remote>'09:18
Zariel joined09:19
Godfather_ qwebirc45852, -u means set as default upstream?09:19
qwebirc45852 anyone who could answer my git clean problem ;-)09:20
osse Godfather_: -u and --set-upstream are the same09:20
Godfather_ ok thx you all09:20
_9dan left09:22
cdown joined09:23
arup_r joined09:23
Muntaner left09:25
reim joined09:25
s8321414 joined09:26
mezod joined09:27
linuxmint2 left09:28
goTAN left09:28
User458764 joined09:28
Padawan_ left09:28
fandi left09:29
mikiones joined09:29
Padawan_ joined09:29
jalnt joined09:29
Orbitrix left09:30
jost joined09:30
keroro520 left09:30
jmpp joined09:31
fandi joined09:31
\toothrot joined09:31
modocache joined09:32
rodrigograca31 joined09:32
IanV0rn2341 left09:33
nettoweb joined09:33
daito left09:34
alienaut joined09:34
faux___ left09:35
gunnaro left09:35
vivp joined09:35
jmpp left09:35
modocache left09:36
vivp left09:36
codesing left09:38
s8321414 left09:38
cdown left09:40
s8321414 joined09:40
siwyi left09:41
keroro520 joined09:43
lindenle joined09:45
znabavi left09:45
kgadek joined09:45
harish left09:46
metaory left09:46
jalnt left09:47
metaory joined09:47
keroro520 left09:47
subscope left09:49
znabavi joined09:49
troulouliou_div2 joined09:50
lindenle left09:50
ahr3n left09:50
blahdodo left09:51
adv_ joined09:51
adv_ looking for a git basics tutorial09:51
thiago joined09:51
adv_ suggestions?09:51
nydel07 left09:51
Anaunymau5 left09:54
faux___ joined09:55
Seveas !book09:56
gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable09:56
stamina joined09:57
Suzeanne left09:57
thiago left09:58
saidi left09:58
User458764 left09:58
saidi joined09:58
Zelest joined09:59
faux___ left09:59
Zelest I think the guys/girls who added git-stash should be awared with the nobel-prize..10:00
geoid left10:00
maxorator left10:00
jost left10:00
reim left10:00
devoldmx joined10:01
simesy joined10:01
User458764 joined10:01
maxorator joined10:01
acetakwas joined10:01
Suzeanne joined10:02
acetakwas_ joined10:02
m0ltar joined10:03
sandGorgon left10:04
Vile joined10:05
devoldmx left10:05
saidi left10:07
jost joined10:07
saidi joined10:07
m0ltar left10:07
notenessUniverse10:08
reim joined10:10
kgadek left10:10
\toothrottoothrot10:10
cbreak Zelest: it's just a shortcut for a bunch of commits and reflog manipulation :)10:11
blahdodo joined10:12
_9dan joined10:13
dimi1947 joined10:13
_9dan left10:13
Zelest cbreak, might be, but I love it! :D10:14
_9dan joined10:14
_9dan left10:14
darkbasic joined10:19
darkbasic_ left10:20
nerd left10:21
osse Zelest: which nobel prize ?10:26
_ikke_ peace10:26
wrouesnel left10:26
_ikke_ ?10:26
subscope joined10:26
vurma joined10:27
lb1a joined10:28
osse why not the one in medecine10:28
darkbasic_ joined10:30
darkbasic left10:30
ErKa joined10:31
nilg left10:31
jmpp joined10:32
cdown joined10:33
bremner economics.10:34
daito joined10:35
znabavi left10:35
znabavi joined10:35
denimsoft joined10:35
Telvana left10:36
jmpp left10:36
nilg joined10:36
faux___ joined10:37
User4587_ joined10:37
metaory left10:38
Telvana joined10:38
User458764 left10:38
daito left10:39
adv_ not book..10:39
tutorial10:39
rwb joined10:40
bremner not cryptic words, sentences.10:41
csdc joined10:41
faux___ left10:41
adv_ left10:41
Anticom Hi all. how do i set a default behaviour for "git add --<all|ignore-removal> <path>" ?10:41
csdc left10:42
adv_ joined10:42
adv_ !designers10:42
gitinfo 'Git for Web Designers' is a quick "Who why what when how" on VCS and git: http://www.webdesignerdepot.com/2009/03/intro-to-git-for-web-designers/10:42
adv_ !tutorial10:42
gitinfo A list of interactive git tutorials: http://try.github.com10:42
geoid joined10:42
bremner adv_: man gittutorial10:42
gitinfo adv_: the gittutorial manpage is available at http://jk.gs/gittutorial.html10:42
darkbasic_ left10:43
adv_ nice10:43
thanks10:43
Anticom I couldn't find the appropriate configure option :/10:43
lb1a Anticom, i simply use an alias for thath10:44
that kind of stuff*10:44
Anticom can i alias an existing command? :>10:44
darkbasic joined10:44
Anticom to kind of overwrite `git add`10:44
lb1a Anticom, something along those lines git config --global alias.au 'add -u'10:45
geoid left10:45
lb1a Anticom, no that is not possible10:45
Anticom, is search for the exact same thing :D10:45
i*10:45
Anticom why `-u` i want `-A` :p10:45
lb1a Anticom, just my example :P read between the lines10:45
Anticom, http://githowto.com/aliases10:46
dionysus69 joined10:46
Gonzo89 joined10:46
Anticom lb1a: well i kind of can't belive there's no configure option for that10:46
Vile left10:48
lb1a Anticom, well you config that option in particular10:48
a_l_e joined10:48
lb1a Anticom, man git config -> search for add.IgnoreErrors10:48
gitinfo Anticom: the git-config manpage is available at http://jk.gs/git-config.html10:48
acetakwas left10:48
lb1a Anticom, ah sorry misread, you wanted ignore-removals10:48
sorry10:48
fandi left10:49
acetakwas_ left10:49
platzhirsch joined10:49
platzhirsch Is there a way to print current repository name and or repository owner ?10:49
chris64_ left10:49
platzhirsch I want to get <owner>/<repository> on command line without parsing git remote -v10:49
osse platzhirsch: there is no such thing10:50
ah10:50
lb1a platzhirsch, there is no such thing as a repository owner10:50
CussBot left10:50
platzhirsch oh true10:50
lb1a platzhirsch, you mean remote name?10:50
platzhirsch sorry, I confused Github specific things with Git10:50
antiatom left10:50
reim left10:50
platzhirsch yes10:50
osse you can parse 'git config remote.origin.url' instead10:50
it will be easier10:50
lb1a platzhirsch, what about if there is more than one remote ?10:50
platzhirsch much easier! thanks a lot10:51
CussBot joined10:51
platzhirsch lb1a: problematic I guess, but doesn't apply in my case10:51
lb1a git config remote.origin.url10:51
ok10:51
sorry osse did it already10:51
Anticom lb1a: i want the --all option as default and not --ignore-removals. You are refering to --ignore-errors which is a different option i'm afraid10:51
lb1a Anticom, i said that above. sorry i misread ignore-*10:51
gfixler1 left10:52
Anticom oh i see10:52
why does git want me to supply either of those flags every time i do git add... doesn't seem very git-like not being able to set a default in a config10:52
albel727 left10:53
SuzieQueue joined10:53
cdown left10:55
_ikke_ Anticom: Options get added after people either use it theirselfs, or someone requests it and isn't found unreasonable10:56
Anticom _ikke_: but usually git tells you right away what option can be used to set a default value so you don't have to specify it every time10:57
_ikke_ Anticom: And especially experienced people, rarely use git add --all10:57
Anticom that's how i remember new features being introduced in the past10:57
Suzeanne left10:57
_ikke_ Anticom: I think you can understand not every parameter has a config option10:58
Nizumzen joined10:58
Anticom _ikke_: because of eventual overhead?10:58
or what's the reason?10:58
goTAN joined10:58
_ikke_ Development overhead, too many options to configure10:58
mizu_no_oto joined10:58
dionysus69 left10:59
Anticom No offense but IMHO `git add` is probably one of the most frequently used git commands. So i figure it would be great being able to set a default value for --all|--ignore-removal10:59
osse use commit -a and be happy11:00
lb1a Anticom, as i said, the alias offers a quite good workaround for that, but for obvious reasons it cannot override the git add command11:00
osse well, happy enough11:00
lb1a osse, have a cookie and be happy too :D11:00
lindenle joined11:01
m0ltar joined11:01
m0ltar left11:02
acetakwas joined11:03
lindenle left11:05
denimsoft left11:05
terminal_echo left11:05
CatKiller joined11:06
denimsoft joined11:06
CatKiller Hi! I have delete a branch on a remote repo. I had never checked out this branch locally, but I somehow can't delete it from the internal refs and it always shows if I use "git branch -a"11:06
Is there a way to delete an unchecked branch>?11:07
lb1a CatKiller, git branch -rd <branchname>11:07
-r for remote -d for delete11:07
CatKiller Ahhhh11:07
osse does that work? o_O11:07
CatKiller thanks, somehow this was hard to google as it kept giving me results for untracked changes11:07
lb1a osse, just the local ref11:08
CatKiller That works! :)11:08
osse lb1a: yeah that's the part I wondered about :P11:08
acetakwas left11:08
CatKiller Yes of course it doesn't do anything on the remote (I haven't pushed)11:08
but that's great11:08
osse CatKiller: in general if you don't know whether one or more branches have been deleted, but you want them deleted locally if that's the case, then git fetch --prune11:08
Godfather_ left11:08
lb1a osse, i read it like he already deleted it on the server, but wants to get rid of the local ref11:08
CatKiller I wonder if I had not deleted the branch on remote and I did "git brand -rd <branchname>; git push"11:08
whether it would then delete11:09
osse CatKiller: and of course you can use that if you deleted it yourself11:09
CatKiller lb1a: That's exactly what I wanted to do11:09
lb1a CatKiller, no it wouldn't11:09
osse CatKiller: it wouldn't11:09
CatKiller osse, lb1a: good to know11:09
vurma left11:09
lb1a CatKiller, git push --delete <remote> <branch> would delete it11:09
znabavi left11:11
CatKiller lb1a: Yep, it makes sense: it's not because I don't have a remote ref that it needs to be removed from the remote necessarily11:11
explicitely deleting remote is the only way to go11:11
And I doubt git even keeps track of what remote branches refs I deleted locally apart from just clearing it locally11:12
Zariel left11:12
CatKiller it's well done :)11:12
antiatom joined11:12
chris64_ joined11:13
osse CatKiller: if you delete a remote ref locally then git fetch will bring it back11:13
CatKiller: if you delete a ref remote then git fetch --prune will get rid of it locally11:13
And that's all I have to say about that.11:13
CatKiller osse: Interesting. So --prune here will prune what I don't have11:13
Actually that's *great* to know11:14
osse no it prunes what you do have that you shouldn't have11:14
Zariel joined11:14
CatKiller when pulling the Linux Kernel I usually only want a few branches and it keeps polluting my branches after a pull11:14
Thanks for the tip11:14
it will be useful11:14
:)11:14
malukenho joined11:16
cavallari joined11:16
User4587_ left11:16
znabavi joined11:17
PsuzeannePsy joined11:17
ErKa left11:19
harish_ joined11:19
jokajak`jokajak11:20
jeffreylevesque joined11:20
dsdeiz left11:21
SuzieQueue left11:21
ggVGc left11:21
albel727 joined11:22
a_l_e left11:22
rnsanchez joined11:24
dionysus69 joined11:27
arup_r left11:28
jeffreylevesque left11:29
ErKa joined11:30
arup_r joined11:30
Raging_Hog left11:31
chris64_ left11:32
modocache joined11:33
platzhirsch So this alias opens nicely the latest commit in GitHub alias clc="git show && sensible-browser https://github.com/$(git config remote.origin.url | awk -F '(:|\\.git)' '{ print $2 }')/commit/$(git rev-parse HEAD)" but I am getting now warnings in non-git direcotires11:33
fatal: Not a git repository, any ideas how to wrap this in a check or so?11:33
_rgn platzhirsch: have you tried hub?11:33
https://github.com/github/hub11:33
Suzeanne joined11:33
arup_r left11:34
_rgn hub browse -- commit/HEAD11:34
platzhirsch ah interesting11:34
oh :)11:34
_rgn hub pull-request is also very useful11:35
thiago joined11:35
Dro__ joined11:35
m0ltar joined11:37
Fingolfin joined11:37
modocache left11:37
Fingolfin left11:37
simesy left11:37
arup_r joined11:37
subscope left11:37
simesy joined11:37
arup_r_ joined11:38
Sceorem left11:38
chris64_ joined11:39
Zariel left11:39
cdown joined11:40
Vile joined11:40
thiago_ joined11:41
arup_r left11:42
Zariel joined11:42
goTAN left11:43
saidi_ joined11:43
thiago left11:44
mostlybadfly joined11:45
saidi left11:45
affa09 left11:45
LBV_User joined11:46
dionysus69 left11:46
Maple__ joined11:46
devoldmx joined11:47
dionysus69 joined11:47
saidi__ joined11:47
saidi_ left11:50
alienaut left11:50
Anticom Concerning git submodules: I'm having kind of a wrapper project which has its own repo and i've added openntp as submodule. now i want to modify the openntpd sources. i created and checked out a new branch for it and did some modifications11:50
question now is: do i have to add+commit the changes in the submodule seperatley or is it sufficient to add+commit in my "wrapper project"?11:50
nnyk_ joined11:51
devoldmx left11:51
LBV_User Anticom: you need add and commit in both11:53
Anticom: in the submodule path to commit you changes to the source code11:53
Anticom LBV_User: okay thank's. Do i need to familiarize myself with "git submodule <...>" aswell in order to work properly with it?11:53
LBV_User and in the master repository to update which commit that submodule must use11:53
sdothum joined11:53
reim joined11:53
Anticom or is this considered "advanced stuff" ?11:53
denimsoft left11:54
lolmac left11:54
LBV_User Anticom: I've been using submodules for 2 years, and add, foreach and update --init are the only commands I had to use so far11:54
bitkiller joined11:56
Zariel left11:56
bijan_ joined11:57
dimi1947 left11:58
bijan_ Hi I want my ubuntu server to push to a git repo in a script. Unfrotunately the script runs as superuser. How to tell git push to user a specific ssh key?11:58
Hi I want my ubuntu server to push to a git repo in a script. Unfrotunately the script runs as superuser. How to tell git push to use a specific ssh key?11:59
fstd left11:59
bijan_ user should mean use11:59
sry11:59
lb1a bijan_, use a host entry in the ~/.ssh/config file ?11:59
tvw left11:59
fstd joined11:59
bijan_ lb1a: but then it is depending on the host and not on the user on the server, right?11:59
Godfather_ joined12:00
Sceorem joined12:00
bijan_ Do I have to create a ssh key for root?12:00
kgadek joined12:00
bvi_ joined12:00
bvi_ left12:00
Anticom bijan_: i guess you could prefix the "git push" with su / sudo <user> ?12:00
just as an alternative12:00
bijan_ I also tried to switch to https but I enabled two factor auth on bitbucket and it wants ssh12:00
Anticom assuming it's a shell script of course :)12:01
bijan_ Anticom: yes it is a shell script that is run as a cron job as root12:01
lb1a bijan_, ? you have a script that should push to a bitbucket repo?12:01
RaceCondition joined12:01
bijan_ lb1a: yes it makes sql backups12:01
and the sql files are versioned12:02
Anticom bijan_: "sudo -u <user> git push"12:02
bijan_ Anticom: I guess that is the solution!12:02
Anticom just try it. if it fails come back :)12:02
lb1a bijan_, either what Anticom said, or write the bitbucket credentials (username keyfile) in the ~root/.ssh/config12:02
bijan_, like that : https://paste.fedoraproject.org/275826/21925114/12:02
bijan_ Anticom: yeees works12:03
Anticom bijan_: sometimes comming up with simple/obvious solutions is a real art ;)12:03
lb1a Anticom, do you use cron for that?12:03
Anticom i've found myself often enough spinning arround and going further and further down the rabbit hole12:03
lb1a ah i meant bijan_12:03
bijan_ Anticom: yes indeed... I slapped myself because this was supposed to be obvious :D12:04
{0xc6} joined12:04
Anticom you're welcome :>12:04
lb1a bijan_, the /etc/crontab enables you to specify the username that should be used to execute the script ...if you're using cron12:04
subscope joined12:05
xcesariox left12:06
bijan_ lb1a: good point but I wanted the script to run as root cause I access stuff like /etc/mysql/debian.cnf12:06
lb1a bijan_, i see. i hope you have an errorhandling in place, if the push fails ;)12:06
bijan_ lb1a: not yet12:07
tvw joined12:07
lb1a bijan_, maybe have a look at bup. a backup tool that uses the git packformat12:08
bijan_ this is the script: https://gist.github.com/tschundeee/f1910dbb6500d7d7d21d12:08
Stummi joined12:08
darkbasic_ joined12:09
darkbasic left12:10
qsuscs platzhirsch: try https://github.com/seveas/git-spindle instead. it’s better.12:10
noisebleed_ joined12:10
lb1a bijan_, yeah it's a simple straight forward approach. used such things myself. but the stuff that applies to deployment in some cases apply to backup as well. i mean the parts where you cannot determine the state of the repo if something to push in a script12:11
{0xc6} left12:11
lb1a maybe have a look at the !deploy comments12:11
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.html12:11
geoid joined12:12
bijan_ lb1a: cool12:12
jeffreylevesque joined12:12
nilg left12:13
bijan_ lb1a: I see the script still has problems with the ssh password prompt12:13
alcohol who uses ssh password prompts, lel12:13
lb1a bijan_, scripts with human interactions is a common fail ;)12:13
bijan_ I used yes password | git push12:14
cagedwisdom left12:14
bijan_ but somehow it still asks GGRRR12:14
alcohol why do you assume that would work?12:14
lb1a bijan_, create a seperate keypair for the backup script, add it to the bitbucket repo with push rights and leave it without a password...12:15
elote left12:15
lb1a ah no, you are using the same user for the push, that wont work -.-12:15
bijan_ lb1a: so I create a keypair without password for root?12:16
qwebirc45852 left12:16
lb1a bijan_, i'd do so, and you could avoid the sudo part for the push as well12:16
youngbaks joined12:16
lb1a bijan_, but i'm not sure if that's a good way12:16
bijan_ lb1a: at least sounds good12:17
lb1a bijan_, not really. if the root user creates new stuff in your local repo (maybe new refs or something like that) your normal user probably will fail to read/edit that because of permissions issues12:18
bijan_ normal user doesn't have to read the sql backups12:18
just dumb backup files stored in /var/backup/mysql/..12:18
lb1a bijan_, then why the sudo in the first place? only for the github credentials?12:18
Ryanar joined12:18
lb1a s/github/bitbucket/12:19
bijan_ :)12:19
chris64_ left12:19
denimsoft joined12:19
dsdeiz joined12:19
s00pcan joined12:20
astrofog joined12:20
kgadek left12:20
bijan_ lb1a: you mean the script doesn't have to run on root level?12:20
jmpp joined12:21
saidi__ left12:21
thiago_ left12:21
saidi__ joined12:22
platzhirsch qsuscs: really nice, if you make full use of it12:24
mizu_no_oto left12:24
jmpp left12:26
jalnt joined12:26
Dro__ left12:27
smaudet left12:27
xcesariox joined12:28
Gamecubic joined12:28
rasto left12:29
nerd joined12:31
thiago joined12:33
MaceBewley left12:34
the_cybersphinx left12:35
Anxi80 joined12:35
CEnnis91 joined12:36
lb1a bijan_, no i meant the part where you called the git push with the sudo gituser thing is kind of strange if the gituser doesn't has access to the repo12:36
(local repo)12:36
fracting left12:37
eliasp left12:37
astrofog left12:37
bijan_ lb1a: yes I removed it and added ssh certs to root user. now it is not necessary12:37
lb1a bijan_, ok12:37
sgambino joined12:37
Ryanar left12:38
aesinv joined12:38
the_cybersphinx joined12:39
MarkyC joined12:39
youngbaks left12:39
alienaut joined12:39
eliasp joined12:39
mellernoia joined12:40
mbrzuzy joined12:41
murgi joined12:41
Manikandan left12:41
Zariel joined12:42
macabre joined12:42
Zariel left12:42
rasto joined12:42
Zariel joined12:42
Zariel left12:43
tinajohnson joined12:43
islalobo joined12:43
Zariel joined12:43
Anxi80 left12:44
darkbasic joined12:44
Anxi80 joined12:44
philophil left12:44
darkbasic_ left12:44
lindenle joined12:44
dstarh joined12:45
paulweb515 joined12:46
philophil joined12:47
siwyi joined12:49
DWestCoast left12:49
devoldmx joined12:50
d0p joined12:51
machan left12:52
pluffsy_ joined12:52
pluffsy left12:52
pluffsy_pluffsy12:52
fracting joined12:53
nerd_ joined12:53
nerd left12:53
jalnt left12:53
moritz_s joined12:53
eliasp left12:53
jost left12:54
devoldmx left12:55
ss1891 joined12:55
fracting left12:55
Gitzilla left12:55
paulweb515 left12:56
eliasp joined12:56
paulweb515 joined12:56
fracting joined12:56
ilmari !book12:58
gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable12:58
halas joined12:58
kgadek joined12:58
nnyk_ left12:58
kgadek left12:59
cdown left12:59
soc42 left12:59
King_Hual joined13:00
tier joined13:00
krawchyk joined13:00
kgadek joined13:00
cbreak left13:01
chris64_ joined13:01
arup_r_ left13:02
cbreak joined13:03
rclanan joined13:04
bsanford_ left13:05
paulweb515 left13:05
gitinfo set mode: +v13:05
adgtl joined13:06
bsanford left13:06
adgtl left13:06
daito joined13:06
smaudet joined13:06
cdg joined13:06
cdg left13:06
cdg joined13:06
rclanan Does anyone have have a good solution or could point me in a good direction on how to checkout the latest tagged commit following semver? For example, say you wanted to check out the latest alpha tag, 1.0.0-alpha13:07
Jackneill joined13:08
liamonade joined13:09
deryni joined13:10
daito left13:11
afuentes left13:11
shambat joined13:12
murgi left13:12
User458764 joined13:12
shambat I have two branches, master and myBranch. I have some new files in master that I want to merge into myBranch, how can I do this?13:12
paulweb515 joined13:13
thiago left13:13
nnyk_ joined13:14
rclanan shambat: git checkout myBranch git merge master13:16
florian^ left13:16
User458764 left13:16
Manikandan joined13:17
darkbasic_ joined13:17
p4trix left13:17
darkbasic left13:18
fxddf joined13:18
florian^ joined13:18
florian^ left13:19
afuentes joined13:20
dimi1947 joined13:20
tristanp left13:20
florian^ joined13:20
florian^ left13:20
florian^ joined13:20
fxddf left13:21
tristanp joined13:21
florian^ left13:21
islalobo left13:21
Anticom left13:22
paulweb515 left13:23
dstarh left13:23
wrouesnel1 joined13:24
rasto left13:24
shinnya joined13:24
machan joined13:24
jackeroo_marc joined13:24
sagerdearia left13:25
florian^ joined13:25
Spacew00t joined13:25
anuvrat joined13:27
MarkyC left13:27
ckruczek I think this autocrlf feature should get deleted in git...i fucking hate this issue maker.13:27
Wulf ckruczek: the whatß13:27
?13:27
nnyk_ left13:28
anuvrat I can clone this private github org repo, but can't run ls-remote on it ... any ideas? https://dpaste.de/zA1113:28
ckruczek Wulf:autocrlf...well actually its not git's fault13:28
I just think, git shouldnt care about this problem.13:28
MarkyC joined13:29
nnyk_ joined13:29
Spacew00t left13:29
Wulf ckruczek: yep, would be better if git wouldn't do any auto conversions...13:30
sagerdearia joined13:30
liamonade left13:30
ckruczek Wulf, My oppinion is, that you/me as a developer should take care of the line-ending problem. so if there are teams with different OS they should configure their IDE to use a common lineending and everything is fine.13:31
or a better option, everybody should use a *nix system :P13:31
Wulf anuvrat: remove trailing /13:31
znabavi left13:32
anuvrat Wulf: okay ...13:32
znabavi joined13:33
genera joined13:33
keroro520 joined13:33
modocache joined13:33
flaguy48 left13:34
anuvrat Wulf: thanks a ton13:34
kaak joined13:34
anuvrat the simplest mistakes are the most irritating ones13:35
:(13:35
scarcry left13:36
algae joined13:36
kaak I'd like to mirror the linux-stable git repository on Bitbucket, but I'm running into size overages (the repo is about 1.2GB).13:36
aesinv left13:36
scarcry joined13:36
kaak What are my options for trimming size if long-term history is not much of a concern13:36
rasto joined13:36
grawity pretty much none13:37
ckruczek left13:37
antiatom left13:37
grawity though you could fork https://bitbucket.org/mirror/linux and see if that still gets rejected by quota13:37
uploading just -stable shouldn't add much13:37
paulweb515 joined13:37
Ankhers left13:38
modocache left13:38
kaak The problem is that I want linux-stable, not the mainline ... I need the bug/security fixes from stable13:38
bijan_ left13:38
Ankhers joined13:38
ilmgb joined13:38
antiatom joined13:38
kaak But I also maintain a very few, small configuration changes. (defconfigs, device tree sources, small changes to the debpackage Makefile)13:39
fracting left13:39
faux___ joined13:39
machan left13:39
davispuh joined13:39
platzhirsch left13:40
kaak So I'm trying to work my way towards a solution that gives me something I can work with.13:40
MarkyC left13:41
ilmgb__ joined13:41
ilmgb_ left13:41
zumba_ad_ joined13:41
whitby joined13:41
Ankhers left13:41
ProbabilityMoon joined13:41
kaak It also feels a bit wonkey and awkward maintaining such a thin layer of changes ontop of such a huge project. Perhaps I'm going about it the wrong way with a fork?13:41
Ankhers joined13:41
tyreld left13:42
ilmgb_ joined13:42
znabavi left13:42
liamonade joined13:43
liamonade left13:43
geoid left13:43
phroa kaak: you could place patchfiles in a repo and apply them to a locally downloaded copy of linux-stable when you need to13:43
faux___ left13:43
Ankhers left13:44
ilmgb left13:44
MarkyC joined13:44
scarcry left13:44
Ankhers joined13:44
geoid joined13:44
scarcry joined13:45
florian^fk13:45
Al1ve joined13:45
dickdaley joined13:45
zumba_ad_ left13:46
ilmgb__ left13:46
ilmgb joined13:46
juril left13:47
dsdeiz left13:48
flaguy48 joined13:48
AaronMT joined13:49
ilmgb_ left13:49
Gitzilla joined13:50
uoi joined13:50
ilmgb left13:51
uoi left13:51
mbrzuzy left13:51
ilmgb joined13:51
fracting joined13:52
chitopunk joined13:53
machan joined13:53
editshare-ericf joined13:54
nerd_ left13:54
nilg joined13:54
azuri5 joined13:54
ixwn joined13:55
cbonobo joined13:55
ixwn left13:55
Milos left13:56
rubyonrailed joined13:56
crose joined13:57
s8321414 left13:57
xtgt joined13:57
bambams left13:58
bambams joined13:58
s8321414 joined13:58
cdown joined13:58
aesinv joined13:59
xcesariox left14:00
xtgt left14:00
bsanford joined14:00
znabavi joined14:00
bsanford_ joined14:00
let joined14:01
krawchyk left14:01
let left14:02
mbrzuzy joined14:02
lfeon joined14:03
lfeon left14:05
znabavi left14:05
vikas027 joined14:05
nilg left14:05
eGGsha left14:06
NotBobDole joined14:07
Leuxo joined14:07
Leuxo left14:07
ozvh joined14:08
ozvh left14:08
linuxmint2 joined14:09
Not_Whatever joined14:09
linuxmint2 left14:10
bsanford_ left14:10
bsanford left14:11
cdown left14:11
jnewt joined14:11
_9dan joined14:11
cdown joined14:12
jnewt left14:12
s8321414 left14:12
jnewt joined14:12
Aioa joined14:12
Dougie187 joined14:12
Aioa left14:13
keroro520 left14:14
keroro520 joined14:14
chris64_ left14:15
ag4ve_ how do i disable the pager in an alias?14:15
cdown left14:15
Noldorin left14:15
zackiv31 joined14:16
cdown joined14:16
User458764 joined14:16
HenriettaSalt joined14:17
Rodya_ joined14:17
MarkyC left14:17
CussBot left14:18
stantonk joined14:18
axl_ joined14:18
chris64 joined14:18
chris64 left14:18
chris64 joined14:18
CussBot joined14:18
Ankhers left14:18
heftig ag4ve_: e.g. git config alias.diffstat "!git --no-pager diff --stat"14:18
Ankhers joined14:19
Sejgd joined14:20
Sejgd left14:20
faux___ joined14:21
m1h4 joined14:21
m1h4 left14:21
keroro520 left14:21
ag4ve_ so ! in alias runs a full command?14:22
codeurge joined14:22
ss1891 left14:22
BBBThunda joined14:23
highcup joined14:23
nnyk_ left14:25
faux___ left14:25
Iuu joined14:25
affa09 joined14:26
Iuu left14:27
davispuh left14:27
chris64 left14:28
WizJin joined14:28
azuri5_ joined14:29
azuri5_ left14:30
victortyau joined14:30
hlwe joined14:31
IrishPrime joined14:31
sanketdg joined14:31
cdown left14:31
azuri5 left14:32
hlwe left14:32
ProbabilityMoon left14:33
pm90_ joined14:33
denimsoft left14:34
denimsoft joined14:35
ncthom91 joined14:35
ncthom91 left14:36
ncthom91 joined14:36
ncthom91 left14:36
noisebleed_ left14:36
ncthom91 joined14:37
ncthom91 left14:37
faux___ joined14:37
tvhf joined14:37
modocache joined14:37
tvhf left14:37
pm90__ joined14:38
moldy joined14:38
moldy hey14:38
https://dpaste.de/RVtw i pulled those 707 commits by accident. how can i throw them away?14:39
phroa git reset --hard origin/master14:39
davispuh joined14:39
Saturn812 left14:39
Godfather_ left14:39
zoso left14:40
noisebleed_ joined14:40
MarkyC joined14:40
moldy phroa: thanks :)14:40
phroa o714:40
dinobytes joined14:40
phroa p.s. that's a lot of unwanted commits14:40
pm90_ left14:40
moldy phroa: it's a project that uses another branch than master as the default branch14:41
acetakwas joined14:41
tiuv joined14:41
faux___ left14:41
tiuv left14:41
acetakwas left14:41
acetakwas joined14:42
phroa mmm14:42
acetakwas left14:42
Alienpruts joined14:42
aard_ joined14:42
Bzwp joined14:42
acetakwas joined14:42
ProbabilityMoon joined14:43
arup_r joined14:43
Bzwp left14:43
xender joined14:43
sid281 left14:44
geoid left14:45
shambat rclanan: thanks!14:45
Milos joined14:45
sid28 joined14:45
geoid joined14:46
dionysus69 left14:46
Walex2 joined14:46
HenriettaSalt left14:46
chris64_ joined14:47
Probabil_ joined14:47
AnalogSuzen joined14:47
Es0teric joined14:47
alienaut left14:47
cbonobo_ joined14:47
aard__ joined14:47
bl4ckpajamas joined14:47
geoid left14:48
rwb1 joined14:48
editshare-ericf_ joined14:49
ProbabilityMoon left14:49
andyrr joined14:49
aard_ left14:49
cbonobo left14:49
theskillwithin left14:49
codeurge left14:49
editshare-ericf left14:49
rwb left14:49
zacts left14:49
andyr left14:49
rwb1rwb14:49
joelsmith left14:49
Uptime left14:49
blackpajamas left14:49
nitrix left14:49
martinklepsch left14:49
dlitz left14:49
Walex left14:49
Eq joined14:49
sid28 left14:50
infiniteturtles left14:50
FIQ left14:50
dreiss joined14:50
machan left14:50
FIQ joined14:50
infiniteturtles joined14:50
zacts` joined14:51
Suzeanne left14:51
devoldmx joined14:51
martinklepsch joined14:51
xender Hi. Is there some guide to efficient and elegant "history post-processing"? :>14:51
joelsmith joined14:51
lvh joined14:51
dlitz joined14:51
_9dan left14:51
xender That is, I have created a lot of commits on a branch named "wip" with intention of cleaning it up later.14:52
And "later" came today.14:52
phroa !sausage and !perfect14:52
gitinfo [!sausage_making] Some developers like to "hide the sausage making", transforming their commits before presenting them to the outside world. See http://sethrobertson.github.com/GitBestPractices/#sausage and !perfect14:52
[!postproduction] So, you want to make your commit history look pretty before pushing? http://sethrobertson.github.com/GitPostProduction talks you through how to use 'rebase -i' to do this.14:52
phroa !rewrite applies to both, of course14:52
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/waqum14:52
rchavik left14:52
phroa though I suspect you don't care about rewriting history on a wip branch :314:52
simesy left14:52
xender phroa: Thanks!14:52
xcesariox joined14:53
gua_ould left14:53
xender Currently one co-worker is working on project and has been warned about my post-processing intentions, so no worries about rewriting :)14:53
Guest6328 joined14:54
aesinv left14:54
rscata left14:55
znabavi joined14:55
gua_ould joined14:55
aesinv joined14:55
devoldmx left14:55
quadz left14:55
keroro520 joined14:55
Noldorin joined14:56
acolson_ left14:56
keroro520 left14:56
Puffball left14:56
Puffball joined14:57
keroro520 joined14:57
aesinv_ joined14:58
akiva joined14:58
quadz joined14:58
sid28 joined14:59
znabavi left14:59
gua_ould left15:00
jonmorehouse left15:00
aesinv left15:00
fedexo joined15:03
xender Hm, does git gc look at object's creation date when determining grace period? Or only on reachability data? (Which of course includes reflog entries with their own expiration date.)15:03
dionysus69 joined15:04
snowcycl_ joined15:04
Thorax joined15:06
daivyk joined15:06
daito joined15:07
bango2 joined15:08
bango2 left15:08
rclanan Does anyone have have a good solution or could point me in a good direction on how to checkout the latest tagged commit following semver? For example, say you wanted to check out the latest alpha tag, 1.0.0-alpha15:08
Sceorem left15:09
bango2 joined15:09
Raging_Hog joined15:09
bond joined15:10
flashpoint9 joined15:10
ojacobson xender: object age for loose objects (see --prune), reflog age and reachability for all objects, and ref reachability for all objects.15:10
Vile left15:11
Raging_Hog left15:11
daito left15:11
machan joined15:11
xender ojacobson: Thank you15:12
denimsoft left15:12
xender So it's 3 months for reflog entries and 2 weeks for dangling loose objects?15:12
denimsoft joined15:12
tier_ joined15:13
ojacobson the defaults are 30 days for reflog entries not reachable from the current value of the ref, 90 days for reflog entries reachable from the current value, 2 weeks for loose objects15:13
The_Phoenix joined15:13
D-Boy left15:13
ojacobson at least as I read it15:13
Manikandan left15:14
angular_mike_ Is there a way to list all tracked files in the order they were changed?15:15
order of files changed in same commits doesn't matter15:15
Zariel left15:15
xender ojacobson: What is the definition of reachability in "reflog entries reachable from current value of ref"?15:16
tier left15:16
grawity the usual one (history DAG), I'd assume15:16
ojacobson yep15:17
krawchyk joined15:17
xender Hm, this way...15:17
ojacobson for the reflog of refs/heads/master, each row is either reachable (if you can find it by walking parents from refs/heads/master) or not (if you can't)15:17
xender So it's mostly for making older reflog entries cleaner or what?15:18
subscope left15:18
rclanan left15:19
xender It seems to be redundant for recovery purposes, because on resetting ref to some random place, all reachable reflog entries with 90 days grace period would degrade to non-reachable ones with 30 days grace period15:20
jonmorehouse joined15:20
xender Then, does git gc autoatically clean up reflog entries themselves or only uses them to determine objects reachability?15:21
onov left15:21
dimi1947 left15:21
znabavi joined15:22
eGGsha joined15:23
noisebleed_ left15:23
snowcycl_ left15:23
pluffsy_ joined15:24
pluffsy left15:24
pluffsy_pluffsy15:24
keroro520 left15:25
jmpp joined15:25
mbrzuzy left15:26
malukenho left15:26
D-Boy joined15:26
znabavi left15:26
dimi1947 joined15:27
settermjd joined15:27
theskillwithin joined15:27
Balliad left15:27
keroro520 joined15:28
subscope joined15:28
dv_ joined15:28
infernix left15:29
lb1a left15:29
ThomasLocke left15:29
scarabx joined15:30
jmpp left15:30
d0p left15:31
sfan786 joined15:31
thinkxl joined15:33
Karkus joined15:34
AAoK joined15:35
malukenho joined15:35
reim left15:36
acetakwas_ joined15:36
mbrzuzy joined15:36
ItSANgo left15:37
The_Phoenix left15:38
Zamyatin joined15:39
settermjd left15:39
antiatom left15:39
islalobo joined15:39
s00pcan_ joined15:40
pluffsy left15:40
fsda joined15:41
The_Phoenix joined15:42
antiatom joined15:42
stickperson joined15:42
PCatinean left15:42
gitinfo set mode: +v15:43
fsda Hi?15:43
gitinfo fsda: 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.15:43
nfk joined15:43
ayaz left15:43
jost_ joined15:44
fsda Is there anyone who help me?15:44
milki fsda: !ask15:44
gitinfo fsda: Yes, it's okay to ask questions here.... in fact, you just asked one! ;-) Pretty much any question is fine. We're not terribly picky, but we might be asleep. Please be patient and you should get an answer soon.15:44
fsda I'm going to update some program in linux15:44
s00pcan_ left15:44
fsda but I'm in introductory level ㅠㅠ15:45
Do you know some plasma simulation code, WARP?15:46
Spacew00t joined15:46
bremner I guess you should ask some scientists about that?15:46
moldy left15:46
fsda But it is some technical problem15:46
ItSANgo joined15:47
fsda in terms of git15:47
skylite joined15:47
bremner ok. then hopefully it doesn't matter what the software does...15:47
jmpp joined15:47
fsda I should update the program15:47
MechtiIde joined15:48
madewokherd left15:48
fsda By the way, I don't know why it don't work in the way indicated by manual15:49
bremner you're not making it easy to help you.15:49
Karkus left15:49
saidi__ left15:49
geoid joined15:49
Probabil_ left15:50
fsda Yes I know15:50
In the manual, written, type 'git pull'15:50
sid281 joined15:51
fsda in some directory indicated15:51
islalobo left15:51
jceb left15:51
fsda but the answer returned is 'error: The requested URL returned error: 403 Forbidden while accessing http://portal.nersc.gov/project/warp/git/warp.git/info/refs'15:53
blackpajamas joined15:53
faux___ joined15:53
sid28 left15:53
fsda Do you know the mean of this comment?15:53
Actually I'm not familiar with both Linux kernel and Git15:54
bremner is that last ' a typo?15:55
fsda Ah15:56
apostrophe ' is not contained in this comment15:57
Actually,15:57
gfixler left15:58
fsda jus15:58
just15:58
WellSaggy joined15:58
fsda error: The requested URL returned error: 403 Forbidden while accessing http://portal.nersc.gov/project/warp/git/warp.git/info/refs15:58
faux___ left15:58
fsda It is the answer of command15:58
wwwald left15:58
fsda command was15:58
git pull15:58
WellSaggy left15:58
bremner and are you certain you have the correct url?15:58
TomyWork left15:59
milki http://portal.nersc.gov/project/warp/git/15:59
islalobo joined15:59
milki theres no warp.git15:59
subscope left15:59
fsda This url is from the developer's repository, bitbucket15:59
ruuda joined15:59
milki should probably be using the bitbucket repository16:00
antiatom left16:00
fsda Is not there?16:00
milki which, in fact, is a git repo16:00
mwhooker joined16:00
mwhooker left16:00
milki fsda: whats not there?16:00
krawchyk left16:00
sfan786 left16:00
rgenito joined16:01
fsda You said to me that theres no warp.git16:01
Alexander123123 joined16:01
fsda Wahts the mean16:01
krawchyk joined16:01
denimsoft left16:01
Alexander123123 left16:01
Psychiatrist joined16:02
milki fsda: i posted a url16:02
bond left16:02
milki fsda: and if you click on it, you'll see warp.git isnt listed16:02
Karkus joined16:02
denimsoft joined16:02
Alexander123123 joined16:02
fsda I see your words16:02
milki fsda: which means the url you posted, isnt a valid url16:03
nasomi joined16:03
bb010g left16:03
ruuda left16:03
syegres left16:03
nasomi could someone tell me the #gitforretards channel16:03
aquiles joined16:04
nKulo joined16:04
acetakwas left16:04
pm90__ left16:04
acetakwas joined16:04
fsda milki: Can you see the page, https://sites.google.com/a/lbl.gov/warp/home/how-to-s/installation ?16:04
acetakwas left16:04
acetakwas joined16:05
acetakwas left16:05
fsda In this page, the part of installing warp, the way of updating warp is listed16:05
zackiv31 left16:06
Noldorin left16:06
chris64_ left16:06
avichalp joined16:07
Gonzo89 left16:08
sssilver joined16:08
sssilver left16:08
stickperson left16:09
editshare-ericf_ left16:09
Noldorin joined16:09
acetakwas__ joined16:10
mikiones left16:11
acetakwas__ left16:12
acetakwas__ joined16:12
ojacobson fsda: the tarball they have you download contains a git repository16:12
acetakwas__ left16:12
ojacobson that repository has a remote (probably "origin", but check git remote -v in that repository) configured16:12
that remote is configured to point to something that's either not a git repo, or a git repo so old modern git can't talk to it16:12
geoid left16:13
ojacobson talk to the people who distribute the software and get them to fix it :)16:13
acetakwas__ joined16:13
fsda Thank you16:13
krawchyk left16:13
milki the remote url in the release points to the bitbucket repo16:13
howdoi left16:13
acetakwas__ left16:14
milki fsda: you should start over from the download step and try again16:14
saidi__ joined16:14
milki fsda: it does say the most recent release16:14
bonswouar left16:14
milki fsda: maybe the older releases arent valid16:14
samw joined16:14
milki fsda: you might be able to just switch the remote16:15
fsda: git remote set-url origin https://bitbucket.org/berkeleylab/warp.git16:15
fsda: git pull16:15
imachuchu joined16:15
madewokherd joined16:16
milki all their releases point to bitbucket16:16
which means they've been on bitbuck for 2 years already16:16
fsda Thank you so much ㅠㅠ16:16
milki either your repo is really old or you changed it16:17
islalobo left16:17
krawchyk joined16:17
Rodya_ left16:18
fsda Oh my god..16:18
It is working !!16:18
Spacew00t left16:19
dimi1947 left16:19
rwb1 joined16:21
aquiles left16:21
chris64 joined16:22
eGGsha left16:22
jmpp left16:22
rwb left16:23
rwb1rwb16:23
droid909 left16:23
achadwick left16:24
faux___ joined16:24
zumba_addict joined16:25
zumba_addict what error did I make? I was in a fix-branch. git stash save "fix" && git checkout master && git pull && git checkout fix-branch && git merge origin/master16:25
w00tner joined16:25
zumba_addict i got a CONFLICT16:26
freimatz left16:26
royalty joined16:26
w00tner hello. i have a repository i want to reuse in a diferent server. i will change some configs like dbs and alter some tables also. Is FORKING the best approach ?16:26
Alexander123123 left16:26
w00tner fork the original project, change name and work there for the other project?16:26
faux___ left16:28
editshare-ericf joined16:30
jackeroo_marc left16:30
keroro520 left16:30
Eugene Sounds like a textbook fork case16:30
ChanServ set mode: +o16:30
avichalp left16:30
kurkale6ka left16:30
yarnfive8 joined16:31
Eugene changed the topic to: Welcome to #git, the place for git help and Yaky Puffs | Current stable version: 2.6.0 | Start here: http://jk.gs/git | Getting "cannot send to channel"? /msg gitinfo .voice | git-fetch: no training required16:31
Eugene set mode: -o16:31
CareBear\ can i haz puffs plz16:31
Spacew00t joined16:31
w00tner no16:31
CareBear\ i sed plz!!16:31
phroa huh?16:31
CareBear\ I am just being noisy16:32
actually I should eat. later!16:32
zumba_addict so I fixed the conflict but now I cannot stash pop it16:33
the file that I fixed is being said as "needs merge"16:33
marcogmonteiro left16:36
scarabx left16:36
faux___ joined16:36
_ikke_ zumba_addict: git add <file>16:36
zumba_addict i did git merge --abort then pop it16:37
now I did the git merge again16:37
fixing conflict now16:37
that should also work right?16:37
i see my changes too16:37
acetakwas_ left16:38
Wetmelon joined16:40
durham joined16:40
faux___ left16:40
durham left16:41
dreiss left16:41
vikas027 left16:41
durham joined16:41
NeckBeardPrince joined16:42
jceb joined16:43
reim joined16:43
whitby left16:44
pm90_ joined16:44
Alienpruts left16:44
aquiles joined16:45
sQVe left16:46
sQVe joined16:46
foul_owl left16:47
reim left16:48
jost_ left16:49
foul_owl joined16:49
pm90__ joined16:49
thomasreggi joined16:49
halas left16:49
keroro520 joined16:50
dinobytes left16:51
devoldmx joined16:51
pm90_ left16:52
zumba_addict left16:52
simesy joined16:53
Darcidride joined16:55
saidi__ left16:55
saidi__ joined16:56
devoldmx left16:56
durham_ joined16:56
duckmaestro joined16:57
stamina left16:57
wrouesnel1 left16:57
odizeuz joined16:58
simesy left16:58
m0viefreak joined16:59
jigjug joined16:59
jigjug left16:59
durham__ joined16:59
durham_ left16:59
durham left16:59
zumba_addict joined17:01
reim joined17:01
d4rklit3 joined17:04
NeverDie left17:04
settermjd joined17:04
saidi__ left17:04
kp666 left17:05
whomp joined17:05
johnnyfive Ok, i'm at a loss. I need a solution to locally cache all repos pulled from outside our company. What solutions come to mind?17:07
milki johnnyfive: clone them?17:07
faux___ joined17:07
reim left17:07
milki johnnyfive: mirror them?17:07
daito joined17:08
FIQ left17:08
encod3 left17:08
aard__ left17:08
denimsoft left17:08
samw left17:08
The_Phoenix left17:08
aard_ joined17:08
geoid joined17:09
Guest87868 joined17:09
aard_ left17:09
kgirthofer joined17:09
settermjd left17:09
johnnyfive Ok, I guess I mean something more transparent. If a dev clones a repo on his box, makes a project, and we deploy said project.. but the git repo it depends on for some reason disappears, and so does his dev copy, we're screwed. I'm trying to create a workflow for making sure that never happens..17:10
Karkus left17:10
fsda I have a question17:11
faux___ left17:11
dinobytes joined17:12
johnnyfive Answers exist17:12
bremner johnnyfive: don't let people deploy from their copies.17:12
daito left17:12
fsda if the command 'git remote set-url origin https://~' don't affect to default set17:12
Psychiatrist left17:13
ankurk joined17:13
johnnyfive bremner| that's not really relevant, since that's not what I said. but ty17:13
snowcycle joined17:13
bremner johnnyfive: why don't you already have the repos that are being deployed?17:14
how is stuff being lost? or how is it possible to lose stuff?17:14
gfixler1 joined17:14
johnnyfive exactly what I said, sometimes repos disappear from github. People delete stuff. It happens17:14
jmpp joined17:15
bremner ah. ok. I missed the external part. sorry.17:15
that's just madness ;).17:15
johnnyfive yes, it's happened a couple times, hence trying to find a solution17:16
bremner so force devs to only use submodules from repos you control?17:17
Guest87868 left17:17
Guest87868 joined17:17
Guest87868FIQ17:17
saidi__ joined17:17
johnnyfive well i'm one of said devs, and we have a solution now. it requires manually mirroring repos in our local git server.. but devs forget.. Dependencies for dependencies change.. etc.. it's just not manageable manually17:18
pantsman- joined17:18
Guest55465tobias17:18
johnnyfive I mean I can't be the only one trying to do this, I get the feeling nobody has a real solution that is automatic17:19
Nevik johnnyfive, so use a caching server?17:19
johnnyfive Nevik| like what? squid?17:19
Nevik no, a git-specific cache17:19
bremner dunno. I'd be freaked if my devs were pulling random stuff from github without any QA or license analysis.17:19
Nevik like a local maven repository17:19
that too17:19
bremner I guess I'm just old fashioned.17:19
Nevik bremner, no you're sane :P17:20
jmpp left17:21
johnnyfive Well I don't live in that world, and even then that doesn't solve the problem.. what if they did it without you knowing? what if it was critical? what if the repo disappeared? that's still not a solution to the problem that exists. That's what i'm getting at17:21
Nevik well, for one thing, everyone who has a clone of said repo has *the entire repo*17:21
stickperson joined17:21
samw joined17:21
Nevik so if it disappears, just push that clone *somewhere* and you're good17:21
johnnyfive Ok, ty for your time, we're just talking in circles now17:21
Nevik (minus fixing all the urls)17:21
Anxi80_ joined17:21
saidi__ left17:22
Nevik not quite, i dont think. you're talking of disappearing repos, which is a thing the distributed nature of git expressly works against17:22
saidi__ joined17:22
noisebleed_ joined17:22
huglester joined17:23
samw left17:23
Nevik johnnyfive, so there are thigns like https://github.com/sitaramc/gitpod and git's --reference support (e.g. see http://randyfay.com/content/reference-cache-repositories-speed-clones-git-clone-reference )17:23
nnyk_ joined17:23
johnnyfive my original question answered your point exactly. What if the dev machine dies? or the dev moves on? or the repo gets deleted on accident on his computer? If you work with data you know that "it's fine if there's a single copy out there" is a bad policy17:23
w00tner left17:23
Nevik (searching for "git caching server" or proxy or something will give you more results)17:23
johnnyfive, buy as a company, you should have a working backup scheme of important data. if your external dependencies are important because you deploy them, they should be part of that17:24
but* as a company17:24
johnnyfive yea, ty Nevik, that was what I was getting at, i've already looked at gitpod and as you can see it was last updated 4 years ago.. which it may or may not work, however I was hoping that there was a more git-specific way to handle this.17:24
What does it look like i'm trying to do...17:24
Nevik hm i thought there was a more ready-made solution for this, but i cant find it right now17:24
johnnyfive Neither can I, hence asking17:25
Nevik basically any big company does this (it's the same idea how maven uses caching proxy repositories)17:25
possibly lots of custom-made solutions17:25
milki sitaram_: johnnyfive thinks gitpod doesnt work because it hasnt gotten updates17:25
johnnyfive Well I am part of a "big" company and we haven't found any solutions that don't require a lot of work on the devs part, which I can't believe.17:25
Anxi80 left17:26
johnnyfive milki| I did not say that17:26
Nevik tbh i dont know how much work it would take, but if it's really that critical to you, you should explore building your own in more detail17:26
_ikke_ johnnyfive: The mailing list has some topics about other big companies running into similar issues17:26
johnnyfive: The git devs know about it, and work for it slowly gets integrated17:26
Nevik it would be mostly setting up a git server in your network, that just clones any repo it doesnt have upon request from github17:26
milki johnnyfive: at $job, we use gitolite and its upstream trigger to mirror all external repos in house17:26
johnnyfive Nevik| we may, it's something we've been thinking about writing if we can't find a solution17:27
milki johnnyfive: and we expressively ensure that all repos point to our mirrors17:27
Nevik milki, i'd be interested in how you check/enforce that17:27
Manikandan joined17:28
fsda left17:28
milki Nevik: nothing literally enforced. we simply dont guarantee it will work if you use an external dependency17:28
Nevik ah17:28
sounds reasonable17:28
milki Nevik: we rely mostly on packaging to pypi and apt repos rather than git checkouts directly17:28
bongjovi left17:28
Nevik ah17:28
i guess that's how i've started to really like using maven17:29
dependency management that works is such a blessing, really17:29
dreiss joined17:29
milki Nevik: luckilly most everyone uses git urls for git repos17:29
kpease joined17:30
milki Nevik: er, ssh urls17:30
Nevik ha17:30
milki Nevik: so our build servers use a key which has limited access17:30
Nevik ah, nice17:30
milki if you touch an external repo, no access!17:30
and then they cry to us -.-17:30
Nevik so the build would fail. nice solution.17:30
and then you point to your guidelines document? :D17:30
milki good point, should write one...17:31
machan left17:31
Nevik "[milki] closed your ticket. Reason: PEBKAC"17:31
samw joined17:31
nnyk_ left17:32
Nizumzen left17:33
milki :P17:33
TomyLobo joined17:33
gancl joined17:34
rubyonrailed left17:34
kpease left17:34
dm7freek joined17:35
Sasazuka joined17:35
smurfsicle joined17:35
monster_ joined17:36
Spacew00t left17:36
kpease joined17:36
monster_ yo bros17:36
time to noob this place up17:36
faux___ joined17:36
dm7freek I made 2 branches off of master: foo and bar. In foo, I made commits A and B, and in bar, I made commits C and D. I want foo's history to look like I did C, D, A, then B. How?17:36
monster_ doing my first pull request,17:36
git request-pull v0.1 https://github.com/OpenBazaar/OpenBazaar-Server.git master17:37
fatal: Not a valid revision: v0.117:37
not sure where I am suppose to get the revision from.17:37
mezod left17:37
dm7freek monster_: probably a tag?17:37
monster_ there is no tags in the project, only master branch17:37
geoid left17:37
dm7freek monster_: use a commit hash?17:38
honestly, i didnt even realize you could start a pr from the cli17:38
thought PRs were a github thing17:38
dzho :)17:38
this is why I tried to learn git before using github17:39
Spacew00t joined17:39
knownasilya joined17:39
dzho so I'd have a better idea as to what comes from which17:39
Milos left17:40
faux___ left17:41
mbrzuzy left17:42
dm7freek monster_: https://git-scm.com/docs/git-request-pull17:42
cbreak a pull request is a request for someone to pull17:42
afuentes left17:42
cbreak a simple "hey, can you pull?" is a pull request17:42
fred1807 joined17:43
dm7freek monster_: "The upstream project is expected to have the commit named by <start>" (i.e. v0.1)17:43
qsuscs though if it's github you may want a github pull request17:43
afuentes joined17:43
fred1807 git's github git https://github.com/git/git17:43
pluffsy joined17:43
qsuscs -> webinterface or e.g. https://github.com/seveas/git-spindle17:43
fred1807: DOES NOT COMPUTE17:44
xcesariox if you wanna learn git the right way, use gitflow, monster_ learn from here https://gist.github.com/shaunstanislaus/622f970ee3589995e76f, dzho .17:45
qsuscs xcesariox: there is no "right way"17:46
xcesariox qsuscs: erm, i beg to differ.17:46
tzero left17:46
xcesariox qsuscs: work flow exist for a reason.17:46
qsuscs xcesariox: !best17:46
gitinfo xcesariox: [!bestway] You want to know the best way to do X? If you can give us a proper definition of "best", we'll give you a proper way to do X ;)17:46
qsuscs xcesariox: gitflow is not bad, but it's certainly not "the right way"17:47
cbreak it's a stupid way that makes stupid assumptions17:47
dzho yeah, I'd avoid git flow early on for the same reason I'd avoid github early on--to steer clear of what I learn being dependent on something that is an extension to git rather than just git itself.17:47
xcesariox cbreak, qsuscs : its a start for novice to try to understand git.17:47
cbreak xcesariox: nah17:47
novices don't need it17:47
qsuscs xcesariox: no. they should learn git first.17:47
Milos joined17:48
cbreak git flow is for teams that work on projects that have a release based workflow (as opposed to CI)17:48
crose left17:49
tzero joined17:49
nfk left17:49
Limes_ joined17:49
troulouliou_div2 left17:50
saidi__ left17:50
King_Hual left17:52
mbrzuzy joined17:52
Orbitrix joined17:53
King_Hual joined17:53
grilled-cheese left17:54
Chill_Surf left17:54
ajf- joined17:55
ajf- Can I exclude a file or pattern from a git diff ?17:55
keroro520 left17:55
malukenho left17:56
malukenho joined17:56
mark3 left17:57
kgadek left17:58
dm7freek I made 2 branches off of master: foo and bar. In foo, I made commits A and B, and in bar, I made commits C and D. I want foo's history to look like I did C, D, A, then B. How?17:58
dspirito joined17:59
matthiaskrgr you can make a new branch and cherry-pick the commits into your target branch one by one18:00
snowcycle left18:00
dm7freek huh... duh! thanks18:00
kpease_ joined18:00
UukGoblin left18:00
UukGoblin joined18:00
matthiaskrgr np :)18:00
dm7freek followup Q: can 2 local branches track the same remote branch?18:00
dm7freek guesses yes18:01
matthiaskrgr should work18:01
just try it :p18:01
dm7freek perfect, sounds like a plan :)18:01
cbreak dm7freek: just git rebase bar18:01
kpease_ left18:01
cbreak (while on foo)18:01
dm7freek cbreak: that will figure it out? i thought that was a job for rebase, but ive only ever used rebase to clean history within one branch18:01
kpease_ joined18:01
dm7freek cool, will try tht first18:02
Amandil joined18:02
livingstn joined18:02
kpease_ left18:02
Nick-S left18:02
kpease_ joined18:03
saidi__ joined18:03
dm7freek beautiful18:03
kpease left18:03
rwb1 joined18:04
znabavi joined18:05
rwb left18:05
rwb1rwb18:05
Balliad joined18:06
faux___ joined18:08
slentzen joined18:08
fracting1 joined18:08
znabavi left18:09
saidi__ left18:09
jceb_ joined18:09
fracting left18:10
rubyonrailed joined18:11
kpease_kpease18:12
faux___ left18:12
jceb left18:12
rubyonrailed left18:13
btree joined18:13
tvw left18:13
Rym7 joined18:14
weaksauce joined18:14
dspirito left18:15
avichalp joined18:15
durham__ left18:15
jackeroo_marc joined18:16
bb010g joined18:16
gitinfo set mode: +v18:16
pluffsy left18:17
AAoK left18:17
tyreld joined18:18
durham joined18:18
encod3 joined18:19
Limes__ joined18:19
mikiones joined18:19
btree left18:20
avichalp left18:21
Limes_ left18:21
rwb1 joined18:21
siwyi left18:21
saidi__ joined18:22
noisebleed_ left18:22
dm7freek cbreak: i rebased, made an additional change on foo, then I did `git rebase -i HEAD~8` and squashed the latest 3 into 1. there are 8 commits listed on my PR now because the hashes changed for 5 common commits that are already in master. (1) why? (2) how do i prevent that? do i just have to do HEAD~3 next time?18:22
zeRez joined18:23
cbreak dm7freek: look at !lol18:23
gitinfo dm7freek: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all18:23
cbreak and compare with upstream18:23
I don't know how your history looks.18:23
moritz dm7freek: it's possible that there was a merge commit in the last 8 commits, and a rebase flattened that out18:23
cbreak pastebin the output if you want to show it to me18:23
kpeasekpease_18:23
moritz dm7freek: which would explain the different sha1s18:23
joki left18:24
smurfsicle left18:24
encod3 left18:24
saidi__ left18:24
zeRez left18:24
saidi__ joined18:25
rwb left18:25
impliednude For some odd reason. I cloned a repository. Changed nothing with the original set except added some new files to the project. I went to merge staging and it said there are conflicts even though I never changed anything with the files they are pointing out.18:25
cbreak impliednude: why merge?18:26
rwb1 left18:26
moritz impliednude: if the upstream project added some of the same files, you can still get a conflict18:26
daito joined18:26
dm7freek moritz: there was def a merge commit... i see now. next Q then: how do i tell git rebase to leave something alone in the editor? just comment out everything?18:26
impliednude nope, none of the same files. I was tasked with developing modules for the system. Which is what the new files were18:26
cbreak dm7freek: if you want to abort, delete every line18:27
dm7freek: if you don't want to change a commit, leave it at "pick"18:27
snthsnth joined18:27
cbreak (it will still change the sha if something before changes)18:27
krawchyk left18:27
Amandil left18:27
madewokherd impliednude: perhaps you're accidentally merging one upstream branch into a different upstream branch?18:27
dm7freek cbreak: ok... so i think at the point i was at the thing to do wouldve been abort and HEAD~3... ty18:28
impliednude maybe *sighs*18:28
Asiajey joined18:28
Asiajey left18:28
Asiajey joined18:28
kpease_kpease18:30
denimsoft joined18:30
rwb joined18:30
joki joined18:30
xcesariox left18:30
chris64 left18:31
Asiajey left18:31
Keridos joined18:31
daito left18:31
jackeroo_marc left18:32
znabavi joined18:32
krawchyk joined18:32
dm7freek left18:32
nydel07 joined18:32
moritz impliednude: if you look at the conflicting files, it should be obvious where the conflicts come from18:33
mizu_no_oto joined18:33
cerkauskas joined18:33
moritz the conflict markers tell you which part conflicted18:33
angular_mike_ Is there a way to list tracked files, ordering them by their last modification date?18:33
geoid joined18:34
pedahzur joined18:34
dickdaley left18:34
moritz angular_mike_: git ls-files|xargs ls -t18:34
daito joined18:34
moritz though that orders by last file system modification, not by last modification from git18:34
denimsoft left18:35
pedahzur So, I have a file I committed without execute permissions. Now I want to add execute permissions. I tried git update-index --chmod=+x script.sh. It updates the file sitting in the working copy, but 'git status' doesn't show any changes, and 'git commit' says nothing to commit, directory clean. How do I commit the permission update?18:35
angular_mike_ moritz: no, I meant the git modification18:35
cdg left18:35
Garriel joined18:35
angular_mike_ moritz: basically ordering by the date of last commit that modified it18:35
faux___ joined18:36
cdg joined18:36
angular_mike_ pedahzur: changing the permission and performing `git add <file>; git commit` should work18:36
znabavi left18:36
pedahzur angular_mike_: Yeah...tried that. Still says 'nothing to commit, working directory clean' :)18:37
anth0ny left18:38
anth0ny joined18:38
pedahzur angular_mike_: OK, strange...looks like the file may have already been set as such in the repo. Another clone showed it properly. Something must have tweaked the perms in my working copy. Sorry for the noise.18:39
antiatom joined18:40
faux___ left18:40
Balliad left18:40
cdg left18:40
daito left18:40
jackeroo_marc joined18:41
snthsnth left18:42
grilled-cheese joined18:44
m0ltar left18:45
User4587_ joined18:45
Manikandan left18:46
jceb_ left18:46
jrahmy joined18:47
saidi__ left18:47
livingstn left18:48
diegoviola joined18:49
pluffsy joined18:49
jonmorehouse left18:49
sanketdg left18:50
pluffsy left18:50
User458764 left18:50
Phoenixz joined18:51
MechtiIde left18:51
m0ltar joined18:51
fred1807 left18:52
devoldmx joined18:52
blinkdesign joined18:52
blinkdesign left18:53
cluelesscoder joined18:53
kgirthofer left18:53
cluelesscoder is there a simple way to show the commits which come after a given commit? reading man git-log and I'm not seeing it18:53
gitinfo the git-log manpage is available at http://jk.gs/git-log.html18:53
geoid left18:54
jarek joined18:54
simesy joined18:54
geoid joined18:54
geoid left18:55
veverak joined18:55
_ikke_ cluelesscoder: The problem is that each commit only points to it's parents, so it's easy to find which commits came before, but not easy which came after.18:55
veverak hi folks18:55
anybody experience with gitolite refusing to allow me to push18:55
while I have correct key?18:55
only difference from usual is that I am connecting over router that port-forwards it18:56
_ikke_ veverak: What error are you getting?18:56
cluelesscoder +_ikke_: so I can use the date I suppose - what is the default date format for git log? the man page says " log.date config variable sets a default value for the log command’s --date option"18:56
veverak Permission denied (publickey).18:56
fatal: Could not read from remote repository.18:56
bremner veverak: also, does "ssh git@server info" work?18:57
cluelesscoder but when I check the git-config, it doesn't mention a default for log.date18:57
nettoweb left18:57
bap1313 joined18:57
veverak bremner: permission denied18:57
cluelesscoder and actually log.date isn't what I'm looking for...18:57
bremner veverak: congrats, you have an ssh problem, not a gitolite problem ;)18:57
jonmorehouse joined18:58
cluelesscoder I'm looking for how I can make 'git log --after="August 12 2015"' work18:58
micah joined18:58
veverak bremner: ... :D18:58
it's virtual server behind router18:58
stantonk left18:58
veverak i can freely ssh into that machine from my "console" that got ssh on the internetz18:58
bremner veverak: I guess try the ssh troubleshooting tips on gitolite.com18:58
jarek left18:59
veverak it worked while I was in same network with the server18:59
and used it's local IP18:59
simesy left18:59
veverak but now nah18:59
Manikandan joined18:59
micah how can I show the git log entries for only two remotes (not all of them)?18:59
stantonk joined18:59
veverak bremner: btw: my pubblic key md5sum and sum of admin key in gitolite-admin matches19:00
saidi__ joined19:00
dstarh joined19:00
nKulo left19:00
Zuki joined19:00
diegoviola left19:00
Zuki left19:01
dstarh I have a file in git that's not ignored. I need to make temporary changes to it due to an OS upgrade that not everyone has made yet, is there any way to easily avoid checkin in my changes to the one file?19:01
tier_ left19:01
grawity add other changes individually (`git add -p`)19:01
machan joined19:02
cluelesscoder is it possible to use something like 'git log --before="12/09/2015" --after="12/07/2015"'19:02
it is only respecting a single option19:02
Nizumzen joined19:03
devoldmx left19:03
dstarh grawity i've been doing that but getting annoying, not expecting to be able to undo or commit the change for a few days19:03
stantonk left19:03
bremner veverak: the page I mentioned is http://gitolite.com/gitolite/sts.html19:03
cluelesscoder well, reading the commit limiting section more carefully I guess not...19:04
tier joined19:04
veverak yeah19:04
bremner: read that, didn't noticed anything that should wnat19:04
*work, or describe my problem19:04
bremner veverak: I guess the next option is to bug #ssh (assuming that exists)19:05
Sasazuka left19:05
veverak hmm19:06
hmmm19:06
veverak got soemthing19:06
Sasazuka joined19:06
machan left19:06
veverak bremner: ssh git@server won't work because that aims at different machine19:07
git uses for this different port than 22 afaik19:07
anchorite joined19:07
veverak but ssh git@server -p 9418 info19:07
faux___ joined19:07
majuscul1 left19:07
veverak reports connection refuset19:07
__main__ left19:07
bremner well. nc, traceroute, etc... sounds like a firewall issue.19:08
chandlerbing joined19:08
_ikke_ port 9418 is the git protocol, not ssh19:09
bremner also that ;)19:10
pedahzur _ikke_: and 29418 is the gerrit ssh server. :)19:10
__main__ joined19:10
Eugene 9418 and 29418 are often co-opted by gerrit & friends19:10
veverak gerrit?19:10
Eugene !gerrit19:10
gitinfo Gerrit is a web-based code review system, built by Google. https://code.google.com/p/gerrit/19:10
cluelesscoder git log -n 5 --after="12/12/2015" sort of works (give me commits starting from August 5 or so), while git log -n 5 --after="12/13/2015" does not... is there any documentation on what format git expects these dates to be in?19:10
veverak ah19:10
Eugene It uses its own SSH daemon so it can do funny tricks for user auth19:10
veverak well, from inside the network, I can clone the repos19:10
youngbaks joined19:11
cluelesscoder git log -n 5 --after="12/13/2015" gives no output19:11
Manikandan left19:11
mikecmpbll joined19:11
Joseph_Silber I have a file's changes staged. Now I want to reset the file's contents to HEAD, without affecting the index.19:11
How can I do this?19:11
faux___ left19:12
stantonk joined19:12
Joseph_Silber `git checkout -- path/to/file` doesn't accomplish anything, since it fulls from the index. I want to apply HEAD's contents to the working directory.19:12
cluelesscoder eh, found it on Stackoverflow https://stackoverflow.com/questions/27313309/list-git-commits-to-master-branch-between-two-dates19:12
veverak ok19:13
I am missing this19:13
but git clone git@server -> this uses what port?19:13
jmpp joined19:13
veverak (using gitolite)19:13
bremner what did you really type?19:13
because that's not a valid url.19:13
veverak "veverak.org"19:14
Alienpruts joined19:14
veverak bremner: git clone using that servers name in that network (sshed into another machine)19:14
git clone [email@hidden.address]19:14
worked19:14
using git cloen [email@hidden.address]19:14
doesn't19:14
bremner ok. that's an ssh url19:14
in both cases.19:15
veverak so it uses 22?19:15
hmm19:15
aquiles left19:15
bremner unless you reconfigure ssh.19:15
oojacoboo joined19:15
espindol_ joined19:16
sssilver joined19:17
_ikke_ Joseph_Silber: easiest: git show :file > file19:17
soryr19:17
Joseph_Silber: easiest: git show HEAD:file > file19:17
Joseph_Silber This worked: git checkout HEAD file19:18
tobyx left19:18
_ikke_ yes, but that also updates index19:18
malukenho left19:18
Joseph_Silber Oh! Ouch!19:19
No way to go back now?19:19
:(19:19
malukenho joined19:19
krawchyk left19:19
_ikke_ well, the object still exist in the repository19:19
chandlerbing left19:20
genera left19:20
_ikke_ git fsck --lost-found19:20
Milos left19:20
_ikke_ then check .git/lost-found/other if you can find the contents19:20
veverak finally!19:20
bremner: thanks a lot!19:21
aquiles joined19:21
Milos joined19:21
bremner wrong port forwarded?19:21
DeMiNe0 left19:22
Joseph_Silber _ikke_, that did it. Thanks!19:22
tobyx joined19:22
__main__ left19:22
Joseph_Silber I should probably get more acquainted lost-found.19:22
No idea what all this dangling is.19:22
guardian joined19:23
guardian hello19:23
_ikke_ Joseph_Silber: They are objects that most of the time are not needed any more19:23
guardian when logAllRefUpdates = true -- is there a way to know who pushed a tag to a remote?19:23
_ikke_ Joseph_Silber: echo foo > bar; git add bar; echo foo >> bar; git add bar -> dangling object19:24
DeMiNe0 joined19:24
Joseph_Silber So dangling objects are things that have been added to the index but never committed?19:24
t-mart_ joined19:25
_ikke_ for example19:25
Or commits that have been amended19:25
__main__ joined19:25
Joseph_Silber Those are available in reflog19:25
_ikke_ yup19:25
ascarter_ joined19:25
blackpaj1 joined19:25
Joseph_Silber I guess dropped stashes19:25
dickdaley joined19:25
ascarter left19:25
krawchyk joined19:25
Joseph_Silber Those aren't in reflog. Or are they?19:25
msonntag left19:25
frdmn left19:25
Guest45384 left19:25
_ikke_ Dropped stashes not anymore19:26
Muzer left19:26
Joseph_Silber So those could be found in lost-found?19:26
znabavi joined19:26
_ikke_ yes, I think so19:26
LoganG left19:26
LoganG joined19:26
gfixler1 left19:27
blackpajamas left19:27
macabre left19:27
skylite left19:27
Internet13 left19:27
t-mart left19:27
cerkauskas left19:28
Kamran joined19:28
frdmn joined19:28
frdmn left19:28
frdmn joined19:28
cdown joined19:28
msonntag joined19:28
KamranGuest5645919:28
MarkyC left19:29
MarkyC joined19:29
__main__ left19:30
Internet13 joined19:31
znabavi left19:31
__main__ joined19:32
mp3 left19:32
JM_ joined19:34
Repox joined19:35
faux___ joined19:35
__main__ left19:35
Muzer joined19:37
fred1807 joined19:38
Repox left19:38
saidi__ left19:38
ankurk What are some good Git workflows for small teams? I would love to know since my team is trying to set up a workflow from the ground up.19:38
fred1807 left19:38
snthsnth joined19:38
phroa !workflows19:38
gitinfo [!workflow] 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.19:38
marc_v92 joined19:39
jeffreylevesque left19:39
marc_v92 left19:39
blackpaj1 left19:40
ankurk Thanks @phroa19:40
faux___ left19:40
vith1vith19:40
ankurk Should be a good read19:40
Asiajey joined19:41
Asiajey left19:42
X67r joined19:43
otter768_ joined19:44
otter768 left19:44
snthsnth left19:44
livingstn joined19:45
espindola joined19:45
pedahzur left19:46
jnewt left19:46
mbrzuzy left19:46
AlexMax_ joined19:46
dustinm- left19:47
krawchyk left19:47
AlexMax left19:47
tomek left19:47
Hello71 left19:47
slixpk left19:47
halfline left19:47
james3015 left19:47
Hello71_ joined19:47
halfline joined19:47
james3015 joined19:47
renoirb joined19:47
slixpk joined19:47
tomek joined19:47
mwhooker joined19:47
Sasazuka left19:48
espindol_ left19:48
machan joined19:48
dustinm joined19:49
jceb_ joined19:49
yqt joined19:50
jonmorehouse left19:50
aquiles left19:51
cdg joined19:52
Xe left19:52
pedahzur joined19:52
znabavi joined19:53
Xe joined19:53
jagob joined19:54
livingstn left19:55
mbrzuzy joined19:57
znabavi left19:57
kpease left19:57
saidi__ joined19:57
Ceber left19:58
kpease joined19:58
mwhooker_ joined19:58
devoldmx joined19:59
mwhooker left20:00
ErKa left20:00
Thorax left20:00
jonmorehouse joined20:00
Brain joined20:01
tier left20:01
mwhooker_ left20:01
tier joined20:01
IrishPrime left20:02
jceb_ left20:03
stantonk left20:04
devoldmx left20:04
Joseph_Silber I'm using `patch -p1 < file.patch` to apply a patch across two different repositories.20:05
wCPO joined20:05
stantonk joined20:05
Joseph_Silber For any conflicts, I get a new file `original-name.rej`20:06
But I also have `original-name.orig`20:06
Seveas Joseph_Silber: that's not bad, but try 'git format patch' and 'git apply' next time. Or simply add the second repo as a remote, and then fetch and cherry-pick20:06
format-patch*20:06
Joseph_Silber Didn't work for me.20:06
They share no heritage.20:06
bap1313 left20:07
_ikke_ Seveas: git format-patch -> git am20:07
Joseph_Silber Back to my patch... I'm trying to understand what those `original-name.orig` are for.20:07
Seveas Joseph_Silber: that shouldn't matter :)20:07
Joseph_Silber I get them for some files that have no conflict.20:07
But what are they for?20:07
Seveas the .orig is the unmodified file from before running patch20:07
Rym7 left20:07
Joseph_Silber I only get it for a few files. Why?20:07
_ikke_ It's a safety20:08
are the other files changed?20:08
Joseph_Silber Sure.20:08
mingwandroid joined20:09
gopar joined20:09
mwhooker joined20:10
pm90__ left20:11
jmpp left20:11
zumba_addict left20:12
Suzeanne joined20:14
livingstn joined20:14
gfixler1 joined20:14
darkbasic_ left20:15
jmpp joined20:16
darkbasic joined20:16
PsuzeannePsy left20:17
flashpoint9 left20:18
snthsnth joined20:19
LBV_User left20:19
mwhooker left20:19
cdown_ joined20:20
cdown left20:20
cjohnson joined20:20
sid28 joined20:21
cjohnson I'm running git clean -df and I'm under the impression that as long as I don't use -x, it should leave ignored files alone20:21
dstarh left20:21
ahr3n joined20:21
cjohnson but when I run it, it's removing a dir that I'm explicitly ignoring20:21
j416 cjohnson: is it empty?20:21
cjohnson http://pastie.org/pastes/10466918/text20:22
j416: it's not20:22
sid281 left20:22
cjohnson git status doesn't show it at all so I know it's being succesfully ignored20:22
cdown joined20:22
algae left20:22
Seveas you're not ignoring that dir, only its contents20:22
cjohnson I thought git had no concept of dirs20:23
Seveas only when ignoring20:23
cjohnson or not in that way, anyway20:23
grawity it has no concept of /empty/ dirs20:23
Seveas only when ignoring it does have a concept of dirs20:23
aesinv_ left20:23
jonmorehouse left20:23
D-unit joined20:24
nessundorma joined20:24
cjohnson I took the empty dirs thing to mean that it just didn't have a concept of dirs period. so anyway I just need to ignore dev-tools/node_modules ?20:24
that will successfully ignore the dir and all its contents?20:24
Seveas yes20:24
cjohnson ok20:24
D-unit left20:24
cjohnson but my question is, why doesn't it show up in git status?20:24
j416 interesting corner-case nonetheless20:24
cjohnson not even as an untracked file20:24
Seveas or you could use git clean -dX20:24
j416 cjohnson: probably because you are ignoring everything in it, and that makes it "empty"20:25
nettoweb joined20:25
cjohnson ahhh right20:25
git status only has concepts of dirs20:25
blimpse joined20:25
cjohnson er files20:25
that makes sense then20:25
Cool thanks folks20:25
j416 o/20:26
AaronMT left20:26
Karkus joined20:26
Sasazuka joined20:26
rwb left20:28
nessundorma left20:30
nettoweb left20:31
troulouliou_dev joined20:32
darkbasic left20:32
bendangelo joined20:32
whomp_ joined20:32
marc_v92 joined20:32
cjohnson left20:32
whomp left20:33
darkbasic joined20:34
youngbaks left20:34
wCPO left20:34
SuzieQueue joined20:35
Oog joined20:36
faux___ joined20:36
madewokherd left20:36
daito joined20:37
Suzeanne left20:39
whomp joined20:40
marc_v92 left20:40
anchorite left20:40
faux___ left20:40
anth0ny_ joined20:41
anth0ny left20:41
dgarzon joined20:41
daito left20:41
whomp_ left20:41
Jackneill left20:42
Milos left20:42
Karkus left20:42
RockLee joined20:43
Milos joined20:43
thiago joined20:45
gdg joined20:45
gdg hi20:45
gitinfo gdg: 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.20:45
gdg I am in a detached branch20:46
NeverDie joined20:46
gdg how can I merge it back to a branch XY20:46
BlueProtoman joined20:46
phroa !merge20:46
gitinfo 'git merge' takes two diverged lines of history (series of commits, e.g. on different branches), and recombines them with a "merge commit" on top. This creates an explicit record of you doing the merge, unless there were no local changes (which does a !fast_forward merge instead). If you don't need to keep a record like that, !rebase may produce easier-to-read history, but the two don't always mix well... see also !merge_vs_r20:46
nuck joined20:46
User458764 joined20:47
adgtl joined20:47
znabavi joined20:47
nettoweb joined20:47
BlueProtoman I have a repo on GitHub that I forked from another repo, but I accidentally diverged from the original repo, and didn't figure this out until after my changes were already on GitHub. How can I just reset my fork's master branch to the original repo's master?20:47
aesinv joined20:47
jagob left20:48
_ikke_ BlueProtoman: Do you know how to fix it in your local clone of your fork?20:48
phroa BlueProtoman: git reset --hard upstream/master ; git push -f origin master20:48
where upstream is the upstream, origin is your fork20:48
Milos left20:49
Amandil joined20:49
BlueProtoman phroa: Thank you!20:49
hobodave joined20:49
BlueProtoman _ikke_: No, I don't. Just that I think I accidentally re-committed some changes, but that doesn't matter now20:49
Karkus joined20:49
Nizumzen left20:50
flashpoint9 joined20:51
mizu_no_oto left20:51
User458764 left20:51
znabavi left20:52
saidi__ left20:52
harish_ left20:52
Milos joined20:52
mbrzuzy left20:53
boombatower joined20:53
cavallari left20:53
BlueProtoman left20:53
Spacew00t left20:53
darkbasic_ joined20:53
whomp left20:54
Amandil left20:54
darkbasic left20:54
bap1313 joined20:55
acetakwas joined20:55
gdg left20:55
livingstn left20:55
AnalogSuzen left20:55
Oog left20:56
arthurix joined20:56
jrahmy left20:56
jonmorehouse joined20:57
adgtl left20:57
tier left20:57
adgtl joined20:59
blimpse left20:59
cdown left20:59
boombatower left21:00
shinnya left21:01
stantonk left21:01
oojacoboo left21:01
ChanServ set mode: -o21:01
m0ltar left21:01
SuzieQueue left21:02
MistahKurtz joined21:02
darkbasic_ left21:02
tpollard joined21:03
darkbasic joined21:03
m0ltar joined21:03
m0ltar left21:03
mbrzuzy joined21:03
snthsnth left21:03
dickdaley left21:04
madewokherd joined21:04
NeckBeardPrince left21:05
stantonk joined21:05
rnsanchez left21:05
pm90_ joined21:05
mbrzuzy left21:05
xudongz left21:06
JM_ left21:06
smaudet left21:06
kgadek joined21:07
kgadek left21:07
dickdaley joined21:08
Rym7 joined21:08
kgadek joined21:09
kgadek left21:09
Karkus left21:09
Anxi80_ left21:09
flashpoint9 left21:09
alexsystemf joined21:10
oojacoboo joined21:10
ankurk left21:10
ahr3n_ joined21:10
anth0ny_ left21:11
anth0ny joined21:11
Rym7 left21:13
ahr3n left21:13
Suzeanne joined21:14
jackeroo_marc left21:14
pm90__ joined21:15
ploopkazoo left21:15
BBBThunda left21:16
espindol_ joined21:17
pm90_ left21:17
ColdKeyboard joined21:19
ploopkazoo joined21:20
xcesariox joined21:20
micah left21:20
espindola left21:20
espindola joined21:21
mingwandroid left21:22
oojacoboo left21:23
espindol_ left21:23
RaceCondition left21:24
macrover joined21:25
Vile joined21:25
darkbasic left21:26
m0ltar joined21:26
linuxmint2 joined21:26
ProfessorKaos64 left21:26
cagedwisdom joined21:28
eikood joined21:28
darkbasic joined21:29
w00die left21:29
arup_r left21:29
boombatower joined21:29
askhl left21:30
anth0ny_ joined21:31
denimsoft joined21:31
dgarzon left21:32
anth0ny left21:32
huglester left21:32
impliednude left21:32
affa09 left21:34
cdown joined21:34
arthurix left21:34
Alienpruts left21:35
troulouliou_dev left21:35
darkbasic_ joined21:36
denimsoft left21:36
darkbasic left21:37
nnyk_ joined21:37
ahr3n_ left21:37
dsdeiz joined21:38
macrover left21:38
ahr3n joined21:38
cagedwisdom left21:39
trv joined21:40
AnalogSuzen joined21:40
mezod joined21:40
ASOLAr joined21:40
slentzen left21:41
modocache left21:41
stamina joined21:41
cdown left21:41
znabavi joined21:42
darkbasic joined21:42
hashtag_ joined21:42
acetakwas left21:42
darkbasic_ left21:43
bb010g left21:43
pedahzur left21:44
Suzeanne left21:44
pedahzur joined21:44
nemix__ left21:44
RockLee left21:44
Brain left21:45
fscala left21:45
acetakwas joined21:45
mellernoia left21:45
hashtag_ left21:46
skullcrasher left21:46
znabavi left21:46
durham left21:46
durham joined21:47
lg188 left21:47
fscala joined21:47
Douhan joined21:49
pandeiro joined21:49
skullcrasher joined21:50
dreiss left21:50
ASOLAr left21:51
AaronMT joined21:51
cagedwisdom joined21:52
AaronMT left21:52
gopar left21:52
darkbasic left21:54
darkbasic joined21:54
zet_013 joined21:56
acetakwas left21:56
mizu_no_oto joined21:57
ajf- left21:57
AnalogSuzen left21:57
ajf- joined21:57
Darcidride left21:59
Dougie187 left21:59
victortyau left21:59
pantsman- left21:59
devoldmx joined22:00
ajf- left22:03
irc-5225225 left22:04
devoldmx left22:05
delaytime0 joined22:07
delaytime0 left22:07
delaytime0 joined22:07
treehug88 joined22:09
znabavi joined22:09
adgtl left22:09
User4587_ left22:10
xcesariox left22:10
znabavi left22:10
Hello71_Hello7122:11
znabavi joined22:11
chitopunk left22:11
zet_013 left22:12
slentzen joined22:14
sgambino left22:14
Es0teric left22:15
irc-5225225 joined22:16
salamanderrake left22:16
jalnt joined22:17
axl_ left22:17
cdg left22:18
dreiss joined22:18
ASOLAr joined22:19
salamanderrake joined22:19
dionysus69 left22:19
retyk joined22:19
dev3 joined22:20
infernix joined22:20
neanderslob joined22:21
_9dan joined22:21
gitinfo set mode: +v22:22
dev3 is there a way to prevent a specific file that will always exist on a branch (master) from being merged into another branch (development) where it should never exist, preferably automatically22:22
Guest82484 left22:22
c74d3a left22:23
s8321414 joined22:25
NotBobDole left22:25
fracting1 left22:25
cdown joined22:28
espindola left22:28
jalnt left22:28
axl_ joined22:30
mikiones left22:31
axl_ left22:31
thiago left22:32
kpease left22:33
durham_ joined22:34
qsuscs dev3: no. sounds like !config22:35
gitinfo dev3: [!configfiles] It is recommended to store local configuration data in a file which is not tracked by git, but certain deployment scenarios(such as Heroku) may require otherwise. See https://gist.github.com/1423106 for some ideas22:35
tinajohnson left22:35
durham left22:36
hobodave left22:36
anth0ny_ left22:36
jalnt joined22:36
dreiss left22:37
ekleog left22:37
dreiss joined22:37
daito joined22:38
dinobytes left22:38
highcup left22:38
ekleog joined22:38
highcup joined22:38
mizu_no_oto left22:39
highcup left22:39
highcup joined22:39
cdown left22:41
bollullera joined22:41
samw_ joined22:42
fedexo left22:42
daito left22:42
highcup left22:43
samw left22:44
Limes__ left22:44
anth0ny joined22:45
mattcen left22:45
acetakwas_ joined22:46
User458764 joined22:47
editshare-ericf left22:47
k_j left22:48
samw_ left22:48
cdown_ left22:49
King_Hual left22:51
User458764 left22:52
flaguy48 left22:53
mattcen joined22:53
cdown joined22:53
cbonobo_ left22:54
malukenh_ joined22:55
slentzen2 joined22:55
Zamyatin left22:55
pm90__ left22:56
slentzen left22:57
malukenho left22:58
Kicer86 left22:58
pm90_ joined22:59
bond joined22:59
jteneyck joined23:00
jteneyck left23:00
jteneyck joined23:00
thinkxl left23:01
yqt left23:05
parasite left23:08
durham_ left23:08
znabavi left23:09
durham joined23:09
cdown_ joined23:10
hexagoxel left23:11
hexagoxel_ joined23:12
dsdeiz left23:12
hexagoxel_hexagoxel23:12
dreiss left23:13
k_j joined23:13
stantonk left23:13
znabavi joined23:13
cdown left23:14
tjbp joined23:15
filisko left23:15
lindenle left23:18
nnyk_ left23:19
jteneyck_ joined23:22
snowcycle joined23:24
dreiss joined23:25
jteneyck left23:25
Gravitron joined23:26
samw joined23:26
Nizumzen joined23:27
diegoviola joined23:27
snthsnth joined23:27
phantombeta left23:30
jonmorehouse left23:30
Egyptian[Home] joined23:30
Egyptian[Home] left23:32
znabavi left23:32
bango2 left23:32
phantombeta joined23:33
grilled-cheese left23:34
machan left23:35
Not_Whatever left23:35
znabavi joined23:35
Nikhil_D left23:37
Nikhil_D joined23:38
boombatower left23:38
shinnya joined23:38
thinkxl joined23:38
acetakwas_ left23:39
bango2 joined23:40
t4nk531 joined23:41
jonmorehouse joined23:41
dinobytes joined23:42
modocache joined23:42
alexsystemf left23:43
zhiwliu joined23:43
stantonk joined23:43
zhiwliu left23:43
sabgenton joined23:44
Noldorin left23:45
t4nk531 left23:46
Noldorin joined23:46
MihaiTodor joined23:46
dsdeiz joined23:46
modocache left23:46
sabgenton AFAIK 'branch' constitutes all the branches that were also merged into it. But if I maintain a nice straight line that never changes what do I call that straight line part?23:46
royalty master?23:48
i just guessed23:48
probably incorrect23:48
jteneyck_ left23:48
stickperson left23:49
bl4ckpajamas left23:49
blackpajamas joined23:50
meLon joined23:50
stantonk left23:51
jteneyck joined23:52
zacg joined23:53
sabgenton royalty: as far as I understand master constitutes every chain underneath it spanning out from merge commits23:53
gitinfo set mode: +v23:54
royalty sabgenton, oh23:54
EqUptime23:55
sabgenton royalty: but sometimes we use loosely say branch 2 mean just the first parent straight line part23:56
dickdaley left23:57
fstd left23:59
m0viefreak left23:59
fstd joined23:59

Logs Search ←Prev date Next date→ Channels Documentation