IRCloggy #git 2013-11-28

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-11-28

lite_ joined00:00
Terabyte left00:00
rednaks left00:01
grawity hmm, Git requires one to commit before merging, not the other way around00:01
anyway, you could teach them to rebase or pull --rebase00:01
bartzy left00:02
jon_r left00:02
kris joined00:03
aaronds sorry grawity, got that wrong. It's after committing but before pushing.00:03
johnkevinmbasco joined00:03
Noldorin left00:03
lite_ left00:04
simesy joined00:04
kris left00:04
MattMaker joined00:05
kriks left00:05
alvaro_o left00:06
alp82 left00:07
alvaro_o joined00:07
kirin` left00:07
majuscule aaronds: rebasing is what you're looking for i think00:07
aaronds: you can also try to always use --fast-forward when merging00:08
bwreilly joined00:08
majuscule aaronds: but rebasing'd probably be preferred00:08
amcsi left00:08
hyperair left00:09
aaronds ok cool - so is this generally what happens in most organisations? Needing to rebase when pulling changes? Or do people just remember to pull before commiting lol00:09
adac left00:09
ericy joined00:09
rjhunter joined00:09
crazydiamond_ joined00:11
jrnieder aaronds: yeah, I think lots of people rebase, unless they're working on a long-term topic branch where a rebase might be disruptive00:11
aaronds ok cool00:12
thanks everyone00:12
jrnieder aaronds: or log --no-merges :)00:12
crazydiamond_ left00:12
boombatower left00:13
zhost left00:14
rjhunter left00:14
dnlrn left00:15
luxgeek joined00:15
Noldorin joined00:15
maestrojed left00:17
kh0d joined00:17
dxdt joined00:19
HappyLappy left00:19
jan1337z joined00:20
PeterBooker left00:20
etcetera left00:21
madewokherd joined00:22
etcetera joined00:22
etcetera left00:23
jon_r joined00:23
etcetera joined00:23
pfFredd left00:24
looper left00:25
asQuirreL left00:25
Kayra left00:26
sdx23 joined00:27
wpaulson joined00:27
Cerise joined00:28
wpaulson left00:28
ericy left00:30
specing joined00:32
m_ke joined00:32
ehmatthes joined00:32
AlecTaylor joined00:32
xobb left00:34
el3ctron_ left00:34
dravidan joined00:34
farn joined00:35
undecim joined00:35
treaki_ joined00:36
treaki__ left00:38
refried_ joined00:38
HappyLappy joined00:39
jarr0dsz left00:39
el3ctron_ joined00:40
ehmatthes left00:40
codeman joined00:40
maqr left00:41
dhackner left00:42
m_ke left00:42
dhackner joined00:42
Ltk left00:43
el3ctron_ left00:43
el3ctron_ joined00:43
el3ctron_ left00:43
DABVCW6 joined00:44
relipse joined00:45
dsdeiz left00:45
relipse Ziber: hey you there?00:45
dreiss joined00:45
ericy joined00:46
dhackner left00:47
simesy left00:47
jcardinal joined00:48
SynthesizerPatel left00:48
echo-area left00:48
ezekielnoob3 joined00:49
dhackner joined00:49
dxdt left00:49
echo-area joined00:50
kirin` joined00:50
HappyLappyHiramHibbard00:50
groglogic joined00:51
mdiers__ left00:51
devanblue left00:52
jcardinal Git noob here. I have a repo that I've done a handful of commits on from a few different machines, all pushed to the origin server. Some of the machines I was committing from had the wrong author info, which I wanted to correct. Searching suggested I should do a rebase and edit each commit that had the wrong author info and amend those commits. I did that, but now git status says my branch and the one on the origin have00:52
diverged. The local copy is the corrected one, and I want to push those corrections to the origin. How do I do that?00:52
b_rare joined00:52
el3ctron_ joined00:52
el3ctron_ left00:53
gregorg joined00:53
el3ctron_ joined00:53
ezekielnoob3 left00:53
el3ctron_ left00:54
smashwilson left00:54
dalias jcardinal, you should wait for someone more experienced to give you a better answer, but the short answer is that this is "changing history" and considered a bad thing if the repo is already published and others may have cloned it00:55
you probably need to force the push if you actually want to do it00:55
Skrypter left00:55
etcetera left00:55
jcardinal dalias: Thanks. In this case, the origin is on a server owned by me and no one else has worked on with this repo yet, so I feel safe "changing history". That said, how would I force that change through?00:56
PeterBooker joined00:56
PeterBooker left00:56
kh0d left00:57
jcardinal Is it literally as simple as just adding the --force option to my push?00:57
shruggar joined00:57
freestyl3r left00:57
SoftwareMechanic joined00:57
dalias i suspect so, but i'm also a git newbie, so i don't want to tell you something wrong and break your repo00:58
pantsman joined00:58
jcardinal dalias: Thanks for being cautious with your advice. My gut says that's all there is to it, but like you said...I'd don't want to risk destroying the repo.00:59
I guess I'll just clone it elsewhere for safety, force the push, and if things get broken, I'll just have to delete the rep on the origin server and recreate it there from the backup.01:00
HiramHibbard left01:00
dalias that sounds right to me01:00
groglogic left01:00
HappyLappy joined01:00
OMGOMG i thought destroying the repo was what you wanted01:00
HappyLappy left01:01
dalias heh that's one way of looking at it...01:01
ewnd9 joined01:01
caseydriscoll joined01:01
dhruvasagar joined01:02
b_rare left01:02
mk_qi joined01:03
hholtmann joined01:03
mdiers__ joined01:03
jcardinal Well, I just forced the push, and it worked. The only side effect, which is understandable, is that all of the commits after the first one I edited had their timestamps updated.01:03
mribeirodantas joined01:03
HappyLappy joined01:04
jcardinal OMGOMG: I guess I wanted to rewrite history on the repo; some may consider that destroying it :P01:04
OMGOMG absolutely01:05
robbyoconnor left01:05
OMGOMG look into filter-branch as well01:05
HappyLappy left01:05
el3ctron_ joined01:05
rjhunter joined01:06
jcardinal "Otherwise, all information (including original commit times or merge information) will be preserved." Looks like I should have waited a few minutes longer for a better answer!01:06
hyperair joined01:06
weiyang joined01:06
hahuang65 left01:07
OMGOMG you'd still have to force push01:07
jcardinal I'm ok with that; at least I'd maintain my timestamps01:08
(To be clear, the message is well-taken that I should never rewrite history on a public / shared repo.)01:08
pantsman left01:09
Watabou joined01:10
sohail joined01:11
el3ctron_ left01:11
lindenle joined01:11
knighthawk left01:11
knighthawk joined01:12
SHyx0rmZ left01:13
nnyk_ joined01:13
nnyk_ left01:14
nnyk_ joined01:15
bwreilly left01:16
sohail left01:16
sohail joined01:16
bbloom joined01:16
knighthawk left01:16
nbrosnahan left01:17
sohail left01:18
rjhunter left01:19
wrouesnel1 left01:21
lindenle left01:22
pr0ton left01:23
ewnd9 left01:24
kiba left01:24
jcardinal Ok, history correctly rewritten thanks to git-filter-branch and a handy script from github: https://help.github.com/articles/changing-author-info01:25
Zarthus left01:25
jcardinal Timestamps preserved. Thanks again OMGOMG!01:25
dalias :)01:26
crazydiamond left01:27
M00sL0gB0t_ left01:27
M00sL0gB0t_ joined01:27
King_Hual left01:28
fairuz joined01:29
aaronds left01:31
Guest25228 left01:32
Guest25228 joined01:32
echo-area left01:33
apipkin left01:35
Balliad joined01:39
xobb joined01:39
simesy joined01:41
|Starcraftmazter joined01:41
mloskot left01:43
Ardit left01:44
Starcraftmazter left01:44
rchavik joined01:44
AlecTaylor left01:45
sgu left01:47
penguin42 left01:47
shruggar left01:48
joshbetz left01:51
dhruvasagar left01:52
dhackner left01:53
joaoh82 left01:53
joaoh82 joined01:54
xobb left01:56
nnyk_ left01:56
akiva left01:57
whitby joined01:57
john2x joined01:57
Imagineer joined01:58
joaoh82 left01:58
joaoh82 joined01:59
dsdeiz joined02:00
ericy left02:01
psyl0n joined02:03
psyl0n left02:03
psyl0n joined02:03
Meistarin left02:03
lu_zero left02:05
lu_zero joined02:05
luc_ joined02:06
ni_ joined02:08
codeman left02:08
boombatower joined02:08
jonatasnona left02:08
chrisss404 left02:09
kirin` left02:09
chrisss404 joined02:09
Devastator left02:10
thiago left02:10
jshawl joined02:11
Devastator joined02:11
groglogic joined02:11
Goplat joined02:12
codeman joined02:13
tobiasBora left02:14
Balliad left02:15
groglogic left02:16
Skrypter joined02:16
jmaya joined02:17
akiress joined02:18
ericy joined02:18
kukks left02:18
luxgeek left02:18
b3tamax_ left02:19
b3tamax left02:19
endiruna left02:19
daito joined02:20
jmaya left02:20
Dougie2187 left02:21
harish joined02:21
john2x left02:21
Devastator left02:21
Devastator joined02:21
Dougie2187 joined02:21
lindenle joined02:23
Meistarin joined02:23
Devastator_ joined02:24
GT4066 left02:24
pbrobst left02:25
Devastator left02:25
kukks joined02:26
kukks left02:26
kukks joined02:26
carbon2 left02:28
mmcdaris left02:28
nemesit|znc left02:29
rjhunter joined02:30
s_e joined02:32
echo-area joined02:32
buzzybron joined02:32
ericy left02:35
rjhunter left02:35
nemesit|znc joined02:36
Davey left02:36
Curtisbeef_ joined02:37
Curtisbeef left02:38
jshawl I'm so about git right now02:38
ask me any question02:38
dhruvasagar joined02:38
nerdfiles joined02:39
Celelaptop What happen if I rebase a branch on which another branch is based?02:40
unkmar left02:41
jshawl updates the original branch with the work done with the other02:41
do you have branch names or relevant git commands?02:42
knighthawk joined02:43
stany joined02:43
john2x joined02:43
Celelaptop Imagine an fix_foo branch from which I make a fix_bar branch.02:43
And suddenly I see a typo that I introduced in the fix_foo branch.02:44
caspingus left02:44
git-newbie joined02:44
Celelaptop Then, I'd like to rebase -i branch fix_foo to fix what happened in the past.02:44
Barrayar joined02:44
Barrayar left02:44
john2x left02:45
Celelaptop It's just an hypothetic use case.02:45
nemesit|znc left02:45
k4rtik joined02:46
Celelaptop That I would have encountered if I hadn't been too lazy to create that new branch tonight. :p02:46
git-newbie left02:47
JustinMac left02:47
lavaman joined02:47
lavaman left02:47
Hello71 man git-rebase02:48
gitinfo the git-rebase manpage is available at http://jk.gs/git-rebase.html02:48
simesy left02:48
jcardinal left02:48
simesy joined02:48
Vampire0 joined02:49
Vampire0 left02:49
Vampire0 joined02:49
jshawl I undid a rebase yesterday and now i feel like a boss02:49
jshawl left02:50
echo-area left02:50
el3ctron_ joined02:50
juvenal joined02:51
el3ctron_ left02:51
k4rtik_ joined02:51
k4rtik left02:52
Davey joined02:52
simesy_ joined02:52
saurabh joined02:52
ni_ left02:52
echo-area joined02:52
saurabhGuest9699602:52
ericy joined02:53
Vampire0_ left02:53
simesy left02:53
nemesit|znc joined02:55
CheckDavid left02:57
el3ctron joined02:57
guampa left02:58
nemesit|znc left03:00
liamkeily left03:00
silviof1 joined03:01
SoftwareMechani1 joined03:02
refried_ left03:03
juvenal left03:04
silviof left03:04
Nicholas_Rishel joined03:04
Nicholas_Rishel left03:05
SoftwareMechanic left03:05
Etheco- joined03:08
thiago joined03:10
thiago left03:10
thiago joined03:10
petey left03:10
pandeiro left03:10
petey joined03:11
el3ctron left03:11
codeman left03:11
CKyle joined03:11
el3ctron_ joined03:12
nemesit|znc joined03:12
caspingus joined03:14
rubix joined03:14
el3ctron_ left03:14
rubix I have a question.03:15
btiernay joined03:15
petey left03:16
btiernay Is there a way to push a tag to a remote repository without first cloning?03:16
I'm trying to tag a remote repository from a CI server without having to checkout the repository (no need)03:16
So I just want to tag this "configuration repository" with a tag03:17
Any pointers would be greatly appreciated :)03:17
LBV_User left03:19
caspingus left03:19
rubix I use command: git svn clone -s https://someurl/svn/project to clone an svn repository03:20
which dirs and files layout like this:03:20
|--aaa/ #empty03:20
|--branches/ #r35, updating...03:20
|--|--file103:20
|--|--file203:20
|--|--file303:20
|--|--dir1/03:20
|--|--dir2/03:20
|--|--dir3/03:20
|--tags/ #empty03:20
|--trunk/ #empty03:20
git auto checkout master to track 'trunk r1', and It's empty.03:20
now I get a directory 'project' which contains only '.git/'03:20
iamjarvo joined03:20
rubix git branch -ra outputs:03:20
*master03:20
remotes/dir103:20
remotes/dir203:20
remotes/dir303:20
remotes/trunk03:20
john2x joined03:21
rubix how can I corporate with others?(they use svn)03:21
nemesit|znc left03:21
rubix part of ./git/config:03:22
[svn-remote "svn"]03:22
url = https://someurl/svn/project03:22
fetch = trunk:refs/remotes/trunk03:22
branches = branches/*:refs/remotes/*03:22
tags = tags/*:refs/remotes/tags/*03:22
john2x left03:23
rubix Is there anyone who can answer me?03:24
OR... Does anyone can tell me some forums to ask this question(use git to corporate with svn)?03:24
angelsl joined03:24
nemesit|znc joined03:30
liamkeily joined03:31
Ltk joined03:31
rubix anyone could answer my question? thanks03:31
Ltk left03:31
dhruvasagar left03:31
Celelaptop Sorry, I never used git svn.03:32
rubix all right, but thank u03:34
hyperair rubix: try git svn clone --stdlayout03:35
ericy left03:36
liamkeily left03:36
rubix that is the problem.03:37
I have done this: git svn clone -s https://url/svn/project03:37
the I get an empty directory: 'project'03:37
bobbobbins left03:37
rubix git branch -ra outputs:03:38
*master #which points to trunk r103:38
remotes/dir103:38
remotes/dir203:38
remotes/dir303:38
remotes/trunk03:38
maestrojed joined03:38
rubix svn/project layout:03:39
|--aaa/ #empty03:39
|--branches/ #r35, updating...03:39
|--|--file103:39
|--|--file203:39
|--|--file303:39
|--|--dir1/03:39
|--|--dir2/03:39
|--|--dir3/03:39
|--tags/ #empty03:39
|--trunk/ #empty03:39
lindenle left03:40
Ltk joined03:41
Ltk left03:41
rubix i can checkout remotes/dir1, remotes/dir2, remotes/dir303:41
but how to checkout file1, file2, file3, etc...03:41
also, how to chekcout dir1, dir2, dir3, file1, file2, file3, etc... as a whole branch?03:41
caspingus joined03:42
rubix svn sucks03:42
petey joined03:43
sohail joined03:43
sohail left03:43
sohail joined03:43
mdiers left03:44
sabgenton joined03:45
sabgenton left03:46
dhruvasagar joined03:47
sabgenton joined03:47
caseydriscoll left03:48
abelsiqueira left03:48
knighthawk left03:48
caseydriscoll joined03:48
fairuz rubix | !paste03:49
gitinfo Please paste snippets longer than one line at a pastebin site, such as https://gist.github.com/ rather than in-channel.03:49
sabgenton is there any danger or different in using git rebase master foobranch vs actual checking out foobranch then runing git rebase master ?03:49
does rebase master foobranch care about where you checked out in anyway?03:50
rubix sorry. I apologize for my unknowns.03:51
daito left03:53
ericy joined03:53
nemesit|znc left03:54
mdiers joined03:55
akiva joined03:55
dhruvasagar left03:55
CodeShark joined03:56
Ltk joined03:57
undecim left03:58
Davey left03:58
Noldorin left03:59
k-man joined03:59
psyl0n left03:59
Davey joined03:59
WABSRX3 joined03:59
k-man if i have an untracked file on a branch, what happens to it when i switch branches?04:00
davo joined04:01
k4rtik_ left04:02
master_j joined04:04
rurufufuss joined04:05
liamkeily joined04:07
Davey left04:07
john2x joined04:08
Davey_ joined04:08
Davey_ left04:09
SoftwareMechanic joined04:09
Davey joined04:09
el3ctron joined04:09
el3ctron1 joined04:11
frogonwheels joined04:11
SoftwareMechani1 left04:12
john2x left04:12
el3ctron3 joined04:14
Davey left04:14
el3ctron5 joined04:14
Davey joined04:14
WABSR0L joined04:14
ericy left04:16
subhojit777 joined04:17
CKyle left04:17
liamkeily left04:18
dravidan left04:18
el3ctron7 joined04:21
Davey left04:21
nemesit|znc joined04:22
Davey joined04:22
john2x joined04:24
oojacoboo left04:24
Davey_ joined04:27
Davey left04:27
s0beits0beit|ZNC04:27
el3ctro10 joined04:27
el3ctron7 left04:28
el3ctron5 left04:28
el3ctron1 left04:28
el3ctron left04:28
master_j left04:28
master_j joined04:29
el3ctron3 left04:29
Davey_ left04:29
Davey joined04:29
rubix :quit04:30
rubix left04:30
davetoo joined04:30
bitkiller left04:30
davetoo git-scm.com b0rked :(04:31
"Sorry, no Host Found"04:31
or... maybe it's my firefox :(04:32
ericy joined04:32
groglogic joined04:32
davetoo wow, in fact it is. n/mind.04:33
daito joined04:35
genehack joined04:35
sabgenton davetoo: you had me worried there :)04:35
thiago left04:36
davetoo well I still don't understand what's going on.04:36
I can get it in Chrome, but not firefox, nor wget04:36
kukks left04:37
john2x left04:37
thiago joined04:37
soiitaire joined04:38
davetoo still debugging04:38
cads joined04:38
davetoo I blame New Relic04:40
whitby left04:41
davetoo interesting.04:42
$ w3m -dump http://www.git-scm.com/04:42
Sorry, no Host found04:42
closures999 joined04:45
davetoo Something is giving firefox a redirect from http://git-scm.com/ to www.git-scm.com, and the server isn't configured to serve that hostname04:46
daito left04:47
soiitaire left04:47
Guest25228 left04:48
marlboromoo joined04:49
caspingus left04:50
LuxuryMode joined04:53
PaulCapestany left04:53
mribeirodantas left04:54
davetoo One of my firefox addons is sending stuff to domain-robot.org, and somehow in the process, rewriting the url to www.git-scm.com.04:55
caspingus joined04:55
caspingus left04:55
yhager left04:55
Davey_ joined04:56
diegoviola joined04:56
groglogic left04:56
thiago the server is doing that04:56
davetoo oh?04:56
yhager joined04:57
thiago $ curl -s -I http://git-scm.com | sed -n '1p;/Location/p'04:57
HTTP/1.1 301 Moved Permanently04:57
Location: http://www.git-scm.com04:57
preflex left04:57
preflex_ joined04:58
preflex_preflex04:58
davetoo interesting; once I disabled my NoScript plugin I stopped having issues, and .. in chrome, the location bar is showing 'git-scm.com' rather than www...04:58
though if I add the www in chrome, I get the 'No host found' error04:59
beautifulmind joined04:59
donmichelangelo left05:00
davetoo anyway, what I was after was... looking for the features added/changed between git 1.7.9 and 1.8.current. Cygwin's still on 1.7.905:00
donmichelangelo joined05:01
veebers left05:01
thiago interesting, I see the same05:01
the browser doesn't work, but I do get a page in curl05:01
pekster Smells like botched server-side code based on the user-agent, but I dunno05:02
thiago checking05:02
pekster I never put back my UA switcher plugin :)05:02
davetoo I think I'm looking at several interactions on my end. Wacky firefox plugin behavior among them. I don't understand why I don't get a redirect if I disable my NoScript plugin.05:02
regardless, this same bookmark in this same browser worked earlier today :)05:02
thiago huh, works now05:03
pekster Yup05:03
davetoo any of you in here had the "pleasure" of interacting with git-fusion yet?05:03
pekster I had to do a few refreshes05:03
davetoo or been forced to? :)05:03
that is, Perforce Git-Fusion.05:03
nerdfiles left05:04
thiago I am getting redirected, but the page does work05:04
davetoo Maybe some kind of "sticky" cache and I'm still on a broken node. It'll sort itself.05:05
Sigma davetoo: not yet, but will have too pretty soon. Surely it must be better than git-p4 though, no? :)05:05
davetoo I haven't tried git-p4.05:06
When I walked into this new job five weeks ago they said "here, make this work" :)05:06
john2x joined05:06
davetoo except that .. that version didn't.05:06
Watabou left05:07
rudi_s joined05:07
davetoo Sigma: read my travails here: http://forums.perforce.com/index.php?/forum/27-git-fusion/05:07
I'm 'dcarmean'05:08
the last thread makes me think that... well,05:08
ericy left05:08
davetoo that my git references are going to explode within weeks as soon as they do the usual willy-nilly perforce-side cherrypicking that they like to do05:09
Watabou joined05:10
jon_r left05:10
griotspeak left05:11
kermit left05:12
rjhunter joined05:15
the_cybersphinx left05:15
jon_r joined05:16
kermit joined05:19
ryez joined05:20
Bass10 left05:20
Qo027 joined05:21
CKyle joined05:21
nicedice left05:22
dhruvasagar joined05:23
Qo027 left05:24
Qo027 joined05:25
hobodave left05:25
ericy joined05:25
Qo027 left05:25
noyb joined05:25
ivar_ joined05:28
ivar_ left05:28
dhruvasagar left05:28
robbyoconnor joined05:28
dhruvasagar joined05:29
forrest joined05:29
daito joined05:29
gitinfo set mode: +v05:30
robinsmidsrod joined05:30
forrest Hi guys, I've screwed up a commit where I've somehow pulled in the previous commit (5e45f11, and 315b83): https://github.com/gravyboat/salt/commits/develop . I've tried several ways to fix it, but it seems to create issues because of the other file that was part of the initial commit. How can I fix this previous commit, while leaving the file associated with the commit I somehow grabbed?05:31
buzzybron left05:31
etcetera joined05:33
Tommy[D]_ left05:33
johnnyfuchs joined05:34
johnnyfuchs left05:34
thiago forrest: sorry, I didn't get it05:34
start with what you had, what you did, and what the result was05:34
skorgon forrest: !fixup05:36
gitinfo forrest: So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!05:36
forrest Yea I was trying to avoid doing that for the sake of screwing up that previous commit05:36
jon_r left05:37
john2x left05:38
Davey left05:38
Davey_Davey05:38
forrest thaigo, basically I somehow merged my commit, with a previous commit, I'll take a look at the links that were provided here.05:38
wrouesnel joined05:38
forrest thanks guys05:38
rjhunter forrest: you had two commits, you squashed them into one commit, you pushed, and now you want to separate out the commits again?05:38
forrest I never squashed them rjhunter05:39
I made changes to a file, and made my commit, which somehow lead me to creating what appears to be a 'dup' of the previous commit. I'm pretty sure this was caused by pulling down the upstream, and somehow either screwing up my merge, or making my commit, then merging the changes, which attached it to that other commit05:40
Davey left05:41
CKyle left05:41
Davey joined05:41
Davey left05:42
simesy_ left05:42
simesy joined05:42
Davey joined05:43
ErKa left05:43
Dreadnaught joined05:45
Tommy[D]_ joined05:46
dsdeiz hey, so say this commit is a part of a merge commit. is there a way to know that? not sure if this makes sense tho :D05:46
say i have only the commit hash. how do i know what the commit hash of the merge commit it belongs to05:46
rjhunter dsdeiz: `git show` shows the parents of a merge commit05:47
(among other things)05:47
dsdeiz: oh wait, you want to go the other way? you want to *find* the merge commit?05:48
dsdeiz: that's harder (though still possible) because commits only list their parents, not their children05:48
dsdeiz yeah, it's the other way around05:49
marthinal joined05:49
etcetera left05:50
rjhunter dsdeiz: if you know a branch that has the merge commit on it somewhere, you can use `git log mybranch` and look for lines that look like Merge: 315b83 a0324c05:50
dsdeiz: you can narrow it down with tooling, but if you're just casually looking for it that's probably the easiest05:51
maestrojed left05:51
dsdeiz ah cool thx05:51
rjhunter dsdeiz: you can also say `git log mycommit..mybranch`05:52
quejajajajaja joined05:52
quejajajajaja Hello05:52
gitinfo quejajajajaja: 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.05:52
petey left05:52
quejajajajaja On Gihub, if I am forking a programming and creating a setup file, what version do I specify if there is no version given in the program I am forking?05:52
dunpeal joined05:52
jaimef joined05:52
dhruvasagar left05:52
dunpeal What's the difference between `--all` and `--mirror` for git push?05:53
dhruvasagar joined05:53
thiago quejajajajaja: version?05:53
quejajajajaja thiago, the version of the program05:53
thiago dhruvasagar: --all pushes refs/heads/*05:53
quejajajajaja in setup.py I need to include a version05:53
thiago dhruvasagar: --mirror pushes refs/* and also deletes05:53
quejajajajaja: non-Git question. Git does not know anything about versions.05:54
dhruvasagar thiago: ?05:54
dunpeal thiago: so --mirror will also push tags and remote branch references?05:54
quejajajajaja well thiago, it is closely related05:54
thiago dhruvasagar: oops, wrong person :-)05:54
dunpeal: yes05:54
dhruvasagar thiago: np05:54
thiago quejajajajaja: no, it isn't. The version is something you define. Write whatever you want.05:54
dunpeal thiago: is there anything else significant that --mirror will push and --all will not?05:54
quejajajajaja ok05:55
davetoo wow, I'm impressed. I got git to compile under cygwin, and it's been passing tests for a couple of minutes now.05:55
rjhunter davetoo: congratulations :-)05:55
thiago dunpeal: tags, remote branches, anything else under refs/ that usually isn't exposed (backup filter-branch, etc.)05:55
davetoo ..to the git devs :)05:55
thiago dunpeal: what for? There are binaries for msys/mingw.05:55
dunpeal thiago: so --all, followed by a --tags push, should be sufficient in most cases... thanks.05:56
thiago dunpeal: yes05:56
dunpeal: note that --mirror deletes branches that don't exist locally. --all has no such behaviour.05:56
yhager left05:57
madewokherd left05:57
dunpeal *nod*, thanks.05:57
davetoo sweet! even gitk is working!05:58
thiago quejajajajaja: do you want to extract something from git that might be used as a version?05:58
quejajajajaja thiago, yes05:58
thiago quejajajajaja: see the output of git describe05:58
quejajajajaja thank you05:59
maestrojed joined05:59
jaimef left05:59
forrest Thanks for your help guys.06:00
forrest left06:00
jaimef joined06:00
aartist left06:00
davetoo wow. Looking at git's repo in gitk is.. impressive.06:01
dhruvasagar left06:02
tpollard left06:02
dhruvasagar joined06:03
kukks joined06:03
davetoo .. the github network diagram is equally impressive06:05
purpleidea joined06:06
HELLC joined06:07
WaReZ joined06:08
jAyenGreen left06:08
aartist joined06:08
purpleidea hi there, i have a question about branches: i'm currently working on git master and i've made some changes to the code, some of which i've added (with git add -p) and some changes are still unmodified. I decided i want to start a new feature branch from the last commit. I've tried stashing, and then branching in an attempt to get a clean tree to work on. I'd like the current WIP changes to be a separate feature branch too if possible. What are the c06:09
Dougie187 left06:09
daito left06:14
ericy left06:14
jaseemabid joined06:16
sgo11 joined06:16
a-l-e joined06:16
closures999 left06:16
sgo11 why git does not sync my empty directories? they are important to hold temp files.06:16
purpleidea sgo11: git doesn't track empty dirs06:16
closures999 joined06:17
purpleidea sgo11: you can put a .foo dot file inside and add it if you need a dir. also maybe a README file or similar.06:17
k4rtik joined06:18
jaseemabid left06:18
sgo11 purpleidea, I just don't understand why git does not do this. track file all permissions and empty dirs should be very easy. but git just ignore all these important changes.06:18
jaseemabid joined06:18
jaseemabid left06:18
purpleidea sgo11: what are you actually trying to do?06:18
rouf joined06:18
ewnd9 joined06:19
purpleidea sgo11: this is part of git design. I can't change that. I've offered you a work around. If you describe the actual problem you're trying to solve, I might be able to help. See: "x y problem".06:19
JustinMac joined06:19
haarg git tracks content, not filesystems06:20
Imagineer left06:21
sgo11 purpleidea, ok. thanks a lot. I will use your workaround. I asked file permissions problem the day before yesterday. git ignores my file permissions change. I have to write a script to update those permission change after git pull. anyway, I have to accept the current design anyway.06:21
closures999 left06:21
noyb left06:21
grahamsavage joined06:22
|Starcraftmazter left06:22
rjhunter sgo11: you may be using git for something that git isn't very good at.06:22
moritz !deploy06:22
gitinfo Git is not a deployment tool, but you can build one around it(in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/the-list-and-irc/deploy.html06:22
grahamsavage hey. i'm looking for a graphical UI for git for ubuntu.. i've got git cola but it's nowhere near as good as osx's tower06:23
git's awesome for deployment06:24
don't let the nay-sayers tell you otherwise06:24
rjhunter says "nay"06:24
sgo11 well. I understand git is not a deployment tool. but I just don't understand why git can not be a deployment tool. file permission track should be very easy to handle. I am very happy with git for my current work except not tracking empty dirs and file permissions. but anyway, sorry about the complain. I will accept the current design. thanks a lot again.06:24
davetoo left06:24
dreiss left06:25
grahamsavage sgoll: it's very easy to use as a deployment tool.. we've got it setup so we can deploy multiple apps to multiple servers06:25
sgoll: file permissions you build on top off git06:25
Gamecubic left06:26
grahamsavage ok so basic approach i like to go with.. is on the server create a cache diretory which has like /srv/urcompany/repositories/appname and set up your deployment to push to that06:26
rjhunter purpleidea: did you figure out your branch/WIP situation?06:26
purpleidea rjhunter: i did not06:26
LuxuryMode left06:26
Goplat left06:27
iamjarvo left06:27
akurilin left06:27
grahamsavage sgoll: then when you deploy.. basically do a cp -R into a new directory excluding the .git directory... run a script to change all the file permissions (or even better use setfacl to set the perms on the parent directory and just have the majority of them inherit).06:27
iamjarvo joined06:27
threesome left06:27
grahamsavage run any scripts you need too (processing js files / whatever).. then update the symlink that points at the current working copy06:28
wirrbel joined06:28
sgo11 grahamsavage, ok. thanks. I am currently using a script to do these jobs. update permission and create empty dirs.06:28
grahamsavage sgoll: empty directories.. you have two options.. either you can just stick a .GIT_KEEP file in each dir06:28
and commit that06:29
or create them manually.. we symlink directories we don't want to get blown away each release06:29
purpleidea rjhunter: do you have any tips?06:29
(or can you describe the method)06:29
daito joined06:29
grahamsavage sgo11: https://gist.github.com/anonymous/550fcf27c6341eeb5540 << that's what we use for setting the permissions for the apps06:30
rjhunter purpleidea: i'm trying to get my head around your exact situation, but here's one option that might be illustrative:06:30
sgo11 grahamsavage, ok. thanks a lot. finally, you type my nick correct. :)06:30
Search12 joined06:30
grahamsavage sgo11: lol.. tab tab06:30
purpleidea rjhunter: (it's sort of like: i've been hacking on master instead of doing feature branches, but now i want to work on different features in parallel, and the current work-in-progress should turn into a feature branch)06:31
kukks left06:31
sgo11 grahamsavage, ^_^06:31
iamjarvo left06:32
rjhunter purpleidea: commit your work (to master is fine). make a new branch "feature1". cherry-pick the relevant commits for "feature1" from master. do the same for feature2. reset "master" to origin/master.06:32
dhruvasagar left06:32
wirrbel left06:32
dhruvasagar joined06:32
ericy joined06:32
User458764 joined06:32
rjhunter purpleidea: does that make sense? does it apply to your situation?06:32
JohnBat26 joined06:33
purpleidea rjhunter: cool idea, but i don't think it does because i'm not ready to 1) commit my changes, and 2) i still want to keep some of the code staged, and some unstaged... it was my mistake for hacking in place, instead of working on a feature branch.06:33
rjhunter purpleidea: seriously, don't worry about "ready to commit". just make sure the commit messages say "WIP" on them so you know not to push them.06:34
JohnBat26 left06:34
purpleidea i tried to git stash, and then feature branch, and other things, but nothing worked as expected :P i hit the maximum of my git skills, and now i need to learn more.06:34
rjhunter: but i want to unstage them all later, and i'd like to keep the index correct...06:34
maleknet joined06:36
JohnBat26 joined06:36
rob_w joined06:37
rjhunter purpleidea: turn the index you want to keep into a commit. turn the work tree you want to keep into another commit. label them appropriately so you can find them again later. when you're ready, use git checkout and git reset to put the working tree and index back to the state you want06:38
purpleidea rjhunter: okay, i'm going to try this...06:38
rjhunter purpleidea: you can throw away those WIP commits once you're ready to replace them with "real" ready-to-push commits06:38
purpleidea (cp -a git-thing git-thing.backup) ;)06:38
john2x joined06:39
rjhunter purpleidea: yay for safe learning :-)06:39
joelrobichaud left06:39
john2x left06:40
ThomasLocke joined06:40
aartist left06:40
john2x joined06:40
purpleidea rjhunter: two commits made. now i branch, right? then what was the next step sorry? (i've never cherry-picked)06:40
(i feel like a git virgin saying that)06:41
rjhunter purpleidea: cherry-pick is really just the same as you looking at some change and doing the same thing yourself, committing the result.06:41
noyb joined06:41
rjhunter purpleidea: like applying a patch + committing with the same message06:41
purpleidea: so branch feature1 from origin/master, check it out, then look through `git log master` (or wherever your mixture was) to find the relevant commits06:42
purpleidea rjhunter: done...06:43
lite_ joined06:43
rob_w left06:43
simesy left06:44
rjhunter purpleidea: and I guess you can do the same for feature206:44
purpleidea rjhunter: (reading cherry pick docs...)06:44
rjhunter: feature i can do after i sort this all out... it hasn't been started yet which is good.06:44
simesy joined06:44
john2x left06:44
purpleidea rjhunter: so according to cherry-pick it applies git commits... however on my new feature branch (since it's branched from master) it already has the two XXX WIP commits applied ...)06:45
did i need to reset the branch somewhere first? or?06:45
or branch from earlier on ?06:46
rjhunter purpleidea: it may not have been clear, but when I suggested branching feature1 from origin/master, that's actually different from master06:46
hoschi joined06:46
purpleidea rjhunter: oh. so i branch from the commit BEFORE my two XXX WIP commits, right?06:47
rjhunter purpleidea: you can literally say "origin/master"06:47
purpleidea (which is where origin/master points of course06:47
rjhunter purpleidea: `git checkout -b feature1 origin/master`06:47
sgo11 left06:47
User458764 left06:47
rjhunter purpleidea: you can change it after the fact, of course (with git reset)06:48
purpleidea: but i figure we'll walk through doing it "cleanly"06:48
simesy left06:48
jargon joined06:49
dsdeiz left06:49
purpleidea rjhunter: okay, i've figure it out (that part is done) and i understand what's going on. Pedantic question: "is it more technically correct to branch from some sha1 than origin/master (in case i hadn't pushed some commits to origin?)"06:49
rob_w joined06:50
kukks joined06:50
dsdeiz joined06:50
rjhunter purpleidea: git branch (or git checkout -b) always resolves whatever you give it to a sha106:50
closures999 joined06:51
rjhunter purpleidea: there are some options around "tracking upstream" that like to know what the branch was called if you want to know things like your branch is ahead of upstream by 3 commits06:51
purpleidea rjhunter: okay. so i'm ready to cherry pick, and i know the sha1's of the two commits. How do I get them to be the unstaged, and staged indexes respectively? (instead of just committing them on)06:51
rjhunter: got it.06:51
Search12 left06:52
matanya joined06:53
jon_r joined06:53
lindenle joined06:53
rjhunter purpleidea: so just to clarify, you have just the two commits (one destined for the work tree, and one for the index)?06:54
purpleidea: in that case, cherry-pick won't be necessary06:54
purpleidea rjhunter: correct.06:54
Raging_Hog joined06:54
rjhunter purpleidea: sorry, i thought you had a few "real" commits already06:54
purpleidea: cherry-pick is good to bring those in06:55
SamB that sounds suspiciously like "git stash"06:55
purpleidea (terminology check: index means "things that are staged?)06:55
SamB: i thought so too, but I was never able to "make it work".06:55
rjhunter purpleidea: yes, the index is "the staging area"06:56
purpleidea rjhunter: cool.06:56
pantsman joined06:57
WaReZ left06:57
WaReZ joined06:58
l0cust joined06:58
harish left06:59
purpleidea rjhunter: so what should i do now?06:59
l0cust Hey, y'all. Friend and I are having an argument as to who has done more work on our git-managed project. Is there a git command that would give relevant statistics?06:59
purpleidea l0cust: git log07:00
iamjarvo joined07:00
purpleidea l0cust: or maybe: http://gitstats.sourceforge.net/07:00
yhager joined07:00
rjhunter purpleidea: so you can use `git checkout --patch 315b83` to check out the contents of commit 315b83 to your working tree. I suggest starting with what you eventually want in your index.07:01
eijk joined07:01
purpleidea rjhunter: don't i want to start with what should be staged first?07:02
grahamsavage holy crap07:02
smartgit is awesome07:02
i just tested out 8 git clients.. smartgit really takes the cake07:02
ewnd9 left07:02
pen joined07:03
l0cust purpleidea: thank you, gitstats seems to be what I was looking for07:03
nbrosnahan joined07:03
purpleidea l0cust: np07:03
l0cust: (i've never tried it, so ymmv)07:03
quejajajajaja hey guys, i cloned a project from my github page and then I made changes to the clone on my computer07:03
nbrosnahan left07:03
rjhunter purpleidea: yes. you can put it straight in your index (skipping the working tree) with `git reset --soft`, but that also updates HEAD (which you may or may not want)07:03
quejajajajaja and tried pushing it, but no changes were made07:03
git push origin master07:03
is the command i used07:03
I created a new directory structure and a set up file07:03
why isnt it showing up on my github?07:04
jon_r left07:04
grahamsavage quejajajajaja: you done a commit?07:04
type git status.. do you see any files?07:04
quejajajajaja grahamsavage, how do I do a commit?07:04
git commit ?07:04
grahamsavage yep07:04
rjhunter purpleidea: you can use `git checkout --patch desiredindex` and `git add`, then another `git checkout --patch desiredworkingtree`07:04
h0rrorvacui left07:04
grahamsavage find an intro tutorial for git somewhere... some of the things can be confusing at first.. but a 15min tute will show you branching merging pushing pulling etc07:05
nbrosnahan joined07:05
Cromulent joined07:05
iamjarvo left07:05
soee joined07:06
rjhunter quejajajajaja: the git main workflow is: repeat ( change files in your work tree, stage the changes for commit, commit ) and then once you're happy you push those commits to someone else (like github)07:07
purpleidea rjhunter: just working through this... the first one prompted me with do you want to add this, sort of like git add --patch... y,y,y,y,y,y... all went well...07:07
rjhunter purpleidea: you can specify a path (like .) instead of --patch if you'd rather not check the changes as you go07:08
rath joined07:09
purpleidea rjhunter: oh that's okay. SO: git d --cached in the original git backup folder, matches the git d --cached in the branch folder.07:09
LionKing joined07:09
purpleidea GREAT news so far.07:09
rjhunter: now i do the SECOND checkout, but i don't want to add any of the files to the index. do i just do n,n,n,n,n ?07:09
ericy left07:10
sohail left07:10
purpleidea rjhunter: so doing n,n,n,n is as if nothing happened.07:11
Apply this hunk to index and worktree [y,n,q,a,d,/,K,g,e,?]? n07:12
(i just want to apply to worktree and not index actually)07:12
ewnd9 joined07:12
noyb left07:12
cbreak-work joined07:13
purpleidea rjhunter: Maybe I could just copy the files from git master (in a different folder) to this git branch07:13
rjhunter purpleidea: sorry, i might have misled you again -- i forgot that `git checkout` (and everything, actually) always modifies the index on the way to the worktree07:13
purpleidea rjhunter: being mislead here is okay. i have backups, and i'm learning.07:13
rjhunter: also, i think this works. I just now have to copy the files over from the master...07:13
robbyoconnor left07:14
rjhunter purpleidea: but if you throw away the current changes, then you should get what you want with something like `git checkout worktreesha .` `git reset indexsha .`07:14
robbyoconnor joined07:14
purpleidea rjhunter: you lost me there...07:14
and actually, it won't let me checkout master because: "07:15
error: Your local changes to the following files would be overwritten by checkout:07:15
Dreadnaught left07:15
Cromulent left07:16
rjhunter purpleidea: yup, so let's clean up first -- `git reset .` to put the index back to HEAD (unstage everything). Then `git checkout .` to put the worktree back to the index.07:16
steveeJ left07:16
pen left07:17
rjhunter (those two commands are a handy pair, and are useful quite often)07:17
purpleidea rjhunter: actually it's not back to the clean branch... i can do this though.07:18
rjhunter purpleidea: `git clean` is sometimes a handy third item in that 'cleanup' set07:19
pen joined07:19
robbyoconnor left07:20
robbyoconnor joined07:20
purpleidea rjhunter: okay i restored my backup :P should i still do the two inital WIP commits ?07:21
Grant484 left07:21
Grant484 joined07:22
pantsman left07:22
rjhunter purpleidea: yup, sure -- the sequence should look something like `git commit -m 'WIP: the index for feature1' && git add . && git commit -m 'WIP: the work tree for feature1' && git checkout -b feature1 origin/master && git checkout master:/'work tree' && git reset master:/index .`07:24
purpleidea git checkout master:/'work tree' <- master:/sha1_of_work_tree right?07:25
rjhunter the :/ syntax is one of the many ways you can specify a sha07:26
purpleidea rjhunter: ah07:26
okay let me try this07:26
rjhunter it means the first commit which has a commit message matching this pattern07:26
purpleidea TIL07:26
ericy joined07:26
purpleidea makes sense. / is search07:27
rjhunter exactly07:27
purpleidea OH. it clicked why you did that. FANCY07:27
rjhunter: you07:27
're spoiling me07:27
rjhunter :-)07:28
dreiss joined07:28
harish joined07:28
rjhunter I need to head off, but I'll join from my phone in case I've sent you in a horribly wrong direction or something :-)07:29
jarr0dsz joined07:30
juril joined07:30
purpleidea rjhunter: actually the search didn't work, but i can do it manually...07:30
rhunter joined07:30
netiul joined07:31
netiul left07:31
netiul joined07:31
rjhunter left07:32
Nevik hmmmm07:32
does anyone know who maintains git-scm.com?07:33
stany left07:33
arjun_ joined07:33
Nevik the site was unreachable for me (timeout) last night, and now i'm getting a simple html response saying "Sorry, no Host found"07:33
dhruvasagar left07:33
_W_ left07:33
stany joined07:33
FrodoTheHobbit joined07:34
j416 Nevik: http://downforeveryoneorjustme.com/git-scm.com07:34
dhruvasagar joined07:34
jarr0dsz left07:34
Nevik j416: yes, that's why i want to investigate it :P07:34
nbrosnahan left07:34
Nevik j416: can you do a ping real quick and see what ip you get for it?, just to double check07:34
purpleidea rhunter: is this rjhunter?07:35
j416 Nevik: https://github.com/github/gitscm-next07:35
kjellski joined07:35
j416 Nevik: if I read the "Contributing" part right, apparently git-scm.com is written by... me07:35
quite a surprise07:36
Kartagis anyone know how repos can be created via web? bash commands?07:36
purpleidea @later tell rjhunter the first checkout part didn't work, but thank you for all the help!07:36
rjhunter joined07:36
purpleidea rjhunter: the first checkout part didn't work, but thank you for all the help!07:37
rjhunter purpleidea: yes, this is rjhunter but I'm on a phone now so it's harder to type effectively07:38
j416 Nevik: 75.101.145.8707:38
purpleidea rjhunter: nobody should have to do git on a phone! i appreciate all the help though07:38
rjhunter ... Or stay connected, for that matter07:38
stany left07:38
Nevik hm07:38
j416 looks like it's heroku07:39
stodan joined07:39
Nevik i get a different (single) ip from my local cache and google dns07:39
beawesomeinstead left07:39
Nevik opendns has the one you mentioned07:39
that is rather.... weird07:39
j416 so use that one? :)07:39
Nevik the thing is, my router is not set up to use google dns, but the one my ISP provides07:39
j416 strange07:40
Nevik sooo somehow faulty DNS entries go spread around, it seems07:40
j416 thanks for reminding me though to use google DNS07:40
rhunter left07:40
purpleidea rjhunter: i'm going to read a bunch of git stuff to learn a bit more and come up with a solution!07:40
Nevik lol07:40
beawesomeinstead joined07:40
j416 Nevik: I've been meaning to change the dns settings for a while but I keep forgetting07:41
arjun_ left07:41
cff joined07:41
j416 the DNS my ISP provides isn't very stable07:41
Nevik j416: i recommend not using google dns07:41
j416 really07:41
why?07:41
rjhunter purpleidea: awesome :)07:41
Nevik ive heard it's somewhat unreliable07:41
j416 tss07:41
Nevik j416: most especially that they dont honor dns timeouts07:41
j416 Imma use it anyway07:41
Nevik lol sure :P07:41
why not use opendns :P07:41
j416 better?07:41
hah, just found it07:42
their site says "The safest, smartest, fastest and most reliable DNS on the planet."07:42
purpleidea rjhunter: i owe you some puppet help if you need it!07:42
j416 I'm sold07:42
talk about falling for marketing07:42
lol07:42
brb07:42
diosmiux left07:43
j416_ joined07:44
h_kon joined07:44
j416_Guest266707:44
j416Guest2131807:44
ericy left07:45
rjhunter purpleidea I'm not using much Puppet right now but who knows what the future might bring :)07:45
Guest2667j41607:45
TomyLobo left07:45
j416 left07:45
j416 joined07:45
purpleidea rjhunter: indeed! thanks again07:45
j416 sigh, silly nick implementation07:45
Nevik: thanks07:45
Nevik++07:45
mishok13 joined07:45
pheaver left07:45
j416 off to work o/07:45
Nevik lol07:46
j416: uhhh glad i could help? xD07:46
Kartagis http://www.git-scm.com/docs/gitweb gives me Sorry, no host found07:46
Nevik Kartagis: same here. there's probably something up at their host07:47
Guest21318 left07:47
Nevik it's a problem with getting the wrong ip from dns, so probably heroku changed IPs or something07:47
dreiss left07:50
pdtpatrick joined07:52
pdtpatri1k left07:53
Sylario joined07:54
jnavila joined07:54
alorence joined07:54
beautifulmind left07:54
a-l-e left07:54
simesy joined07:55
robbyoconnorr0bby07:56
r0bbyr0bby_07:56
r0bby_robbyoconnor07:56
kukks left07:57
_W_ joined07:59
katterstrophe joined07:59
Grant484 left07:59
Xethron joined07:59
simesy left07:59
Xethron left07:59
Xethron joined07:59
harish left08:02
ns5 joined08:02
ns5 how to change author of all commits?08:03
Kartagis anyone know how repos can be created via web? bash commands?08:04
Norm_ left08:04
k4rtik left08:04
Grant484 joined08:05
nbrosnahan joined08:05
harish joined08:05
threesome joined08:06
purpleidea left08:06
bvi joined08:06
purpleidea joined08:08
purpleidea left08:08
purpleidea joined08:08
canton7 Kartagis, local repos? repos on github?08:08
Kartagis canton7: repos on my server08:08
canton7 Kartagis, gitolite can be set to create a repo the first time you push to a particular address08:09
lacrosse_ left08:09
Kartagis canton7: hrm, do you know of drupal?08:09
canton7 I do. python framework right?08:10
Kartagis no, php08:10
canton7 ah yeah, getting it mixed with django08:10
jon_r joined08:10
gitinfo set mode: +v08:10
gua_ould joined08:10
Kartagis I was looking to create a similar functionality. on their website, you create a project, hence a repo08:11
want a screenshot?08:11
gua_ould left08:11
canton7 they're probably calling 'git init --bare' somehow, either via system() of via one of the many git wrappers for php08:12
gua_ould joined08:13
GeertV joined08:13
Exdaix left08:15
tirengarfio_ left08:15
tirengarfio joined08:16
thierryp joined08:16
katterstrophe left08:18
armin_w joined08:18
harobed_ joined08:18
harobed_ left08:18
harobed_ joined08:19
h0bbit_ joined08:20
ntio joined08:20
joaoh82 left08:20
Asenar joined08:20
irqq joined08:21
joaoh82 joined08:21
mitz left08:23
simesy joined08:23
mitz joined08:23
bkhan joined08:24
Gonzo89 joined08:25
Sonderblade joined08:25
Sonderblade left08:26
Sonderblade joined08:26
thiago left08:27
TomyWork joined08:30
stany joined08:33
stany left08:33
TaylanUB joined08:34
stany joined08:34
stany left08:34
freimatz_ joined08:34
freimatz_freimatz08:36
tvw joined08:36
maestrojed left08:38
jarr0dsz joined08:38
freimatz left08:38
master_j left08:39
nafg___ joined08:39
jarr0dsz got disconnected, having some troubles getting git repo to work correctly after removing the .git from my local project08:40
milki jarr0dsz: the .git is pretty important08:40
jarr0dsz i removed it because there where some issues on an older project and wanted to start fresh08:40
milki jarr0dsz: hope you have a !backup08:41
gitinfo jarr0dsz: Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups08:41
gasbakid joined08:41
milki jarr0dsz: do you have a remote you can just clone again?08:41
jarr0dsz no need for the commit history so removed .git and copied the config from an backup now try to deploy again but this fails with several errors08:41
milki o08:41
jarr0dsz: you can just git init then08:41
adac joined08:41
milki wait, what does deploy do here?08:41
jarr0dsz yes i have done git init locally and copied the config from a backup ( which hold the remote git repo info )08:41
slassh joined08:41
jarr0dsz git push origin master goes okay but let me gist the error trace08:42
milki can you step back and explain what you are trying to do08:42
Kartagis I have /var/www/git/my-project.git on the server owned by git:apache and of which perms is 755. I try to push to it, and I get fatal: 'my-project.git' does not appear to be a git repository08:42
milki Kartagis: what is your git url?08:42
Kartagis milki: origin?08:43
milki Kartagis: yes, git remote -vv08:43
jarr0dsz anyone can help me fix these? a bit lost on this https://gist.github.com/anonymous/768890008:43
thierryp left08:43
rhunter joined08:43
jarr0dsz i have the remote repo still there but not with latest changes08:43
milki jarr0dsz: git init doesnt give you a remote08:43
thierryp joined08:43
milki jarr0dsz: git remote -vv?08:43
jarr0dsz preferrable i would like to clearout the remote repo so i can do just git push origin master clean08:44
Kartagis origin [email@hidden.address] (fetch)08:44
origin [email@hidden.address] (push)08:44
milki: ^08:44
jarr0dsz git remote -v yes i already checked that is correct 2 entry's "origin fetch and push "08:44
milki Kartagis: and how is that supposed to map to /var/www/git/my-project.git?08:44
jarr0dsz with correct path to my remote .git repo08:44
jeff joined08:44
Eridius joined08:44
he_re joined08:44
Eridius left08:44
Eridius joined08:44
jeff left08:44
jeff joined08:44
lllama joined08:44
jarr0dsz so i changed git reset --hard origin/master to origin only but fails also08:44
kenyon joined08:45
jarr0dsz assuming it will take the master branch automatically08:45
milki jarr0dsz: did you fetch?08:45
intellix joined08:45
jarr0dsz milki i dont want to fetch i want to write my local changes to remote repo, i don't want the remote repo data anymore08:45
milki jarr0dsz: you cant refer to origin/master until you have fetched08:45
Hamled joined08:45
Kartagis milki: it should be [email@hidden.address] ?08:45
jarr0dsz hmz okay, can i just reset to origin? instead of origin/mater08:46
or would it be better removing the remote repo and start from scratch?08:46
milki jarr0dsz: no that wont work08:46
Kartagis: /var/www/git/my-project.git would definitely work08:46
jarr0dsz fetching is not an option there is an older version on the remote git repo, is there any shortcut i can do to fix and start cleanly?08:46
Misan joined08:47
milki jarr0dsz: why do you need to reset?08:47
jarr0dsz perhaps remove the remote git repo init bare it again then push all my local changes?08:47
milki jarr0dsz: you can just git push -f probably08:47
jarr0dsz already did that too milki pushing is not an issue that works08:47
rhunter left08:47
milki jarr0dsz: then i totally dont understand your situation08:47
jarr0dsz i need to reset cause i have some issues i could not track back, so i copied an working older backup to my working station08:47
harish left08:48
jarr0dsz i can push.. but not deploy it fails with https://gist.github.com/anonymous/768890008:48
milki what in the world is deploy08:48
jarr0dsz because locally i have a new git init, as you stated this reference to origin/master would not work without a fetch which is non wanted08:48
so not quite sure how i best would fix now08:48
milki if you cant get someone else to understand, starting over from scratch would probably solve your problems08:49
Kartagis milki: that worked, thanks08:49
jarr0dsz never mind the deploy i have capistrano non git related the problem is it tries to git reset --hard origin/master08:49
halu joined08:49
milki well, wherever its doing that, it doesnt know what your remotes are08:49
Kartagis milki: can I set a path so that git would be relative?08:50
purpleidea left08:50
Kartagis git/*08:50
milki Kartagis: it defaults to the relative home of your remote user if you dont put a leading /08:50
jarr0dsz git branch shows me *master08:50
milki Kartagis: jarr0dsz that has nothing to do with your remote08:50
er08:50
mixing up people here now08:50
jarr0dsz locally but argh don't know what the issue is even sa bit hard to look for a solution then ;p08:51
hahuang65 joined08:51
lb1a joined08:51
milki do you even know where these errors are?08:51
are they remote? are they local?08:51
purpleidea joined08:51
Kartagis milki: so [email@hidden.address] would work as well?08:51
ianmcorvidae left08:52
milki Kartagis: no, you have a leading / now08:52
ianmcorvidae joined08:53
ericy joined08:53
Kartagis milki: in another project, they tell me to set the url [email@hidden.address] I want a similar structure. how should my fs structure be?08:54
mastro joined08:54
milki Kartagis: you need to find the homedir of your git user08:54
then put my-project.git there08:54
Kartagis milki: in such a structure, are these users real?08:55
Grant484 left08:55
Kartagis or can they be virtual?08:55
milki must be a real user08:55
you are using ssh08:55
johnkevinmbasco left08:55
milki no such thing as a virtual user with ssh08:55
Kartagis hrm08:56
milki Kartagis: you might be looking at gitolite, but you dont seem to know linux enough to use that08:56
Grant484 joined08:56
psoo joined08:56
Kartagis so, a $HOME is essential08:56
Balliad joined08:56
Kartagis milki: I know linux enough (I think it is enough)08:56
just, I didn't know git pushed over ssh08:57
psoo left08:57
Kartagis then again, I should have gotten that from [email@hidden.address]08:57
damn it08:57
psoo joined08:57
Kartagis (not you, me)08:57
lllama left08:57
milki Kartagis: well, if you can, check out !gitolite if you want those nice paths08:58
gitinfo Kartagis: Gitolite is a tool to host git repos on a server. It features fine-grained access control, custom hooks, and can be installed without root. Download: https://github.com/sitaramc/gitolite Docs: http://gitolite.com/gitolite/08:58
milki im going to bed -.-08:59
hahuang65 left08:59
angelsl left09:02
Rob___ left09:03
ns5 left09:04
el3ctro10 left09:04
ns5 joined09:06
el3ctron joined09:06
Cathy [01:55:57] <milki> no such thing as a virtual user with ssh09:06
of course there is09:06
yhager left09:06
Cathy ssh is commonly used to log into shell accounts on the system, but it obviously doesn't have to used that way09:06
it could be backed by an arbitrary authentication paradigm09:06
dalias well the sshd implementation depends on there being a unix account corresponding to the client-requested username09:07
Cathy you mean the OpenSSH implementation specifically09:08
grawity AFAIK, Launchpad has a custom sshd written in twisted-conch that does only virtual users09:08
ns5 left09:08
dalias cathy, and dropbear09:08
Cathy nothing stops you from writing your own sshd anyway09:08
dalias altho dropbear may support some virtual user thing if you run the daemon as non-root09:08
i forget09:08
grawity so yes, most common implementations require this, but the protocol certainly does not...09:09
Cathy and i'm not actually sure it's true that OpenSSH requires shell accounts09:09
OpenSSH allows arbitrary PAM authenticaiton09:09
dalias it probably doesn't09:09
Cathy you could write a PAM module that is not backed by shell accounts09:09
dalias if you use pam creatively09:09
altho PAM is at the system level09:09
grawity Cathy: it *does* require that the account could be looked up with getpwnam() and similar interfaces, as far as I know09:09
dalias so the admin would be responsible for setting up the non-unix-account ssh setup09:09
grawity Cathy: because it needs to switch the server process to some UID09:10
Cathy you could replace those functions with your own shared library when you load sshd09:10
ns5 joined09:10
ns5 left09:10
grawity Cathy: but then one could just write a NSS (libnss_*) module that returns all tohose 'virtual' users09:10
Cathy good idea09:10
grawity like the existing ones for LDAP, /etc/passwd, Hesiod...09:10
so the line between 'real' and 'virtual' users is kinda thin09:10
Cathy it's also possible to run an sshd from within a virtual machine09:11
we could call those virtual users09:11
ericy left09:11
dalias :)09:11
moritz calls virtual users "bots"09:13
adhawkins-awayadhawkins09:13
lite_ can i revert a specific file to whatever version it had before I branched out ?09:15
Cathy try git checkout09:15
teran left09:16
Cathy well, it might be more useful to say try `man 1 git-checkout`09:16
grawity or `man git checkout`09:16
gitinfo the git-checkout manpage is available at http://jk.gs/git-checkout.html09:16
Nevik indeed09:16
teran joined09:16
Nevik lite_: git checkout <desired revision> -- path/to/file09:17
lite_ i just did that but my working dir still appears to be clean09:17
wait. 1 moment09:18
h0bbit_ left09:18
Nevik lite_: then the file probably hadnt changed09:18
lite_ yeah sorry. i had the wrong revision.09:19
blinkdesign joined09:20
h0bbit_ joined09:20
lindenle left09:20
joaoh82 left09:21
FerreusR joined09:21
teran left09:21
joaoh82 joined09:21
Cathy grawity: did you know that `man git checkout` apparently doesn't work on OS X?09:23
gitinfo grawity: the git-checkout manpage is available at http://jk.gs/git-checkout.html09:23
LionKing Cathy: try git help checkout09:23
Cathy it displays error message "No manual entry for checkout" and then shows the man page for git(1)09:23
LionKing: i know how to get to the man page09:23
i just thought grawity might find that fact interesting09:23
fairuz left09:23
LionKing Cathy: OK09:24
pfFredd joined09:24
closures999 left09:24
fairuz joined09:25
fairuz left09:25
shadok left09:25
Nevik well, macos *is* kinda messed up09:25
Cathy: it's probably just a question of how git is installed though09:26
LionKing Cathy: Stupid question: Shouln´t it be man git-checkout09:26
gitinfo Cathy: the git-checkout manpage is available at http://jk.gs/git-checkout.html09:26
Cathy git is installed out of the box on OS X09:26
freestyl3r joined09:26
LionKing with the dash between git and checkout?09:26
Nevik Cathy: it's not09:26
it comes with developer tools, if anything09:26
and that is usually an old-ass version09:26
Cathy well Nevik it's installed on my MacBook Pro I got three days ago09:26
and i took no steps to install it09:26
Nevik it probably had dev tools preinstalled09:26
Cathy looks like git version 1.8.3.4 (Apple Git-47)09:27
Nevik who knows what apple does with these things09:27
ha, that's even halfway decent09:27
LionKing: the dash should make no difference if git is installed properly09:27
LionKing Nevik: I think it is quite a difference09:27
Nevik but some versions of man might have a limitation with the two-name lookup09:27
Cathy i think it's just a different behaviour of `man` on OS X09:27
knighthawk joined09:28
ericy joined09:28
LionKing Without the dash you give the man two arguments: git and checkout09:28
Nevik yeah. i dont know if the alias lookup happens in the shell or in man09:28
LionKing: well, it works on all linuxes :P09:28
gasbakid left09:28
Nevik LionKing: basically, linux man tries to look up the full list of arguments as a single command first, then falls back to multiple commands if it doesnt find anything09:29
behaviorally anyway. as i said, i dont know where that resolution happens09:29
LionKing Nevik: oh, thank you. I didn´t know that...09:29
Nevik i know that git subtree isnt in the default man list for git09:29
Cathy let's apply science to find out09:29
bkhan left09:29
Nevik oh, it is now09:30
that's recent09:30
Xethron left09:30
Cathy here's what i've discovered09:30
[cathyjf@cathy-vm ~]$ strace man git checkout09:31
gitinfo the git-checkout manpage is available at http://jk.gs/git-checkout.html09:31
Cathy execve("/usr/bin/man", ["man", "git", "checkout"], [/* 46 vars */]) = 009:31
bartzy joined09:31
gasbakid joined09:31
Cathy looks like the `man` command handles the resolution09:31
harish joined09:31
ruby|angry_hamst joined09:31
Nevik cool09:31
so macos man is dumber09:31
grahamsavage left09:33
eletuchy left09:33
lite__ joined09:33
Nevik man's manpage probably describes how it tries to resolve the arguments. but im too lazy to sift trough it :D09:33
eletuchy joined09:34
Cathy it's only 721 lines09:34
Nevik but my laziness is over 9000!09:35
Cathy i just read it and found nothing relevant09:35
heh09:36
ericy left09:36
Cathy man --version returns 1.6c on OS X09:36
harish left09:36
Cathy compared to 2.6.5 on my Fedora installation09:36
ericy joined09:36
lite_ left09:36
lite_ joined09:37
cads left09:37
MetalMatze joined09:37
Nevik that might do it :D09:38
micw joined09:38
karavanjo left09:38
karavanjo_ joined09:38
lite__ left09:40
zhost joined09:41
achadwick joined09:42
Sendoushi joined09:44
grahamsavage joined09:45
svector left09:45
boombatower left09:46
mihamina joined09:47
m0viefreak left09:47
sabgenton left09:51
fRAiLtY- joined09:52
Guest75350 joined09:52
GT4066 joined09:52
leakybuckit joined09:53
user258467 left09:54
hyperair left09:54
ericy left09:54
raonyguimaraes joined09:55
purpleidea left09:55
harish joined09:55
jkremser joined09:56
jkremser left09:56
jkremser joined09:56
ewnd9 left09:56
teran joined09:56
blahdodo joined09:56
purpleidea joined09:57
rfree left09:57
gua_ould left09:57
user258467 joined09:57
rfree joined09:57
l0cust left09:58
Norm_ joined09:58
weiyang left09:59
svector joined09:59
mlechner joined09:59
gua_ould joined10:00
alezost joined10:01
pfFredd left10:01
Skrypter left10:02
xobb joined10:03
tvw left10:04
oo_miguel joined10:04
alezost http://www.git-scm.com gives me "Sorry, no Host found". Does anyone know what the problem is?10:04
bremner alezost: probably local to your network10:06
lacrosse_ joined10:06
eijk_ joined10:06
soee left10:07
JustinMac left10:07
soee joined10:08
xpe joined10:08
sabgenton joined10:08
rendar joined10:10
eijk left10:10
jon_r left10:11
psoo left10:11
psoo joined10:11
psoo left10:11
psoo joined10:12
ericy joined10:12
eijk joined10:13
alezost bremner: no idea what i can do with that, but thanks for the reply10:13
closures999 joined10:14
bremner well, I was just being http://downforeveryoneorjustme.com/git-scm.com10:15
beautifulmind joined10:15
angelsl joined10:16
eijk_ left10:17
harish left10:18
JustinMac joined10:18
Nevik no, it's a DNS problem10:18
ive had it since yesterday10:18
some NSs return an IP that results in the above message10:19
alezost: it's something to do with git-scm's hosting, so unless someone knows who does technical adminning on it, we wont be able to ring any bells :D10:19
Sendoushi left10:21
JustinMac left10:21
mk_qi left10:23
eletuchy_ joined10:23
Guest75350 left10:24
eletuchy left10:24
Nevik alezost: since it doesnt seem to be an isolated problem, i have opened an issue: https://github.com/github/gitscm-next/issues/32610:24
though i dont know if any techies/webmasters will notice that10:24
singham joined10:25
singham lo all10:25
what does "git --al" do?10:25
i forgot the last 'L'10:25
yacks left10:26
Nevik singham: nothing10:26
the command "git" without any subcommand doesnt do anything10:26
singham Nevik: well it's added the files to staging using the 'a' ... i'm not sure about the l10:26
Nevik if anything, it should show you a usage message10:26
singham: you possibly mean "git add --all" or something10:26
singham Nevik: yes exactly...but I typed the above and it added files to staging. I was wondering if the 'L' paremter did naynthing10:27
PeterBooker joined10:27
Nevik $ git --al10:27
Unknown option: --al10:27
^10:27
--all does the same10:27
singham whoops10:27
sorry i meant10:27
grahamsavage left10:27
Nevik so please clarify what command exactly you entered10:27
singham $ git add --al10:27
Sendoushi joined10:28
Nevik my guess is that git augments that argument to --all10:28
since it's probably unambiguous10:28
singham right, thanks for your help10:28
Nevik singham: see man git add for details on what --all does10:28
gitinfo singham: the git-add manpage is available at http://jk.gs/git-add.html10:28
grahamsavage joined10:28
singham cheers!10:28
yacks joined10:29
oo_miguel Can I somehow see which merges had conflicts and who resolved them?10:29
Nevik no10:29
ericy left10:29
leandrosansilva joined10:30
Nevik there would be a trial-and-error method of finding out which merges must have produced conflicts; but there's no telling what happened between the conflict and the resolution10:30
it's usually safe to assume that whoever created the merge commit did resolve the conflicts though10:30
unless you have extreme pair/group programming in your project10:31
oo_miguel I just wonder, because some of my code is gone, and I suppose, that a collegue removed it during a merge10:31
just overwriting my version with his one10:32
Nevik oo_miguel: the diff on the merge commit will show what changed10:32
YoungFrog perhaps "git log -S..." will help you find when it has disappeard, too10:32
Nevik true10:32
kriks joined10:32
oo_miguel what does git show exaclty tell me?10:32
I have a git show on a commmit right AFTER the merge, where all my lines get removed10:33
:P10:33
luc_ left10:33
oo_miguel does this mean its his fault ?10:33
Nevik that means that commit removed those lines, yes10:34
it's usually the point of commit messages to give reasons for why things change10:34
if that is not the case, time to go ask your colleague :P10:34
StarFire_ joined10:34
oo_miguel yes, he did it not by purpose, I just wonder where the lines get removed10:35
i thought it might be git, by doing some automerging10:35
Nevik in the commit whose diff shows them as removed :P10:35
ruby|angry_hamst left10:36
LionKing left10:38
alezost Nevik: thank you very much, now i see10:39
Nevik alezost: sure, no problem :)10:39
ruby|angry_hamst joined10:39
YoungFrog oo_miguel: git won't remove lines in a merge on its own for no reason : if it removes them, it means that they were present before in both branches, and removed in one of the commit.10:39
oo_miguel yes, thats makes sense10:40
leandrosansilva left10:40
oo_miguel I will examine the log carefullly10:40
leandrosansilva joined10:40
MetalMatze left10:42
Nevik oo_miguel: if `git show` on the commit *after* the merge shows them as removed, that's where they were removed10:44
penguin42 joined10:44
h0bbit_ left10:44
Nevik not much reason to examine the log further, really10:44
papegaaij joined10:46
ericy joined10:46
bitkiller joined10:49
raf joined10:51
nbrosnahan left10:52
arjun_ joined10:52
codiez joined10:52
akbar204 joined10:55
akbar204 Hi10:55
gitinfo akbar204: 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.10:55
eijk_ joined10:55
akbar204 anybody there?10:55
eijk left10:55
akbar204 what happends if i am on a different branch and i do a git push origin development??10:56
grahamsavage_ joined10:57
grahamsavage left10:59
akbar204 left11:00
oo_miguel Nevik: ok so I know what happened11:00
micw hi11:00
Nevik apparently akbar really didnt wanna know the answer to his question11:01
oo_miguel my collegue opened his file, pulled , git merged without conflicts, saved his file after doing some minor changes, overwriting my changes, pushed11:01
what can I do about it now?11:01
Nevik oo_miguel: first of all, you go to your boss and make him make your colleague get an editor which notices file changes on the filesystem11:01
alternatively, whack your colleague with a sledgehammer and get a new colleage11:01
oo_miguel hehehehe11:01
rouf left11:02
oo_miguel I did this already11:02
;)11:02
Nevik oo_miguel: then you check out the old version of the file or copy those changes from the older version, depending on if new changes have been made11:02
grawity so use `git checkout` to get an older version of the file – specifically, the one from the merge11:02
Nevik grawity: lemme finish, man :<11:02
oo_miguel :)11:02
grahamsavage_ left11:02
micw allows "subtree" do edit/commit/push code in sub repositories or are those read only?11:02
Nevik irc needs "is currently typing" notifications >.>11:02
rouf joined11:03
joaoh82 left11:03
oo_miguel ok so I fix it manually in one word..11:03
joaoh82 joined11:03
Nevik oo_miguel: if there have been new changes, you need to yes. if there havent been, a checkout and commit fixes it11:03
there's nothing more automatic than that11:03
grahamsavage_ joined11:05
oo_miguel Nevik: ok makes sense11:05
thx11:05
ericy left11:10
user125 joined11:11
adambrenecki joined11:11
jarr0dsz left11:12
user125 hello. am i supposed to do a git-rm -rf dirname before i do a filter-branch removal?11:12
timthelion joined11:12
echo-area left11:12
z8z joined11:16
z8z left11:16
z8z joined11:16
mlechner left11:17
timthelion left11:17
mlechner joined11:18
closures999 left11:19
devanblue joined11:22
mlechner left11:24
dhruvasagar left11:24
dhruvasagar joined11:25
ericy joined11:26
donmichelangelo left11:27
donmichelangelo joined11:27
LuxuryMode joined11:28
psyl0n joined11:29
Watabou left11:29
epta left11:29
asQuirreL joined11:30
purpleidea left11:31
the_cybersphinx joined11:31
LuxuryMode left11:32
purpleidea joined11:32
purpleidea left11:32
purpleidea joined11:32
joaoh82 left11:33
mitz left11:33
joaoh82 joined11:33
mitz joined11:34
LuxuryMode joined11:34
harish joined11:35
armin_w left11:35
SuRfDeMoN joined11:36
joaoh82 left11:38
joaoh82 joined11:38
joaoh82 left11:38
pen left11:39
pen joined11:40
ericy left11:41
m0ltar joined11:42
ewnd9 joined11:42
asQuirreL left11:42
eijk_ left11:43
purpleideapurpleidea-afk11:43
purpleidea-afkpurpleidea11:43
arjun_ left11:43
gwb3 joined11:46
konadr joined11:46
z8z left11:48
gua_ould left11:48
fairuz joined11:48
user125 is there a way to change repacking tmp folder from .git/objects/pack/ ?11:50
mlechner joined11:50
slassh left11:51
lb1a user125, git repack ?11:51
user125 lb1a: my git gc --prune=now is failing because i dont have enough space for the temp pack files11:53
lb1a git cannot help you with your available hdd space Oo11:54
user125 if i could change .git/object/pack/ to /tmp/11:54
dsdeiz left11:54
setmeaway left11:55
vals_ joined11:56
Mattias left11:57
tango_ left11:57
ericy joined11:58
paulweb515 left11:58
joaoh82 joined11:58
ayaka I want to cherry-pick some commites but I got http://paste.debian.net/68220/12:00
Mattias joined12:00
joaoh82_ joined12:01
nafg___ left12:02
Guest96996 left12:03
joaoh82 left12:04
lb1a ayaka, and your question is12:07
mdiers__ left12:08
ayaka lb1a, how to fix it12:09
_ikke_ ayaka: Your commit doesn't include new changes12:09
ayaka: git is telling you that12:09
SicoWork left12:09
lb1a ayaka, if your read your paste, you will have every information to continure what you were doing12:09
SicoWork joined12:09
codiez left12:10
jarr0dsz joined12:10
codiez joined12:10
jarr0dsz left12:11
ericy left12:11
jarr0dsz joined12:11
Plouj joined12:12
ayaka _ikke_, lb1a but it is a new branch, and the commit I refering in cherry-pick is not in the log of this branch(it is in the other branch)12:12
xobb left12:12
codiez left12:12
codiez joined12:12
VictorCL joined12:13
armin_w joined12:13
vtunka joined12:13
knighthawk left12:14
user125 uhh... git is so complicated.12:15
hs366 joined12:15
closures999 joined12:16
kcj left12:16
gua_ould joined12:16
user125 i removed a huge blob of data from the repo using filter-branch, yet the .git folder is still too large in comparison with the working tree12:16
timthelion joined12:17
Celelaptop What is the best way to contribute to an open source software using git? Given that most of the software requires patches to be sent via a mailing list and to be applyable on origin/master directly.12:17
lb1a Celelaptop, !best12:17
gitinfo Celelaptop: [!bestway] You want to know the best way to do X? If you can give us a proper definition of "best", we'll give you a proper way to do X ;)12:17
teran left12:17
Celelaptop Should I patch my local master? Create a branch for all my modifications? Create one branch per patch serie? Should these branches be based on origin/master or on master? Should I update these branches with a pull a or rebase?12:17
teran joined12:18
Celelaptop lb1a: so let's rephrase the question as: how most people do?12:18
oo_miguel left12:18
lb1a Celelaptop, i'd say it always depends on the project12:19
mihamina left12:20
dhruvasagar left12:20
lb1a Most projects document a proper way to contribute12:20
abelsiqueira joined12:21
Celelaptop What I've seen for syslinux and qemu, they only say "submit patch on the mailing list, and follow the guidelines of linux".12:21
kcj joined12:21
lb1a hm hmm git-scm.com seems to be down "Sorry, no Host found"12:21
Celelaptop, so follow the contribution guidelines of the linux kernel12:21
Celelaptop It doesn't talk much about git.12:22
johnkevinmbasco joined12:22
Celelaptop And I don't think they care about the way contributors use git on their own computers.12:22
timthelion left12:22
mdiers__ joined12:22
xobb joined12:23
rainbyte joined12:23
lb1a Celelaptop, you asked how to contribute to a project, not how to setup your workflow at home12:23
Celelaptop Yes but some of the workflows do not match very well the projects requirement that all patches should apply on origin/master, for instance12:24
lb1a why not?12:25
graphitemaster left12:25
graphitemaster joined12:25
joaoh82_ left12:25
Celelaptop Doing several kind of midifications on the same branch (local master or all in one branch) is not very good because the patch you will produce may not apply on origin/master.12:25
lb1a why do you care about contributing when it comes to your workflow while development. you can always craft patches after all or rebase history according to the guidelines...12:25
Luke-Jr joined12:26
closures999 left12:26
joaoh82 joined12:26
Celelaptop Well, rewriting history is not always a fun thing to do.12:27
ericy joined12:28
Celelaptop Is there a difference between basing a branch on origin/master or on master?12:28
TheFuzzball left12:28
mdiers__ left12:29
canton7 Celelaptop, depends if origin/master points to the same commit as master ;)12:30
hs366 left12:32
arjun_ joined12:32
TheFuzzball joined12:32
hs366 joined12:33
ciampix joined12:33
echo-area joined12:33
intellix left12:33
hs366 left12:33
hs366 joined12:34
user125 left12:35
thierryp left12:35
lun___ left12:36
YoungFrog So the question is : what is the difference ? origin/master is a branch that you shouldn't ever checkout, it simply follows master on origin. your own master is whatever you do with it, but usually it's set up so that it is somehow related to origin/master (either an exact copy, or you merge regularly from origin/master to master)12:37
by "follows", I mean that git fetch will make it point to the same commits as "master" on "origin".12:38
carbon2 joined12:38
canton7 another point to make it that origin/master is updated on every 'git fetch', but your local master is normally only updated by you when you check it out, presumably with the intention of working on it. therefore origin/master is always going to better reflect the state of the origin repo12:38
raf left12:39
hs366 left12:40
hs366 joined12:40
grahamsavage_ left12:40
Celelaptop ok thx12:40
mdiers__ joined12:41
Gavrisimo joined12:41
devanblue left12:44
joaoh82 left12:46
joaoh82 joined12:47
btiernay Is it possible to push a tag to a repo for which you have not first cloned?12:47
ericy left12:47
_ikke_ btiernay: yes12:47
asQuirreL joined12:47
btiernay _ikke_, Interesting, please do expound sir!12:48
_ikke_ btiernay: Add it as a remote, and then git push <remote> <tag>12:48
It will push every commit reachable by that tag though12:48
Xethron joined12:48
btiernay _ikke_, Is it possible even if you don't have the repo locally, but have git installed?12:48
Celelaptop And if I have a branch with unmegered commits while origin/master is updated. Should I merge or rebase it?12:49
btiernay I'm trying to tag a repo from CI12:49
_ikke_ btiernay: No12:49
btiernay But not the main repo12:49
Aw shucks12:49
_ikke_ btiernay: You have to have the history for that tag you want to push12:49
btiernay I can't just say "Hey remote, tag HEAD with this tag"?12:50
_ikke_ nope12:51
The git protocol doesn't allow that12:51
maleknet left12:51
btiernay Okay, fair enough!12:51
Thanks :)12:52
_ikke_ It only allows you to say: "Hey remote, I have here some refs with this according history"12:52
StarFire_ How can I completely remove a subdirectory from a converted SVN repo, if the instructions in ¨Prog Git¨, chapter 9.7, ¨Removing objects¨ does not work12:52
?12:52
btiernay One last thing, is it possible to force delete a remote tag? By this I mean, if it doesn't exist, don't complain12:52
ni_ joined12:52
asQuirreL left12:52
mdiers left12:52
_ikke_ StarFire_: You need to use filter-branch fro that12:52
canton7 StarFire_, define "does not work"12:52
btiernay _ikke_, Thanks for the explanation12:53
StarFire_ _ikke_: It is described with filter-branch in said chapter12:53
canton7: count-objects shows be before and after filter-branch the same ¨size-pack¨12:53
_ikke_ StarFire_: Then explain what command you executed, and what output you get12:53
mdiers joined12:54
mdiers__ left12:54
StarFire_ I did: git rm -r _dev/defaults/doc12:55
git commit -m ¨Removed huge documentation¨12:55
canton7 cna we have a pastebin, please, with a terminal log of you executing the command and the resulting output?12:55
btiernay Basically I want do is delete a tag on the remote if it exists, otherwise do nothing12:55
canton7 "insignificant" things tend to get lost otherwise12:55
SicoWork left12:55
tma996 joined12:56
StarFire_ git filter-branch --index-filter ´git rm -r --cached --ignore-unmatch _dev/defaults/doc´ HEAD12:56
teran_ joined12:56
StarFire_ rm -Rf .git/refs/original12:56
rm -Rf .git/logs12:56
git gc12:56
canton7 StarFire_, can we have a pastebin, please, with a terminal log of you executing the command and the resulting output?12:56
StarFire_ canton7: It is quite a repo (21300 committs), I don´t have all the output...12:57
canton7 iirc a filter-branch output isn't more than a few lines? my memory is that it continuously rewrites the same line to show progress. I could be wrong though12:58
anyway, output of 'git branch'?12:58
StarFire_ canton7: Yes, it has output if he has something to do12:58
dsdeiz joined12:58
canton7 fair enough12:58
StarFire_ canton7: In my case it startes about commit 13000 (til the end)12:59
kbart joined12:59
canton7 all looking very promising12:59
output of 'git branch'?12:59
teran left12:59
StarFire_ * master12:59
canton7 good, was worried you were on a detached HEAD13:00
look at some point in history - does that dir still exist?13:00
_toordog joined13:00
StarFire_ I am quite new to git. How do I look that up in some point in the history?13:01
_ikke_ git log shows you the history13:01
RichiH Dougie2187: aye... and i am incredibly annoyed by the fact that13:01
_ikke_ gitk would also be easy for that13:01
canton7 I'm talking about looking at a commit in history13:01
not a diff13:01
RichiH a) the history is in the wrong order13:01
canton7 StarFire_, easy way: git checkout -b tempbranch HEAD^^^^^13:02
RichiH b) the merge commit ist not marked as such13:02
canton7 (you could detach your HEAD, but I'm not going to suggest that to someone who's new)13:02
RichiH c) 12 hours is not "dragging on"13:02
pen left13:02
pen joined13:03
StarFire_ canton7: It does not exist in HEAD^^^^^^13:03
ericy joined13:04
canton7 StarFire_, then it looks like your method of determining whether filter-branch worked is flawed, rather than the filter-branch itself?13:04
_ikke_ git log --all -- path/to/dir should show you if there are commits left that have that dir13:04
canton7 ^^ also worth doing13:04
TheFuzzball left13:05
mdiers__ joined13:06
davividal joined13:06
thierryp joined13:06
StarFire_ _ikke_: There are quite a lot of commits...13:06
RichiH !lolo13:06
!lol13:06
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all13:06
Kartagis if I checkout a branch (say 8.x-2.x) then git push origin HEAD, will it be pushed to that branch?13:07
StarFire_ _ikke_: Actually it looks like the committs I wanted to remove13:07
k4rtik joined13:07
_ikke_ Kartagis: no13:08
daito left13:08
_ikke_ Kartagis: You have to specify the name of the branch13:08
Kartagis: git push origin HEAD:8.x-2.x13:08
slassh joined13:08
TheFuzzball joined13:08
_ikke_ Kartagis: (it also depends a lot on the setting of push.default, and if an upstream is defined for that branch)13:08
TheFuzzball left13:09
vals_tango_13:09
TheFuzzball joined13:09
canton7 StarFire_, do you have any branches other than master?13:09
TheFuzzball left13:10
TheFuzzball joined13:10
TheFuzzball left13:10
StarFire_ canton7: Yes, 34 ¨remotes¨ (they are not real remotes, they are from converting) and 13 ¨remote tags¨ (also from conversion)13:11
TheFuzzball joined13:11
canton7 StarFire_, so the log --all will be showing commits belonging to those remotes13:11
if you don't have any local branches other than master, 'git log -- path/to/dir'13:11
mdiers__ left13:11
davividal left13:12
StarFire_ canton7: git log -- path/to/dir returned nothing...13:13
bgy joined13:13
bgy hi13:13
canton7 StarFire_, good, then your local master branch has definitely been rewritten correctly13:13
StarFire_ hmm13:13
bgy Is it possible to do something like /foo/{sub,other,directory} in .gitignore?13:14
StarFire_ Should I checkout every branch and do the same procedure as in master?13:14
canton7 StarFire_, I thought you only had one local branch/13:14
bgy, from man gitignore, "Otherwise, Git treats the pattern as a shell glob suitable for consumption by fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match a / in the pathname. For example, "Documentation/*.html" matches "Documentation/git.html" but not "Documentation/ppc/ppc.html" or "tools/perf/Documentation/perf.html""13:15
gitinfo bgy: the gitignore manpage is available at http://jk.gs/gitignore.html13:15
intellix joined13:15
StarFire_ canton7: I don´t know actually. The other branches start all with remote/...13:15
canton7: but I converted that repo from SVN13:15
canton7 StarFire_, so they're local read-only copies of branches which exist in those remote repos?13:15
asQuirreL joined13:15
StarFire_ canton7: So they are kind of local too...13:15
canton7 StarFire_, what are the *exact* remote branch names?13:15
StarFire_ git branch -a shows me:13:16
* master13:16
remotes/BR_R113:16
remotes/R113:16
canton7 ok, git-svn converted repo. all good13:16
hyperair joined13:16
StarFire_ remotes/R213:16
etc.13:16
canton7 so there are a ton of remote branches, but you only created one local branch, master13:16
so create a new local branch for each of those remote branches13:16
then do the filter-branch again, but use '-- --all' instead of 'HEAD'13:16
j0ran left13:16
bgy canton7, yeah I read it, but I doesn't seem to handle such pattern, that's why I asked here13:16
StarFire_ canton7: OK, I will do this. It´ll take a while13:17
canton7: Thank you!13:17
canton7 StarFire_, wait a sec13:17
StarFire_ yes?13:17
koda joined13:18
canton7 you can script that branch-creation process13:18
StarFire_ Like described in Pro Git?13:18
canton7 not sure. been a while since I read that book13:18
Celelaptop When I create a branch, with git branch newbranch startingbranch, will that make subsequent git pull to merge from startingbranch?13:19
davividal joined13:19
StarFire_ I alread have. I also have removed the branches that I no longer need13:19
canton7 is confused13:19
canton7 never mind, go and create all of your local branches manually13:19
subhojit777 left13:19
WABL58H joined13:19
canton7 Celelaptop, depends whether startingbranch is a remote-tracking branch iirc13:20
StarFire_ canton7: I did that on another copy of that repo13:20
thierryp left13:20
canton7 ok cool13:20
StarFire_ canton7: sorry to confuse you...13:20
Celelaptop what is a remote-tracking branch?13:20
thierryp joined13:20
canton7 Celelaptop, one that starts with e.g. 'origin/'. They're local read-only records of the states of remote branches13:20
Celelaptop ok13:21
So it cannot be a local branch?13:21
canton7 (to clarify, if the starting point is a remote-tracking branch, then tracking info is set up, and 'git pull' will just work (tm))13:21
Kayra joined13:21
canton7 (if the starting point is a local branch, everything's the same exept that tracking info isn't set up)13:22
SicoWork joined13:22
buzzybron joined13:22
mdiers__ joined13:23
buzzybron left13:24
Celelaptop Hum... But git pull will fetch and merge from the branch set with git branch --track, doesn't it?13:25
So pull wouldn't work if the tracking origin isn't set.13:25
paulweb515 joined13:26
guampa joined13:28
lun__ joined13:28
mdiers__ left13:29
leandrosansilva left13:29
leandrosansilva_ joined13:30
grahamsavage joined13:30
grahamsavage left13:30
grahamsavage joined13:30
paulweb515 left13:32
rjhunter left13:32
snag joined13:33
VictorCL left13:34
VictorCL joined13:34
micw recently i have seen a nice flow diagram how to do things with git (in the style "if you hate someone - rebase interactive on origin" ;-) ) but i cannot find it anymore. does anyone know this?13:34
xobb left13:35
micw ah, remembered the name. it's "Git pretty". found ;)13:36
infynyxx joined13:36
grahamsavage left13:36
paulweb515 joined13:37
grahamsavage joined13:37
wlemuel joined13:37
edude03 left13:37
Nevik i love how the hate is so nonchalant in that13:37
edude03 joined13:37
Nevik do you hate them? rebase away!13:37
TheFuzzball left13:39
micw ;)13:39
ruby|angry_hamst left13:40
ruby|angry_hamst joined13:40
wlemuel left13:40
mdiers__ joined13:41
TheFuzzball joined13:42
xobb joined13:42
canton7 Celelaptop, yup13:44
but the logic is, if you created the branch from another local branch, there isn't yet a remote branch for it to track13:44
if you created the branch from a remote branch, there *is* a remote branch to track, so tracking is set up13:44
ericy left13:45
Celelaptop Ok.13:46
wlemuel joined13:46
Celelaptop So the usage is: if I track a remote branch I pull, if I derive a local branch into another local branch, i just merge or rebase.13:46
infynyxx left13:47
TheFuzzball left13:47
canton7 Celelaptop, you can set up tracking when you first push the branch13:48
with git push -u13:49
or later, with git branch --set-upstream-to13:49
grahamsavage left13:50
grahamsavage joined13:51
grahamsavage left13:51
Dougie2187 left13:52
grahamsavage joined13:52
Dougie2187 joined13:52
dhruvasagar joined13:54
rchavik left13:56
rethus joined13:57
RogerWS left13:57
liamkeil1 joined13:58
hs366 left13:59
stany_ joined14:00
__Hassen__ joined14:00
St_Marx joined14:00
__Hassen__ why isn't "man grep" working in git bash? isn't it supposed to be working like the linux bash?14:01
i use win714:01
aartist joined14:02
mdiers__ left14:02
infynyxx joined14:02
codiez left14:02
ericy joined14:03
canton7 __Hassen__, with some caveats. one is a lack of man pages14:03
renatow_ left14:03
kriks left14:03
lun__ left14:05
__Hassen__ canton7, ah so doesn't it contain the full list of man pages like linux OS's do?14:05
telmich joined14:05
telmich good day14:05
stany_ left14:05
canton7 __Hassen__, correct. google is your friend here - plenty of man pages online14:05
dsdeiz left14:05
telmich how can I create a new branch that has no ancestors? i.e. like a fresh branch in an existing project?14:05
renatow joined14:05
codiez joined14:05
canton7 telmich, man git checkout --orphan14:05
gitinfo telmich: the git-checkout manpage is available at http://jk.gs/git-checkout.html14:05
stany joined14:05
__Hassen__ canton7, understood.14:05
sonOfRa left14:06
sonOfRa joined14:06
stany left14:06
__Hassen__Hassen14:06
lun__ joined14:07
saorge left14:08
flaguy48 left14:08
telmich canton7: thanks14:08
snag left14:08
Raging_Hog left14:09
sohail joined14:09
rethus left14:09
saorge joined14:09
arjun_ left14:10
gasbakid left14:13
mdiers__ joined14:13
soon joined14:13
fairuz left14:13
johnkevinmbasco left14:14
Cromulent joined14:14
lun__ left14:15
sebrock joined14:16
johnkevinmbasco joined14:16
fairuz joined14:17
Kayra left14:17
soon Anyone have experience using git to synchronize a local folder and a webdav folder? (as an alternative to e.g. Dropobx)14:17
Kartagis how do I allow creation of repos on-the-fly?14:18
johnkevi_ joined14:18
bremner Kartagis: context?14:18
Kartagis bremner: like a repo is not created on the server beforehand, but it is created when the user pushes14:19
adac left14:19
infynyxx left14:19
bremner Kartagis: gitolite can do that with "wildrepos"14:20
_ikke_ Kartagis: !gitolite has support for 'wild' repo's14:20
gitinfo Kartagis: Gitolite is a tool to host git repos on a server. It features fine-grained access control, custom hooks, and can be installed without root. Download: https://github.com/sitaramc/gitolite Docs: http://gitolite.com/gitolite/14:20
mdiers__ left14:20
jonatasnona joined14:20
Kartagis cool14:20
thanks14:20
j0ran joined14:20
johnkevinmbasco left14:21
vurma joined14:22
ericy left14:24
aberrant joined14:25
soon everybody liked Kartagis' question and nobody liked mine .. <sulk> :-)14:26
Kartagis aww14:26
what was yours?14:26
_ikke_ soon: Because you mentioned dropbox :P14:26
soon: Git is not really meant for synchronization14:26
It's a lot of overhead14:27
soon: even rsync in a cron is a better sollution imo14:27
soon I've considered rsync, but it's not quite up to the job14:27
bremner soon: git annex assistant is designed as a dropbox replacement14:27
soon ahh ... I can google that14:28
_ikke_ soon: Why isn't rsync good enough?14:28
bluesm joined14:28
bremner of course there are several others that don't involve git.14:28
Ingmar joined14:28
Ingmar left14:28
Ingmar joined14:28
soon _ikke_ rsync will not handle deletions very well14:28
Ingmar left14:28
_ikke_ soon: Can you explain?14:29
soon I could do a bi-lateral rsync, but if I decided to delete a file, it would be re-sync'ed14:29
beautifulmind left14:29
soon thus I would have to manually delete the file from every copy/client14:29
Ingmar joined14:30
Ingmar left14:30
Ingmar joined14:30
_ikke_ Okay, you want two way synchronization14:30
soon yes14:30
arjun_ joined14:30
moritz unison does two-way syncing14:30
pandeiro joined14:30
lindenle joined14:30
soon I found unison ... looks promising, but apparently not really developed anymore, hence I thought I'd ask if Git was a better solution14:31
but as stated ... perhaps overkill14:31
I'll look at unison and git annex assis.14:31
adac joined14:31
soon If neither fits my problem-pants, I'll come back :-)14:31
mdiers__ joined14:32
osa1 joined14:32
osa1 git book webpage is down?14:32
_ikke_ osa1: progit?14:32
osa1 http://www.git-scm.com/book14:32
this one14:32
lorenx joined14:32
_ikke_ osa1: aparently, yes14:33
osa1 is this correct URL?14:33
ewnd9 left14:33
_ikke_ yes, it is14:33
JonasF joined14:33
wlemuel left14:34
_ikke_ Even the website of the maintainer of that website is down aparently14:34
JonasF left14:34
thierryp left14:34
mastro left14:36
moritz how meta14:36
edwardly joined14:36
_ikke_ I'm so meta, even this acronym14:36
moritz I never met a meta I didn't like14:37
simesy left14:37
simesy joined14:38
teran joined14:39
jonatasnona left14:39
soon left14:39
mlechner left14:40
MapleyMaplez14:40
MaplezMapley14:40
lorenx can i have a git repository ignoring inner/path/* and a second nested git repository in inner/path?14:40
abelsiqueira left14:40
_ikke_ lorenx: sure14:41
takamichi left14:41
aChatir joined14:41
thierryp joined14:41
ericy joined14:41
akitada joined14:41
dccc left14:41
lorenx _ikke_: m, ok... i tried but i'm having problems when i switch from a post-nested branch and a pre-nested one14:42
joaoh82 left14:42
k4rtik left14:42
mgedmin joined14:42
luxgeek joined14:42
SeySayux left14:42
teran_ left14:42
joaoh82 joined14:42
mgedmin how hard would it be to write a hook to stop pushes if I've got commits with 'WIP' at the start of the commit message?14:42
takamichi joined14:42
hyperair left14:43
simesy left14:43
lorenx let me explain... at some point of my history i decided to have a second nested repository so i moved away all the inner/path/* (to delete it from the main repository), i ignore inner/path/*, i create a second nested repository in inner/path/ and copy back here my previous files14:43
kcj left14:43
jeek joined14:43
takamich_ joined14:44
luxgeek left14:44
SeySayux joined14:44
nilg joined14:44
_ikke_ lorenx: yes, that's a problem indeed14:44
tvw joined14:44
lorenx but now, when i checkout a previous branch, the main git says i have to delete those files14:44
what am i missing?14:44
_ikke_ lorenx: You aren't missing anything, it's just a situation that is difficult to handle14:44
mr_red joined14:45
lorenx but it is a normal scenario with nested repos14:45
i guess14:45
_ikke_ lorenx: Normally submodules are used14:45
lorenx excuse me?14:45
ntio left14:45
_ikke_ !submodules14:45
gitinfo [!submodule] git-submodule is ideal to add subsidiary git repositories to a git superproject when you do not control the subprojects or more specifically wish to fix the subproject at a specific revision even as the subproject changes upstream. See http://book.git-scm.com/5_submodules.html14:45
lun__ joined14:46
_ikke_ lorenx: The problem is that git sees that there are files that that are not being tracked, and git refused to delete / overwrite files that aren't tracked, so it complains14:46
moritz you can delete them with git clean14:46
lorenx _ikke_: yeah but i thought that telling it to ignore that path would be enough14:47
takamichi left14:47
ewnd9 joined14:47
moritz you were wrong :-)14:47
angelsl left14:47
_ikke_ lorenx: Would you think it's a good idea to delete / overwrite ignored files without question?14:47
lorenx moritz: git clean doesn't sound a great solution14:47
xyxy joined14:48
lorenx _ikke_: cause i thouhgt that if they are ignored git has to ignore them :P14:48
_ikke_ lorenx: .gitignore only tells git to not show it as untracked in git status, and to warn you when you try to add it to git14:48
przemkovv joined14:48
el3ctron left14:48
lorenx _ikke_: anyway... i'll read about git submodule14:49
King_Hual joined14:49
edwardly left14:49
_ikke_ (submodules have explicit support for this, where git places the .git dir in the parent repo, so the entire dir can be removed, but only when there aren't any uncomitted changes in the submodule)14:49
Kayra joined14:50
soee left14:51
closures999 joined14:51
edwardly joined14:51
jonatasnona joined14:52
draknir joined14:53
dccc joined14:53
gitinfo set mode: +v14:54
draknir hello :) does anyone else have trouble accessing git-scm.com ?14:54
Kartagis all of us14:55
de-Vri-es joined14:55
stodan left14:55
draknir ok, good to know14:55
codiez left14:55
draknir is there anywhere else I can download git for windows?14:56
Gavrisimo left14:56
codiez joined14:56
Gavrisimo joined14:57
Octalot joined14:57
Gavrisim_ joined14:58
ericy left14:58
arjun_ left14:59
donmichelangelo left15:00
eletuchy_ left15:00
matanya left15:00
eletuchy joined15:00
codiez left15:00
de-Vri-es left15:01
donmichelangelo joined15:01
dhruvasagar left15:01
Gavrisimo left15:02
leandrosansilva_ left15:02
Gavrisim_ left15:02
phile joined15:02
lorenx _ikke_: i removed the second git repository (inner/path/.git and inner/path/.gitignore) and i removed the ignore path in the main git but now i cannot add my inner/path/* files back, is it expected?15:03
stany joined15:04
bamj0rb joined15:04
gitinfo set mode: +v15:04
eletuchy left15:05
sebhoss joined15:05
_ikke_ lorenx: What do you mean with that you cannot add the files back?15:05
sebhoss left15:05
lorenx that if i got git status in the main git, it doesn't tell me it find the inner/path/* files15:05
everything is clean for it15:05
hholtmann left15:05
lb1a hm where to determine what's the latest git version? topic says 1.8.4.4, website says 1.8.4.315:06
lorenx even if i edit a inner/path/* file15:06
_ikke_ lb1a: does git ls-tree HEAD -- inner/path return anything?15:06
hholtmann joined15:06
lorenx it seems it is still ignorring that path15:06
_toordog left15:06
moritz lb1a: look at the newest tag in the git git repo?15:06
_ikke_ lb1a: git mailing list15:06
lorenx: and git-scm is often behind15:07
lb1a hmkay15:07
ewnd9 left15:07
lorenx it returns a line15:07
zhost left15:07
lb1a git-scm seems a bit unstable today...15:07
anyway thanks15:07
_ikke_ lb1a: it is15:07
1.8.4.4 has been released15:07
PaulCapestany joined15:07
takamich_ left15:07
lorenx _ikke_: it returns a commit line but if i do git show it says "fatal: bad object"15:08
simesy joined15:08
kpreid left15:09
_ikke_ Can you paste that line here?15:09
stany left15:09
lorenx _ikke_: i see know you were talking with lbla15:09
AaronMT joined15:09
lorenx anyway: 160000 commit 51a8c8e82dad63b14a205a7f9d33dc5b498c0a61 inner/path15:10
AaronMT left15:10
_ikke_ lorenx: That means git already sees it as a submodule15:10
lorenx then "git show 51a8c8e82dad63b14a205a7f9d33dc5b498c0a61" returns "fatal: bad object 51a8c8e82dad63b14a205a7f9d33dc5b498c0a61"15:10
AaronMT joined15:10
_ikke_ git rm --cached inner/path and comitting that should solve it15:10
lorenx i haven't created any submodule yet15:10
takamichi joined15:11
lorenx _ikke_: git rm? but "git status" is empty15:11
jonatasnona left15:11
kbart left15:11
_ikke_ lorenx: yes, because git doesn't look at the files in a submodule15:11
kukks joined15:11
kukks left15:11
kukks joined15:11
h_kon left15:11
_ikke_ "160000 commit" is a submodule15:11
jonatasnona joined15:11
_ikke_ 51a8c8e82dad63b14a205a7f9d33dc5b498c0a61 is the commit that was checked out in the sub repository15:12
pfFredd joined15:12
h_kon joined15:12
TheBrainWork joined15:12
lorenx _ikke_: it seems it worked15:12
arjun_ joined15:13
lorenx now git tells me "deleted: inner/path" and "untracked: inner/path/" at the same time15:13
sounds weird :P15:13
liamkeil1 left15:14
cagedwisdom left15:14
ohmy joined15:14
ohmy Hello15:14
lorenx _ikke_: i haven't undertood clearly what happened but it worked, thanks a lot15:15
tvw left15:15
Kayra left15:15
ohmy i have a remote got repository, cointaining my first commit. I would like to reset it as if it was a clean and empty repo, how can i make this please ?15:15
ericy joined15:15
_ikke_ try git push --delete origin master15:16
Not sure if it works though. Guess it will complain15:16
h_kon left15:17
simesy left15:17
ohmy _ikke_: errir unknown option delete :(15:17
kpreid joined15:17
_ikke_ ohmy: Older git version?15:17
ohmy: try git push origin :master15:17
moritz or just delete the remote repo, and create a new one15:17
I guess a normal branch deletion can't delete the default branch15:18
eijk_ joined15:18
ohmy moritz: thanks15:18
_ikke_ Poor repos, people deleting them for no reason :P15:18
ohmy _ikke_: thanks15:18
ttl117 joined15:18
jeffszusz joined15:18
_toordog joined15:19
Venix joined15:19
Venix just thought you'd like to see my response to www.godhatesfags.com http://pastebin.com/F9siPCbR15:19
ChanServ set mode: +o15:20
bremner set mode: +q15:20
ttl117 Anyone using gitflow? I did a new repo(git flow init), switched to master, did 2 commits of production(master) versions. What's the correct way now to continue working on develop branch? It's empty and there's not git flow command for this situation15:20
ChanServ set mode: -o15:21
moritz git checkout develop; git merge master # I suppose15:21
Sadeukko joined15:22
Venix left15:22
_ikke_ Amount of spam is increasing lately15:23
Xethron left15:23
Norm_ left15:24
papegaaij left15:25
lorenx _ikke_: do i need a repo url to init a submodule?15:26
lite_ left15:26
de-Vri-es joined15:26
Gavrisimo joined15:27
psoo left15:27
lorenx cause "git submodule init inner/path" does nothing15:28
draknir left15:28
Ploujmsg15:29
msgPlouj15:29
jarr0dsz left15:29
Gavrisim_ joined15:29
cads joined15:29
lorenx it seems i can "submodule add" a remote repo only15:31
eletuchy joined15:31
aberrant left15:31
Gavrisimo left15:32
ericy left15:32
Gavrisim_ left15:33
_ikke_ lorenx: Yes, a submodule is basically a reference to an external repository15:33
lorenx _ikke_: so it's not what i need15:33
_ikke_ Ok, what *do* you need?15:33
lorenx i just need 2 nested locel reposotory15:34
*local15:34
Dougie187 joined15:35
lorenx but ignoring the subpath and creating a normal nested repo doesn't work perfectly, as i already told you15:35
Rhonda joined15:35
lorenx you told me "it's just a situation that is difficult to handle"15:36
what about subtree?15:36
magnus^^p left15:36
lorenx or i should just move my second repo out of the main one and symlink them15:36
_ikke_ !subprojects15:37
gitinfo So, you want to add git repositories inside of other git repositories? Well, you have four main options. First is to just do it, add the repo to the outer project's .gitignore, and treat them entirely separately. Best if they are entirely separate. Otherwise your best options are "!submodule", "!gitslave", and "!subtree". Try those commands in this channel, or in a PM to avoid flooding.15:37
VictorCL left15:37
psavage joined15:38
psavage hey all a bit of a workflow question15:38
say I have a two features I'm developing in separate branches15:39
now all of a sudden one depends on the other15:39
but they still both need continued development15:39
shinnya joined15:39
rubatdub joined15:40
psavage how is that strategy best handled?15:40
bamj0rb Depends. You could continuously rebase one branch onto the other one. Or continuously merge one branch into the other.15:40
psavage right hte rebasing I get15:41
If I keep merging one branch into another15:41
bamj0rb That's probably what I would do, but you do have to be a bit more careful to not screw up conflict resolution.15:41
(The rebasing..)15:41
psavage yeh15:41
ohmy left15:41
xyxy left15:42
LuxuryMode left15:42
VictorCL joined15:42
psavage bamj0rb, what if I have 3-4 branches that all need combining and developing on?15:42
nested rebasing?15:42
bamj0rb First of all I'd say your features shouldn't all be intertwined like that. It probably means you're doing it wrong. :)15:42
petey joined15:43
psavage bamj0rb, yeh - I was thinking the same - not that I have that many branches ;)15:43
omarek joined15:43
bamj0rb It might be useful to rebase in order to take advantage of refactoring, but it might complicate source control and make a mess.15:43
omarek Hi, how do I remove the last commit ? I realized I made a mistake. The entire commit is pointless, a proper solution will take more time and there's nothing to really --amend...15:44
bamj0rb It might be better to just develop the other features against the old code, and once it's considered "good" either rebase or merge then.15:44
If it doesn't actually /require/ the other branch then you can get away developing with the dependency.15:44
_ikke_ omarek: git reset HEAD^15:44
That will undo the commit, but leave the changes there15:44
psavage bamj0rb, yeh that was my thinking15:44
ok15:44
ty15:44
micw left15:45
omarek _ikke_: Then what's the point ? I want to cancel the changes.15:45
_ikke_ omarek: Okay, then use reset --hard15:45
omarek The changes in commit.15:45
eletuchy left15:46
rethus joined15:46
_ikke_ omarek: (I though you just wanted to undo the commit, not remove the commit with its changes entirely)15:46
noyb joined15:46
eletuchy joined15:46
omarek _ikke_: is it possible to do to a remote bare repo ?15:46
Without logging in via ssh, that is.15:46
_ikke_ nope15:47
sebrock left15:47
bamj0rb omarek: It's not a good idea to edit published history. If you must, you can push --force. You should understand the implications of that first... It won't remove that commit for other people. They'll need to manually do it (or clone anew).15:48
kalleth i just did it on a published branch on github that other people have cloned15:48
they threw things at me across the office.15:48
keep that in mind ;(15:48
psavage kalleth, yeh not a good idea ;)15:48
simesy joined15:49
Nevik kalleth: at least you'll remember it :D15:49
omarek bamj0rb: Okay, so what's the best thing to do ? Commit --ammend -m "sorry about that" ?15:49
kalleth i'd do it again!15:49
omarek and push it ?15:49
Nevik it's like locking yourself out of your apartment in your underwear15:49
it is burnt into your memory15:49
ericy joined15:49
kalleth it was that or have 5 commits in a row with the title "Buggeration."15:49
bamj0rb omarek: commit --amend is still editing history. Same thing.15:49
psavage It's like the whole series of Steins;Gate ;)15:49
Nevik kalleth: why would you push them? o.O15:49
psavage kalleth, squash them?15:50
then you'd only have 1 :p15:50
Nevik psavage: i dont watch titles with semicola in them15:50
omarek The change I commited turns out to be harmful.15:50
psavage Nevik, our loss :p15:50
kalleth because they were to fix a weirdness with CI and i couldn't be arsed to branch off to a different branch to perform the fix and then adjust CI to trigger on that branch ;)15:50
bamj0rb omarek: You can use git revert to make a new commit that undoes an undesirable one. That is best if you want to undo it and still preserve history.15:50
psavage your :p15:50
Nevik psavage: hehe15:50
kalleth: then you deserve things to be throw at you15:51
omarek bamj0rb: Doable to a remote bare repo ?15:51
Nevik especially heavy, desnse objects15:51
at high velocities15:51
bamj0rb omarek: If you are in control of the project/remote/etc., then you could still edit history (I've edited history published to GitHub tons of times... Nobody is interested enough in my code to care :P).15:51
psavage sometimes people use it as part of their workflow15:51
bamj0rb omarek: You are just making a new commit. It is like manually undoing everything bad and committing again: "Ooops, this was stupid, undone..."15:51
Nevik bamj0rb: you *could* always edit history -- at the risk of the hate of everyone else in the world :P15:52
Goplat joined15:52
bamj0rb Nevik: Sure. Unless you actually get everybody to cooperate though your history editing will not work. They don't bother, they'll merge back in with you, etc. The history will still ultimately be there when you fetch again.15:52
Nevik that depends on who has push access15:53
in a stanard fork-PR workflow it's no problem15:53
because you can just reject everything that isnt right15:53
bamj0rb is a rebase *whore*. I am no stranger to editing history. I edit every commit like 20 times. :P15:53
psavage Depends on how the workflow goes, if you have someone who is in complete charge of a canonical repo, you may have contributors that clean the PRs ;)15:53
armin_w left15:53
Nevik i rebase a lot too15:53
but i dont collaborate much15:53
psavage too15:53
psavage rebase --onto a lot too :)15:53
I love that command15:53
Nevik lol15:53
simesy left15:54
psavage pick up a branch and move it else where :)15:54
bamj0rb Yes, I do that a lot as well.15:54
Nevik rebase --onto A^ A A^15:54
# keep branch moving so it doesnt go stale15:54
bamj0rb rebase --onto $new_base $thing~(git rev-list $new_base..$thing) $thing # ;)15:55
Nevik why use the revlist15:55
bamj0rb (Hmm, rev-list might be wrong.... I usually do log --oneline instead)15:55
Nevik but why15:56
rebase can take a difference15:56
bamj0rb Just saves you the trouble of counting revisions.15:56
psavage mine are usually branch tips anyway15:56
Gonzo89 left15:56
omarek I just made a new commit.15:57
bamj0rb --onto A B C tells git to only take the revisions between B and C (if I'm thinking clearly this morning...).15:57
Nevik bamj0rb: using the new_base..thing is the same as not passing the third argument15:57
bamj0rb Nevik: The third argument checks out $thing (if you aren't already there).15:57
Sonderblade left15:57
Nevik OH jessus15:58
bamj0rb If you're already on C then you can just do rebase $new_base.15:58
rubatdub left15:58
Nevik youre using the list as a number indicator15:58
bamj0rb Only when I know that it's The Right Thing(tm).15:58
Nevik i'd jsut copy the shas from gitk which i have open anyway, lol15:59
StarFire_ canton7: I am trying now with local branches and -- --all15:59
psavage hehehe ++ Nevik15:59
bamj0rb I do not use gitk. >:) I only use the command line. EVAR.15:59
lindenle left15:59
psavage though these days it's magit in emacs ;)15:59
StarFire_ canton7: It has now about 24000 commits instead of 2330015:59
Nevik bamj0rb: s/gitk/tig or git-log--graph/15:59
or what psavage said15:59
if youre an emacs kind of person15:59
psavage which i wasn't until 2-3 weeks ago16:00
rethus left16:00
psavage now I'd never go back16:00
dreiss joined16:01
Nevik heh16:01
TomyWork left16:01
bamj0rb uses Vim. >:)16:01
psavage getting flake8 python checking on the fly is really nice ;)16:02
joaoh82 left16:02
joaoh82 joined16:02
Nevik im using vim for some stuff as well16:03
canton7 StarFire_, sounds good16:03
lorenx left16:03
bamj0rb uses Perl. >:)16:03
omarek left16:04
LuxuryMode joined16:05
LuxuryMode left16:05
thierryp left16:05
leakybuckit left16:05
LuxuryMode joined16:05
qsusOFFcsqsuscs16:06
Nevik ive always wondered why perl has that extraneous vowel in its name16:06
that seems... unperlish to me16:06
psavage hehe16:08
sgambino joined16:08
CKyle joined16:10
ericy left16:11
tma996 left16:12
m0viefreak joined16:12
siavashserver joined16:13
ttl117 left16:14
bartzy left16:14
siavashserver Hello16:14
gitinfo siavashserver: 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.16:14
cbreak-work left16:14
carbon2 left16:15
siavashserver !backup send-email16:15
gitinfo Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups16:15
threesome left16:16
psavage left16:16
rubatdub joined16:17
VictorCL left16:17
dsdeiz joined16:18
wrouesnel left16:18
eletuchy left16:18
eletuchy joined16:19
Orphis joined16:19
abelsiqueira joined16:19
pedda joined16:19
hyperair joined16:20
eruMelko_ joined16:20
Ltk left16:20
sabgenton left16:21
Jackneill joined16:23
eletuchy left16:23
ngladitz joined16:23
ngladitz left16:23
ngladitz joined16:23
njbair # this log format can be split per-virtual-host based on the first field16:24
LogFormat "%V %h %l %u %t \"%r\" %s %b" vcommon16:24
rath left16:25
adhawkinsadhawkins-away16:26
bamj0rb (!backup is specifically help for backing up xD)16:26
gitinfo Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups16:26
bamj0rb Awww. >:( STFU gitinfo. Not now.16:26
dsdeiz left16:27
Zarthus joined16:27
ericy joined16:27
Gavrisimo joined16:30
StarFire_ bibi, cu16:30
lite_ joined16:30
StarFire_ left16:30
hyperair left16:31
Nevik bamj0rb: simple: use another punctuation in front of the exclamation mark16:31
like .!backup16:31
bamj0rb Ah.16:32
dhruvasagar joined16:32
Nevik i didnt know it would ignore the bracket though16:32
that's interesting16:32
TomyLobo joined16:33
bamj0rb It might be too complex, but in theory it could keep track of when it last said it, and if the target was joined at the time, and just tell the user to read the scrollback. :D16:33
Then if the user is really sure they want it repeated do !! instead. >:)16:33
jargon left16:34
dreiss left16:34
bamj0rb Nevik: Perl is not about consonants. It is about punctuation. :P16:34
Nevik btw that wouldnt be very complex16:35
but generally not necessary16:35
Gavrisimo left16:35
Nevik if it bothers you, you can just write a reactive ignore script for your client16:35
rubatdub left16:35
pandeiro left16:35
GeertV left16:35
Nevik shouldnt be a big deal for a perler :P16:35
bamj0rb It's a simple idea, but the implementation can certainly be finicky. It would be easy to do, but difficult to tune /well/.16:35
Like you said, it's probably not worth the trouble.16:36
aChatir left16:36
Nevik well, tuning something "well" is never done anyway16:36
you always just make things good enough16:36
which in this case would be 5-10 minutes or 30-50 lines16:36
King_Hual` joined16:37
rjhunter joined16:37
rob_w left16:37
endiruna joined16:37
Nevik s/or/and/16:37
user258467 left16:38
LuxuryMode left16:38
bamj0rb Are you sure about that? What about network interruptions, odd scrollback, IRC n00bs that don't know what you're talking about, etc. It might end up being more noise than just repeating the help. :)16:38
pen left16:38
bamj0rb Who maintains gitinfo anyway?16:39
yhager joined16:39
user258467 joined16:40
Nevik jast16:40
King_Hual left16:41
hobodave joined16:41
King_Hual` left16:41
Nevik bamj0rb: https://github.com/jast/gitinfo/16:41
King_Hual joined16:41
aberrant joined16:41
Nevik youre gonna love those language stats16:41
endiruna left16:42
rjhunter left16:42
endiruna joined16:42
doev joined16:42
jnavila left16:43
siavashserver left16:44
abelsiqueira left16:45
dsdeiz joined16:45
ciampix left16:45
dsantiago joined16:46
bamj0rb The language stats seem to be removed from GitHub...16:46
noyb left16:47
rubatdub joined16:47
LuxuryMode joined16:47
dsantiago left16:47
hyperair joined16:47
Nevik nope16:48
theyre in the same place where they used to be, only now you have to click them to see the numbers16:48
it's a silly change that no one at github has yet seen fit to fix16:48
because fuck the users16:48
bamj0rb I don't remember where they used to be. :(16:48
Bass10 joined16:49
rcu joined16:49
eletuchy joined16:49
Bass10 left16:49
bamj0rb Oh, there we go. Just a mysterous line. BRILANT UI GitHub.16:49
kjellski left16:49
dhruvasagar left16:50
ericy left16:50
Bass10 joined16:50
eruMelko_ left16:50
rcu left16:50
bamj0rb I should probably study gitinfo's code. I am in need of learning an event framework in Perl. Bambot is in need of refactoring. >:)16:51
irqq_ joined16:51
bbloom left16:51
kukks left16:52
Nevik lul16:52
kriks joined16:52
Nevik bamj0rb: feel free to let github knokw how you feel about the language bar :P16:52
johnkevi_ left16:53
gua_ould left16:53
pheaver joined16:54
irqq left16:54
irqq_irqq16:54
bamj0rb If I'm going to talk to a brick wall I want it to be one that I like.16:54
Misan left16:56
Nevik hands bamj0rb finger paint16:56
abelsiqueira joined16:57
arjun_ left16:57
yhager left16:58
Norm_ joined16:59
bvi left16:59
Noldorin joined17:01
pheaver left17:01
lite_ left17:02
VictorCL joined17:03
Abbas-- joined17:03
lite_ joined17:03
Abbas-- guys, i keep getting this error. i just added my github repo as git origin master. http://i.imgur.com/OaDwvcS.jpg17:03
when i try to push from local folder, this is error i get ^17:03
bamj0rb Your remote is origin. origin/master is a remote tracking branch.17:04
imMute Abbas--: did you read the message? it's pretty detailed17:04
groglogic joined17:04
Abbas-- imMute what is an upstream branch?17:04
bamj0rb See also man git-push.17:04
gitinfo the git-push manpage is available at http://jk.gs/git-push.html17:04
CKyle left17:04
imMute Abbas--: the branch on the remote17:04
LuxuryMode left17:05
lb1a left17:05
imMute Abbas--: translation: "I have no idea where I should push this to. Here's how to tell me."17:05
Abbas-- ah , thanks :)17:05
so it shud act like normal after i run that command?17:05
Macka joined17:06
Abbas-- i see progress :D thanks http://i.imgur.com/nxEy4ce.jpg17:06
Davey left17:06
imMute depends on your definition of "normal" (and the setting for ... push.default)17:06
ericy joined17:06
ericy left17:06
Abbas-- I'm the sole developer for my git repo. i just use it so i can have multiple time-frame backups17:07
drjd joined17:07
ericy joined17:07
Abbas-- so as long as this allows me to push new code without losing previous history on github, it'll be great17:07
alorence left17:07
stany_ joined17:07
PaulCapestany left17:09
mikecmpbll joined17:09
Freeaqingme Hi; I need to move 20 submodules within my repository. How should I do so?17:09
LuxuryMode joined17:09
Macka Hi. I'm preparing to migrate a Perforce repo to git. I've used git-p4.py to clone the repo which produced a very large 598M git repo. There's one single file there that's a whopping 405M.17:11
.git/objects/pack/pack-93e056ddb68d22c2e0e515446c1837305e543033.pack17:11
It's not a blob17:11
jwmann left17:11
Macka so don't think I can find it and prune it with a filter-branch17:12
stany_ left17:12
Freeaqingme Macka, out of curiosity, why are you migrating?17:12
mikecmpbll left17:12
imMute Hassen: that's a packfile. it's a bunch of objects collected into a single file (like a tarball, but extra compression and deltas)17:12
Macka is there a way to reduce the size of that, or get rid of it without loosing any of the commit history?17:12
Hassen imMute, at what?17:13
mikecmpbll joined17:13
imMute Macka: you can repack it, and tell it to compress more aggressively17:13
Hassen: sorry, wrong nick.17:13
rurufufuss left17:13
imMute Macka: see my message to Hassen17:13
Hassen imMute, i see.17:14
Macka we're migrating because the company is splitting. Also we've moving to a new model that will use Gerrit & Jenkins.17:14
aberrant left17:14
threesome joined17:14
ThomasLocke left17:15
dhruvasagar joined17:15
shwaiil joined17:16
shwaiil HI17:16
oops! Hi: )17:16
TheFuzzball joined17:17
shwaiil Q: Can I prevent other members committing to the Master Branch ? I'd like them to create their own branch from Master but not being able to merge and push to Master branch - if this makes sense ? Thanks!17:17
jwmann joined17:17
moritz shwaiil: !gitolite has per-branch write access control17:17
gitinfo shwaiil: Gitolite is a tool to host git repos on a server. It features fine-grained access control, custom hooks, and can be installed without root. Download: https://github.com/sitaramc/gitolite Docs: http://gitolite.com/gitolite/17:17
shwaiil moritz: thanks :)17:18
Macka so I need to unpack the packfile to discover what's big in there, and clean up that way?17:18
shwaiil moritz: I've always worked solo, I guess Pull Requests are done in a different way correct and probably better for this cases when you want to keep control of your repo ?17:18
imMute Macka: no, "git repack" is the command you want.17:18
Macka: see https://www.kernel.org/pub/software/scm/git/docs/git-repack.html for more17:19
HappyLappy joined17:19
Gavrisimo joined17:19
Macka thanks very much. will read up on that and give it a go.17:20
fRAiLtY- left17:21
lun__ left17:22
TheFuzzball left17:22
master_j joined17:22
yhager joined17:22
Kayra joined17:22
Kayra_ joined17:24
moritz shwaiil: yes, that's one approach17:24
Kayra left17:24
PaulCapestany joined17:24
moritz I personally prefer trust, and haven't been burned yet17:24
fairuz left17:25
shwaiil moritz: yeah I see. So, basically, I can just ask my colleges not to push to Master and do a Pull request from their branch. If this makes sense ?17:25
moritz shwaiil: or you can just allow them to push to master, and ask them get a review first if they push anything controversal17:25
s/if/before/17:26
shwaiil moritz: ok, so I can do that too I see. Thanks!17:26
moritz it's really a cultural thing17:26
psyl0n left17:26
moritz you have to talk to them, and find out what works for everybody17:26
bobbobbins joined17:26
shwaiil yeah, I think I'll go with the pull request, first because I never done that as I always work solo17:27
second, because I need to send stuff for staging and the production: a shell script does this for me, that I created17:27
at least I could trigger that or do it manually if everything's ok, no conflicts and stuff.17:27
siavashserver joined17:28
siavashserver How can I send-email a specific git commit?17:28
mishok13 left17:28
ericy left17:28
imMute siavashserver: run the hook manually with whatever arguments it expects to send that commit.17:29
kukks joined17:29
kukks left17:29
kukks joined17:29
lun___ joined17:29
siavashserver imMute: simply git send-email?17:30
donmichelangelo left17:30
vtunka left17:30
imMute oh, send-email is an actual git command. ignore everything I said.17:31
psyl0n joined17:31
psyl0n left17:31
psyl0n joined17:31
donmichelangelo joined17:31
dxdt joined17:31
siavashserver erases17:31
Goplat left17:32
fairuz joined17:32
rainbyte left17:33
siavashserver Never mind got it17:34
bremner is it "-1" ?17:34
dsdeiz left17:34
siavashserver bremner: No I'm not after last commit17:34
git format-patch --cover-letter -M origin -o outgoing/17:34
and manually git send email /outgoing/whatever17:34
Noldorin left17:34
bremner but there is a -1 argument to git-format-patch that does a single patch17:35
master_j left17:35
Noldorin joined17:35
Balliad left17:35
bremner and those args can also be passed to git-send-email17:35
BiggFREE joined17:35
intellix left17:36
siavashserver nice17:37
btree joined17:38
teran left17:38
pfFredd left17:39
master_j joined17:39
btree left17:40
aberrant joined17:40
koda left17:41
Octalot left17:41
Abbas-- left17:41
thiago joined17:42
blinkdesign left17:43
achadwick left17:43
HappyLappy left17:44
kirin` joined17:44
HiramHibbard joined17:45
St_Marx left17:45
pen joined17:46
FerreusR left17:46
angelsl joined17:46
ericy joined17:46
mfulz joined17:46
pencilcheck joined17:47
St_Marx joined17:47
pencilcheck left17:47
pen left17:47
pen joined17:48
juril left17:48
kallis joined17:49
siavashserver left17:49
quejajajajaja left17:51
xobb left17:51
groglogic left17:51
groglogic joined17:52
tango_ left17:52
kukks left17:53
kukks joined17:53
MattMaker left17:54
mikecmpbll left17:54
mikecmpbll joined17:56
User458764 joined17:57
kallis left17:59
dhruvasagar left18:01
groglogic left18:02
Vampire0 left18:05
singham left18:06
pen left18:06
pen joined18:06
noyb joined18:06
xpe left18:07
looper joined18:08
diosmiux joined18:09
spaceonline left18:09
aberrant left18:09
GarethAdams joined18:10
ericy left18:10
kjellski joined18:14
pheaver joined18:14
Kayra_ left18:15
Sendoushi left18:16
bobbobbins left18:16
devbug joined18:17
Vampire0 joined18:18
alip left18:18
lbod joined18:19
asQuirreL left18:19
Ingmar left18:19
User458764 left18:20
asQuirreL joined18:21
lbod hi, this should be quick for you guys but it's workflow im constantly using at the moment. I'm working against an upstream and origin at the moment and my commits are added to upstream via GH pull requests. I want to blast everything in my local master, overwriting every file and any in progress commits, merges etc and then push that to my remote origin so it's always in sync with the remote upstream.. Whats the best way to do this?18:21
edude03 left18:21
ErKa joined18:22
joaoh82 left18:22
bamj0rb git checkout master && git reset --hard upstream/master # (assuming your upstream remote is named "upstream")18:23
joaoh82 joined18:23
ChrisAnn left18:23
lbod bamj0rb so if i get "Your branch and 'upstream/master' have diverged" should i just use -f?18:24
bamj0rb lbod: Warning. That will happily destroy uncommitted state, and it will hide all of your "local master stuff".18:24
lbod yeh thats fine18:24
bamj0rb Depends if you want to keep what you have in your branch or not. If you just want to follow upstream the you probably want to reset --hard.18:25
Or, if you just want to push upstream/master to origin/master, you can do that directly: git push origin upstream/master:master18:25
Add a -f if necessary (and you're sure).18:26
ericy joined18:26
lbod i think i follow.. ive been using git for a while now, only at home and not at work but it still confuses the hell outa me, makes me feel very inexperienced18:26
codiez joined18:27
bamj0rb If you just want to avoid messy merging, but want to preserve your own work, the you could instead rebase onto upstream/master. That would effectively move your divergent commits onto the end of upstream/master (so no merge necessary).18:27
lbod after checking git reflog, that looks like it worked ok, even though it warned me about merges18:27
bamj0rb Probably means you had previously merged (or pulled, which is fetch + merge) with origin or something.18:28
lbod yeh, ive been trying to use rebase and ended up in a messy state too.. i guess i need to create some test remote repos and work on them18:28
bamj0rb Yes, you just need to practice it a bit and you'll figure it out. It's actually really easy, but if you haven't done it before then it's easy to get confused.18:29
michael_lee left18:29
lbod reflog looks fine.. a side note, how long till you got properly acquainted with remote repo's?18:29
(and thanks btw)18:29
jAyenGreen joined18:30
gitinfo set mode: +v18:30
codiez left18:30
l0cust joined18:30
lbod bamj0rb i think thats what's starting to annoy me is i feel ive been doing it for a while but with really basic workflow and all against my own remote repo18:31
codiez joined18:31
shwaiil left18:32
edude03 joined18:32
jAyenGreen When I create a submodule, commit it to the base and then push the base, then clone the repo locally, it seems the fact that the local path is different from the remote path results in an error about the submodule path not being a repo18:32
bamj0rb lbod: I basically got curious about remotes pretty early. First I created a local one to push/pull with. The I created a GitHub account and started using that.18:32
lbod: If you're obsessive compulsive then that helps to encourage you to figure out how it works. :)18:33
Hello71 left18:33
bobbobbins joined18:33
lbod you might find it amusing, we still use cvs at work, so i only ever use git from home on o/s projects.. anyway, thx for the help..18:34
bamj0rb lbod: (On the other had, I find the reflog hard to follow, so if it looks fine to you then that's something to be proud of :D)18:34
lbod ahah shit, mibbe im wrong then :D18:34
diosmiux left18:35
bamj0rb lbod: It happens. You can be the force that triggers the switch to Git. There might also be a tool to interface Git with CVS (there is for Subversion). Worst case, you could always use both (secretly using Git). That's pretty common.18:35
Hello71 joined18:35
codiez left18:35
pedda left18:36
bamj0rb They predominantly use Mercurial at my company (which I am not happy about, but they're too stoopit for Git), and where I'm contracting right now they usually use *nothing*. D:18:36
matanya joined18:36
HiramHibbard left18:36
bamj0rb I basic find(1) reveals like 120 copies of binaries... Let alone source copies...18:36
Hello71 the correct solution is to name one file for each version in DVCS18:36
because then it's distributed18:37
dhruvasagar joined18:38
blinkdesign joined18:38
blinkdesign left18:38
blinkdesign joined18:39
m0ltar left18:39
asQuirreL left18:39
joelrobichaud joined18:39
l0cust left18:40
danecando joined18:40
speeder joined18:40
speeder can I sort of create a stash in a git repository, and apply it in ANOTHER repository?18:40
hs366 joined18:41
jAyenGreen If someone could look at the steps I followed and tell me where I went wrong I'd greatly appreciate it http://pastebin.com/tkkizPfJ18:41
richwestcoast joined18:41
Hello71 speeder: you are looking for the "patch" function.18:42
petey left18:42
Gavrisimo left18:42
speeder thanks :)18:42
bamj0rb speeder: \o/18:42
speeder bamj0rb: hey!18:42
=D18:42
petey joined18:42
canton7 speeder, or cherry-pick a commit18:42
EugeneKay speeder - Sure, a stash is just a (pair of) commit(s) stored with a funny ref. `git stash` in A, then in B `git fetch A refs/stash` to yank it over18:42
Or patch, sure.18:43
lbod thx again & bye, helpful ppl in here!18:43
lbod left18:43
speeder I want to do that because I am creating several games that have the same source code (only assets change, and some scripts), and that is my best idea to update they all at once...18:44
joaoh82 left18:44
joaoh82 joined18:44
bamj0rb The stash? Noo...18:44
Gavrisim_ joined18:44
BigBlueBacon joined18:44
EugeneKay Then it's a traditional patch scenario18:44
HiramHibbard joined18:44
jAyenGreen checks breath18:44
jnavila joined18:45
petey_ joined18:45
gua_ould joined18:45
petey left18:46
eletuchy left18:46
bobbobbins left18:47
richwestcoast left18:47
undecim joined18:48
richwestcoast joined18:48
bobbobbins joined18:49
shinnya left18:50
abelsiqueira left18:51
ericy left18:51
HiramHibbard left18:51
noyb left18:52
ravigehlot joined18:52
fossrox joined18:53
vurma left18:53
mikecmpbll left18:53
Black_Prince joined18:53
jnavila left18:53
Nevik speeder: git subtree might be interesting for you18:53
or submodules18:53
JustinMac joined18:54
Black_Prince what happened to git remote helpers python module in git 1.8.5?18:54
ravigehlot By mistake, I ended up including some large video files on my git index. The problem is that my hosting account has exceeded its quota. When I git push origin master, it exceeded the quota and hung up. So I git rm -r -cached videos/, re-committed. But when I re-run git push origin master, it tries to compress/commit the previous commit instead of deleting the videos.18:54
cbreak ravigehlot: git stores history18:55
it does not delete it18:55
jnavila joined18:55
cbreak ravigehlot: if you want to delete it, rewrite local history, so that the commit in which you added the files never happened18:55
ravigehlot: can you do a !lol and pastebin the first dozen lines or so?18:55
gitinfo ravigehlot: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all18:55
ravigehlot cbreak: that makes sense18:55
Sadeukko left18:56
Nevik ravigehlot: is your host github?18:56
ravigehlot Nevik: hawkhost18:56
Nevik: I got 3 GB total18:56
Nevik k, nvm :D18:56
cbreak github has a limit? :)18:56
liamkeil1 joined18:56
Nevik cbreak: yes18:56
but it's a limit, not a quote18:56
quota* even18:56
ravigehlot cbreak: how can I re-write history to have it forget the faulty commit?18:56
Nevik though depending on what youre thinking of as a quota, it might be called that too18:56
cbreak ravigehlot: in your situation, the easiest would probably be to reset the commit away18:57
codiez joined18:57
cbreak ravigehlot: git reset --soft commitbefore18:57
then git rm --cached -f filesyouwantgone && git commit -C oldcommit18:57
ciaranm joined18:57
speeder nevik too much confusing18:57
cbreak then git push -f18:58
ravigehlot cbreak: right. But I went back and made two other commits. One to delete the videos/ and another one to delete public/. So now I am ahead by 3 commits.18:58
cbreak: should I ran that 3 times?18:58
Nevik speeder: i didnt say you HAVE to use them. but using them is probably less hassle than patching everything manually all the time18:58
sq-one joined18:58
speeder nevik I tried before, did not worked, but I don't remember why18:59
ereslibre left18:59
Nevik i wouldnt know :P18:59
Noldorin left18:59
pekster I have a project and a local clone I'm using as a remote; on the remote is an 'expiry' branch and I'd like to cherry-pick 1 commit, but I need to change a couple lines as it contains info that "should not" go into the upstream. Is there a sane way to let git know I've "already merged" that commit since the final merge won't be the commit from my remote?18:59
abelsiqueira joined18:59
FerreusR joined19:00
Black_Prince left19:01
doev left19:01
bamj0rb speeder: Any way to make the program shared and just supply it different data (where scripts are also data)? You could track the assets/scripts without the program, and just combine them when installed.19:01
leeN joined19:01
HiramHibbard joined19:01
robertnix joined19:01
HiramHibbard left19:02
bamj0rb speeder: i.e., the_game -C path/to/game/assets19:02
EugeneKay Huh19:02
Try that one again?19:02
speeder bamj0rb: the problem is that my stupid SDK (Corona) do not support that19:03
Nevik bamj0rb: the assets are probably part of a development environment19:03
bamj0rb Seems like a good opportunity to refactor. ;)19:03
speeder Corona works by packing everything into a directory as the game (and everything I mean EVERYTHING, any random garbage there, go with it...)19:03
Nevik bamj0rb: that doesnt help if you need them in your project configuration19:04
speeder and Corona does not support build scripts (on purpose)19:04
abelsiqueira left19:04
cbreak ravigehlot: you should give me the !lol output19:04
gitinfo ravigehlot: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all19:04
speeder (if you want to use automated build you have to pay them 1k USD)19:04
gitinfo set mode: +v19:04
cbreak ravigehlot: basically, you want to reset to the commit before the mess started19:04
Nevik speeder: oh btw, you're not on linux for that kind of development, eh?19:04
abelsiqueira joined19:04
speeder Nevik OSX19:04
Nevik symlinks might be an easy solution19:04
bamj0rb speeder: Ah, so you're using a third party proprietary framework...19:04
speeder because iOS...19:04
AaronMT left19:05
yhager left19:05
Nevik dunno how well macos's fs does symlinks19:05
bamj0rb It is UNIX. Should be fine.19:05
speeder Nevik OSX is a fork of BSD19:05
Nevik bamj0rb: not if the fs doesnt like symlinks19:05
pekster HFS+ does symlinks fine; what the proprietary frameworks does though..19:05
yhager joined19:05
Nevik thanks pekster ;)19:05
speeder Corona dislike symlinks and hardlinks19:05
Nevik lawl19:05
so fail19:05
speeder I already tried (and ended with a crazy mess)19:06
ravigehlot cbreak: give me a sec please19:06
Nevik speeder: why did you pick that :P19:06
speeder Nevik because it was really fast to develop cross-platform stuff19:06
now I use it for legacy stuff19:06
cbreak Qt.19:06
speeder I switched 3 months ago to a new one19:06
Nevik ah19:06
cbreak the one and only.19:06
speeder cbreak: games, not business apps19:06
jnavila left19:06
speeder cbreak: also cross-platform I mean, Android + iOS19:06
cbreak OS X supports symlinks perfectly :)19:07
Nevik cbreak: you should read19:07
cbreak speeder: yeah, Qt can do that :)19:07
(somewhat :)19:07
Nevik lol19:07
Nevik gives cbreak a cookie19:07
ericy joined19:07
daito_ joined19:07
MattMaker joined19:07
cbreak has cookies disabled19:07
speeder Qt for making games is like trying to nail something using a spoon in place of a hammer19:07
yes, you can do it, but...19:07
AaronMT joined19:08
JustinMa_ joined19:08
BigBlueBacon left19:09
liamkeil1 left19:09
thierryp joined19:10
zhost joined19:10
ehmatthes joined19:10
Gamecubic joined19:11
daito_ left19:12
fossrox hi guys, i don't have much experience with git yet and have such as issue: i converted my bzr repo to git, and then i updated the email information according to 1st answer http://stackoverflow.com/questions/750172/how-do-i-change-the-author-of-a-commit-in-git -- all looked ok, meaning that 'git log' was showing new email and complete list of commits19:12
tango_ joined19:13
fossrox but then i notices that with git log --all i can still see old email addresses, and when tried to play with python-git i could see imports and rewrites (the email rewrites), is there a way i can remove that completely from my repo? how much i should worry about this not going to published to public repo?19:14
abelsiqueira left19:14
ehmatthes left19:15
JustinMa_ left19:15
Octalot joined19:15
abelsiqueira joined19:16
fossrox in next step i installed some gui tools to visualize the branches, i have there only master branch with correct commits and then some commits from import which do not belong to any branch at all, not sure how to get rid of that stuff19:16
valgrind joined19:17
Nevik fossrox: can you post a !repro or screenshot of that git log showing both old and new email address?19:17
gitinfo fossrox: 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.19:17
Nevik my guess is you have some branch or tag that still points to the non-rewritten history19:17
kukks left19:18
fossrox ok, will start with paste19:18
master_j left19:19
dxdt left19:20
kpreid is there a convenient way to remove empty directories (only)?19:20
User458764 joined19:20
Nevik kpreid: reclone :P19:20
jnavila joined19:21
kpreid oh, hm, it had ignored files which is probably why it didn't get auto removed anyway19:21
Nevik otherwise, besides writing a script for it, no19:21
moritz find -type d -empty -delete19:21
doesn't need a script :-)19:21
Nevik ah19:21
forgot about find19:21
the magic all-cure19:21
aberrant joined19:22
aberrant left19:22
Sendoushi joined19:24
St_Marx left19:24
jkremser left19:25
damccull joined19:25
damccull If someone submitted a pull request to my github project and I want to take the code from their request but not the changes to the version files...can I do that?19:25
Nevik damccull: sure19:26
damccull where should I look to learn how?19:26
lamont joined19:26
ericy left19:26
abelsiqueira left19:26
Nevik damccull: just trying it out. your friend is the checkout command in this case19:27
what exactly to do depends on both the situation and what you want it to look like afterward19:27
damccull Hmmm. Like there's 4 files changed and I want 3 of them19:27
Nevik damccull: are the version changes (that you dont want) in an extra commit or in the same commit as the other changes? (if the repo is public, feel free to link us)19:29
abelsiqueira joined19:29
damccull https://github.com/damccull/sublimetext-SolarizedToggle/pull/12/files19:30
I want all the files except the bottom two: messages.json, and update-*19:30
atomx joined19:30
hs366 left19:30
edude03 left19:30
hs366 joined19:31
deuti joined19:31
Nevik damccull: will it be a problem if the updated versions are in your history, but you remove them in another commit?19:31
damccull not really.19:32
can you back-date individual files?19:32
Nevik damccull: then you can merge the PR (manually or via the website) and then undo the changes in an additional commit19:32
damccull hmm19:32
Nevik what do you mean by back-date files? git does not keep track of individual files' dates19:32
it only keeps the dates of commits19:32
i can also tell you how to modify the second commit to remove the changes from history, if you want19:33
cbreak damccull: forget about pull/merge19:33
and do a git cherry-pick -n instead?19:33
or a normal cherry-pick and a commit --amend?19:33
I think I'd do the latter.19:34
nbrosnahan joined19:34
Nevik sighs19:34
damccull i shall google cherry pick19:34
cbreak there's man git-cherry-pick19:34
gitinfo the git-cherry-pick manpage is available at http://jk.gs/git-cherry-pick.html19:34
JustinMa_ joined19:34
damccull thanks. reading.19:35
davo left19:35
LuxuryMode left19:35
finspin joined19:36
codiez left19:36
codiez joined19:37
LuxuryMode joined19:38
fossrox Nevik, gitinfo http://paste.debian.net/68309/ -- does it help?19:38
finspin i have cloned remote repository, created a new branch, made changes but haven't committed yet. remote master have changed in the meanwhile. what's the best way to proceed?19:39
JustinMa_ left19:39
Nazca__ joined19:39
davividal We recently migrated from SVN on a (PHP) Symfony application. We have a lot of config files that we need to be versioned and a couple of times a year we need to change. Yet, we need to modify those same files for each developer (folders, URLs, emails, bla bla bla). So, we can't use .gitignore. What's the alternative?19:39
pheaver left19:39
Ingmar joined19:39
Ingmar left19:39
Ingmar joined19:39
finspin i thought of committing changes to local branch, switch to master, pull the latest version and merge my branch. there will be conflicts to resolve, right?19:40
cilly joined19:40
finspin oh yeah, i forgot to mention that i want to push changes back to remote master19:40
codiez left19:41
bamj0rb finspin: Conflicts are nothing to worry about (!panic). Also, there's no guarantee there will be conflicts. Also, you can either merge or rebase (similar, but different).19:41
gitinfo finspin: [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice!19:41
zhost left19:41
Nevik fossrox: that ipython shows the rewrite need not concern you. my guess is that it includes events from the reflog (which git log doesnt)19:41
joaoh82 left19:41
eletuchy joined19:41
nbrosnahan left19:42
ncd|leeN joined19:42
diegoviola left19:42
ncd|leeN left19:42
joaoh82 joined19:42
Nevik fossrox: as for the duplicate history, the normal log doesnt show branch names so that output doesnt help so much. try !lol and see if that makes sense to you19:42
gitinfo fossrox: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all19:42
leeN left19:42
finspin bamj0rb: gitinfo: thanks guys. i haven't done this before so just wanted to make sure im not doing anything stupid.19:42
gitinfo finspin: you're welcome, but please note that I'm a bot. I'm not programmed to care.19:42
Nevik fossrox: if it doesnt, paste it again, i hope it doesnt need too much editing19:42
Nazca left19:42
Nevik fossrox: if the names arent too confidential, you can also make the pastie private and pm me the link19:43
leeN joined19:43
Nevik i love how the bot auto-responds to thanks19:43
nicedice joined19:44
ericy joined19:44
finspin Nevik: love it too! it made me smile. for a second i imagined this super smart robot getting bored answering the same newbie questions all over again :)19:44
Nevik ;)19:44
takamichi left19:44
fossrox !lol19:45
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all19:45
zhost joined19:45
offby1 !herp derp19:45
EugeneKay .trigger_edit herp derp19:45
gitinfo EugeneKay: Okay.19:45
Nevik LOL19:45
totally worth it19:45
nbrosnahan joined19:46
leeN left19:46
leeN joined19:47
Noldorin joined19:47
davo joined19:47
luto !herp19:48
gitinfo derp19:48
Hassen left19:48
Nevik !gitten19:48
gitinfo Here, have a cute and cuddly Gitten. Nyaa~19:48
Sendoushi left19:49
fossrox Nevik: http://paste.debian.net/68315/ -- added the graph on the bottom19:49
petey joined19:50
Sendoushi joined19:50
stodan joined19:50
davividal We recently migrated from SVN on a (PHP) Symfony application. We have a lot of config files that we need to be versioned and a couple of times a year we need to change. Yet, we need to modify those same files for each developer (folders, URLs, emails, bla bla bla). So, we can't use .gitignore. What's the alternative?19:51
fossrox with gui the bottom/duplicated commits look like one line in a separated branch parallel to master19:51
Nevik fossrox: is [email@hidden.address] or <example.com> the name+email you want to have? (i.e. which is the old vs new one)19:51
codiez joined19:51
Cathy davividal: you could have the versioned config file called config.template or something19:51
fossrox Nevik: i want to have it 'User <example.com>' to avoid spam in future19:51
moritz davividal: the normal approach is to include your.conf.example in the git repo19:51
Cathy davividal: then each developer copies it to config19:52
moritz davividal: and .gitignore the actual .conf file19:52
fossrox but people should figure out how to contact still i think19:52
Nevik fossrox: heh. that's a bit weird of a measure but okay.19:52
fossrox: your history is fine19:52
Cathy i thought worrying about spam was passé in 201319:52
Nevik fossrox: in the graph you can see the bottom strip to be origina/refs/heads/master, which is a backup ref created by filter-branch when you rewrote history19:52
fossrox: if the new history (pointed to by the branch master) is like you want it, you can delete that backup ref19:53
Skrypter joined19:53
fossrox Nevik: how i would go about the deletion?19:53
joki left19:53
davividal Cathy: moritz yeah, the usual would be great, but I'm instructed to do small changes a time. So renaming is out for now :( I was thinking about update-index --assume-unchanged19:53
petey_ left19:54
moritz davividal: renames are small changes in git land :-)19:54
Nevik fossrox: if you want to be absolutely safe, make a !backup of your repo; then remove the folder .git/refs/original/19:54
gitinfo fossrox: Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups19:54
Cathy davividal: that's also very error prone19:54
davividal moritz: I know, but it's not my call... :(19:54
fossrox Nevik: thank you very much!19:54
pantsman joined19:54
Nevik fossrox: sure, no problem ;)19:54
pantsman left19:54
pantsman joined19:55
Cathy well people can just avoid committing their changes through any number of methods19:55
they're all going to require people not to make a mistake though19:55
fossrox :)19:55
Sendoushi left19:55
leeN left19:55
Cathy and you'll deal with erroneous commits to this file being pushed all the time19:55
davividal Cathy: I'm already dealing... :(19:55
Cathy: some guy just removed the files using git rm --cached and add them into gitignore19:56
fossrox !thanks19:56
gitinfo You're very welcome!19:56
fossrox :D19:56
Cathy davividal: sounds like you need to rename the file19:56
however, i can imagine one highly obfuscated alternative19:56
you could implement a post-receive hook on the central repository that examines all the changesets being pushed for whether they touch this file19:56
and if so, shows a message saying the file should not normally be checked in19:56
and requires them to type something ot confirm they really want ot do it19:56
moritz you could patch the application to also look in app.local.config if it exists19:57
ojacobson joined19:57
moritz and so give developers a method to override settings locally without touching the "proper" config file19:57
Cathy having files in the repository which are intended to be locally modified is fraught with peril anyway19:57
ruby|angry_hamst left19:58
Cathy actually the guy who gitignored the file would have been fine so long as he doesn't push that commit19:58
he could set it up to rebase what he actually wants to push to remove that commit19:58
rafaqueque joined19:59
Cathy not a good approach though19:59
joki joined19:59
joaoh82 left20:00
joaoh82 joined20:00
angelsl left20:00
rednaks joined20:02
davividal well, new issue! Someone just pushed into master! I need to undo his commits. :( Could I undo, say, the last 3 commits and put those 3 commits into another branch?20:03
ericy left20:03
St_Marx joined20:04
Cathy davividal: you can do that very easily20:05
but somebody else might push them back later, if they've already pulled them20:05
jizanthapus left20:05
Cathy just fix it to be the way you would like in your local repository and then push both branches (with -f)20:05
veebers joined20:05
Cathy maybe include another commit to master20:06
that way somebody else trying to push those commits back will get an error20:06
bwreilly joined20:06
Cathy better act quickly to reduce problems20:06
davividal: also you probably don't want to get in the habit of doing such things. if it works for you, you can just revert the commits in a new commit20:07
there's no real risk of losing data when you do this kind of surgery, but it could confuse your team20:07
especially people who aren't that familiar with git20:07
like the poor guy who pushed these commits20:08
he'll have to strip them off his local repository in order to pull again20:08
rednaks left20:09
davividal Cathy: I can strip his HEAD off, no worries :) (pun intended)20:09
karstensrage joined20:09
Cathy it might be warranted to send out an email about this operation20:10
or else somebody might not understand what is going on and do a push -f of their own20:10
karstensrage is git-scm.com down for everyone?20:10
davividal I know... we had to do this SVN -> git migration in a hurry this week and we're paying a high price for it :(20:10
karstensrage Sorry, no Host found20:10
Cathy well davividal this kind of surgeyr wouldn't exactly be clean in svn either20:11
davividal karstensrage: http://www.downforeveryoneorjustme.com/20:11
ianmcorvidae left20:11
St_Marx left20:11
davividal Cathy: we don't have SVN anymore :)20:11
Cathy in this case, that link is not that useful20:11
karstensrage: git-scm.com returns a number of A records20:11
some of the servers are down, some of htem aren't20:11
54.225.172.112 appears to be up20:12
St_Marx joined20:12
Cathy so you can see 54.225.172.112 git-scm.com to your /etc/hosts file20:12
*so you can add20:12
and then you should be able to use it20:12
rhombus joined20:12
rhombus left20:12
|rhombus| joined20:12
davividal Cathy: what I mean is: we migrated from SVN this week without training. That's why I'm dealing with those problems20:12
cff_ joined20:12
|rhombus| left20:13
hyperboreean joined20:13
rhombus joined20:13
CareBear\ davividal : exciting times20:15
ereslibre joined20:15
pdtpatri1k joined20:15
sohail left20:15
pdtpatri1k left20:16
kloeri joined20:16
hobodave left20:17
Dougie2187 left20:17
gan joined20:17
Dougie2187 joined20:17
speeder left20:18
takamichi joined20:19
VictorCL left20:19
ZujkisNx joined20:20
ericy joined20:20
Sendoushi joined20:21
bartzy joined20:22
bamj0rb left20:23
revyd joined20:23
ecube left20:24
bamj0rb joined20:24
gitinfo set mode: +v20:24
ianmcorvidae joined20:25
JustinMac left20:25
Nikoli hi, do git tests support only bash? because several tests fail with dash20:28
Dougie2187 left20:28
kcj joined20:28
koda joined20:28
Watabou joined20:29
offby1 I assume that the tests indeed demand a specific shell20:29
I also assume that there's a top-level makefile that ensures that the right shell gets used.20:30
karavanjo_ left20:30
offby1 I'd be further surprised if the tests didn't start with a "shebang line" that specifies the shell to use20:30
ojacobson It's entirely possible they specify sh but actually lean on bash features -- that's a regular failing for folks coming from systems where sh is bash (including redhat, and older debian)20:30
offby1 in other words: why on Earth are you running bash scripts with some other shell?20:30
ojacobson specific examples would hlep20:30
m0ltar joined20:30
offby1 nods gravely20:31
offby1 they sholy would20:32
EugeneKay All hail the glorious bash master race20:32
katterstrophe joined20:34
ericy left20:35
aChatir joined20:35
canton7 from what I've seen from the list, several people are very passionate about shell cross-compatibility, so I'd be surprised if basic oversights still lingered20:35
aChatir left20:36
l0cust joined20:36
kermit left20:37
Skrypter left20:38
paulweb515 left20:39
techkid6 joined20:39
pfFredd joined20:40
eletuchy_ joined20:42
tpollard joined20:42
eletuchy left20:42
sohail joined20:44
sohail left20:44
sohail joined20:44
revyd left20:44
codiez left20:45
shuaib joined20:45
simesy joined20:46
LuxuryMode left20:47
danecando left20:48
jhulten joined20:49
katterstrophe left20:50
simesy left20:51
ericy joined20:51
dxdt joined20:52
Cromulent left20:53
finspin left20:54
Noldorin left20:56
schribl left20:56
St_Marx left20:56
hoschi left20:57
St_Marx joined20:57
techkid6 Is there a way to git rid of previous (pushed) commits and re-push them?20:58
rubatdub left20:58
moritz only with force-push20:59
eqyiel left20:59
eqyiel joined20:59
damccull left20:59
techkid6 force-push?20:59
TheBrainWork left21:00
ecube joined21:00
moritz push --force21:00
techkid6 ok21:00
Gavrisim_ left21:00
techkid6 thanks21:00
Gavrisimo joined21:01
cilly left21:03
cillybabe joined21:03
Gavrisimo left21:04
techkid6 so do I just have to bring the head back to the commit before the (three) i messed up?21:04
then force a push?21:04
gua_ould left21:04
bobbobbins left21:04
canton7 beware that you're !rewriting_public_history potentially21:04
gitinfo 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/waqum21:04
canton7 but yeah21:04
or git push -f origin HEAD^^^:master21:04
techkid6 alright, thanks21:05
stodan left21:05
cillybabecilly21:05
Goplat joined21:07
Noldorin joined21:08
LuxuryMode joined21:08
sohail left21:11
cilly left21:15
TaylanUB left21:16
lite_ left21:16
VictorCL joined21:17
lite_ joined21:17
lite_ left21:17
JohnBat26 left21:17
lite_ joined21:17
paulweb515 joined21:19
telmich left21:20
abelsiqueira left21:20
kcj left21:20
m0ltar left21:21
davividal left21:21
CheckDavid joined21:21
dhruvasagar left21:21
lite_ left21:21
cfoellmann joined21:22
aChatir joined21:22
ericy left21:22
abelsiqueira joined21:22
SoftwareMechanic left21:22
simesy joined21:23
JustinMac joined21:24
srayner joined21:25
joaoh82 left21:25
leeN joined21:26
aChatir left21:26
closures999 left21:27
simesy left21:28
farmanimal joined21:28
visy left21:28
shuaib left21:29
St_Marx left21:31
St_Marx joined21:32
jeffszusz left21:32
setmeaway joined21:32
leeN left21:33
marthinal left21:34
ec|ipse joined21:36
ec|ipse im new to git and having some issues21:37
petey left21:37
ec|ipse so I did "git init test" to make a test repo21:37
im on windows btw21:37
srayner left21:37
petey joined21:37
St_Marx left21:38
St_Marx joined21:38
ericy joined21:38
ec|ipse when i try to add a file to it, it says "fatal: pathspec 'test.html' did not match any files"21:38
moritz so, is there a test.html?21:38
ec|ipse i dragged test.html into the test folder, and ran "git add test.html"21:39
cfoellmann left21:39
lindenle joined21:39
moritz ec|ipse: does a 'dir' or 'ls' command in the test/ directory show it?21:39
jds left21:40
ELLIOTTCABLE ec|ipse: oh gods21:40
your nick is the worst thing D:21:40
ec|ipse moritz: yes it shows it21:41
hah21:41
is there some kind of git navigation im missing? I don't know how to "be" in the test repo, It says ~ (master)21:42
petey left21:42
ec|ipse before any of this I just typed git init and now I have a .git folder also, idk if that affects anything21:42
leeN joined21:42
imMute ec|ipse: what does 'dir' or 'ls' tell you?21:43
ec|ipse oh shit21:44
hah... ok. I realize my mistake. the git bash confused me because i didn't think of it as a terminal, just commands for git21:44
itd help if i were on linux. well anyways, i cd'd into the test repo and it worked21:45
Nazca__Nazca21:45
Nazca left21:45
Nazca joined21:45
St_Marx left21:46
imMute ec|ipse: "git bash" brings bash to windows via cygwin. it still uses the shitty Command Prompt terminal emulator though.21:46
lamont left21:46
EugeneKay cygwin supports a local SSH server, so you can putty into that21:46
ec|ipse ok I see. Thanks!21:47
Gavrisimo joined21:48
acl_ joined21:49
Kayra joined21:49
WaReZ left21:50
matanya left21:52
maroloccio left21:52
jhulten left21:53
LNDN joined21:53
WaReZ joined21:55
quejajajajaja joined21:55
abelsiqueira left21:56
simesy joined21:56
VictorCL left21:57
unreal joined21:57
dxdt left22:00
HiramHibbard joined22:02
lindenle left22:04
WaReZ left22:04
ec|ipse left22:05
cff_ left22:05
madewokherd joined22:05
nilg left22:06
HiramHibbard left22:06
kjellski left22:06
User458764 left22:06
alezost left22:07
Ardit joined22:08
matanya joined22:11
King_Hual left22:11
Jackneill left22:13
shruggar joined22:13
polyzen left22:13
sq-one left22:15
irqq left22:15
noyb joined22:15
tmcmahon joined22:15
carbon joined22:15
joaoh82 joined22:19
snearch joined22:19
atomx left22:20
DMA joined22:20
DMA So... git 1.8.5 is not even a day old22:20
But is it stable, I guess?22:20
snearch left22:21
Su7 joined22:22
Su7 Hi all !22:23
gitinfo Su7: 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:23
Su7 !backup22:23
gitinfo Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups22:23
Su7 Well, thanks for the backup stuff !22:24
robertnix left22:24
Su7 I need some help guys.22:24
I have a v2.0 tag that is ahead of master by several commits22:24
I'd like to move master to this tag (so it includes all commits between current master and v2.0)22:25
does anyone have a clue ?22:25
cagedwisdom joined22:25
bamj0rb Su7: The most straightforward way is to merge: git checkout master && git merge tags/v2.022:26
Kicer86 left22:26
Su7 bamj0rb: that's what I tried in the first place, but I do have the dev branch that contains commits AFTER v2.022:27
slassh left22:27
Su7 so I'll need to merge the merge (!) of v2.0 and master to dev and master ?22:27
bamj0rb Su7: It's up to you. You can rebase instead. But it's a bit odd to rebase master on a tag (depends on your workflow).22:28
Su7: I personally find it odd that you have a tag /after/ master, but again it all comes down to workflow.22:29
Su7 bamj0rb: the idea is to write code on dev, then merge it to master, then tag22:29
but I forgot to merge to master for v2.022:29
let me try the rebase thing22:29
l0cust left22:30
quejajajajaja left22:31
Goplat left22:33
simesy left22:33
qsuscsqsusOFFcs22:34
mribeirodantas joined22:35
richwestcoast left22:35
adac left22:35
bamj0rb My workflow is still a work in progress, but I like to develop in a feature branch, and rebase onto master.22:35
I consider master the main "development" branch.22:36
lamont joined22:37
mdiers__ left22:37
xobb joined22:38
drjd left22:38
eijk_ left22:38
Gavrisimo left22:38
rendar left22:40
LuxuryMode left22:41
Watabou left22:42
Su7 bamj0rb: rebase worked like a charm. Thanks !22:42
xobb left22:42
Sendoushi left22:44
jnavila left22:44
johnkevinmbasco joined22:45
bamj0rb Su7: Do note that editing published history would be bad. :)22:45
magu|m joined22:46
Su7 Why would I do that ? :(22:46
bamj0rb I am currently torn between making production/testing a branch or tag. Currently they are tags, but that makes it somewhat hard to manage for bug fixes, etc. Doable, but yeah.22:46
Su7: If master has already been pushed then it is "published". See !rewriting_public_history. You *shouldn't* do that, but you should understand what it means. :)22:47
gitinfo Su7: 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/waqum22:47
mdiers__ joined22:48
wrouesnel1 joined22:48
Su7 Well, I'm the only one working on the repo at the moment so I don't really face this kind of issues :)22:49
magu|q left22:49
ericy left22:51
flaguy48 joined22:51
jarr0dsz joined22:51
looper left22:52
Kayra left22:52
endiruna left22:53
fossrox left22:54
atomx joined22:54
schribl joined22:55
looper joined22:55
jhulten joined22:55
LuxuryMode joined22:56
ngladitz left22:56
DMA left22:57
grahamsavage_ joined22:57
TomyLobo left22:57
halu left22:58
petey joined22:58
phile left22:58
VictorCL joined22:59
Kayra joined22:59
LuxuryMode left23:00
grahamsavage left23:00
oojacoboo joined23:01
looper left23:02
Tacker joined23:02
devbug left23:02
fairuz left23:04
groglogic joined23:06
groglogic left23:07
ericy joined23:07
bamj0rb left23:08
HiramHibbard joined23:09
HiramHibbard left23:09
HiramHibbard joined23:10
tvw joined23:11
harobed_ left23:12
rainbyte joined23:13
przemoc left23:15
abelsiqueira joined23:16
ehmatthes joined23:16
HiramHibbard left23:18
xerxas joined23:18
richwestcoast joined23:19
pantsman left23:20
Kayra left23:21
FerreusR left23:24
ericy left23:25
Balliad joined23:26
kukks joined23:26
kukks left23:26
kukks joined23:26
damccull joined23:27
harobed_ joined23:28
harobed_ left23:28
joaoh82 left23:28
rhombus left23:28
harobed_ joined23:28
joaoh82 joined23:28
joaoh82 left23:29
joaoh82 joined23:29
Watabou joined23:29
jhulten left23:30
harobed_ left23:33
petey left23:34
petey joined23:34
hs366 left23:35
dsdeiz joined23:35
nbrosnahan left23:35
Goplat joined23:36
Watabou left23:37
mfulz left23:39
l0cust joined23:40
juliohm joined23:41
ericy joined23:41
el3ctron_ joined23:43
mdiers__ left23:43
VictorCL left23:44
trusktr joined23:45
koda left23:46
Zarthus left23:47
jhulten joined23:48
JBlazeCo_ joined23:49
noyb left23:50
etcetera joined23:50
etcetera left23:50
nutron left23:51
freestyl3r left23:52
simesy joined23:53
leeN left23:54
mdiers__ joined23:55
RDove left23:56
raonyguimaraes left23:56
mdiers left23:56
tmcmahon left23:58
valgrind left23:59
tvw left23:59
petey left23:59

Logs Search ←Prev date Next date→ Channels Documentation