IRCloggy #git 2013-10-10

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.

2013-10-10

pr0ton joined00:01
LuxuryMode joined00:01
pr0ton left00:02
boombatower__ left00:03
bwreilly joined00:03
bitkiller joined00:04
_live joined00:04
cannonball joined00:04
FabTG_ joined00:05
_live left00:05
quazimodo left00:05
YannH left00:05
_live joined00:05
pr0ton joined00:05
stamina joined00:05
_iron left00:05
_live left00:05
reskp left00:06
Robarelli joined00:06
Roots47 left00:07
FabTG left00:07
bakers left00:08
_live joined00:09
_live left00:09
hwrd|work left00:10
zjason` left00:13
fowlduck left00:13
alvaro_o left00:13
alvaro_o joined00:14
Dougie187 joined00:15
stamina left00:15
zjason joined00:15
HereCas joined00:18
vigs left00:19
maslowbeer joined00:20
starfox21 left00:20
brettnem left00:20
normanrichards joined00:21
harish_ left00:21
Baluse left00:22
petey joined00:22
Zushakon joined00:22
mFacenet joined00:22
dyng joined00:23
CycoCid left00:24
mFacenet left00:25
petey left00:26
petey joined00:27
dreiss_ left00:29
mklappstuhl left00:30
petey left00:31
mklappstuhl joined00:32
davidmturner joined00:32
bwreilly left00:32
PeterBooker left00:33
acharlieh left00:33
petey joined00:34
mattmcclure left00:34
hyperair left00:34
davidmturner left00:34
bsaboia_ left00:37
mklappstuhl left00:37
rednaks left00:37
Robarelli left00:38
Robarelli joined00:39
Swayz joined00:39
bunbury left00:41
axl_ joined00:43
Andrevan left00:43
Zarthus left00:44
rat_thing left00:45
minim left00:46
KillYourTV left00:49
fuzzybunny69y joined00:50
minim joined00:52
jaequery joined00:53
cannonball left00:54
clreed87 joined00:54
clreed87 left00:55
minim left00:55
HereCas left00:56
exobyte left00:56
axl_ left00:57
R1KRDO joined00:57
perlstein does anyone rememeber my problems from before? this is how i feel: http://devopsreactions.tumblr.com/post/61746167797/spent-all-day-fixing-merge-conflict-wrong-branch00:58
freestyl3r left00:58
tufflax left00:59
carbohydrate joined00:59
axl_ joined00:59
freestyl3r joined00:59
Kabaka left01:01
Entomo joined01:01
luxgeek joined01:01
Kabaka joined01:02
Mikicacarica joined01:03
kukks left01:04
Mikicacarica left01:04
shinnya left01:06
R1KRDO left01:06
KillYourTV joined01:07
Vampire0 joined01:08
langhun joined01:08
hyperair joined01:10
hahuang65 left01:11
Vampire0_ left01:12
rchavik joined01:13
vinc joined01:13
kmctown left01:13
foucist joined01:14
normanrichards left01:15
rat_thing joined01:16
Gooder left01:16
weiyang joined01:17
thiago left01:17
gogobudyy joined01:21
delianides joined01:22
gogobudyy left01:23
maslowbeer left01:23
rat_thing left01:24
introom23 joined01:25
goshawk left01:25
jhulten left01:25
gitinfo set mode: +v01:25
Goplat joined01:25
introom23 hi. I have an idle linux box. and I'd like to set it as a git server for data backup use. Has anyone done that before? How's that?01:25
sayanee joined01:26
jaequery left01:26
jon_r joined01:27
axl_ left01:27
joshsmith joined01:28
jaequery joined01:28
intripoon_ joined01:29
chrisss404 left01:29
petey left01:30
petey joined01:30
chrisss404 joined01:31
intripoon left01:32
aartist joined01:32
petey left01:32
Curtisbeef don't use git for backing up binary files01:32
petey joined01:32
Curtisbeef use rsync and some scripting with a cron job01:33
mribeirodantas left01:34
mribeiro1antas joined01:34
mattmcclure joined01:34
batrick left01:34
Swayz left01:34
introom23 Curtisbeef: If I delete my file locally, I don't want the file will be deleted from the server. Can rsync fulfill that?01:35
Curtisbeef yup01:35
shruggar left01:36
Curtisbeef look up "rsync backup incremental"01:36
jhulten joined01:36
daito joined01:38
jaequery left01:39
LuxuryMode left01:39
Destos left01:40
batrick joined01:40
pr0ton left01:41
byprdct joined01:42
iateadonut i've got a directory that i want to ignore: /home/me/project/www/ but i don't want to ignore /home/me/project/libs/dompdf/www/01:42
byprdct left01:42
iateadonut the root of the project is /home/me/project01:42
SBoudria1 joined01:42
iateadonut i've got www/ in my .gitignore, but that is not correct - it's also preventing libs/dompdf/www from being inserted01:43
Robarelli left01:43
SBoudria1 left01:43
petey left01:43
yacks left01:43
petey joined01:44
mattmcclure left01:44
iateadonut /usr/bin/rsync -ab --backup-dir=/home/back/backup/site_live/old_`date +%F` --exclude=/admin/templates_c/ site@site:/home/site/public_html/ /home/back/backup/site_live/01:44
introom23, that's my backup script - /home/back is the home directory of the backup user, while /home/site (user:site, /etc/hosts server name:site)01:45
i run that once a day01:45
introom23 iateadonut: you backup it locally?01:46
cmpera left01:46
iateadonut no01:46
locally?01:47
one server to another01:47
Newtonianb joined01:47
iateadonut go in #linux and ask more.01:47
jhulten left01:48
petey left01:48
ojacobson joined01:50
Robarelli joined01:50
resmo_ joined01:50
bwreilly joined01:51
Hello71 iateadonut: because you want /www01:53
not www/01:53
man gitignore01:53
gitinfo the gitignore manpage is available at http://jk.gs/gitignore.html01:53
tinti left01:53
resmo left01:54
tmcmahon joined02:00
adamwathan left02:00
synergy__ joined02:02
luc__ joined02:03
yacks joined02:03
refried_ joined02:03
bunbury joined02:04
FernandoBasso left02:06
GT left02:06
gitpicker left02:06
kerrick joined02:07
alvaro_o left02:07
LuxuryMode joined02:08
gitpicker joined02:08
rgr joined02:10
robbyoconnor joined02:12
introom23 left02:15
funfunctor left02:16
harish joined02:16
LuxuryMode left02:17
Squarism left02:17
tmcmahon left02:17
kerrick left02:18
HenryG left02:18
MrKeuner joined02:19
mattmcclure joined02:19
amcsi_work left02:21
Robarelli left02:23
GT joined02:25
Robarelli joined02:26
mattmcclure left02:27
angelsl joined02:27
vigs joined02:28
jaequery joined02:29
jamiis joined02:32
acharlieh joined02:32
jaequery left02:34
langhun left02:35
kerrick joined02:37
kerrick left02:38
R1KRDO joined02:39
echo-area joined02:41
jaequery joined02:42
rurufufuss joined02:43
bwreilly left02:43
mobileblue joined02:45
bwreilly joined02:46
hahuang65 joined02:46
mobilebl- left02:49
maslowbeer joined02:51
dong joined02:51
bwreilly left02:52
AaronMT left02:53
dreiss_ joined02:54
minim joined02:54
Goplat left02:55
robbyoconnor left02:55
simera left02:56
Goplat joined02:56
Robarelli left02:57
joki left02:58
robbyoconnor joined02:59
Swayz joined03:00
robbyoconnor left03:00
delianides left03:00
johnnyfuchs joined03:00
johnnyfuchs left03:00
mattmcclure joined03:02
EdGrubemran joined03:02
EdGruberman left03:03
joki joined03:04
Dougie187 left03:05
mattmcclure left03:07
jaequery left03:09
bandroidx left03:10
delianides joined03:11
jaequery joined03:11
acharlieh left03:12
byprdct joined03:12
byprdct left03:13
byprdct joined03:13
Gamecubic left03:15
dsdeiz joined03:16
bitkiller left03:17
Swayz left03:18
freestyl3r left03:19
chirayuk joined03:20
hahuang65 left03:21
dyng left03:21
dyng joined03:21
MrKeuner left03:24
bwreilly joined03:25
dyng left03:26
rchavik left03:28
willwh left03:29
carbohydrate left03:30
redrocket joined03:36
kermit left03:36
echo-area left03:37
nitrixcake03:38
cakenitrix03:38
el3ctron_ joined03:39
relipse joined03:39
PaulCapestany left03:39
falconfoxx left03:39
relipse how do i get colors in git on my mac osx03:39
falconfox joined03:40
bandroidx joined03:41
bandroidx left03:41
bandroidx joined03:41
woollyams joined03:41
relipse git config --global color.ui true03:41
got it03:41
how come when i type git commit -am foo, i get a fatal: Paths with -a does not make sense. on mac osx03:42
delianides left03:42
Guest50535 joined03:46
functorfun joined03:46
functorfunfunfunctor03:46
the_cybersphinx left03:47
rchavik joined03:48
gitinfo set mode: +v03:48
Guest50535fobius03:49
jaequery left03:50
fobius I'm a git newb with a question:03:50
karstensrage relipse, doesnt -a mean all?03:50
relipse i restarted the terminal and it started working properly03:50
fobius Git uses a three way merge as the standard merge procedure I gather. Whenever users make edits to different parts of a file git has an auto merge procedure that it uses to create the new file03:50
i.e. if the changes don't conflict03:51
then keep both03:51
but what about code that has side effects, e.g. global variables?03:51
In that case, it seems that git might break the code if it merged in code which changed a global/side effect03:51
and code which depends on that global/side effect03:51
chirayuk left03:51
fobius so, what are best practices for avoiding that type of situation?03:52
MrRoot joined03:53
preflex_ joined03:53
foucist fobius: if there's a commit that modifies the global variable, then presumably that same commit has modified the rest of the codebase to handle that change..03:53
or something like that03:53
fobius Well, I'm talking about two different commits03:54
for instance, say there's a method that's been add, addXYZ03:54
sqlnoob joined03:54
fobius and this method is a new feature03:54
originally it returns an array03:54
preflex left03:54
fobius *not an array, a float03:54
preflex_preflex03:54
hahuang65 joined03:54
fobius anyway, one user writes some code that uses this method addXYZ03:54
but doesn't change the method03:54
now, another user comes along and changes the method03:55
to return an integer instead of a float03:55
These changes will be auto merged since they don't modify the same hunks03:55
but the method is now incompatible03:55
foucist uh, if another user changes the method, s/he should change the rest of the codebase that depends on that03:56
fobius: also, this is what CI (continuous integration) is for03:56
like travis CI03:56
it detects breakage like this03:56
fobius well, I mean, if the changes to the method03:56
are being made at the same time that the new code which uses the method is being written03:56
then when they merge together it will break, right?03:57
ingof joined03:57
foucist there's no same time though, someone pushes first, the other person that comes along has to pull & merge and make sure his changes don't break stuff (ideally)03:57
or if it's done through pull requests then sometimes the person needs to re-pull and redo his stuff and update the pull request03:57
if the merger encounters an issue03:58
i'm not really an expert here though03:58
dhruvasagar joined03:58
foucist just talking out my assk03:58
out of my ass*03:58
fobius lol. So then from what I gather here the solution is to basically just test after a merge and make sure everything still works proper?03:58
Because essentially the issue that I'm talking about is that the code base that you started with03:59
isn't the same one that you merge back into03:59
bitkid left03:59
foucist fobius: i believe there's a way to have automatic tests that prevent merges if a merge is gonna break stuff04:00
albel727 left04:00
donmichelangelo left04:00
hagabaka joined04:00
donmichelangelo joined04:01
druonysus left04:01
delianides joined04:01
delianides left04:01
ingof left04:02
fobius foucist, How would you know if it was gonna break stuff without knowing what the language is like? I mean, I think that in general this sort of thing shouldn't happen unless you have code with bad side effects anyway.04:02
kermit joined04:03
kermit left04:03
kermit joined04:03
mribeiro1antas left04:05
foucist fobius: well there'd need to be tests basically04:05
funfunctor left04:05
YannH joined04:06
fobius foucist, Yeah, I suppose that makes sense. I think I'm looking for some kind of magical reassurance that auto merge always works out but it's probably not there. I was just wondering if this is a known problem or something that only people who are as OCD as myself are interested in.04:06
foucist fobius: i recommend you ask again when serious git people are around04:07
hahuang65 left04:07
shoshin left04:07
foucist ask in 12-14 hours from now :P04:07
fobius foucist, okay, thanks for your help.04:07
lol04:07
fridim_ left04:08
albel727 joined04:08
fobius left04:09
YannH left04:12
Katafalkas joined04:14
hwrd|work joined04:14
hwrd|work left04:14
Newtonianb left04:14
atSetKey left04:16
niggler joined04:16
axl_ joined04:17
atSetKey joined04:17
niggler hello! suppose i have 5 commits (initial,a,b,c,d) and I want to squash commits a,b,c into one commit. how can i do that with rebase?04:17
natechan left04:18
relipse git rebase -i04:18
atSetKey left04:18
niggler can you give it an initial and end commit, or do i have to rebase from initial04:18
breck7_ joined04:19
breck7 left04:19
fragamus joined04:20
SamB niggler: see man git-rebase04:22
gitinfo niggler: the git-rebase manpage is available at http://jk.gs/git-rebase.html04:22
willwh joined04:22
SamB niggler: it has pictures and everything04:22
diegoviola joined04:22
niggler nvm my confusion stemmed from the fact that the rebase got rid of the merge commits (which, incidentally, was desired)04:23
MrRoot left04:23
shoshin joined04:24
daito left04:24
bwreilly left04:24
daito joined04:24
daito left04:24
dyng joined04:24
R1KRDO left04:25
niggler actually SamB now I'm confused04:27
rpg left04:28
niggler i think there was some timezone difference, and git is getting tripped up by it04:28
SamB why do you think that?04:28
I mean git doesn't usually do much with times04:28
rjhunter niggler: you can reset the commit date as part of rebase if you like04:29
niggler no the dates are correct, but git is getting confused by the timestamp04:29
rjhunter niggler: git itself doesn't care04:29
SamB what's it doing wrong?04:29
epicowl joined04:30
foucist left04:30
dyng left04:30
niggler so the history has a few commits04:30
in order04:30
dyng joined04:31
niggler Date: Sat May 18 13:55:18 2013 +020004:31
Date: Sat May 18 08:19:17 2013 -040004:31
Date: Sat May 18 15:02:31 2013 +020004:31
Date: Sat May 18 06:08:49 2013 -070004:31
dyng left04:31
dyng joined04:31
niggler chronologically, they are the correct order04:32
SamB yeah?04:32
niggler then i rebased04:32
SamB and?04:32
niggler and the new history has the commits in the order04:32
SamB I'm guessing this is related to the merge04:32
willwh left04:32
niggler so one of the merge commits was lost04:33
rjhunter if you want the commits in a particular order, use rebase --interactive04:33
niggler rjhunter i used rebase and tried to squash two unrelated commits04:33
eletuchy_ joined04:34
niggler but it appears that the commits were reordered based on the time without adjusting for time zones04:34
Sat May 18 08:19:17 2013 -0400 shows up before Sat May 18 13:55:18 2013 +020004:35
SamB the commits would be in whatever order you left them in in the file you edited04:35
Smrtz joined04:35
el3ctron_ left04:36
glosoli joined04:36
eletuchy left04:36
Smrtz I'm trying to clone a repo into ~/<gitName>, I would do this with git clone git.github.com/<user>/<gitName> ~/<gitname> right?04:36
hahuang65 joined04:37
rjhunter niggler: i'll have to check to make sure, but i'm pretty sure git doesn't care about dates at all when choosing default order of commits for rebase.04:37
glosoli Hey I have a branch on which I did git rebase master, I had so conflicts, so I solved and pushed them (wanted to update it with the latest changes from master). Now history of my branch includes my commits twice (some sort of duplicates with different hashes) one before master commits I rebased and the other duplicates after04:38
any ideas ?04:38
niggler ok so it appears that the original view (from git log --oneline) is sorted correctly, but the file from git rebase -i is not sorted properly rjhunter04:38
rjhunter git doesn't care about dates much at all04:38
niggler and the sort is consistent with using the stated date but ignoring the timezone modifier04:38
eletuchy_ left04:38
rjhunter niggler: you can move the lines into whatever order you like in the --interactive list04:39
niggler rjhunter is there a switch i can pass to rebase so that the sort is consistent with the git log order?04:39
rjhunter Smrtz: close -- you'll want a little bit more on your source URL. you can copy it from the Github web page04:39
bitkid joined04:39
Robarelli joined04:40
AWinterman left04:40
rjhunter glosoli: i'll be with you in a second, but it sounds like your pre-rebase commits and your post-rebase commits both got pushed04:41
AWinterman joined04:41
Smrtz rjhunter: so https://www.github.com/<user>/<gitName> <~/<gitname>?04:41
dyng left04:41
nwertman_ left04:41
dyng joined04:41
rjhunter Smrtz: that looks pretty reasonable to me -- the last part is just the directory you want the results to go in -- if you don't provide one, git makes a new folder under the current directory04:42
yacks left04:42
Smrtz rjhunter: thanks.04:43
longbeach joined04:43
robbyoconnor joined04:43
joshsmith left04:44
bitkid left04:44
rjhunter niggler: I don't see any control over the starting order in the manpage (I'll check the source shortly), but really if you want a specific order then just put them in that order. that's what --interactive is for.04:44
iamjarvo joined04:45
AWinterman left04:45
dyng left04:46
glosoli left04:48
xjiujiu joined04:49
rjhunter niggler: the starting order for rebase is --topo-order (see man git-revlist for a description what that means)04:49
GT left04:50
rjhunter niggler: in short, it's not the dates but the parentage that make the difference to the starting order (again, you can re-order them how you like in --interactive)04:51
dyng joined04:51
Smrtz left04:51
danillonunes left04:52
beautifulmind joined04:52
beautifulmind left04:53
GT joined04:53
beautifulmind joined04:53
hahuang65 left04:54
Tommy[D] joined04:56
Tommy[D]_ left04:56
eletuchy joined04:56
dsdeiz left04:57
LuxuryMode joined04:58
ebertx joined05:01
eletuchy left05:01
hahuang65 joined05:01
thiago joined05:02
breck7_ left05:02
hendry joined05:03
hendry what's the typical operation to try get the size of git repo down?05:03
woollyams left05:03
woollyams joined05:06
tango_ left05:07
jwmann left05:07
rat_thing joined05:08
akurilin left05:09
iamjarvo left05:09
iamjarvo joined05:10
tango_ joined05:11
rjhunter hendry: du -sh .git05:12
zbcm joined05:12
momomomomo joined05:12
rjhunter hendry: oops, sorry, i misread your question05:12
hendry: `git gc` for garbage collection05:13
daito joined05:14
Caritade joined05:15
rjhunter hendry: you can use du -sh .git before and after to see the difference :-)05:16
byprdct left05:17
woollyams left05:17
maestrojed joined05:18
Devastator left05:19
DonRichie joined05:19
Devastator joined05:21
JohnBat26 joined05:21
angelsl left05:22
awc737 left05:24
NanoArrow left05:24
iamjarvo left05:25
willwh joined05:25
willwh left05:25
willwh joined05:25
momomomomo left05:25
madewokherd left05:25
iamjarvo joined05:25
atSetKey joined05:27
awc737 joined05:27
rchavik left05:28
jwmann joined05:28
iamjarvo left05:30
willwh left05:30
v0n joined05:30
glosoli joined05:30
ej joined05:31
atSetKey left05:32
dreiss_ left05:35
rchavik joined05:35
functorfun joined05:35
functorfunfunfunctor05:35
chairabanta joined05:40
drodger left05:41
drodger joined05:42
Caritade left05:42
Robarelli left05:42
ThomasLocke joined05:42
youlysse` joined05:42
youlysses left05:42
eletuchy joined05:43
Dudalus joined05:47
magu|q left05:50
leeN joined05:50
LuxuryMode left05:50
dreiss_ joined05:50
magu|q joined05:51
AWinterman joined05:51
LuxuryMode joined05:51
refried_ left05:52
rath joined05:52
TomyLobo joined05:53
lifechamp joined05:55
tpollard left05:55
druonysus joined05:56
Zarthus joined05:56
AWinterman left05:56
druonysus left05:59
ciampix joined05:59
LuxuryMode left05:59
druonysus joined05:59
chairabanta left05:59
lifechamp left06:02
fRAiLtY- joined06:03
lng joined06:03
momomomomo joined06:05
soee joined06:06
papegaaij joined06:07
rjhunter left06:08
kcj joined06:08
kwmiebach left06:10
rjhunter joined06:10
ej left06:10
Devastator left06:10
h0bbit_ joined06:10
ej joined06:11
kwmiebach joined06:11
momomomomo left06:11
Zushakon left06:13
ebertx left06:13
eletuchy left06:13
eletuchy joined06:13
a-l-e joined06:14
ej left06:15
cbreak-work joined06:15
Devastator joined06:16
jargon joined06:17
willwh joined06:17
eletuchy left06:18
beingbrown joined06:19
gitinfo set mode: +v06:20
h0bbit joined06:20
beingbrown hello.06:20
gitinfo beingbrown: 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.06:20
zarubin joined06:22
beingbrown Is there anyone around that might be able to answer a quick question?06:22
dsdeiz joined06:23
GT left06:24
beingbrown left06:25
axl_ left06:25
cbreak-work left06:25
jon_r left06:25
willwh left06:28
cbreak-work joined06:28
dyng left06:28
dyng joined06:29
coredumb joined06:31
GT joined06:31
coredumb left06:31
reim left06:32
iateadonut depends on the question06:32
but now it's too late, because you left the room and will never see this.06:33
epicowl left06:33
vurma joined06:33
Woet maybe that was his actual question06:33
you never know06:33
dyng left06:33
dyng joined06:33
youlysse` left06:34
youlysses joined06:37
angelsl joined06:37
quasimodo joined06:37
relipse left06:38
threesome joined06:40
TomyLobo left06:46
jnavila joined06:47
ej joined06:48
JohnBat26 left06:49
rob_w joined06:50
rjhunter left06:51
netiul joined06:52
JohnBat26 joined06:52
ej left06:53
threesome left06:53
dyng left06:53
dyng joined06:53
quasimodo left06:54
mishok13 joined06:56
dyng left06:57
MrKeys88 joined06:58
dsdeiz_ joined06:58
cbreak-work left06:58
dsdeiz left06:59
kate_r joined06:59
lite_ joined06:59
dyng joined06:59
stamina joined07:01
marthinal joined07:03
hoschi joined07:06
beautifulmind left07:06
Devastator left07:06
h_kon joined07:08
rat_thing left07:09
GeertV joined07:10
Xethron joined07:10
sm0ke joined07:10
ingof joined07:11
ingof left07:11
lb1a joined07:12
Goplat left07:13
Devastator joined07:13
gua_ould joined07:13
TomyWork joined07:14
sr78ger joined07:14
reim joined07:15
jon_r joined07:16
jargon left07:16
dfanjul joined07:18
dfanjul left07:18
dsdeiz joined07:18
staafl joined07:18
dfanjul joined07:18
Misan joined07:19
dsdeiz_ left07:19
dfanjul left07:19
Norm_ left07:19
y_nk joined07:21
threesome joined07:22
japaric left07:22
NanoArrow joined07:23
OOPMan joined07:23
m0viefreak left07:23
kama_ joined07:25
kama_ hi all07:27
why i am now on a nobranch, all changes are commits to nonbranch07:27
http://iyanwu.com/pastebin/showthread.php?tid=182807:27
kewah joined07:27
zequence_ left07:29
Robarelli joined07:29
Balliad joined07:29
zequence joined07:30
reskp joined07:31
lb1a kama_, because you've checked out a specifig ref07:32
specific*07:32
_ikke_ detached07:32
lb1a with bang !07:32
^^07:32
!detached07:32
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 !reattach07:32
_ikke_ yeah, trying out my new external tabletkeyboard07:33
lb1a hardware keyboard for a tablet?07:33
_ikke_ yeah07:33
jfinn left07:33
zarubin left07:33
lb1a very ambitious07:33
_ikke_ lol07:34
but aparently shift+1 doesn't work07:34
lb1a _ikke_, you certainly heard about this new invention... it's called "Laptop"07:34
^^07:34
harobed_ joined07:34
_ikke_ no?07:34
lb1a ok here's the deal: a computer, that is portable07:35
and it already has a keyboard attached to it07:35
minim left07:35
awc737 left07:35
_ikke_ genious07:35
brilliiant07:35
lb1a and a monitor,too07:35
_ikke_ no07:35
lb1a screen?07:35
matanya_ joined07:36
lb1a and the best: it's a flat screen :P07:36
kama_ lb1a: seems i should name that non branch at first07:36
switch back to master branch, then merge that branch to master branch:)07:37
lb1a so throw away this shitty tablet, and run to your next walmart/whatever and buy a decent laptop for only 299$$$ ^^07:37
bruce-zu left07:37
lb1a kama_, depending on what you did, that is a good solution07:37
awc737 joined07:37
arvind_khadri joined07:39
Guest95586 joined07:41
Dreadnaught joined07:41
lite_ left07:42
diegoviola left07:42
Dreadnaught left07:43
robstanley left07:43
peter5 joined07:43
sm0ke left07:43
maestrojed left07:44
maslowbeer left07:44
sm0ke joined07:45
_iron joined07:46
jon_r left07:46
vigs left07:47
Asenar joined07:47
chirayuk joined07:48
jon_r joined07:48
reskp left07:49
reskp_ joined07:49
sm0ke left07:53
reskp_ left07:53
starfox21 joined07:55
sm0ke joined07:55
lite_ joined07:57
marhaban joined07:57
starfox21 left07:58
dharriga1 left07:58
dharriga1 joined07:58
dharriga1dharrigan07:58
s0undt3ch left07:59
jfinn joined08:00
rainbyte left08:00
Robarelli left08:02
kbart joined08:02
pantsman joined08:04
pantsman left08:04
pantsman joined08:04
s0undt3ch joined08:05
kate_r left08:05
weiyang left08:06
tortal joined08:07
dyng left08:07
Dudalus left08:08
dyng joined08:08
Katafalkas left08:09
Katafalkas joined08:09
Robarelli joined08:10
Katafalkas left08:10
Katafalkas joined08:11
nuclearkitten joined08:11
dyng left08:13
Dudalus joined08:13
ej joined08:13
yacks joined08:13
Katafalkas left08:14
Katafalkas joined08:14
juril joined08:15
kenperkins_ joined08:15
Katafalkas left08:16
Katafalk_ joined08:16
Katafalk_ left08:16
Katafalkas joined08:17
kenperkins left08:17
jargon joined08:17
darkmutt joined08:20
sig left08:20
Katafalkas left08:20
darkmutt would someone give me an example of how to test whether or not git push works on a server without any branches on it?08:20
Katafalkas joined08:20
tortal left08:21
Sonderblade joined08:22
dreiss_ left08:22
Sonderblade left08:22
Katafalk_ joined08:22
Sonderblade joined08:22
Katafalk_ left08:23
Katafalk_ joined08:23
bunbury left08:24
Katafalk_ left08:24
Katafalk_ joined08:24
dyng joined08:25
dyng left08:25
thiago left08:25
Katafal__ joined08:26
dyng joined08:26
Katafalkas left08:26
Katafalk_ left08:26
Katafalkas joined08:27
sig joined08:28
Anticom joined08:28
_Qman joined08:28
Davey joined08:28
darkmutt left08:29
howlymowly joined08:29
Katafalkas left08:29
Katafalkas joined08:30
stormwild joined08:31
ewnd9 joined08:31
Katafal__ left08:31
sylon left08:33
zarubin joined08:33
aChatir joined08:34
Daveygrumbles08:35
noname001__ joined08:36
pilif joined08:38
rat_thing joined08:38
atSetKey joined08:41
pantsman left08:41
Robarelli left08:41
el3ctron_ joined08:41
chirayuk left08:44
amcsi_work joined08:44
renumi joined08:44
terminalRepeat left08:46
rudak joined08:46
grumblesDavey08:49
moritz can't even think of a way to have a server without any branches on it08:53
FernandoBasso joined08:53
_ikke_ lol08:54
Katafalkas left08:54
ChanServ set mode: +v08:54
moritz well, except a server without any git repos, of course08:55
tatsuya_o joined08:55
Katafalkas joined08:58
leeN left08:58
lb1a moritz, but all the svn branches having a party :P08:58
mischief joined08:59
mischief hi08:59
lb1a mischief, !hi08:59
gitinfo mischief: [!welcome] Welcome to #git, a place full of helpful gits. If you have a question, feel free to just go ahead and ask—somebody should answer shortly. For more info on this channel, see http://jk.gs/git/ Take backups (type !backup to learn how) before taking advice.08:59
ChrisAnn joined08:59
mischief i just made some commits i dont want any more because i was trying to test a pre-commit hook, so i comitted some garbage09:00
how can i 'rewind' 2 commits?09:00
i didn't push to remote yet09:00
axrfnu mischief: git reset --hard HEAD~2109:00
err HEAD~109:01
or the like :(09:01
_ikke_ HEAD~209:01
sayanee left09:01
moritz or just git reset --hard $last_good_commit09:01
starfox21 joined09:01
noname001__ left09:01
mischief HEAD~2 means '2 commits behind the current one'?09:01
_ikke_ yes09:02
the seccond ancestor of HEAD09:02
mischief moritz: are you moritz bartl?09:02
_ikke_ so the parent of the parent of HEAD09:02
moritz you can preview with 'git log HEAD~2'09:02
mischief: no09:02
mischief haha09:02
i just deleted my pre-commit hook doing that09:02
is it gone, or can i go 'forward' again? :)09:03
axrfnu man git-reflog09:03
gitinfo the git-reflog manpage is available at http://jk.gs/git-reflog.html09:03
_ikke_ git reset --hard @{1}09:04
was the hook comitted?09:05
mischief i did, but then it was gone with the reset09:05
_ikke_ ok09:05
mischief i checked out the commit it was in (it said detached head mode), copied the shell script to tmp, then git checkout master09:05
so now i will commit it again since i figured out what was wrong before09:05
(the script wasn't marked +x)09:05
_ikke_ you can also do git checkout <commit> path/to/file09:06
GT left09:06
rainbyte joined09:07
atSetKey left09:08
kate_r joined09:10
mischief hm09:10
is it a good idea to 'git stash' in my pre-commit hook?09:10
and pop at the end, obviously09:10
rat_thing left09:11
_ikke_ what does the hook do?09:11
Robarelli joined09:11
mischief http://sprunge.us/iBBc?sh09:11
when i do this, the first command fails09:12
but i end up with some junk in my file now from the stash commands09:12
git diff after running the hook manually is http://sprunge.us/HCJY09:13
rat_thing joined09:13
Guest95586diegoviola09:14
Norm_ joined09:15
_Qman left09:15
jaseemabid joined09:16
rednaks joined09:17
intellix joined09:17
uslssqwertz_09:18
lifechamp joined09:18
rurufufuss left09:18
ewnd9 left09:18
amcsi_work hi09:19
mischief _ikke_: any ideas? :309:19
zbcm left09:19
amcsi_work is it correct that it's into the HTTP protocol that to make an HTTP proxy, you are going to need to dedicate an entire IP and Port to it?09:20
hence most implementations that let you use proxies (such as curl) only ask for an IP and Port if you want to use a proxy?09:20
mbear_nbr left09:20
matteo joined09:21
dbuch joined09:21
amcsi_work wrong channel09:21
G0re left09:22
shuaib joined09:22
daito left09:23
daito joined09:24
sqlnoob left09:25
sqlnoob joined09:26
pantsman joined09:26
khushildep joined09:27
daito left09:28
BiggFREE joined09:29
mikecmpbll joined09:29
el3ctron_ left09:29
MafooUK left09:29
mischief should i just not git stash in my pre-commit hook?09:30
lifechamp left09:30
MafooUK joined09:30
h_kon left09:31
osse is ./... a thing go understands?09:31
el3ctron joined09:31
rurufufuss joined09:31
mischief yea09:32
h_kon joined09:33
h_kon left09:34
osse mischief: seems strange to supress go's error output and then write your own warning saying "please check the output"09:34
jkremser joined09:34
jkremser left09:34
jkremser joined09:34
mischief it seems i had a git stash, but no outstanding changes on master09:35
Katafalk_ joined09:35
mischief so 'git stash' was a no-op09:35
but git stash pop was popping the old stash09:35
thats not what i wanted D:09:35
pantsman left09:35
Katafalkas left09:35
Katafalk_ left09:35
Katafalkas joined09:35
mischief the idea is to only run the tests on code market for commit09:36
marked09:36
osse I don't see why your pre-commit hook shouldn't work.09:37
Except you shouldn't have an extension09:37
mischief the file is .git/hooks/pre-commit09:37
h_kon joined09:37
mischief it's a symlink to ../../pre-commit.sh09:37
and that file is being committed to the repo once it works09:38
atSetKey joined09:38
y_nk left09:39
mischief osse: the problem is that if there is files staged, and no file is changed but unstaged, *and* something in the stash, the pre-commit hook will do 'git stash' but thats no-op, then 'git stash pop' which will pop the _old_ stash09:39
y_nk joined09:39
y_nk left09:39
y_nk joined09:39
mischief so.. i need to only stash pop if stash actually stashed something09:39
Hetu joined09:39
mischief you see?09:39
Davey left09:41
victorbjelkholm joined09:41
Robarelli left09:43
glebihan_ joined09:44
Robarelli joined09:44
barq joined09:44
Davey joined09:44
daito joined09:46
rethus joined09:46
cbreak-work joined09:47
atSetKey left09:47
glebihan left09:47
rethus I have master, and Branch A, B and C.09:48
Say i have changed something in A and finish my work, i merge it to MASTER.09:48
Whats now the right way, if i work on B. Should i MERGE master into B, or have i to use REBASE in this case?09:48
babilen joined09:48
tango_ left09:48
glosoli left09:49
King_Hual joined09:50
rudak left09:50
tango_ joined09:51
BiggFREE left09:51
albel727 left09:52
NanoArrow left09:52
rudak joined09:52
mischief stupid git.09:54
PeterBooker joined09:55
rethus mischief ??09:55
masak well, that's why it's called "git", isn't it? because it's stupid.09:56
manpage even says: "git - the stupid content tracker"09:56
demiurgo joined09:57
sonOfRa git can mean anything!09:58
mklappstuhl joined09:59
tvw joined10:01
irqq joined10:01
rethus left10:02
albel727 joined10:02
sm0ke left10:02
King_Hual left10:02
King_Hual joined10:02
sm0ke joined10:03
rat_thing left10:05
shoshin left10:05
shoshin joined10:08
dsdeiz_ joined10:08
dsdeiz left10:09
harish left10:09
onethfour3 joined10:11
jaseemabid left10:12
Cornlius joined10:13
ryan_turner|MTW joined10:13
multiverse left10:13
Cornliusmultiverse10:13
raijin left10:13
wagle left10:14
Davey left10:14
dccc left10:14
raijin joined10:14
wagle joined10:14
dccc joined10:14
cagedwisdom left10:15
onethfour left10:15
kate_r left10:15
zarubin left10:15
cagedwisdom joined10:15
hyperair left10:16
PigeonFriend joined10:17
noname001__ joined10:20
ryan_turner|MTW left10:22
h0bbit_ left10:23
h0bbit left10:24
FernandoBasso left10:24
ryan_turner|MTW joined10:24
osse mischief: use git diff to check if there is anything to stash10:25
and if there isn't, never pop10:25
carbohydrate joined10:26
kate_r joined10:26
rat_thing joined10:26
h0bbit_ joined10:27
gzg joined10:27
dsdeiz joined10:28
dsdeiz_ left10:29
the_cybersphinx joined10:30
mithro-work joined10:31
mithro-work is there a way to find out why git thinks my .git directory is no longer a gitdir?10:31
osse mischief, beware, contains massive amouns of awesomeness within: http://sprunge.us/IAID10:31
mischief o.o10:32
osse heh, I forgot to actually git stash10:32
mischief yes that would help ^^10:32
chairabanta joined10:32
osse http://sprunge.us/LXVV10:33
gzg left10:33
Hetu my local master is two commits ahead of its remote. Can I still make these two commits part of a new branch?10:33
youlysses left10:33
mischief osse: so i put this at the top of the script10:33
osse mischief: I think that could work, yep. Seems to me you always want to pop the stash right before exiting10:33
mischief yes10:34
but only if a stash was pushed :P10:34
DoniRS joined10:34
osse which this achieves10:34
mishok13 left10:34
osse you might have to change #!/bin/sh to #!/bin/bash10:34
mischief oh.. :s10:35
mithro-work I've never seen git fail to recognize a .git directory before :/10:35
mishok13 joined10:35
osse mithro-work: maybe some of the GIT_ environment stuff is set10:36
cmn the .git directory isn't the issue, it's the contents10:36
osse mithro-work: try echo $GIT<tab><tab>10:36
lng left10:36
mithro-work "export | grep GIT" returns nothing10:36
osse mischief: but proably not, if sh is a symlink to bash anyway10:36
mischief no this is real sh10:37
cmn what's in that .git dir then?10:37
starfox21 left10:37
slassh joined10:37
mischief osse: i use git on several systems. openbsd and linux, mainly10:37
rednaks left10:37
mischief but this seems to work on openbsd sh10:37
Guest83628 joined10:38
osse mischief: isn't sh a symlink to zsh there? :P10:38
mithro-work It looks like a valid .git repository to me. I was happily working away on this repository and my machine power cycled. Now git doesn't think its a git repository and won't tell me why10:38
mischief osse: no ._.10:38
cmn strace would tell you10:38
osse mischief: good news: trapping the "signal" EXIT is POSIX sh blabla. So it'll probably work everywhere10:39
mithro-work Last thing it opens is .git/HEAD then it says it's not a git repository10:40
maslowbeer joined10:40
AzizLight joined10:41
cmn so what did you find out about it?10:41
AzizLight left10:42
mithro-work ahh ha, I tried replacing HEAD's content with a value from refs/heads/ and it seems to recognise it now10:42
mischief osse: do you think i should add --keep-index to stash?10:42
osse mischief: oh, definitely. I forgot about that10:42
mischief ok10:42
osse mischief: use the same git stash commands you already use10:42
mischief well, the idea is to test staged files10:43
without --keep-index staged files would be stahed10:43
atSetKey joined10:43
AzizLight joined10:44
kewah left10:44
AzizLight Hello everybody10:44
_nova joined10:45
AzizLight is there a command to add all files to the staging area and remove the ones that have been deleted please? (Essentially a combination of git add and git rm)10:45
jaseemabid joined10:45
marhaban left10:45
mischief git do-all-the-things10:46
chairabanta left10:46
osse AzizLight: add -A10:46
maslowbeer left10:46
Robarelli left10:47
daito left10:47
osse mischief: http://sprunge.us/FGCh10:47
dsdeiz_ joined10:47
daito joined10:47
AzizLight osse: cool, thanks a lot ;)10:48
dsdeiz left10:48
atSetKey left10:48
osse mischief: but I would reconsider silencing stderr10:48
kc8qvp_ left10:48
rat_thing left10:48
osse ie. dropping 2>&110:48
dyng left10:49
dyng joined10:50
mklappstuhl left10:51
aChatir left10:51
mischief osse: i'll see how this goes10:52
daito left10:52
mischief https://github.com/PacketFire/go-ircd10:52
thanks again, now we wont have fail code committed (hopefully)10:52
_nova left10:53
_nova joined10:54
grilix left10:54
dyng_ joined10:54
imarcusthis- joined10:54
dyng left10:55
lng joined10:56
dyng_ left10:56
dyng joined10:56
grilix joined10:58
osse no credit to me? :( Hee hee10:59
starfox21 joined10:59
donmichelangelo left11:00
dong left11:00
mischief osse: sorry11:00
osse: file an issue >:)11:01
donmichelangelo joined11:01
dyng left11:01
ewnd9 joined11:02
Xethron left11:02
kcj left11:02
rudak left11:02
slassh left11:05
dbuch left11:06
diegoviola left11:06
Katafalk_ joined11:06
Katafalkas left11:07
dsdeiz joined11:08
dsdeiz_ left11:09
cbreak-work left11:12
stormwild left11:12
stormwild joined11:12
frgtn left11:12
haukur joined11:12
frgtn joined11:13
haukur I have a master and a dev branch. I wanted to merge dev into master, as I've usually done, but after doing so git diff master (from dev) shows that there's still a difference between the two branches (one simple line).11:14
How can I fix this?11:15
arand__ was that line added/modified in dev or in master?11:16
kewah joined11:17
CheckDavid joined11:17
frgtn left11:17
haukur I'm pretty sure it was modified in dev, at least it should've been. One second.11:17
vilesoft joined11:18
vilesoft left11:18
asQuirreL joined11:20
Katafalkas joined11:21
D-Boy joined11:21
kirsty joined11:22
cmpera joined11:24
Katafalk_ left11:24
hpm joined11:27
TomyWork left11:28
mikecmpbll left11:29
raonyguimaraes joined11:29
twoface88 joined11:31
Ropt joined11:31
Ropt Is this the appropriate channel to ask questions about GitLab?11:32
haukur left11:32
Ropt Oops I found the #gitlab channel, sorry ignore my question please11:32
Droolio joined11:32
hpm left11:35
sdx23 left11:35
tmcmahon joined11:35
nemesit|znc left11:35
Roots47 joined11:35
luc__ left11:36
Roots47 left11:37
Happzz left11:37
King_Hual left11:38
farn left11:38
Roots47 joined11:38
King_Hual joined11:38
Cerise left11:40
carbohydrate left11:41
HenryG joined11:42
mklappstuhl joined11:43
atSetKey joined11:43
LuxuryMode joined11:44
ojacobson left11:45
cannonball joined11:46
VictorCL joined11:46
bunbury joined11:47
dbuch joined11:47
tmcmahon left11:47
irqq left11:47
ThomasCle joined11:48
vipzrx joined11:48
atSetKey left11:48
twoface88 left11:49
NanoArrow joined11:49
dhruvasagar left11:50
jaseemabid left11:50
kcj joined11:51
merlin83_ left11:51
irqq joined11:52
Hetu hi, can I enforce a three way merge when my feature branch is just ahead of master? I don't want the feature commits to get rebased into master.11:52
_ikke_ git merge --no-ff11:53
a fast-forward merge doesnt rebase anything11:53
dsdeiz_ joined11:53
dsdeiz left11:54
Hetu thanks a lot11:54
right, by "rebase" I probably meant them each and every commit being merged into master11:55
NanoArrow left11:55
vipzrx left11:55
Happzz joined11:57
LuxuryMode left11:57
nemesit|znc joined11:57
farn joined11:57
Cerise joined11:58
beautifulmind joined11:58
dhruvasa1ar joined11:58
_ikke_ The only thing that happens is that a branch (a pointer) gets moved11:58
frgtn joined11:59
stamina left11:59
sdx23 joined11:59
beautifulmind left11:59
beautifulmind joined12:00
gzg joined12:00
Katafalkas left12:01
h_kon left12:01
Katafalkas joined12:01
h_kon joined12:02
vipzrx joined12:02
dhruvasa1ar left12:02
Katafalkas left12:02
jon_r left12:03
dhruvasagar joined12:03
blackjack joined12:04
blackjack left12:04
Kulrak joined12:05
blackjack joined12:05
blackjack left12:05
[emmajane]emmajane12:05
blackjack joined12:06
blackjack left12:06
dsdeiz_ left12:06
dsdeiz joined12:06
diegoviola joined12:08
asQuirreL left12:09
nuclearkitten left12:10
h_kon left12:10
ozette joined12:11
h_kon joined12:11
ojacobson joined12:11
jon_r joined12:12
Entomo left12:12
mklappstuhl left12:12
mklappstuhl joined12:12
Man joined12:13
panpainter joined12:13
v0n left12:14
stormwild left12:14
CodeShark left12:16
mklappst_ joined12:16
mklappstuhl left12:17
CodeShark joined12:17
CodeShark left12:18
mklappst_ left12:20
Jackneill joined12:20
rethus joined12:20
osse mischief: no worries. it probably doesn't work anyway12:20
rethus have this error:12:20
mklappstuhl joined12:21
rethus git show12:21
error: object file .git/objects/6b/fecc157959895b732e237f276dc7a84142a27f is empty12:21
fatal: loose object 6bfecc157959895b732e237f276dc7a84142a27f (stored in .git/objects/6b/fecc157959895b732e237f276dc7a84142a27f) is cor12:21
rupt12:21
what can i do to fix it12:21
grilix left12:22
breakingthings joined12:22
grilix joined12:23
reskp joined12:24
iveqy joined12:25
bitkiller joined12:25
mklappstuhl left12:25
jon_r left12:25
rfoust left12:26
hakril have you pushed this object ?12:26
grilix left12:27
Kulrak left12:27
g0bl1n joined12:28
kenperkins_ left12:28
hakril (if you have no idea, you can verif this by cloning again your repos and using 'git rev-parse 6bfecc157959895b732e237f276dc7a84142a27f')12:28
aspiers left12:28
mklappstuhl joined12:28
aspiers joined12:29
rat_thing joined12:29
Devastator left12:29
Devastator joined12:29
Saurabh_ joined12:31
vipzrx left12:32
rethus hakril: the horrible true is, that this is only a local repo12:32
iamjarvo joined12:32
freeed joined12:32
rethus no copies at all12:32
m0viefreak joined12:32
Squarism joined12:33
rethus before i had a OS freeze and to restart (without shutdown)12:33
sdx23 left12:35
kenperkins joined12:36
iveqy rethus: you do know that your OS doesn't write things to disc instantly and when you save something it's only i RAM and will be lost forever if you force a reboot or if the system freeze12:36
carbohydrate joined12:36
rethus iveqy yes. but this answer not help in any direction.12:37
Saurabh_ left12:38
rethus I didn't ask why this happend, i ask how to fix it to got git back to work12:38
nemesit|znc left12:38
freeed left12:38
iveqy rethus: I was disconnected so I couldn't read your question. However a freeze can be fatal12:38
at least git let you know about it12:38
nemesit|znc joined12:40
Milossh left12:41
rethus error: object file ./objects/6a/b1aeda549cdd998b4069f6d40f6ad5063164c9 is empty12:42
fatal: loose object 6ab1aeda549cdd998b4069f6d40f6ad5063164c9 (stored in ./objects/6a/b1aeda549cdd998b4069f6d40f6ad5063164c9) is corrupt12:42
what if i only remove this file12:42
freeed joined12:42
rethus or fill it with content of another one?12:42
ciampix left12:42
sdx23 joined12:42
iveqy rethus: have you runned git fsck and git gc?12:42
rethus thats the result of git fsck12:43
EdGruberman joined12:44
atSetKey joined12:44
nnyk_ joined12:44
EdGrubemran left12:45
rnsanchez joined12:46
Milossh joined12:46
nova_ joined12:46
freestyl3r joined12:47
sony left12:47
rethus left12:48
glosoli joined12:48
atSetKey left12:49
_nova left12:49
vipzrx joined12:49
vipzrx left12:49
Quanteek joined12:50
dsdeiz left12:50
rethus joined12:50
Quanteek left12:50
rethus I have now removed 4 corrupted objects and run git fsck --full12:50
than i got:12:51
vipzrx joined12:51
rethus Checking object directories: 100% (256/256), done.12:51
error: HEAD: invalid sha1 pointer 6bfecc157959895b732e237f276dc7a84142a27f12:51
error: refs/heads/master does not point to a valid object!12:51
error: 6ab1aeda549cdd998b4069f6d40f6ad5063164c9: invalid sha1 pointer in cache-tree12:51
vipzrx left12:51
sm0ke left12:51
Robarelli joined12:51
tvw left12:51
iamjarvo left12:52
freeed left12:52
iamjarvo joined12:52
tvw joined12:53
TheBrainWork joined12:54
dsdeiz joined12:54
haaja left12:54
haaja joined12:55
HumanSky joined12:55
kmctown joined12:56
freeed joined12:56
iveqy rethus: I would say, move it manually12:56
rethus to?12:56
from?12:56
iveqy rethus: to the latest commit you've that's still there12:56
seems like you just removed your latest commit12:57
nuclearkitten joined12:57
Burer joined12:57
Burer left12:57
Burer joined12:57
mikecmpbll joined12:57
rethus don't see what you mean. What should i move12:57
rfoust joined12:58
rethus if i remember right, last thing i've done was a rebase12:58
DanielKarp joined12:58
iveqy a branch is a pointer to a commit12:59
your branch master points to a commit you've removed12:59
you need to point it to acommit that exists12:59
grilix joined13:00
rethus thats the last entry in my log:13:01
1d5dcf311b96fcbfd27d0ad017854d9e2876a0e8 6bfecc157959895b732e237f276dc7a84142a27f Samuel Suther [email@hidden.address] 1381399067 +0200 merge refs/heads/#66Buttonbeschriftung: Merge made by recursive.13:01
psynor joined13:01
rethus exactly my broken one ... 6bfecc....13:02
so how can i now set a new pointer13:02
freeed left13:02
rjhunter joined13:03
delianides joined13:03
iveqy rethus: man git reset but in this case I would have just edited the file .git/refs/heads/master13:03
gitinfo rethus: the git-reset manpage is available at http://jk.gs/git-reset.html13:03
shoshin left13:04
rethus .git/refs/heads is emty13:04
hoschi left13:04
rethus no file in there13:04
freeed joined13:05
sr78ger left13:05
raijin left13:06
jerius joined13:06
rethus k, got thin now: http://pastebin.com/KJ0xHc7f13:06
nessib left13:07
Xethron joined13:07
iveqy no files at all? What's in your .git/refs?13:08
rethus folders: heads, stash tags13:08
jaseemabid joined13:09
rethus whats with my pastebin, isnt it a step forward?13:09
jast if the branch doesn't exist in .git/refs/heads/, it probably lives in .git/packed-refs instead13:09
(which is a single file)13:10
iderik joined13:10
rethus http://pastebin.com/sVrFF5mS13:11
thats the content of the file13:11
decotii joined13:11
iveqy jast: I thought the current branch never should be packed?13:12
rethus: there you can see refs/heads/master point to 6bfecc157959895b732e237f276dc7a84142a27f13:12
nuclearkitten left13:12
rethus so should i replace it by 1d5dcf311b96fcbfd27d0ad017854d9e2876a0e813:13
iveqy rethus: I'm not sure with that you should replace it with, do a backup and try13:13
barq I changed .gitignore to ignore *.class files, but git status still shows them as modified. How can I refresh?13:14
nuclearkitten joined13:14
buibex joined13:14
geekbri joined13:15
axrfnu barq: git rm --cached on the *.class files13:15
barq: that'll remove them from the indexd13:16
*index13:16
jast barq: !ignoretracked13:16
gitinfo barq: [!ignore_tracked] Git only applies ignore patterns to untracked files. You can't use ignore patterns to ignore changes to files that are already tracked by git. Still, see https://gist.github.com/1423106 for ways people have worked around the problem.13:16
jast if you want to stop tracking the files, run 'git rm --cached' on them13:16
iderik left13:16
rethus iveqy: thanks a lot. You save my day.13:17
seems to work now13:18
ThomasLocke left13:18
GODDOG joined13:18
rethus so what's a good way to got even local git repos saved?13:18
shoshin joined13:19
YannH joined13:19
rethus I have a shop-project local, but no git on the Live-Server. So should i anyway copy the .git-Folder to the Server to be save?13:19
v0n joined13:20
iamjarvo left13:20
iamjarvo joined13:21
grilix left13:21
DolphinDream joined13:21
matanya_ left13:21
Guest26260 joined13:22
Fandekasp left13:22
sdx23 left13:23
sdx32 joined13:23
Wilduck joined13:24
Wilduck left13:24
rethus1 joined13:24
momomomomo joined13:24
threesome left13:24
rat_thing left13:24
diegoviola left13:24
barq How can I rm --cached everything that's listed? rm --cached * had rather undesirable results.13:24
Robarelli left13:25
momomomomo left13:25
iamjarvo left13:25
sonOfRa listed?13:26
panpainter left13:26
barq listed did not match any files13:26
Robarelli joined13:26
tbmiller joined13:27
m0ltar joined13:27
rethus left13:27
rat_thing joined13:27
nemesit|znc left13:27
nemesit|znc joined13:27
iveqy rethus1: nice to hear =). I suggest you clone your local repo and work there instead. A corrupt git repo won't care any corruption over a clone13:28
tbmiller left13:29
iveqy rethus1: the best way for a backup IMHO is to have a remote repo to push to somewhere (bitbucket gives you one for free) however there's always git clone --mirror13:29
tbmiller joined13:29
tbmiller left13:30
|Freeman| joined13:30
tbmiller joined13:30
Dougie187 joined13:30
rethus1 left13:31
rethus1 joined13:31
rob_w left13:31
axl_ joined13:32
LuxuryMode joined13:33
AaronMT joined13:33
rethus1 left13:34
raijin joined13:34
lb1a left13:34
rethus joined13:34
rethus ok. good idea. for first short solution, i could clone the repo to another hdd, and use this one as "kind of" remote repo?13:34
tdussa joined13:34
apipkin joined13:34
Arokh left13:35
cbreak-work joined13:35
fridim_ joined13:35
h_kon left13:35
gitinfo set mode: +v13:35
Guest26260diegoviola13:35
Guest83628 left13:35
tdussa Does anyone have any experience with git bundles?13:36
I seem to be unable to figure out how to prune a bundle by date properly.13:36
moritz 9913:37
LuxuryMo_ joined13:37
Xiti left13:37
moritz sorry, keyboard hung13:37
LuxuryMode left13:37
Xiti joined13:38
lumberg joined13:38
kukks joined13:38
kate_r left13:38
barq I am trying to git rm --cached on a .metadata/ directory, but git says: did not match any files. Is there a problem with .dirs?13:39
lumberg left13:39
Arokh joined13:39
AaronMT left13:39
frio80 joined13:39
jast barq: use -r13:40
barq I have13:40
jast (*with* --cached)13:40
yahoololman joined13:40
jast well, you didn't say :}13:40
HumanSky left13:40
barq git rm -r --cached path/.metadata/13:40
v0n left13:40
jast and that complains about not matching anything?13:41
apipkin left13:41
barq .metadata did not match any files13:41
jast is this still the same question? i.e. does that dir contain files that currently show up as 'modified'?13:41
jaseemabid left13:41
barq it shows as untracked files13:41
Guest32557 joined13:42
jast oh. well, you can't untrack files if they're already untracked ;)13:42
moritz 'git rm' is only for tracked files13:42
barq oh, so manually add to .gitignore then -.-13:42
jast 'git rm --cached' and .gitignore are related but different13:42
moritz use regular 'rm' to delete untracked files13:42
tdussa Rephrasing my problem: Am I mistaken to believe that a "git bundle create" command should only include the commits that, say, a "git log" command would show if the same limitations are applied?13:42
Xiti left13:42
Voting joined13:42
lite_ left13:42
sdx32 left13:43
el3ctron left13:43
lite_ joined13:43
tdussa So if I say "git log --since 2013-10-01", and it shows, say, one revision, then shouldn't that be all that is included in a "git bundle create Foo --all --since 2013-10-01"?13:43
sdx23 joined13:43
jast .gitignore is for stopping untracked files from being listed/added; 'git rm --cached' is for getting rid of the 'tracked' status.13:43
PerlJam tdussa: sounds right.13:44
barq git rm -r doesn't find the dir either13:44
stamina joined13:44
Voting So, after I fetch from something that is NOT my origin, how do I do the merge? I want to something like "git merge -Xtheirs dev" but it was dev from the repo that I just did the fetch from that I want to do the merge. Is the question clear?13:44
jast barq: if it's all untracked, that makes sense13:44
tdussa PerlJam: That's what I thought, but the bundle includes way more.13:44
PerlJam barq: git also doesn't track dirs per se13:44
jast tdussa: compare to 'git log --all --since ...', not 'git log --since ...'13:44
tdussa Ah.13:44
jast: THX.13:44
jast and if you don't want --all, don't use --all ;)13:44
tdussa Good point, of course.13:44
HumanSky joined13:44
AaronMT joined13:44
atSetKey joined13:44
el3ctron_ joined13:44
tdussa jast: Same effect, though.13:45
frio80 A colleague asked my to rebase my commits into a single commit and open a pull request so he can merge my changes. Of my 3 commits, the 1st one is simply merged a pull request from his repo to 'stay up to date'. Do I need to squash all those commit as well?13:45
jast Voting: have you added a remote for the other repo? (i.e. git remote add foo ...)13:45
kermit left13:45
Destos joined13:45
Voting jast: do I need to? I did the fetch already.13:45
barq So how can i get rid of those untracked files in the status?13:45
PerlJam barq: .gitignore :)13:45
cwillu_at_work left13:46
jast Voting: so you did a 'git fetch <url>'?13:46
diegoviola left13:46
Voting PerlJam: any other options beside .gitignore ?13:46
jast: yes13:46
jast Voting: he wasn't talking to you, actually :)13:46
barq Is it good practice to gitignore .gitignore?13:46
Voting jast: I know but I have junk in my git status also...13:47
jast barq: not really. .gitignore is for shared ignore patterns. if you want extra ignore patterns for yourself, put them in .git/info/exclude13:47
barq ok, thanks13:47
Xiti joined13:47
jast Voting: the problem with fetching 'anonymously' is that it fetches all branches and stores them in FETCH_HEAD; you can't really merge a specific of those branches then13:47
PerlJam Voting: why do you want something other than .gitignore ? IS there something wrong with that solution?13:47
yahoololman left13:48
jast if you're okay with a bit of manual work, do a 'cat .git/FETCH_HEAD', find the right branch, and merge by commit ID13:48
lite_ left13:48
Voting PerlJam: .git/info/exclude does look like the right thing for just junk...13:48
jast in general I recommend creating a remote, fetching that, and then 'git merge theremote/thebranch'13:48
Voting jast: I can find the ID by looking at the source repo that I pulled from, right?13:49
jast sure13:49
PerlJam Voting: well, "junk to you, for this repo". If it's "just junk" and you think everyone using your repo will have the same idea of "junk" .gitignore is a good option13:49
harobed_ left13:49
jast and FETCH_HEAD knows it, too, until you fetch something else :)13:49
atSetKey left13:49
PerlJam Voting: adding another remote like jast says is way easier to deal with. (fwiw)13:50
harobed_ joined13:50
jast for one-off merges there's nothing wrong with doing it the less easy way if it saves a bit of time13:50
but the next time you do something like this, creating a remote will probably be easier13:50
Voting jast: so, assuming my comit is 4321, what do I type to kick off the merge?13:50
jast 'git merge 4321'13:50
Voting jast: git merge 4321 -Xtheirs ?13:51
panpainter joined13:52
Voting jast: do I put in the branch somewhere?13:52
PerlJam one-off merges are like one-off code; you almost always need to use it more than once. (IMHO)13:52
bamj0rb joined13:52
jast no need. merge doesn't care about the source branch, it simply resolves the branch to its topmost commit13:52
gitinfo set mode: +v13:53
AaronMT left13:53
jast and the target is always the branch you have checked out, so no name needed for that, either13:53
Voting jast: I'm grateful for your support!13:53
jast you may want to mention the source in your merge commit message, though13:53
for posterity13:53
you're welcome :)13:54
NanoArrow joined13:54
JohnBat26 left13:55
grilix joined13:55
marhaban joined13:55
Xethron left13:55
Voting jast: you rule! So much easier than I was GOING to do.13:56
marhaban left13:56
jast 's all a matter of experience13:57
and you get a lot of experience if you hang around here :)13:57
(and actually do stuff yourself from time to time, I suppose)13:57
kate_r joined13:57
Wilduck joined13:58
soee left13:58
saurabh joined13:58
Robarelli left13:59
mizu_no_oto joined13:59
donmichelangelo left14:00
VictorCL left14:00
juvenal_ joined14:00
donmichelangelo joined14:00
mFacenet joined14:02
juvenal left14:02
juvenal_juvenal14:02
buibex left14:04
aChatir joined14:04
buibex joined14:04
herdingcat joined14:05
ThomasCle left14:05
Voting this is a great room! Now, what is easier when I set up more "remotes" than just the one I cloned off of?14:05
babilen Voting: It's called "channel" on IRC, but yeah :)14:05
Guest54977 joined14:06
sqlnoob left14:06
fridim_ left14:07
buibex_ joined14:08
jnavila left14:08
jnavila_ joined14:08
irqq left14:08
kewah left14:08
buibex left14:09
nnyk_ left14:09
ThomasCle joined14:09
marhaban joined14:09
mizu_no_oto left14:09
comjf left14:10
rob_w joined14:10
robbyoconnor left14:10
iamjarvo joined14:10
rpg joined14:11
glosoli left14:11
mizu_no_oto joined14:12
beautifulmind left14:13
fragamus left14:14
asQuirreL joined14:14
Voting babilen: lol - I knew that! I'm just not that careful with my words... What are the best books and websites to really understand git so I'll be more efficient? I LOVE http://marklodato.github.io/visual-git-guide/index-en.html14:14
What else should I be reading?14:14
cwillu_at_work joined14:15
jast depends on what kind of approach you like14:15
!doc14:15
gitinfo A list of useful documentation of all kinds is here: http://git-scm.com/documentation -- or try the wiki at http://git.wiki.kernel.org/. Also try typing "!book" "!cs" "!bottomup" "!parable" "!best_practices" or "!vcbe" or "!designers" here in IRC. !book is probably the most helpful.14:15
jast I like !gcs for an explanation of all the data structures and implications from that14:15
gitinfo [!concepts] "Git Concepts Simplified" explains the basic structures used by git, which is very helpful for understanding its concepts. http://gitolite.com/gcs/14:15
Voting jast: I am not clueful enough to have an "approach" that I am aware of. (Beside "keep it simple")14:15
Guest54977 left14:16
Voting jast: what are the possible "approaches" one could choose among?14:17
funfunctor left14:18
NanoArrow left14:18
jast well, I mean... are you a computer scientist or mathy person? we have something for that. are you not much of a developer at all? we have something for that. do you think you might benefit from seeing the building blocks of git? we have something for that. etc.14:18
frio80 left14:18
Robarelli joined14:19
Roots47 left14:19
saurabh left14:20
asQuirreL left14:20
phile joined14:21
wildfire joined14:21
druonysus left14:21
juril left14:21
ehmatthes joined14:21
wildfire Hi, is there a way to mark a local branch as something that should not be pushed to a remote location?14:21
v0n joined14:22
tang^ joined14:22
lov no, I don't believe so.14:23
but, wait for the rest of the brain trust to wake up :)14:23
bklane joined14:23
ezakimak_work left14:23
papegaaij left14:24
merlin83_ joined14:24
merlin83_ left14:24
merlin83_ joined14:24
carbohydrate left14:26
hholtmann joined14:26
kewah joined14:26
Swayz joined14:28
canton7 wildfire, no, there isn't. if you look at push.default in man git-config, there are options that stop all branches being pushed automatically, so a branch won't be pushed unless you explicitely push it14:28
gitinfo wildfire: the git-config manpage is available at http://jk.gs/git-config.html14:28
iveqy canton7: only tracking branches will be pushed anyway14:28
so yes, a normal branch won't be pushed. or do I miss something big here?14:29
canton7 wildfire, ooh, no I remember something. You can set branch.<name>.pushremote to "Don't push here you numpty" or something I seem to recall? That'll cause pushes to fail14:29
marhaban left14:29
OOPMan left14:29
canton7 iveqy, I was assuming that this might be a branch which does exist on the remote, but which he doesn't want to push14:29
babilen Voting: I liked http://git-scm.com/book14:29
barq left14:29
canton7 iveqy, well, by default (on older git versions) matching branches are pushed - not tracking branches.14:30
Voting babilen: Tx! Anything else?14:30
canton7 !doc !book14:30
gitinfo A list of useful documentation of all kinds is here: http://git-scm.com/documentation -- or try the wiki at http://git.wiki.kernel.org/. Also try typing "!book" "!cs" "!bottomup" "!parable" "!best_practices" or "!vcbe" or "!designers" here in IRC. !book is probably the most helpful.14:30
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 !parable14:30
canton7 I especially liked bottomup14:30
rainbyte16 joined14:30
aChatir1 joined14:31
iveqy !talks (I like Jessicas)14:31
gitinfo Some good video talks about Git: [yt] http://goo.gl/z72s (Linus Torvalds: History&Concepts); [yt] http://goo.gl/R9H2q (Scott Chacon: Git basics, live examples); http://vimeo.com/35778382 (Randal Schwartz: Git basics, descriptional); http://vimeo.com/46010208 (Jesica Kerr: Git basics, descriptional)14:31
boboc joined14:31
Man left14:31
Voting thanks everyone!!!14:31
asQuirreL joined14:31
wrouesnel joined14:32
petey joined14:32
canton7 (!bottomup)14:32
gitinfo 'Git from the bottom up' starts with explaining the building blocks of git and proceeds to tell you how they fit together. http://ftp.newartisans.com/pub/git.from.bottom.up.pdf (http://ikke.info/git.from.bottom.up.pdf)14:32
aChatir left14:32
xjiujiu left14:32
herdingcat left14:33
Voting perhaps I know enough now to read that gbo thing!14:33
AaronMT joined14:34
onethfour3 left14:34
babilen Hmm, why isn't the bot answering to private requests? I tried "/msg gitinfo parable" and got nothing. Do I *have* to use it in the channel and spam everybody else?14:34
onethfour joined14:35
canton7 babilen, you forgot the !14:35
lov 10:35:12 -!- Irssi: Starting query in freenode with gitinfo14:35
10:35:12 <lov> !parable14:35
10:35:12 -gitinfo(jast@infobot.gitrecipes.de)- 'The git parable' provides some good reasoning behind git. http://tom.preston-werner.com/2009/05/19/the-git-parable.html14:35
gitinfo 'The git parable' provides some good reasoning behind git. http://tom.preston-werner.com/2009/05/19/the-git-parable.html14:35
onethfour I have a bunch of modified files. How do i return my branch to the state of the last commit14:35
lov yeah, don't forget the !14:35
Dudalus left14:35
qsusOFFcsqsuscs14:35
canton7 onethfour, 'git status' will tell you14:35
kcj left14:35
babilen canton7: That's the address character in the channel .. Why would you include that in the factoid names? But thanks, "/msg gitinfo !parable" works. Strange decision though ...14:35
gitinfo canton7: 'The git parable' provides some good reasoning behind git. http://tom.preston-werner.com/2009/05/19/the-git-parable.html14:35
babilen: you're welcome, but please note that I'm a bot. I'm not programmed to care.14:35
canton7 remember you can use directory names, . and * as well as filenames14:35
iveqy onethfour: git reset --hard HEAD14:36
onethfour thanks canton7 and iveqy14:36
canton7 babilen, the bot responds to a range of stuff, some of it starting with !14:36
onethfour what if i dont put --hard?14:36
canton7 then nothing happens14:36
byprdct joined14:36
canton7 (in this case)14:36
wildfire canton7: excellent - thanks14:36
canton7 reset --hard = move the branch *and* the working copy *and* the index to the named commit (in this case HEAD) - so the moving the branch bit is a no-op, but the rest takes effect14:37
iveqy babilen: !privmsg14:37
gitinfo babilen: You can get gitinfo keyword expansion (e.g. !doc or this one) sent directly to you by sending a private message to me: /msg gitinfo !doc. This avoids spamming the channel. Also see http://jk.gs/git/bot/trigger.php14:37
onethfour Now, how do I copy 1 file from another branch over to my current branch?14:37
babilen canton7: yeah, fair enough. Seems to be a strange design decision, but I won't argue the point. :)14:37
canton7 reset [--mixed] = move the branch and the index to the named commit, leave the working copy alone14:37
iveqy onethfour: man git checkout14:37
gitinfo onethfour: the git-checkout manpage is available at http://jk.gs/git-checkout.html14:37
canton7 again, the moving the branch bit is a no-op, so it'll just reset the index14:37
reset --soft = move only the branch, leaving the working copy and index alone. that's a complete no-op in this case14:38
kewah left14:38
babilen iveqy: yeah, I was simply surprised by the fact that I have to include the "!" as that should simply be necessary to address the bot in the channel (a lot of bots allow you to configure this "address character" and I wouldn't expect it to be necessary in a query. But thanks.14:38
canton7 onethfour, my preferred approach, and the one recommended by 'git status' is 'git checkout -- .'14:38
iveqy canton7: you know about !resets?14:38
gitinfo canton7: tl;dr of man git-reset: --soft moves HEAD, --mixed moves HEAD+index, --hard moves HEAD+index+work-tree, -- foo.txt will !unstage14:38
canton7 iveqy, I did not know that trigger, thanks14:38
!reset also14:38
gitinfo A good resource explaining git-reset is http://git-scm.com/2011/07/11/reset.html14:38
iveqy canton7: I learned it yesterday, I like it =)14:39
canton7 babilen, the bot also responds to 'man something', some wiki stuff, other docs, dot-prefixed commands to edit triggers, generate graphs, etc14:39
HereCas joined14:40
canton7 the stuff prefixed with '!' is a subset of the stuff it responds to, so keeping the prefixes keeps everything nice and unambiguous14:40
merlin83_ left14:40
canton7 (it also responds to new joiners, people saying things, and some other odd stuff - all in response to non-prefixed keywords)14:40
onethfour iveqy, so this: git checkout master~2 Makefile14:40
i would do git checkout <otherbranch> path/to/file14:41
wildfire canton7: unfortunately I can't find .pushremote as an option14:41
iveqy onethfour: what's stopping you?14:41
wildfire iveqy: git push origin -- seems to push *all* local branches14:41
onethfour ok i'll try that14:41
thansk14:41
canton7 wildfire, it's new I think? it's in man git-config14:41
gitinfo wildfire: the git-config manpage is available at http://jk.gs/git-config.html14:41
canton7 wildfire, set push.default to something sensible14:41
like I said at first14:41
wildfire whereas I want to configure which ones go, or require explicit branch names -- so that local things are not inadvertedly pushed up14:41
iveqy wildfire: no it won't. See canton7s answer to me earlier. It just push matching branches14:42
wildfire: if you create a branch with a different name than any branch that's on your remote it won't be pushed14:42
babilen canton7: I don't think it would be appropriate to continue this discussion here, but I still think it is a weird design decision. Either way I understand how gitinfo works now and will keep future "conversations" with it in private.14:42
canton7 wildfire, yes, that's what push.default configures. new git versions use 'simple' as the default value, but old git versions use the less intuitive 'matching'14:42
babilen, cool. it has its reasons, that's all. jast's the creator if you want to question him personally :P14:43
it might be worth making the '!' optional in privmsg to avoid confused people like yourself14:43
iveqy canton7: actually, git uses just a warning right now but will switch to simple when version 2.0 is released14:43
rpg left14:43
canton7 iveqy, oops, I mis-remembered14:43
babilen canton7: Nah, it works and that's what counts. I wouldn't have designed it that way but it is by no means horrible enough to warrant changing it now. :)14:43
iveqy babilen: gitinfo is on github and I'm sure jast likes pull requests =)14:44
grilix left14:44
canton7 github.com/jast/gitinfo iirc14:44
herdingcat joined14:44
merlin83_ joined14:44
merlin83_ left14:44
merlin83_ joined14:44
babilen canton7: fun, line after line of undocumented perl14:44
ThomasClem joined14:45
babilen (almost undocumented)14:45
canton7 isn't that par for the course in perl? :P14:45
dsdeiz_ joined14:45
atSetKey joined14:45
Norm_ left14:45
dsdeiz left14:45
iveqy babilen: good code doesn't need documentation they say ;)14:45
onethfour iveqy, it didn't work. I did git checkout mybranch path/to/file && git status and it says nothing changed14:45
canton7 maybe the file didn't change in mybranch?14:46
kbart left14:46
iveqy onethfour: !repro14:46
gitinfo onethfour: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.14:46
onethfour oh maybe14:46
iveqy onethfour: you can check that with git diff14:46
reskp__ joined14:46
fragamus joined14:47
p3lim left14:47
sebastianmarkow left14:47
p3lim joined14:47
teejmya joined14:47
wildfire canton7: ahh, my problem is my local git is a bit old in the teeth and doesn't have know 'simple'14:48
ThomasCle left14:48
sebastianmarkow joined14:48
wildfire canton7: thank you again though14:48
reskp left14:48
canton7 wildfire, set it to 'current' or 'upstream'14:48
(depending on your preferences)14:48
rat_thing left14:48
canton7 'simple' is like a combination of those two, that's even safer for newbies14:48
fragamus left14:49
raijin left14:49
p3lim_ joined14:49
wildfire canton7: cool, I'll read up on those (but upgrade in progress anyway)14:50
Robarelli left14:50
atSetKey left14:50
teejmya left14:50
canton7 wildfire, cool :)14:50
mFacenet left14:50
cmpera left14:51
p3lim left14:51
willwh joined14:52
d2dchat joined14:52
boboc left14:53
aChatir1 left14:53
normanrichards joined14:53
eddyb joined14:54
nnyk_ joined14:54
merlin83_ left14:55
eddyb is there a way to force submodule update to clone only the HEAD of a branch?14:55
setting the branch in .gitsubmodules and running git submodule update --init --depth=1 doesn't work :(14:56
glosoli joined14:56
v0n left14:57
eddyb it seems to fetch master14:57
v0n joined14:57
mikecmpbll left14:57
bunbury left14:57
buibex_ left14:57
willwh left14:58
cannonball Somehow, my local master has diverged in some small way from the origin/master. As a result, when I 'git push --tags', it generates a large (5MB) upload to the server, and then 20 or so tags (previous years of work) get rejected because it's non-fast-forward.14:58
bwreilly joined14:58
ej left14:58
buibex joined14:58
harobed_ left14:58
eddyb s/gitsubmodules/gitmodules14:58
cannonball I want to delete my local master, and then pull a fresh copy of master from origin. I'm trying to wrap my head around it, but I can't figure out how to get rid of whatever is fubar'd to cause this difference.14:58
fobius joined14:59
juvenal left14:59
gitinfo set mode: +v14:59
iveqy eddyb: !broken14:59
gitinfo eddyb: [!doesntwork] Sorry to hear it doesn't work, but how about some details? At this point we don't even know whether it did nothing, spit out an error message, or abducted your pet unicorn in a flying saucer. That makes it hard to troubleshoot – unicorn abduction requires a completely different solution than an error message, for instance. So, please be specific...14:59
Robarelli joined14:59
ToxicFrog cannonball: so, for just "delete local master and get a fresh copy" - git fetch; git checkout master; git reset --hard origin/master14:59
eddyb iveqy: git submodule update --init --depth=1 fetches the last commit from master, not the branch in .gitmodules15:00
lng left15:00
ToxicFrog cannonball: that said, it sounds like it has diverged in more than "a small way" if it's trying to push that many non-ff tags and the like.15:00
cannonball: are you sure you haven't rebased or filter-branched master?15:00
bklane left15:00
canton7 I'm surprised by the non-ff tags. Are you sure it isn't trying to push some other branches as well, which are being rejected?15:01
bklane joined15:01
rob_w left15:01
iveqy eddyb: the --depth thing is quite bad. Since git only allows fetching refs (and their parents) the --depth=2 thing to a submodule says "give me master and 1 parent". However if the superproject point to a submodule commit that's currently a grandparent to master the correct commit won't be fetched. So that's actually quite bad and git submodule --depth won't be usefull until git allows you to fetch commits directly and not just refs15:01
matthiaskrgr joined15:01
gitinfo set mode: +v15:01
Streward left15:01
mikecmpbll joined15:02
cannonball ToxicFrog: filter-branched, definitely not. rebased...I don't think so. The tags that it's complaining about are tags between 2005 and 2009. Everything since then is just fine.15:02
bklane left15:02
eddyb iveqy: the commit is the HEAD of the branch I set in .gitmodules. I want it to fetch from that branch, not master15:02
matthiaskrgr does someone know a regex to extract git commit hashes (long and short) from text ?15:02
v0n left15:02
bklane joined15:02
iveqy eddyb: --depth is a clone only command. So if your submodule already is clone, it won't effect the fetch15:02
ToxicFrog cannonball: honestly, I'd recommend firing up gitk and looking at the history and seeing exactly what's happened.15:02
cannonball I'm gonna try the reset --hard, but I don't expect it to fix the issue, because the issue appears to be back years ago, not with current commits.15:02
buibex left15:03
cannonball ToxicFrog: Agreed.15:03
v0n joined15:03
eddyb iveqy: the submodule isn't initialized15:03
ToxicFrog cannonball: are you sure someone else hasn't rebased or filtered master and then force pushed it?15:03
iveqy eddyb: good.15:03
v0n left15:03
cannonball No, I'm not sure of that. Am digging now.15:03
v0n joined15:03
raijin joined15:03
bklane left15:03
v0n left15:03
cannonball git reflog just shows *my* actions, right? I can't see what others would have done to the remote repo.15:03
iveqy eddyb: so it should clone the branch and not master =(15:04
v0n joined15:04
iveqy eddyb: have you played with reference?15:04
zarubin joined15:04
bklane joined15:04
acharlieh joined15:04
eddyb iveqy: why is it not fetching again, after deinit?15:04
iamjarvo left15:05
ToxicFrog cannonball: as far as I know, yes15:05
dsdeiz joined15:05
buibex joined15:05
eddyb iveqy: oh, there we go, rm -rf .git/modules15:05
Cromulent joined15:05
natechan joined15:06
eddyb iveqy: # On branch master15:06
iamjarvo joined15:06
willwh joined15:07
willwh left15:07
willwh joined15:07
jnavila_jnavila15:07
dsdeiz_ left15:07
eddyb iveqy: I have branch = rust-2013-08-28-do-not-delete in .gitmodules, it does a shallow clone (the commit is the HEAD of that branch), but the resulting clone only has master's HEAD15:08
BSaboia joined15:08
glosoli left15:08
cmpera joined15:08
bklane left15:08
cannonball ToxicFrog: Ok, so it was easier than I thought. The problem was with my repo. A simple "git pull --tags" fixed it (which appears to be equivalent to git fetch --tags). My local repo didn't know of those tags (they were plain not present in gitk). After the pull --tags, they were visible and now push works as expected.15:09
ojacobson cannonball: not quite equivalent15:09
PaulCapestany joined15:09
ojacobson 'git pull --tags' still does the merge15:09
If you want to *download* changes or refs, use git-fetch15:09
shuaib left15:10
cannonball would that be equivalent to git pull --no-merge --tags ? (fetch and merge minus merge == fetch) ?15:10
ojacobson no15:10
Cromulent left15:10
eddyb iveqy: this works as expected: git clone --depth=1 --branch rust-2013-08-28-do-not-delete https://github.com/alexcrichton/libuv.git15:10
cannonball Ok, thanks all for the feedback. I have a better understanding now.15:10
ozette left15:11
willwh left15:11
willwh joined15:12
willwh left15:12
willwh joined15:12
matthiaskrgr left15:12
cbreak-work left15:12
chuckharmston left15:13
harobed joined15:13
eddyb iveqy: git-submodule is broken :(. it checks out the branch *after* cloning15:14
which means I have no chance of fixing that today. bloody thing15:15
kama_ left15:15
iveqy eddyb: nah that's by design. The --branch thing is for people that need the submodule to be on a branch instead of beeing on the tracked commit-id15:15
kama_ joined15:15
qsuscsqsusOFFcs15:15
iveqy however I'm a bit surprised about the clone issue you're having15:15
is it a public repo?15:16
(I'm btw. the one that added the --depth option to git submodule, but I did not write the clone part)15:16
eddyb iveqy: clone --branch works, but branch in .gitmodules doesn't, because it does checkout after clone. you just confirmed that's the intended behavior, what's surprising?15:17
japaric joined15:17
fobius Newb Question: What are best practices for making sure that auto merges work as expected? For example, say that we have two users, user1 and user2. user1 introduces a new method addXYZ which returns a float. User2 now goes and writes some code which uses addXYZ but does not change the method. User2 pushes to the server. Now, in the meantime user1 rewrites addXYZ to return an integer. User1 pulls down changes made by user2 and merges them. The chang15:17
es made by user2 are auto merged because they do not try to modify the same lines since user2's code simply uses addXYZ. Yet, the changes user1 made to addXYZ break user2's new code.15:17
eddyb iveqy: this repo: https://github.com/mozilla/rust/blob/master/.gitmodules (first two submodules are really big)15:17
sttau joined15:18
iveqy eddyb: it's surprising that git submodule update doesn't care about branches.15:18
eddyb it made no difference before --depth15:19
v0n left15:19
lavaman1 left15:19
iveqy eddyb: the -b branch option isn't about cloning15:19
tuxx joined15:19
iveqy eddyb: hmm that's true15:19
eddyb (whether it was a clone argument or a checkout afterward)15:19
tuxx left15:19
ngladitz joined15:20
kama_ left15:20
iveqy eddyb: well, the correct solution is to make --depth fetch a commit and its history, not a branch. So making git submodule update respect branches when cloning is not a final solution I'm afraid15:20
ngladitz left15:21
teejmya joined15:21
m8 joined15:21
iveqy fobius: User1 did the merge and is responsible that it works. He should run the test-suite and compile before pushing that15:22
willwh left15:22
iamjarvo left15:22
pepijndevos joined15:23
iveqy eddyb: look at man git clone at -b. It looks like it's not possible to clone from a refs as it is to fetch from one15:23
gitinfo eddyb: the git-clone manpage is available at http://jk.gs/git-clone.html15:23
iamjarvo joined15:23
iveqy eddyb: or wait, maybe with adding --single-branch15:23
eddyb git clone --branch works fine15:23
pepijndevos I just did "git reset --hard HEAD" but "git status" still shows a lot of modified files. What's up with that?15:24
rpg joined15:24
iveqy eddyb: doesn't that give you all the branches?15:24
eddyb iveqy: with --depth=1 it does exactly what I want15:24
twisted` left15:24
iveqy eddyb: :(, not according to the docs. Too bad15:24
kirsty left15:24
eddyb and it's fast (which is the important thing here. I don't want half an hour in the build process)15:25
chriswk left15:25
todd_dsm joined15:25
iveqy eddyb: well, it would be quite easy to modify git-submodule.sh to allow it to pass -b to git clome15:25
clone*15:25
pepijndevos: are those tracked files?15:26
eddyb fobius: I would use rebase in that context, so the commit user1 made (changing return type) could be amended to include updated usage for addXYZ, and it will be directly on top of user2's last commit15:26
asQuirreL left15:26
pepijndevos iveqy, yes15:26
skelterjohn left15:26
iveqy pepijndevos: what does git status tell you?15:26
pepijndevos they are listed under changes not staged for commit15:26
iveqy and what does git reset --hard HEAD tell you?15:27
eddyb iveqy: let me try without --depth=115:27
pepijndevos iveqy, HEAD is now at blabla15:27
iveqy pepijndevos: !repro15:27
gitinfo pepijndevos: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.15:27
eddyb iveqy: same thing, only the branch specified in clone's --branch argument gets fetched15:27
maestrojed joined15:28
pepijndevos iveqy: http://www.fpaste.org/45794/14189081/15:28
fobius eddyb, thanks. I'm not really sure how rebase works so I'll go look it up.15:28
LukeKetley joined15:29
iveqy eddyb: that's a good thing... I'm afraid you found a bug :)15:29
eddyb iveqy: oh c'mon...15:29
fobius iveqy, It just seems strange to me that the choice in git was to auto merge code that could be potentially harmful.15:29
iveqy eddyb: it's easy to fix if you really need it though...15:29
eddyb fobius: that's why you have a choice :P. git pull --rebase15:30
iveqy fobius: tell me one other VCS that doesn't do this15:30
FernandoBasso joined15:30
skelterjohn joined15:30
ThomasClem left15:30
iveqy pepijndevos: what does git diff tell you? What's changed in those files?15:31
Burer left15:31
ELLIOTTCABLE left15:31
iveqy eddyb: open git-submodule.sh and edit line 278 to add -b to clone15:31
eddyb fobius: merge combines changes which are in the wrong order. rebase moves local changes on top, as if all local changes were made after the latest remote ones15:31
fobius iveqy, well, I don't mean git specifically. I'm kind of a newb to VCS in general. I'm really just trying to understand the workflow better. I.e. what is expected of me if I need to push code that includes other people's changes.15:31
pepijndevos iveqy, you want to see the full diff? It's quite big. But it has actual changes...15:31
eddyb iveqy: -b and the branch, which isn't provided to module_clone AFAIK15:32
iveqy fobius: it's expected that you make sure you changes work...15:32
howlymowly left15:32
lavaman joined15:32
dhruvasagar left15:32
iveqy pepijndevos: very strange, I'm afraid I can't give you a straigth answer on why. Usually there's a good explanation for this15:33
primitive left15:33
iveqy eddyb: no it isn't. But you could manually provide it first to test if it works as expected15:33
pepijndevos ok :(15:33
HereCas left15:33
irqq joined15:33
primitive joined15:33
fobius iveqy, Well, sure, but does that mean writing tests for other people's code if they're not provided? If git auto merges other people's changes then how should I know what to test even?15:34
Ropt left15:34
mishok13 left15:34
chuckharmston joined15:34
iveqy fobius: it doesn't. It merges your changes15:34
steme_jomps_ left15:35
eddyb iveqy: I was ready to make a pullreq to rust... no way I'm getting all of this setup today. I just wanted faster build times :(15:35
iveqy fobius: in your example you used a function in your code that had been changed upstream. That make your code errornous15:35
v0n joined15:36
iveqy eddyb: that's the glory of open source. You find a bug and then you can actually fix it. It's much faster than trying to get a company to give you a fix15:36
fobius iveqy, sure, but how would I know that it's erroneous? It wasn't changed when I started working on it. When I merged the changes into my code before I pushed git didn't even tell me that it had changed.15:36
rchavik left15:36
iveqy eddyb: and you got direct help from one of the submodule developers...15:36
jasonroyle joined15:37
eddyb iveqy: oh I know but there's like 3 places where I need to make changes, and the entire thing is a hack because there's no clone-by-commit-id :(15:37
mribeirodantas joined15:37
iveqy fobius: of course git did told you that. Didn't you read the merge diff?15:37
ngladitz joined15:37
iveqy eddyb: yes. And that's a security feature... By design we're not allowed to fetch commnits that's not a parent to a reference. So to implement a fetch by commit_id, it will be quite expensive on the server-side15:38
tdussa left15:38
iveqy and even when we do, most hosting services like github/bitbucket etc. will take some time to get the changes into their codebases15:38
so it's not completely trivial15:38
fobius iveqy, Aha, okay. That's pretty much what I'm looking for. Again, I'm a git newb. How do you get ahold of the merge diff to show what was automatically merged in?15:38
ngladitz left15:39
iveqy fobius: man git diff15:39
gitinfo fobius: the git-diff manpage is available at http://jk.gs/git-diff.html15:39
iveqy is afk15:39
renumi left15:39
fobius iveqy, Okay, thanks.15:39
eddyb iveqy: still, in the case of rust, all of those submodules are pointing to branch HEADs, so it would work, but only maybe in 1.8.5 :(15:40
d2dchat left15:40
boboc joined15:40
worblehat joined15:41
joshsmith joined15:41
cmpera left15:41
Cromulent joined15:41
psynor ok, i know this question isnt "right" but how do i switch the active branch of a bare repo?15:43
jnavila left15:43
jargon left15:44
Balliad left15:44
iamjarvo left15:44
iamjarvo joined15:45
PerlJam psynor: do you have access to the filesystem that the bare repo lives on?15:45
atSetKey joined15:45
Roots47 joined15:46
Roots47 left15:46
PerlJam psynor: if so, you should be able to run "git symbolic-ref HEAD refs/heads/some_branch" to change it.15:46
Roots47 joined15:46
PerlJam psynor: if you don't have access to the filesystem, then I have no clue how to do it. Google or stackoverflow might be your friend.15:47
lifechamp joined15:47
druonysus joined15:49
druonysus left15:49
druonysus joined15:49
jargon joined15:49
iamjarvo left15:49
cmpera joined15:50
dhruvasagar joined15:50
atSetKey left15:50
atrigent joined15:50
willwh joined15:50
willwh left15:50
willwh joined15:50
shinnya joined15:50
grilix joined15:51
atrigent hey guys, I've got a blob in the history of my repo that I would like to compare with a file that is outside my repo - is there a way to do this with git diff?15:51
jargon left15:51
glosoli joined15:51
asQuirreL joined15:51
zarubin left15:52
Misan left15:52
milki atrigent: hm, you could replace that blob with your new file in a new commit and hten use git diff?15:52
infynyxx joined15:52
jargon joined15:52
milki or maybe just add the file so that its a blob and compare two blobs15:53
jaequery joined15:54
leeN joined15:55
axl_ left15:55
atrigent hmm well if it came to that then I'd rather just check out the blob somewhere and use regular diff15:56
osse atrigent: maybe something like diff <(git show HEAD:path/to/file) path/to/other/file15:56
atrigent osse: ah yeah, that'll work15:57
I guess that's good enough15:57
thanks15:57
osse atrigent: according to the man page you can do git diff -- some/path ../outside/repo/...15:58
atrigent osse: right, you can compare two files, but not a file and a blob it seems15:58
Amandil joined15:59
rat_thin_ joined15:59
ehmatthes left16:00
jasonroyle left16:01
epta left16:01
axl_ joined16:02
hyperair joined16:02
boboc left16:02
bwreilly left16:03
Amandil left16:03
Amandil joined16:04
Norm_ joined16:04
acharlieh left16:04
Anticom left16:04
AWinterman joined16:05
rednaks joined16:06
MafooUK left16:07
acharlieh joined16:07
dsdeiz left16:07
AWinterman left16:07
freestyl3r left16:08
petey left16:08
freestyl3r joined16:08
jargon left16:08
epicowl joined16:08
willwh left16:10
ngladitz joined16:10
ngladitz left16:11
mizu_no_oto left16:12
ehmatthes joined16:12
Roots47 left16:12
Exodist joined16:13
Roots47 joined16:13
NanoArrow joined16:15
nathanbbb left16:15
nathanbz joined16:15
v0n left16:17
chirayuk joined16:17
HereCas joined16:18
cmpera left16:19
HumanSky left16:19
|Freeman| left16:19
ebertx joined16:21
MafooUK joined16:22
zhost joined16:22
MafooUK left16:23
huli_ joined16:23
DanielKarp left16:23
zxvf joined16:24
harish_ joined16:24
gitinfo set mode: +v16:24
rfree joined16:24
herdingcat left16:25
multiverse left16:25
Voting left16:25
bwreilly joined16:25
huli_ left16:25
harish_ left16:26
harish_ joined16:26
glosoli left16:26
harish_ left16:26
mklappstuhl left16:27
zxvf hello. a question a bit off-topic: Where can I find info about percentage of use of different DVCS systems?16:27
ngladitz joined16:27
epta joined16:28
ojacobson probably nowhere, if you want numbers with any kind of statistical relevance16:28
why do you want them?16:28
arvind_khadri left16:29
chirayuk left16:29
LuxuryMo_ I had a conflict when rebasing. I resolved the conflict and did "git add . && git rebase --continue", but git tells me "No changes - did you forget to use 'git add'?"16:30
donmichelangelo left16:30
v0n joined16:30
mikecmpbll left16:30
Xethron joined16:30
Xethron left16:30
Xethron joined16:30
donmichelangelo joined16:30
LuxuryMo_ Should I just --skip?16:30
noname001__ left16:31
rfree consider that I forked a repository and then made 10 changes (git commits) to it16:31
how to select 3 of thoes changes and make a nice poll-request for the upstream consisting only of them?16:31
consider that I forked a repository and then made 10 changes (git commits) to it (that is my question also from #github)16:31
reim left16:31
xpe joined16:31
ngladitz left16:32
rfree uh. the git question is, what would be the git command to make such a branch and cherry pick into it16:32
osse oojacoboo: wild guess: to convince his boss to switch16:33
oops16:33
wrong person16:33
aarwine left16:33
rfree actually, I guess http://nathanhoad.net/how-to-cherry-pick-changes-with-git displays it enough16:33
zxvf ojacobson: I am curious16:33
willwh joined16:34
aarwine joined16:34
Peter_Occ joined16:34
bamj0rb left16:35
sttau left16:36
gitinfo set mode: +v16:36
HereCas left16:36
HereCas joined16:37
YannH left16:38
lazers joined16:38
YannH joined16:39
zarubin joined16:39
willwh left16:40
Peter_Occ What does this mean? Your branch and 'origin/master' have diverged, and have 1 and 1 different commit each, respectively.16:40
aard_ joined16:40
osse Peter_Occ: you have one commit on your computer that's not present on 'origin', and there is one commit on origin you don't have on your computer16:41
Sonderblade left16:41
ojacobson Peter_Occ: have a visualization: 'git log --graph --oneline --decorate --color HEAD origin/master'16:41
LuxuryMo_ Looks like git will view resolving a conflict when rebasing by essentially discarding your commit as not "adding" anything…so --skip seems to be the way to go...?16:41
ojacobson LuxuryMo_: the "this" part of your "if this then that" logic doesn't hold16:42
git doesn't view resolution that way, except in specific circumstances16:42
dsdeiz joined16:42
ojacobson if the resolution ends up being identical to HEAD, then it's viewed as no change, because it _is_ no change from HEAD16:42
HereCas left16:43
LuxuryMo_ right16:43
thanks ojacobson16:43
is that sort of what git means when it says ""If there is nothing left to stage, chances are that something else already introduced the same changes; you might want to skip this patch.""?16:43
glosoli joined16:43
harish_ joined16:43
rednaks left16:44
harish_ left16:44
harobed left16:44
jamiis left16:44
gnrlbzik joined16:45
atSetKey joined16:46
sguselnikov joined16:46
sguselnikov left16:47
nickpresta joined16:48
lng joined16:49
arietis joined16:50
atSetKey left16:51
dreiss_ joined16:51
maslowbeer joined16:52
GeertV left16:52
GeertV joined16:53
thiago joined16:53
Baluse joined16:53
hambone joined16:54
buibex left16:54
Peter_Occ Thanks for the help.16:54
glosolicowsoli16:54
cowsoliglosoli16:55
zhost left16:55
acharlieh left16:55
JoeQuery joined16:55
babilen left16:56
JoeQuery Hi! I'm using git svn, and I recieve this error when running 'git svn dcommit': "Permission denied: Can't open file '/var/svn/myproject/db/txn-current-lock': Permission denied at /usr/lib/git-core/git-svn line 922"16:56
hambone left16:56
JoeQuery That /var/svn directory doesn't even exist though. I tried making it just in case, and that doesn't help.16:57
GeertV left16:57
JoeQuery (Also made it writable after making it)16:57
DoniRS left16:58
rvince joined16:58
rvince I just changed every jsp file in a java web project. Now I have to commit them. Since htey are in all different directories, do I have to do a git add on each individual file? How can i tell it to just add every changed cjsp from a certain directory and lower?16:58
iamjarvo joined16:58
lov git add /path/to/root/of/changes/16:59
twisted` joined16:59
rvince lov : and it will add all files from the root on down?16:59
blackstar257 joined16:59
acharlieh joined16:59
lov yes, it's recursive16:59
xpe left16:59
rvince ah! Thank you!16:59
rath left17:00
rfree how to remove one commit abcd1234 from my history?17:00
or apply this commit in reverse17:00
rjhunter left17:00
ToxicFrog rfree: "git revert" to reverse a commit without rewriting history.17:01
safinaskar joined17:01
rjhunter joined17:01
ToxicFrog "git rebase -i" to remove a commit from history entirely (warning: impolite)17:01
k4rtik joined17:01
ChrisAnn left17:01
Sigma joined17:01
iamjarvo left17:02
iamjarvo joined17:02
arietis left17:03
YannH left17:03
pepijndevos left17:04
kulp left17:04
jnavila joined17:05
Sigma[Mtp] joined17:05
rat_thin_ left17:05
LuxuryMo_ What does a conflict with (add/add) mean?17:05
arietis joined17:05
rjhunter left17:05
rat_thing joined17:06
Vampire0 left17:06
y_nk_ joined17:06
HumanSky joined17:06
Sigma left17:07
hahuang65 left17:07
lng left17:08
khushildep left17:08
kulp joined17:08
LuxuryMo_ just means it was added anew in both branches?17:08
whunt joined17:09
cmpera joined17:09
HereCas joined17:09
y_nk left17:09
rat_thing left17:10
JoeQuery left17:10
chirayuk joined17:11
y_nk_ left17:11
Squarism left17:11
Vampire0 joined17:11
chairabanta joined17:11
chairabanta left17:12
babilen joined17:12
guillaum joined17:12
dhruvasagar left17:12
Sigma joined17:12
guillaum left17:13
Wilduck left17:13
Sigma[Mtp] left17:14
guillaum joined17:14
guillaum left17:15
todd_dsm left17:15
nnyk_ left17:15
atrigent I'd like to do a git log starting a ways back in my projects history, and I'd like to get the log for a directory that no longer exists17:15
is there a way to do that?17:15
guillaum joined17:15
minim joined17:16
gghoffman joined17:16
atrigent oh wait nevermind17:16
just needed the --17:16
minim left17:16
Burer joined17:17
multiverse joined17:17
Burer left17:18
multiverse left17:18
gghoffman left17:18
boombatower joined17:18
multiverse joined17:18
Burer joined17:18
NanoArrow left17:19
Norm_ left17:20
fobius left17:20
Xethron left17:20
atc3030 joined17:20
gitinfo set mode: +v17:21
ToxicFrog left17:22
OOPMan joined17:22
minim joined17:22
atc3030 Hello everyone, as I am still gitting used to git ;) I had a question. If i was wanting to cherry-pick this commit from github (http://goo.gl/mERv0K) is there any way that I can find what has followed after, or perhaps what would have it as a dependency. Gerrit makes this process much much easier but their gerrit is shady at best.17:23
thank you for any help17:23
rurufufuss left17:23
atc3030 I will also need some help in figuring out how to actually cherry-pick said commit, but any commit in general will work as I will be doing it alot17:23
Roots47 left17:24
davividal joined17:24
Peter_Occ If I delete a repository and then create a new repository and don't add or commit anything, git status says :17:25
On branch master17:25
Initial commit17:25
What does that mean?17:25
davividal hi. I have this one (legacy) SVN project. I want to import the SVN branch "foo" into a new git repository. Is that possible using git svn? I found this http://ivanz.com/2009/01/15/selective-import-of-svn-branches-into-a-gitgit-svn-repository/ but I'm not sure if it is what I'm looking for (SVN newbie :( )17:25
bwreilly_ joined17:26
b0rsuk joined17:26
bamj0rb joined17:26
Cromulent left17:26
gitinfo set mode: +v17:26
bwreilly_ left17:27
nuclearkitten left17:27
zxvf left17:27
btree joined17:28
btree left17:28
btree joined17:28
boblee left17:28
HenryG left17:28
ToxicFrog joined17:29
DoniRS joined17:29
bwreilly left17:29
ELLIOTTCABLE joined17:29
ngladitz joined17:29
gnrlbzik left17:29
grampajoe joined17:30
bwreilly joined17:30
ngladitz left17:30
amcsi_work left17:30
angelsl left17:30
Vampire0 davividal, I personally would not recomment git-svn for a one-time conversion17:31
For using Git as frontend client to a SVN repository with two-way communication it is great17:31
davividal Vampire0: what about migration? I was going to follow http://git-scm.com/book/en/Git-and-Other-Systems-Migrating-to-Git17:32
Vampire0 But for doing a real switch over I greatly prefer svn2git from the KDE project and probably svneverever before to help analyze the history of the repository17:32
http://blog.hartwork.org/?p=76317:32
This is a blogpost about svneverever that also has a link to the right svn2git tool17:32
jkremser left17:33
intellix left17:34
chriswk joined17:34
davividal Vampire0: it says something about 15,000 revs. I have 'only' 4k. Would you still use svneverever + svn2git ?17:34
steme_jomps_ joined17:34
GODDOG left17:35
panpainter left17:35
mizu_no_oto joined17:35
Burer left17:35
osse atc3030: you can do something like git branch --contains foo to see which branches contain foo (in this case 518c329)17:35
atc3030: as for cherry-picking it: that might be difficult since it is a merge commit17:35
kpreid left17:36
atc3030 ok. I am going to take the time to read up more on git actually to hopefully be able to understand it a bit more rather than just copy past commands and praying they work. lol.17:37
THank you osse17:37
thank you #git17:37
OOPMan left17:37
guillaum left17:37
osse atc3030: to see a log of everything that follows, try git log --all ^518c329 (meaning the log of everything leading up to all refs, but exclude everything leading up to 518c329)17:37
Vampire0 davividal, I didn't read that page. Where does it say something with 15000 revs?17:37
dreiss_ left17:37
Droolio left17:37
Wilduck joined17:37
panpainter joined17:37
Vampire0 I personally would always use svn2git for the Migration I used it multiple times on projects of varying sizes and you have superior control over what goes where and so on17:38
MoHaX joined17:38
osse atc3030: git is hard to just "start using" if you don't know anything about it. Reading a bit would be a good idea.17:38
!book17:38
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 !parable17:38
osse !talk17:38
gitinfo [!talks] Some good video talks about Git: [yt] http://goo.gl/z72s (Linus Torvalds: History&Concepts); [yt] http://goo.gl/R9H2q (Scott Chacon: Git basics, live examples); http://vimeo.com/35778382 (Randal Schwartz: Git basics, descriptional); http://vimeo.com/46010208 (Jesica Kerr: Git basics, descriptional)17:38
dhruvasagar joined17:38
Vampire0 I even splitted a big fat SVN repository with it into multiple small Git repositories per module with one run17:38
davividal Vampire0: "So you’re about to convert a larger SVN repository to Git, say 15,000 revisions." but I'll use it anyway17:38
it's a 8 year project...17:38
cagedwisdom left17:38
atc3030 cool. thank you osse17:39
Vampire0 Ah ok davividal, on my link, I thought on your link17:39
That's just an example with the 15.000, I would even use svneverever and svn2git for a project with 50 commits17:40
eddyb left17:40
OMGOMG left17:40
eddyb joined17:40
osse atc3030: you're welcome17:41
hahuang65 joined17:41
OOPMan joined17:42
Voting joined17:43
schemanic joined17:43
victorbjelkholm left17:44
mdentinho joined17:44
victorbjelkholm joined17:44
dhruvasagar left17:46
ngladitz joined17:46
ngladitz left17:46
atSetKey joined17:46
b0rsuk left17:47
tatsuya_o left17:47
jhulten joined17:47
Guest32557 left17:47
Voting left17:47
ngladitz joined17:48
tatsuya_o joined17:48
ngladitz left17:48
Roots47 joined17:48
guillaum joined17:48
guillaum left17:48
heylouiz joined17:48
str joined17:49
mishok13 joined17:49
MoHaX left17:49
wildfire left17:49
matanya_ joined17:50
TomyLobo joined17:51
str hi everyone. I have a git repository with the 2 last commits wrongly commited to master. How do I tell git to create a branch from the HEAD-2 revision and move those changes to that branch?17:51
atSetKey left17:51
iveqy str: create a new branch from master and then reset master17:52
BSaboia left17:52
str iveqy, create a new branch from mast <- done,17:52
danillonunes joined17:52
tatsuya_o left17:52
str iveqy, and then reset master <-- how do I do that?17:52
Andrevan joined17:53
gitinfo set mode: +v17:53
heylouiz it's not better to rebase to the another branch?17:54
this way he'll keep those two commits17:54
chirayuk left17:54
tufflax joined17:56
jasom iveqy: git checkout master; git reset HEAD~217:56
infynyxx left17:56
Vampire0 ivegy: git reset HEAD~2 master17:56
str: git reset HEAD~2 master17:56
dhruvasagar joined17:57
btree left17:57
Vampire0 Peter_Occ, it just means that you are preparing the first (initial) commit and that there is no commit currently in the repository but that it is empty and you are on the branch called "master" that is created by default when you create a new Git repository.17:58
jasom Oh, for anyone interested, I was talking yesterday about storing .tgz in unzipped form for better packs; I (ab)used smudge/clean filters to do that and my pack went from 7G to 2.3G so I will call that success17:58
jrnieder jasom: nice :)17:59
jasom: any ideas about how this could be documented better for the next person?17:59
tvw left17:59
tvw joined18:00
jrnieder jasom: e.g., a more complete example (including the filter-branch step, etc) for the EXAMPLES section of gitattributes(5)?18:00
breck7 joined18:00
multiverse left18:00
str_ joined18:01
multiverse joined18:01
jasom jrnieder: I might be able to write it up this weekend; should I just send it to the mailing list?18:01
jrnieder yeah, that would be excellent18:01
apipkin joined18:03
PaulCapestany left18:03
str left18:04
multiverse left18:04
ngladitz joined18:04
asQuirreL left18:05
ngladitz left18:05
pantsman joined18:06
pantsman left18:06
pantsman joined18:06
jasom jrnieder: okay, it's on my todo list, but below about a half-dozen pull requests for another project I'm working on, so no promises :)18:06
str_ left18:06
jasom thinks you can tell when his kids are with the grandparents by the flurry of his activities on FOSS projects18:07
dhruvasagar left18:08
nnyk_ joined18:09
byprdct left18:11
mdentinho left18:14
epicowl left18:15
byprdct joined18:16
schemanic left18:16
Norm_ joined18:16
PaulCapestany joined18:17
maslowbeer left18:18
dreiss_ joined18:18
tavoe joined18:20
d2dchat joined18:20
gitinfo set mode: +v18:21
tavoe Looking for help. I have "node_modules/" in my root .gitignore. I expect this to ignore every folder named "node_modules/" and all their contents. It does not.18:22
heylouiz left18:23
ngladitz joined18:24
jsec left18:24
alvaro_o joined18:25
cbreak tavoe: why do you think it does not?18:25
onethfour How do i grab a file from another branch and pull it into my current directory? (without checking out cp to temp dir checkout out other branch and cp from temp)18:25
cbreak tavoe: does such a directory show up as untracked?18:26
atrigent can git log --follow and --full-diff be used together? I'm getting "usage: git logs can only follow renames on one pathname at a time", but I'm only supplying one filename...18:26
cbreak onethfour: man git checkout18:26
gitinfo onethfour: the git-checkout manpage is available at http://jk.gs/git-checkout.html18:26
onethfour cbreak what do i use for the path?18:26
ngladitz left18:26
MrKeys88 left18:26
cbreak atrigent: pastebin18:26
onethfour git checkout OTHERBRANCH path/to/file ?18:26
cbreak onethfour: yes.18:26
onethfour: be aware that you will not get any history18:26
so it is NOT advised to do that18:26
onethfour: you should make a proper merge instead18:27
onethfour i dont need history18:27
lifechamp left18:27
infynyxx joined18:27
atrigent cbreak: pastebin what? "git log --follow <path>" works, but "git log --follow --full-diff <path>" gives the message I gave above18:27
synergy__ left18:28
Sendoushi joined18:28
cbreak atrigent: put a -- in as separator18:28
kwmiebach left18:28
atrigent cbreak: that doesn't work either, I already tried that18:28
atSetKey_ joined18:29
cbreak hmm...18:29
Roots47 left18:29
cbreak you are using -p?18:29
maybe --full-diff implies -p18:29
kwmiebach joined18:29
onethfour cbreak: i tried and it gave me a18:30
fatal: Could not switch to .... error18:30
frgtn left18:30
iamjarvo_ joined18:30
shoshin left18:30
cbreak onethfour: you don't have to switch.18:30
iamjarvo left18:30
onethfour i didnt18:30
cbreak onethfour: as said above, put in a -- as separator as well18:30
atrigent cbreak: why would -p be a problem?18:30
frgtn joined18:30
cbreak that helps git tell appart the path and the argument part18:30
atrigent: not having -p would be one18:30
pr0ton joined18:31
onethfour cbreak: i tried: git checkout MYBRANCH -- /path/to/file.php and it gave me that fatal Could not switch error18:31
jasom isn't -p the default?18:31
atrigent ok well "git log -p --follow --full-diff <path>" doesn't work either18:31
pr0ton left18:31
atrigent still not sure why -p is relevant though18:31
just --follow by itself works, as I said above18:32
cbreak onethfour: well, clearly, / is outside the repository18:32
snuffeluffegus joined18:32
onethfour ok i took out the preceding /18:32
cbreak atrigent: because --full-diff doesn't make sense if you don't show a diff18:32
lazers left18:32
onethfour and now i'm getting '' did not match any file(s) known to git18:32
cbreak onethfour: then that commit doesn't have that file18:32
ezakimak_work joined18:33
infynyxx left18:33
pr0ton joined18:33
onethfour its not a commit it is a branch18:33
cbreak onethfour: it's a commit18:33
infynyxx joined18:33
arietis left18:33
tavoe left18:34
maroloccio joined18:34
onethfour ok i switched it to git checkout MYBRANCH -- path/to/file.php and typed ls and the file doesn't exist?18:34
atrigent cbreak: it looks like --full-diff is just ignored when -p is not supplied18:34
cbreak onethfour: git cat-file -t blah, it'll tell you what it is :)18:34
atrigent just tried without --follow18:34
onethfour what you mean?18:34
Misan joined18:34
cbreak onethfour: it's a commit. that commit doesn't have that file.18:35
frgtn left18:35
atrigent in any case, yes I was using -p... sorry, I took it out for simplicity18:35
cbreak onethfour: if you want to see which files it contains, git ls-tree -r blah18:35
atrigent perhaps I shouldn't have18:35
onethfour ok so it turns out it didn't copy the file to my current directory like i wanted, but rather in the same path as the other branch it was in18:35
mdentinho joined18:35
cbreak atrigent: then it seems something's wrong. I wonder if the order matters...18:35
willwh joined18:35
cbreak onethfour: of course.18:35
onethfour: it won't copy anything anywhere, it'll just check it out.18:36
zhost joined18:36
onethfour what the heck is a "check out"18:36
cbreak checkout has many functions18:37
epicowl joined18:37
osse onethfour: the "it" makes all the difference18:37
onethfour well git checkout did too many things i didn't want18:37
cbreak in file mode, it gets files from the index or from commits and checks them out into the current working directory (and index)18:37
onethfour all i wanted to do was copy and paste a file18:37
cbreak onethfour: then you should be more specific with what you want :)18:37
onethfour and use the file as a template for what i was doing18:37
no history nothing18:38
git checkout added to staged18:38
FernandoBasso left18:38
cbreak then you could have used git cat-file -p Blah:path/to/file | pbcopy18:38
(on OS X)18:38
onethfour yeah cat-file might have worked18:38
lazers joined18:38
onethfour just cat it to a file18:38
>18:38
aard_ left18:38
howlymowly joined18:38
cbreak pbcopy would be better.18:38
that'd allow you to copy&paste the thing18:39
onethfour git cat-file -p MyBranch:path/to/file > myfile.txt18:39
dhruvasagar joined18:39
onethfour no need to use clipboard18:39
cbreak you can't really copy&paste without it.18:39
onethfour you can copy though18:39
and effectually that's what i meant18:39
grampajoe left18:40
fobius joined18:40
Roots47 joined18:40
arietis joined18:40
grampajoe joined18:41
LuxuryMode joined18:41
demiurgo left18:42
vurma left18:42
LuxuryMo_ left18:42
ngladitz joined18:43
lazers left18:43
terminalRepeat joined18:43
willwh left18:43
demiurgo joined18:43
onethfour Why does it take a few operations for git to figure out that you renamed a folder? is there a quick way to tell it that you did that18:44
osse onethfour: use git mv from the get-go18:44
ngladitz left18:44
onethfour oooh i see18:44
osse or regular mv, then git add -A18:44
ryan_turner|MTW left18:44
chuckharmston left18:46
onethfour Is there a way to ignore a file without adding it to .gitignore18:46
repo specific?18:46
axl_ left18:46
chuckharmston joined18:46
osse onethfour: add it to .git/info/exclude18:46
freestyl3r left18:47
jrnieder jfyi, onethfour has been repeating the same questions over a few days :)18:47
AaronMT left18:47
jrnieder perhaps that means the answers weren't helpful enough18:47
chuckhar_ joined18:47
chuckharmston left18:47
onethfour i forget easily :(18:47
dhruvasagar left18:47
onethfour and i learned something new with that git cat-file thing (thanks cbreak)18:48
osse I have to look up what a "record" and what a "field" is every single time I use awk. It just won't stick18:48
chuckhar_ left18:48
dsdeiz left18:48
tjbiddle joined18:49
chuckharmston joined18:49
tatsuya_o joined18:50
chuckharmston left18:50
victorbjelkholm left18:50
chuckharmston joined18:50
jasom osse: really, I thought those were common terms18:51
harobed_ joined18:51
demiurgo left18:51
osse jasom: they probably are :'(18:51
jasom osse: e.g. C has "fields" in structs18:52
asQuirreL joined18:52
osse heh, I call them members.18:52
demiurgo joined18:53
osse I'm not good with lingo18:53
cbreak HTML has fields in forms. :)18:53
asQuirreL left18:53
Jiffy_Jiffy18:53
jasom osse: you probably cal RDMBS records "rows" too then18:53
osse jasom: depends on what RDMBS is18:53
atrigent baseball has fields too18:53
jasom that seems to be an old-school new-school divide: fields vs. members and records vs. rows18:54
dhruvasagar joined18:54
cbreak HTML also has rows. In Tables.18:54
must be the ultimate language for databases.18:54
osse Formula 1 circuits have records18:55
type: lap18:55
jasom: I may have exhaggerated. These days it's roughly every other time I use awk.18:56
axl_ joined18:56
osse The "member" thing probably comes from OOP18:56
though I still call methods functions :P18:56
cbreak osse: they are called "member functions" in the C++ standard too :)18:57
osse cbreak: brilliant. then I don't have to feel bad18:57
jasom called "fields" in the C standard18:57
osse At least I don't say bitmember18:57
jasom also pascal has "records" which contain "fields"18:58
cbreak C++ has all kinds of members. Member types, member functions, member templates, member variables... :)18:58
osse commitee members18:59
jasom C is just C++ that has been dismembered18:59
osse haha18:59
matteo left19:00
karstensrage left19:00
sparq_ joined19:00
tvw left19:00
HumanSky left19:00
rethus left19:01
ngladitz joined19:01
ngladitz left19:01
ngladitz joined19:01
sparq_ left19:01
arietis left19:02
buibex joined19:02
nwertman joined19:03
iamjarvo_ left19:03
iamjarvo joined19:03
pr0ton left19:03
bremner so why is C++ so much more painful??19:03
lifechamp joined19:03
buibex left19:03
Guest29305 joined19:04
mdentinho left19:04
ngladitz left19:04
rvince left19:04
cbreak it's not.19:05
I love it.19:05
ewnd9 left19:06
cbreak osse: C++ has bit members too :) https://ideone.com/8xyfW919:06
jasom cbreak: We'll have to agree to disagree :)19:06
cbreak hardly anyone uses them.19:06
(for obvious reasons)19:06
jasom bitfields in C should be avoided, since many ABIs require quite suboptimal code gen for them19:07
ryan_turner|MTW joined19:07
jasom e.g. an int is passed in a register while a bitfield (that would fit in an int) is passed on the stack19:07
nwertman left19:08
nickpresta left19:08
sq-one joined19:08
rpg_ joined19:09
rpg left19:09
rednaks joined19:10
jasom the e500 sysV abi even is caller copy, so a copy is made even if the callee doesn't always write to it; (a copy can be avoided if the function is declared const, but nobody actually remembers to add const to their function declarations)19:10
snuffeluffegus left19:11
snuffeluffegus joined19:11
AaronMT joined19:11
cbreak just use a const ref. :)19:11
snuffeluffegus left19:11
snuffeluffegus joined19:12
x2z joined19:14
mFacenet joined19:15
FernandoBasso joined19:16
Wilduck left19:16
davividal Vampire0: sorry, just curiosity: why don't you recommend use git-svn for one-time conversions?19:18
I just got asked from my boss19:18
k4rtik left19:18
NanoArrow joined19:18
onethfour why don't man pages have any examples :(19:18
git mv ???19:18
MrKeys88 joined19:19
davividal onethfour: are you talking specifically about git-mv?19:19
Lekensteyn joined19:19
onethfour yeah nevermind19:20
pretty simplistic19:20
asQuirreL joined19:20
Lekensteyn left19:20
kcm1700 left19:21
kcm1700 joined19:21
canton7 git mv [-v] [-f] [-n] [-k] <source> <destination> - pretty clear :P19:21
valgrind joined19:22
stamina left19:22
onethfour examples are very helpful to me19:22
d2dchat left19:22
onethfour So i did git mv oldfile.php newfile.php and now the file is gone completely!!19:22
what the heck??19:22
BSaboia joined19:23
Mode-M joined19:23
x2z left19:23
cbreak it should now be called newfile.php19:23
onethfour its not19:23
its gone19:23
and it says taht the file is deleted when i do git status19:23
canton7 it'll show 'oldfile.php' as being deleted, because it has been19:24
a mv is a delete of the old file,and an add of the new one19:24
eddyb left19:24
Sendoushi left19:24
canton7 there should be a corresponding 'add' for newfile.php19:25
MrKeys88 left19:25
MrKeys88 joined19:25
canton7 sure you didn't type 'rm' instead of 'mv'? got your shell history you can pastie?19:26
Pyrogerg joined19:26
multiverse joined19:26
andrewSC joined19:27
MrKeys88 left19:27
andrewSC hi all19:27
could someone recommend me a good gui mergetool?19:27
Guest58300Freeaqingme19:27
canton7 OS?19:27
andrewSC i use diffmerge now and it's on my last nerve19:27
os x19:27
canton7 hmm not sure about mac. I like p4merge for windows - not sure if there's a mac version. Have a look at the supported tools in man git mergetool19:28
gitinfo the git-mergetool manpage is available at http://jk.gs/git-mergetool.html19:28
cmpera left19:28
Wilduck joined19:28
tang^ andrewSC: Kaleidoscope?19:29
mattmcclure joined19:29
LuxuryMode left19:30
sq-one left19:30
khushildep joined19:30
khushildep left19:30
blackstar257 left19:31
reim joined19:31
breakingthings I have branch foo that branched from branch bar. Branch bar has new commits. How can I make branch foo also have these changes (preferably by changing foo's parent commit to the newest one)19:31
sq-one joined19:32
mattmcclure left19:32
delianides andrewSC: +1 Kaleidoscope19:32
canton7 breakingthings, so you want to rebase? has branch foo been pushed anywhere?19:32
ngladitz joined19:32
ngladitz left19:32
NanoArrow left19:33
cbreak andrewSC: OS X has one that comes with Xcode19:33
breakingthings canton7: no it has not. and yes, I think I do, but I've only used rebase for reordering commits on a single branch yet so I don't know how.19:33
shadok_ joined19:33
y_nk joined19:33
shadok_ left19:33
shadok_ joined19:33
y_nk left19:33
y_nk joined19:33
canton7 breakingthings, cool. git checkout foo; git rebase bar19:33
cbreak andrewSC: it's the default, so you don't have to configure anything19:33
breakingthings and this will keep foo branch?19:33
canton7 that was rebase in its original incantation, before -i was introduced19:34
Muad`Dib left19:34
breakingthings well, keep both branches in tact, that is.19:34
canton7 yup, rebase rebase creates a new set of commits, then moves the branch ref to point to the new version of the branch19:34
LuxuryMode joined19:34
breakingthings alright, thanks.19:34
canton7 so any commits which are referred to by any other branches/tags stick around19:34
mizu_no_oto left19:35
breakingthings cool, didn't realize that's how that worked.19:35
cmpera joined19:35
sparq_ joined19:35
infynyxx left19:35
sparq_ left19:36
bbloom left19:36
rat_thing joined19:36
sparq_ joined19:36
sparq__ joined19:36
sparq_ left19:37
sparq__ left19:37
d2dchat joined19:38
bbloom joined19:38
worblehat left19:38
InvidFlower joined19:38
JohnBat26 joined19:38
canton7 breakingthings, btw, rebase -i does the same with regard to changing what a branch is based on. it's just the common use-case involves rewriting a branch to sit on the same commit that it was sitting on before19:38
mFacenet left19:38
breakingthings yeah19:38
thanks19:39
fragamus joined19:39
sparq__ joined19:40
sparq_ joined19:40
tallest_redd left19:40
minim left19:40
zacts left19:40
maslowbeer joined19:40
banzounet Hey guys, If I pused a commit to github with api key, how can I remove them from my commit history?19:40
sparq__ left19:40
banzounet (reference to my api key in certains files)19:41
el3ctron_ left19:41
sparq_ left19:42
lov banzounet: !filter-branch19:42
zacts joined19:42
lov .... really?19:42
argh19:42
!rewrite19:42
gitinfo [!rewriting_public_history] Rewriting public history is usually bad. Everyone who has pulled the old history 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 -f` to force (and the remote may reject that, anyway). See http://goo.gl/waqum19:42
Sendoushi joined19:42
Norrin I'm doing something wrong here?19:42
$ git checkout -p 1330e660bee1fb43d2e0cc5139532781b172c27b BurstlyPlugin.jar19:42
No changes.19:42
$ git checkout -p ec12e9b79ac5afb1313a0ad50a40f0d69e8d76ef BurstlyPlugin.jar19:42
No changes.19:42
mklappstuhl joined19:42
sparq_ joined19:42
sparq__ joined19:43
Norrin btw, the file is different between the two commits19:43
lov that depends, is- oh.19:43
sparq__ left19:43
el3ctron joined19:43
apipkin left19:43
tagava joined19:43
apipkin joined19:43
tagava|2 joined19:43
babilen left19:45
sparq_ left19:45
banzounet lov: Thanks19:45
rpg_ left19:45
luxgeek left19:46
jfinn left19:46
jrnieder Norrin: what does 'git diff --stat 1330e6 ec12e9b7 -- BurstlyPlugin.jar' say?19:47
whunt left19:47
arrosado joined19:47
mizu_no_oto joined19:49
asQuirreL left19:49
Sendoushi left19:49
sparq_ joined19:49
sparq_ left19:49
ngladitz joined19:49
ngladitz left19:49
sparq_ joined19:50
sparq_ left19:50
a-l-e left19:50
chuckharmston left19:51
dwmw2_gone left19:51
hyperair left19:52
Norrin jrnieder, no output19:52
strange, because github is showing the file changed on that ec12 commit19:52
willwh joined19:52
Norrin jrnieder, https://github.com/burstly/BurstlyUnityPlugin/commit/ec12e9b79ac5afb1313a0ad50a40f0d69e8d76ef19:53
BiggFREE joined19:53
starfox21 left19:53
infynyxx joined19:53
byprdct left19:54
d2dchat left19:54
Soliton left19:54
dwmw2_gone joined19:56
fragamus left19:57
Jackneill left19:57
jrnieder looks19:58
rfoust left19:58
andrewSC tang^, delianides: maybe free/open source? I'd like to exhaust free options before I pay. Not that I have a problem with paying but why pay if something else I see fits the bill just fine, you know?19:59
OOPMan left20:00
Soliton joined20:00
danicampa901 joined20:00
jrnieder Norrin: BurstlyPlugin.jar is in a subdirectory20:00
Norrin: so perhaps you want 'git diff --stat 1330e6 ec12e9b7 -- "**/BurstlyPlugin.jar"'20:00
Norrin: likewise for the checkout command20:00
mklappstuhl left20:01
bamj0rb left20:01
jrnieder that said, the message from checkout was kind of unhelpful20:01
reim left20:01
jrnieder it would be better to notice that there were no special characters in the filenames and give a hint that there's no such file20:02
minim joined20:02
delinquentme joined20:02
delinquentme made a commit w too many files ... how can I undo JUST the commit ... so that I can redo the commit and select the specific files that SHOULD be added20:03
jrnieder delinquentme: did you commit with or without "-a"?20:03
rpg joined20:03
jrnieder to keep the index as-is but just undo the commit, you can do "git reset --soft HEAD^"20:04
_ikke_ delinquentme: git reset HEAD^20:04
DoniRS left20:04
stamina joined20:04
surfdue left20:04
_ikke_ That undoes the last commit, but keeps the changes20:04
aard_ joined20:04
delinquentme git add -A20:04
pr0ton joined20:04
jrnieder to undo the commit and reset the index (but keep your changes in the worktree), "git reset HEAD^" does the trick, like _ikke_ said20:04
wrouesnel left20:04
jrnieder !reset is a nice quick-reference card :)20:05
gitinfo A good resource explaining git-reset is http://git-scm.com/2011/07/11/reset.html20:05
sparq_ joined20:05
jrnieder gah, that's the wrong one20:05
sparq_ left20:05
jrnieder hunts it down on jk.gs20:05
maslowbeer left20:05
willwh left20:05
Soliton left20:05
jrnieder !resets20:05
gitinfo tl;dr of man git-reset: --soft moves HEAD, --mixed moves HEAD+index, --hard moves HEAD+index+work-tree, -- foo.txt will !unstage20:05
howlymowly_ joined20:05
jrnieder there it is :)20:05
howlymowly left20:05
Mode-M left20:06
Devastator_ joined20:06
ngladitz joined20:07
ngladitz left20:07
ngladitz joined20:07
ngladitz left20:07
Norrin jrnieder, well I was in the dir with the file, so no additional path was needed20:08
sparq_ joined20:08
mribeirodantas left20:08
Devastator left20:08
Norrin but i figured it out. the file is in two places. it didn't change in the place I was lookijng. but the commit history shows the other location is where the change happened20:08
chuckharmston joined20:08
sparq_ left20:08
surfdue joined20:09
delinquentme left20:09
worblehat joined20:11
FernandoBasso left20:11
Devastator_ left20:11
Devastator_ joined20:11
Devastator_Devastator20:11
Robarelli left20:12
MacWinner joined20:13
Robarelli joined20:14
cmpera left20:15
mattmcclure joined20:15
TheMoonMaster left20:16
peroht joined20:17
cmpera joined20:17
pepper_chico joined20:18
lifechamp left20:18
arvind_khadri joined20:18
SHyx0rmZ joined20:18
h0bbit_ left20:19
TheMoonMaster joined20:19
atc3030 left20:19
iamjarvo left20:20
s0ber left20:20
iamjarvo joined20:21
iamjarvo left20:21
skorgon left20:21
iamjarvo joined20:22
whunt joined20:22
s0ber joined20:22
sparq_ joined20:22
tang^ andrewSC: oh, yeah, I forgot how much that one was.20:23
andrewSC: they do have a 15 day trial, though. you might find it worth it20:23
ngladitz joined20:24
mozzie_ joined20:25
beastd joined20:25
Sycokinetic joined20:25
maslowbeer joined20:26
JohnBat26 left20:26
Sycokinetic alright, i need more newbie help. i'm trying to push my project to github, but i keep getting a permission denied error :c20:28
canton7 Sycokinetic, output of 'git remote -v'?20:28
willwh joined20:28
willwh left20:28
willwh joined20:28
mozzie_ left20:28
cmpera left20:28
DanielHollands joined20:29
Sycokinetic canton7:20:29
origin git@github.com:Sycokinetic/Random-Stuff.git (fetch)20:29
origin git@github.com:Sycokinetic/Random-Stuff.git (push)20:29
sparq_ left20:29
canton7 looks sensible. If you push, do you get a password prompt?20:29
pr0t joined20:29
Sycokinetic canton7: nope20:29
axl_ left20:29
canton7 exact error?20:30
sounds like a key problem20:30
LimeBlast left20:30
zivester left20:30
p3lim_ Is it possible to specify a specific directory or a file when embedding other repos with gitmodules?20:30
p3lim_p3lim20:30
saml left20:31
Sycokinetic canton7: here's the pastebin http://pastebin.com/U0vb6dcL20:31
aard_ left20:31
JohnBat26 joined20:31
canton7 Sycokinetic, you set up your keys right?20:31
Sycokinetic canton7: i'm honestly not sure :/20:31
canton7 what did you do to set up the keys?20:32
maslowbeer left20:32
Hetu left20:32
Sycokinetic canton7: errrr... i'm not even sure i did anything honestly. the first time i ran the command, bash gave me the RSA key and asked if i wanted to continue connecting20:33
grilix left20:33
tatsuya_o left20:34
willwh left20:34
canton7 Sycokinetic, https://github.com/settings/ssh - have you added a key there?20:34
Sycokinetic canton7: ah! no... i have not20:34
Soliton joined20:34
canton7 that's very, very important ;)20:34
read the two guides linked at the top of that page20:34
tatsuya_o joined20:35
chrisss404 left20:35
willwh joined20:35
willwh left20:35
willwh joined20:35
grilix joined20:35
grilix left20:36
Sycokinetic canton7: is there any particular difference between the ssh and https methods?20:36
canton7 Sycokinetic, with https, you need to enter your password on every push, or store your github password in plaintext somewhere20:37
ingof joined20:37
canton7 with keys, you can always have a password-less push, or use ssh-agent to cache your key's passphrase after you've entered it once20:37
also with keys you can revoke access for particular keys20:37
Sycokinetic canton7: ahhhh20:37
canton7 but https can often get through firewalls with ssh blocks... basically, ssh is preferable, if it works20:37
msheiny joined20:37
mizu_no_oto left20:38
Sycokinetic canton7: right, i used to have a similar ssh setup for my pc's here20:38
canton7 s/with/which20:38
tatsuya_o left20:39
Sycokinetic ... this is the same ssh key guide i used to set that up too XD20:39
canton7 cools20:39
arvind_khadri left20:40
circ-user-5rMaA joined20:40
Soliton left20:41
circ-user-5rMaA left20:41
JosephFerano joined20:41
nt4cats joined20:41
dreiss_ left20:42
chrisss404 joined20:42
willwh left20:42
zacts left20:42
victorbjelkholm joined20:43
nt4cats I am looking for a website I found a while back. It was a list of git problems or challenges broken down by their difficulty. I've been asking the Google for 15 minutes and haven't been able to find it again ...20:43
canton7 nt4cats, is it that interactive introduction to branching thing?20:43
nt4cats Let me try that in Google and see what it comes back with20:44
onethfour to scriptomaniacs: is there a way to get autocompletion within another branch, like FOOBAR:path/to/file20:44
zivester joined20:44
canton7 nt4cats, I'm thinking of http://pcottle.github.io/learnGitBranching/20:44
axl_ joined20:44
mattmcclure left20:44
LukeKetley left20:45
tvw joined20:45
nt4cats canton7: that site looks pretty good, but it isn't the one I was thinking of. I know I'm doing a terrible job of describing the site (which is probably why Google can't help me either)20:46
canton7 yeah, I don't think I've seen the one you're trying to describe, I'm afraid20:46
rat_thing left20:46
nt4cats canton7: I figured it couldn't hurt to try here, thanks for jogging your brain and offering a link20:46
|Freeman| joined20:47
reim joined20:47
starfox21 joined20:47
canton7 someone else might know what you're talking about :P20:47
Soliton joined20:47
nt4cats left20:47
rednaks left20:47
geekbri left20:47
starfox21 left20:47
osse onethfour: yes. zsh20:48
maroloccio left20:48
TheBrainWork left20:50
mishok13 left20:50
chuckharmston left20:51
iamjarvo left20:51
chuckharmston joined20:51
Sycokinetic canton7: thar! now it's working. thank you :320:52
onethfour osse, what about bash?20:52
pr0ton left20:53
dreiss_ joined20:53
Octalot joined20:54
Soliton left20:54
canton7 Sycokinetic, coolio! With gitolite you get a password prompt if you don't have your keys set up right, and for some reason I assumed github would do the same (though it makes sense that they've bothered to configure that away), hence the slight red herrings at the beginning :P20:55
BiggFREE left20:55
onethfour does zsh allow normal bash scripts? i'm so used to bash i dont think i could make the switch20:55
p3lim Is it possible to specify a specific directory or a file when embedding other repos with gitmodules?20:57
acharlieh left20:57
Mars joined20:57
bekks onethfour: Its a different shell. If zsh doesnt support all bash constructs, it does not support bash scripts fully.20:57
raonyguimaraes left20:57
MarsGuest5325420:57
infynyxx_ joined20:58
tang^ canton7: you only get that password prompt if your sshd is set up to allow password connections.20:58
andrewSC left20:58
osse onethfour: there is a git completion script for bash included with git itself. I don't know if it has that feature20:59
banzounet c20:59
osse onethfour: running a bash script (or a zsh script) is typically do different than running a python script or a perl script (or ruby or tcl)).20:59
onethfour: if the script has #!/bla/bla/bla line a process will be run for it so it doesn't matter what shell you use to execute it21:00
SamB onethfour: when I hear "bash script", I think "#!/bin/bash", which zsh obviously doesn't have to do anything about at all ...21:00
grawity osse: if it also has the +x permission21:01
SamB darn osse beat me by 30 seconds21:01
infynyxx left21:01
apipkin left21:01
kmctown left21:01
msheiny left21:01
osse grawity: sure. But in case it doesn't: bash path/to/script :P21:01
pr0ton joined21:02
osse SamB: my chronograph says 31 second. hah!21:02
zacts joined21:03
tpollard joined21:03
acharlieh joined21:03
ingof left21:04
apipkin joined21:04
panpainter left21:04
Sycokinetic left21:04
iderik joined21:06
rainbyte16 left21:07
AzizLight left21:08
King_Hual left21:08
sgu joined21:08
King_Hual joined21:08
King_Hual left21:09
onethfour oh21:09
turns out git auto completion DOES work for BRANCH:21:09
how do io copy a whole directory from branch A to current branch21:09
jason237 left21:09
cannonball left21:09
staafl left21:10
PerlJam onethfour: git checkout branch -- path/to/dir21:10
(that doesn't add it to the branch automatically, but you can figure that part out)21:10
onethfour but i want to specify a destination folder21:10
staafl joined21:10
BSaboia left21:11
PerlJam oh. Hmm.21:11
albel727 left21:11
osse onethfour: git archive branch -- path/to/dir | tar -xf - -C desti/nation21:11
staafl left21:11
arrosado left21:12
onethfour that's quite a line21:12
i'll give it a shot thanks21:12
arrosado joined21:12
staafl joined21:12
PerlJam osse++21:12
OMGOMG joined21:12
snuffeluffegus left21:12
asQuirreL joined21:12
arrosado left21:12
osse \o/21:12
willwh joined21:12
freeed left21:13
osse maybe something like cd destinaton; GIT_DIR=path/to/.git git checkout branch -- path/to/dir could work too.21:13
But then git-archive is simpler, imho21:13
peroht left21:14
_iron left21:14
LuxuryMo_ joined21:14
dhruvasagar left21:15
onethfour git archive didnt work, i resorted to cat-file21:16
davemq joined21:16
osse lies21:16
onethfour fatal: current working directory is untracked21:16
tar: This does not look like a tar archive21:16
tar: Exiting with failure status due to previous errors21:16
tinti joined21:16
osse where did you run it?21:16
onethfour there was probably a typo in your answer but i was to unknowledgable to fix it21:17
Soliton joined21:17
delianides left21:17
onethfour git archive HOTFIX -- src/foo/bar/ | tar -xf - -C .21:17
LuxuryMode left21:17
onethfour is what i ran21:17
osse onethfour: you have to run it from the git repo dir21:17
gzg left21:17
onethfour i was in a git repo21:18
Dougie187 left21:18
osse hmm. works here.21:18
y_nk left21:18
breck7_ joined21:18
tang^ might have to define 'the git repo dir'21:18
y_nk joined21:18
osse onethfour: was src/foo/bar relative to where you were?21:19
breck7 left21:19
onethfour osse, no it was relative to the root of the branch21:19
errr root of the repo21:19
koda joined21:20
onethfour i'm on bash though21:20
is that why?21:20
gzg joined21:20
breakingthings left21:20
osse onethfour: make it relative to the current dir21:20
bash has nothing to do with it21:20
LuxuryMo_ left21:20
onethfour osse, that doesnt make sense, because the path doesnt even exist in the current branch, only in the other one i'm trying to get it from21:21
joshc passing '-f -' to tar is a bit redundant21:21
tang^ onethfour: but what if git is using your current location as its starting point to find the files in the other branch?21:22
osse onethfour: I see, I get the same message now21:22
onethfour tang^, oh yeah that's a possibility21:22
asQuirreL left21:23
willwh left21:23
y_nk left21:23
osse onethfour: if you're in the root of the repo it'll work21:23
This is a bug, imo21:23
onethfour but....?21:23
osse no but21:23
onethfour i can't pass it relative path?21:23
osse apparently not21:23
onethfour well you can make a script to CD to the repo root21:24
osse my instinct was that it would behave like tang^ said. I think many other git commands do.21:24
infynyxx_ left21:24
osse onethfour: luckily that's simple: cd "$(git rev-parse --show-toplevel)"21:25
NoiseEee joined21:25
mizu_no_oto joined21:25
onethfour cool21:26
Soliton left21:26
worblehat left21:26
zarubin left21:26
NoiseEee hey folks, if i'm working on a branch, and I have a bunch of commits on it, and then I want to merge that into Master... whats the merge option to NOT include the log of all branch commits?21:26
mizu_no_oto left21:26
osse onethfour: I see you want to extract to the current dir (-C .). Is that dir ideally outside the repo completely?21:26
gzg left21:27
osse NoiseEee: git merge --squash21:27
NoiseEee thanks osse21:27
osse NoiseEee: that'll make one jumbo-commit at the tip of master containing everything you did in the other branch.21:27
NoiseEee osse: cool thanks :)21:27
osse Are you sure that's what you want? If you delete the other branch the history is gone21:27
NoiseEee osse: prettty sure, is that an unusual request?21:28
atSetKey_ left21:28
osse No21:28
tang^ looking at some of the commits i've made, yeah, I'd say I want to hide all those half-witted attempts and make it look like I did everything in one clean pass :-P21:28
onethfour honestly though it seems like a bit of a hackery, i just want to cp -r a folder from a git branch to a/path/on/my/system/, git checkout would be pretty annoying21:28
gzg joined21:29
NoiseEee left21:29
osse onethfour: (cd repo; git archive branch -- path) | tar -xf -21:29
that could work too21:29
donmichelangelo left21:30
tang^ onethfour: have you looked at man git-readtree yet?21:30
onethfour you mean all on 1 line ?21:30
NanoArrow joined21:30
onethfour tang^, not recently21:30
tang^ man git-read-tree21:30
gitinfo the git-read-tree manpage is available at http://jk.gs/git-read-tree.html21:30
donmichelangelo joined21:30
osse onethfour: it doesn't have to be on one line. But it's a pipeline so in my opinion it looks nicer on one line as long as it isn't very long21:31
rainbyte left21:31
tang^ I've been using a tip to merge repositories together that reads the files from one branch into a subdirectory elsewhere21:31
rainbyte joined21:31
osse onethfour: the point is, it doesn't matter what the current directory is. As long as you know the path to the repo and the path to the destination everything's possible21:31
infynyxx joined21:31
SporkWitch joined21:32
onethfour osse, well ideally i would alias it or make another script21:32
branchcp21:32
apipkin left21:32
irqq left21:33
osse sure, no problem21:34
as of 1.8.4 Git has a -C switch akin to tar. that'll make it even easier21:34
ojacobson left21:34
tbmiller left21:34
frgtn joined21:34
psynor left21:35
tbmiller joined21:35
tbmiller left21:35
onethfour i'm on debian which is liek 1.7.....21:36
tallest_red joined21:36
onethfour s/liek/like21:36
jrnieder onethfour: can you say again what you're trying to do?21:36
lifechamp joined21:36
jrnieder onethfour: is it !deploy or similar?21:36
gitinfo onethfour: 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/the-list-and-irc/deploy.html21:36
SporkWitch onethfour: sounds like a job for make && make install ^^21:37
onethfour i was just trying to copy a directory from another branch into my current dir21:37
jrnieder onethfour: okay, that's *how* you were planning to do it21:37
but it still doesn't tell me the goal21:37
onethfour no i was going to start coding but i wanted a starting point21:37
jrnieder okay, the idea is you have a repo21:37
onethfour so i was going to use a similar dir to start from21:37
jrnieder and you want to copy a directory to start with on another project?21:37
onethfour I'm sorry i dont have time to discuss i got to get going21:38
tang^ judging from the branch named HOTFIX, I'd guess he's after just a part of that branch21:38
jrnieder I'd usually do that by checking out the branch I am interested in in the repo with the first project21:38
and then "cp -R" into the second one21:38
InvidFlower left21:38
onethfour yeah thats the ~slow~ way tod o it JrCs_21:38
longbeach left21:38
onethfour ;)21:38
jrnieder, but you'd have to use a temp dir21:38
jrnieder I guess that depends on the context21:38
onethfour or i guess you could float the changes over21:38
jrnieder e.g., if I want to copy some files from glibc into my-special-project21:39
then I probably already have a clone of glibc around21:39
there's no temp dir involved.21:39
tang^ jrnieder: this is between branches of a single project21:39
jrnieder in that case, it's not clear to me what it means to take a subdirectory of one branch as a starting point for another21:39
in any "how do I" question, there are two ways to answer21:40
DonRichie left21:40
tang^ one branch has a directory that isn't contained in another and the desire is to copy just that directory into another branch21:40
tinti left21:40
jrnieder one is to figure out the goal and figure out a good way to do that21:40
the other is to ignore the goal and answer it as a technical question21:40
SporkWitch jrnieder: maybe not the cleanest approach, but couldn't you just fork the branch, delete what you don't need, and if/when you merge back later you just make sure to keep the files from main branch that you removed from your working branch?21:41
SporkWitch new to git, so assumes there's a cleaner way than this21:41
jrnieder SporkWitch: maybe? It's not clear to me what onethfour is trying to do21:41
once I know, I can give a command.21:41
like many people have already above :)21:41
SporkWitch jrnieder: fair enough, just testing my own understanding; i learn a lot from looking at what others are trying to do heh21:41
Georg3 joined21:42
onethfour honestly though there should be something like cp BRANCHB:path/to/file .21:42
jrnieder SporkWitch: if the idea is 'I want a new branch based on a subdirectory of an existing branch, and I want the history to record that', I think your method makes sense21:42
onethfour: depending on what you're trying to do, maybe there should be21:42
it's still not clear at all to me what you want the effect to be21:43
if you're just trying to grab a file from another branch, the usual way is "git show BRANCHB:path/to/file"21:43
onethfour sorry i'll get in trouble if i spend more time on irc, you can try reading the logs above21:43
jrnieder you can redirect the output to a file21:43
onethfour: ok :)21:43
Amandil left21:43
onethfour and yes that works for files, but what about directories21:43
el3ctron left21:43
onethfour ack really leaving21:43
SporkWitch does not miss jobs that were that draconian21:44
jrnieder onethfour: if you're trying to grab a directory from another branch, the usual way is "git archive BRANCH:path/to/directory"21:44
you can pipe the output to 'tar'21:44
tang^ which has been offered21:44
onethfour can someone make a "git cp" command21:44
to do just that21:44
jrnieder onethfour: sure, you can :)21:44
minim left21:45
onethfour would take me proabbly 5 hours21:45
SporkWitch jrnieder: ++21:45
jrnieder if you make a script in the $PATH named git-cp, then running "git cp" will do what you're asking for21:45
onethfour you're kidding21:45
that's awesome!21:45
SporkWitch onethfour: 5 hours to save how many future hours for how many other people out there? :)21:45
osse onethfour: my pipeline above works just fine21:45
jrnieder if you want it to be included in the standard installation of git, [email@hidden.address] is the place to suggest it21:45
howlymowly_ left21:46
SporkWitch is totally the guy from XKCD writing the mouse-wiggle script and the arbitrary-condiment-passing script...21:46
g3orge joined21:46
atSetKey joined21:47
jon_r joined21:47
jon_r left21:47
glosoli left21:47
jnavila left21:48
axl_ left21:49
breck7 joined21:49
breck7_ left21:50
axl_ joined21:50
natechan left21:50
zoli joined21:50
pr0t left21:51
h0bbit_ joined21:51
Misan left21:51
davemq left21:53
willwh joined21:53
willwh left21:53
willwh joined21:53
leeN left21:53
g3orge how can I make git grep look into submodules as well??21:54
axl_ left21:55
Sigma left21:55
m0viefreak g3orge: you could probably do something along 'git submodule foreach --recursive git grep ...'21:56
TomyLobo left21:56
m0viefreak but the output you are getting will not indicate from what submodule the results are coming from21:56
beastd left21:57
infynyxx left21:57
jason237 joined21:57
rat_thing joined21:57
g3orge yeah. or use plain grep. I guess I am asking *why* doesn't git grep recurse through submodules...21:58
m0viefreak why should it?21:58
infynyxx joined21:58
m0viefreak after all, the main repo and the submodules are kind of intedepdent21:58
minim joined21:59
reim left21:59
infynyxx left21:59
jerius left22:00
kcm1700 left22:00
frgtn_ joined22:02
NanoArrow left22:02
ngladitz left22:02
eletuchy joined22:02
rat_thing left22:02
g3orge hmm, yeah I guess22:03
acharlieh left22:03
h0bbit_ left22:03
rpg left22:04
sdx23 left22:04
frgtn left22:04
kcm1700 joined22:04
pr0ton left22:04
valgrind left22:05
sdx23 joined22:05
nemesit|znc left22:06
Fandekasp joined22:06
gitpicker left22:07
kcm1700 left22:07
robbyoconnor joined22:08
nemesit|znc joined22:08
gitpicker joined22:09
_nova joined22:09
kermit joined22:09
multiverse left22:09
pr0ton joined22:09
jrnieder g3orge: forward-port the patches from https://github.com/jlehmann/git-submod-enhancements/commits/grep-recursive?22:11
nova_ left22:12
nova_ joined22:12
raonyguimaraes joined22:12
Vampire0 davividal, svn2git is a gazillion faster as git-svn has to do a manual svn checkout for each and every revision to build up the repository, the history that comes out is more correct as far as I remember and especially you have much more control over how the conversion is done, like what path in SVN lands in which path in which Git repository, and so on, like e. g. splitting one big SVN repo with many modu22:12
les into several small Git repositories and so on.22:12
kcm1700 joined22:13
_nova left22:14
pantsman left22:14
HumanSky joined22:15
zhost left22:17
Swayz left22:17
Soliton joined22:18
harobed_ left22:19
sgu Hi all, when I do `git pull -s recursive -X theirs` and I get this message "XX file would be overwritten by merge, commit your changes or stash them before you can merge". What should I do if I just want it to be overwritten.22:19
kcm1700 left22:19
functorfun joined22:20
functorfunfunfunctor22:20
jaequery left22:20
osse sgu: git checkout HEAD -- file22:20
BiggFREE joined22:22
grampajoe left22:24
Soliton left22:24
dreiss_ left22:24
Gamecubic joined22:24
boombatower left22:25
freestyl3r joined22:26
DanielKarp joined22:27
hholtmann left22:27
panpainter joined22:28
Archweasel joined22:28
willwh left22:29
v0n left22:29
sgu osse: is there an option of `git pull` let me save this step?22:30
boombatower joined22:30
Soliton joined22:31
purpleidea joined22:31
zoli left22:31
Guest29305 left22:32
purpleidea hey, something has gone wrong. i was working on master, i had some files added and some modified to staging. i did git stash and then git stash list. i then wrote a patch, and merged it. it is seen in my log. i then did git stash apply, and some of the earlier git add -p changes i've made aren't seen. help!22:32
dreiss_ joined22:32
Destos left22:33
iveqy purpleidea: !repro22:34
Huevos left22:34
gitinfo purpleidea: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.22:34
druonysus left22:34
knuth joined22:34
druonysuse joined22:34
knuth hi guys.22:34
gitinfo knuth: 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.22:34
phile left22:35
vinc left22:35
purpleidea iveqy: any idea what happened in my particular scenario if i did something the wrong way ?22:35
willwh joined22:36
normanrichards left22:36
danicampa901 left22:36
iveqy purpleidea: I can't understand your explanation, that's why I asked you to repro22:36
purpleidea iveqy: ok22:36
DanielKarp left22:37
mitz_ left22:37
Narven joined22:37
Orbitrix joined22:38
bwreilly_ joined22:39
purpleidea http://fpaste.org/45956/14447751/22:39
bhutjolokia joined22:39
purpleidea iveqy: http://fpaste.org/45956/14447751/22:39
madewokherd joined22:40
bhutjolokia Git can detect file integrity problems, right?22:40
Guest53432 joined22:41
HicksD left22:41
purpleidea bhutjolokia: git-fsck ?22:41
mobileblue left22:42
bwreilly left22:42
bhutjolokia purpleidea, no, git in general. If a bit gets corrupted somewhere it should know, should it not?22:42
mitz_ joined22:42
Soliton left22:42
grawity yes, it should know22:42
sayd a/close22:42
purpleidea bhutjolokia: yes, see git-fsck22:42
iveqy purpleidea: but 00:40 -!- purpleidea [~james@unaffiliated/purpleidea] has joined #git22:43
purpleidea: sorry..22:43
purpleidea iveqy: ?22:43
jaequery joined22:44
iveqy purpleidea: What I can see from git status the exact same things are added to the index both before and after your stash. Is it so that part of stuffxyz isn't added22:44
?22:44
Droolio joined22:44
grawity hmm, interesting22:44
natechan joined22:44
grawity apparently git does not check if a blob it just read actually matches its hash22:44
oh, it does22:44
purpleidea iveqy: yes, exactly. part of my changes to stuffxyz aren't seen after the git stash apply. in fact, some of those changes included 'e' edits, so data seems to be lost.22:44
rnsanchez left22:44
grawity just `git cat-file` doesn't, but things like `git show` still do.22:45
$ git show fd247ec09b6e1d5b4189b4fc1248ff898adb9a4f22:45
error: sha1 mismatch fd247ec09b6e1d5b4189b4fc1248ff898adb9a4f22:45
cotton joined22:45
grawity so yeah, bhutjolokia, git would know that.22:45
bhutjolokia Curious. I have a .jar file tracked in a git repo. The file began failing out of nowhere after a system reboot. Git sees no difference in the file. When I recompile the jar from source and replace it, git _does_ see a difference and the file runs.22:45
sq-one left22:45
bhutjolokia How do I explain this?22:46
jaequery left22:46
grawity Does it work if you delete the file from working tree, then check out a good copy from the repo?22:46
gitinfo set mode: +v22:46
jason237 left22:46
SHyx0rmZ left22:46
fobius What's the difference between (merging topic_branch and master and then deleting topic_branch) and (rebasing topic_branch onto master)?22:47
iveqy purpleidea: this is not good at all, please send this to the !list22:47
gitinfo purpleidea: [!mailing_list] The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist22:47
grawity I think things like `git status` have some optimizations – e.g. they won't compare the contents if the timestamp is still the same22:47
bhutjolokia grawity, yes, it does.22:47
purpleidea iveqy: :(22:47
bhutjolokia How can there be no difference between a broken file and a running one?22:47
grawity fobius: you're basically asking "What's the difference between merging and rebasing in general", right?22:47
purpleidea iveqy: can you reproduce this issue ?22:47
grawity bhutjolokia: see what I said about optimizations22:48
bdavenport joined22:48
bhutjolokia grawity, Even git diff?22:48
grawity hmm, not sure22:48
normanrichards joined22:48
iveqy purpleidea: sorry, I don't have a possibility to reproduce rightnow22:49
m0ltar left22:49
kcj joined22:49
DanielKarp joined22:49
fobius grawity, pretty much. I mean, from what I gather they produce the same end result on the branch being merged into/rebased onto. According to git-scm it causes the histories to differ but I'm confused as to how. It seems like in both situations git log would show the merged/rebased commit and then the commits on master prior to that commit.22:49
bhutjolokia grawity, you were right.22:49
purpleidea anyone have an idea how to fix this please? http://fpaste.org/45956/14447751/22:49
jrnieder purpleidea: use "git stash --keep-index"22:50
iiuc22:50
Soliton joined22:50
knuth Can someone point me to a good article or two that I can use to help convince my org to convert from vss to git?22:50
bhutjolokia Thanks guys.22:50
purpleidea jrnieder: at which point?22:50
m8 left22:51
purpleidea jrnieder: at the git stash 'save' part ? is it too late to get my data back ?22:51
jrnieder purpleidea: ah, let me back up. are you trying to see what went wrong or to recover?22:51
okay, to recover22:51
knuth looking to compare to svn.22:51
purpleidea jrnieder: i want my data and changes back22:51
grawity from what little I know about VSS, "Git/SVN won't corrupt your data" seems a good argument..22:51
HumanSky left22:51
jrnieder purpleidea: ok, do I understand correctly that what's in the worktree is right but it forget what was in the index?22:52
or is it something else you've lost?22:52
knuth lol, how about svn vs git.22:52
Siecje joined22:52
purpleidea jrnieder: yeah, well everything that i git add -p 'ed is gone. including changes made with git add -p 'e' (edits)22:52
jrnieder purpleidea: ok, good22:52
Siecje if I add a file to staging area why can't I use the command git diff on it?22:53
jrnieder I'd use "git fsck --lost-found"22:53
willwh left22:53
multiverse joined22:53
jrnieder purpleidea: it will take some sifting --- sorry I don't have a better idea :/22:53
knuth my understanding is that git is going to be harder to use then svn.22:53
jrnieder purpleidea: (when you add something to the index, that forces git to record its content, which is good)22:53
knuth I want to go with git but need reasons on paper for people.22:54
AWinterman joined22:54
jrnieder purpleidea: (but there is nothing like a reflog for the index, so there's no record of *which* unreferenced blob in particular is the one you're interested in)22:54
purpleidea jrnieder: dangling blobs and other things... now what?22:54
jrnieder purpleidea: grep through the blobs :(22:54
purpleidea: they should be in .git/lost-found22:54
mobileblue joined22:54
Pyrogerg left22:55
knuth .22:55
is git more easy to run on windows then svn?22:56
epicowl left22:56
Soliton left22:56
jrnieder knuth: they're both pretty easy to run on windows22:56
grawity these days both are equally easy22:56
jrnieder knuth: for svn lots of people like tortoisesvn22:56
knuth: (a shell extension)22:56
g3orge left22:56
jrnieder knuth: there's no single standard gui tool like that which everyone loves for git22:56
grawity [although in the past, I used to hear that TortoiseGit was really inferior compared to TortoiseSVN]22:56
v0n joined22:56
jrnieder exactly, I think gitcheetah's a bit better22:57
purpleidea jrnieder: nope. none of those have any useful data22:57
panpainter left22:57
jrnieder purpleidea: your file isn't in .git/lost-found/other/?22:57
grawity but either way – those are just GUIs22:57
purpleidea jrnieder: nope22:57
jrnieder: and not in .git/lost-found/commit either22:57
jrnieder purpleidea: that's strange. anything you added to the index would be in the object db22:57
purpleidea: meaning it would either show up in the lost + found or be referenced by some actual commit22:58
purpleidea git --version 0.3141522:58
just kidding git version 1.8.3.122:58
knuth Do you guys keep a central repository on a server or just depend on developers boxes?22:58
Soliton joined22:58
jrnieder knuth: at work, central repo22:58
purpleidea jrnieder: beats me. i'm a little pissed. git stash has generally worked before. i haven't used it in a while, but still. wtf22:58
grawity I think most Git projects have some kind of a central repo22:58
Siecje if I add a file to staging area why can't I use the command git diff on it?22:59
jrnieder purpleidea: hm, let me try to reproduce it22:59
purpleidea jrnieder: sure, thanks23:00
jason237 joined23:00
jrnieder Siecje: I don't know. why can't you?23:00
tang^ left23:00
grawity Siecje: you can, after you understand how `git diff` works23:00
by default, it compares the working tree with the staging area23:00
purpleidea jrnieder: any idea if git stash show can show the long output of the diff as opposed to the shortlog23:00
grawity if you add a file to the staging area, then there's no difference anymore23:00
jrnieder purpleidea: sure, git stash show -p23:00
purpleidea s/shortlog/diffstat23:00
knuth but pull requests are still handled by the hithub account?23:00
grawity you might be looking for `git diff --cached` or other options in the manpage23:00
purpleidea jrnieder: ah thanks23:00
Siecje grawity: how do I compare it to the last commited version23:00
grawity Siecje: man git diff23:01
gitinfo Siecje: the git-diff manpage is available at http://jk.gs/git-diff.html23:01
knuth on entiprise how do you deal with code promotion?23:01
jrnieder Siecje: git diff HEAD23:01
Siecje ty23:01
jrnieder knuth: mostly, give talks23:01
DanielKarp left23:01
jrnieder knuth: or do you mean as part of release management?23:01
knuth: or advocacy?23:02
knuth not sure honestly. I have only played with git with some simple open source projects.23:02
tt-rss.23:02
purpleidea jrnieder: so looking through git stash show -p i don't see *any* of the individual changes that i had previously made with git add -p, (particularly the 'e' stuff which was what mattered the most)23:02
mFacenet joined23:03
jrnieder purpleidea: ok, let me walk through the same steps you did23:03
Soliton left23:03
knuth I got the project made a change and made a pull request.23:03
jrnieder purpleidea: first you made some change to a file23:03
druonysus joined23:04
jrnieder purpleidea: then "git add -p", edited the file in the index that way23:04
knuth when you have a room of coders how is checking in code delt with... (yes i'm talking like a vss noob...)23:04
jrnieder purpleidea: then, "git stash"23:04
Shaladdle left23:04
knuth does each programer make a pull request and the lead approve them?23:04
iderik left23:04
purpleidea jrnieder: (i'm doing it too)23:05
jrnieder purpleidea: it looks like it does save the index along with everything else. I learn something new every day :)23:05
g0bl1n left23:05
jrnieder purpleidea: now, "git stash pop"23:05
mFacenet left23:06
jrnieder it unfortunately doesn't apply the change to the index23:06
if I do "git reset <stash commit>^2 -- ." then the change gets applied to the index23:06
this UI is crazy23:06
druonysuse left23:06
knuth jrnieder: release23:06
purpleidea jrnieder: so afaict, you're seeing the same issue, correct ?23:07
jrnieder purpleidea: yeah, the stash records the old index but "git stash apply" doesn't reapply it23:07
grawity knuth: I have no experience at all, but from what I've heard, it really varies... some projects do pull requests – Github, Gerrit, Phabricator, or just email; others have a "review" repo to push to; yet others just push directly to the main repo.23:07
purpleidea jrnieder: will reset-ing to the stash fix this?23:07
jrnieder purpleidea: looks like 'git stash apply' takes a --index option23:07
lavaman left23:07
purpleidea jrnieder: i don't know the ^2 -- . syntax23:07
jrnieder purpleidea: "git stash pop --index" would have done the trick23:08
why in the world that's not the default I don't know23:08
purpleidea jrnieder: it's a HUGE bug atm.23:08
sounds like mailing list material23:08
jrnieder purpleidea: UI bug, yes, I agree23:08
jason237 left23:08
jrnieder purpleidea: working as intended, but the intention is wrong :)23:09
purpleidea jrnieder: agreed23:09
knuth grawity: Can you have repos that get auto pull aproved. The "review" repo?23:10
mdiers joined23:10
Risto joined23:10
Hello71 left23:11
boombatower left23:11
jrnieder knuth: for large projects, I like the way the kernel is maintained23:11
knuth: but lots of companies can't afford to have one person be full-time maintainer23:11
purpleidea jrnieder: what would be the correct git reset command to pull out the stash correctly on master?23:11
boombatower joined23:12
grawity knuth: sounds like a repo that just allows everyone to push to23:12
jrnieder knuth: and prefer to have developers make changes with some autonomy, possibly after code review23:12
Hello71 joined23:12
jrnieder purpleidea: do you still have the stash you were trying to apply?23:12
knuth our shop is a bit of a free for all..23:12
purpleidea jrnieder: yeah, i never pop-ed it.23:12
jrnieder purpleidea: then I'd do "git reset --hard" followed by "git stash apply --index"23:13
purpleidea: note that will make the worktree and index look exactly like HEAD before applying the stash23:13
fobius left23:13
jrnieder purpleidea: so if you had local changes it wouldn't be a good thing to do23:13
knuth book suggestions I'm looking at pro git and the link.23:13
http://refcardz.dzone.com/refcardz/git-patterns-and-anti-patterns23:13
purpleidea <stdin>:322: new blank line at EOF.23:13
+23:13
warning: 1 line adds whitespace errors.23:13
error: The following untracked working tree files would be overwritten by merge:23:13
...23:13
Please move or remove them before you can merge.23:14
Aborting23:14
Index was not unstashed.23:14
funfunctor left23:14
grawity knuth: that sounds like a simple Git or SVN setup then... a central repo where anyone can push anything. Easy to set up with Gitolite or whatever other tool you choose23:14
jrnieder purpleidea: ah, sure, "git reset --hard && git clean -nd && git clean -fd"23:14
Siecje left23:15
falconfox left23:15
tbmiller joined23:15
falconfox joined23:15
victorbjelkholm left23:16
purpleidea jrnieder: i think i'll just remove some of those files manually, because some of those aren't tracked or saved anywhere...23:16
so the git clean would delete them i think.23:16
knuth grawity: cool thanks :) One more question for now (besides the request for book suggestion) can I hook github into this setup. We are taking over a project from an outside vendor. We will still use them but often will be updating the code ourselves.23:16
pr0ton left23:16
jrnieder purpleidea: yeah23:17
knuth How do you suggest setting up that so we can push but they have to be approved/put in a testing/staging area.23:17
nova_ left23:17
joshsmith left23:18
Wilduck left23:18
grawity knuth: I'm guessing you could create an 'organization' on Github, then you'll be able to give push access to a specific group, and everyone else will have to do pull-requests23:18
purpleidea jrnieder: well it seems things are almost back to normal. thanks for the chat. who wants to report this?23:19
jrnieder purpleidea: you can :)23:19
purpleidea: thanks23:19
purpleidea jrnieder: balls :(23:19
yacks left23:19
purpleidea jrnieder: thank goodness for irssi history23:19
$ git stash apply --index23:20
<stdin>:322: new blank line at EOF.23:20
+23:20
warning: 1 line adds whitespace errors.23:20
Auto-merging ...23:20
i don't remember having a EOL problem before...23:20
pepper_chico left23:21
mizu_no_oto joined23:21
purpleidea git d --cached --check23:21
primitive left23:21
purpleidea file.foo 162: new blank line at EOF.23:22
knuth anyone useing https://enterprise.github.com/23:22
frgtn_ left23:22
purpleidea but it's not there in the cache or the regular file23:22
Soliton joined23:22
frgtn joined23:22
mklappstuhl joined23:23
boombatower left23:23
willwh joined23:23
koda left23:24
luxgeek joined23:24
knuth grawity: could I have a local repo that is slave to the github repo so that if github is down we still are up?23:24
tinti joined23:24
knuth have the local repo be a single user?23:25
grawity knuth: sure23:25
farn left23:25
knuth then let anyone local push to that as they wish?23:25
gitinfo set mode: +v23:25
purpleidea sweet23:25
grawity yeah, just need to find a way to automate the synchronization23:25
knuth with github?23:25
grawity automating a fetch, or push, is easy23:26
it's a bit harder when people can push to *both* repositories and the script has to decide whether to push from local-copy to github or to fetch instead23:26
tagava|2 left23:26
tagava left23:26
purpleidea jrnieder: if you do a git stash pop instead of apply, and you don't use the --index, does that mean the index data (that you helped me find) would be "deleted" forever ?23:27
knuth ya that is why I figured it would be managed by a person.23:27
grawity knuth: but, technically, you can still be 'up' even without that23:27
knuth though honestly most changes could come from local.23:27
frgtn left23:27
raonyguimaraes left23:27
decotii left23:27
grawity since everyone just keeps committing locally – to their own clone – and when Github goes back up the next day, they can continue as if nothing happened23:28
knuth yep yep. but this is probably needed anyhow with the outside vendor.23:28
have two local repos one to pull back the vendors stuff to test?23:29
the other our groups current copy?23:29
el3ctron_ joined23:29
tbmiller left23:30
tbmiller joined23:31
Robarelli left23:32
raf joined23:33
boombatower joined23:35
farn joined23:35
tbmiller left23:35
willwh left23:36
Soliton left23:38
tvw left23:40
Soliton joined23:40
kcj left23:41
mizu_no_oto left23:41
infynyxx joined23:43
zacts left23:44
Archweasel left23:44
Soliton left23:45
functorfun joined23:45
functorfunfunfunctor23:45
natechan left23:45
Zarthus left23:45
sgu Hi all, A particular version may stay unchanged for many commits, so the last version of a particular may not be in HEAD~1. Any git command can give me the file before its last change?23:47
adamm joined23:47
pr0ton joined23:47
sgu Hi all, A particular file may stay unchanged for many commits, so the last version of a particular may not be in HEAD~1. Any git command can give me the file before its last change?23:47
bwreilly_ left23:48
purpleidea is there a way to do an interactive merge similar to how git add --patch works or the 'e' works, so that i can make a few simple changes before the merge applies?23:49
grilix joined23:50
joshsmith joined23:50
Soliton joined23:50
rchavik joined23:53
iveqy sgu: not afaik. You can always do something like this:23:54
FILE=<filename> && git diff $(git rev-list HEAD "$FILE" | head -2 | tail -1) "$FILE"23:54
sgu: are you used to work with cvs?23:54
purpleidea: I don't know, see man git merge23:55
gitinfo purpleidea: the git-merge manpage is available at http://jk.gs/git-merge.html23:55
iveqy sgu: usually you use git log to see the history of a file23:56
epicowl joined23:56
chirayuk joined23:57
iveqy sgu: like git log -p <filename> see man git log23:57
gitinfo sgu: the git-log manpage is available at http://jk.gs/git-log.html23:57
cagedwisdom joined23:57
slakmagik joined23:57
slakmagik left23:58
tjbiddle left23:59

Logs Search ←Prev date Next date→ Channels Documentation