IRCloggy #git 2013-03-08

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-03-08

catsup joined00:00
w09x joined00:00
w09x left00:01
iveqy but the parents git doesn't exists anymore?00:02
__Big0__ left00:02
avalarion the parent exists, but is not recognizing the files from the childs git00:02
__Big0__ joined00:03
Squarism2 left00:03
iveqy is there a file called .git in the child?00:03
avalarion i deleted it^^00:03
so not anymore00:03
guampa joined00:04
iveqy I'm confused... Let's see00:04
you had a git repo: a00:04
avalarion /home/.git00:04
v0n left00:04
avalarion is a00:04
/home/plugins/.git00:05
is b00:05
iveqy okay00:05
and you delete plugins/.git?00:05
avalarion yep, I did00:05
iveqy and was that a file or a directory?00:05
avalarion because I wanted to add all plugins to the main git00:05
it was a directory00:05
catsup left00:06
anonymuse left00:06
iveqy okay, in that case you should be able to do a git add now..00:06
tplaner joined00:06
elixir_ left00:06
catsup joined00:07
avalarion git status says that everything is up to date00:07
git add is not changing anything about this00:07
SBoudrias joined00:07
iveqy did you use git add before removing the .git dir in b?00:08
avalarion inside b or from parent? I would say both yes00:08
iveqy then b is registered as a submodule00:09
avalarion automatically?00:09
iveqy you need to delete the submodule to make git look for files in that directory again00:09
no, you added it...00:09
avalarion I've been afraid that you'd say this^^00:09
iveqy there's no way to delete a submodule today in git00:09
but you can do it manually: http://stackoverflow.com/questions/1260748/how-do-i-remove-a-git-submodule00:10
however, as you already done some cleanup not all steps applies to you00:10
avalarion git rm --cached path_to_submodule will not delete any files?00:10
Davey left00:10
iveqy avalarion: I'm unsure, I wouldn't count on it00:11
and I would suggest a backup before00:11
_abc_ left00:11
ssb1 left00:11
scelis joined00:12
avalarion thanks for your help!00:12
iveqy git submodules are extremly powerful, and hard...00:12
good luck =)00:12
avalarion I wll try it out tomorrow00:12
catsup left00:12
avalarion is it still not possible to be on master with submodules? do you know it?00:12
giallu left00:12
iveqy you mean to track master and not a specific commit?00:13
catsup joined00:13
avalarion yep00:13
roler joined00:14
iveqy oh, well git 1.8.1.3 was released a few hours ago. In the release message there was a note about git submodule had started to learn that00:14
sebuba left00:14
rabellamy joined00:14
iveqy I don't think git submodule had learnt it by heart yet... but hopefully soon00:14
avalarion it would be so much easier00:15
snql joined00:15
iveqy yeah in some cases. In some cases it just will be worse.00:15
You can easily end up with a configuration noone else had tested00:15
roler Hey guys, my team and I are taking the plunge to switch from svn to git. We have 2 other developers besides me. I am the final check of all code before it goes live. This is a website. What is the proper way to set this up? Setup live website as the "server" which I have ssh access to. I clone the directory. Do my developers clone the same live server, or my clone? Also, do they push updates to me, or do I pull updates from them to th00:16
push live?00:16
Vampire0 left00:16
cthuluh joined00:17
pinchy joined00:17
breck7 left00:17
iveqy roler: it's up to you...00:17
roler: git is flexible and can be used in many ways. You'll need to find the optimal way for your team to work00:18
mattp joined00:18
Vampire0 joined00:18
hakunin_ joined00:18
iveqy bare in mind that you cannot (or should not) push to a repository with a working index. That is, only push to bare repositories00:19
markalanevans left00:20
pastime left00:21
hakunin left00:21
siriuz joined00:21
roler iveqy; so the working index being the main master that I cloned rom.. So I should always log into the box and run a pull ?00:23
diegoviola joined00:23
pastime joined00:23
iveqy roler: yes, but you could automate that with a hook00:23
pinchy left00:25
xiangfu joined00:25
__Big0__ left00:25
jayrobot left00:29
b1rkh0ff left00:29
felipe left00:29
Nibato left00:29
Learath2 left00:29
charon left00:29
hwrd|work left00:29
Tommy[D] left00:29
mattp_ left00:29
przemoc86 left00:29
hyperair left00:29
todd_dsm left00:29
nelk left00:29
kukks left00:29
cyphase left00:29
rgngl left00:29
mgedmin left00:29
halcyonCorsair left00:29
xerxas left00:29
roger_raymond left00:29
vmiklos left00:29
Adys left00:29
claudiu____ left00:29
floppyears left00:29
ldlework left00:29
Khisanth left00:29
pdtpatrick left00:29
jbub left00:29
Derander_ left00:29
dlan left00:29
chadi_ left00:29
SaCu left00:29
Stravy left00:29
hays left00:29
ToBeFree left00:29
cxreg left00:29
RichardBronosky left00:29
PaulePanter left00:29
raz left00:29
Tekk_ left00:29
heidar left00:29
kpreid_ joined00:29
Parhs8 joined00:29
revele joined00:29
Parhs left00:29
preflex left00:29
phryk left00:29
alegen left00:29
mloskot left00:29
phryk_ joined00:29
cybersphinx joined00:29
robbyoconnor left00:29
sonicblud joined00:29
RichardBronosky_ joined00:29
Moult_ joined00:30
kmels_ left00:30
Internet13 left00:30
kpreid left00:30
orafu left00:30
rvl left00:30
kpreid_kpreid00:30
ohcibi left00:30
Moult left00:30
tokkee joined00:30
rufhausen joined00:30
orafu joined00:30
ohcibi_ joined00:30
preflex joined00:30
kmels_ joined00:30
the_cybersphinx left00:30
ehsan_ left00:31
pfefferz_ left00:31
duosrx joined00:31
duosrx left00:31
Marcux83|away joined00:31
Marcux83|awayGuest4022600:31
Nibato joined00:31
while1eq1 joined00:31
Learath2 joined00:32
Turicas joined00:32
yshh left00:32
boombatower left00:33
anabelle joined00:33
primitive left00:33
Internet13 joined00:34
alegen joined00:34
heidar joined00:34
eletuchy left00:34
techlife left00:34
karupanerura left00:35
eletuchy joined00:35
j^2 left00:35
karupanerura joined00:35
lethjakman_lapto left00:36
stliu joined00:36
rufhausen left00:36
natechan left00:36
cashwilliams joined00:37
cashwilliams is this the correct channel to ask for help?00:37
or is there a git-support or something I should be in?00:38
techlife joined00:38
vierja joined00:38
decotii joined00:39
SBoudrias left00:39
decotii left00:39
hwrd|work joined00:39
Tommy[D] joined00:39
mattp_ joined00:39
przemoc86 joined00:39
todd_dsm joined00:39
nelk joined00:39
kukks joined00:39
cyphase joined00:39
rgngl joined00:39
mgedmin joined00:39
halcyonCorsair joined00:39
xerxas joined00:39
roger_raymond joined00:39
vmiklos joined00:39
Adys joined00:39
claudiu____ joined00:39
floppyears joined00:39
ldlework joined00:39
Khisanth joined00:39
Tekk_ joined00:39
pdtpatrick joined00:39
jbub joined00:39
Derander_ joined00:39
dlan joined00:39
chadi_ joined00:39
SaCu joined00:39
Stravy joined00:39
hays joined00:39
ToBeFree joined00:39
cxreg joined00:39
PaulePanter joined00:39
raz joined00:39
w0m joined00:39
surfdue joined00:39
Slush- joined00:39
tm512 joined00:39
sacrelige joined00:39
Paparaciz joined00:39
ejnahc joined00:39
badfw2 joined00:39
Hamled joined00:39
iAsterisk joined00:39
alip joined00:39
Tuna-Fish joined00:39
Aaeriele joined00:39
eagles0513875_ joined00:39
SBoudrias joined00:39
HedgeMage cashwilliams: here's fine, just ask00:39
iveqy !welcome00:39
gitinfo Welcome to #git, a place full of helpful gits. If you have a question, feel free to just go ahead and ask—somebody should answer shortly. For more info on this channel, see http://jk.gs/git/ Take backups (type !backup to learn how) before taking advice.00:39
vierja left00:40
iveqy :), that worked. I really getting to like @gitinfo00:40
eletuchy left00:40
cashwilliams thanks00:41
d2dchat left00:41
cashwilliams I just got this message - "Your branch and 'origin/development' have diverged,00:41
and have 408 and 151 different commits each, respectively."00:41
HedgeMage lol iveqy00:42
cashwilliams but thing is, I have made 0 commits00:42
I'm guessing someone changed history or something?00:42
kenperkins left00:42
Gentlecat left00:44
AdrienBrault left00:45
aberrant left00:46
myndzi joined00:47
myndzi hey, i've generated an ssh key and added it to my github account, but git still prompts me for a user/password00:47
it's got to be some config thing but i don't know what to look for, any help?00:47
eletuchy joined00:47
skorgon left00:48
jjore joined00:49
HedgeMage myndzi: You need to tell ssh how to id you to github :)00:49
myndzi: You are on Linux?00:49
myndzi i think i just found the problem actually (of course)00:49
need ssh:// in the config00:49
yes?00:49
HedgeMage just go to your ~/.ssh/config and add an entry that looks like this:00:50
Host github.com00:50
User yourusername00:50
Hostname github.com00:50
IdentityFile /path/to/your/key00:51
opus left00:51
HedgeMage :)00:51
myndzi ah that makes sense. i suppose my local user isn't the one i want to log in with00:51
HedgeMage Then you're done00:51
myndzi thanks so much!00:51
HedgeMage You want to log in with your github username :)00:51
np00:51
R1KRDO joined00:52
minusthetiger left00:53
Turicas HedgeMage, myndzi to push to GitHub you should log-in with user 'git'00:53
its servers will identify your GitHub username based on your public key00:53
myndzi that did it00:54
\o/00:54
etcetera left00:54
bubbles10101 left00:55
opus joined00:55
roler left00:56
mikepack joined00:56
sonicblud left00:56
SethRobertson joined00:56
jayrobot joined00:56
otherj left00:58
Gentlecat joined00:58
Ryback_ left00:58
ejd left00:59
Targen left01:00
myndzi left01:00
tmcmahon joined01:00
nkr left01:00
scrape joined01:01
SeoZ-work[AWAY]SeoZ01:01
rchavik joined01:01
rabellamy left01:02
Targen joined01:03
yshh joined01:03
jjore left01:03
Gentlecat left01:04
rfoust joined01:04
huoxito joined01:04
Gentlecat joined01:05
thl0 joined01:05
minusthetiger joined01:06
mikef left01:06
pxdr left01:06
pxdr joined01:07
OliverJAsh joined01:07
danishkhan left01:08
tmcmahon left01:08
HedgeMage Turicas: Interesting, I've always done it with my github username...it works01:08
HedgeMage shrugs01:08
thl0 left01:10
Turicas HedgeMage, hahah so probably they ignore it, but when you copy the "git clone URL" from the Web interface, it says "***git***@github.com:username/repo.git"01:10
NiteRain left01:10
bousquet joined01:10
ojacobson joined01:10
HedgeMage fair enough01:10
I've been using hub for awhile, so maybe it overrides what's in my ssh config anyway01:11
HedgeMage stopped paying attention after "it works"01:11
HedgeMage :P01:11
yshh_ joined01:12
jayrobotjayrobot_01:12
yshh left01:13
boombatower joined01:13
dtm guys, i'm wanting to change the 'git' command which is embedded in the gitstats script, so that it only displays since a certain date and only with certain contributors. what's the syntax for the 'git' command to do that?01:13
SethRobertson dtm: man git-log. Look at the --since and --author restrictions. Most commands that allow selection allow those restrictions01:14
gitinfo dtm: the git-log manpage is available at http://jk.gs/git-log.html01:14
jayrobot_jayrobot01:14
sgronblom joined01:16
maestrojed left01:16
scrape left01:16
bootstrapper left01:16
sallesao left01:17
bartzy left01:17
avtobiff left01:17
hyperair joined01:17
ehsan joined01:17
ssb1 joined01:18
bmac left01:18
chuckhar_ left01:18
monk3y left01:19
pdeee left01:19
relipse joined01:19
etcetera joined01:21
cashwilliams left01:22
dtm SethRobertson: thanks01:22
dhruvasagar joined01:22
dtm SethRobertson: all i know is that it seems to me that the gitstats script calls the 'git' executable. i dont think it calls the git-log executable.01:23
Turicas left01:24
lethjakman_lapto joined01:25
skorgon joined01:25
bremner dtm: perhaps you should pastebin the relevant part of the script01:26
dtm bremner: yeah sorry i'm workin on finding that, thanks01:26
mfilipe left01:29
Sky[x] left01:29
dmarkham_ joined01:30
nigelb left01:30
nigelb joined01:31
OliverJAsh left01:34
mikepack left01:35
cirenyc joined01:35
cirenyc left01:36
R1KRDO left01:37
eletuchy left01:38
danishkhan joined01:38
eletuchy joined01:38
lethjakman joined01:39
boombatower left01:40
AnimeCYC left01:40
boombatower joined01:41
lethjakman_lapto left01:41
chuckharmston joined01:42
aberrant joined01:42
gdoteof left01:42
eletuchy left01:43
LeMike left01:44
opus left01:45
tongcx hi guys, why my git pull won't automatically rebase01:45
bootstrapper joined01:45
bremner maybe you didn't tell it to?01:45
tongcx is that because I didn't specify upstream or downstream or sth?01:46
bremner: how do i tell it to do automatically rebase?01:46
danishkhan left01:46
bremner man git pull01:47
gitinfo the git-pull manpage is available at http://jk.gs/git-pull.html01:47
bremner err, automatically must be a config option01:47
devians yep. rebase = true in config under the branch01:47
bremner see man git config, search for rebase01:47
gitinfo the git-config manpage is available at http://jk.gs/git-config.html01:47
pfefferz_ joined01:48
juril left01:48
kmels_ left01:48
sgambino joined01:49
bradios joined01:51
trungqtran joined01:52
Derega joined01:52
bradios left01:52
marc_kdab left01:52
marc_kdab joined01:52
hwrd|work left01:53
CodeShark joined01:57
rakl left01:57
simesy left01:58
simesy joined01:58
pfefferz_ left01:59
kmels_ joined02:00
jackh joined02:02
chuckharmston left02:02
maletor left02:02
simesy left02:03
alexim left02:03
d2dchat joined02:05
sluther joined02:05
WouterDS left02:05
mmlac left02:05
squentin left02:06
wrouesnel joined02:07
MatthewWilkesmwilkes|away02:07
mfilipe joined02:07
dmarkham_ left02:07
anna18 joined02:08
thiago left02:08
TechCel joined02:08
eletuchy joined02:09
jackh_ joined02:09
s0undt3ch left02:10
sallesao joined02:10
s0undt3ch joined02:10
dreiss left02:10
avtobiff joined02:10
squentin joined02:10
jackh left02:10
madewokherd joined02:11
simesy joined02:11
jaequery left02:11
pfefferz_ joined02:12
snql left02:13
maestrojed joined02:13
hiroyuki joined02:14
Noldorin joined02:15
quazimodo left02:15
mfilipe left02:16
WouterDS|Away joined02:18
lethjakman left02:19
hwrd|work joined02:19
eletuchy left02:19
intripoon joined02:19
private joined02:22
cashwilliams joined02:22
privateGuest9860402:22
cirenyc joined02:23
intripoon_ left02:23
rurufufuss joined02:23
Jay0x1 joined02:23
simesy left02:24
gitinfo set mode: +v02:24
gdoteof joined02:24
simesy joined02:25
Jay0x1 is it generally a good idea to git my whole c:/xampp?02:25
bremner no02:25
Jay0x1 or separate repositories?02:25
bremner probably. What is c:/xampp?02:25
Jay0x1 the web server bundle02:26
apache, mysql, php, perl02:26
http://www.apachefriends.org/en/xampp.html02:26
bremner in general, git is best suited for version control of source code, or similar text files02:26
bmac joined02:26
Jay0x1 i ask bc i've made changes to the config files of apache and would like to record these02:27
cashwilliams left02:27
Jay0x1 the conf files are std txt files02:27
bremner right, that could work out.02:27
spyro left02:27
pfefferz_ left02:27
Goplat joined02:27
Jay0x1 i'm sure there is a regex cmd for excluding exe files?02:28
bremner technically a glob and not a regex, but yes, you can do that.02:28
spyro joined02:28
pppaul joined02:29
HerrK left02:29
bremner if it's just config files, and they all live in the same place, it might make sense to put them in the same repo, like !etckeeper does02:29
gitinfo etckeeper is a collection of tools to let /etc be stored in a git, mercurial, darcs, or bzr repository. It hooks into various package managers. http://kitenet.net/~joey/code/etckeeper/02:29
simesy left02:29
Vampire0_ joined02:29
Jay0x1 don't have an /etc (i'm on win7)02:30
and the file structure looks like, c:/xampp/apache, c:/xampp/mysql, ...02:31
bremner well, it's up to you I guess.02:31
Vampire0 left02:32
splud left02:33
Jay0x1 never heard of glob, googled "git glob" but the details are sparse02:33
bremner it's just a wildcard, like *.exe02:33
Jay0x1 is there a certain syntax to it?02:34
bremner technically it is the "fnmatch" syntax02:35
maybe that is a better google term.02:35
see also man gitignore02:35
gitinfo the gitignore manpage is available at http://jk.gs/gitignore.html02:35
Jay0x1 real fast on the glob02:36
could it be something like "git add *.[!exe]"02:37
soypirate left02:37
bremner not directly.02:37
chuckharmston joined02:37
etcetera left02:38
Jay0x1 just simply "git add [!.exe]" (everything NOT a ".exe")02:38
simesy joined02:38
bremner that syntax doesn't exist, but if you know a scripting language, it's easy enough.02:38
bmac left02:39
Jay0x1 i wanted to learn git before i did programming so as to document changes (show growth and the like)02:39
bremner ah catch 22 ;)02:39
what about just adding individual config files?02:39
git add configdir/* would work, for example02:40
markalanevans joined02:40
anna18 left02:40
Jay0x1 xampp/ has 24 folders...02:40
i could just simply add the files i've touched (if i'm using the right terminology)02:41
the files i've made edits to02:41
bremner right. that makes sense.02:41
maybe even commit them before you edit, if you remember02:41
Jay0x1 ah! that's right...02:42
i won't remember lol02:42
alvaro_o left02:44
geniusape joined02:44
geniusape left02:44
Jay0x1 ok, onto the .gitignore02:45
sgambino left02:45
bremner good luck, /me off for now.02:45
NiteRain joined02:45
Jay0x1 i could make that file in either the project's .git or my $HOME/.gitconf right?02:45
thank you sir02:45
sgambino joined02:45
jcromartie left02:46
eletuchy joined02:46
SonikBoom left02:46
keller joined02:47
chuckharmston left02:47
ssb1 left02:47
ozette left02:47
eletuchy left02:47
MistuhKurtz So it seems like you can't initialize a brand new .git repo with a .gitmodules config file and run 'git submodule init' to initialize the submodules in there02:47
eletuchy joined02:48
MistuhKurtz anyone know if I'm mistaken?02:48
daniel_- left02:48
MistuhKurtz lol asking it in here helped me come up with a better search query - http://stackoverflow.com/a/11258810/19349402:49
lucs MistuhKurtz: That happens to me all the time: I prepare a question to paste into an IRC channel, then I just pop it into google, and bingo! :)02:50
MistuhKurtz I'm trying to create a boilerplate repo with submodules02:50
__Big0__ joined02:51
MistuhKurtz clone boilerplate -> rm .git -> git init -> git submodule init02:51
timj1 joined02:51
MistuhKurtz I suppose I'll just include that script in my boilerplate02:52
erkules_ joined02:52
devians left02:53
tongcx hi guys, how to list commits between two branches?02:54
up to common parent?02:54
timj left02:54
jaequery joined02:55
erkules left02:55
__Big0__ left02:56
bousquet left02:56
redrocket left02:57
aartist left02:57
jaequery left02:58
pen left03:00
pr0ton left03:01
mmlac joined03:01
redrocket joined03:02
meLon joined03:02
trungqtran left03:03
Jay0x1 left03:04
alainus[-_-]alainus03:04
herdingcat joined03:05
cbreak|evil joined03:05
marhaban1 left03:07
__Big0__ joined03:08
rking If you had a repo with dozens of branches, and you remember that one of the commit subjects said Foozwangle, how would you find that?03:08
timj1 left03:09
rking I could list out each branch then search each history, but that's a mess and also is going to be slow.03:09
dreiss joined03:09
Mannequin left03:10
guampa left03:11
frogonwheels joined03:11
orafu left03:12
OuLouFu joined03:12
OuLouFuorafu03:12
apok left03:13
s0undt3ch left03:14
armin left03:14
minusthetiger left03:17
hkj left03:19
herdingcat left03:21
arvind_khadri left03:22
cashwilliams joined03:23
tongcx hi guys, when remote branches are deleted, i need to manually delete the local remote branches, right?03:25
pen joined03:26
jason237 joined03:27
cashwilliams left03:27
pencilcheck joined03:29
cirenyc left03:29
milki yes03:31
natechan joined03:31
pen left03:32
dankest left03:32
mikepack joined03:33
eletuchy left03:35
eletuchy joined03:35
normanrichards joined03:36
fire joined03:36
infynyxx joined03:38
pastime left03:39
robbyoconnor joined03:39
eletuchy left03:40
__Big0___ joined03:42
sluther left03:43
Anders_J left03:43
kmels_ left03:44
__Big0__ left03:45
silntbob joined03:46
taylorlapeyre joined03:47
brian_ joined03:48
silntbob left03:48
whitemage joined03:49
beautifulmind joined03:49
sluther joined03:49
nickpresta joined03:50
Bankzilla left03:51
Guest98604 left03:52
pfefferz_ joined03:55
whitemage left03:55
wrouesnel left03:57
chrisgeorge joined03:57
wrouesnel joined03:57
pfefferz_ left03:57
chuckharmston joined03:57
markalanevans left04:01
chuckharmston left04:03
kcj left04:04
diamonds joined04:04
infynyxx left04:05
hatake left04:06
eletuchy joined04:06
kcj joined04:07
diamonds left04:09
pencilcheck left04:10
tjbiddle left04:10
curist joined04:11
pen joined04:12
griotspeak joined04:14
jaequery joined04:14
OOPMan joined04:17
eletuchy left04:17
kpreid left04:17
kpreid joined04:18
philips_ left04:18
jaequery left04:18
mattp_ left04:20
eletuchy joined04:20
pen left04:21
__Big0___ left04:23
ojacobson left04:24
philips_ joined04:25
aweorit joined04:25
chuckharmston joined04:26
mattp_ joined04:26
aweorit are branch commits completely removed from history when you delete a branch?04:29
natechan left04:30
EugeneKay No?04:30
Chryyz left04:30
milki aweorit: what kind of history?04:30
chuckharmston left04:30
chuckharmston joined04:31
aweorit` joined04:32
hwrd|work left04:32
aweorit left04:34
Bombe left04:35
thiago joined04:36
obert left04:38
dc5ala joined04:38
chuckharmston left04:38
Bombe joined04:40
pen joined04:41
chuckharmston joined04:41
eletuchy_ joined04:41
gtmanfred left04:42
hwrd|work joined04:43
gtmanfred joined04:43
Esa_ left04:44
nickpresta left04:44
eletuchy left04:45
hwrd|work left04:45
dankest joined04:46
solusfaran joined04:47
vedant joined04:48
dankest left04:54
preflex_ joined04:54
dydave joined04:56
preflex left04:56
preflex_preflex04:56
tongcx hi guys, with git log --all --graph i can see the structure of all commits04:57
how could I see all structure of a sub tree?04:57
AdrienBrault joined04:58
SBoudrias left04:59
maestrojed left05:01
aberrant left05:02
cworth left05:02
jayrobot left05:02
pretty_function joined05:03
jayrobot joined05:04
s0undt3ch joined05:05
armin joined05:07
dpwrussell left05:07
dpwrussell joined05:08
s0undt3ch left05:10
JeremyWei joined05:11
mmlac left05:12
maestrojed joined05:12
vedant left05:13
jphilly left05:13
subhojit777 joined05:13
b1rkh0ff joined05:14
Gentlecat left05:14
asd joined05:14
private joined05:15
asdGuest7285805:15
s0undt3ch joined05:15
privateGuest9049305:15
anabelle left05:17
aweorit` left05:17
Gentlecat joined05:17
dc5ala left05:18
dermoth_ joined05:18
otherj joined05:18
aberrant joined05:19
solusfaran left05:19
kukks left05:19
cybersphinx left05:19
taylorlapeyre left05:20
bootstrapper left05:21
dermoth|home left05:21
cashwilliams joined05:23
aberrant left05:24
jdunck left05:24
griotspeak left05:24
brum joined05:24
Tommy[D] left05:25
dpwrussell left05:25
dpwrussell joined05:25
nihilista left05:25
dtm bremner: sorry to delay. this is an old post, but it illustrates the portion of the code which queries the 'git' executable. http://stackoverflow.com/questions/4686647/how-do-i-modify-gitstats-to-only-utilize-a-specified-file-extension-for-its-sta05:27
cashwilliams left05:27
quazimodo joined05:28
dtm and here's the whole file https://github.com/ShawnMilo/gitstats/blob/master/gitstats05:29
so it's on line 27705:29
so just look at that github link on line 277 i guess.05:30
if you'd be so kind.05:30
again, i'm just wanting to know how to tell gitstats to use the 'git' executable to narrow its report down to just since a certain date and with certain people.05:31
brum left05:31
camkego joined05:32
JeremyWei left05:32
camkego left05:34
Vampire0_Vampire005:37
scorphus left05:37
scorphus joined05:38
OOPMan left05:38
eletuchy_ left05:39
Fandekasp left05:39
eletuchy joined05:39
rakl joined05:39
Tommy[D] joined05:39
Fandekasp joined05:40
felipe joined05:42
camkego joined05:42
mikepack left05:43
camkego left05:43
littlebearz left05:43
eletuchy left05:43
littlebearz joined05:43
QaDeS joined05:47
dhruvasagar left05:49
hoschi joined05:51
dhruvasagar joined05:51
o-O-o left05:51
fire left05:52
v0n joined05:52
dev2 joined05:54
chrisgeorge left05:55
dev2 I have two machines. I run git daemon --export all in my git repo on machine A. Then I clone that repository on machine B. Now machine B has the repo as well. Should I expect to see uncommited changes from machine A on the newly cloned machine B?05:56
rue left05:56
fire joined05:56
milki no05:56
dev2 is there a way to force it? I really just want to move all my work to another machine. I could just ftp it....05:57
Guest72858 left05:57
milki rsync?05:57
commit the changeS?05:57
boombatower left05:58
stliu left05:58
fire left05:58
normanrichards left05:58
dev2 its just a one time move. I thought clone took the working tree05:58
otherj left05:59
thiago dev2: git only transfers commits05:59
dev2 thiago: I thought clone was an exception.05:59
guess not :)05:59
thiago nothing is an exception06:00
git only transfers objects from the object database06:00
commits, tags, notes and stuff commits points to (trees and blobs)06:00
rue joined06:01
m0viefreak left06:01
dev2 now I know06:01
eletuchy joined06:02
thierryp joined06:03
eletuchy left06:03
milki dev2: nothing wrong with commit one-time things06:03
eletuchy joined06:04
fire joined06:05
eletuchy_ joined06:05
TechCel left06:05
fire left06:06
rakl left06:06
gruen0 joined06:08
eletuchy left06:08
richardeid joined06:09
rakl joined06:09
tewecske left06:09
simesy left06:10
simesy joined06:11
sgambino_ joined06:12
rue left06:12
picasso left06:12
Sigma joined06:12
Noldorin left06:12
sgambino left06:13
sgambino_sgambino06:13
jdunck joined06:13
Jay0x1 joined06:14
Katafalkas left06:14
gitinfo set mode: +v06:14
huoxito left06:14
quazimodo left06:15
simesy left06:15
scorphus left06:17
fire joined06:17
infynyxx joined06:18
camkego_ joined06:19
kswenson left06:19
gitinfo set mode: +v06:19
bootstrapper joined06:20
gitinfo set mode: +v06:20
camkego_ hello?06:20
gitinfo camkego_: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.06:20
mihamina joined06:20
camkego_ I broke the code. wow.06:20
Question for the knowledgeable :06:21
On this page: http://git-scm.com/book/en/Getting-Started-Git-Basics06:21
it says : Git has three main states that your files can reside in: committed, modified, and staged.06:21
and further, it says : Committed means that the data is safely stored in your local database. Modified means that you have changed the file but have not committed it to your database yet. Staged means that you have marked a modified file in its current version to go into your next commit snapshot.06:22
Is that true?06:22
Is there three states?06:22
muep yes06:22
camkego_ I get modified, but am confused on Committed vs Staged06:23
muep staged is not yet in any commit06:23
camkego_ git commit, commits to the index, correct?06:23
muep but it is what would get recorded into a commit if you run git commit06:23
dev2 before you can commit you have to stage the file (git add myfile.rb)06:23
camkego_ so staged = new file in work dir, and modified = file in working dir with modifications?06:24
dev2 new files aren't staged until you do git add new_file.txt06:25
camkego_ I think I get it, thank you for the clarification06:25
I was thinking modified and staged are the same, but they are not06:25
nickpresta joined06:25
camkego_ Thank you, muep, dev2 !06:25
nickpresta left06:26
camkego_ it is funny, because you need a commit after an 'add', correct?06:27
dev2 yes06:27
you can use git add .06:27
camkego_ so a staged file is not in the 'staging area' [index] correct?06:28
maybe that was part of my confusion06:28
dev2 to add all of the files, I avoid it though06:28
camkego_ yeah, I think git add . will get me in trouble06:28
lots of non-ignored files not in the repo06:29
Let me clarify, a staged file is not in the staging area, correct ?06:29
dev2 yeah, like the credit card statement I accidently put in my project folder :)06:29
camkego_ only Commited files are in the staging area, correct?06:30
R1KRDO joined06:30
cagedwisdom left06:30
dev2 I think that it IS in the staging area06:30
once its commited its unmodified06:31
Chryyz joined06:31
camkego_ well, if I understand, only a 'git commit' will put files in the staging area [index] ?06:31
dev2 I'm still very green myself so don't take my words to the bank06:31
giallu joined06:31
camkego_ so, a 'git add' will put a new file in the staging area, but it is as of yet, uncommited. correct?06:31
dev2 I think git add adds the files to the index, git commit commits the staged (index) files to the repo.06:32
vdv left06:32
camkego_ its all semantics, but import for us to understand06:32
fire left06:32
camkego_ dev2, I dont think so!06:32
commit -> index06:32
push -> repo06:32
I think06:32
experts?06:32
dev2 no, repo is local as well06:32
camkego_ I am not talking local vs remote06:33
quazimodo joined06:33
camkego_ just commit vs push06:33
dev2 push pushes all your commits to another repo, either remote or in some arbitrary location06:33
hwrd|work joined06:34
sluther left06:34
camkego_ you said 'git commit commits the staged (index) files to the repo.', I think that is wrong, I think the commit puts files in the index06:34
but I am just trying to figure it out. :)06:34
i am pretty sure commit -> index06:35
kswenson joined06:35
thiago no06:35
camkego_ thank you for all the help though06:35
thiago commit commits the staging are to the repository06:36
Guest90493 left06:36
thiago to the object database06:36
it is correct06:36
dev2 index stores the files until you are ready to commit them06:36
camkego_ then what does 'push' do ?06:36
I thought commit goes from working files -> index06:37
where index == staging area06:37
thiago push uploads the contents of one repository to another06:37
where contents = commits, tags and notes06:37
not the inde06:37
x06:37
git add does workdir -> index06:38
camkego_ I need to keep reading, and not waste your time! : )06:38
thiago git commit does index -> repo06:38
git push does repo -> other repo06:38
camkego_ local repo, i get it!06:38
thank you for explaining06:38
I feel silly, but it will sink in. : )06:39
dev2 yes thanks thiago06:39
camkego_ so, a git clone creates a local repo?06:39
thiago git commit *can* do workdir -> index -> repo in one go06:39
yes, it downloads the object database and creates a repository06:39
optionally, it checks out that repository (that is, create the workdir and index)06:39
camkego_ ok, so I better get used to the concept of local, and remote repo06:39
phryk_ left06:40
camkego_ Thiago, thank you for the help06:40
dev2 push and pull, (like send and get)06:40
thiago no06:41
push and fetch06:41
simesy joined06:41
phryk joined06:42
dev2 right bc pull does a merge06:42
thiago correct06:42
dev2 or?06:42
ok06:42
camkego_ so when I do a git clone, I usually copy from remote repo, and create local repo, and working dir, and local index, correct?06:42
thiago correct06:43
except there's no "usually"06:43
camkego_ always?06:43
thiago in what case wouldn't it be?06:43
camkego_ ok, got it06:43
fire joined06:44
mihamina left06:44
Jay0x1 left06:44
maletor joined06:44
jaequery joined06:45
madewokherd left06:47
Damgaard left06:48
maestrojed left06:48
engla joined06:49
d2dchat left06:49
simesy left06:50
jdunck left06:51
pantsman joined06:53
pantsman left06:53
pantsman joined06:53
PaulCapestany left06:53
Sky[x] joined06:54
fRAiLtY- joined06:57
Cromulent joined06:59
scrape joined07:01
pencilcheck joined07:02
nfroidure_ joined07:03
v0n left07:04
pen_ joined07:05
ThomasLocke joined07:05
pen left07:06
johnny_rose joined07:06
osse Correct me if I'm wrong: all the subdirectories of $GIT_DIR/objects should have the sticky bit set.07:06
_abc_ joined07:07
nfroidure left07:07
chuckharmston left07:07
pencilcheck left07:07
pen joined07:08
skorgon left07:09
longbeach joined07:10
cbreak-work joined07:11
cenuij joined07:11
cenuij left07:11
cenuij joined07:11
nfroidure_ left07:11
pen_ left07:12
hwrd|work left07:12
nfroidure joined07:12
nfroidure left07:13
maletor left07:14
hwrd|work joined07:15
jargon joined07:15
skorgon joined07:15
Katafalkas joined07:15
R1KRDO left07:16
Sigma left07:16
Goplat left07:19
hanzz left07:19
cyd joined07:20
cyd left07:20
beautifulmind left07:20
cyd joined07:20
KBme joined07:22
maestrojed joined07:23
cashwilliams joined07:24
Mez joined07:25
Mez left07:25
Mez joined07:25
KBme left07:28
erkules_erkules07:28
cashwilliams left07:28
alexwhitman left07:29
Mez left07:30
Cromulent left07:30
Mez joined07:31
Mez left07:31
Mez joined07:31
jdunck joined07:32
alexwhitman joined07:32
camkego_ OK, git pros! question number 2: ARE LOTS OF UNTRACKED FILES A PROBLEM? OR OK ? (about 30 files from git status)07:33
osse camkego_: not a problem if they aren't supposed to be in the repo (for example build products)07:33
camkego_: but if that's the case then you might want to add them to .gitignore so that git-status becomes for useful07:34
engla it's your call07:34
Damgaard joined07:34
engla if you have a clean repo you're not going to forget to add new files etc07:34
camkego_ okay, cool. I was wondering if I was supposed to have everything in .gitignore07:34
good point, engla!07:34
thiago left07:35
camkego_ so ideally, with a good .gitignore, no untracked files ?07:35
osse camkego_: say someone else clones your repository for purposes of working on the same project. Does he need/want the untracked files you now see?07:35
jceb joined07:35
TheJester joined07:35
Bombe camkego_, not everything belongs in .gitignore… also, there are three different ways to ignore files in Git. :)07:36
Mez left07:36
camkego_ it is a big project, and getting a perfect .gitignore is a fair bit of work, but it sounds like it is recommended07:36
Sigma joined07:36
camkego_ Bombe, what are the three ways?07:36
gasbakid joined07:36
Bombe camkego_, well, there’s .gitignore, there’s .git/info/exclude, and there’s a global ignore file (man git-config has details).07:37
gitinfo camkego_: the git-config manpage is available at http://jk.gs/git-config.html07:37
marthinal joined07:37
Bombe camkego_, I use the global file for files I always want to ignore, such as backups from my editor.07:37
camkego_ Bombe, @gitinfo, thanks07:37
gitinfo camkego_: you're welcome, but please note that I'm a bot. I'm not programmed to care.07:37
camkego_ nice!07:37
Bombe camkego_, .git/info/exclude I am using to exclude local environment stuff, such as configuration of my IDE.07:37
KBme joined07:38
camkego_ Bombe, cool, thanks07:38
Bombe camkego_, and that leaves mostly only build products for .gitignore, such as *.o if you’re doing C/C++, or target/ folders if you’re e.g. working with Java/Maven.07:38
arvind_khadri joined07:39
camkego_ ok, cool07:39
RandalSchwartz joined07:40
RandalSchwartz waves07:40
tsdh joined07:40
soee joined07:42
pppaul left07:42
h0bbit joined07:42
Jahm left07:43
rob_w joined07:44
ducch joined07:45
Jahm joined07:46
simesy joined07:46
Mez joined07:46
Mez left07:46
Mez joined07:46
Cerise joined07:47
elixir_ joined07:47
Guest45517 joined07:48
boucman_work joined07:48
gitinfo set mode: +v07:48
thyseus left07:48
TheJester anyone here using git bash under windows ? im having trouble getting access to repo. Doing ssh -i privatekey gitolite@host gives me gitolite output. Doing a git clone ssh://gitolite@host/repo calls for a passwd, while doing the same from a linux pc does an actual clone... any ideas ? private key is also in dir in /d/Users/username/.ssh07:48
vedant joined07:50
cbreak-work TheJester: you need to make git use the private key07:50
which means making ssh automatically use it07:50
sjugge joined07:50
cbreak-work TheJester: the easiest way on Mac OS is to use ssh-agent, with ssh-add key07:50
sjugge left07:50
LeMike joined07:50
cbreak-work and then everything will work automatically07:50
probably won't work on windows, so try naming it correctly07:50
TheJester and correctly means ?07:51
cbreak-work it must be in $HOME/.ssh/id_rsa07:51
marthinal left07:51
cbreak-work id_rsa being the file containing the private key07:51
netiul joined07:51
eletuchy_ left07:51
cbreak-work you can cat $HOME/.ssh/id_rsa to look at it07:51
marthinal joined07:52
cbreak-work (if you don't see your private key, then it's not at the right place)07:52
eletuchy joined07:52
cbreak-work TheJester: you can also configure the ssh client to use the key, details are in man ssh_config07:52
thyseus joined07:53
simesy left07:53
cbreak-work (look for IdentityFile)07:53
elixir_ left07:53
TheJester daamn.... its working... file must be named exactly id_rsa07:54
bootstrapper left07:54
cbreak-work yes.07:54
Guest12999 joined07:54
cbreak-work if it's an rsa key :)07:54
TheJester i was under the assumption that you could have multiple, and just make names of the private keys unique and throw them all in .ssh and it would work07:54
dydave left07:55
bootstrapper joined07:55
cbreak-work nope, won't work.07:55
TheJester but anyway, assumptions are the mother of all....07:55
cbreak-work if you want that, use the config file as I said above07:55
or the agent as I said above07:55
TheJester ok, i will look into it... thanks !07:55
cbreak-work np :)07:55
St_Marx left07:56
arietis joined07:56
eletuchy left07:56
mihamina joined07:57
ferdev left07:57
grn joined07:57
rath joined07:57
xiangfu left07:57
Guest12999 left07:57
AdrienBrault left07:57
pen left07:57
dhruvasagar left07:57
xiangfu joined07:58
thierryp_ joined07:58
thierryp left07:58
ThePawnBreak joined07:59
eletuchy joined07:59
heoa joined08:00
bootstrapper left08:00
_abc_ left08:01
ohcibi_ohcibi08:01
ducch left08:02
stewiee joined08:03
papegaaij joined08:04
dhruvasagar joined08:04
stewiee left08:05
stewiee joined08:05
quazimodo left08:05
fire left08:06
YoungFrog joined08:06
quazimodo joined08:08
baba joined08:08
flijten joined08:08
baba left08:09
pen joined08:10
dhruvasagar left08:10
mulinux joined08:12
kewah joined08:13
bauruine left08:14
r0bby joined08:14
alorence joined08:16
OOPMan joined08:16
robbyoconnor left08:17
suy joined08:19
a-l-e left08:19
snql joined08:19
dydave joined08:19
dnr left08:19
TheJester left08:21
_Qman joined08:21
mihamina left08:23
magnus joined08:24
cashwilliams joined08:24
variousnefarious left08:25
Guest24782 joined08:25
jfisk1987 joined08:26
jfisk1987 hey all08:26
how can i undo a commit, but keep the changes i made?08:27
variousnefarious joined08:27
Guest24782 left08:27
jfisk1987 i commited stuff on the wrong branch08:27
ferdev joined08:27
pantsman left08:28
pen left08:28
magnus hello! this might seem like a odd question, but is it possible to completely replace the master of an origin? the situation i have is that i've deviated so much from the original tree that i just want to replace whatever is at origin. and i would prefer to not merge or keep any of the history. I could remove the entire repo and start over, but my origin is managed by a broken system which makes that difficult. Can i somehow push a new master08:28
that replaces the old one at my remote?08:28
vStone joined08:28
vStone When doing a git svn migration, and using --ignore-paths, is it possible to have git log all files that have been ignored?08:29
cashwilliams left08:29
jfisk1987 magnus: yes, you can delete hte old one08:29
delete the old one by git push origin :master08:29
and push a new one08:30
engla jfisk1987: you can cherry-pick the commit you made, onto the new branch08:30
nesti joined08:30
tango_ left08:31
jfisk1987 engla: i just thought of that. and then i realized i am just tired and was actually on the right branch :)08:31
engla hehe08:31
tango_ joined08:31
magnus i just did push -f, seem to do what i want08:32
mihamina joined08:32
kcj left08:33
jfisk1987 hmmm08:33
idk enough about that, but im pretty sure it will retain the history from bfore08:33
jjido joined08:35
nesti left08:35
jfisk1987 anywayz im out08:35
jfisk1987 left08:35
jjido left08:36
tim joined08:36
psoo joined08:36
engla it should be fine. some git hosts deny forced updates but allow deleting branches though08:37
snql left08:37
jjido joined08:37
tomek joined08:38
maxmanders joined08:38
nesti joined08:38
kewah left08:39
dhruvasagar joined08:40
Thra11 joined08:40
snql joined08:43
tPl0ch joined08:43
rasputin joined08:44
StanleyDing joined08:44
hendry joined08:45
elixir_ joined08:47
relipse left08:47
setmeaway2 joined08:47
xarragon joined08:48
Thra11 left08:48
StanleyDing left08:49
nihathrael joined08:49
simesy joined08:49
cristi_ joined08:50
cristi_Guest3008:50
charon joined08:51
Cromulent joined08:51
joooooo left08:51
setmeaway2 left08:52
dpwrussell left08:54
Sonderblade joined08:54
ThePawnBreak left08:54
dpwrussell joined08:54
simesy left08:54
leehambley joined08:55
LekeFly joined08:55
LekeFly left08:56
xarragon I just managed to push an annotated tag to a public repo, attached to a commit that was local. However, that commit had not been reviewed and was not ready for pushing. Deleting tags is bad practice from what I can tell. Is the proper solution to push the commit to origin, revert it and then push it once reviewed?08:57
setmeaway joined08:58
francisfish joined08:58
oposomme joined08:59
xarragon I assume that pushing a tag is similar to pushing a branch, everything up until that tag is pushed?08:59
Thra11 joined09:00
WorkeD joined09:01
puchrojo joined09:01
dbck joined09:01
SamB_ xarragon: yeah09:01
jdunck left09:01
SamB_ the difference being that tags aren't supposed to change09:01
dbck left09:02
xarragon Yeah, since they're more or less reference points..09:02
jjido left09:03
jaequery left09:04
SamB_ (though if you make a mistake and catch it quickly enough it's not too bad)09:04
alainusalainus[-_-]09:05
Jamiltz joined09:07
Thra11 left09:07
SeoZ left09:09
engla I think deleting tags is fine.. but never reuse the tag name09:11
xarragon Well now I let it sit and rot for a while, the commit is trivial and just moves a block of code in a build support script so in this case I will just push that one and keep the tag/commit.09:12
quazimodo left09:13
xarragon But for next time I'd nuke it if none else is working on the repo.09:13
Jamiltz Hey. Little question, imagine this: I'm working on my local development branch and make 10 commits for example. Then I merge to master and commit on master. Then I do a git log and see all the commits I performed on the development branch in the history. When I push to github I see all the "development commit". But I don't want them to appear.09:13
SeoZ joined09:13
dreiss left09:13
quazimodo joined09:14
Jamiltz especially when I name my commits on the development branch like s*** http://cl.ly/image/0l2u2H1N191U09:14
milki Jamiltz: !perfect and clean up that history before pushing09:15
gitinfo Jamiltz: [!postproduction] So, you want to make your commit history look pretty before pushing? http://sethrobertson.github.com/GitPostProduction talks you through how to use 'rebase -i' to do this.09:15
kmels_ joined09:15
Jamiltz milk gitinfo thanks, yeah that's basically it. Or even simpler, I want to ignore all the commit messages of the development branch after merging with master09:18
gitinfo Jamiltz: you're welcome, but please note that I'm a bot. I'm not programmed to care.09:18
rakl left09:18
AaronMT joined09:18
Vile left09:18
Jamiltz :|09:18
milki the do the rebase before the merge09:19
then*09:19
Thra11 joined09:19
Jamiltz milki cool09:20
LekeFly joined09:21
gruen0 left09:22
soc42 joined09:23
cashwilliams joined09:24
cashwilliams left09:25
IntricateRuin joined09:25
yuwang left09:25
wanders left09:25
wanders joined09:26
bootstrapper joined09:27
daniel_- joined09:27
simmel joined09:28
Damgaard left09:28
Zenith77 left09:28
Gentlecat left09:28
Zenith77 joined09:28
simmel Before you could use `git rebase -i` to automaticlly avoid "Merge-commits", but since a few released I now get $EDITOR to pick which one I want to include in the rebase. What changed and what should my new workflow be?09:29
dr_lepper -i means "interactive"09:30
it has always been spawning editor09:31
Damgaard joined09:31
simmel Ok, so I guess I'm remembering it wrong then = / What is the command I should be using?09:31
Damgaard left09:32
amcsi joined09:32
wanders left09:32
simmel Ah, it might be `git pull --rebase`?09:32
mihamina left09:32
wanders joined09:32
dr_lepper it might, yes09:33
Damgaard joined09:33
bauruine joined09:33
dahood joined09:34
bootstrapper left09:34
simmel Thanks and have a great weekend dr_lepper!09:34
dahood left09:34
simmel left09:34
eletuchy_ joined09:34
pretty_function can we change the command line text editor (used to type merge messages, etc) to a gui text editor?09:35
lb1a pretty_function: yes09:36
pretty_function how?09:36
lb1a pretty_function: man git config see core.editor09:36
gitinfo pretty_function: the git-config manpage is available at http://jk.gs/git-config.html09:36
pretty_function lb1a: gitinfo thanks, I'll take a look09:37
gitinfo pretty_function: you're welcome, but please note that I'm a bot. I'm not programmed to care.09:37
pretty_function ouch LOL09:37
lb1a ^^09:37
charon left09:37
charon joined09:37
eletuchy left09:37
lb1a pretty_function: maybe this helps you too http://stackoverflow.com/questions/8951275/git-config-core-editor-how-to-make-sublime-text-the-default-editor-for-git-on09:38
Damgaard left09:38
babilen left09:38
Damgaard joined09:39
pretty_function lb1a: so it should be the path to the executable/bin, right?09:39
lb1a if this bin is not in your PATH then yes09:39
duosrx joined09:39
eletuchy_ left09:39
littlebearz left09:40
vedant left09:43
johnny_rose left09:44
jalmeida joined09:49
lifelike left09:49
OOPMan left09:49
pretty_function now how do I test it? (make git open the editor)?09:49
ncd|leeN joined09:49
pretty_function feels dumb09:49
Damgaard left09:50
GeertJohan left09:50
amcsi_ joined09:50
jackh_ left09:50
Damgaard joined09:50
amcsi_ left09:50
siriuz left09:51
lb1a pretty_function: commit something?09:51
pretty_function lb1a: lol, yeah. thanks :)09:51
arvind_khadri left09:52
OOPMan joined09:54
AaronMT left09:55
eletuchy joined09:56
exoon joined09:56
JSharpe joined09:56
mulinux left09:58
dpwrussell left09:58
jetole joined09:58
jetole osse: ok. you there09:58
my comment and question was off topic for #bash09:59
dpwrussell joined09:59
jetole or if anyone else knows and wants to answer, my questions was: 04:58 < jetole> osse: regarding git, iirc, no one will ever commit the same file. I mean the file that git stores. I know two people might commit say, program.c changes but doesn't git store those as sha1's in a directory? Actually asking. not too sure09:59
mikef joined09:59
osse jetole: no, they won't, but they put files in the same subdir of $GIT_DIR/objects. And if that subdir is not writable, then you get an error.10:00
tinti left10:00
Guest7609 joined10:01
nihilista joined10:02
milki i dont see the reasoning behind not committing the same file10:03
jetole osse: so every commit is a different file named as the sha1?10:03
milki what if i want to add two empty files with different filenames?10:03
osse jetole: if I commit something that results in an object named abcdef12346 that is stored in $GIT_DIR/objects/ab/cdef123456. If ab/ didn't exit it will be created. Then you commit something and need to upload an object named ab5464534, to be put in $GIT_DIR/ab/6454334. But if the ab/ directory was created in such a way that it's not writable than me, then I can't upload.10:03
Oops, I mean if ab/ isn't writable by *you*10:03
jetole milki: I think you just run "git add file1 file2" and then "git commit"10:04
milki: I think. I don't use git often10:04
milki but wouldnt the file blobs be the same?10:04
jetole osse: ah I see10:04
osse milki: thatæs not a problem.10:04
Guest30 left10:04
osse milki: yes, the blobs will be the same.10:04
siriuz joined10:04
jetole milki: probably but they would be saved as separate files inside git since they are separate files10:04
osse jetole: hence the need to setsid the objects/ directory, so that when I create ab/ it will be writable by all.10:05
mwilkes|awayMatthewWilkes10:05
jetole osse: give me a sec10:05
osse: I don't think setsid is what you need10:05
uh.. you mean setuid?10:05
osse jetole: no, they won't. It's one of the ways git saves spaces. If two files are equal, they will be stored once. But if you check them out, you do get two files in the working tree.10:05
jetole: hmm, perhaps.10:05
milki iif the file blobs are the same, i would expect the file tree to be able to reuse the same file blob and just use a different filename10:05
osse jetole: no, setgid.10:06
jetole osse: I know git saves a lot of space but I didn't realize it did that for two different files commited separately10:06
osse milki: yes, that's how it works10:06
elixir_ left10:06
jetole osse: though it actually sonds like a good idea so no complaint from me10:06
elixir_ joined10:06
jetole osse: anyways I want to look into your ssh issue. give me a sec10:06
Guest7609 left10:06
osse jetole: keep in mind, the issue has been solved. so there's no rush :P10:06
mikewintermute joined10:07
Vile joined10:07
jetole osse: one thing that came to mind just now which is common in many VCS's is post commit hooks where you write a program or script or whatever and you tell the VCS to run this script I wrote after every commit to the server10:07
milki jetole: man githooks, either post-receive or update hooks10:08
gitinfo jetole: the githooks manpage is available at http://jk.gs/githooks.html10:08
jetole osse: but that still sounds like crutch resolution. I don't think your git install should be doing what it's doing and if it was normal then this corrective action would be done by default10:08
milki: I'm good. Helping out someone else. I don't use git often but we started the conversation in #bash10:09
osse: see what milki and gitinfo just said10:09
jkremser joined10:09
jetole milki and gitinfo: you guys sound like you can be helpful to osse here. He's running git+ssh. Every commit, if a dir doesn't exist then it's created with the perms of the user who commited it so other users can't commit to that dir until he chmod's the dir10:10
Raging_Hog joined10:10
milki check out !gitolite10:10
gitinfo 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/10:10
milki or the man git init --shared=group10:11
gitinfo the git-init manpage is available at http://jk.gs/git-init.html10:11
jetole milki and gitinfo: this doesn't sound like what I would call normal working behavious of a well tested and widly used application so... have you guys seen this? Have any advice for him. I was about to google and read on it but only because I'm not the guy to know the answer10:11
sirdancealo2 left10:11
jetole !gitolite osse10:11
gitinfo 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/10:11
hwrd|work left10:11
jetole well that didn't work10:11
mmlac joined10:12
alorence left10:12
jetole osse: but you now have a good place to start I think. I hope. Good luck. I'm going to bed but it seems like milki and ... oh that's a bot. Seems like milki may be a good person to ask from here or, well obviously the room in general. You get the point. Night10:12
osse: good night and good luck. Don't worry. I can feel the force is strong in this one. peace10:13
elixir_ left10:14
milki confuzzled10:14
jetole it's ok milki. I'm weird sometimes but osse needs the help so later guys10:15
milki later10:15
marhaban joined10:15
kerrick left10:15
wanders left10:16
babilen joined10:16
osse I could write a hook that double-checks that the permissions are correct, or I could isntall gitolite... OR I could setgid on the objects/10:16
:)10:16
jn_ joined10:17
milki osse: git init --shared=group will alleviate the need for setgid yourself10:17
osse I realize using gitolite is the proper way to go. But we are only three developers here. It has worked well for a year so far. It was just now that two developers needed to access the same objects subdirectory10:17
anderse joined10:17
kswenson left10:17
jetole milki: back when I was a kid drugs were common and we all used to hang out and have parties. big campfires outside, everyone passing acid or shrooms or whatever around, usually a bunch of joints and making free love whenever we felt like it. It was a fun and exciting time but things are different now. Anyways, we had a wild ride back then and I would do it again but you know, because of all the fun we had I can seem weird or ...10:18
beautifulmind joined10:18
jetole ... ecstatic sometimes but only too kids who aren't from that day and age man10:18
god I miss 2011. It was like so wild and radical and open10:18
milki lol sounds like a former hippie10:18
osse milki: I will definitely do that. I did not know about that option. I did chmod g+s on all the object dirs :O For future repos I'll do this. I should probably even run it in the current ones as well.10:18
milki nods10:18
jetole just kidding about 2011 or still being a kid then or doing tons of drugs when I was a kid but thought a little humor may be in order before I leave10:18
milki it sets a config option10:18
note its not the same as clone --shared10:19
osse core.sharedRepository is set to true in all the repos already. I can just change it to group I suppose10:19
milki i think it just tells git to use a differnt umask10:20
anderse left10:20
exoon left10:20
dhruvasagar left10:21
pastime joined10:21
dhruvasagar joined10:22
giallu left10:22
g3orge joined10:23
alorence joined10:24
milki uses gitolite and im the only user for most of the repos -.-10:26
milki its just so easy to use10:27
WorkeD left10:29
kurkale6ka joined10:30
codebeaker joined10:30
kurkale6ka Hi, how can I revert the changes related to a specific SHA?10:30
wereHamster kurkale6ka: what do you mean by 'revert to a specific SHA'?10:31
leehambley left10:31
vedant joined10:32
kurkale6ka wereHamster: not to a specific SHA, there many comits since that I wanna keep, but all changes to files in that SHA I want them back10:32
DoniRS joined10:33
soc42 left10:33
DoniRS left10:33
DoniRS joined10:33
engla git revert does exactly this10:34
kurkale6ka engla: ok, so git revert MY_SHA10:34
engla: cheers10:35
giallu joined10:37
wanders joined10:39
curist left10:40
tinti joined10:42
hkj joined10:43
AdrienBrault joined10:43
the_cybersphinx joined10:43
wanders left10:45
wanders joined10:46
Guest92252 joined10:46
Guest92252 left10:46
rasputin1 joined10:46
dorkmafia left10:49
rasputin left10:49
Chryyz left10:50
simesy joined10:50
OOPMan left10:51
eijk_ joined10:52
ncd|leeN left10:52
bartzy joined10:54
simesy left10:54
alexbligh joined10:55
wanders left10:55
hatake joined10:56
ozette joined10:57
Chryyz joined10:59
mikecmpbll joined11:02
przemoc86przemoc11:02
mihamina joined11:05
jcromartie joined11:06
Cromulent left11:07
bootstrapper joined11:09
babilen left11:09
VinceThePrince joined11:10
Raydiation joined11:12
Raydiation any tipps for11:12
*** Error in `git': malloc(): memory corruption: 0x0000000001b7f4e0 ***11:12
im getting this very often on more than one pc11:12
if i rebase11:12
engla sounds bad11:13
wanders joined11:13
engla git version and platform?11:13
jcromartie left11:14
Raydiation git version 1.8.1.511:14
engla: archlinux11:15
ThePawnBreak joined11:15
wereHamster Raydiation: can you reliably reproduce it?11:16
Raydiation im trying sec11:16
cloning the repo again :)11:16
Tommy[D]_ joined11:17
mikef left11:17
elixir_ joined11:17
elixir_ left11:17
jcromartie joined11:18
elixir_ joined11:18
bootstrapper left11:18
babilen joined11:18
Hounddog joined11:18
Tommy[D] left11:19
wanders left11:19
sgronblom left11:21
Squarism2 joined11:22
codebeaker left11:22
hyperair left11:23
wasanzy joined11:24
Raydiation wereHamster: yeah, i can reproduce it11:24
git clone https://github.com/owncloud/core.git11:24
cd core/11:24
git pull --rebase https://github.com/PatrickHeller/core.git master11:25
wanders joined11:25
iveqy using git version 1.7.2.511:26
I can't reproduce it11:26
cashwilliams joined11:26
mmlac left11:26
iveqy using git version 1.8.2.rc311:29
I can't reproduce it11:29
dwmw2_gonedwmw211:29
Khisanth left11:30
hkj left11:30
cashwilliams left11:31
wanders left11:31
iveqy using git version 1.8.1.511:32
Raydiation iveqy: maybe introduced in a newer version?11:32
Alecs left11:32
iveqy I can't reproduce it11:32
lahwran joined11:32
Raydiation iveqy: ty11:32
hkj joined11:32
hkj left11:32
Raydiation maybe ram or ssd issue11:33
iveqy Raydiation: this is still a problem, but not reproduceable on debian squeeze11:33
Raydiation although i havent noticed anything yet11:33
iveqy: does git link other libs?11:33
YoungFrog you said on multiple pc, do you share any hardware between them ?11:33
hkj joined11:33
Raydiation no11:33
hkj left11:33
brocken joined11:33
iveqy Raydiation: yes a few. libcurl, libc etc.11:33
Raydiation i cant try to reproduce the issue though because im 7 hours away from my main pc11:34
hkj joined11:34
hkj left11:34
Hounddog left11:34
VinceThePrince left11:34
hkj joined11:34
hkj left11:34
iveqy I would say the next step is to use git fetch and git rebase instead of git pull11:35
YoungFrog ok, just try with git version 1.8.1.4 and couldn't reproduce either.11:35
s/try/tried/11:35
hkj joined11:35
hkj left11:35
littlebearz joined11:35
iveqy if the error is in git fetch we could have a problem with libcurl, and that can be a reason we can't reproduce it (we're not using the same version of libcurl as you)11:35
Kichael left11:36
hkj joined11:36
hkj left11:36
kurkale6ka left11:36
YoungFrog you say you see the problem often ; how do you work around it usually ? or do you just leave thinsg as they are ? or is trying again sufficient ?11:36
tvw joined11:36
Chikore joined11:36
Raydiation most of the time i merge it11:37
not rebase11:37
hkj joined11:37
hkj left11:37
Raydiation although im not sure tbh11:37
im trying to split the stuff like you said11:37
how do i rebase after i fetched?11:37
simply git rebase?11:37
Jamiltz left11:37
Chikore left11:37
hkj joined11:37
hkj left11:37
wanders joined11:37
ThePawnBreak left11:38
YoungFrog I guess it should be "git rebase FETCH_HEAD"11:38
hkj joined11:38
hatakerhyda11:38
hkj left11:38
hkj joined11:39
hkj left11:39
Raydiation ty11:39
hkj joined11:39
hkj left11:39
hkj joined11:40
hkj left11:40
hkj joined11:41
hkj left11:41
dhruvasagar left11:41
leo2007 joined11:41
leo2007 has anyone used gitlab?11:41
hkj joined11:42
hkj left11:42
hkj joined11:42
hkj left11:42
g3orge left11:42
wereHamster leo2007: ask your actual question11:43
hkj joined11:43
wanders left11:43
hkj left11:43
wereHamster !yes11:43
Raydiation iveqy: http://dpaste.com/1016014/11:43
Onkeltem joined11:43
Raydiation can this even be related to curl?11:43
gitinfo set mode: +v11:43
hkj joined11:44
wereHamster Raydiation: no, this is in rebase11:44
hachque joined11:44
hkj left11:44
Onkeltem Hi all. I forgot how to automatically run merge tool when CONFLICT occurs :-/ Help please :)11:44
leo2007 it seems quite an effort to install. do you find it useful?11:44
wereHamster Raydiation: lines 8,9,10 are from git-rebase11:44
Raydiation yeah11:44
bootstrapper joined11:44
hkj joined11:44
hkj left11:44
Onkeltem So when I do: git merge something, I just get "CONFLICT (content): Merge conflict in blah blah" and my lovely meld is not launched :-/11:44
wereHamster leo2007: so your actual question is: Does anybody find GitLab useful?11:45
iveqy Raydiation: probably not, it's in rebase as wereHamster says11:45
leo2007 wereHamster: ;)11:45
hkj joined11:45
hkj left11:45
Raydiation iveqy: git pull works fine11:45
wereHamster leo2007: somebody does. Many do, in fact. Otherwise the people who write and use it wouldn't have started that project11:45
Raydiation so its probably something only related to rebase11:45
wereHamster leo2007: also: http://gitlab.org/ -> Who is already using GitLab?11:46
hkj joined11:46
hkj left11:46
iveqy the strange part is, we know that the problem probably is in git, but can't reproduce it11:46
dokma|2 joined11:46
hkj joined11:46
hkj left11:46
leo2007 what is the easiest way to get gihlab installed?11:46
gitlab*11:47
Raydiation maybe related to ram size?11:47
ive got 4gb11:47
hkj joined11:47
hkj left11:47
iveqy Raydiation: me too11:47
dydave left11:48
hkj joined11:48
hkj left11:48
Raydiation :/11:48
iveqy you said you can reproduce this on multiple machines?11:48
wereHamster leo2007: there is a button 'installation guide' on the website.11:48
Raydiation iveqy: well, ive encountered this on my other archlinux pc before11:48
Khisanth joined11:48
hkj joined11:48
hkj left11:49
Adys left11:49
iveqy and always on arch linux?11:49
Raydiation but i cant reproduce this issue since im 7h away11:49
diegoviola left11:49
Raydiation yes11:49
havent tried other distros yet though11:49
iveqy any specific version of arch linux11:49
?11:49
Raydiation amd6411:49
x86_6411:49
hkj joined11:49
dokma left11:49
hkj left11:49
ChanServ set mode: +v11:49
jast let's create 6502_6411:50
wereHamster Raydiation: arch linux as well, same git version. Cna't reproduce11:50
hkj joined11:50
hkj left11:50
iveqy wereHamster: Raydiation: same archlinux version?11:50
jast Onkeltem: sounds like you want to run 'git mergetool'11:50
iveqy thinking of glibc11:50
wereHamster iveqy: unlikely, arch linux is a rolling release11:50
Adys joined11:51
hkj joined11:51
hkj left11:51
wereHamster glibc probably yes11:51
Raydiation glibc version?11:51
n11:51
sry :)11:51
core/glibc 2.17-3 (base) [installed]11:51
arvind_khadri joined11:51
hkj joined11:51
hkj left11:51
gusnan joined11:52
iveqy wereHamster: that's fearly new build, since 28 january this year (I think)11:52
hkj joined11:52
hkj left11:52
jcromartie left11:52
hkj joined11:53
hkj left11:53
bootstrapper left11:53
tplaner left11:53
hkj joined11:53
hkj left11:54
wrouesnel left11:54
hkj joined11:54
hkj left11:54
wanders joined11:54
Raydiation glibc is famous for crap right?11:55
OOPMan joined11:55
hkj joined11:55
hkj left11:55
h0bbit left11:55
jast the only thing I know that glibc is famous for is Ulrich Drepper11:55
iveqy Raydiation: not what I know about.11:55
leo2007 wereHamster: thanks.11:55
Raydiation jast: ah right :D11:55
hkj joined11:55
hkj left11:56
iveqy I'm more in the thought of git using glibc in a strange manner. But malloc is pretty standard, there shouldn't be any problem there11:56
gommo joined11:56
iveqy more likely a memory corruption in git11:56
Raydiation: you should use valgrind to digg deeper in this11:56
hkj joined11:56
hkj left11:56
kadoban_ left11:57
hkj joined11:57
hkj left11:57
Raydiation iveqy: not sure if this is helpful, arch builds without debug symbols11:57
dont ask me why11:57
hkj joined11:57
hkj left11:58
eletuchy left11:58
hkj joined11:58
Raydiation or does valgrind work without debug symbols?11:58
hkj left11:58
eletuchy joined11:58
bremner it works better with debug symbols, but it does work without.11:59
hkj joined11:59
hkj left11:59
hkj joined12:00
Raydiation valgrind /usr/bin/git =12:00
?12:00
nkr joined12:00
Raydiation http://dpaste.com/1016031/12:02
heres the valgrind output12:02
r0bby left12:02
rhyda left12:03
Raydiation do i need to use valgrind with the proper git rebase param?12:03
eletuchy left12:03
Raydiation like valgrind /usr/bin/git --rebase ...12:03
tcurdt joined12:03
iveqy Raydiation: yes, you need a git crash12:04
DoniRS left12:04
tcurdt left12:04
aksnot joined12:05
RawProduce joined12:05
Element9 joined12:06
Onkeltem I've just realized how to handle several local branches :) Just make them all linked with remote!12:06
RawProduce I have a particular piece of code that I need to retrieve from a previous unknown commit - how can I grep through the entire set of changes in the repository and get the hash of any matching commits?12:06
Raydiation any tipps? im not an experienced C programmer ;)12:07
valgrind /usr/bin/git pull --rebase https://github.com/PatrickHeller/core.git master12:07
doesnt really rebase anything12:07
grawity RawProduce: man git log, see the -S and -G options12:07
gitinfo RawProduce: the git-log manpage is available at http://jk.gs/git-log.html12:07
RawProduce thanks grawity12:08
mishok13 left12:08
kmels_ left12:08
mishok13 joined12:09
DoniRS joined12:09
Raydiation k, oversaw git error msg12:11
now im stuck with http://dpaste.com/1016037/12:11
rasputin1 left12:11
Raydiation if i ctrl c this is the output http://dpaste.com/1016038/12:12
rmichnik joined12:12
boo joined12:12
vedant left12:13
iveqy Raydiation: thanks. However I'm unable to give you any good answer. I would suggest that you put together the things we talked about (the logs, the version, etc.) and then send a mail to [email@hidden.address] then you will reach more people that can look in to this more closely12:13
Ryback_ joined12:14
Conjuro left12:14
Raydiation iveqy: thanks12:15
iveqy Raydiation: you're welcome. And please to, this is not an error we want in git...12:17
infynyxx left12:18
marhaban left12:18
bootstrapper joined12:18
marhaban joined12:19
booConjuro12:20
leo2007 left12:20
FernandoBasso joined12:22
Raydiation ok, sent the mail12:22
guampa joined12:23
cirenyc joined12:23
yshh_ left12:23
beautifulmind left12:24
marhaban left12:24
untaken joined12:24
untaken is there away to run git status without being in the directory setup on git? ie git status /some/dir/with/git/on12:25
or do we have to do `cd` first?12:25
grawity (cd /some/dir && git status)12:25
untaken k12:26
ta12:26
kmels_ joined12:26
itatitat joined12:27
bootstrapper left12:27
Raging_Hog left12:27
hyperair joined12:27
nihathrael Is there any way I can detect a subtree merge, after it has happened? Meaning by going through all the commits?12:28
jast untaken: you can do it without the subshell but it's not very convenient because you have to pass git two extra arguments12:29
eletuchy joined12:29
jast something like --work-tree=/foo/repo --git-dir=/foo/repo/.git12:29
untaken thats no worries, I'll just do the cd && ... option for now. cheers12:30
marhaban joined12:30
jast luckily the () means you end right back up where you were :)12:30
it was a few years after I started using shell script that someone told me about that12:31
Mannequin joined12:31
cirenyc left12:31
Chikore joined12:31
R1KRDO joined12:32
normanrichards joined12:32
AdrienBrault left12:32
kristofers joined12:33
Thra11 left12:34
Thra11 joined12:37
Adlai joined12:38
Adlai anybody using the alias alias?12:38
I'm having trouble getting it to work ( https://git.wiki.kernel.org/index.php/Aliases#alias )12:38
jcromartie joined12:39
eletuchy left12:39
AdrienBrault joined12:41
R1KRDO left12:41
Vile left12:42
aksnot left12:42
pandeiro joined12:42
setmeaway left12:42
otherj joined12:42
aksnot joined12:43
WinstonSmith left12:45
Vile joined12:45
Adlai My .gitconfig and the actual errosr are here: http://www.bitbin.it/q9p6o8bv12:46
jcromartie left12:46
JaredMiller joined12:47
JaredMiller left12:47
beaky joined12:47
beaky hello12:47
how do I switch from my current version of my project to an ancient one?12:47
WinstonSmith joined12:48
beaky to demonstrate what beaky's app 1.0 looks like (compared to 2.0)12:48
bob2 do you mean 'git checkout somerandomhash'12:48
beaky ah thanks12:48
jn_ left12:48
dokma|2 left12:48
Adlai beaky: there should be tags, though12:49
infynyxx joined12:49
beaky ah12:49
tags? what's that12:49
Adlai try `git tag --list' to see the available tags, and then `git checkout v1.0' or whatever12:49
beaky ah thanks12:49
hmm.. git tag --list gives nothing :( maybe i didn't put tags12:49
Adlai tags are a way of pointing to a specific commit and saying, "This is version X"12:50
they're pretty easy to use and save you the trouble of remembering old hashes afterwards12:50
beaky fortunately every discrete commit/merge in my master is one version :D how do I tag each?12:50
engla use git tag -a on each12:51
Katafalkas left12:51
beaky ah thanks12:51
Katafalkas joined12:51
Adlai beaky: you can read http://git-scm.com/book/ch2-6.html for some more info about tags12:52
mishok13 left12:52
Adlai or read the git-tag manpage, it's not that long12:52
Anders_J joined12:52
jn_ joined12:53
mishok13 joined12:53
babilen left12:53
Adlai any git wizards have comments about my issue? http://www.bitbin.it/q9p6o8bv12:53
Guest50376 joined12:54
beaky wow my git version history is now nice and neat :D thanks for teaching me tags12:54
Adlai I tried escaping the hash so git doesn't treat it as a comment, but that also gave an error12:54
beaky: you're welcome12:55
it's reassuring that I can still give git help after three years of not touching it...12:55
Adlai is just getting his feet wet again with programming12:55
NiteRain left12:55
beaky how do I diff a certain file (maybe open them side-by-side) between two different commits (like bettween version 1.0 and 2.0)? :D12:57
bob2 git help diff12:57
engla git difftool for external programs12:57
beaky ah thanks12:58
infynyxx left12:58
oposommeoposomme|away12:59
bartzy left13:00
tagava joined13:00
Adlai ok, I solved my issue and am fixing the version in the git wiki :)13:01
beaky does the it dance13:01
beaky git*13:01
Raging_Hog joined13:01
mikecmpbll left13:02
Guest50376 left13:02
RawProduce trees do the git dance the best because they branch so often13:03
tagava left13:03
DoniRS left13:04
tagava joined13:04
beaky how do I do soemthing like difftool, but open up the entire files rather than just the differences?13:04
DoniRS joined13:05
eletuchy joined13:06
Raging_Hog left13:06
rob_w left13:06
bob2 maybe you want git show13:07
ankurankan joined13:07
bob2 which git tutorial did you read?13:07
heytrav left13:07
sgambino left13:07
beaky I read from the book pro-git linked in git-scm.com13:08
Khisanth left13:09
beaky http://git-scm.com/book13:09
Khisanth joined13:09
xiangfu left13:10
Raging_Hog joined13:10
ankurankan left13:11
tagava left13:12
v0n joined13:12
cmn difftool gets the whole file, if you're not happy with your current tool, there are more available13:13
heytrav joined13:14
hellopat left13:14
eliasp left13:15
lmm joined13:15
daniel_- left13:15
Adlai fixed version at work, solving one of my pet peeves... http://www.bitbin.it/hKFgMPO113:16
lmm hi, is there an existing module/similar for offering http access to repositories with node.js?13:16
tagava joined13:16
eletuchy left13:16
itatitat left13:16
sirdancealo2 joined13:16
Khisanth left13:16
angelsl joined13:16
anonymuse joined13:18
iveqy lmm: you can reach a git-repository with http, https, ssh, git13:18
normanrichards left13:18
lmm iveqy: I want to serve my repository so that other people can access it with http13:18
the machine I want to serve it from is running node.js but not apache13:18
eijk_ left13:18
lmm it wouldn't be a huge effort to install apache on it as well and do some routing between them13:19
eijk joined13:19
lmm but I'd rather just do both the git hosting and the other stuff I'm hosting there in node.js if possible13:19
cmn unless you're willing to reimplement the git object packer, you should use git13:19
oriba joined13:19
avtobiff left13:20
lmm "use git" in what sense?13:20
Chikore left13:20
sallesao left13:20
wereHamster "I want to serve my repository so that other people can access it with http" you mean clone via http or a html repo viewer?13:21
lmm clone via http13:21
hmm, looking into it it seems the apache way of doing it is actually just webdav?13:21
wereHamster lmm: man git-http-backend13:21
gitinfo lmm: the git-http-backend manpage is available at http://jk.gs/git-http-backend.html13:21
pastime left13:22
wrouesnel joined13:22
MatthewWilkesmwilkes|away13:23
lmm ok, looks like there's a way to do cgi from node, so that will work13:23
thanks13:23
fire joined13:23
sebuba joined13:24
guampa left13:24
jast that sounds like a pretty bad idea13:25
remember that as long as the CGI doesn't finish, node can't serve any other requests13:25
Adlai left13:25
edgy joined13:26
Adlai joined13:26
iveqy jast: is node.js single threaded?13:26
cashwilliams joined13:26
jast yes13:27
it's got a pretty good event loop, but no concurrency13:27
lmm oh, point13:27
iveqy oh =(13:28
jast well, you can fork processes13:28
mikewintermute left13:28
jast but the event loop still doesn't continue until your request callback returns13:28
beaky how does git compare to the other dvcs like hg, bzr, darcs, mstfs?13:28
iveqy use nginx as a load balancer before node.js and allow multiple node.js instances to run?13:28
jast !isgitbetter :}13:28
gitinfo We think so, but if you don't, please go away and use $YourFavoriteSystem instead. For a comparison to other VCSes, see http://thkoch2001.github.com/whygitisbetter/13:28
obert joined13:28
edgy left13:28
beaky ah thans13:28
jast not sure how up-to-date that is, though13:28
lmm meh, if I was going to set up nginx in front I might as well set up apache in front instead, since I know how to make it serve git already13:29
jast basically, node.js shouldn't be used to serve anything ;P13:29
mikewintermute joined13:29
iveqy lmm: nginx is so much better than apache ;)13:29
iron_houzi joined13:30
jast depends on your requirements13:30
apache sure has more of a tendency to lock up13:30
lmm not better in a way that matters for me yet13:30
jast but perhaps that's what some people need for their applications13:30
Khisanth joined13:30
lmm I've never had it lock up, shrug13:30
jast happened to me several times last week13:30
single worker processes hung at 100% CPU usage13:30
lmm it works, I know how to use it, and I'm not in a position where performance is going to be an issue any time soon13:31
jast (no, we don't run mod_php)13:31
lmm shrug; never seen that myself13:31
cashwilliams left13:31
geekbri joined13:31
pandeiro left13:31
iron_houzi if I create branch A, then, while on branch A, I create branch B. This means that branch A has a "sub-branch" B, right? If so, what happens to branch B if I merge branch A with master?13:31
bob2 nothing at all13:32
and using terms like 'sub-branch' is just going to confuse you13:32
iveqy jast: that's why I used the ;). it depends on your needs of course. A pretty usual setup is to use nginx to load balance multiple apache servers13:32
jast there's no such thing as sub-branches13:32
haarg branches aren't based on other branches, they are based on commits13:32
Raydiation left13:32
jast B is basically a copy of A13:32
(at the point you create it)13:32
except it reuses everything, so it's more like with hardlinks13:32
haarg the branches may have the same commits in them, but that is the only relationship between the branches13:32
mikewintermute left13:33
SeoZSeoZ-work[AWAY]13:33
iron_houzi bob2: But will branch B still available and branch A be removed when it is merged into master?13:33
jast nothing is removed automatically13:33
iron_houzi OK13:33
jast if you want to get rid of a branch, you delete it. if you don't, it stays.13:34
wereHamster jast: are you sure about that? If you spawn a CGI process (fork, ..) you can write/read to its stdin/stdout without blocking node13:34
mikecmpbll joined13:34
tplaner joined13:34
iron_houzi But if I explicitly remove branch A after merging it with master, branch B will still be available and working as it should..?13:35
guampa joined13:35
BadDesign joined13:36
BadDesign left13:36
BadDesign joined13:36
bob2 of course13:36
iveqy iron_houzi: yes, afaik. Which SCM are you used to?13:36
bob2 'B' is just a pointer at a commit13:36
iron_houzi iveqy: What is an SCM?13:37
iveqy iron_houzi: source control manager13:37
skanev_ joined13:37
R1KRDO joined13:37
iron_houzi I use git from the linux command line13:37
skanev joined13:37
sunya7a joined13:37
skanev hey guys13:37
gitinfo skanev: 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.13:37
iron_houzi ..obviously a noob though13:37
iveqy iron_houzi: a branch in git is simple a pointer to a commit. Making a new branch is basically creating a small file with a sha1 in13:37
iron_houzi: oh okay. It sounded like you'd used something else before git...13:38
xeviox joined13:38
skanev I'm trying to do some esoteric here. Is there a way to have a hook that commits in a submodule in the same repo?13:38
daniel_- joined13:38
iron_houzi iveqy: no no, just learning..13:38
erichynds joined13:38
xeviox if I simply clone a svn repository using "git svn", are the branches kept in separate folders like they appear in svn?13:38
iveqy xeviox: no13:39
jast wereHamster: yes, but as long as the HTTP request handler still runs (i.e. the request hasn't ended and we haven't sent a response to the client), the event loop stays out of the loop (pardon the pun)13:39
in node.js, that is13:39
kmels__ joined13:39
wereHamster jast: wrong.13:39
xeviox iveqy: so just the "trunk" gets cloned?13:39
iveqy xeviox: I'm afraid git-svn doesn't handle svn branches very well13:39
xeviox I want to migrate from svn to git13:39
skanev I tried writing a post-commit hook, but when i add something to the submodule's repo, I get unable to create submodule-name/.git/index.lock: not a directory. However, if I run the same script directly (instead of a post-commit hook), it works13:39
xeviox to later drop svn completely13:40
wereHamster jast: I dont' think you should be giving advice about node if you don't know how it works ;)13:40
bob2 skanev, are you sure you want submodules?13:40
iveqy xeviox: I'm not fully up to date, I used git-svn latest last summer. Then you should clone trunk only, otherwise you'll end up with a git repo with all svn-branches in it13:40
skanev bob2, well, not, but they seem to be an OK idea. do you want me to tell you what I'm trying to accomplish?13:41
iveqy skanev: that's because .git in a submodule isn't a directory but a git file.13:41
skanev iveqy, sure, but why don't I get this error outside of the post-commit hook?13:41
Desproges joined13:41
guampa left13:42
diamonds joined13:42
iron_houzi So please help the noob understand something: If I am working on a feature branch (branch A) that isn't completely working yet, but good enough to start focusing on some other feature I want to start working on (branch B). Then I complete branch A and want to merge it with my other work: Do I merge branch A with master and branch B and then remove branch A. Then when branch B is complete, I merge branch B with master??13:42
kmels_ left13:42
iveqy skanev: I can't answer that I'm afraid. But start with checking if .git actually is a dir. It souldn't be13:42
littlebearz left13:42
eletuchy joined13:42
xeviox iveqy: that's what I mean, using "git svn" in the simplest way, I would end up with all branches in different folders on the created git clone, right?13:43
jast wereHamster: oh, right. it does the callback dance. never mind, then. still doesn't make me appreciate the concept. :)13:43
I retract my previous statement. CGI *can* be done sanely in node.js, for certain values of 'sane'.13:43
shwaiil joined13:43
iveqy xeviox: yes. So just to git svn clone [path]/trunk13:44
babilen joined13:44
shwaiil hello : )13:44
minusthetiger joined13:44
xeviox iveqy: thanks! :D13:44
v0n left13:44
iveqy xeviox: the svn and git branch concepts are so different it's almost impossible to keep them in sync in a good way13:44
in svn you can do a branch of a part of your tree, it's not possible with git. A branch is always your complete tree13:45
SkAzZ joined13:45
subhojit777 left13:45
SkAzZ left13:45
GodEater left13:45
xeviox iveqy: yup, I just want to be sure that a simple "git svn clone [path]" ends up with everything being cloned (and branches move to different subfolders like it appears in a svn tree)13:45
shwaiil Q: How to have a specific git config user based in the logged in user. I'm right now logged in to my VM as userX and I'm wondering if I set git config --global user if this is going to be equal to all users or just userX ?! What should I do, so that each user has its own git config user ? Tks : D13:45
SkAzZ joined13:45
GodEater joined13:45
xeviox iveqy: just wanted to be sure that it doesn't skip branches by default..13:46
iveqy: thank you!13:46
bgerber left13:46
normanrichards joined13:46
GodEater left13:46
eijk left13:46
eijk joined13:46
jcromartie joined13:47
iveqy shwaiil: --global is for all your repositories. Not for all users on the machine, you shouldn't have write access to do settings for other users13:47
at least not if you're using a unix-system13:47
shwaiil iveqy: thanks for looking! I used to work in my localmachine but I just setup a VM running linux ubuntu. I'm now working in the VM and wondering if someday I ask some help and if I need him to log to this VM or something, maybe he'll just work in his environment, I'm just confused in the moment :Z13:49
elixir_ left13:49
elixir_ joined13:49
JaredMiller joined13:50
GodEater joined13:50
pandeiro joined13:50
iveqy shwaiil: give him a different user and he will have an own enviroment13:50
DoniRS left13:50
sgambino joined13:50
bgerber joined13:50
simesy joined13:51
shwaiil iveqy: truth :) sorry for the question, just confused in the moment13:51
JaredMiller1 joined13:53
DoniRS joined13:53
eletuchy left13:53
JaredMiller left13:54
simesy left13:56
gruen0 joined13:56
gruen0 left13:56
revagomes joined13:57
beaky left13:57
AndroUser joined13:57
okar joined13:57
JaredMiller1 left13:58
ISF_ left13:58
AndroUser left13:58
trungqtran joined13:58
paulweb515_ left13:58
jn_ left13:59
rfoust left14:00
vedant joined14:00
GodEater_ joined14:00
tmcmahon joined14:01
Guest16355 joined14:03
cannonball joined14:03
GodEater_ left14:03
GodEater left14:03
GodEater joined14:04
Squarism2 left14:04
GodEater left14:04
OOPMan left14:05
avtobiff joined14:07
Cerise left14:08
sallesao joined14:08
Guest16355 left14:08
Chikore joined14:09
stewiee left14:10
Shurakai joined14:10
decotii joined14:11
rath left14:11
nihilista left14:13
paulweb515_ joined14:13
hkj left14:13
freeed joined14:13
_protagoras271_ left14:13
Raging_Hog left14:15
infynyxx joined14:15
tagava left14:15
jn_ joined14:15
gdoteof left14:16
hkj joined14:16
nihilista joined14:16
tmcmahon left14:17
jargon left14:17
maleknet joined14:18
gasbakid left14:19
eletuchy joined14:20
daniel_- left14:20
tongcx why sometimes, it's prefered to do a merge when fast-forward is default?14:21
elixir_ left14:21
macabre joined14:22
jast if you want to leave an explicit record that you added that new history, you create a real merge commit14:22
maybe to indicate that you verified/tested the new stuff14:23
tongcx jast: in terms of maintainence, is merge better?14:23
jast: maybe in future, it's easier to take the merge off?14:24
alorence left14:25
tongcx jast: sorry, what i said doesn't make sense14:26
breakingthings joined14:26
jast actually, merges are harder to "undo"14:27
because if you revert them (using 'git revert'), you can't merge that history again14:27
otherj left14:27
thl0 joined14:27
alorence joined14:27
maleknet left14:28
rfoust joined14:28
rue joined14:29
Raging_Hog joined14:30
eletuchy left14:30
lethjakman joined14:30
bluj left14:31
chimay joined14:32
mwilkes|awayMatthewWilkes14:34
aksnot left14:35
PigeonFriend joined14:35
brokenjames joined14:36
dc5ala joined14:36
vedant left14:36
ries joined14:37
fire left14:37
ries Hello! Small question, with git you cannot checkout a single file under a different revision (like in SVN) right?14:37
cmn ries: git checkout <commitish> -- <files>14:38
rbmk joined14:38
gdoteof_ joined14:38
ries cmn: Hmm interesting… I always thought it was a all or nothing..14:38
soee left14:39
cmn you're thinking about history14:39
ries cmn: is that the same for updates? Let's say I have a repo and can I checkout a single file from a specific commit?14:39
gommo left14:39
cmn what updates?14:39
marthinal left14:40
cmn what I just told you is how to checkout a file from a commit14:40
this has nothing to do with updating anything14:40
ries cmn: Let me explain a bit better… our report users commit a file to SVN under a revision.. then during deployment we checkout that specific revision of a file… I know it's a bad way of working but….14:40
cmn you can ask git for a particular commit's version of a file14:40
ries ok..14:41
cmn if you want it to stick, you can commit it14:41
gustavnils joined14:41
ries ok14:41
brian_ left14:42
msimav joined14:42
netzmonster joined14:42
Raging_Hog left14:43
jn_ left14:43
tomprince joined14:44
msimav hi all, how can i force git to ask merge message?14:44
wereHamster msimav: git merge --no-ff14:44
msimav thx wereHamster14:45
tomprince I'm using git-svn, with two remotes, and doing 'git svn fetch' appears to be grabbing the 'ignore-paths' config from the wrong config section14:45
Katafalkas left14:47
BadDesign left14:47
v0n joined14:48
tongcx if someone did a fast-forward, is there anyway to track the name down?14:50
since there is not commit created, is this info stored or lost?14:50
wereHamster 'the name'? Which name14:50
bob2 as in who did it?14:51
tongcx yes14:51
who did fastforward14:51
wereHamster no14:51
armin hi, when i do "git checkout -b spielwiesenbranch --track remotes/origin/2.0", why does git branch -a not show me a "-> remotes/origin/2.0" after the spielwiesenbranch entry in the output? git already told me that the new local branch spielwiesenbranch has been set up to track the remote one.14:51
tongcx wow, that's sad, so perfer to have a merge even if can be fastforwarded?14:52
simesy joined14:52
jast tomprince: I don't think using git-svn with multiple remotes gets a lot of love, code wise14:52
bob2 if you want a merge commit, yes14:52
wereHamster tongcx: git merge --no-ff14:52
tongcx wereHamster: great! thanks14:52
bob2 (it's not sad, it's part of the git model)14:52
huoxito joined14:52
bmac joined14:52
jast armin: 'git branch' doesn't show that info without -vv14:53
nihathrael left14:53
cashwilliams joined14:53
itatitat joined14:54
ojacobson joined14:54
msimav So is there any way to alias merge to 'merge --no-ff'? Adding it to .gitconfig affects behavior of pull which something i dont want.14:54
tongcx bob2: haha, is it possible to make --no-ff default?14:54
wereHamster msimav: make an alias?14:54
ojacobson sure: I have 'git config --global alias.ff "merge --ff-only"'14:54
jast msimav: you can create a new command, e.g.: git config --global alias.supermerge merge --no-ff14:54
ojacobson you can hack that, I'm sure14:54
philips_ left14:54
msimav well i accidently merge with 'git merge' not 'git supermerge'14:55
jast the config doesn't distinguish between 'git merge' and 'git pull', since internally git pull simply calls git merge14:55
yshh joined14:56
msimav jast, i see14:56
jast alternatively you can set merge.ff to false and use 'git pull --ff'14:56
simesy left14:56
jast setting branch.<your branch>.mergeoptions to '--ff' might take care of that for you14:57
not sure14:57
eletuchy joined14:57
tongcx msimav: you can reflog14:57
natechan joined14:57
msimav thx jast14:57
NiteRain joined14:57
tongcx msimav: and revert back to before-merge status14:57
xiangfu joined14:57
netiul left14:58
bartzy joined14:58
Parhs8 left14:58
msimav i will search about them, tongcx14:58
AnimeCYC joined14:59
jatt joined14:59
philips_ joined14:59
arietis left15:00
mtk left15:01
Goles joined15:01
quazimodo left15:02
rue left15:03
marhaban left15:04
mtk joined15:04
johnthebear joined15:04
mmitchell joined15:05
arietis joined15:05
teear left15:06
mmitchell left15:06
Esa_ joined15:06
teear joined15:06
mtk left15:06
mmitchell joined15:06
mtk joined15:07
vedant joined15:08
eletuchy left15:08
_iron joined15:08
e66 joined15:09
__Big0__ joined15:09
hellopat joined15:09
kukks joined15:10
kukks left15:10
kukks joined15:10
mtk left15:11
TeckniX joined15:12
unbounced joined15:12
bootstrapper joined15:12
CreativeEmbassy joined15:12
arvind_khadri left15:12
CreativeEmbassy can anyone help me diagnose what I'm doing wrong with subtrees?15:13
babilen left15:13
tim left15:13
tim joined15:13
CreativeEmbassy I have an open source ticketing engine15:13
at https://github.com/fracturedatlas/artfully_ose15:13
infynyxx left15:13
CreativeEmbassy it's a complete Rails engine15:13
breck7 joined15:13
CreativeEmbassy I also have a standalone Rails app at https://github.com/fracturedatlas/artfully_app15:14
santosh joined15:14
CreativeEmbassy and it adds artfully_ose as a subtree at lib/artfully_ose15:14
Pigeon|Dup joined15:15
normanrichards left15:15
CreativeEmbassy so I've been pulling the engine's changes with `git subtree push --prefix=lib/artfully_ose ose 1.1.0.rc1`15:15
breck7 left15:15
santosh How to add all untracked (just untracked) files?15:15
PigeonFriend left15:15
mtk joined15:15
CreativeEmbassy (changes that my co-workers make to the engine by itself)15:15
and likewise, pushing subtree changes with `git subtree push --prefix=lib/artfully_ose ose 1.1.0.rc1`15:15
rmichnik left15:15
Desproges left15:15
axrfnu santosh: maybe git add $( git ls-files -o )15:16
CreativeEmbassy erm, I meant pulling the engine's changes with `git subtree pull --prefix=lib/artfully_ose ose 1.1.0.rc1` earlier15:16
xeviox left15:16
beitao joined15:17
CreativeEmbassy "ose" in those examples is the remote repository for artfully_ose, of course15:17
axl_ joined15:17
guampa joined15:17
CreativeEmbassy so when I pull, I get15:17
* branch 1.1.0.rc1 -> FETCH_HEAD15:17
Already up-to-date.15:17
chrisirc joined15:17
CreativeEmbassy but if I try to push out there, I get15:18
! [rejected] c1fed7c4f4fcbc7528448247cd66540902f4719a -> 1.1.0.rc1 (non-fast-forward)15:18
how do I figure out what's going on? there's no reason why my ose subtree and the branch on the remote repo should be any different15:18
should I be merging or splitting somewhere that I'm not? am I missing something?15:18
m0viefreak joined15:19
santosh left15:19
m0viefreak left15:19
m0viefreak joined15:19
jackh joined15:19
pareidolia joined15:20
eijk_ joined15:20
pareidolia Hi all15:20
chrisgeorge joined15:20
tjbiddle joined15:21
pareidolia Can someone help me with some problems, I'm trying to do a rebase -i to squash commits15:21
bootstrapper left15:21
chrisirc Hi. How do I apply (rebase, cherry-pick) a range of commits on top of the current branch?15:21
I excplicitely don't want to rebase from a common merge base.15:21
pareidolia But these commits span over a branch merge, some googling showed me that this is a difficult case15:21
chrisirc Just "rebaseget $from $to", where $from is a (grand*)parent of $to.15:22
Pigeon|Dup left15:22
pareidolia chrisirc, me?15:22
chrisirc No, that was an extension of what I said myself.15:22
OOPMan joined15:23
gitinfo set mode: +v15:23
eijk left15:23
chuckharmston joined15:23
plasticboy joined15:23
CreativeEmbassy ah crap, I haven't had voice the entire time I've been talking15:23
chrisirc pareidolia, you might want to try my http://github.com/pflanze/cj-git-patchtool15:23
tjbiddle_ joined15:24
CreativeEmbassy I'll try to be more succinct the second time around15:24
griotspeak joined15:24
chrisirc CreativeEmbassy, "should I be merging or splitting.." was the last thing I saw15:24
cilly joined15:24
pareidolia chrisirc: I am wondering if removing the last commits without throwing away the current state would work15:24
CreativeEmbassy alright, that's where I ended15:25
PigeonFriend joined15:25
garbagecollectio joined15:26
garbagecollectio how can i merge a remote branch into a local branch15:26
neither of them are master15:26
wereHamster garbagecollectio: fetch the branch, merge it15:27
chrisirc pareidolia, typically you would rework the history while ignoring the merge, then merge again afterwards.15:27
tjbiddle left15:27
tjbiddle_tjbiddle15:27
garbagecollectio while on the local branch i want it to merge into?15:27
chrisirc pareidolia, or, if the part after the merge is depending on the merge, rework the part before, merge, rework the rest.15:27
thiago joined15:27
msimav left15:27
wereHamster garbagecollectio: yes, you are always merging into the branch you are currently on15:27
St_Marx joined15:27
garbagecollectio so git fetch <branchname>15:27
jonshea_ joined15:27
garbagecollectio git merge15:27
CreativeEmbassy anyhow, I'm getting the hint "Updates were rejected because the tip of your current branch is behind its remote counterpart. Merge the remote changes (e.g. 'git pull') before pushing again."15:27
garbagecollectio or can i just do git pull origin/branchname15:28
CreativeEmbassy but I have been `git pulling` and `git subtree pulling`15:28
wereHamster garbagecollectio: no, git fetch takes other arguments.15:28
CreativeEmbassy so I'm not sure where the difference lies, and why I can't fast-forward15:28
garbagecollectio wereHamster, can you tell me15:28
infynyxx joined15:28
jkremser left15:28
pretty_function left15:29
wereHamster garbagecollectio: yes. But the man page has it described in much better words that I could ever produce. man git-fetch15:29
gitinfo garbagecollectio: the git-fetch manpage is available at http://jk.gs/git-fetch.html15:29
jkremser joined15:29
HerrK joined15:29
CarieFisher left15:29
jonshea left15:29
jonshea_jonshea15:29
garbagecollectio git pull origin <branchname> right?15:29
wereHamster garbagecollectio: !tias15:30
gitinfo garbagecollectio: Try it and see™. You learn much more by experimentation than by asking without having even tried. If in doubt, make backups before you experiment (see !backup). http://gitolite.com/1-basic-usage/tias.html may help with git-specific TIAS.15:30
garbagecollectio lol I'm not going to try and see on a codebase15:30
pareidolia chrisirc: How about a soft reset?15:30
lethjakman left15:30
wereHamster garbagecollectio: "If in doubt, make backups before you experiment ..."15:30
garbagecollectio wereHamster, can you be a bit human and just tell me what to do15:30
vedant left15:31
chrisirc pareidolia, you can do that, yes, then commit -a, to squash everything since the reset point together.15:31
vedant joined15:31
chrisirc pareidolia, but that doesn't magically take care of the merge (properly)15:31
pareidolia chrisirc, yes, but I don't care about the other branch, it's deleted15:32
garbagecollectio Automatic merge failed; fix conflicts and then commit the result.15:32
chrisirc pareidolia, meaning, you would get the merged changes without saying what was merged, which could be confusing in the future15:32
pareidolia, ok, if nobody has the other branch, then you'll be fine.15:32
pareidolia chrisirc: It was a private "feature branch"15:32
chrisirc I think you'll be fine then.15:32
plasticboy left15:33
chrisirc Never did this myself, but from my understanding it should do what you want.15:33
FernandoBasso left15:33
pareidolia chrisirc: I think I can promote this to a "workflow thingy". I hope I won't have to do it too often though15:33
__Big0__ left15:33
Sky[x] left15:33
plasticboy joined15:33
relipse joined15:33
ThomasLocke left15:34
pareidolia chrisirc: Thanks so much for your help :)15:34
sjugge joined15:34
chrisirc Yes, may make sense; as long as you're happy to squash every feature into a single commit:)15:34
sjugge left15:34
eletuchy joined15:34
mikecmpbll left15:34
sirdancealo2 left15:34
chrisirc np15:34
rchavik left15:35
__Big0__ joined15:36
Chikore left15:36
mezner joined15:37
ries left15:37
littlebearz joined15:38
aberrant joined15:38
mezner left15:39
yshavit joined15:40
beitaotrythis15:40
normanrichards joined15:40
kswenson joined15:41
yshavit I've got a local repo of a github repo (I'm asking here because it seems like a git question, not github). A few branches have been deleted on the remote (github), but they still show up for me when I type `git branch -r --merged master`. I've done a git fetch, and a git pull. Is there a way to get these branches to go away?15:41
bootstrapper joined15:41
kevwil joined15:42
wereHamster yshavit: git remote prune ...15:44
grawity or `git fetch -p`15:44
psoo left15:44
eletuchy left15:45
yshavit wereHamster, grawity: that did the trick, thanks!15:45
Noldorin joined15:46
tjbiddle_ joined15:47
__Big0__ left15:47
pareidolia left15:48
__Big0__ joined15:49
kermit left15:49
alunduil left15:49
penguin1 joined15:50
GodEater joined15:50
tjbiddle__ joined15:50
tjbiddle left15:50
tjbiddle__tjbiddle15:50
daniel_- joined15:51
kermit joined15:51
esr joined15:52
tjbiddle_ left15:52
alunduil joined15:52
simesy joined15:52
Sigma left15:52
jrex left15:53
Destos joined15:53
cashwilliams left15:53
elixir_ joined15:53
chrisirc Is there a way to check whether the working directory is clean, while ignoring changes in subrepositories?15:54
scrape left15:54
ehsan left15:55
MB_wrk joined15:55
Thra11 left15:55
willob joined15:55
chrisirc Or at least to ignore untracked content in submodules.15:56
magnus left15:56
mnemoc joined15:56
MB_wrk Hello. So I made a branch, develop, from the master branch. And then I made a commit on the master branch. How do I rebase the develop branch on the new master branch?15:56
simesy left15:57
thiago left15:57
mnemoc hi, can I make `git ls-files -m` consider staged changes? -s/--stage has a totally different meaning ... and git state --porcelain is messy to parce when there are renames with spaces :|15:57
itatitat left15:59
jrex joined15:59
SJS joined16:00
SJS left16:00
SJS joined16:00
jaequery joined16:00
jackh left16:00
exoon joined16:00
charon mnemoc: parse git status --porcelain -z instead16:00
anabelle joined16:00
MB_wrk Welp, got it. Had to cherry pick the commit.16:00
charon mnemoc: but to answer the specific question, git diff-index16:01
flijten left16:01
j^2 joined16:02
PaulCapestany joined16:03
d2dchat joined16:03
mnemoc charon: `git diff-index --name-only -z` is exactly what I needed, thanks!16:04
nilg left16:04
hatake joined16:05
mnemoc | xargs -r0 friendly :)16:05
aksnot joined16:05
maxmanders left16:06
MB_wrk left16:07
mmu_man joined16:08
ankurankan joined16:08
Sicp joined16:08
SJS left16:09
fobban joined16:10
cbreak-work left16:10
oposomme joined16:10
oposomme left16:10
oposomme joined16:11
hyperair left16:11
cjs joined16:11
GodEater left16:11
SJS joined16:11
SJS left16:11
SJS joined16:11
eletuchy joined16:11
guillaum joined16:12
dhruvasagar joined16:12
ankurankan left16:12
marhaban joined16:13
cjs left16:13
rue joined16:14
AnimeCYC_ joined16:14
oposomme|away left16:15
green- joined16:15
rgsteele joined16:15
elixir_ left16:15
oposomme left16:16
green- i have a file that differs on two checked out copies/clones of a repos, though both working copies say they are fully up to date w/o any uncommitted or changes … any ideas on how this is possible?16:17
alorence left16:17
Noldorin left16:17
AnimeCYC left16:18
private joined16:19
jpcamara joined16:19
privateGuest6549816:19
alexbligh How do I set up a file that is not in the repo, is in .gitignore, but does NOT get cleaned by git clean -xdf. It's editor settings in this case.16:19
xiangfu left16:20
wereHamster alexbligh: don't uxe -x in git clean16:20
rue left16:20
LekeFly left16:20
xxghostxx joined16:21
_Qman left16:21
pandeiro left16:22
scrape joined16:22
eletuchy left16:22
last_chance joined16:23
rgsteele left16:23
brandonw left16:24
ehsan_ joined16:24
daniel_- left16:24
mihamina left16:24
lethjakman joined16:25
netzmonster left16:26
chuckharmston left16:27
ehsan_ left16:27
kenperkins joined16:27
madewokherd joined16:28
alexbligh left16:28
Chillance joined16:28
vedant left16:29
hwrd|work joined16:29
__Big0__ left16:29
__Big0__ joined16:30
kswenson left16:30
last_chance left16:31
aberrant left16:32
tsdh left16:34
infynyxx left16:34
runde left16:35
tjbiddle left16:35
CodeShark left16:35
ehsan_ joined16:35
Sonderblade left16:35
tjbiddle joined16:36
lb1a left16:36
ehsan_ left16:36
ejnahc left16:36
runde joined16:37
ehsan_ joined16:37
tplaner left16:37
ejnahc joined16:37
nitrix- left16:39
hyperair joined16:39
maestrojed left16:40
garbagecollectio left16:40
misster_lonely joined16:40
garbagecollectio joined16:41
bootstrapper left16:41
__Big0__ left16:41
misster_lonely left16:42
siriuz left16:42
__Big0__ joined16:42
tim left16:43
enex left16:43
enex joined16:43
siriuz joined16:44
LeMike left16:44
pppaul joined16:45
Thra11 joined16:46
b1rkh0ff left16:47
LeMike joined16:47
system64 joined16:48
eletuchy joined16:48
jatt left16:49
puchrojo left16:49
maleknet joined16:51
papegaaij left16:51
LeMike left16:52
malkomal_ joined16:52
simesy joined16:52
lavaman left16:53
dreiss joined16:53
malkomal_ left16:55
angelsl left16:55
yshavit left16:55
malkomalko joined16:56
toddWork_ left16:57
Davey joined16:57
simesy left16:57
infynyxx joined16:57
alvaro_o joined16:57
b1rkh0ff joined16:58
eletuchy left16:58
Leucaruth left16:58
elixir_ joined16:58
macrover joined16:58
Adlai left16:59
Chikore joined16:59
soypirate joined17:00
sallesao left17:01
avtobiff left17:01
Guest65498 left17:01
malkomalko left17:02
rakl joined17:02
malkomalko joined17:02
sluther joined17:02
tomprince left17:04
Goles left17:04
AdrienBrault left17:05
hkj left17:05
lucs Hmm... Is it just me, but my gitk diffs highlight (in red) lines that don't start with "-" (and they don't because they have not changed!)?17:05
juvenal joined17:06
arvind_khadri joined17:07
maxmanders joined17:07
Parhs joined17:08
Parhs left17:08
Parhs joined17:08
Cromulent joined17:09
nioncode joined17:09
tureba left17:09
bootstrapper joined17:09
jaequery left17:10
infynyxx left17:10
fRAiLtY- left17:10
lavaman joined17:11
gotwig joined17:11
gotwig how can I update my git project from origin17:11
HedgeMage gotwig: git pull origin master (assuming master is the branch you are pulling to)17:12
cdeszaq_ left17:12
cdeszaq joined17:12
hiroyuki_ joined17:12
skanev_ left17:13
rmichnik joined17:13
gotwig HedgeMage: when I do that, whats next?17:13
HedgeMage: how can I remove obsolote, old files which are not part of the current trunk?17:13
HedgeMage gotwig: if they are files tracked by git, and they were deleted with "git rm" git will do that for you17:13
gotwig: if they are untracked files you must remove them manually17:14
gotwig HedgeMage: so that pull thing overwrote my old files?17:14
charon HedgeMage: !pull417:15
gitinfo HedgeMage: [!fetchfour] Never use the four-word version of git-fetch or git-pull (e.g. git fetch <remote> <refspec>). It always ends in tears. Yes, if you understand the implications of FETCH_HEAD it can technically be done, but really it is easier to just fetch the whole remote (or perhaps edit the fetchspec if you never want other bits). If you must, see !fetch4why17:15
charon gotwig: !pull17:15
gitinfo gotwig: pull=fetch+merge (or with flags/config also fetch+rebase). It is thus *not* the opposite of push in any sense. A good article that explains the difference between fetch and pull: http://longair.net/blog/2009/04/16/git-fetch-and-merge/17:15
bootstrapper left17:15
gotwig oh17:15
great17:15
I understand it now17:15
throstur joined17:15
gotwig ( I guess )17:15
tureba joined17:15
charon it's really less a matter of overwriting than of git *updating* the worktree to match what you merged.17:16
throstur hey guys, I made a big boo-boo when creating a git repo, I meant to only add 1 file but I have a whole folder instead17:16
mikef joined17:16
throstur how can I remove all files except that one file so that when I push/pull that the .o files and such don't get synced?17:16
wereHamster throstur: git reset; git add <dat file>17:16
hiroyuki left17:16
throstur thanks wereHamster17:16
maleknet left17:16
mikewintermute joined17:16
charon gotwig: and it is very careful. if that update ran the risk of actually destroying *uncommitted* work, it would abort. it's still better if you don't merge with uncommitted work, however.17:16
nitrix joined17:17
gotwig nothing to commit (working directory clean) ;P17:17
bauruine left17:17
Goles joined17:18
lucs Spurious red: http://scullucs.com/Selection_004.png17:18
maletor joined17:19
sq-one joined17:19
lucs Anyone else get things like that from gitk?17:19
bryanstedman joined17:19
Adlai joined17:20
SonikBoom joined17:20
charon lucs: if you have a simple reproducer, send it to the list -- the Tk dinosaurs will have a look at it17:20
aberrant joined17:20
itatitat joined17:21
Vinnie_win left17:21
lucs charon: Hmm... Dunno if I can build a simple example that will reproduce the problem.17:22
If it drives me nuts, I'll give it a shot :)17:22
charon lucs: well, you could start by making a repo that contains only the pre- and postimage of this file in two successive commits17:22
then see if that reproduces17:22
that would be simple enough in my book ;)17:23
lucs I'm not sure I understand what you mean. A repo holding two PNGs?17:23
charon err no17:24
Vinnie_win joined17:24
charon pre/postimage is just the terminology for before/after sides of a diff17:24
gregorio joined17:24
lucs Ah, I see.17:24
I could try that.17:24
eletuchy joined17:24
francisfish left17:25
gregorio left17:25
mikewintermute left17:27
jceb left17:27
tPl0ch left17:27
gasbakid joined17:28
daniel_- joined17:29
thiago joined17:30
jn_ joined17:31
jaequery joined17:31
bootstrapper joined17:32
brocken left17:32
itatitat left17:34
eletuchy left17:34
tjbiddle left17:35
dreiss left17:35
babilen joined17:35
trungqtran left17:36
tagava joined17:37
gotwig left17:37
esr left17:37
mikef left17:38
chuckharmston joined17:38
griotspeak left17:38
gasbakid left17:38
macrover left17:38
boucman_work left17:39
rurufufuss left17:40
alainus[-_-]alainus17:41
sallesao joined17:42
avtobiff joined17:42
thierryp_ left17:42
chuckharmston left17:43
mishok13 left17:45
o-O-o joined17:45
elixir_ left17:47
sq-one left17:47
splud joined17:47
elixir_ joined17:47
elixir_ left17:47
rue joined17:48
Sicp left17:49
dc5ala left17:49
gittish joined17:49
marthinal joined17:50
sunya7a left17:51
skanev_ joined17:52
bgerber left17:52
scorphus joined17:52
mmu_man left17:52
Thra11_ joined17:52
boombatower joined17:53
simesy joined17:53
axl_ is it very hard to set up a git repository within the branch of another git repository?17:53
alexim joined17:53
gasbakid joined17:54
Thra11 left17:54
axl_ ( i want to ignore a branch in the parent repository and make it its own repository)17:54
skanev_ left17:54
goshawk joined17:54
brandonw joined17:55
gotwig joined17:55
HedgeMage axl_: I think what you are trying to get at is a git submodule -- throw that phrase in your favorite search engine and watch the documentation fly :)17:55
riskable left17:55
axl_ awesome. thanks that should get me going17:56
bgerber joined17:56
etcetera joined17:56
juril joined17:56
etcetera left17:56
HedgeMage axl_: No problem. :)17:56
LekeFly joined17:57
suy left17:57
simesy left17:57
eletuchy joined18:00
drizzd joined18:00
Cromulent left18:00
hkj joined18:01
relipse left18:01
madewokherd left18:01
Sigma joined18:02
maxmanders left18:02
kiffer84 joined18:03
ferdev left18:03
engla left18:03
engla joined18:04
skanev_ joined18:05
wasanzy left18:05
obert left18:06
dharrigan left18:07
dev2 left18:08
eletuchy left18:08
guy joined18:09
guy if I have uncommitted changes, what will happen when I do git checkout -b foo?18:09
breakingthings left18:09
guy will these be moved to a new branch?18:09
bmac left18:10
haarg they will stay in your working tree18:10
grawity technically they don't belong to any branch yet, so there's nothing to move18:10
skanev__ joined18:10
Saby joined18:10
Saby left18:10
Saby joined18:10
grawity `git checkout -b` will just create a new branch, won't touch uncommitted changes.18:10
OOPMan left18:10
guy great.18:10
afflicto-laptop joined18:11
chrisgeorge_ joined18:11
setmeaway joined18:11
chrisgeorge left18:12
chrisgeorge_chrisgeorge18:12
tvw left18:13
Steelsouls joined18:13
sunya7a joined18:13
skanev_ left18:14
cworth joined18:14
skanev__ left18:14
hwrd|work left18:14
ttz quick question, does OpenSMTPD support a recipient delimiter, to do plus addressing18:15
macrover joined18:15
EugeneKay Not a clue. Try #opensmtpd18:15
frenchlaf joined18:15
Chikore left18:16
taylorlapeyre joined18:17
hwrd|work joined18:17
mikef joined18:17
bgerber left18:18
huoxito left18:19
bgerber joined18:19
m0ltar joined18:20
hwrd|work left18:20
sfalcon joined18:21
cworth left18:21
PaulCapestany left18:22
dreiss joined18:22
tjbiddle joined18:22
chimay left18:22
cashwilliams joined18:22
jaseemabid joined18:25
dmarkham_ joined18:25
opus joined18:26
arvind_khadri left18:26
MatthewWilkesmwilkes|away18:26
LekeFly left18:26
cworth joined18:27
mihamina joined18:28
o-O-o grawity: so you can start cracking your code and by the time you realize you'd need to commit it into a new branch, you just create it and commit? :)18:28
_ikke_ o-O-o: correct18:28
o-O-o so much better than svn...18:28
rfoust left18:28
cashwilliams left18:29
jdunck joined18:29
duosrx left18:29
sunya7a left18:30
cmn nope18:30
you can do the same with svn18:30
rath joined18:30
sunya7a joined18:30
johnkw joined18:31
trungqtran joined18:31
chuckf left18:32
trungqtran left18:34
Sonderblade joined18:34
Sonderblade left18:34
mwilkes|awayMatthewWilkes18:34
Sonderblade joined18:34
eletuchy joined18:35
maestrojed joined18:35
system64 left18:35
dougsland left18:36
johnkw wonders why there's a git "--staged" but a git "--keep-index" referring to the same thing18:36
EugeneKay !why18:36
gitinfo Why? Because screw you, that's why.18:36
cmn because that's what the authors wrote18:36
MatthewWilkesmwilkes|away18:36
milki !wry18:36
darn18:36
johnkw insightful18:36
_ikke_ Because junio accepted the patch that added the argument18:36
grawity because "index" and "staging area" are aliases, I thought18:37
jcromartie left18:37
EugeneKay When looking at git's architecture you have to remember that it is proof of evolution, not intelligent design18:38
johnkw several web pages use them interchangeably18:38
Damgaard left18:38
EugeneKay Because who the hell would have designed git-checkout18:38
cmn hear hear18:38
esc EugeneKay: yeah, wtf is that all about18:38
EugeneKay Design by mailing list ;-)18:38
esc there is even a git stage alias for git add now18:38
Sigma left18:39
engla it's been thought for a long time that stage is the better term to use18:39
but we're stuck less than half way there18:39
esc git diff still even has a --cached option18:39
EugeneKay I hope that git 3.0 gets a fresh set of porcelain, in addition to SHA3 et al18:39
_ikke_ EugeneKay: Where is git 2?18:39
john2496 joined18:39
Damgaard joined18:39
EugeneKay Hiing18:40
Hiding18:40
grawity heh, at least there's no "dircache" anymore18:40
esc Git 3.0 will be based on libgit2 and have a porcelain in python18:40
grawity I sincerely hope you are joking.18:40
EugeneKay And lasers18:40
bremner and sharks18:40
_ikke_ and bears18:40
esc yeah, and cow super-powers18:40
grawity and LASER COWS18:40
EugeneKay I sincerely hope he isn't - libgit2 is the only sane git API I've found :v18:40
alainus left18:40
mikehaas763 joined18:41
grawity no, git 3.0 will be a renamed bzr with its git plugin18:41
johnkw boggles at "--cached"18:41
QaDeS left18:41
skanev_ joined18:41
vad You left out git 2.018:41
grawity johnkw: git used to be called "dircache" long long ago18:41
johnkw resolves to always type `git stage` from now on, for improved clarity18:41
skanev__ joined18:41
EugeneKay vad - go look at the logic behind linux 3.0 and you'll get the joke18:41
ferdev joined18:42
esc i think using the python library argparse, or optrions.py (from bup) one could make a real solid CLI18:42
eletuchy left18:43
EugeneKay Now you're trying to make me vomit18:43
esc EugeneKay: ;p18:43
grawity I avoid hg primarily because python takes so long to load from disk18:43
Sonderblade how can you take the last commit from the master branch and "move" it to a feature branch?18:43
cmn that doesn't make much sense18:43
grawity Sonderblade: including all previous commits?18:44
cmn Sonderblade: cherry-pick most likely18:44
esc Sonderblade: man git cherry-pick18:44
gitinfo Sonderblade: the git-cherry-pick manpage is available at http://jk.gs/git-cherry-pick.html18:44
EugeneKay Sonderblade - many git-cherry-pick18:44
cmn depends on what you mean by modve18:44
EugeneKay Damn, beaten18:44
esc hehe :)18:44
HerrK left18:44
esc EugeneKay: what would you use to write the cli?18:44
_ikke_ assembly18:45
Sonderblade grawity: no just 1 commit18:45
EugeneKay esc - in all seriousness, Python is probably pretty good. But I've used it just enough to know when to emulate an ostrich18:45
skanev_ left18:46
_riz_ So, I'm hearing from elsewhere that it's considered a Bad Thing to have commits on the same branch in two different repos in git18:46
a) is this true and b) if so, dubyateeeff?18:46
EugeneKay Huh?18:46
esc EugeneKay: ok18:47
skanev__ left18:47
cmn that sentence doesn't say much18:47
EugeneKay That doesn't even make sense _riz_. If they're the same history then it's the same commit, so.... what's the problem?18:47
cmn having branches in multiple repos is how you work18:47
sq-one joined18:47
gittish left18:47
B|aster joined18:48
guy left18:48
B|aster hey has anyone seen this error... error: inflate: data stream error (invalid distance too far back) fatal: object 33f1c034c308b29eb6ee48c0fc6654ae7d471c00 is corrupted18:48
_riz_ I haven't gotten details18:48
B|aster it's happening when I run git clone18:48
grawity _riz_: please get them18:48
tmcmahon joined18:48
milki B|aster: sounds like something is corrupted18:48
grawity B|aster: cloning from which repository?18:48
skanev_ joined18:48
B|aster on my one machine I did a git clone --bare repo repo.git18:49
cmn B|aster: is that a local error? does it have remote: as a prefix?18:49
B|aster then uploaded repo.git to my other server and did a git clone repo.git18:49
normanrichards left18:49
B|aster yes its local18:49
grawity run `git fsck` in all three18:49
oriba_ joined18:49
wrouesnel left18:49
_riz_ grawity: trying to. I want to make sure that when I dislike git, it's for all the right reasons ;)18:49
shwaiil left18:49
chuckharmston joined18:50
mwilkes|awayMatthewWilkes18:50
alainus joined18:50
cmn if someone says that sentence, you can feel free to ignore them18:50
_riz_ all I have so far is "and apparently if you commit on the same branch in two different repos, the commits clobber each other in some crazy way instead of just needing to be merged"18:50
cmn right, ignore it18:50
unreal left18:51
grawity sounds like someone just tried git once, had a bad merge trip, and said "never again!"18:51
cmn and use !book to get to know git instead18:51
gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable18:51
_riz_ I would if it wasn't from someone who I respect a lot in other areas18:51
the main problem I have with git his how horribly bad the "user interface" is18:51
grawity that's true18:51
obert joined18:51
grawity but do they have a practical example for the merge problem?18:52
_ikke_ _riz_: If you repeat that often enough, you are going to believe it18:52
_riz_ s/his/is/18:52
o-O-o lolz18:52
milki riz wants a gui?18:52
oriba left18:52
_riz_ milki: no, just a sane command line interface18:52
milki its not sane?18:52
_ikke_ _riz_: It's not that bad18:52
TheJH so what's insane about git's command line interface?18:53
grawity heh, we just had this discussion half an hour ago18:53
_riz_ no, it is definitely not. certainly not compared to monotone or mercurial18:53
cmn don't assume it's some other VCS with a different prefix18:53
johnkw index/cache/stage naming is insane, for the record18:53
cmn they're different things18:53
they have different UIs18:53
exoon left18:53
grawity EugeneKay was right about `git checkout` being ... poor18:53
cmn johnw: yes, we know you don't like it18:53
_ikke_ johnkw: Who cares18:54
MatthewWilkesmwilkes|away18:54
johnkw I don't have strong feelings about it one way or the other - just objectively pointing out that it's insane18:54
TheJH asked - shrug18:54
milki some objective perspective you have18:54
_ikke_ All three terms describe a way the index is used18:54
_riz_ I love how defensive people get when you suggest that their pet isn't perfect.18:55
skanev_ left18:55
_ikke_ _riz_: I'm not saying git is perfect18:55
_riz_: But people tend to bash git for the sake of it18:55
johnkw TheJH asked what's insane - I gave an example of insanity - it wasn't bashing for the sake of it18:56
unreal joined18:56
IntricateRuin left18:57
ttz left18:58
_ikke_ And with every release the interface of git gets a bit better18:58
engla at the same time it adds more flags and options18:58
I don't have a good grasp of all pushing and remote and branch defaults options even18:58
_riz_ Mostly, I'm just frustrated that none of the other tools gained the popularity git has. *any* of them would be preferable to me.18:59
cashwilliams joined18:59
_riz_ (the distributed vcses)18:59
Davey left18:59
johnkw bah. you can never have too many flags or options. http://2.bp.blogspot.com/_sSz4SqR6_10/SnNTm2QlDWI/AAAAAAAAGeU/GzFHVvYHL4I/s400/more+flags+more+fun.jpg18:59
cmn !refund18:59
gitinfo If you are not satisfied with git, or the support provided by the volunteers in #git, you are entitled to a full refund of the purchase price, and are invited to use another VCS. Elsewhere.18:59
looper joined19:00
Adlai my daddy always said that free advice was worth what you paid for19:00
_riz_ cmn: thanks, love the attitude. _Very_ helpful.19:00
cmn the attitude is that if all you want to do is badmouth git, you can go somewhere else19:00
sirdancealo2 joined19:00
hwrd|work joined19:01
kevwil_ joined19:01
jason237 left19:01
engla ...19:01
_riz_ there's that defensive attitude again.19:01
initself joined19:01
cilly left19:02
initself what command gets me changes made to an individual file over time?19:02
grawity initself: git log $file19:02
kevwil left19:02
duosrx joined19:02
initself is there anything that actually shows me the source code changes?19:02
grawity initself: git log -p $file19:02
_ikke_ _riz_: Maybe that's because git does have something that is usefull :)19:02
initself grawity++19:02
grawity _riz_: personally, I use git because it gives me control over everything19:03
valtih joined19:03
Adlai initself: try also blame19:03
alexim left19:03
grawity _riz_: it does not tell me "thou shalt not remove a commit" or "this functionality comes as a year-old extension" or things like that19:03
_ikke_ When I have to use mercurial, I find it very limiting in what it can do19:03
dorkmafia joined19:03
tmcmahon left19:03
Adlai initself: in other words, `git blame file'19:04
grawity `tig blame file` is more colourful19:04
valtih in windows, I am getting "could not readlink, 'this_file' is not a directory" for symlinks19:04
Adlai grawity: tig?19:04
valtih how do I git a symlink in Windows?19:04
cmn you don't19:04
initself Adlai: cool thanks19:05
Khisanth left19:05
grawity Adlai: tig19:05
http://i.imgur.com/GSRWQ3l.png – blame on the left, history on the right19:05
that's the second largest reason why I stick with git :D19:05
hwrd|work left19:05
_ikke_ _riz_: What git lacks in interface, it makes up in flexibility and control19:06
valtih I read that git and windows support symlinks. Why do I get "could not readlink, 'this_file' is not a directory" for symlinks?19:06
oposomme joined19:06
cashwilliams left19:07
pr0ton joined19:07
relipse joined19:07
alexim joined19:07
grawity msysgit or cygwin git, and Windows symlinks or Cygwin symlinks?19:07
Noldorin joined19:07
Adlai I see what you did there grawity and I like it19:07
tinti_ joined19:07
trungqtran joined19:07
grawity Adlai: the best part is jumping directly to the commit from blame view, or split history/commit view19:08
eletuchy joined19:09
cmn valtih: Windows has something not quite like symlinks, which git doesn't record19:09
guillaum left19:09
_riz_ _ikke_ like not being able to have multiple heads on a branch?19:10
hwrd|work joined19:10
_riz_ So, I just did my test19:10
_ikke_ _riz_: That's a mercurialism19:10
_riz_ maybe I'm doing something wrong and folks can correct me19:10
no19:10
it's not19:10
cmn that's not how you do things19:10
if it's worth keeping, you name it19:10
otherwise, you throw it away19:10
_ikke_ _riz_: What do you want to achieve with "multiple heads on the same branch"19:10
_riz_ ah, there's that vaunted "flexibility"19:10
cmn mercurial branch != git branch19:10
grawity cmn: It does have symlinks now.19:11
_riz_ for example, I just created a test repo19:11
cmn now?19:11
_riz_ one file19:11
oposomme left19:11
_riz_ "foo", containing "bar"19:11
grawity in git, a branch *is* a head19:11
_riz_ cloned it to another machine19:11
cmn _riz_: git branch is a hg bookmark, roughly19:11
_riz_ changed that file on both machines19:11
valtih cmn: people get massive downvotes at stackoverflow for what you are saying http://stackoverflow.com/a/46891/108370419:11
_riz_ now, how do I sync that? :)19:12
_ikke_ define sync19:12
_riz_ it *should* just be a merge19:12
cmn valtih: and I care?19:12
_riz_ get the changes over and reconcile them19:12
_ikke_ _riz_: You can *just* merge it19:12
cmn _riz_: sync doesn't exist, say what you want to do19:12
then fetch and merge19:12
grawity _riz_: if you *modified* that line on both repos, how is git supposed to reconcile conflicting changes like that?19:13
valtih cmn: I see that you do not care. I with people who do not care keep silence.19:13
cmn valtih: that post has absolutely nothing to do with what we're talking about19:13
I know about Windows links19:13
this has less than zero to do with shortcuts19:13
_ikke_ _riz_: like grawity said, in git, a branch is a head. So you merge them by merging branches19:14
_riz_ grawity: by having two heads. or branches. or whatever.19:14
grawity cmn: I'm not talking about shortcuts. I'm not talking about junctions. I'm saying that Windows has actual Unix-style symlinks starting with Vista on 7.19:14
_riz_: how is that a merge if the changes remain completely separate?19:14
_ikke_ _riz_: git namespaces branches19:14
cmn grawity: nobody said anything about shortcuts19:15
skanev_ joined19:15
_ikke_ _riz_: if you fetch from a repo called origin, git prefixes the branchnames with origin/19:15
duosrx left19:15
_ikke_ _riz_: so if you fetch master from origin, the branch you just fetched is called origin/master19:15
tongcx left19:15
Katafalkas joined19:15
_ikke_ _riz_: So if you want to merge it, you do git merge origin/master while on the master branch19:15
bootstrapper left19:16
_riz_ and that's where "horrible user interface" comes in, with messages like19:16
"fatal: 'merge' is not possible because you have unmerged files."19:16
eletuchy left19:16
bootstrapper joined19:17
valtih Is there a Windows 7 client that supports symlinks?19:17
_ikke_ _riz_: Well, if git would merge those files, you'd loose changes19:17
Vile left19:17
_ikke_ _riz_: That would be a good interface...19:17
elixir joined19:17
mloskot joined19:17
cmn _ikke_: in fairness, it should shout telling you you're in the middle of a merge19:17
_riz_ I don't want git to auto-merge anything. I want it to behave rationally.19:18
etcetera joined19:18
_riz_ I can then edit the file and commit19:18
cmn that sentence makes no sense19:18
git merges whenever you ask it to, only19:18
_riz_ but attempting to push gets me another horribly cryptic error19:18
_ikke_ _riz_: note that mercurial pull == git fetch19:18
Element9 left19:18
_riz_ yes, I get that19:18
thl0 left19:19
fisted joined19:19
etcetera left19:19
sunya7a left19:19
_ikke_ _riz_: Probably because you are pushing to a non-bare repository19:19
_riz_ for such a simple (and common) case, resolving this is exceedingly complex.19:19
thl0 joined19:19
o-O-o what is the difference between fetch and pull?19:19
dougsland joined19:19
_riz_ *THAT* is what I mean by "horrible user interface"19:20
o-O-o I always use pull19:20
_ikke_ o-O-o: pull = fetch + merge19:20
rcu joined19:20
o-O-o and fetch does that, exactly?19:20
and fetch does what, exactly?19:20
_riz_ (that, and things like "fetch" and "pull" have slightly different semantics)19:20
_ikke_ o-O-o: get history from another reposity19:20
Adlai o-O-o: downloads the objects from another repository19:20
_riz_ anyway, I'll stop now.19:20
o-O-o why you don't want to merge after a fetch?19:20
Adlai o-O-o: but it just downloads them to the git database, without updating your working tree19:21
o-O-o Adlai: I understand. Now tell me a reason for doing that19:21
please19:21
_riz_ o-O-o: because you want to be able to see and manipulate the changes, without being required to edit anything immediately?19:21
jkremser left19:21
etcetera joined19:21
o-O-o _riz_: that is for resolving conflicts?19:22
rmichnik left19:22
cilly joined19:22
dhruvasagar left19:22
_riz_ it can be. Of course, I've already demonstrated that I don't necessarily understand or agree with the assumptions made by the "designers"19:22
madewokherd joined19:22
cmn there is no such animal19:22
sunya7a joined19:22
cmn if you think you can make it better, make it better19:23
elixir left19:23
o-O-o if I do a fetch, but I go to sleep. when I wake up, I do a second fetch and there is new content available from remote repo. what happens?19:23
cmn it's get fetched19:23
PerlJam o-O-o: nothing important.19:24
cmn that's all that ever happens when you fetch19:24
PerlJam :-)19:24
o-O-o so I can just ignore my first fetch and I still can merge my local data with 2nd fetch?19:24
fisted left19:24
fisted joined19:24
cmn you merge with whatever you think you should merge19:25
Khisanth joined19:25
lethjakman left19:25
cmn if it's what you get the second day, then merge with that19:25
rmichnik joined19:25
o-O-o cmn: so having a daemon that does autofetching can be good?19:25
_protagoras271_ joined19:25
cmn unlikely19:25
o-O-o I can just decide to merge whenever I want19:25
cmn: why? It can run while I am sleeping19:26
dougsland left19:26
cmn but why is that so important to have?19:26
_ikke_ o-O-o: It's not like it's going to take all night19:26
o-O-o and when I wake up, I will have everything in my devbox19:26
_ikke_ o-O-o: or when you wake up, you do git fetch19:26
cmn but whta's "everything" do you continuously merge?19:26
_riz_ o-O-o: it is a very sane and normal way to want to work, yes.19:26
cilly left19:26
rue left19:26
cmn do you work on 50 branches all at once or what?19:26
o-O-o _ikke_: but that can take a long time that can be saved at night :)19:26
rue joined19:26
o-O-o cmn: we have A LOT of developers here19:26
_ikke_ o-O-o: 15 seconds19:26
cmn but why is the number of devs relevant?19:27
mihamina left19:27
cmn you're working on your thing19:27
o-O-o cmn: usually each one works in a separate feature and feature branches are poping around19:27
apok joined19:27
o-O-o cmn: or not19:27
cmn right, but why do you have to keep so up to date with every single one?19:27
_ikke_ o-O-o: It's not going to take on hour to fetch the changes or something19:27
kadoban_ joined19:28
o-O-o cmn: I can't answer with details and I don't think that is relevant since I am just asking how git works19:28
_riz_ failure of imagination. It absolutely can take that long with large repos.19:28
danishkhan joined19:28
o-O-o yup19:28
cmn yes, so?19:28
_riz_ ok I really need to leave before I become impolite.19:29
_riz_ left19:29
cmn o-O-o: and I'm telling you that you don't need to get every single thing all the time19:29
o-O-o why?19:29
cmn that's how git works19:29
_ikke_ o-O-o: distributed development19:29
o-O-o do you know what is my job role?19:29
cmn because you're working on your thing19:29
o-O-o or where are the repos?19:29
fisted left19:29
o-O-o because you ASSUMED19:29
cmn and I supposed to guess?19:29
fisted joined19:29
o-O-o don't guess and don't make assumptions either, please19:29
cmn o-O-o: I'm telling you how development with git works, which is what you're asking19:29
danishkhan left19:29
o-O-o cmn: you are telling about what I need19:30
tongcx joined19:30
o-O-o that is irrelevant and pedantic19:30
cmn then what do you want to know?19:30
because I'm answering the issue you just said you wanted answered19:30
_ikke_ The question started with why you wanted to merge19:30
o-O-o my issue was solved, you gave me the OK to fetch a lot19:30
yes19:30
gotwig left19:30
_ikke_ You want to merge because you have diverged history19:30
cmn o-O-o: either say what you're actually trying to achieve or don't complain that we assume you're a developer19:31
rakl left19:31
Praise left19:32
danishkhan joined19:32
LekeFly joined19:32
xxghostxx left19:32
rakl joined19:33
Praise joined19:33
o-O-o cmn: whatever19:33
Davey joined19:33
Khisanth left19:34
fisted left19:34
cmn indeed19:34
fisted joined19:34
madewokherd I think it's a good policy to answer the question that was asked, and if you think it was the wrong question you can explain further19:35
then you can be helpful without making assumptions19:35
vdv joined19:35
Noldorin left19:36
bremner _I_ think it's a good policy to be nice to the people donating time to help you.19:36
PerlJam Postel's Law is a good policy too :)19:36
relipse left19:36
tongcx left19:36
elixir joined19:37
tagava|2 joined19:37
jcromartie joined19:37
aweorit joined19:37
bootstrapper left19:37
cworth left19:38
johnkw yuck. postel's law leads to the nightmare that is modern html rendering.19:38
axl_ left19:38
aweorit does git accept things like *.(a|b|c) in gitignore/gitattributes?19:39
_ikke_ No19:39
tagava left19:39
wereHamster aweorit: man fnmatch, that's what git uses19:40
cmn the next release will also support wildmatch, for some reasobn19:40
Goles left19:41
Xethron left19:42
kcj joined19:42
cworth joined19:42
whowantstolivef1 joined19:43
madewokherd bremner: sure, but I can understand the frustration when you ask a question and just get answers to irrelevant questions you didn't ask (or you got the answer to the wrong question and someone knew a better one but didn't tell you)19:43
eletuchy joined19:43
primitive joined19:43
skanev_ left19:43
skanev_ joined19:44
tagava joined19:44
skanev_ left19:44
tagava|2 left19:44
cmn then you need to say why it's not going in the right direction19:46
not get offended because someone is explaining the typical way to use git when you're a developer, which is what you get here19:46
PerlJam This is all normal communication difficulty anywya19:46
breakingthings joined19:47
PerlJam I tend to ask my qife very precise questions (in the hope that I'll get an answer), but most times I have to ask the question 2 or 3 times to get an answer.19:47
sirdancealo2 left19:47
Davey left19:47
PerlJam But, from her perspective, she was answering me.19:47
teear left19:48
PaulCapestany joined19:48
siriuz left19:48
skanev_ joined19:49
tagava left19:49
valtih Is there a Windows 7 client that supports symlinks?19:50
tagava joined19:50
infynyxx joined19:50
eletuchy left19:50
siriuz joined19:51
ThePawnBreak joined19:51
pr0ton left19:51
danillonunes joined19:52
geekbri left19:52
teear joined19:53
simesy joined19:53
longbeach left19:54
cbreak|evil left19:56
cashwilliams joined19:56
Samual joined19:57
cbreak joined19:57
grizwako joined19:57
gotwig joined19:57
jjore joined19:58
simesy left19:58
Khisanth joined19:58
Noldorin joined19:58
ThePawnBreak left19:59
elixir left20:00
rvl joined20:02
danillonunes left20:02
revele left20:03
opus left20:03
throstur left20:03
tvw joined20:03
etcetera left20:04
sunya7a left20:04
elixir joined20:04
jwmann left20:05
skanev_ left20:05
taylorlapeyre left20:06
opus joined20:06
jpcamara left20:07
lacrymology joined20:07
mirkgeo joined20:07
maxmanders joined20:08
jwmann joined20:08
elixir left20:08
sunya7a joined20:10
rmichnik left20:10
Vile joined20:11
bootstrapper joined20:11
opus left20:11
gitinfo set mode: +v20:11
mirkgeo hello20:11
gitinfo mirkgeo: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.20:11
ErKa joined20:11
grizwako left20:12
nicoulaj joined20:12
grizwako joined20:13
infynyxx left20:13
mirkgeo If I'm going to create a whitelabel version of a product, what would be the best way to do that? just create a new branch?20:13
jcromartie left20:14
webczat joined20:14
milki whats a whitelabel?20:15
avtobiff left20:15
vad different color than a pink label20:15
grizwako left20:15
zealiod joined20:16
CreativeEmbassy left20:16
sallesao left20:16
mirkgeo milki: almost the same functionality but another brand.20:16
zealiod Is it possible to have a origin that is local rather than remote - and how do I set this up?20:16
ThePawnBreak joined20:16
vad zealiod: remotes can point to anywhere20:16
DoniRS left20:17
chuckharmston left20:17
eletuchy joined20:17
zealiod vad: So, a the mo I have "git remote add origin [email@hidden.address] - that is the address of the repo - but it's local to me, how could I reference it locally instead rather than looping in?20:18
afflicto-laptop left20:18
HardDisk_WP left20:18
LekeFly left20:19
valtih left20:20
tjbiddle_ joined20:20
jn_ left20:20
tjbiddle left20:20
tjbiddle_tjbiddle20:20
cenuij left20:21
oakdog8 joined20:21
leehambley joined20:22
boombatower left20:22
cmn you give git a path20:23
TriRas joined20:23
lethjakman joined20:23
LekeFly joined20:23
nkr left20:24
relipse joined20:24
cmn but be aware that doing it via the filesytem goes around gitlite's hooks, IIRC you make it unhappy if you try to push afterwards20:24
webczat left20:25
eletuchy left20:25
cashwilliams left20:25
rakl left20:25
mirkgeo We want have the possibility to merge in bugfixes to the main product20:26
Adlai mirkgeo: you can always cherry-pick commits back and forth20:26
aweorit left20:26
Adlai or rebase feature branches20:26
CreativeEmbassy joined20:26
jcromartie joined20:27
mirkgeo Adlai: cherry-pick was the first idea. I just thought if there maybe is some other ways to do it? A separate repo would be a bad idea?20:27
pantsman joined20:27
pantsman left20:27
pantsman joined20:27
bootstrapper left20:27
alexim left20:28
AnimeCYC joined20:28
Adlai mirkgeo: I'd say two "parallel" branches in the same repo20:28
cmn a repo is where you store your branches; using different repos is about separating who has access to what20:28
rakl joined20:28
cmn having one repo or two doesn't affect how you work much20:28
Adlai mirkgeo: you'd do most development on one version, and then just merge stuff periodically into the other branch20:29
HardDisk_WP joined20:29
HardDisk_WP left20:29
HardDisk_WP joined20:29
bootstrapper joined20:29
mirkgeo Adlai: Okok! Right now there is one dev and one master for the base product. I think the best would be to have the same for this separate version, one dev and one master?20:29
cmn that's bound to get confusing, as they're the same project, just slightly different versions20:30
Adlai mirkgeo: no, I think there should be three branches: dev, master, and whitelabel20:30
development takes place on dev, and then when there are releases, dev gets merged into master and whitelabel20:30
(seperately to each one)20:30
mirkgeo Hm20:31
Adlai that way, you get all the features and fixes into each release branch, without contaminating between them20:31
fobban left20:31
mirkgeo But dev for whitelabel and original will always be different20:31
AnimeCYC_ left20:31
tplaner joined20:31
mwilkes|awayMatthewWilkes20:31
juvenal left20:32
alexim joined20:32
Adlai mirkgeo: why? how big is the difference between them?20:32
if you need to make something just for whitelabel, you can have a temporary "dev-white" branch for that20:33
mirkgeo Adlai: much, the functionality will be almost the same but a bit scaled in whitelabel. But the UI would be totally different20:33
mishok13 joined20:33
Adlai but you should do as much dev as possible on one dev branch20:33
danishkhan left20:34
pr0ton joined20:34
Saby left20:34
Adlai otherwise you'll just have a history that's full of extraneous merges20:34
relipse left20:34
cmn if the UI is going to be completely different, it could be easier to have that as a compile/deploy option, rather than make a different branch20:35
longbeach joined20:35
mirkgeo Adlai: yeah, bugfixes20:35
Adlai mirkgeo: what cmn said... maybe you can separate the UI from the backend, and avoid the need for separate branches20:36
cmn a branch is useful for when you have diverging development; if you have a completely different UI, a different dir might be all you need (and would make it easier to handle)20:36
stayarrr joined20:36
mirkgeo true20:37
alfplayer left20:37
cmn I'd say the same applies to features you're going to scale/limit/whatever, you might want to use a compile/build/deploy option20:37
mirkgeo but what I also want is to kind of isolate the whitelabel-project, since that will be deployed to another server. We would actually avoid touching the main-product as much as possible20:37
cmn a build script could take care of extracting only the features/code you need20:38
zealiod left20:39
Gentlecat joined20:40
gommo joined20:40
mirkgeo yeah true20:40
cmn the gist of it is that it's easier to put this logic into a script than the devs having to figure out which changes belong in which branch and how to bring together all those different changes you've done to the different branches20:40
sgambino left20:40
etcetera joined20:41
tewecske joined20:41
macrover left20:41
BadDesign joined20:41
mirkgeo yeah, but I think there will be very few changes that are merged between the both products20:42
zealiod joined20:42
pppaul left20:42
Ryback_ left20:43
cmn I'm thinking about bugfixes to the core that you discover in one or the other20:43
it can get complex20:43
mirkgeo me too, but I think there may be a big win to be able to separate it to 2 projects..20:44
Since the main product isn't developed any more at this time20:44
rcu left20:45
cmn ok, that changes things a bit20:45
pppaul joined20:45
cmn if the dev is going to be on this new version and any fix porting will be rare, then you can probably fork it as a different project20:45
mirkgeo and this whitelabel would be a smaller project that I think would be stop developed after these changes are made20:46
what is the difference between fork and branch?20:46
cmn a fork is mostly a mental thing20:46
it's when you take the code and essentially produce a different product20:46
scrape left20:47
hoschi left20:47
cmn (the term is overloaded, as GitHub calls "fork" the repo you have in your personal account that's taken from an uptream project, which may or may not be a fork in the traditional ssense)20:47
mirkgeo ah20:48
what is a fork in traditional sense then?20:48
cmn it's getting fed up with the project and starting your own taking the existing code as starting point20:48
gyre007 joined20:49
_ikke_ mirkgeo: Taking a project in a different direction20:49
etcetera left20:49
mirkgeo aha20:49
but still have the possibility to merge things?20:49
breakingthings fork is just a concept for cloning a repo20:49
it's separate from the original repo, more than just a branch20:49
trungqtran left20:50
breakingthings you can take the code from there and commit your own things20:50
gtmanfreddontcare20:50
KaiSforzadoescare20:50
cmn breakingthings: that's not the traditional fork concept20:50
mirkgeo ah20:50
breakingthings this includes taking the project somewhere completely else, or making changes and making a pull request to have some fixes pulled into the source repo20:50
kcj left20:50
_ikke_ breakingthings: forking used to be a radical thing to do20:50
breakingthings cmn: the traditional fork concept has always been "a separate copy of an original thing"20:50
cmn to take it in a different direction20:51
breakingthings right, but that's a motive.20:51
cmn it's not a fork in the traditional sense when you clone to send aptach20:51
yes20:51
breakingthings fork as a concept still wasn't necessarily tied to that motive.20:51
cmn and the motive is what makes it the traditional one20:51
eletuchy joined20:51
TriRas left20:52
Thra11 joined20:52
breakingthings shrugs20:52
mirkgeo but you could still pick specific commits and merge between the original and fork?20:52
breakingthings It's all a semantics read-in to what people were thinking when they forked projects20:52
_ikke_ https://en.wikipedia.org/wiki/Fork_(software_development)20:52
etcetera joined20:52
whowantstolivef1 left20:52
breakingthings You could still fork and make fixes for your own use without actually being motivated to change the project direction20:52
tplaner left20:52
doescareKaiSforza20:53
_ikke_ breakingthings: You usually fork just because you *can't* change a projects direction20:53
breakingthings _ikke_ and you still can't.20:53
That's why we fork.20:53
cmn breakingthings: then you aren't forking the project20:53
breakingthings cmn: but you are20:54
wereHamster I created a fork. And I feel good about it!20:54
breakingthings the concept of forking is you clone the repo and do something with it20:54
_ikke_ I use forks to eat with20:54
simesy joined20:54
breakingthings it doesn't have to be I fork linux and make xunil20:54
wereHamster I EAT FORKS!20:54
WITH FORKS!20:54
breakingthings I can fork linux and make a few bug fixes and still call it linux20:54
still a fork20:54
not a radical change in direction20:54
cmn that'd be the concept of forking a repo, not a project20:54
wereHamster nope, yours will be a SPOON20:54
breakingthings the concept has always existed as just a technical term for "a separate copy of an original thing"20:54
dorkmafia left20:55
grizwako joined20:55
Thra11_ left20:55
_ikke_ breakingthings: In the time without distributed scm's, you couldn't just clone a project20:55
breakingthings whatever, it's all semantic read-in of whatever people in the past said fork for, who gives a.20:55
alainusalainus[-_-]20:55
wereHamster every time you download the source of a project (tarball, svn checkout, git clone) you could view it as a fork.20:55
breakingthings ^20:55
distributed means nothing20:56
source is what matters.20:56
jast if a fork is the same thing as a copy, I just call it a copy20:56
breakingthings thas' all I'm gonna say in the matter.20:56
jast and use the word 'fork' for something different20:56
I dunno, makes sense to me20:56
bootstrapper left20:56
kcj joined20:57
jast I maintain a fork of this channel, by the way20:57
jason237 joined20:57
jast ... in ~/irclogs20:57
_ikke_ mine is in .weechat/logs20:57
bremner fork off with your forking confusing terminology.20:57
oh, well, it is git.20:57
soreau left20:57
jast hey _ikke_, wanna merge forks?20:58
_ikke_ jast: sure20:58
wereHamster wanna spoon?20:58
tewecske left20:58
dougsland joined20:58
simesy left20:58
jast are we regurgitating atlassian jokes now?20:58
skanev_ joined20:58
_ikke_ atlassian jokes?20:58
jast atlassian had a video on spooning for bitbucket last April 1st20:58
_ikke_ oh, lol20:59
mikehaas763 I never saw it!20:59
_ikke_ https://bitbucket.org/spooning/20:59
eletuchy left20:59
kcj left20:59
sgambino joined20:59
JSharpe left20:59
tewecske joined20:59
gasbakid left21:00
gusnan left21:00
jast the presenter is doing an awesome job21:00
gregor3005 joined21:00
hesco2 joined21:01
_ikke_ Fork, spoon and knife :D21:01
kcj joined21:01
erichynds left21:02
ivanzgb joined21:02
boombatower joined21:03
mirkgeo cmn: but using rebase isn't a good idea then? create 2 new branches, whitelabel-master and whitelabel-dev. Each time master is fixed I rebase whitelabel-master from that?21:03
mikehaas763 haha wtj21:03
mirkgeo whitelabel-master/whitelabel-dev21:03
mikehaas763 *wth21:03
daurnimator left21:04
danishkhan joined21:04
cmn rebase causes problems if the branch is public21:05
EugeneKay Old21:05
cmn !rewrite21:05
gitinfo [!rewriting_public_history] Rewriting public history is usually bad. Everyone who has pulled the old history have to do work (and you'll have to tell them to). If you must, you can use `git push -f` to force (and the remote may reject that, anyway). See http://git-scm.com/docs/git-rebase.html#_recovering_from_upstream_rebase21:05
jcromartie left21:05
dontcareexcitebike21:05
cmn so you should avoid it21:05
mirkgeo cmn: what do you mean by public?21:06
cmn other people know about it and may have fetched it21:06
dharrigan joined21:06
dharrigan left21:06
dharrigan joined21:06
cmn the main dev branch is public e.g.21:06
mirkgeo cmn: just the dev team21:06
cmn that's still public21:06
mirkgeo aha21:06
gitinfo set mode: +v21:06
excitebikegtmanfred21:07
cmn rebase rewrites history, so if they merge what you have, you'll get the commits twice (sort of, they're different commits, with the same changes)21:07
RWOverdijk joined21:07
hesco2 I was doing some final changes on a branch specific to a ticket I was working on. I have now checked out the local branch for the tagged release I need to add these changes to, before pushing those changes to the corresponding remote tagged release in the origin repo. How is it I first inspect the diff for the two files I am concerned with between the ticket branch and the release branch, and then merge just those changes from the ticket br21:07
dougsland left21:07
ivanzgb left21:07
dougsland joined21:08
RWOverdijk (PR: on github). Let's say I have a PR waiting, and I want to start working on the next PR… But the files I have to work in are in the first PR and I don't want to cause conflicts, but I also don't want to wait for that PR to be merged.. What's the best thing to do?21:08
trungqtran joined21:08
mirkgeo cmn: true21:09
cmn while rebase is useful when you're preparing your branch to be sent upstream, once the code lands upstream, you don't rewrite it21:09
ErKa left21:10
cmn there are exceptions for branches that are accessible to other people but understood to be unstable, but those wouldn't usually end up in the main repo21:10
dorkmafia joined21:10
rath left21:11
_ikke_ RWOverdijk: Create a new branch based on the first branch. When the first branch has been merged, rebase your new branch on top of it21:11
(ie, on top of upstream)21:11
RWOverdijk _ikke_: Isn't that how the next PR will have a ton of commits from the previous PR?21:11
(sorry, new to this sort of stuff)21:11
mirkgeo cmn: alright21:11
drizzd left21:12
_ikke_ RWOverdijk: Nope21:12
RWOverdijk: rebase sees duplicate commits21:12
tinti_ left21:12
RWOverdijk _ikke_: Thank you :)21:12
MatthewWilkesmwilkes|away21:13
pppaul left21:14
gusnan joined21:14
danishkhan left21:14
mirkgeo cmn: so you think a fork would be the best?21:14
RWOverdijk left21:14
mwilkes|awayMatthewWilkes21:14
ohnoesit_ joined21:15
skanev_ left21:16
cmn from what you're saying, the development is really going to be in this whitelabel stuff, no? then you can concentrate on developing the new project and leave the old one mostly behind21:16
BadDesign left21:16
cmn you'd still be able to backport with cherry-pick (as long as the code hasn't diverged too much), but you can leave the old project alone in its own repo if it's not going to get used really21:17
jjasinski left21:17
mirkgeo cmn: yes, that is what it looks like. That is why 2 new branches was the idea from the beginning21:17
_ikke_ mirkgeo: two repo's or two branches are basically the same thing21:17
cmn two new branches are four branches21:18
jjore left21:18
mirkgeo yeah, so 2 repos with 4 branches or 1 repo with 4 branches21:18
AnimeCYC left21:19
sebuba left21:19
EugeneKay Therre are four lights21:19
cmn right, in this case case it would be easier with two repos21:19
QaDeS joined21:19
gtmanfreddontcare21:19
anabelle left21:19
leehambley left21:20
dontcaregtmanfred21:20
Thra11_ joined21:20
mishok13 left21:20
jjasinski joined21:20
Chikore joined21:21
ChikoreShuck21:21
johnthebear left21:22
Thra11 left21:22
ecksit joined21:22
daniel_b left21:23
mishok13 joined21:24
mirkgeo cmn: guess so too21:24
longbeach left21:24
zealiod left21:24
zealiod joined21:24
zealiod left21:24
tinti_ joined21:24
eletuchy joined21:25
e66 left21:25
cashwilliams joined21:25
jjore joined21:26
ouah joined21:26
scrape joined21:26
Orbitrix left21:26
freeed left21:26
mirkgeo I cloned the master branch of a github-repo. Another branch is 17 commits ahead. How do I do to merge it into master and then push it to github?21:27
chuckharmston joined21:27
cashwilliams1 joined21:28
cashwilliams left21:28
b1rkh0ff left21:28
charon mirkgeo: git merge origin/other; git push origin master ?21:28
unless by "cloned the master branch" you mean you actually did a restricted clone of only that branch21:28
Turicas joined21:29
b1rkh0ff joined21:30
boblannon joined21:30
mirkgeo chol: not restricted as far as I know :)21:30
b1rkh0ff left21:31
guampa left21:31
mcdebugger joined21:31
boblannon i like using git add -p. i swear i used to be able to split hunks on it, though. now i don't see the option21:31
and pressing 's' gives me the same result as pressing '?'21:32
breakingthings boblannon: git add -i21:32
I do beleev.21:32
eletuchy left21:32
breakingthings that is what you are look for.21:32
b1rkh0ff joined21:32
mirkgeo charon: looks like it worked. But github still says on branches-page that the other is 17 ahead..21:32
chuckharmston left21:33
jason237 left21:34
Sigma joined21:35
boblannon breakingthings: still the same result. when i get to the interactive patch screen, it only offers some of the normal options21:35
"Stage this hunk [y,n,q,a,d,/,j,J,g,e,?]?"21:35
note the lack of 's'!21:35
_ikke_ boblannon: It means git can't split it up further21:35
breakingthings ^21:35
boblannon oh, okay, that's what i was afraid of21:36
breakingthings never used -p so wasn't sure if it couldn't split for another reason21:36
but ikke is indeed correct21:36
sq-one_ joined21:36
breakingthings however, you can always use 'e'21:36
to be a 1337 inline haxx0r21:36
mmu_man joined21:36
pooya joined21:36
boblannon right. 'e' keeps opening nano, though. is there a way to make it use vim?21:37
m0ltar left21:37
boblannon (i have vim set as my difftool already)21:37
_ikke_ boblannon: change the EDITOR virable21:37
marhaban left21:37
vad vi, a virable (viral...) editor, no less.21:38
cmn there's also core.editor in the config if you don't trust your environment to set the right one21:38
revagomes left21:39
pr0ton left21:39
etcetera left21:39
danishkhan joined21:39
sq-one_ left21:39
boblannon awesome, thanks!21:39
sq-one left21:40
boblannon setting core.editor got the job done21:40
cashwilliams1 left21:40
gtmanfredexcitebike21:40
cmn you might still want to set the environment settings, as they also affect other parts of the system21:40
like what less does when you hit v21:41
vad use ? to find out21:41
tjbiddle_ joined21:41
tjbiddle_ left21:41
cmn what?21:41
Cromulent joined21:42
dougsland left21:43
aksnot left21:43
grawity_grawity_21:43
_ikke_ wat?21:43
_grawity_grawity21:43
vad Use the '?' key while in less to get help, and to figure out what 'v' would do21:43
cmn how does that help you set the visual editor?21:43
KaiSforzagtmanfred21:43
dougsland joined21:43
vad I misread your line, then,.21:44
gtmanfredKaiSforza21:44
guampa joined21:44
cmn not that '?' gives you help anyway21:44
PaulCapestany left21:44
tjbiddle left21:44
mulinux joined21:45
daniel_b joined21:47
gruen0 joined21:47
dropdriv1 left21:48
jaseemabid left21:48
dropdrive joined21:48
garbagecollectio i do a git pull21:48
and it says21:48
"There is no tracking information for the current branch."21:48
grawitygtmanfred21:48
garbagecollectio please specify which branch you want to merge with21:48
danishkhan left21:49
gtmanfredGuest6192321:49
Guest61923grawity21:49
danishkhan joined21:49
excitebikegtmanfred21:49
ErKa joined21:51
pooya hmm, any idea why when i try to cherry-pick or rebase a range of pervious commits, it does nothing?21:51
cmn they're already applied on your current code?21:52
also, !repro21:52
gitinfo Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session. This will help immensely with troubleshooting.21:52
tjbiddle joined21:52
tinti_ left21:52
redrocket left21:53
AnimeCYC joined21:53
garbagecollectio any reason why21:53
pooya cmn: already applied but reverted21:53
garbagecollectio There is no tracking information for the current branch."21:53
why would that have happened21:53
cmn garbagecollectio: because you never set it21:53
garbagecollectio but it was set21:53
what happened was someone pushed updates from something from their side21:54
jonshea left21:54
garbagecollectio and then it said i needed to update21:54
and i did a pull21:54
v0n left21:54
garbagecollectio and it said no tracking information21:54
pooya I used to use a script like this to revert a bunch of changes and put in a different branch: http://pastebin.com/LNWJYNvn but in this case it is not working21:54
i wonder if anyone did a force push onto the master branch21:55
cmn garbagecollectio: when was it set?21:55
mikehaas763 left21:55
j^2 left21:55
marhaban joined21:55
garbagecollectio i don't know if it was set21:55
it usually is set21:55
probably when i first do it21:55
the question is how did it get unset21:55
cmn that shouldn't be the question, as you don't know it was21:56
rue left21:56
cmn how did you create the current branch?21:56
albel727 left21:56
arietis left21:56
albel727 joined21:56
taylorlapeyre joined21:56
timj joined21:56
tinti_ joined21:57
pr0ton joined21:57
jstemmer left21:57
garbagecollectio it was set days ago21:58
it somehow got unset21:58
not manually21:58
zoned joined21:58
garbagecollectio what do i do21:58
seriously21:58
cmn either set the upstream information or tell pull what it should do21:59
garbagecollectio how do I do that21:59
cmn git branch -u <upstream> in the branch sets its upstream21:59
eletuchy joined21:59
frenchlaf left22:00
sunya7a left22:00
zoned i was trying to push a local 'updates' branch over the top of my 'dev' branch… so i did: git push -f origin updates:dev; git checkout dev; git pull; and i was missing my updates. I'm assuming this is because i forgot to do a git commit on the updates branch first. so now i do a git checkout updates; git pull; … and its still old…. how do i get my updates back!?22:00
cmn pooya: both master and $TAG_FROM are pointing to the same place22:00
so the rebase is a noop22:00
ouah left22:01
cmn oh, wait; maybe not, why are you using such a complex way to commit a particular set of files?22:01
pooya i just want to revert a set of commits and put them in a different branch22:01
so that they can easily be merged later22:02
grawity zoned: if you didn't commit them, then they're still in your working tree22:02
zoned: run `git status`22:02
zoned grawity: the only thing it says has been modified is my .cache folder22:02
pooya i revert them all, branch and rebase that set. not sure why you say complex22:02
cmn pooya: you're not reverting anything, you're committing on top of $TAG_TO with the files of $TAG_FROM, and undoing anything after $TAG_FROM22:02
pastime joined22:03
grawity zoned: does `git log updates` show them?22:03
cmn and setting your master branch to $TAG_TO22:03
zoned grawity: no, last commit was days ago22:03
cmn oh, i see what you're doing22:03
pooya cmn: on top of master not TAG_TOP22:03
cmn pooya: use diff22:03
pooya: master is at TAG_TOP22:03
pooya i want to keep history22:03
cmn not with this script22:04
pooya yes, before i start the operation22:04
zoned grawity: it has some of them, but not the recent stuff22:04
pooya cmn: the script works on a normal repo, i've tested it22:04
cmn for some values of normal22:04
zoned (because i never committed it…) i really hope i didn't lose these..22:04
pooya not that master changes after the first batch of revert commands22:04
cmn your rebase just seems to be a very complicated way of doing cherry-pick22:04
pooya s/not/note/22:04
cmn there are no revert commands22:04
pooya cherry-pick is pretty bad with merges22:04
cmn it's exactly the same22:05
you're rebasing the one diff22:05
pooya ya, the whole revert is squashed into a single commit22:05
cmn right22:05
pooya so that i can re-merge the old commits22:05
otherwise git will think they are already applied22:05
cmn which makes the difference between cherry-pick and rebsae what?22:05
R1KRDO left22:06
cmn this sounds a lot like an xy problem, what are you actually trying to accomplish?22:06
pooya at least for me i have to manually cherry-pick one by one and specify -m <n> when needed22:06
this sounds like easier to batch22:06
cmn now you're talking about doing something different22:06
gyre007 left22:06
pooya i am trying to take out a series of recent commits and put them in a different branch so that i can merge them back22:06
kawamanza joined22:06
pooya but since they're already pushed i don't want to use reset --hard...22:07
and push -f22:07
eletuchy left22:07
stayarrr left22:07
cmn so what's the deal with the resets?22:07
why are you setting master back?22:08
alainus[-_-]alainus22:08
redrocket joined22:08
garbagecollectio git branch -u and then what22:08
to get my shit tracking22:08
WorkeD joined22:08
cmn garbagecollectio: that's what sets the upstream information22:08
garbagecollectio but what do i give it to the22:08
just the branch name22:09
just the branch name?22:09
redrocket left22:09
cmn the remote-tracking branch name22:09
garbagecollectio which would be what22:09
just the name22:09
ThePawnBreak left22:10
kawamanza left22:10
cmn its name, upstream/fancy or whatever they're called22:10
daniel_b left22:10
garbagecollectio origin/feature-geapp-207-part122:10
?22:10
cmn that could be22:10
garbagecollectio how do i find out which one it is22:11
etcetera joined22:11
cmn you're the one who should know22:11
Cromulent left22:11
cmn it's the project you're working with22:11
what branch corresponds to what you're basing off of or where it should go?22:11
garbagecollectio its called feature-geapp-207-part122:12
so what do i type22:12
PaulCapestany joined22:12
cmn what you just did22:12
<upstream> would be origin/feature...22:12
garbagecollectio but i have the branch locally already22:13
git brnach --set-upstream mybranch name origin/mybranchname22:14
markalanevans joined22:14
pooya cmn: those resets are making a diff change of things that needs to be reversed. hard reset to TAG_FROM but soft reset to TAG_TO22:14
so actual code will be similar to TAG_FROM state, but HEAD pointer will be on TAG_TO22:15
so gives a list of changes reversed...22:15
cmn don't think of HEAD as something special, you're moving master to TAG_TO22:16
pooya try it22:16
it works22:16
SonikBoom left22:16
pooya yes, code wise it is on TAG_TO22:16
no i mean the other way22:16
cmn master is pointing to TAG_TO after the second reset22:16
pooya the actual files will be similar to TAG_FROM22:17
but a git diff will show the differences with TAG_FROM22:17
etcetera left22:17
cmn right, you're taking the known files and commit as they are in TAG_FROM22:17
which you can just do with a read-tree $TAG_FROM22:17
without having to reset anything to anything22:17
pooya try it man, that step is working fine22:17
cmn I know the diff will be right22:18
but why are you moving master22:18
pooya it's the second rebase step that is failing in this case22:18
like i said i want to revert changes but if i do git revert22:18
cmn you say you don't want to rewrite, but yo move master, why is that?22:18
pooya i want to move master to an old tag (TAG_FROM)22:18
yedi joined22:18
pooya but if i just do git --reset hard TAG_FROM22:19
and do a git push -f22:19
yedi how do i clear all the files in my staging area22:19
pooya it will break everyone else's pull22:19
yedi i need to do this all the time and idk how its possible that i haven't figured it out yet22:19
i thought it was like git checkout -- .22:19
cmn yes, but if you want master's code to be at $TAG_FROM, you can do git read-tree $TAG_FROM && git commit -m "whatever"22:19
I guess it'd be easier to see what's happening if you git checkout $TAG_FROM -- . && git commit22:20
etcetera joined22:20
cmn now you have a commit on top of master with the files at $TAG_FROM, without rewriting history22:20
pooya that's exactly what i want. i can rewrite history because it's already pushed22:21
if i rewrite history other dev's checked out repos will break22:21
etcetera left22:21
cmn right22:21
so don't move master22:21
vdv left22:21
jaseemabid joined22:22
cmn I don't get why you keep saying you can't move master but still want to move it to TAG_TO22:22
evanp Will "git checkout $TAG -- . && git commit" delete files created since $TAG? IIRC it won't....22:22
boblannon left22:22
Watabou joined22:22
cmn no22:22
__Big0__ left22:22
pooya cmn: oh i see what you're saying, i should that step in a tmp branch22:22
actually this works22:23
Thra11_ left22:23
cmn or detach HEAD, anything but reset master22:23
and really, those resets just confuse22:23
pooya ya22:23
anyhow you know what i want to do in that step22:23
my question is the second one22:23
kadoban_ left22:23
jaequery left22:23
dorkmafia left22:24
cmn TAG_TO isn't off of master22:24
hellopat left22:24
Noldorin left22:24
cmn have you tried w/o moving master to be built on top of TAG_TO/22:24
ojacobson left22:24
cogitos joined22:25
Sigma left22:25
mattt_ joined22:25
relipse joined22:26
mattt_ Is there a way to replay changes in some branch that's ahead of master (but shouldn't be) over master?22:26
cebor joined22:26
Noldorin joined22:27
Thra11 joined22:27
Davey joined22:27
jjore left22:28
scrape left22:29
johnw joined22:31
jjore joined22:31
Gaddel joined22:32
Gaddel hi, i have a github repo that i own. i want to basically clear out that repo and replace it with my local files. what's the best way of doing this?22:32
my local repo is much more up to date than the remote repo22:33
grawity Force-push22:33
or, no, maybe don't.22:33
eletuchy joined22:33
pr0ton left22:34
_iron left22:34
marhaban left22:34
Gaddel that's sort of what i want to do. i want to overwrite the remote repo (i've never pulled it before, to my current computer)22:34
also i am very new to git so i am a bit lost22:35
lethjakman left22:35
Thra11 left22:35
PhreakIT joined22:36
rbmk left22:37
zoned git add .; git commit -am "some message"; git push origin local_branch:remote_branch22:37
macabre left22:37
trungqtran left22:37
Gaddel okay, done that; it all works. thanks22:38
gruen0 left22:38
m0ltar joined22:39
Parhs left22:40
milStaja joined22:41
tjbiddle_ joined22:41
eletuchy left22:42
SonikBoom joined22:43
lethjakman joined22:44
tjbiddle left22:44
tjbiddle_tjbiddle22:44
brokenjames left22:44
john2496 left22:46
mulinux left22:47
diamonds left22:47
rfoust joined22:47
pppaul joined22:48
marhaban joined22:48
hwrd|work left22:48
mirkgeo left22:48
Noldorin left22:49
hwrd|work joined22:49
hesco2 left22:49
pr0ton joined22:50
gommo left22:50
nicoulaj left22:51
Noldorin joined22:51
jason237 joined22:53
SonikBoom left22:53
Davey left22:53
SonikBoom joined22:53
mattt_ How can I retroactively merge the remote master?22:54
alainusalainus[-_-]22:54
vad You can't retroactively, only now22:55
wereHamster or in the future22:56
unless you have a time-travel machine. Then you can do it retroactively22:56
but if you have, consider using it for something more useful (like killing hitler or something)22:56
vad see Novikov self-consistency principle22:57
PerlJam mattt_: why do you want to do this?22:57
vad The XY problem: You want to do X, but don't know how. You think you can solve it using Y, but don't know how to do that, either. You ask about Y, which is a strange thing to want to do. Just ask about X.22:57
the command alias to output _that_ still works ;)22:57
wereHamster vad: FYI, there is the !xy trigger :)22:58
gitinfo vad: This sounds like an "XY Problem" http://mywiki.wooledge.org/XyProblem So let's step back for a minute. What are you actually trying to achieve? Why are you doing it this way?22:58
mattt_ PerlJam: Working on bitbucket I did a pull request from my fork's branch to remote master, then I merged the same branch into my fork's master, and figured I'd be up to date with remote, but that wasn't the case. Now I've made a bunch of changes and can't figure out how to reconcile my fork with remote22:58
lonewulf` left22:59
vad wereHamster: only in select channels; so, to have the club ready at any time, only a client-level trigger/alias (like /xy) is the true solution!22:59
skanev_ joined22:59
kermit left22:59
maestrojed left23:00
lonewulf` joined23:00
oakdog8 left23:00
fisted_ joined23:00
CreativeEmbassy left23:01
Davey joined23:01
kermit joined23:01
skanev_ left23:02
breakingthings left23:02
Damgaard left23:03
fisted left23:04
fisted_fisted23:04
cannonball left23:04
maestrojed joined23:07
eletuchy joined23:08
m0ltar left23:09
mattt_ left23:09
pantsman left23:09
Sky[x] joined23:10
d2dchat left23:10
trythis left23:10
nioncode left23:11
hwrd|work left23:12
hwrd|work joined23:13
Destos left23:13
etcetera joined23:13
thiago left23:14
etcetera left23:15
quazimodo joined23:15
eletuchy left23:16
perlstein hey23:17
what do people use for internal code review?23:17
zoned left23:18
Gaddel left23:18
green- left23:19
bmac joined23:19
garbagecollectio left23:22
gdoteof_ left23:23
atrus perlstein: custom tools here. tool pushe review branch to common location for review. issues are filed, and resolved and pushed to that common location again for verification. once the review is finished, the tool merges the review branch into branch the code was originally targeted for.23:23
!review23:23
gitinfo [!codereview] Gerrit is a code review tool for git. See http://code.google.com/p/gerrit/ You may want to enforce certain workflow to prevent people bypassing review. gitolite (and a branching workflow) or a integrator repository (distributed workflow) would be good for this.23:23
atrus (we don't use that, i was just curious if !review had useful content)23:23
gitinfo [!codereview] Gerrit is a code review tool for git. See http://code.google.com/p/gerrit/ You may want to enforce certain workflow to prevent people bypassing review. gitolite (and a branching workflow) or a integrator repository (distributed workflow) would be good for this.23:23
atrus (oops)23:23
unbounced left23:24
sgambino left23:24
tjbiddle_ joined23:25
hiroyuki_ left23:25
WorkeD left23:26
atrus gerrit does sound pretty close to what we use.23:27
decotii left23:27
eletuchy joined23:27
taylorlapeyre left23:27
zacts joined23:28
tjbiddle left23:29
tjbiddle_tjbiddle23:29
bartzy left23:29
maxmanders left23:29
gotwig left23:30
thl0 left23:30
lethjakman left23:30
Shurakai left23:31
atrus although it looks like gerrit operates on individual commits?23:31
lethjakman joined23:31
eletuchy left23:31
atrus maybe not?23:31
mmitchell left23:31
tjbiddle_ joined23:32
cebor left23:32
erkules left23:32
erkules_ joined23:32
beitao joined23:33
mitzip left23:33
pastime left23:34
penguin1 left23:35
Watabou left23:35
tjbiddle left23:35
tjbiddle_tjbiddle23:35
hwrd|work left23:35
hwrd|work joined23:36
engla left23:36
anonymuse left23:38
pastime joined23:38
markalanevans left23:39
lavaman left23:39
hellopat joined23:40
pr0ton left23:40
tjbiddle_ joined23:43
pr0ton joined23:43
malkomalko left23:43
beitao_ joined23:44
beitao_ left23:44
hwrd|work left23:44
DarkAceZ joined23:44
willob left23:44
beitao left23:44
cogitos left23:44
tjbiddle_ left23:45
hwrd|work joined23:45
tjbiddle left23:46
Watabou joined23:46
kadoban_ joined23:46
normanrichards joined23:47
Xethron joined23:47
scorphus left23:50
lethjakman left23:50
hwrd|work left23:51
sfalcon left23:53
TeckniX left23:53
simesy joined23:55
hwrd|work joined23:55
Adlai errrrr... error? http://bitbin.it/hqXQg6UP23:56
eijk_ left23:56
bmac left23:56
hwrd|wor_ joined23:58
madewokherd left23:59
simesy left23:59
madewokherd joined23:59

Logs Search ←Prev date Next date→ Channels Documentation