IRCloggy #git 2013-08-05

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

enr left00:00
DonVitoCorleone joined00:01
rfk joined00:03
dustyfneon joined00:04
simesy left00:04
rfk I'm looking for a utility that allows me to pull specific files out of repositories/packages that i download, for inclusion in projects (e.g., PHP or JS includes); as of now, I must pull out the specific files I want and place them in the appropriate include directories, e.g. $WWW_ROOT/static/js/file.js. Does git have anything for this kind of situation?00:05
Should I just symlink them all, and re-symlink them whenever I update the package?00:06
clreed87 joined00:06
rfk I guess, what I am looking for is 'dependency management' ? I heard of composer for PHP, but have not gotten deep into the documentation (yet)00:06
AWinterman joined00:06
jaequery left00:07
Davey left00:07
huoxito left00:07
Gitzilla joined00:07
milki rfk: the short answer is no and the management is outside the scope of git. see !deploy, but that probably wont give you a final solution00:08
gitinfo rfk: Git is not a deployment tool, but you can build one around it(in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/the-list-and-irc/deploy.html00:08
KernelPanicMK2 joined00:09
jackdempsey left00:09
jaequery joined00:09
rfk OK, makes sense. Do you know off the top of your head any utilities that might accomplish this, or even what the generic name is for what i am talking about ?00:10
huoxito joined00:10
madewokherd left00:10
Dougie187 joined00:10
jaequery left00:11
o] left00:11
jaequery joined00:11
o] joined00:12
tmcmahon joined00:12
jackdempsey joined00:12
breck7 joined00:13
ej joined00:13
mribeirodantas joined00:14
tmcmahon left00:14
adamwathan joined00:15
PaulCapestany joined00:16
clreed87 left00:16
iliketurtles joined00:16
AWinterman left00:16
ej left00:18
iliketurtles left00:19
AWinterman joined00:21
emergion joined00:24
emergion left00:29
br1 left00:30
dreiss left00:31
cigarshark left00:32
milki rfk: package management, deployment systems, dependency management00:32
if you rely on 3rd party files, refer them at their original filepaths rather than try to bring them into your own project hieararchy00:33
wakd left00:34
scorphus joined00:35
warlock_mza left00:35
simesy joined00:35
michaelarestad left00:35
Vampire0 left00:36
BSaboia left00:37
simesy left00:38
rfk left00:38
simesy joined00:39
mechanicalduck joined00:39
rfk joined00:39
jaequery left00:39
joelpittet joined00:40
Vampire0 joined00:40
AWinterm_ joined00:42
hyperair left00:43
jaequery joined00:44
FreezingCold joined00:44
iliketurtles joined00:44
dreiss joined00:44
iliketurtles left00:44
iliketurtles joined00:45
rfk left00:46
hellopat left00:47
groglogic joined00:48
pdurbin joined00:48
iliketurtles left00:49
Destos left00:49
parcs joined00:49
redrocket left00:49
oojacoboo joined00:50
oojacoboo left00:50
nathancahill joined00:50
jaequery left00:51
AWinterm_ left00:52
parcs_ left00:53
madewokherd joined00:54
plumpkin left00:55
R1KRDO joined00:58
k_sze[work] joined00:59
melee joined00:59
KillYourTV left01:00
JeremyWei joined01:00
KillYourTV joined01:00
Marenz joined01:02
jelmer_jelmer01:03
Octalot left01:03
Davey joined01:04
hyperair joined01:05
Suprano left01:05
acharlieh joined01:05
lamarus joined01:07
Suprano joined01:11
z8z joined01:13
ej joined01:14
ncd|leeN joined01:14
Marenz left01:15
hyperair left01:16
R1KRDO left01:16
fase left01:17
AWinterm_ joined01:18
ej left01:18
warlock_mza joined01:19
quazimodo left01:20
quazimod1 left01:20
hyperair joined01:21
Hoosier2016 joined01:22
ArokhArokh[Off]01:22
CheckDavid left01:25
dougsland left01:25
weiyang joined01:26
AWinterm_ left01:27
gusnan joined01:29
normanrichards joined01:30
mechanicalduck left01:34
iliketurtles joined01:34
St_Marx left01:35
St_Marx joined01:37
LBV_User left01:40
Fandekasp hi there01:44
I have a problem with git merge -s theirs01:44
getting error git-merge-theirs: command not found01:44
and a git rebase --continue will do the same as git merge -s ours01:45
Goplat joined01:45
Fandekasp I want to make sure that when upstream and local edit the same file, local lines are preserved, but upstream new lines are added01:45
luc_ joined01:45
Fandekasp and reading the manpage, strategy theirs is for the local repo. Any idea how to fix that issue ?01:46
joki left01:46
swiftkey joined01:47
swiftkey left01:47
swiftkey joined01:47
enr joined01:48
Hoosier2016 left01:48
ToxicFrog Fandekasp: don't you just want plain 'git merge' for that?01:51
Vampire0_ joined01:51
verysoftoiletppr joined01:52
ToxicFrog (there is no "theirs" merge strategy. There is a "theirs" option to the "recursive" strategy, which is different.)01:52
joki joined01:52
goshawk joined01:52
daito joined01:52
PaulCapestany left01:52
enr left01:52
groglogic left01:54
Hoosier2016 joined01:54
Fandekasp ToxicFrog: no I don't want to resolve conflicts manually, there would be too many of them. currently reading the "RECOVERING FROM UPSTREAM REBASE" part of the manpage, very interesting01:54
jon_r left01:54
AWinterm_ joined01:54
Vampire0 left01:54
chrisgeorge joined01:55
zendeavor so i want to create a new branch based on the remote master, and update a single file from a current working branch. i'm assuming i should checkout master, checkout -b newbranch, and then...something to fetch the other branch's single file that i want to update to.01:55
Hoosier2016 left01:55
gusnan left01:55
docwhat left01:55
chriswk joined01:56
Fandekasp ToxicFrog: and you're right, -Xtheirs isn't good enough because it doesn't add new lines from upstream01:56
jackdempsey left01:57
pr0ton joined01:58
Fandekasp hmm I basically want commits from upstream to be added first, and commits from local to be patched on top of upstream commits, should do the trick01:58
docwhat joined01:59
verysoftoiletppr left02:02
AWinterm_ left02:03
jackdempsey joined02:04
Fandekasp ah02:05
ToxicFrog: got it... I just wanted the -Xours, and was mistakengly doing a -s ours :)02:06
milki Fandekasp: rebase!02:06
Fandekasp: !rebase02:06
gitinfo Fandekasp: [!mergerebase] @!merge_or_rebase02:06
dhruvasagar joined02:06
milki o that is so not useful02:06
quazimodo joined02:08
iliketurtles left02:08
jon_r joined02:09
Dougie187 left02:12
daito left02:14
quazimodo left02:14
daito joined02:14
xpirator joined02:14
ej joined02:15
flippo joined02:15
EugeneKay !triggers02:15
gitinfo Please don't spam me! I'm just a poor bot! Here's everything I know: http://jk.gs/git/bot/trigger.php -- that's a list of these nifty keywords like "!bot" that you can use in the channel, in case you were wondering.02:15
EugeneKay !mergerebase02:16
gitinfo [!merge_or_rebase] For a detailed discussion of the dis-/advantages of merge and rebase, and when to best use which, see: https://coderwall.com/p/ny1hia -- and here's how Linus explains which one to use: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html02:16
iliketurtles joined02:16
EugeneKay .trigger_edit rebase @!merge_or_rebase02:16
gitinfo EugeneKay: Okay.02:16
warlock_mza left02:16
EugeneKay !rebase02:16
gitinfo [!merge_or_rebase] For a detailed discussion of the dis-/advantages of merge and rebase, and when to best use which, see: https://coderwall.com/p/ny1hia -- and here's how Linus explains which one to use: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html02:16
dsdeiz joined02:16
EugeneKay set mode: -o02:16
ology !ugh02:16
jeffery_ left02:18
daito left02:19
warlock_mza joined02:19
ej left02:19
rabellamy joined02:20
lavaman joined02:22
AWinterman left02:22
pr0ggie joined02:25
pr0ggie left02:25
pr0ggie joined02:26
BJfreeman left02:27
cads joined02:28
bewest left02:30
AWinterman joined02:30
jfoy joined02:31
joshsmith left02:34
AWinterman left02:38
chrisgeorgeCasear_02:40
pr0ggie left02:41
pr0ton_ joined02:41
daito joined02:42
pr0ton left02:42
pr0ton_pr0ton02:42
rabellamy left02:42
lamarus left02:43
SeoZ2 left02:45
goshawk left02:46
Casear_chrisgeorge02:47
jfoy left02:48
Bosox20051 left02:49
simesy left02:51
hahuang61 joined02:52
Marquisk2 left02:52
dustyfneon left02:53
Bosox20051 joined02:53
Bosox20051 left02:53
Bosox20051 joined02:53
Bosox20051 left02:53
Bosox20051 joined02:54
Bosox20051 left02:54
Fandekasp left02:56
Fandekasp joined02:57
jeffery_ joined02:58
methods joined03:00
methods left03:00
methods joined03:00
methods what is the command that shows you waht head pointed to the last few times ?03:00
offby1 git log -g03:01
breck7 left03:01
offby1 aka git reflog03:01
!reflog03:01
gitinfo The git reflog (`git log -g`) records the SHAs of your HEADs for 2+ weeks. `git checkout -b myrestore OLDSHA` and `git reset --hard OLDSHA` will relink to that state via a new and current branch respectively, see http://sethrobertson.github.com/GitFixUm/ for full details. WARNING: reset --hard will trash any uncommitted changes! Visualize with: gitk --all --date-order `git log -g --pretty=%H`03:01
Orbitrix left03:01
skorgon left03:01
AWinterman joined03:01
skorgon joined03:02
threesome joined03:03
simesy joined03:03
donmichelangelo left03:03
methods left03:03
donmichelangelo joined03:04
mdhopkins joined03:04
AWinterm_ joined03:06
babilen_ joined03:06
Fandekasp left03:08
chrisgeorge left03:09
Inside joined03:09
Inside left03:09
Inside joined03:09
babilen left03:09
Fandekasp joined03:10
mitz left03:11
warlock_mza left03:11
mitz joined03:11
parcs_ joined03:12
dhruvasagar left03:12
carlos-huang joined03:14
parcs left03:14
Cromulent joined03:14
echo-area joined03:14
AWinterm_ left03:14
ej joined03:16
HenryG left03:17
bmac joined03:18
herdingcat joined03:20
ej left03:20
dhruvasagar joined03:20
JoeCoolDesk joined03:20
marhaban left03:20
jackdempsey left03:21
JoeCoolDesk left03:21
Orbitrix joined03:21
Orbitrix left03:21
Orbitrix joined03:21
godoitis joined03:21
Patrick joined03:23
godoitis left03:23
PatrickGuest2953703:24
jaequery joined03:26
SinnerNyx joined03:26
dhruvasagar left03:27
Noldorin left03:30
iliketurtles left03:30
michaelarestad joined03:32
m104 joined03:33
kukks left03:33
madewokherd left03:34
AWinterman left03:37
adamwathan left03:37
SeoZ-work[AWAY] joined03:37
SeoZ-work[AWAY]SeoZ203:38
Guest29537 left03:40
dreiss left03:40
bmac left03:41
texasmynsted1 left03:41
AWinterman joined03:41
jackdempsey joined03:42
shinnya left03:43
preflex_ joined03:44
preflex left03:44
preflex_preflex03:44
jaequery left03:45
zacts left03:46
dsdeiz_ joined03:47
dsdeiz left03:47
cogitos joined03:47
nathancahill left03:48
zacts joined03:50
AWinterman left03:51
unreal left03:52
sqlnoob joined03:53
pen left03:56
pen joined03:57
lavaman1 joined03:57
lavaman left03:57
mribeirodantas left03:57
m104 left03:59
donmichelangelo left04:00
donmichelangelo joined04:01
unreal joined04:01
z8z left04:02
zacts left04:04
Chikore joined04:04
ivan` left04:06
dsdeiz joined04:06
zbcmZombiesAreComing04:07
ZombiesAreComingzbcm04:08
pr0ton left04:08
dsdeiz_ left04:09
skorgon left04:11
barneybook left04:13
quazimodo joined04:13
acharlieh left04:14
ej joined04:17
AWinterman joined04:18
quazimod1 joined04:18
ej left04:21
AWinterman left04:27
jaequery joined04:28
pr0ton joined04:28
maroloccio left04:28
daito left04:29
sgambino left04:30
Tommy[D] joined04:31
m104 joined04:31
m104 left04:32
m104 joined04:32
m104 left04:32
PaulCapestany joined04:33
YoMomma joined04:34
YoMomma left04:34
Tommy[D]_ left04:34
mitz left04:34
mitz joined04:35
m104 joined04:35
m104 left04:35
beautifulmind joined04:36
ivan` joined04:38
quazimod1 left04:39
quazimodo left04:39
cha1tanya joined04:40
Cromulent left04:40
quazimodo joined04:40
quazimod1 joined04:40
mdhopkins left04:41
huoxito left04:43
m0viefreak left04:43
Inside left04:44
simesy left04:44
m104 joined04:44
macmartine joined04:47
zacts joined04:48
ErKa left04:49
skorgon joined04:49
dreiss joined04:50
ghostlines joined04:50
bobdobbs joined04:51
zacts left04:52
AWinterman joined04:54
hahuang61 left04:56
daito joined04:56
purplevillage joined04:57
rbento joined04:59
daito left05:00
ej joined05:02
AWinterman left05:03
matanya left05:03
bits8mybytes joined05:04
dhruvasagar joined05:04
simesy joined05:04
bits8mybytes left05:04
the_cybersphinx left05:05
zacts joined05:07
purplevillage left05:07
nathancahill joined05:08
v0n left05:09
macmartine left05:10
Praise- joined05:11
Praise left05:12
iliketurtles joined05:13
Andrevan joined05:13
nathancahill left05:16
kcj joined05:17
zacts left05:17
jackdempsey left05:18
AWinterman joined05:18
joelpittet left05:19
hoschi joined05:19
nicedice left05:20
OOPMan joined05:22
fridim_ left05:24
Chikore left05:25
warthog9 joined05:25
daito joined05:26
michaelarestad left05:27
cha1tanya left05:28
bewest joined05:28
AWinterm_ joined05:30
tvw joined05:30
devoldmx_ joined05:32
cha1tanya joined05:32
pantsman joined05:35
Davey left05:35
pr0ton left05:37
tpollard left05:38
ntus1017 joined05:38
AWinterm_ left05:39
sajbar joined05:39
PaulCapestany left05:39
enr joined05:40
ThomasLocke joined05:40
train_or left05:41
jackdempsey joined05:41
PaulCapestany joined05:43
SuperDMP joined05:46
warthog9 left05:47
aldodelgado joined05:48
nilg joined05:51
Zeelot joined05:51
HelloShitty joined05:52
pantsman left05:53
babilen joined05:53
sajbar left05:54
babilen_ left05:55
GeertV left05:56
Spyro left05:57
fRAiLtY- joined05:57
rasto left05:57
Daniel joined05:57
DanielGuest9136105:57
lresende joined05:57
Guest91361sajbar05:57
lresende left05:57
whowantstolivefo left05:57
michaelarestad joined05:57
soee joined05:59
AWinterman left05:59
AWinterman joined06:00
fsvehla joined06:00
worstadm1n left06:00
fsvehla left06:00
loteriety left06:00
stliu joined06:01
hahuang61 joined06:01
Anders_J joined06:02
lavaman1 left06:02
galaris left06:03
lavaman joined06:03
lavaman left06:03
Spyro joined06:03
jargon joined06:04
AWinterman left06:05
AWinterman joined06:06
michaelarestad left06:07
Goplat left06:07
hahuang61 left06:08
papegaaij joined06:08
marthinal joined06:09
tasslehoff joined06:09
cbreak-work joined06:10
babilen_ joined06:11
ghostlines left06:11
worstadmin joined06:11
h0bbit joined06:13
h0bbit left06:13
HelloShitty left06:13
endiruna joined06:13
rurufufuss left06:14
babilen left06:14
AWinterman left06:16
staodd joined06:16
babilen joined06:16
stliu-s joined06:17
babilen_ left06:18
stliu left06:19
stliu-s left06:19
mckendricks left06:19
stliu joined06:20
AWinterman joined06:20
h0bbit joined06:25
endiruna left06:26
normanrichards left06:26
arvind_khadri joined06:27
rath joined06:27
vince_prignano joined06:28
scorphus left06:29
zbcm left06:29
pduin joined06:30
private joined06:31
jaequery left06:32
quazimodo left06:32
quazimod1 left06:33
aldodelgado left06:33
novile joined06:33
rob_w joined06:34
Carraway left06:35
ayaz joined06:37
cogitos left06:37
stliu left06:38
stliu joined06:38
ejnahc left06:38
ejnahc joined06:40
iliketurtles left06:40
enr_ joined06:41
babilen_ joined06:41
rudak joined06:41
_iron joined06:41
babilen left06:41
tasslehoff left06:42
enr_ left06:43
AWinterm_ joined06:43
shuaib joined06:43
enr_ joined06:45
babilen joined06:46
babilen_ left06:46
m104 left06:47
stfn left06:50
stfn joined06:50
babilen_ joined06:51
Cassiel left06:51
AWinterm_ left06:52
LekeFly joined06:52
LekeFly left06:52
devoldmx_ left06:52
babilen left06:53
ewnd9 joined06:54
_goTAN joined06:54
revyd joined06:54
beautifulmind left06:56
quimes joined06:56
jayfk joined06:57
tjbiddle left06:57
AWinterman left06:58
threesome left06:58
michaelarestad joined06:58
KernelPanicMK2 left06:59
Gooder joined07:01
quimes left07:01
GeertV joined07:01
quimes joined07:01
michaelarestad left07:03
SuperDMP left07:03
KernelPanicMK2 joined07:03
SamB joined07:05
emergion joined07:07
d3pwnd joined07:09
d3pwnd left07:09
rbento left07:11
benoit_ joined07:13
rudak left07:14
ktosiek left07:14
crater2150 left07:15
ktosiek joined07:15
chuckharmston left07:15
peper left07:15
rpg left07:15
chuckharmston joined07:16
rpg joined07:16
rudak joined07:16
ziddey left07:17
raf joined07:17
peper joined07:17
crater2150 joined07:18
TLH joined07:18
SuperDMP joined07:19
AWinterman joined07:19
ej left07:19
harish joined07:20
satazor joined07:22
Asenar joined07:22
Arokh[Off]Arokh07:24
benoit_ left07:26
gua_ould joined07:26
dfanjul joined07:27
matanya joined07:28
matanya left07:28
matanya joined07:28
AWinterm_ joined07:28
AWinterman left07:29
iamtakingiteasy left07:30
zacts joined07:31
Element9 joined07:31
jeffery_ left07:32
St_Marx left07:32
Plummer joined07:32
dreiss left07:33
maxmanders joined07:35
AWinterm_ left07:36
PaulCapestany left07:37
PigeonFriend joined07:38
zbcm joined07:39
SuperDMP left07:39
threesome joined07:41
PeterBooker joined07:44
harish left07:44
psoo joined07:46
Davey joined07:46
mishok13 joined07:47
alkino joined07:49
kcj left07:49
revyd left07:50
vince_prignano left07:50
ej joined07:51
Raging_Hog joined07:52
ology left07:52
cads left07:52
hyperair left07:53
hyperair joined07:53
cha1tanya left07:54
satazor left07:54
AWinterman joined07:55
ej left07:56
cha1tanya joined07:57
jackdempsey left07:57
tvw left07:58
exoon joined07:58
michaelarestad joined07:59
Balliad joined08:00
chuckf left08:00
enr left08:02
quazimodo joined08:02
_goTAN left08:02
quazimod1 joined08:02
theForce joined08:03
theForce hi08:03
michaelarestad left08:03
theForce i have 2 repositories A and B. is it possible to "merge" B into a folder in A so that the whole history is kept etc. but at the end there is only 1 repository A?08:04
jkremser joined08:04
jkremser left08:04
jkremser joined08:04
cbreak-work theForce: yes. subtree merging08:04
iveqy theForce: are the code in B a subset of A or is it the same code?08:05
AWinterman left08:05
tjbiddle joined08:05
chuckf joined08:05
iveqy theForce: !subprojects08:05
gitinfo theForce: So, you want to add git repositories inside of other git repositories? Well, you have four main options. First is to just do it, add the repo to the outer project's .gitignore, and treat them entirely separately. Best if they are entirely separate. Otherwise your best options are "!submodule", "!gitslave", and "!subtree". Try those commands in this channel, or in a PM to avoid flooding.08:05
tjbiddle left08:07
theForce ok thx guys08:08
kcj joined08:08
kewah joined08:08
simesy left08:08
skylamer` joined08:10
cschneid left08:10
nsanden left08:10
emergion left08:11
jackdempsey joined08:11
JeremyWei left08:12
nicholasruunu joined08:12
iamtakingiteasy joined08:14
lyang0 joined08:15
achadwick joined08:16
anonymuse joined08:16
quazimodo left08:17
quazimod1 left08:18
purplevillage joined08:18
nova_ joined08:19
jgornick left08:21
novile left08:21
bandroidx left08:22
bandroidx joined08:22
bandroidx left08:22
bandroidx joined08:22
jgornick joined08:22
hwrd|work left08:24
eijk joined08:25
tatsuya_o joined08:25
anonymuse left08:26
chris___ left08:28
michaelarestad joined08:30
jackdempsey left08:30
raging_swine joined08:31
AWinterman joined08:32
chris___ joined08:32
enr joined08:33
noname001 joined08:34
tirengarfio left08:34
michaelarestad left08:34
Raging_Hog left08:34
_goTAN joined08:35
gebi joined08:36
tirengarfio joined08:36
aChatir joined08:37
Marqin joined08:37
noname001 left08:38
mikecmpbll joined08:39
tirengarfio left08:40
raging_swine left08:40
tirengarfio joined08:40
kadoban left08:41
enr left08:41
noname001 joined08:41
noname001 left08:42
KernelPanicMK2 left08:42
dvor joined08:42
Sonderblade joined08:45
_goTAN left08:45
noname001 joined08:47
noname001 left08:47
nova_ left08:47
crane_work joined08:48
nilg left08:48
emergion joined08:48
nova_ joined08:48
Sonderblade git log master..X lists all commits made to feature branch X. but git diff master..X lists something else?08:49
marhaban joined08:49
harish joined08:49
noname001 joined08:49
noname001 left08:50
endiruna joined08:50
crane_work left08:50
crane_work joined08:50
valgrind joined08:52
crane_work left08:52
fuzzybunny69y left08:52
crane_work joined08:52
deuterium left08:52
cschneid joined08:52
_ikke_ Sonderblade: git diff diffs trees08:52
Sonderblade: so git diff A..B is the same as git diff A B08:53
noname001 joined08:53
crane_work left08:53
zz_michael_mbpmichael_mbp08:53
crane_work joined08:53
aChatir left08:53
babilen_babilen08:53
parcs_ left08:53
ntus1017 left08:54
LimeBlast joined08:54
Sonderblade _ikke_: so what is the equivalent git diff command to my git log then?08:54
fuzzybunny69y joined08:55
ntus1017 joined08:55
_ikke_ There is none, git diff does something different than git log08:55
weiyang left08:55
_ikke_ Sonderblade: You probably want git log -p08:55
SergeyPenkin joined08:56
Sonderblade _ikke_: no, i want the union of the diffs git log -p shows08:56
|Freeman| joined08:56
BitPuffin joined08:56
herdingcat left08:56
_ikke_ Sonderblade: git diff master...X08:57
note the three dots08:57
It's the same as git diff $(git merge-base master X) X08:57
noname001 left08:58
nilg joined08:59
flaguy48 left08:59
Sonderblade _ikke_: :) thanks, that works08:59
quazimodo joined08:59
quazimod1 joined08:59
thiago left09:00
cedeon joined09:01
rednaks joined09:02
carlos-huang left09:02
endiruna left09:05
emergion left09:05
endiruna joined09:05
arvind_khadri left09:06
hahuang61 joined09:06
purplevillage left09:07
OOPMan left09:08
quazimodo left09:09
quazimod1 left09:09
St_Marx joined09:09
gittish joined09:09
hahuang61 left09:10
OOPMan joined09:10
marhaban left09:12
bvi joined09:13
harish left09:13
z8z joined09:14
skylamer` left09:16
alexO joined09:17
SirFunk left09:18
johnkpaul left09:18
Forkk left09:18
saurabh joined09:18
Z3tta left09:18
johnkpaul joined09:18
Forkk joined09:18
cedeon left09:18
SirFunk joined09:18
Z3tta joined09:19
St_Marx left09:19
quazimodo joined09:19
quazimod1 joined09:19
aChatir joined09:20
dc5ala joined09:20
arvind_khadri joined09:22
DrNick left09:22
verysoftoiletppr joined09:22
Andrevan left09:23
DrNick joined09:23
NET||abuse left09:23
modInfo3 left09:26
tirengarfio left09:27
tirengarfio joined09:27
nilg left09:28
tirengarfio left09:29
shruggar joined09:29
michaelarestad joined09:30
cedeon joined09:31
tirengarfio joined09:31
OOPMan left09:33
deuterium joined09:33
tirengarfio left09:35
michaelarestad left09:35
tirengarfio joined09:35
OOPMan joined09:35
noname001 joined09:36
saintcajetan_ left09:36
dc5ala left09:36
NET||abuse joined09:36
emergion joined09:36
Sigma joined09:40
frogonwheels left09:41
dfanjul man config09:41
saintcajetan left09:42
mechanicalduck joined09:42
babilen left09:46
dfanjul hi all, is it possible to have something like @{upstream} but refering to the branch.<name>.pushremote or remote.pushdefault?09:47
babilen joined09:48
aChatir left09:49
zbcm left09:49
flippo left09:50
satazor_ joined09:51
tirengarfio left09:52
emergion left09:53
_goTAN joined09:53
tirengarfio joined09:53
parcs_ joined09:53
maroloccio joined09:53
tirengarfio left09:53
babilen_ joined09:54
babilen_ left09:56
babilen left09:56
emergion joined09:56
emergion left09:57
_Qman joined09:59
Raging_Hog joined09:59
beautifulmind joined10:00
michaelarestad joined10:01
michaelarestad left10:01
michaelarestad joined10:01
the_cybersphinx joined10:02
beautifulmind left10:02
beautifulmind joined10:03
tirengarfio joined10:05
michaelarestad left10:05
St_Marx joined10:06
szx joined10:07
valgrind left10:07
h0bbit left10:08
valgrind joined10:08
fr00ty joined10:10
charon dfanjul: afraid not. you could send an email about your workflow and why it needs this to the !list10:12
gitinfo dfanjul: [!mailing_list] The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist10:12
h0bbit joined10:12
tirengarfio left10:13
satazor_ left10:14
raf left10:14
emergion joined10:14
tirengarfio joined10:14
h0bbit_ joined10:15
matteo joined10:16
Chryyz left10:16
adhawkinsadhawkins-away10:17
tirengarfio left10:18
dfanjul charon: thanks10:18
tirengarfio joined10:21
babilen joined10:26
bvi left10:27
ntus1017 left10:28
|Freeman| left10:29
michaelarestad joined10:32
GT4066 joined10:32
godgodgodgo joined10:33
michael_mbpzz_michael_mbp10:33
fr00ty left10:35
gittish left10:35
michaelarestad left10:36
guns joined10:38
mikecmpbll left10:39
marhaban joined10:40
ayaz left10:40
godgodgodgo_ joined10:41
mechanicalduck left10:42
jast left10:42
kewah left10:42
szx` joined10:42
luc_ left10:44
babilen_ joined10:44
paul424 joined10:44
mutex_ joined10:45
jgornick left10:45
godgodgodgo left10:45
babilen left10:45
alkino left10:45
nehaljwani left10:45
saurabh left10:45
bgerber left10:45
catsup left10:45
ThomasLocke left10:45
HedgeMage left10:45
parcs_ left10:45
johnkpaul left10:45
kaictl left10:45
mutex left10:45
catsup joined10:45
z8z left10:45
jefflyne left10:45
GT4066 left10:45
Sigma left10:45
Forkk left10:45
bandroidx left10:45
johnkpaul joined10:45
szx left10:45
jefflyne joined10:45
jgornick joined10:45
bgerber joined10:45
HedgeMage joined10:45
Forkk joined10:45
bandroidx joined10:46
bandroidx left10:46
bandroidx joined10:46
ThomasLocke joined10:46
saurabh joined10:46
nehaljwani joined10:46
emergion left10:46
kaictl joined10:47
mechanicalduck joined10:47
parcs_ joined10:47
hyperair left10:48
arand_ joined10:48
Gue______ joined10:48
FreezingCold left10:48
zz_michael_mbpmichael_mbp10:48
nevyn left10:49
gitinfo left10:49
nevyn joined10:50
_ikke_ gitinfo down10:50
Droolio joined10:51
cha1tanya left10:51
prathamesh joined10:51
szx` left10:53
eijk_ joined10:56
nevyn left10:56
nehaljwani left10:56
nevyn joined10:57
Sigma joined10:57
emergion joined10:58
eijk left10:59
verysoftoiletppr left10:59
nevyn left11:02
michaelarestad joined11:03
nevyn joined11:03
marthinal left11:05
harish joined11:07
michaelarestad left11:07
jast joined11:08
robbyoconnor joined11:08
bvi joined11:09
theForce is it possible with subtree merging to completely eliminate the need for the 2nd repository? meaning i have 2 repositories A and B, and i want to "merge" B in a folder in A so that the history is kept and all the changes to B will be done in A/path/to/B => only 1 remaining repository, no need for e.g. "git pull -s subtree ..."11:09
gitinfo joined11:09
ChanServ set mode: +o11:09
selckin you can merge 2 repos without subtree11:10
r0bby_ left11:10
k_sze[work] left11:10
_ikke_ theForce: You can just do changed to A/path/to/B and commit that. No need to do that in the 2nd repository and merge back11:11
s/changed/changes11:11
arand yes, if all commits that you want will go into repo A from that point on, then B would not be needed anymore no, I've I've understood your reasoning?11:12
s/I\'ve/if/11:13
angelsl joined11:14
voiceofgrog left11:14
sgambino joined11:14
carlos-huang joined11:14
hellopat joined11:17
GeertV left11:18
GeertV joined11:18
exoon left11:19
exoon joined11:19
flaguy48 joined11:20
bvi left11:21
zhanglongyang joined11:22
bvi joined11:22
stliu_ joined11:22
GeertV left11:23
sgambino left11:24
daito left11:24
xpirator left11:25
theForce selckin: how can i merge 2 repos without subtree?11:25
stliu left11:25
echo-area left11:25
selckin add a remote and rebase11:26
theForce but how can i tell git to put that under a certain path?11:26
and will i keep the revision history from B?11:26
tinti left11:26
iveqy move it to that path first in repo B11:27
why wasn't subtree an option?11:27
selckin you'll keep the full history11:27
tinti joined11:27
arvind_khadri left11:28
spaceonline joined11:28
rasnor joined11:28
jeffery_ joined11:30
gittish joined11:32
marthinal joined11:32
theForce iveqy: subtree is an option. i was just reading about it and was under the impression that one always had to do "git pull -s subtree...", meaning changes to B would still be done in B's old repository11:33
michaelarestad joined11:33
iveqy theForce: that's one way to do it yes, but of course you could also do a subtree merge once and then only do updates in the common repo11:34
jon_r left11:35
mtk left11:35
stliu_ left11:35
Gue______ left11:36
stewiee joined11:37
mtk joined11:37
michaelarestad left11:38
kewah joined11:38
valgrind left11:39
flippo joined11:39
guns left11:41
Destos joined11:42
jon_r joined11:43
valgrind joined11:43
keller joined11:43
dbolser_ hihi11:43
I'm looking at filter-branch, I can't work out how to remove a single commit from my branch11:44
arvind_khadri joined11:44
dbolser_ trying: git filter-branch --commit-filter skip_commit a65398b11f27fa6f80e8f6b4c3e23d1832123e66 # but that don't work11:44
iveqy dbolser_: are you sure you aren't looking for git rebase -i?11:44
cbreak-work dbolser_: --commit-filter expects a string as command. no spaces.11:45
dbolser_: something it can execute directly11:45
dbolser_ iveqy: not sure at all really... my branch has diverged from production by a lot, so I'm just manually cherry picking a few changes applying them to dev and removing from my branch11:46
cbreak-work: so I should define the skip_commit shell function?11:46
cbreak-work write a program for it11:47
or a shell script11:47
iveqy dbolser_: then it's rebase -i you need11:47
dbolser_ I'm sure what I'm doing isn't right, I'm just 'tidying up' manually11:47
iveqy dbolser_: man git rebase11:47
gitinfo dbolser_: the git-rebase manpage is available at http://jk.gs/git-rebase.html11:47
dbolser_ a rebase feels like overkill here, since there are many conflicts11:47
arand left11:47
dbolser_ I just want to toggle a few settings in this code...11:48
perhaps I should try it and see...11:48
dfanjul left11:48
selckin rebase -i, will give you a list of commits, where you can just remove the commit from and close editor11:48
dbolser_ selckin: but I want to look at each one (i.e. diff) and decide11:49
selckin gitk <sha> &; git rebase -i <sha>11:49
maybe i'm just lazy11:49
iveqy dbolser_: then use gitk/tig/whatever first11:49
dbolser_ right, using rebase -i with gitk open11:50
cbreak-work dbolser_: you should be aware of the major goals of filter-branch11:50
simesy joined11:50
cbreak-work dbolser_: and how it works11:50
dbolser_: it will NOT remove the effect of commits11:50
it will merely remove the commit itself11:50
dbolser_ The thing is... gah.... I want to remove my commits from my branch one by one, apply them to the dev branch and push11:51
cbreak-work if you do it properly, it will look like the next commit performs both its own and the previous changes at once11:51
then don't use filter-branch11:51
dbolser_: man git-cherry-pick11:51
gitinfo dbolser_: the git-cherry-pick manpage is available at http://jk.gs/git-cherry-pick.html11:51
cbreak-work use that11:51
dbolser_ cbreak-work: yes, I want to reset the wd to undo the commit after filtering11:51
cbreak-work that's irrelevant11:51
dbolser_ cbreak-work: the issue with cp is that their are conflicts11:52
cbreak-work the working dir has nothing to do with it11:52
dbolser_: so?11:52
shuaib Is it normal for a "$git svn rebase" to take too long when checking out a newly created branch?11:52
cbreak-work resolve them11:52
dbolser_: you won't get around that.11:52
shuaib :q11:52
dbolser_ cbreak-work: it's easier to apply my change manually than to resolve a conflict11:52
SuperDMP joined11:52
dbolser_ s/apply/re-apply/11:52
nova_ left11:52
cbreak-work resolving the conflict IS applying the changes11:52
dbolser_ cbreak-work: I suppose11:53
how do I abort rebase -i?11:53
:q!11:53
cbreak-work rebase --abort11:53
dbolser_ ?11:53
I'm in the editor now11:53
Inside joined11:53
cbreak-work then just delete everything and :wq11:53
dbolser_ remove everything, the rebase will be aborted.11:53
ty11:53
cbreak-work yes.11:53
themsay joined11:53
dbolser_ OK, my tries cherry-picking11:54
wrouesnel joined11:54
dbolser_ hah... no conflicts on this one ;-) thanks11:54
bgerber left11:54
dbolser_ thank you all11:55
simesy left11:56
dbolser_ so now that commit x from branch z is in dev, will a rebase of z on dev 'do the right thing'?11:57
pdurbin left11:57
dbolser_ i.e. will the history of z be re-written to put x in a different place? I guess not11:57
bgerber joined11:57
cbreak-work dbolser_: x is not in a different place11:59
flippo left11:59
cbreak-work dbolser_: you now have a new commit that is similar to the original.11:59
the new is a copy of the effect, but likely has different tree, and of course has different parents11:59
d33tah why does git stash return to the system with 0 exit code if there was no stash created, because the working tree has no changes?12:00
cbreak-work if you rebase stuff, the rebase internal code will cherry pick commits as well (in -i mode)12:00
hellopat left12:00
cbreak-work if it notices that a commit has no effect (because you already cherry-picked it), that one gets dropped, and not copied12:00
d33tah: why not?12:01
the working dir is as you'd expect, and there's no error, so no point pretending there's one :)12:02
d33tah cbreak-work: i wrote an alias for git-svn12:02
dbolser_ cbreak-work: so the result is that branch z has x or the x' (copy)12:02
?12:02
d33tah it performs git stash, then does git svn dcommit and git stash pop12:02
arand joined12:02
d33tah i'd rather not have git stash pop if git stash didn't save anything12:02
hyperair joined12:03
dbolser_ d33tah: check git stash list12:03
in your script12:03
cbreak-work d33tah: just git diff before git stash12:03
canton7 there might be a stash from earlier - doesn't help?12:04
cbreak-work git diff can give you an exit code12:04
dbolser_ oh12:04
canton7: right12:04
Gu_______ joined12:04
d33tah cbreak-work: thanks!12:04
michaelarestad joined12:04
rudak left12:05
valgrind left12:06
saurabh left12:06
d33tah canton7: git diff kept returning zero.12:08
ah, git diff --exit-code12:08
michaelarestad left12:09
emergion left12:09
rurufufuss joined12:10
BitPuffin left12:10
dhruvasagar left12:10
bvi left12:11
cbreak-work yes. I said that :)12:11
bvi joined12:12
rfoust_ left12:12
BitPuffin joined12:12
flippo joined12:12
PsySc0rpi0n joined12:15
IrishPrime joined12:16
Destos left12:17
_goTAN left12:17
angelazou joined12:17
angelazou quick question, I'm getting this error when I try to commit12:17
error: pathspec did not match any file(s) known to git.12:17
cbreak-work angelazou: user error.12:18
angelazou as in I didn't authenticate?12:18
shuaib left12:18
elixir joined12:18
cbreak-work no12:18
as in you typed wrong stuff12:18
angelazou oh crap...you're right12:19
forgot the -m option12:19
exoon left12:19
cbreak-work ... that's not important12:19
just type "git commit"12:19
freestyl3r left12:19
cbreak-work -m is just for lazy people who can't be bothered to write non-crappy commit messages :)12:19
angelazou yeah, I know, I added a message without the -m option12:19
exoon joined12:19
angelazou thanks12:20
angelazou left12:20
mdhopkins joined12:20
freestyl3r joined12:20
cbreak-work np :)12:20
freestyl3r left12:21
mechanicalduck left12:23
rudak joined12:23
breakingthings joined12:24
g3orge joined12:24
HenryG joined12:25
ewnd9_ joined12:26
themsay left12:26
normanrichards joined12:27
ewnd9 left12:27
SicoWork left12:27
Will| joined12:28
HariboPenguin|Of left12:28
Seveas left12:28
Asenar left12:29
enr_ left12:29
sonOfRa left12:29
adamm left12:29
Nevik left12:29
sonOfRa joined12:30
ncd|leeN left12:30
Hoosier2016 joined12:30
midnightmagic left12:30
flippo left12:30
ncd|leeN joined12:30
ncd|leeN left12:30
Inside left12:30
shihan left12:31
Mogget left12:31
adamm joined12:31
xSmurf left12:31
shihan_ joined12:32
SeoZ2SeoZ-work[AWAY2]12:32
normanrichards left12:32
_goTAN joined12:32
xSmurf joined12:32
reim_reim12:33
simesy joined12:33
godgodgodgo_ left12:34
enr joined12:34
midnightmagic joined12:34
dougsland joined12:34
SicoAnimal joined12:35
HariboPenguin|Of joined12:35
Seveas joined12:35
Nevik joined12:35
michaelarestad joined12:35
HariboPenguin|OfHariboPenguin12:35
Asenar joined12:36
elixir left12:37
anonymuse joined12:37
dfanjul joined12:38
enr_ joined12:38
pdx joined12:38
kcj left12:38
Mogget joined12:39
jerius joined12:40
michaelarestad left12:40
miluz joined12:41
enr left12:41
miluz left12:41
PsySc0rpi0n left12:42
rfoust joined12:43
enr_ left12:43
enr joined12:43
rshetty joined12:43
Jenser joined12:43
kukks joined12:44
kukks left12:44
kukks joined12:44
Will| left12:44
jon_r left12:44
babilen_babilen12:45
sriracha left12:45
alexO left12:45
Hoosier2016 left12:45
Jenser left12:46
BitPuffin left12:46
DolphinDream joined12:46
devoldmx3 joined12:47
BitPuffin joined12:47
simesy left12:47
simesy joined12:48
devoldmx left12:49
Will| joined12:49
alkino joined12:49
Will| left12:50
flippo joined12:51
zhanglongyang left12:51
paul424 left12:53
Raging_Hog left12:53
Entomo left12:53
ewnd9_ left12:53
oliveiraev joined12:55
ewnd9 joined12:55
marhaban left12:55
satazor_ joined12:58
freeed joined13:00
_goTAN left13:01
dgx joined13:02
dgx Hey all. When I try to do : git push upload master I get an error: The program can´t start because libcurl-4.dll is missing. How can I fix that? I have installed SourceTree13:03
Jenser joined13:04
devoldmx3 left13:04
rshetty left13:04
g3orge left13:06
michaelarestad joined13:06
imarcusthis- left13:06
michael_mbpzz_michael_mbp13:06
noname001 left13:06
dsdeiz_ joined13:06
dsdeiz left13:07
devoldmx joined13:07
ZujkisNx joined13:09
flaguy48 left13:10
iveqy dgx: install libcurl, however sourcetree should probably already done that for you since libcurl isn't a standard software on a linux system13:10
*windows system13:10
so I suggest you first try to reinstall sourcetree13:10
Hoosier2016 joined13:10
michaelarestad left13:10
wakeup joined13:11
dgx iveqy, SourceTree is the 3rd re-install, I´ve tried one more beforehand(after second re-install, i did reboot) - still the same13:11
wakeup ez13:11
is there a way to pull to a bare repo?13:11
Jenser left13:11
_ikke_ pull to?13:11
kermit left13:11
_ikke_ It's either push to, or pull from13:11
dsdeiz joined13:11
Will| joined13:12
iveqy wakeup: you should be able to fetch to it, but pull to it I don't think you can, merging without a worktree would be difficult if you've a conflic.13:12
_ikke_ Either way, there is no difference between a bare repo and a non-bare repo in that regard13:12
wakeup git pull13:12
fatal: /usr/libexec/git-core/git-pull cannot be used without a working tree.13:12
_ikke_ wakeup: correct13:12
dsdeiz_ left13:12
t0by joined13:12
_ikke_ what iveqy said13:12
flaguy48 joined13:12
iveqy wakeup: however you should push to the bare repo and pull from it, as _ikke_ said13:12
t0by Hi, I'm sorry, I'm working on a branch of a fork of a repo13:12
wakeup ah ok thanks, so I just fetch13:12
noname001 joined13:12
kermit joined13:12
_ikke_ wakeup: yes13:12
t0by upstream:master has been changed in a way that my work is now unmergeable13:13
iveqy dgx: well file a bug-report to sourcetree and install libcurl manually13:13
_ikke_ pull = fetch + merge. A bare repo can fetch, but not merge13:13
t0by what do I do now to get my branch mergeable?13:13
iveqy wakeup: !xy13:13
gitinfo wakeup: Woah, slow down for a bit. Are you sure that you need to jump to that particular hoop to achieve your goal? We suspect you don't, so why don't you back up a bit and tell us about the overall objective...13:13
Werring left13:13
_ikke_ t0by: What do you mean, not mergable?13:13
t0by Some critical parts have been changed13:13
dgx iveqy, right, digging into it13:13
konundra joined13:13
_goTAN joined13:13
t0by So a merge would simply not make sense13:14
prathamesh left13:14
t0by I need to manually update a few files13:14
Destos joined13:14
t0by But fiorst I need to get them from upstream13:14
wakeup iveqy: I work on a repo hosted on github, my local workflow is to have working copies and bare repositories that get backed up. I wan't a bare repo in between my working copy and github to protect me against data loss.13:14
GeertV joined13:14
_ikke_ t0by: fetch13:14
t0by how do I do that without disrupting my entire local branch?13:14
simesy left13:14
t0by I've fetched, but then?13:14
cherry-pick?13:14
Werring joined13:14
_ikke_ for example13:14
wakeup normally, no-one but me pushes to the repos, so I just use github as a mirror if I have to, but in this case I want to sync with whatever my client does on github13:15
Mowsh joined13:15
angelazou joined13:15
t0by so git pull upstream; git checkout master; git log, see what I need, git checkout mybranch; git cherry-pick interesting_commit; manually edit?13:15
iveqy wakeup: oh so you want a bare repo to mirror the github one? Well then I guess fetch is a good way. There's also man git clone --mirror but if the github repo gets corrupted your mirrored repo could be corrupte too13:16
gitinfo wakeup: the git-clone manpage is available at http://jk.gs/git-clone.html13:16
_ikke_ t0by: s/pull/fetch13:16
Milossh joined13:16
dsdeiz left13:17
devoldmx left13:17
trungqtran joined13:17
michaelarestad joined13:17
Mode-M joined13:17
devoldmx joined13:18
staodd left13:19
t0by Thanks _ikke_13:19
ZujkisNx left13:19
lamarus joined13:20
ZujkisNx joined13:20
cagedwisdom left13:21
ewnd9 left13:22
angelazou hi, I'm having trouble with a pull request in github13:22
I have already forked and make new commits to my repo13:22
and when submitting a pull request, they don't show up in the diff13:22
_ikke_ selected the correct branch for the pull request?13:23
angelazou I think so, both are masters13:23
iveqy angelazou: the pull request doesn't show up in the diff?13:23
untaken joined13:24
beautifulmind left13:24
_goTAN left13:24
angelazou iveqy: it shows up some diff, but not my diffs13:24
untaken can I add a directory with . at the beginnning? for instance .vim . I have tried but doesn't look like it's getting added?13:24
iveqy untaken: yes you can !repro13:24
gitinfo untaken: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.13:24
_ikke_ untaken: is it an empty directroy?13:25
directory*13:25
hellopat joined13:25
untaken _ikke_: there is a directory in .vim , but no files *yet*13:25
iveqy angelazou: sorry but I don't understand. Could you !repro13:25
gitinfo angelazou: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.13:25
_ikke_ untaken: git doesn't track directories13:25
untaken ahh so a file must exist in there13:25
_ikke_ untaken: yes13:25
untaken never knew that :)13:25
zz_michael_mbpmichael_mbp13:26
untaken thanks _ikke_13:26
devoldmx left13:26
devoldmx joined13:26
angelazou it's in the root directory13:26
I think I'll try again tomorrow13:26
it might be that I just made the commit13:26
michaelarestad left13:27
devoldmx3 joined13:27
michaelarestad joined13:27
jrex joined13:27
tmcmahon joined13:28
iveqy angelazou: the commit should be showed instantly13:28
GarethAdams left13:28
_ikke_ But you have to push it first13:28
satazor_ left13:29
ojacobson joined13:29
devoldmx left13:30
satazor_ joined13:30
natechan joined13:30
v0n joined13:31
michaelarestad left13:31
carlos-huang left13:31
aldodelgado joined13:33
aldodelgado left13:33
GarethAdams joined13:34
satazor_ left13:34
_goTAN joined13:34
Christi123 joined13:35
untaken how do you make an alias to another git account? For instance, if I want a directory to contain another repo, without copying the files and then committing them. Like on this page https://github.com/vgod/vimrc/tree/master/bundle how is this done?13:36
BSaboia joined13:36
iveqy untaken: !submodules13:37
gitinfo untaken: [!submodule] git-submodule is ideal to add subsidiary git repositories to a git superproject when you do not control the subprojects or more specifically wish to fix the subproject at a specific revision even as the subproject changes upstream. See http://book.git-scm.com/5_submodules.html13:37
_ikke_ !submodules13:37
gitinfo [!submodule] git-submodule is ideal to add subsidiary git repositories to a git superproject when you do not control the subprojects or more specifically wish to fix the subproject at a specific revision even as the subproject changes upstream. See http://book.git-scm.com/5_submodules.html13:37
decotii joined13:37
cbreak-work untaken: git doesn't have accounts :/13:37
dhruvasagar joined13:37
kesha joined13:37
untaken thanks :)13:37
mike_af joined13:37
dgx left13:40
ewnd9 joined13:40
ewnd9 left13:41
ewnd9 joined13:41
m0viefreak joined13:41
mdhopkins left13:41
Hoosier2016 left13:42
w0ng left13:44
mechanicalduck joined13:44
valgrind joined13:44
kesha left13:44
kesha joined13:46
flippo left13:47
adamwathan joined13:50
nova_ joined13:50
freestyl3r joined13:50
Raging_Hog joined13:51
TeckniX joined13:51
angelazou left13:53
geekbri joined13:53
scorphus joined13:54
glosoli joined13:54
Hoosier2016 joined13:55
cedeon left13:55
sriracha joined13:55
methods joined13:56
methods left13:58
michaelarestad joined13:58
soee left14:00
Raging_Hog left14:00
kesha left14:00
dhruvasagar left14:00
cizra joined14:01
vedranm joined14:01
LuxuryMode joined14:01
dhruvasagar joined14:02
ikuraj joined14:02
tmcmahon left14:02
kesha joined14:03
ZujkisNx left14:03
devth joined14:04
cizra Hi! git-svn is giving me headaches. I'm trying to set up a new branch to track a SVN branch, and it tells me that the upstream thingy is not a branch. For example, git branch --set-upstream-to=trunk master says "fatal: Cannot setup tracking information; starting point 'trunk' is not a branch.". I distinctly remember this stuff working before.14:04
CheckDavid joined14:04
cizra I've got a rather recent SVN (1.8 series), maybe this changed something?14:04
PigDude joined14:05
PigDude I have a weird issue: I can SSH to my server, but I cannot clone over SSH14:05
cizra git-svn version 1.8.3.4 (svn 1.6.18)14:06
PigDude this just recently started happening so I find it confusing14:06
git clone -v ... produces no more output14:06
(than without -v)14:06
kesha_ joined14:06
cizra PigDude: Check the logs on server side? Maybe they disabled scp or something.14:07
PigDude cizra, it is my server, OK14:07
cizra, indeed the server i cam clonign from, I am messaging you from right now over a pubkey authenticated ssh session14:07
gusnan joined14:08
ojacobson PigDude: did you add something to your .bashrc that generates output on stdout, or that can fail?14:08
kesha left14:08
asmacdo joined14:08
PigDude cizra, ah, it was using another username14:08
cizra, I think it is too early on a monday :(14:08
thanks guys14:08
asmacdo left14:08
normanrichards joined14:09
PigDude left14:10
cedeon joined14:10
sqlnoob left14:11
acharlieh joined14:13
quimes left14:13
kesha_ left14:14
infogulch left14:15
BitPuffin left14:15
kewah left14:16
bvi left14:16
dfanjul left14:16
dfanjul joined14:17
GT4066 joined14:17
kesha_ joined14:18
kewah joined14:18
michaelarestad left14:20
nkambo left14:20
simesy joined14:21
onethfour how do i rebase a branch against master?14:21
ojacobson onethfour: what did you try? :)14:22
infogulch joined14:22
rickruby left14:22
ojacobson (I'm asking because the obvious answer is the correct answer, so I'm assuming that didn't work)14:22
Hoosier2016 left14:22
dfanjul left14:22
kesha_ left14:22
onethfour i didnt try anything, but the idea is that I want the updated master, correct? rather than the master a few weeks ago when i initially created the branch14:23
JosephSilber joined14:24
m104 joined14:24
dfanjul joined14:26
simesy left14:26
jeffery_ left14:26
SmokeyD joined14:27
ojacobson left14:27
SmokeyD hey all. How do I see all the commits for a specific branch? Right now, when I do git log on a checked out branch, I see commits on other branches as well, and the log also goes back before the branch was created.14:27
ErKa joined14:28
ojacobson joined14:29
mklappstuhl joined14:29
bestform SmokeyD, of course it does. it's the list of linked commits starting from your current ref. it doesn't care if there are ones with more than one parent (eg. a branch was created). therefore you might see commits from other branches, if they are reachable from your current ref14:29
offby1 smokeyd: something like "git log branch-im-interested-in...some-other-branch" will show only commits after the "merge base"14:30
cbreak-work SmokeyD: all commits in a branch are all commits reachable from the branch tip.14:30
papegaaij left14:30
onethfour crud, i did git rebase master, but now it has several merge conflicts (with files i never even modified)14:30
cbreak-work in particular, the initial commits are reachable from the branch tip14:30
dsdeiz joined14:31
SmokeyD I just want to see how did what, when on a specific branch. So I would like to see all commits that were done on a specific branch. I don't care whether or not they have been merged to another branch.14:31
offby1 smokeyd: you might be interested in the reflog14:32
nkambo joined14:32
jerrad joined14:33
infogulch left14:33
pen left14:33
bestform SmokeyD, you have to understand, that a branch is nothing but a ref on a particular commit, not a range of commits or something like that.14:33
tatsuya__ joined14:34
SmokeyD bestform: ok, but can't I see the all commits with that specific ref.14:34
offby1: you might be right, thanks. I am checking whether it is what I need (didn't know it)14:34
bestform SmokeyD, that's just one commit. what offby1 said should get you to where you wanna be :)14:35
pen joined14:35
infogulch joined14:35
offby1 smokeyd: actually, I, and I suspect most long-time gitters, simply don't want to do exactly what you want to do. We are more likely to be interested in all the commits leading up to a given point, regardless of which branch was current when those commits were made14:36
tatsuya_o left14:36
offby1 other than the reflog, git doesn't even record that information.14:36
Sendoushi joined14:36
offby1 you can check out a branch based on master, make one commit on it, merge it into master, then delete the branch. If the merge was fast-forward, as far as I can tell, there will be no trace left of the new branch14:36
Underbyte left14:37
offby1 so I think the lesson is: git doesn't consider branches to be interesting historically; they're more a convenience for the present.14:37
Sendoushi hey guys. i'm thinking here... I'm starting using git on my workflow and deciding what is best as a gui. it seems to me the gui is the best approach to me but... tell me wrong. for now, i'll use mostly local git14:37
SmokeyD hmm, I need it for administrative purposes right now. But when I do a commit, git recods the branch on which the commit was done right? SO can't you know all the commits on a specific branch? I mean, how else can you roll back bunch of commits on a branch if you don't know which commits were done on which branches?14:37
Sendoushi here i was checking the git official app and the tower app... what do you think?14:38
exoon left14:38
babilen_ joined14:38
babilen left14:39
offby1 smokeyd, no. Other than the reflog, git does _not_ record the current branch when you make a commit. That's my point.14:39
devoldmx3 left14:39
cbreak-work git doesn't care on which branch a commit is made.14:40
you can make commits even on no branch at all14:40
offby1 nods vigorously14:40
Davey left14:40
EugeneKay git is an unloving divorcee14:40
cbreak-work and by virtue of merging (one of git's great super powers), commits can be in many branches at the same time14:40
offby1 git treats me right!14:40
EugeneKay Just wait until your money runs out, honey.14:41
offby1 an unloving, promiscuous divorcee.14:41
lavaman joined14:41
SmokeyD cbreak-work: why do you branch then? If you checkout a branch, how does git then determine what the code should look like, if it doesn't know which commits have been done?14:41
offby1 smokeyd: checking out a branch does not cause git to forget which commits have been done.14:41
!gcs14:41
gitinfo [!concepts] "Git Concepts Simplified" explains the basic structures used by git, which is very helpful for understanding its concepts. http://gitolite.com/gcs/14:41
EugeneKay SmokeyD - I recommend reading through !concepts to get a handle14:41
gitinfo SmokeyD: "Git Concepts Simplified" explains the basic structures used by git, which is very helpful for understanding its concepts. http://gitolite.com/gcs/14:41
offby1 !cs14:41
gitinfo "Git for Computer Scientists" is a quick introduction to git internals for people who are not scared by phrases like Directed Acyclic Graph. http://eagain.net/articles/git-for-computer-scientists/ See also !concepts !bottomup14:41
SmokeyD offby1: you say "other than the reflog". I see the reflog, but what exactly is it?14:41
EugeneKay Shit, beaten.14:42
offby1 eugenekay jinx14:42
EugeneKay nou14:42
kewah left14:42
cbreak-work SmokeyD: git can find out which commits are on a branch, but it can't find out (easily) on which branch a commit is14:42
offby1 smokeyd: it's a simple log of every commit to which a particular ref has ever "pointed".14:42
cbreak-work because a branch points to its commits14:42
nafg_ joined14:42
cbreak-work but commits have no clue by which branches they are pointed at14:42
michaelarestad joined14:42
cbreak-work there could be thousands that your repository isn't even aware of14:42
babilen_babilen14:43
Kronuz good morning14:44
offby1 "which branches point to them" would be a better phrasing.14:44
remember, branches are Post-It notes14:44
Dougie187 joined14:45
ikuraj left14:45
cbreak-work offby1: there's a difference?14:45
offby1 rubs chin14:45
gasbakid joined14:46
offby1 sure. A branch just comes out and tells you "I point to commit 0xdeadbeef". A commit says no such thing14:46
it's a one-way arrow, just like commits point to their parents but not to their children.14:46
PerlJam ..oO( It says "I *AM* 0xdeadbeef" ;-)14:46
m104 left14:46
offby1 gets all philosophical14:46
valgrind left14:47
offby1 perljam: surely HEAD, typically, is more "points to" than "is".14:47
Also: Long Time No See14:47
PerlJam yeah, greetings! :)14:47
SmokeyD offby1: ok, I start to understand I think. A branch points to a commit, not the other way around. And by doing more commits, you just change the commit that a specific branch points to.14:48
jepler joined14:48
_ikke_ SmokeyD: correct14:48
offby1 yep14:48
SmokeyD does the reflog record which commits a specific branch has ever pointed to?14:48
offby1 the "checked out" branch is, more or less by definition, the one that "moves along with you" as you make commits.14:49
adamwathan left14:49
_ikke_ And the branch being updated is the one being pointed to by HEAD14:49
offby1 the others stay put.14:49
heh14:49
_ikke_: jinx-o-rama14:49
_ikke_ SmokeyD: yes14:49
ZujkisNx joined14:49
offby1 where else do you get three or four teachers fighting each other to best explain?14:49
_ikke_ whaha :D14:49
SmokeyD _ikke_: strange to talk to ikke. I am not talking to myself ;)14:49
jepler so as I often do, I just wrote 'git for-each-ref upstream.. | while read ref; do git checkout ref; do something; done' and then when I'm done I have to remember the name of the branch I left14:49
_ikke_ SmokeyD: ;-)14:49
SmokeyD but thanks14:49
valgrind joined14:50
offby1 jepler: !reflog14:50
gitinfo jepler: The git reflog (`git log -g`) records the SHAs of your HEADs for 2+ weeks. `git checkout -b myrestore OLDSHA` and `git reset --hard OLDSHA` will relink to that state via a new and current branch respectively, see http://sethrobertson.github.com/GitFixUm/ for full details. WARNING: reset --hard will trash any uncommitted changes! Visualize with: gitk --all --date-order `git log -g --pretty=%H`14:50
jepler (whoops, git checkout $ref) is there a way to push/pop the current branch to return to it after some git checkouts? or is there a different idiom I should use?14:50
devoldmx joined14:50
offby1 jepler: I don't think I've ever passed an argument to "git for-each-ref". Does that filter the output?14:50
SmokeyD ok, the reflog only records 2+ weeks.14:50
that is why I saw so little14:50
that is a shame14:50
jepler err apparently my example was wronger than I thoght14:50
git rev-list upstream.. | while read $ref14:50
offby1 jepler: there's "git checkout -" but that only does what I want about half the time14:50
verysoftoiletppr joined14:51
_ikke_ jepler: Not something you can control yourself. There is git checkout - to checkout the previous branch, or git checkout @{-N} where N is the n'th previous branch14:51
dhruvasagar left14:51
PerlJam jepler: or you could just write the current commit/branch to an environment var and check it out when you're done :)14:52
jepler ah maybe I should be using git rebase --exec14:52
offby1 smokeyd: I assume you can tell git to keep more in the reflog. Not after the fact, of course :)14:52
SmokeyD :(14:52
that is a shame, that git throws away meta data14:52
git reflog show14:52
oops14:52
PerlJam SmokeyD: if you've munged stuff that you need your reflog from a long time ago, you've done seomthing horribly wrong.14:52
SmokeyD wrong window14:52
:)14:52
rickruby joined14:52
_ikke_ You can also modify to period the reflog keeps items I believe14:53
kesha_ joined14:53
_ikke_ default is btw 90 days, not 1414:53
jepler ah yes, GIT_EDITOR=true git rebase --no-autosquash -i --exec "do something" upstream14:53
offby1 smokeyd: I have the vague sense that You're Doing It Wrong™. I.e., you want to know "on what branch was this commit made" only because you're confused14:53
if you explain in detail why you want this, perhaps someone here can suggest a better way to get what you want14:53
joshsmith joined14:54
SmokeyD offby1: I am trying to find out what I spent my time on :) So how many commits I did on which branch, and when14:54
dfanjul and 30 days for unreachable objects14:55
michael_mbpzz_michael_mbp14:55
offby1 smokeyd: might you not answer that question just as well by simply noting the _files_ that you changed, and _how_ you changed them?14:55
mckendricks joined14:55
offby1 do you want to attribute your work to (say) bugs in a bug tracker? I.e., I spend three hours on bug #12314:55
SmokeyD offby1: not _how_ because then I need to go back 2 months and read all the commits and figure out for which specific branch (read: project) they were relevant.14:56
offby1 yeah I gotcha14:56
verysoftoiletppr left14:57
kevwil joined14:57
offby1 in fact I understand you so well that I'm now wondering why this question doesn't come up more often. I don't have an answer.14:57
SmokeyD :)14:57
offby1 One semi-crappy way might be: always put the "project name" in the commit message14:57
SmokeyD offby1: as many will understand: I am way behind on recording my worked hours. I have the log of when I was working, but not what I was working on, so I am trying to defer that from the commit logs14:58
offby1 another: always do your merges to master with "--no-ff", so that the commit graph plainly shows those separate work items as diverging and then merging streams of commits14:58
pduin left14:58
offby1 ooooh you're a consultant, eh?14:58
shinnya joined14:58
PerlJam SmokeyD: just remember that git is a VCS, not a "what did I work on last month" system ;)14:58
SmokeyD PerlJam: you are right, but I am way to lazy14:59
offby1 smokeyd: yeah, you're gonna have to improvise something to scrape data from the past, and then you're gonna have to have some discipline in recording that info in the future.14:59
jaequery joined14:59
Milossh left14:59
SmokeyD I still might be able to defer it from trac (which we use) and see the trac logs. :)14:59
offby1 you might well use separate repositories for separate clients.14:59
sriracha left14:59
offby1 that probably wouldn't help any, now that I think about it15:00
SmokeyD offby1: i am not really a consultant, but my boss does want to know what I roughly spent my time on15:00
offby1 unless you never merged 'em in which case what's the point ...15:00
SmokeyD offby1: I did merge them :)15:00
offby1 where I work we use JIRA for that.15:00
SmokeyD offby1: ok. I am going to figure out know if trac did store all the commits. I think it does, and maybe also some extra info on it.15:01
PerlJam SmokeyD: the only time I've been able to really keep track of exactly which projects I worked on when, is when I was absolutely religious about recording when I switched from one to another and what they were.15:01
rickruby left15:01
offby1 I find that I can never tell how log I was working on something by just looking at commits. I can certainly see that I committed some relevant work at a few instants, but it's not at all clear if I was working _continually_ in the in-between times, or maybe off doing something else in some other repo15:01
nsanden joined15:02
tjbiddle joined15:02
thiago joined15:02
boblee left15:03
SmokeyD offby1: I already know how many hours I have worked in total. So I just need to divide those roughly per branch, which I can do by knowing how many commits I did per branch. That is accurate enough. It doesn't have to be precise15:03
mishok13 left15:03
SmokeyD But I think I already found it in trac15:03
matanya left15:04
Milossh joined15:04
Noldorin joined15:06
Hoosier2016 joined15:07
loteriety joined15:07
exoon joined15:09
cbreak-work left15:09
sriracha joined15:09
loteriety left15:09
ikuraj joined15:10
kevwil_ joined15:11
gasbakid left15:11
roots47 joined15:11
roots47 Hey all, after you complete a merge manually and your branch still says you're on (master|MERGING)... how do you get out of merge mode?15:12
Hey all, after you complete a merge manually and your branch still says you're on (master|MERGING)... how do you get out of merge mode?15:12
exoon left15:13
duch_kazatel joined15:13
kevwil left15:13
duch_kazatel left15:13
CheckDavid left15:14
canton7 roots47, then you haven't completed the merge15:14
What have you done?15:14
duch_kazatel joined15:14
duch_kazatel left15:14
boblee joined15:15
roots47 canton7: nevermind, all set15:15
canton7 (you need to 'git commit' after adding all files)15:15
_Qman left15:17
arvind_khadri left15:18
rath left15:20
MasterBob joined15:22
szx joined15:22
MasterBob Hello. so I have one repository for many small tools. I'd like to have a master branch (which has stable versions of the tools) and then individual branches for each of the tools where features will be fixed and bugs removed. Only merge stable tools to the master branch. Does that sound like a good plan?15:23
Element9 left15:23
ThomasLocke left15:25
roots47 Hey all, after completing a merge and committing, i notice my commit history looks pretty messy. Any tips on using rebase for a newb?15:26
enr left15:26
dhruvasagar joined15:26
ToBeFree joined15:26
melee left15:27
marhaban joined15:27
szx left15:27
AWinterm_ joined15:28
rob_w left15:29
GeertV left15:29
acharlieh left15:29
threesome left15:29
GeertV joined15:29
osse /615:30
arand_ left15:30
cizra roots47: First tip, never rebase anything you've published.15:31
roots47 cizra: it's not published15:31
cizra: it's committed locally, not pushed15:31
cizra MasterBob: Sounds cool. Did you know about the octopus merge?15:31
roots47: Then erase the merge, check out the branch, rebase on top of master and fast-forward master :-)15:32
psoo left15:32
gua_ould left15:32
cizra I can elaborate on the steps as needed.15:32
roots47 cizra: that would be good... let's start with step one :D15:32
cizra What are the names?15:32
marhaban left15:32
cizra .. of the branches. And what do you want to merge into what?15:32
marhaban1 joined15:32
AWinterm_ left15:33
roots47 cizra: so basically i just did a merge by running 'git pull origin master'15:33
acharlieh joined15:33
cizra oh15:33
mechanicalduck left15:33
cizra THAT is much easier to fix15:33
roots47 cizra: I had to complete a manual merge on one of the files15:33
cizra git reset --hard HEAD^ (deletes the latest commit, which in your case is a merge)15:33
git pull --rebase15:33
..aaaand you'll have to re-do the manual merge, 'fraid.15:33
jkyle left15:33
GeertV left15:33
cizra during rebase, it'll abort and say that something needs manual work15:34
BUT you can save a backup copy of your manually merged file!15:34
then restore it (instead of manually resolving the conflicts) and git rebase --continue15:34
roots47 cizra: no worries, it wasn't a big merge15:34
arvind_khadri joined15:34
cizra Well, task 1: erase merge15:34
roots47 cizra: real quick though, before moving on... I ran the command you just said, things are back to where i started before pulling15:34
cizra yes, that's intended15:34
task 2: pull with rebase15:35
git pull --rebase15:35
roots47 cizra: now, i actually have two commits that should be combined into one15:35
dreiss joined15:35
cizra no, you said the other commit was on origin/master?15:35
carpii joined15:35
cizra Squashing commits together is easy too: git rebase -i origin/master15:35
jefflyne left15:35
roots47 cizra: in my local commit history, my previous two commits have the exact same commit message, but the latter has a small change i missed15:36
cizra then edit the list that pops up -- replace "pick" with "f" or "s" (s retains commit messages of both, f only of the first)15:36
In your case, you want f15:36
trungqtran left15:36
carpii i have a large number of stashes, some of which i suspect have long since been merged into master. Is there any way I can scan over each stash and decide whether they would change master if applied ?15:36
Christi123 left15:36
roots47 cizra: that will only be for the previous two commits? or15:36
Christi123 joined15:36
dvor left15:37
cizra roots47: Did you run git rebase -i origin/master?15:38
I don't get your question.15:38
jefflyne joined15:38
sriracha left15:39
roots47 cizra: yes, it opens VI with two lines, they both say pick hash message15:39
mmlac-bv joined15:40
roots47 cizra: ah, sorry I missed your message above15:41
cizra yeah, well, the upper one is your first commit, I think. The lower one is the second15:41
change the "pick" into "f15:41
chuckharmston left15:42
hyperair left15:42
arand left15:42
roots47 cizra: did that, it said "Cannot 'fixup' without a previous commit'15:42
konundra left15:42
Hoosier2016 left15:43
canton7 roots47, you have to rebase -i onto at least one commit *before* the one you want to fixup15:43
so the first commit in the editor window is a 'pick', not a 'fixup'15:44
roots47 canton7: I just tried running the command again, deleted the old rebase, but now instead of having two commits listed it just says 'noop'15:44
canton7 then you didn't ask it to do anything. are you sure you unwound the old rebase properly?15:45
devoldmx left15:45
roots47 canton7: I ran the command git recommended to delete it 'rm -fr path'15:45
melee joined15:45
rickruby joined15:45
canton7 'it'?15:46
roots47 canton7: the rebase15:46
canton7 what? a rebase isn't a path15:46
roots47 canton7: the rebase merge directory15:46
devoldmx joined15:46
canton7 git recommended that, instead of 'rebase --abort'?15:46
groglogic joined15:46
cizra roots47: You should have changed the _second_ commit to a fixup. The timeline is top (old) to bottom (new).15:47
roots47 canton7: ugh, yeah maybe I shouldn't have deleted that, hah15:47
canton7: now when I try git rebase --abort it just says "No rebase in progress?"15:47
canton7 I'm just curious where you got that recommendation from15:47
Nicholas_Rishel joined15:48
canton7 it may well have worked, I'm just surprised15:48
roots47 canton7: http://pastie.org/820855315:48
trungqtran joined15:48
Devastatr joined15:49
Devastatr left15:49
Devastatr joined15:49
Hoosier2016 joined15:49
kevwil joined15:49
canton7 how did you manage to get that? run rebase -i with a rebase -i already in progress?15:49
roots47 canton7: I think because I had the f and the pick on the wrong lines15:50
tjbiddle left15:50
canton7 I'm still missing steps, but ok15:50
dreiss left15:50
Devastator left15:50
harish left15:50
DevastatrDevastator15:51
kevwil_ left15:51
roots47 now when I exit the vi that says "noop" it says "Successfully rebased and updated detached HEAD"15:51
canton7 oh so you were in the middle of a rebase when you started rebasing again, and you didn't abort it properly15:51
checkout a branch15:51
'git checkout branchname'15:51
then rebase -i again15:51
roots47 canton7: Ok, now it's listing my last two commits, I want to combine them into one15:52
cha1tanya joined15:52
roots47 canton7: I put the f on the first or second line?15:52
canton7 you 'fixup' the latter, so the second one15:53
that means 'rewrite the first one to include the changes from the second one'15:53
JorgeRuiz joined15:53
roots47 canton7: ah i see. Ok, the output was "error: could not apply {hash}... {message}"15:53
rabellamy joined15:53
canton7 wait what? was any of the commits listed in the editor window a merge commit?15:54
roots47 canton7: no, they are both regular commits15:54
canton7 and just those two commits appeared in the editor window?15:54
groglogic left15:55
stewiee left15:55
Luke-Jr left15:55
roots47 canton7: yes15:56
sainaen joined15:56
Asenar left15:56
Luke-Jr joined15:56
canton7 then I'm really confused as to why that didn't apply. Output of 'git status'?15:56
enr joined15:56
cizra Because the merge fails, we discussed it already15:58
Umm, hang on, no15:58
roots47 I just went back to step one, the git reset --hard HEAD^15:58
canton7 that means "reset everything to the commit before the current commit" - are you *sure* that's what you wanted to do?15:59
roots47 yes15:59
canton7 do you currently have a branch checked out? 'git branch'15:59
roots47 so now I basically want to pull in remote changes and cleanly merge them16:00
I was told to use 'rebase' which I have never done before16:00
Balliad left16:01
mastro joined16:01
cin joined16:01
cizra No, wait, you're trying to do 2 things here16:01
valgrind left16:01
SwashBuckla anyone here use gitflow with git-svn? I'm wondering about any implications combining the two has to your workflow16:01
cizra Step 1 would have been to roll your two commits into one.16:01
Mode-M left16:02
normanrichards left16:02
private left16:03
roots47 cizra: shit, i may have lost my changes16:04
milki roots47: probably, thats what git reset can do. but you can recover!16:04
roots47 :(16:04
milki roots47: and after you recover, you should !backup16:04
gitinfo roots47: Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups16:04
leptonix joined16:05
enr left16:05
cizra roots47: Don't panic. You most likely have them in "git reflog"16:05
adamwathan joined16:05
milki roots47: !fixup can detail recovery process16:05
gitinfo roots47: So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!16:05
sferry joined16:05
sferry left16:05
sferry joined16:05
Norrin what's the easiest way to get the patch of a commit. and then apply it, assuming it isn't already there16:06
michaelarestad left16:06
canton7 roots47, 'git branch'. what's the output16:06
cizra roots47: Step 1, tar everything up, as milki said. Before further messing around!16:06
canton7 I asked you before, and I'm pretty sure it'll be "(no branch)"16:06
cizra Norrin: git format-patch, I'd suppose?16:06
roots47 canton7: i'm on master16:06
rpg left16:06
g0bl1n joined16:07
canton7 roots47, cool. that reset --hard HEAD^ probably threw away the latest commit on master, then16:07
Norrin cizra, looks complicated. git diff -p is patch format right?16:07
roots47 I'm so lost right now :\16:07
rpg joined16:07
canton7 roots47, pastie the output of 'git reflog'16:07
groglogic joined16:08
mcepl joined16:08
cizra Norrin: -p is default16:08
roots47: Instead of panicking, tar up your whole Git repo, so that whatever you do, you'dn't lose your changes.16:08
noname001 left16:08
arand joined16:09
roots47 canton7: http://pastie.org/820860216:09
cizra: ok16:09
Norrin git format patch:16:09
"A single commit, <since>, specifies that the commits leading to the tip of the current branch that are not in the history that leads to the <since> to be output."16:09
milki rather, panicking is step -116:09
Norrin wtf… is that english?16:09
mcepl is there a way how to have with two bzr:: remotes and git would recognize common commits between the two? (bzr::http://code.bitlbee.org/bitlbee/ and bzr::http://code.khjk.org/bitlbee/ to be exact)?16:09
roots47 hehe16:09
mcepl *how to have a repo16:09
Norrin that that that that16:09
roots47 cizra: you mean just compress the whole project?16:09
vince_prignano joined16:09
canton7 roots47, yup. So you were on master, the you run 'git reset --hard HEAD^', which threw away the latest commit on master16:10
roots47, after backing up the repo, run 'git reset --hard 8c74532'16:10
aberrant left16:10
gittish left16:10
canton7 to move *back* to the "old" mastr16:10
*master16:10
Norrin i'm going to pretend like the man page doesn't include that line. even though "since" is probably what i need16:10
milki Norrin: good for you16:11
nicedice joined16:11
roots47 canton7: changes are back!16:11
trungqtran left16:12
roots47 cizra, canton7: I really appreciate the help guys... beyond measure16:12
milki did you backuo yet16:12
roots47 milki: yes16:12
Norrin "A single commit, <since>, specifies that the commits leading to the tip of the current branch that are not in the history that leads to the <since> to be output."16:12
nathancahill joined16:12
canton7 roots47, hint: DON'T run 'reset --hard' when you don't understand what it does!!16:12
Norrin after "specifies that", where is the complete predicate?16:12
kevwil left16:13
roots47 canton7: I knew it went back to a previous commit, I just forgot that I had done a git pull first the first time!16:13
milki if you take out some clasuses, its a bit awkard16:13
arand does "git fsck" do much more extensive checking than "git fetch/push" would? And hence would running a "git fsck" periodically on a server make any sense?16:13
leptonix left16:13
_ikke_ arand: yes16:13
primitive joined16:13
milki a commut specifies that the commits to be the output16:13
_ikke_ arand: KDE ran into that16:13
I believe16:13
http://www.phoronix.com/scan.php?page=news_item&px=MTMzNTc16:14
fRAiLtY- left16:14
_ikke_ http://jefferai.org/2013/03/29/distillation/16:14
roots47 canton7: So now I'm back at the point where I want to rebase my previous two commits into one16:14
Norrin milki, will you explain what the since option does for git format patch?16:14
arand _ikke_: Yes, I'm trying to set up a backup, and trying to avoid the same trap...16:14
JorgeRuiz left16:14
cizra roots47: git rebase -i HEAD^^ or git rebase -i origin/master16:14
roots47 cizra: http://pastie.org/8208611 that's what my tree looks like16:15
milki Norrin: logically, show commits after specified commits, probably16:15
Norrin: !tias16:15
gitinfo Norrin: 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.16:15
canton7 milki, we've gone through that16:16
cizra roots47: Looks good...16:16
leptonix joined16:16
amaury_d joined16:16
Raging_Hog joined16:16
Raging_Hog left16:16
raging_swine joined16:16
trungqtran joined16:16
themsay joined16:17
Norrin so to back up, i want to take a commit and apply it to a different repo16:17
roots47 cizra: ok done, used 'f' on the second commit. Got the 'error: could not apply...'16:17
Norrin trying to find the easiest way to do that16:17
mishok13 joined16:17
arvind_khadri left16:17
canton7 roots47, output of 'git status'?16:17
dpac|awaydpac16:17
cizra roots47: What'd you do to the first one?16:17
roots47 cizra: left pick16:18
carpii left16:18
cizra Norrin: git fetch; git cherry-pick16:18
Norrin said nothing about a remote16:18
jargon left16:18
roots47 canton7: "not currently on any branch, fix conflicts and then run git rebase continue" ok, let me take a look at this file real quick16:18
canton7 roots47, and you *only* changed 'pick' to 'fixup' on the second?16:18
roots47 canton7: yes16:18
canton7 roots47, I was kinda after the rest of the output...16:19
Norrin and its a different repo, so how would i be able to cherry-pick something, cizra ?16:19
cizra Norrin: Easily.16:19
roots47 canton7: I have some changes to be committed and one 'unmerged path'16:19
canton7 roots47, go fix the conflict then. I'm interested in what it is16:19
cizra roots47: Well, check what the modifications are like...16:19
flippo joined16:19
Gu_______ left16:20
Norrin cizra, can't the git diff output be applied somehow?16:20
_ikke_ arand: See also http://comments.gmane.org/gmane.comp.version-control.git/21896416:20
Norrin **easiest**16:20
anonymuse left16:20
devoldmx27 joined16:20
roots47 cizra, canton7: conflicts have been merged, now I assume I run git rebase --continue ?16:20
milki Norrin: are you going to even try?16:21
michaelarestad joined16:21
canton7 roots47, once you've 'git add'ed the file, yup16:21
roots47, what sort of conflict was it?16:21
(there shouldn't have been one at all)16:21
roots47 canton7: just some conflicting code, since I was rebasing from origin/master16:21
arand Norrin: Either 1. add other repo as remote, 2. fetch content, cherry-pick from feched content; OR 1. format-patch in one repo, 2. git am in other repo.16:21
milki or git diff and patch16:21
enr joined16:22
canton7 roots47, oh, so you ran 'git rebase -i origin/master' not 'git rebase -i HEAD^^'16:22
cizra Norrin: You don't even need to add it as a remote, just git fetch <repo> should work.16:22
kevwil joined16:22
roots47 canton7: yes exact, and... LOOKS LIKE IT WORKED!!!16:22
canton7 roots47, aah that explains it16:22
cool16:22
arand (with just diff you will some metadata like author and date, though)16:22
devoldmx left16:22
cizra roots47: Oh shit, that was my bad )=16:23
amaury_d left16:23
cizra roots47: I managed to mess up and combine the two steps into one )=16:23
roots47 cizra: no worries, i really appreciate the help16:23
Norrin cizra, arand, isn't fetch a pull? the histories are divergent. how can you pull from a different history?16:23
cads joined16:23
Norrin milki, i like that option. seems the easiest16:23
roots47 cizra: Well hell, we knocked out two birds with one stone, no?16:23
Norrin just can't figure out these different diff formats16:23
cizra roots47: Yeah, exactly what I wanted to avoid.16:24
h0bbit left16:24
Norrin what applies a git diff?16:24
milki Norrin: pull = fetch + merge16:24
h0bbit_ left16:24
milki Norrin: patch16:24
cizra Norrin: Are you going to fetch or not?16:24
arand Norrin: no fetch just gets the content, it does not try to merge it into the content in the repo it is being fetched to.16:24
Norrin milki, yeah…. merging something completely different. does'nt sound right16:24
cizra Norrin: Until you've tried, quit blathering.16:24
Norrin oops. i read fetch == pull + merge16:24
roots47 cizra: I see the results of what we just did... but what exactly does git rebase origin/master do?16:25
thiago left16:25
roots47 git rebase -i origin/master *16:25
milki Norrin: doooit16:25
cizra roots47: Well, git rebase origin/master moves all your new commits on top of origin/master.16:25
Norrin break it break it break it!!!!!16:25
love that16:25
so eager to do that16:26
milki Norrin: !backup16:26
gitinfo Norrin: Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups16:26
cizra roots47: And -i lets you do interactive editing on top like fixups.16:26
Norrin: God created throwaway test repos for just that reason.16:26
milki Norrin: backup, tias, and learn somwthing16:26
Norrin or find out how to do it the right way16:26
roots47 cizra: Cool, well I'll play around with it... and thanks again, you've been a tremendous help16:26
babilen_ joined16:26
devoldmx joined16:27
roots47 canton7: you too16:27
cizra roots47: Nodnod. That'd be $32.16:27
milki Norrin: !fish16:27
gitinfo Norrin: In the long run, it is much better to give pointers to answers than the answers themselves.16:27
canton7 np :)16:27
lamarus left16:27
roots47 cizra: paypal? :P16:27
Skrypter joined16:27
cizra milki: Light a man a fire, he'll be warm all night. Light a man afire, he'll be warm the rest of his life.16:28
roots47: Jokin', jokin'16:28
milki cizra: sounds like a plan16:28
Norrin because prolonging the peril of others is the real purpose of life16:28
lamarus joined16:28
cizra roots47: I've got unbelievable amounts of help over IRC...16:28
jfoy joined16:28
milki /ignore Norrin16:28
roots47 cizra: Some of these git commands are just really hard to understand by reading the man pages16:28
cizra roots47: Yeah, well, most things are best learned by seeing examples, then doing them under supervision.16:29
Norrin milki, its ok. i can tell when annoying someone is enjoyment for someone else16:29
roots47 cizra: true true16:29
geekbri left16:29
babilen left16:29
devoldmx27 left16:30
donmichelangelo left16:30
Norrin [09:24:18] <milki> Norrin: patch16:30
$ git help patch16:30
No manual entry for gitpatch16:30
matanya joined16:30
chuckharmston joined16:30
Norrin misdirection == air16:30
donmichelangelo joined16:30
tjbiddle joined16:30
milki patch isnt a git command16:31
jefflyne left16:31
f0ster joined16:31
babilen_ left16:31
JosephSilber left16:31
mechanicalduck joined16:31
tatsuya__ left16:31
babilen joined16:31
dreiss joined16:32
milki i wonder if am works on regular diffs16:32
Norrin milki, thanks! i was just googling how to get git to realize commands it said it didn't know about16:32
SamB milki: I think there is also a "git apply"?16:33
jefflyne joined16:33
milki man git apply16:33
gitinfo the git-apply manpage is available at http://jk.gs/git-apply.html16:33
milki o ya16:33
that works too16:33
ErKa left16:35
threesome joined16:37
groglogic left16:37
achadwick left16:38
Rylai left16:40
Rylai joined16:41
whaley joined16:42
LimeBlast left16:43
JorgeRuiz joined16:43
JorgeRuiz left16:43
enr^ joined16:43
normanrichards joined16:43
cedeon left16:43
Noldorin left16:43
Rylai left16:44
Rylai joined16:44
SpecialEmily[w] joined16:44
Thra11_ joined16:44
Sonderblade left16:45
JorgeRuiz joined16:45
JorgeRuiz left16:45
JorgeRuiz joined16:46
jefferai arand: this thread may be of interest, too: http://git.661346.n2.nabble.com/propagating-repo-corruption-across-clone-td7580504.html16:47
enr left16:47
Noldorin joined16:47
jefferai but, basically, git fsck will check everything; normal fetch/push/pull will only check what affects the current operation16:47
which is relatively expected16:47
arand jefferai: I've read it twice already :)16:47
jefferai ah, heh16:47
ok16:47
_W_ left16:48
groglogic joined16:48
vince_pr_ joined16:49
hyperair joined16:49
Sendoushi anyone knows how to change the name of the repo without change the folder's name or change the description after making the repo on github app?16:50
heroux left16:51
danillonunes joined16:51
dfanjul left16:51
vince_prignano left16:52
aberrant joined16:53
m8 joined16:54
goshawk joined16:54
rabellamy left16:54
MasterBob cizra: what is the octopus merge?16:54
HariboPenguinHariboPenguin|Of16:54
paul424 joined16:54
breck7 joined16:56
Christi123 left16:57
_ikke_ MasterBob: A merge strategy for more than two parents16:57
MasterBob _ikke_: know where I can find more information? just google it?16:57
Hoosier2016 left16:58
_ikke_ man git merge has some info on it16:58
gitinfo the git-merge manpage is available at http://jk.gs/git-merge.html16:58
Plummer left16:59
zhost joined16:59
Cromulent joined16:59
kevwil left16:59
Cromulent left17:00
jhulten joined17:00
_goTAN left17:00
Fritz7 left17:01
enr joined17:01
heroux joined17:01
Fritz7 joined17:01
iliketurtles joined17:02
maroloccio left17:02
wrouesnel left17:03
cizra MasterBob: You can create cool-looking history by changing all your tools, then merging them all simultaneously into master.17:04
sferry left17:05
huoxito joined17:05
shruggar left17:05
enr left17:05
tonyj joined17:05
PigeonFriend left17:05
MasterBob cizra: cool looking history? lawl. okay thanks.17:06
ikuraj_ joined17:07
flippo left17:08
rabellamy joined17:08
kevwil joined17:09
ikuraj left17:09
themsay left17:11
jackdempsey joined17:11
thiago joined17:11
preflex left17:12
preflex_ joined17:12
preflex_preflex17:13
iliketurtles left17:13
HariboPenguin|OfHariboPenguin17:13
devoldmx27 joined17:14
iliketurtles joined17:14
brotatos joined17:14
brotatos Is there any way to prevent git-merge from calling up an editor? I have a message I already want to use and doing a `git merge --no-edit -m $(message)` still brings up an editor.17:15
cigarshark joined17:15
konundra joined17:15
nova_ left17:16
devoldmx left17:17
bil joined17:17
bil can i do a git stash apply and force it to merge even if theres a conflict?17:18
fRAiLtY- joined17:18
bil and then resolve it manually17:18
_ikke_ brotatos: is $(message) empty perchance?17:18
brotatos _ikke_: nah, it's full of good stuff.17:18
deryni $(message) or ${message}?17:18
maslowbeer joined17:18
brotatos ${message}17:18
Well, this is really done in ruby.17:18
cbreak bil: that's what it always does.17:18
brotatos So #{message}17:19
https://github.com/iFixit/git-scripts/blob/2f37fc57b8b386528f53f5e8efea14da672b8a55/bin/hotfix#L9417:19
bil cbreak: its erring telling me i need to commit my changes first17:19
erroring*17:19
anonymuse joined17:19
maxmanders left17:20
adamwathan left17:20
cbreak bil: yes, do that.17:20
bil: git will not recklessly endanger unrecoverable changes in a merge17:22
you'll get your conflict after committing too17:22
and can amend when you're done resolving17:22
freeed Hey guys.. When I do a git pull to pull in changes from my team git opens up VIM asking me to add a commit message for the merge. Is there any way to disable that? I'm fine with the default merge commit message "Merge branch 'master' of my_remote_server_name".17:22
bil Basically i started working again and i forgot i had some stuff stashed17:22
isn't it bad practice to commit half worked stuff?17:23
cbreak as long as you don't push it it's fine.17:23
Chryyz joined17:23
deryni You can always reset that commit away after the stash apply too.17:23
cbreak freeed: man git-merge17:23
gitinfo freeed: the git-merge manpage is available at http://jk.gs/git-merge.html17:23
cbreak freeed: look at --no-edit17:23
bil so commit, apply stash, and then edit commit?17:24
nova_ joined17:24
freeed thanks cbreak!17:24
deryni brotatos: Unrelated to the problem at hand why shellescape message but not hotfix? (Also why is hotfix only quoted on some lines?) Also that line says '--edit' not '--no-edit'.17:25
jhulten left17:25
jhulten joined17:26
freeed cbreak, I see I can git pull has the same flag. Is there anyway to set that as a default flag for git pull so I don't have to manually add it? (everyone on my team gets this same everytime we pull several times a day)17:26
brotatos deryni: hotfix is bound to be just a plain string17:27
deryni: it's not quoted in places where the hotfix branch is the literal name of the path17:27
keller left17:27
Thra11_ left17:27
deryni brotatos: If it has spaces in it the shell doesn't care what you are using it as.17:28
JosephSilber joined17:29
galaris joined17:29
crane_work left17:29
brotatos deryni: the hotfix branch name will never have spaces in it.17:29
HariboPenguinHariboPenguin|Of17:30
brotatos deryni: branch names can't have spaces in them.17:31
mishok13 left17:31
Xiti left17:31
groglogic left17:32
deryni So they can't. They still can have other shell metacharacters though, but like I said this is besides the point.17:32
s-e joined17:33
ikuraj_ left17:33
brotatos deryni: You're right. It's just a matter of typing in shellescape anyways. :P17:33
Yakko joined17:34
HariboPenguin|OfHariboPenguin17:35
JrCs joined17:35
rickruby left17:36
Xiti joined17:37
s0undt3ch_ left17:37
Davey joined17:37
Sigma left17:37
michaelarestad left17:37
hwrd|work joined17:37
frankstallone joined17:37
s0undt3ch_ joined17:37
JrCs left17:38
snow_ru joined17:38
snow_ru hi all17:38
gitinfo snow_ru: 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.17:38
JrCs joined17:39
s0undt3ch_ left17:39
JakePee left17:39
s0undt3ch joined17:39
JrCs left17:39
snow_ru I want to work on git --- I code in C. I need some help to start :)17:40
Inside joined17:40
JrCs joined17:40
PerlJam snow_ru: What do you think that git needs?17:40
Guest____ joined17:40
PerlJam snow_ru: And have you tried the mailing list?17:40
iliketurtles left17:41
snow_ru I don't have a complete view about git as you do, so I need to start small --- I'm looking around17:41
nkambo left17:41
mastro left17:41
snow_ru PerlJam, no mailing list in /topics17:41
PerlJam, no mailing list in /topic17:41
bremner !list17:42
gitinfo [!mailing_list] The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist17:42
Davey left17:42
kesha__ joined17:42
skorgon snow_ru, http://git-scm.com/community17:42
kesha_ left17:43
tirengarfio im getting this error after pushing: remote: error: unable to unlink old 'web/views/materiales_aluminio.twig' (Permission denied)17:43
Yakko hey guys, I have a features/report.html file that gets generated automatically by my test system, however when I'm trying to merge code from other people in my team, it always shows me a merge conflict on that file and asks me to decide how to merge it, is there something like a .gitignore that always accepts the latest changes for some specific files? that would really help17:45
Kyle seems silly to be commiting that17:46
+t17:46
JrCs left17:47
mastro joined17:47
nadirvar_ joined17:47
JrCs joined17:47
sq-one joined17:48
iliketurtles joined17:48
alkino left17:48
cizra snow_ru: The best way to start: 1) get the source, 2) play around, 3) create couple of useful commits, and only then: 4) start figuring out how to contribute them back.17:48
_iron left17:49
Hoosier2016 joined17:49
Collin joined17:49
bremner snow_ru: are you an experienced user of git?17:49
masak Yakko: yeah, check out .gitattributes17:49
maqr left17:49
telesto joined17:50
telesto Is it possible to untrack a file in Git without it being removed from other people's repositories? I know I can 'git rm --cached FILE', but that still deletes FILE from other people's systems when they pull17:51
Inside left17:51
_ikke_ telesto: nope17:52
git has no way to store that a file is only deleted from the repostory, not from the filesystem17:52
telesto _ikke_: ok, thanks. I didn't think so17:52
Yakko masak: what exactly am I trying to do here? force to consider it a binary?17:52
alvaro_o joined17:53
sferry joined17:53
sferry left17:53
sferry joined17:53
masak Yakko: I was thinking of the 'merge strategy' setting.17:53
MasterBob left17:53
Yakko masak: I can't find specific information about it on google, but thanks for the heads17:53
OnlyMax joined17:54
kesha__ left17:54
longbeach joined17:54
Sonderblade joined17:54
Sonderblade left17:54
masak Yakko: see the heading "Merge strategies" under http://git-scm.com/book/ch7-2.html17:54
szx joined17:55
Sonderblade joined17:55
preaction joined17:55
kesha__ joined17:56
ojacobson left17:56
_BJFreeman joined17:57
chrob joined17:57
_BJFreemanBJfreeman17:57
h0bbit joined17:58
h0bbit` joined17:58
rfk joined17:58
carpii joined17:59
h0bbith0bbit_17:59
h0bbit`h0bbit17:59
carpii im cherrypicking a commit which modified 3 files. Because of a conflict, two files are unstaged but one (index.php) is already staged. I cannot seem to unstage it, I just want to discard changes to that file and resolve the other 218:00
_ikke_ how do you try to unstage it?18:00
s-e left18:00
causasui joined18:00
causasui left18:00
carpii ive tried to git co -- index.php18:00
aard_ joined18:00
carpii and also git co --ours and --theirs18:00
tatsuya_o joined18:01
enr joined18:01
devoldmx27 left18:01
legolim left18:02
f0ster left18:02
JrCs left18:02
maqr joined18:02
mmlac-bv left18:02
JrCs joined18:03
angelsl left18:03
Collin_ joined18:03
kermit left18:03
devoldmx joined18:04
carpii ok it seems i can git reset HEAD to unstage it18:04
Droolio left18:05
proq joined18:05
_ikke_ djflskjf18:05
ups18:05
Collin left18:05
enr left18:06
rickruby joined18:06
rfk So git rm r --cached '*.pyc' returns "pathspec 'work/r' did not match any files"18:06
dsdeiz left18:07
rfk Is there a surefire way I can eliminate such files from my git index and my working tree, and ensure that they are not added again?18:07
Oh, so I do need a - before the r18:07
Still, it's not recursive18:08
Actually18:08
GT4066 left18:08
proq when I run git status I get the error "fatal: This operation must be run in a work tree", even though I am in a git repo. how do I make this error go away?18:08
rfk Alright, that works - will .gitignore in the repository directory now ensure that these files are not ever added again?18:09
proq: Is it a bare repository?18:09
oojacoboo joined18:09
proq rfk: no18:09
Hoosier2016 left18:09
_W_ joined18:09
snow_ru bremner, I'm just a normal git user. But if you guys have some algorithmic tasks in mind, I would like love to dig in :)18:10
Villadelfia left18:10
iveqy proq: are you in a work tree?18:10
deryni proq: You have checked out files and a .git directory in that directory?18:10
_goTAN joined18:11
gmdaas2 left18:11
jamiis joined18:11
marhaban1 left18:12
johnnyfuchs joined18:12
trungqtran left18:13
_goTAN left18:13
JorgeRuiz left18:13
marhaban joined18:13
kevwil_ joined18:14
rickruby left18:14
legolim joined18:15
kevwil left18:15
telesto left18:15
torbjorn left18:17
Shusshu joined18:17
Vampire0_Vampire018:17
aldodelgado joined18:17
PsySc0rpi0n joined18:18
HariboPenguin left18:18
torbjorn joined18:18
Shusshu left18:18
kermit joined18:18
Tree_Hugger joined18:18
PsySc0rpi0n left18:19
HariboPenguin joined18:19
thiago left18:20
HelloShitty joined18:20
Skrypter left18:20
maxmanders joined18:20
thiago joined18:20
drager_ left18:20
drager_ joined18:20
drager_drager18:21
|Freeman| joined18:21
proq it's a working repository with all the files checked out. it works on another machine and I copied it to this machine via thumb drive18:21
maxmanders left18:21
ziddey joined18:22
tatsuya_o left18:22
trungqtran joined18:22
Mode-M joined18:22
_ikke_ proq: did you also copy the .git directory?18:22
michaelarestad joined18:24
kesha__ left18:24
carpii left18:26
maxmanders joined18:26
JorgeRuiz joined18:26
BJfreeman left18:26
mechanicalduck left18:26
zacts left18:26
Sigma joined18:27
rurufufuss left18:28
JakePee joined18:28
GodEater left18:29
Nicholas_Rishel left18:30
CheckDavid joined18:30
grzesag joined18:30
nafg_ left18:30
proq _ikke_: yes18:31
normanrichards left18:31
mechanicalduck joined18:31
_ikke_ does the .git directory contain a file called HEAD18:31
iveqy proq: what filesystem do you have on your USB drive and what filesystem do you have on your harddrive?18:31
voila joined18:31
adhawkins-awayadhawkins18:32
proq also, icbw but it seems this only started happening after I upgraded git to 1.7.12.418:32
hoschi left18:32
iveqy proq: that's good to know. What operating system do you use?18:32
SmokeyD left18:33
proq os x 10.818:33
kesha__ joined18:33
rfk In the master branch, `git checkout master' returns "Your branch is ahead of 'origin/master' by 3 commits."; and `git pull` indicates that i am already up to date. But in fact my master branch is behind the current material quite a bit -- a website redesign was done recently, and locally I still have the old design. Should I just clobber everything?18:33
brotatos left18:33
proq the USB drive and filesystem are HFS+. I will try copying the files over again with scp18:33
ziddey left18:34
imMute joined18:34
proq _ikke_: yes18:34
iveqy rfk: how about: git checkout master && git merge origin/master18:35
rfk: but do a git fetch before that18:35
GodEater joined18:35
JSharpe joined18:35
therealGent joined18:35
iveqy proq: with scp? Why do you use scp for copy between a harddisk and a usb-drive?18:35
voila k18:36
am i connected to internet18:36
proq iveqy: I don't. why would anyone do that?18:36
rfk iveqy: Still gives the same indications :/18:36
voila iveqy, but his master 3 commits ahead of origin master ... will merge is good ?18:36
iveqy proq: you said so...: I will try copying the files over again with scp18:37
rfk voila: It's interesting, because git is indicating I am ahead, but there are considerable changes in the remote repository that I don't have18:37
proq iveqy: no, I didn't18:37
paul424 left18:37
iveqy voila: it shouldn't be if he made the git fetch first as I wrote on line later...18:37
orthoplex64 joined18:37
proq iveqy: I tried copying the original repo from one machine to another with scp and I get the same error. I guess I will try git clone now18:37
iveqy proq: 20:37 < proq> the USB drive and filesystem are HFS+. I will try copying the files over again with scp18:37
proq: maybe there's something wrong with your or mine irc client18:38
proq iveqy: yes, copying the files over again from the original machine. you're making assumptions18:38
iveqy rfk: what did git fetch told you?18:38
orthoplex64 I'm so glad there's a channel for git help18:38
voila rfk, yeah .... then as iveqy said .. fetch origin/master and merge ..18:38
Praise-Praise18:38
iveqy proq: of course I do, if you don't tell us everything we have to make assumptions18:38
voila then push master18:38
orthoplex64 Would anyone mind looking at http://pste.me/n0eUg/ ? I'm very new to git/github and I have no idea how to respond to this error18:38
iveqy orthoplex64: read the error message, it's pretty well explained. What is it you don't understand?18:39
proq iveqy: just stop already. no one is making you make assumptions18:39
orthoplex64 it just says "Failed to merge in the changes."18:39
mizu_no_oto joined18:40
orthoplex64 Since I don't really know what I'm doing, I have no idea what to do next18:40
boblee anyone have experience with post-receive-email. I am receiving error -> error: hooks/post-receive exited with error code 118:40
voila rfk, what i can understand is .. your master is 3 commits ahead of your master tracking branch .. but your remote repository is far ahead ..18:40
rurufufuss joined18:41
mizu_no_oto left18:41
iveqy orthoplex64: read line 15-16-17 it tells you what to do18:41
Zeelot left18:41
orthoplex64 "When you have resolevd this problem"18:41
voila then .. on master branch ... git fetch origin master ; git merge origin/master .... then git push origin master ..18:41
zacts joined18:41
orthoplex64 but that's what I'm trying to say. I don't know how to resolve this problem; I'm not even sure what's wrong18:42
iveqy proq: so if you want help, please tell us the whole picture. And why are you using scp for transferings git archives?18:42
orthoplex64: open the files in your favorite editor and edit them until you're happy. Look for <<<<< >>> and === lines18:42
johndo rfk: are you sure the website changes are checked in into the repository you are fetching from? and they are checked in on the master branch?18:43
jerrad left18:43
jerrad joined18:43
voila orthoplex64, first block contains what is present in your file (your changes) , second block contains what is being fetched ''18:43
orthoplex64 what happens if I just continue without chaning anything in the file?18:44
Zeelot joined18:44
voila you can try18:44
cin left18:44
orthoplex64 it says "You must edit all merge conflicts and then mark them as resolved using git add"18:45
cin joined18:45
mizu_no_oto joined18:45
voila orthoplex64, yes .. you have to first resolve the conflict ..18:46
iveqy orthoplex64: git won't care, your program will not compile since there's conflict markers in your file18:46
rfk left18:46
orthoplex64 but why is there a conflict? I did this exact same thing just a few hours ago and everything was all hunky-dory18:46
proq iveqy: why not?18:46
rfk joined18:46
mishok13 joined18:47
voila conflict occurs .. because you have made changes in your file say at line 1 : this is abc ... but when changes fetched from remote .. then at line 1 is : this is cde ... So git is not able to decide which one it has to keep ..18:47
badgeruk left18:47
orthoplex64 oh18:48
so what is the patch file actually supposed to look like when I'm done editting it?18:48
voila orthoplex64, i don't know much about what .. here comes the iveqy :)18:49
fuzzybunny69y left18:49
voila that*18:49
mklappstuhl left18:49
iveqy proq: depends on your use-case of course, but usually you're just interested in the stuff you get from a git clone. With scp you get garbage too, and scp will open a new connection for each file (which will be slower) and if you don't have synced clocks on your machines or if scp doesn't got the flag to preserve timestamps, your worktree will/might be strange18:49
voila orthoplex64, are you asking about how to resolve conflict ??18:49
cin left18:49
orthoplex64 how to resolve conflict? well that's why I'm here; I want to resolve whatever conflict is goign on18:50
going*18:50
iveqy orthoplex64: you should never edit a patch file, you should edit your *.java files, and only you know how they should look18:50
kevwil joined18:50
voila lol18:50
orthoplex64 oh18:50
voila orthoplex64, remove markers and keep code whatever you want .. either your code or code fetched from repo18:51
kevwil_ left18:51
orthoplex64 so git just shoved both changes in the same file and it's asking me to continue after I edit the files to keep which one I choose?18:51
fuzzybunny69y joined18:52
voila orthoplex64, have you made changes in your files ?18:52
orthoplex64 and then how do I "mark them as resolved using git add"?18:52
no, not yet; I'm doing that right now18:52
voila git change the file to keep changes whatever you want .. and then commit18:53
orthoplex64 can I somehow tell git to keep the most recent changes?18:53
voila iveqy, Can we do commit directly after resolving conflicts . ?18:53
johndo orthoplex64: right, use git add after you have edited the files18:54
ziddey joined18:54
orthoplex64 but there should be a way to tell git to use the most recent commits18:54
maxmanders left18:54
iveqy voila: no commit at all in a rebase afaik18:54
voila iveqy, and in merging ?18:55
proq iveqy: well it would appear that with the latest git stable (or maybe the combination of the latest git stable with this repo) that scp is no longer an option18:55
voila instead of rebase18:55
mmlac-bv joined18:56
iveqy orthoplex64: there is. read man git rebase and look at the merge strategies. However, usually you want to look at the problem yourself18:56
gitinfo orthoplex64: the git-rebase manpage is available at http://jk.gs/git-rebase.html18:56
iveqy voila: a merge will result in a merge commit, so there you should commit18:56
voila yeah .. thanks iveqy :)18:57
saintcajetan joined18:57
iveqy proq: latest git stable is 1.8.3.4 you said you're using 1.7.12.4. I'm confused18:57
Andrevan joined18:58
Andrevan left18:58
Andrevan joined18:58
iveqy proq: 1.7.12.4 is 10 months old18:58
johndo git stash does not track the content of a file when it gets deleted?18:59
matteo left19:00
jamiis left19:00
johndo i have deleted a file, then stashed that state, edited the file and applyed the stash19:00
orthoplex64 ok, I changed the files to the way they're suppoesd to be19:00
proq iveqy: that's very odd. I ran the 1.8.3.2 installer and it isn't updating git19:00
johndo i somehow had expected that stash apply to fail19:00
orthoplex64 how do I "add them with git add"? sorry if you already said something19:00
Tree_Hugger left19:00
cads left19:01
xrq`xrq19:01
proq ah, the paths were not set up right19:02
enr joined19:02
voila git add19:02
kevwil left19:03
drager Can you show changes but the file haven't been added nor commited?19:03
orthoplex64 just "git add"?19:03
voila git add <your files> .. hey I think you should read a bit of manuals .. so that you can get idea of what are you doing .. otherwise you will get confused soon :)19:04
johndo drager: show changes against what? when git does not even know the file19:04
drager Ah yes19:04
iveqy drager: git status?19:04
SocalNick joined19:04
orthoplex64 but how do I format <your files>19:05
I tried pasting the path19:05
also just saying the file name19:05
Collin_ left19:05
voila git diff <you file> ..19:05
orthoplex64 and the manuals are confusing because all the pages assume you know pretty much all the other pages except the one you're reading19:05
voila orthoplex64, lol , git add file1 file219:05
orthoplex64 just the name of the file?19:06
anonymuse left19:06
voila you can give full path19:06
drager I was looking for git diff --cached19:06
thanks19:06
DolphinDream how do you do interactive staging ? i want to stage all then unstage a few changes within a file19:07
jamiis joined19:07
iveqy DolphinDream: man git add19:07
gitinfo DolphinDream: the git-add manpage is available at http://jk.gs/git-add.html19:07
rickruby joined19:07
_ikke_ git add -i19:07
enr left19:07
maxmanders joined19:07
jamiis left19:07
w0ng joined19:07
marthinal left19:07
orthoplex64 http://pste.me/fv05T/19:07
johndo DolphinDream: maybe you are looking for git reset -p19:08
DolphinDream what about git add -p ?19:08
anonymuse joined19:08
jamiis joined19:08
iveqy orthoplex64: do you really not see the error there?19:08
vince_pr_ left19:08
orthoplex64 ...19:09
voila orthoplex64, are you using windows ?19:09
orthoplex64 yes19:09
voila hmm19:09
orthoplex64 oops19:09
should I use forward slashes?19:09
iveqy orthoplex64: don't you miss a few \ in your pathname?19:09
voila try it in double quotes and where are '\' ?19:09
"c:\users\abc" "c:\mno"19:09
hahuang61 joined19:10
devoldmx27 joined19:10
orthoplex64 now it just says that it "is outside repository"19:10
Charmi joined19:10
voila hmm ..19:10
go to directory where is .git folder is .. afaik19:10
i think you are somwhere else19:11
orthoplex64 me too19:11
voila lol .. what mee to ?19:11
Villadelfia joined19:11
orthoplex64 nevermind19:11
I haven't been this frustrated in a very long time19:11
Charmi Hi, I am unable to clone a repository because of a file whose name has special characters in it. Any suggestions?19:11
voila me too19:11
maasdesigner1 joined19:12
rickruby left19:12
iveqy orthoplex64: git isn't user friendly, git is a tool that will make your work easier, but it requires some understanding19:12
matanya left19:12
_ikke_ git is a tool for professionals19:12
jamiis left19:12
maasdesigner1maasdesigner19:13
iveqy orthoplex64: since you're using windows, you're trying to learn a unix-shell, with its windows specific problems, and git at the same time. No wonder that it's confusing19:13
jwmann left19:13
iveqy Charmi: never heard of it. Could you please !repro19:13
gitinfo Charmi: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.19:13
orthoplex64 oh19:13
devoldmx left19:14
rosipov joined19:14
insejn joined19:14
paul424 joined19:14
ej joined19:14
insejn has anyone here tried adding a submodule containing git-annex repo?19:14
_ikke_ nope19:14
JorgeRuiz left19:14
iveqy orthoplex64: don't worry, microsoft is trying to get git into visual studio and then it will be more "windows-ied". It's really a unix program as of now and it works, but has some quirks19:14
D4N3 left19:14
iveqy insejn: no, but why would that be a problem? A submodule doesn't know that it is a submodule19:15
JorgeRuiz joined19:15
JorgeRuiz left19:15
Charmi @iveqy the repository is private. but it has a folder named "<em>files<"19:15
JorgeRuiz joined19:15
napping joined19:16
SocalNick left19:16
drizzd joined19:16
Charmi windows doesnt allow a folder with special characters in it. so my whole process of git clone gets struck due to this problem19:16
insejn iveqy: The reason I'm asking is because I'm getting the following error: git-annex: git config [Param "annex.uuid",Param "60c6cdfc-fe03-11e2-a291-3f735ae37e7a"] failed19:16
voila !repo19:16
gitinfo Repo is a tool produced by Google for the AOSP project(and others) which wraps git and provides its own set of commands. While it is possible to use git with repositories that are managed by repo, it is not always easy. http://source.android.com/source/version-control.html19:16
_ikke_ Charmi: There is no easy way to fix that19:16
insejn when trying to get the files for annexed repo19:16
SHyx0rmZ joined19:17
iveqy Charmi: git shouldn't have a problem with those characters afaik. But I can't help you if I don't get to see the error message. See !secret. You could always reproduce the error in a non-secret enviroment as !repro suggests19:17
gitinfo Charmi: [!topsecret] If your situation is so secret that you can't tell us how to !reproduce it, there's really not much we can do. Perhaps you need to find or buy support you can trust? There are people with clearances even on #git but since clearance levels are classified and #git is not a secure channel, this may not help you. However, you are protected by the biggest secret of all: We just don't care.19:17
Charmi: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.19:17
bremner insejn: there is a channel #git-annex on irc.oftc.net19:17
Charmi @_ikke_ could you suggest something apart from switching to linux?19:17
Nicholas_Rishel joined19:17
insejn bremner: thanks, I'll give it a try19:17
_ikke_ Charmi: Fix the file name in the repository19:17
drizzd_ joined19:18
iveqy Charmi: well if your filesystem doesn't support those names, there's really nothing git can do about it. Use an other filesystem19:18
ej left19:18
Octalot joined19:19
Charmi @_ikke_ I wish i could but i am not the owner of repository and I have limited access.19:19
ewnd9 left19:19
orthoplex64 maybe I'm not going about this the right way19:19
I'll just describe my problem19:19
ewnd9 joined19:20
Charmi @iveqy ever faced/heard of similar issue like this?19:20
orthoplex64 I'm making changes to a clone of my fork of a repository19:20
iveqy Charmi: does the owner know that (s)he is limiting contributions from windows machines?19:20
rosipov Charmi: nothing can be done about it: only rename file in repo or use other platform19:20
orthoplex64 but since I've started working, changes have been made to the main repository19:20
how can I download those changes, yet still have my work?19:20
iveqy orthoplex64: do a rebase...19:20
cigarshark left19:20
rosipov orthoplex64: git stash && git pull --rebase && git stash pop19:21
Charmi @iveqy yes, owner is aware but the project has already reached almost upto completion, so changing a filename would not be a feasible solution19:21
iveqy orthoplex64: the stash-thing is only needed if you have things you haven't commited19:21
orthoplex64 oh19:21
g0bl1n left19:21
voila !stash pop19:21
iveqy Charmi: then, don't use a filesystem with those limitations19:21
orthoplex64 gah! but if I do git pull --rebase, how does git know what to pull?19:22
drizzd left19:22
iveqy orthoplex64: it doesn't, it guesses. It will pull your remote called origin if nothing else is said19:22
Sigma left19:22
orthoplex64 how can I see or edit remotes?19:23
iveqy orthoplex64: I think you're looking for something like this: https://gist.github.com/CristinaSolana/188543519:23
troker joined19:23
iveqy orthoplex64: man git remote19:23
gitinfo orthoplex64: the git-remote manpage is available at http://jk.gs/git-remote.html19:23
rosipov orthoplex64: git remote -v19:23
voila orthoplex64, nice pdf peecode .. git internals19:23
Sigma joined19:24
Charmi @iveqy ext4 allows special characters in filename but not ntfs19:24
jamiis joined19:24
ej joined19:24
jamiis left19:24
orthoplex64 peecode?19:24
iveqy Charmi: windows has limitations, git can't help you work past them, so you've to make sure all platforms using that git repo doesn't do anything not windows friendly. The special characters are only one limitations of windows, length of filenames is an other19:25
kevwil joined19:25
iveqy Charmi: then switch to ext4?19:25
cha1tanya left19:25
OnlyMax left19:25
jamiis joined19:25
insejn left19:25
jamiis left19:25
mklappstuhl joined19:26
mechanicalduck left19:26
arand left19:26
jamiis joined19:26
Charmi so, i have two possible solutions. either switch to ext4 or change the filename inside repository!19:26
matanya joined19:27
iveqy Charmi: well, there's a number of filesystems you can choose from, but yeah ext4 is the only one I know that will work somewhat on windows19:27
huoxito left19:27
mechanicalduck joined19:27
maxmanders left19:27
rasnor left19:28
private joined19:28
ej left19:28
ej joined19:31
dpacdpac|away19:31
Charmi well, thanks for help @iveqy @_ikke_19:32
iveqy Charmi: good luck. If I was in your shoes I would just install ubuntu on avirtual machine19:32
orthoplex64 how do I start tracking new files that I added to my local repo?19:32
Hoosier2016 joined19:32
iveqy orthoplex64: git add19:32
orthoplex64: it seems like you need !book !talks19:32
gitinfo orthoplex64: 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 !parable19:32
orthoplex64: Some good video talks about Git: [yt] http://goo.gl/z72s (Linus Torvalds: History&Concepts); [yt] http://goo.gl/R9H2q (Scott Chacon: Git basics, live examples); http://vimeo.com/35778382 (Randal Schwartz: Git basics, descriptional); http://vimeo.com/46010208 (Jesica Kerr: Git basics, descriptional)19:32
nsanden left19:32
orthoplex64 is git add just some sort of multifunctional command?19:32
iveqy orthoplex64: no, git add adds files to your index19:33
orthoplex64 index...?19:33
iveqy orthoplex64: as I said, !book19:33
gitinfo orthoplex64: 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 !parable19:33
orthoplex64 I really could use a book19:33
iveqy orthoplex64: it really explains things better that I can do here, and it has images =)19:33
voila peepcode git internals19:34
Guest____ left19:34
Sigma left19:35
Marqin left19:36
Marqin joined19:37
nathancahill left19:37
Davey joined19:38
hahuang61 left19:39
joshsmith left19:39
mmlac-bv left19:39
devth left19:41
Bass10 joined19:41
Marqin left19:42
t0by left19:44
worstadmin left19:44
mribeirodantas joined19:44
devth joined19:46
Marqin joined19:49
aberrant left19:49
SocalNick joined19:49
Norrin milki & some more guys that are out of my scrollback: thanks!19:49
git fetch; git cherry-pick is working out19:49
Sicp joined19:50
Sicp I want to see how far behind my origin is from master19:51
origin means my local..master, right?19:51
zacts left19:51
iksik joined19:51
iksik left19:51
iksik joined19:51
_ikke_ no19:52
iveqy origin it the remote you have cloned from19:52
_ikke_ It's the default name for the remote where you cloned from19:52
a remote is a shortcut to a url to another repository19:52
Sicp to the master19:52
no, I'm thinking in terms of using stuff like BitBucket and Github19:53
what I mean to say, I have a repository on one of those services and I push to it from local19:53
strictlyb joined19:53
iveqy Sicp: doesn't matter, mine and _ikke_'s description is still valid19:53
Sicp in this case, what is the one on that service called and what is the one on my local machine called?19:53
trungqtran left19:53
Sicp because I say "git add remote origin http://etc.", right?19:53
_ikke_ the one what?19:54
normanrichards joined19:54
_ikke_ yes19:54
Sicp exactly, what is the one I'm referring to :P19:54
a repo with one branch, the master branch19:54
iveqy Sicp: git remote -v will give you a list of your remotes and what is called what19:54
iksik left19:54
mmlac-bv joined19:54
_ikke_ What are you trying to name? The repository, the branch, what?19:54
pr0ggie joined19:55
acharlieh left19:55
jamiis left19:55
jackdempsey left19:55
Sicp one moment19:55
rosipov Sicp: you probably refer to remotes, correct?19:55
robbyoconnor left19:56
worstadmin joined19:56
Sicp I get it; the repo with the one master branch is on my local machine and I just add to it a remote on one of those services by virtue of adding that service's URL at the end of the "git add remote origin URL"19:56
gebi left19:57
iveqy Sicp: "the repo with the one master branch"?19:58
ziddey left19:58
iveqy Sicp: the default branchname in git is master, usually every repo has a master branch19:58
Sicp yea, after all it is a repository that I have when I "git init"19:58
and its only branch is master19:58
matanya left19:58
OOPMan left19:58
trungqtran joined19:58
Sicp yea, just was making it clearer to myself19:59
rosipov Sicp: git add remote name19:59
cin joined19:59
rosipov Sicp: doesn't have to be "origin", origin is a default19:59
Sicp so now the question is, how can I tell how far behind the master is from the remote that I added on Github or BitBucket19:59
_ikke_ Sicp: You first need to fetch from the remote20:00
Sicp only then will I be able to find how far off I've been?20:00
_ikke_ yes20:00
Sicp ok20:00
_ikke_ the git protocol allows for very little interrogation20:00
mdhopkins joined20:00
_ikke_ git ls-remote origin is all you can get20:00
Sicp so pushing if you're behind is out of the question, that's why that non-fast-forward error pops up when out of sync20:01
_ikke_ Sicp: Well, that has to do that you can't merge on the server20:01
mckendricks left20:01
IrishPrime left20:01
acharlieh joined20:02
nsanden joined20:02
HelloShitty i have a question20:03
nicholasruunu left20:03
Cromulent joined20:03
HelloShitty i was editing a file in my "git folder"20:03
then i have renamed that file with mv command20:03
Hoosier2016 left20:03
rfoust left20:03
HelloShitty but when i did git status20:03
oliveiraev left20:03
willob joined20:04
HelloShitty it showed me a deleted file and an untracked file20:04
Sicp stage it and it will recognize that it was a rename20:04
HelloShitty i have made git checkout -- file20:04
Hoosier2016 joined20:04
the8thbit joined20:04
jackdempsey joined20:04
HelloShitty but the file is still in the folder20:04
Sicp yes, stage that change you've made20:04
HelloShitty hum ok20:04
Sicp add it20:04
HelloShitty after that the old file will be gone from folder?20:05
rosipov HelloShitty: git add new_name && git rm old_name20:05
devoldmx joined20:05
Sicp it hasn't gone anywhere, it's still the same file and will still exist but that's how git recognizes renaming20:05
right?20:05
BSaboia left20:06
r0bby joined20:06
HelloShitty but i want it to be gone20:06
Sicp it wasn't created to be gone20:06
the8thbit Hello, I am very new to git and revision control, and I am having trouble understanding exactly how git works. I've created a local git repository, created a new branch, and checked out the new branch. Where is this branch stored, and how do I go about making changes to it?20:06
BSaboia joined20:06
iveqy the8thbit: !book !talks20:06
gitinfo the8thbit: 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 !parable20:06
the8thbit: Some good video talks about Git: [yt] http://goo.gl/z72s (Linus Torvalds: History&Concepts); [yt] http://goo.gl/R9H2q (Scott Chacon: Git basics, live examples); http://vimeo.com/35778382 (Randal Schwartz: Git basics, descriptional); http://vimeo.com/46010208 (Jesica Kerr: Git basics, descriptional)20:06
rosipov the8thbit: when you checkout branch contents of the directory become contents of the branch20:07
HelloShitty Sicp-20:07
rosipov left20:07
ziddey joined20:07
HelloShitty i was mistaken when i created the file20:07
rickruby joined20:07
HelloShitty so i have renamed it20:07
Sicp I would have removed it20:08
the8thbit rosipov: So if I make changes in the branch I created, and then switch to the master branch, should those changes go away?20:08
HelloShitty so i didn't want the file with the old name20:08
but now in folder is the old file with old name20:08
and the file with the new name20:08
the8thbit iveqy: Thanks, I'll check out that book20:08
intripoon joined20:08
devoldmx27 left20:09
Sicp try what rosipov said20:09
Cromulent left20:09
_iron joined20:10
hwrd|work left20:10
napping left20:10
johndo HelloShitty: that's because you did a git checkout -- file20:10
you will have to remove it (a 2nd time)20:11
voila left20:11
HelloShitty ok20:11
rfk left20:11
johndo the checkout restored thet file20:11
rickruby left20:12
HelloShitty and why is git preventing me of using the git commit -a -m "message" to skip the staging part?20:12
konundra left20:12
konundra joined20:12
ej left20:12
the8thbit iveqy: I'm reading this, thanks again for linking. All of the other resources I could find assumed that I already understood other contemporary version control systems.20:12
michaelarestad left20:13
acharlieh left20:13
_ikke_ HelloShitty: What do you mean, preventing you?20:13
HelloShitty it doesn't let me use that command20:13
_ikke_ HelloShitty: "doesn't let you"?20:13
HelloShitty: Be a little more specific20:13
HelloShitty: git commit -a doesn't add new files20:13
Charmi Hi, is there a way to exclude a folder while checking out a branch?20:14
pantsman joined20:14
iveqy Charmi: yes, but don't. It's complicated20:14
kermit left20:14
HelloShitty when i issue the command20:14
Charmi i would like to know about it20:14
HelloShitty git keeps telling me to use git add to add new files20:15
_ikke_ yes20:15
You need to explicitly tell git to track new files20:15
milki Norrin: awesome. just a little misunderstanding of the patch program and me forgetting about git apply then20:15
HelloShitty so what is the -a flag?20:16
isn't it to skip the staging part?20:16
Charmi @iveqy could you please tell how could I do the exclusion?20:16
cin left20:16
_ikke_ HelloShitty: It tells git to add every change to tracked files to the index (the stage), and commit that20:17
iveqy Charmi: sure, it's called a sparse checkout20:17
something like this: http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/20:17
Charmi: and git newer than 1.7.920:17
Charmi: and git newer than 1.7.0 i mean20:17
kadoban joined20:17
therealGent left20:17
daniel2_ joined20:19
Dante93 joined20:19
daniel2_ Hi. I am new to GIT. Is it possible to have a acc on bitbucket or github, create there a project and sync this project with my project, which is developed on my webserver via ftp?20:19
SHyx0rmZ left20:20
daniel2_ or does i have to develop local and always commit to the project on bitbucket?20:20
iveqy daniel2_: you can't control a git repo over ftp20:20
daniel2_: but otherwise, yes20:21
_ikke_ daniel2_: You work and commit local, and push that to for example bitbucket20:21
iveqy daniel2_: however !deploy20:21
gitinfo daniel2_: Git is not a deployment tool, but you can build one around it(in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/the-list-and-irc/deploy.html20:21
HelloShitty i don't know why but i can't see the new file in bitbucket20:21
Charmi @iveqy what exactly are "sub-tree of a repository"?20:21
JosephSilber left20:21
orthoplex64 will "git add -a" followed by "git commit -m "test"" be the same as "git commit -a "test""?20:21
daniel2_ iveqy, _ikke_ : thank you20:22
_ikke_ git add -a does not exist20:22
orthoplex64 320:22
oops20:22
I was trying to get a spec of dust out of my keyboard between my 3 and enter keys on the numpad20:22
cagedwisdom joined20:23
daniel2_ left20:23
iveqy Charmi: a path20:23
jhulten_ joined20:23
iveqy Charmi: or well, it can be many things, but in this case, a path and it contents, recursively20:23
Charmi @iveqy so, each folder is a new sub-tree?20:24
@iveqy each folder inside a repository20:24
jhulten left20:25
iveqy Charmi: almost20:25
kermit joined20:25
matanya joined20:26
Dante93 is there something on linux like the github for windows?20:26
SergeyPenkin left20:27
iveqy Dante93: github is a website, it works on all systems that have a decent webbrowser, even on linux20:27
johndo iveqy: is that also a kind of a sparse clone then? or does git still fetch the whole tree?20:27
Collin joined20:28
iveqy johndo: it's not a sparse clone, you can do a shallow clone (look at --depth in man git clone) but not a sparse one20:28
gitinfo johndo: the git-clone manpage is available at http://jk.gs/git-clone.html20:28
Dante93 i mean the github software for windows, the one you download20:28
psoo joined20:28
nathancahill joined20:29
adhawkinsadhawkins-away20:29
johndo iveqy: then I do not see much use for that, seeing how rather complicated it is20:29
HelloShitty what means when git status says that one branch is one commit or push (i can't remember well) ahed of some other branch?20:30
iveqy johndo: there's use for it in deployment scenarios, otherwise not. And I don't recommend using it20:30
raging_swine left20:30
johndo iveqy: ok, deployment, yes20:30
Sonderblade Dante93: there is wine :)20:30
Charmi @iveqy what could possibly go wrong with sparse checkout? I mean why were you suggesting not to use this?20:30
arand__ Dante93: No, nothing that's git-hub-specific like that.20:30
iveqy Dante93: well, depends on your needs. There's graphical git clients on linux, github has noone afaik. There's github programs for linux (none with GUI afaik)20:30
Dante93 ok thanks20:31
troker left20:31
onethfour left20:31
freestyl3r left20:31
iveqy Charmi: because it's complicated to setup and most users are doing something wrong if they try to use it the way svn do sparse checkouts.20:31
endiruna left20:32
iveqy Charmi: and it's just a checkout, not a clone, so the performance benefits are small20:32
proq why, when I checkout an older revision in my repo, do my submodules also not point to the version they were pointed to when that revision was current?20:32
Sendoushi left20:32
D4N3 joined20:32
iveqy proq: did you do a git submodule update?20:33
groglogic joined20:33
Dante93 left20:33
karihre joined20:33
michaelarestad joined20:34
HelloShitty What does this means:20:34
Your branch is ahead of 'main/master' by 1 commit.20:34
SocalNick left20:35
kevwil_ joined20:35
Charmi iveqy: i'll try this out on a dummy repository first. before moving onto big thing directly20:35
iveqy HelloShitty: what it says, main/master is one commit ahead of your branch20:35
joshsmith joined20:35
Charmi iveqy: thanks a lot for help20:35
iveqy Charmi: you're welcome20:36
matanya left20:36
proq iveqy: no, but that is beside the question. why should I have to run git submodule update incessantly?20:36
troker joined20:36
iveqy proq: you shouldn't, work is ongoing to improve submodules in that area, I'm not sure how far it has come20:37
kevwil left20:37
HelloShitty iveqy-20:37
my branch is master, right?20:37
jamiis joined20:37
iveqy HelloShitty: how would I know?20:37
SocalNick joined20:37
troker left20:37
mmlac-bv left20:37
raf_ joined20:38
proq iveqy: ah, ok. I've had to endure a lot of bitching from my team about that behavior, to the point where they are abandoning submodules altogether and I was just wondering20:38
tallest_red left20:38
iveqy proq: I'm a bit surprised that it hasn't already been done20:38
HelloShitty so how is master 1 commit ahed of main/master?20:38
_ikke_ HelloShitty: it means you made one commit you haven't pushed yet20:38
HelloShitty iveqy- i have one remote - main20:38
and 2 branches20:38
master and testing20:39
ah ok20:39
kadoban left20:39
HelloShitty and can i see what is that commit?20:39
h0bbit_ left20:40
karihre left20:40
iveqy HelloShitty: what is what commit?20:40
Learath2 joined20:40
gitinfo set mode: +v20:40
HelloShitty i can't remember what is missing in this branch20:41
kevwil_ left20:41
iveqy HelloShitty: gitk, git log, git diff, git status etc.20:41
Learath2 hey everyone :)20:41
troker joined20:41
tallest_red joined20:42
h0bbit left20:42
Mode-M left20:42
mckendricks joined20:43
Collin_ joined20:43
ej joined20:43
Davey left20:45
Andrevan left20:45
Collin left20:45
mizu_no_oto left20:45
insejn joined20:45
skylamer` joined20:45
Sicp left20:47
HelloShitty iveqy- git diff --staged, git diff --cached, git diff doesn't show anything20:48
:|20:48
mdhopkins left20:48
sainaen left20:49
iveqy HelloShitty: since I still not understand what you really are asking, I gave you a list of commands to use to examine your repo20:49
if git diff doesn't show anything, there's nothing changed20:49
akurilin joined20:50
paul424 left20:50
HelloShitty when i issue git status in my main remote, it says this:20:50
http://pastebin.com/f9KRYkGw20:50
matanya joined20:51
iveqy HelloShitty: okay?20:51
ej left20:51
insejn left20:51
Yakko left20:51
maslowbeer left20:52
HelloShitty and i can't understand what "Your branch is ahead of 'main/master' by 1 commit." means20:52
frankstallone left20:52
johndo HelloShitty: try gitk as iveqy said, it's a nice tool to understand what's going on in your repository20:52
iveqy HelloShitty: try !lol20:52
gitinfo HelloShitty: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all20:52
Charmi left20:52
iveqy HelloShitty: your branch has one commit that main/master doesn't have20:53
it's that simple20:53
tubbo joined20:53
tubbo so this is weird20:53
johndo HelloShitty: and you probably want git log main/master..20:53
longbeach left20:54
onethfour joined20:56
aquarius joined20:56
HelloShitty so let me see if i understood20:56
tubbo i'm pushing to a non-bare repo and i have a little hack script that git checkout's the branch from master to my feature branch20:56
spaceonline left20:56
sq-one left20:57
konundra left20:57
tubbo basically it goes `ssh: git checkout master`, `git push feature-branch`, `ssh: git checkout feature-branch`20:57
HelloShitty there is a local branch (in my computer) and there is a remote branch (the one in bitbucket, in my case), right?20:57
tubbo this is so i can push to the non-bare repo20:57
today, however, it stopped working20:57
iveqy HelloShitty: git branch -a to see all your branches20:57
HelloShitty and in my local branch i have one commit that is not yet commited to the remote branch, is that?20:57
tubbo whenever i run the ssh:git checkout master, it returns with an error saying that "error: Your local changes to the following files would be overwritten by checkout:"20:58
grzesag left20:58
iveqy tubbo: !broken and don't push to a non-bare repo =(, see !deploy20:58
gitinfo tubbo: [!doesntwork] We're sorry it doesn't work, but "it doesn't work" is about the worst problem description possible. Please give us some details, what exactly are you doing, what are you expecting to see and what are you seeing instead?20:58
tubbo: Git is not a deployment tool, but you can build one around it(in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/the-list-and-irc/deploy.html20:58
HelloShitty iveqy- i didn't know about that -a flag on branch option of git20:58
tubbo basically i edited some files on the server i'm pushing to, reset the changes, and every time i try to checkout a different branch it gives me that error. every time.20:58
iveqy tubbo: it looks like there's been changes to the worktree..20:58
tubbo basically i keep resetting the same change over and over again20:58
iveqy HelloShitty: man git branch tells you about them20:59
gitinfo HelloShitty: the git-branch manpage is available at http://jk.gs/git-branch.html20:59
tubbo iveqy: yeah but i'm trying to clear them out20:59
HelloShitty i'm reading the got pro book but i'm just at the beggining20:59
iveqy tubbo: git reset --hard HEAD fixes them and then you have to use git clean20:59
HelloShitty :)20:59
tubbo iveqy: okay, i did both20:59
that's on my feature-branch btw20:59
sferry left20:59
tubbo iveqy: the same exact thing happens21:00
iveqy tubbo: and you did them on your server?21:00
maxmanders joined21:00
kadoban joined21:00
ewnd9 left21:01
wakeup left21:01
tubbo iveqy: this is absically what i see https://gist.github.com/tubbo/f0be6e5f6a5d46296fbc21:01
basically* :)21:01
i run the `deploy` function21:01
wakeup joined21:01
HelloShitty iveqy- one last question21:01
Anders_J left21:01
HelloShitty is it possible to change an old commit message?21:01
tubbo i do understand that git is not a deployment tool, however this is the best solution i've found to push files from my local box to this test machine i have to use temporarily21:01
my problem with this is that it worked right up until i made that edit21:02
and now i can't get it to not recognize the edit21:02
iveqy tubbo: so, youir webapp creates a lockfile and you track that lockfile in git and tries to overwrite it21:02
tubbo it's really annoying21:02
iveqy: well i tracked it in git, but i didn't make it a commit21:02
so the updates to the lockfile shouldn't be in git at all21:03
iveqy tubbo: maybe you should read !deploy one more time... to find a better solution21:03
gitinfo tubbo: Git is not a deployment tool, but you can build one around it(in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/the-list-and-irc/deploy.html21:03
tubbo it seems like some file isn't getting written somewhere..21:03
lamarus left21:03
enr joined21:03
iveqy tubbo: if you track it how can it not be in a commit?21:03
tubbo iveqy: well what i mean is the changes that i made to it are not tracked.21:03
bil left21:03
tubbo i'm trying to reset them21:03
the actual file *is* tracked.21:03
iveqy tubbo: if you track it and you checkout a branch where that file isn't, it should be removed in the worktree21:04
tubbo: well, I guess we've found your error21:04
jamiis left21:04
iveqy HelloShitty: yes, git rebase -i21:04
HelloShitty: man git rebase21:04
gitinfo HelloShitty: the git-rebase manpage is available at http://jk.gs/git-rebase.html21:04
tatsuya_o joined21:04
acharlieh joined21:05
hwrd|work joined21:05
insejn joined21:05
freeed left21:06
ojacobson joined21:06
tubbo iveqy: what? no...21:07
mechanicalduck left21:07
tubbo iveqy: i did a git reset --hard HEAD21:07
or wait21:07
i guess that's not in the script.. :)21:07
enr left21:07
b4rt joined21:08
jhford is there a way to do a merge, such that the resulting diff is equivalent to having cherry-picked the change over?21:08
tubbo iveqy: that did it...strange, i didn't need that this morning :P21:08
tylerkern joined21:08
tpollard joined21:08
tubbo jhford: wouldn't that basically be a fast-forward merge?21:09
b4rt left21:09
jhford tubbo: ff merges require the parent of the commit to be the HEAD of the branch, right?21:09
tubbo jhford: yeah, is it possible for you to do that here?21:09
b4rt joined21:09
b4rt left21:09
maxmanders left21:09
jhford nope21:10
tubbo jhford: to do that you can rebase the branch you're going into with the branch you're currently on21:10
jkremser left21:10
crash\ left21:10
rabellamy left21:10
jhford that would alter history right?21:10
tubbo like if you're on feature-branch and you want to push to master, you can do `git checkout feature-branch; git rebase master; git checkout master; git merge feature-branch`21:10
crash\ joined21:10
tubbo that'll do a fast-forward21:10
breakingthings left21:10
tubbo jhford: that puts the commits you made on your feature "on top of" the commits that exist in master.21:10
and yes, rebase rewrites history21:10
jhford this is for a tool, and I won't be able to control the time between rebasing on master and merging21:10
tubbo or can, i should say21:10
jhford: huh? there are definitely plugins for git that do that21:11
git-process i believe21:11
jhford cool!21:11
jhford researches21:11
tubbo jhford: i like git-process, it really influenced my personal workflow21:11
jhford cool!21:11
Thra11_ joined21:12
v0n left21:12
jhford tubbo: https://github.com/jdigger/git-process ?21:12
HelloShitty sorry, i do have one more question21:12
jhulten joined21:12
private left21:13
jhulten_ left21:13
matanya left21:13
tubbo jhford: yup. i don't use it anymore but i've implemented most of its commands in ~/.gitconfig directly21:13
HelloShitty i don't know why, but when i do git clone git:mylin........21:13
jhford neat21:13
tubbo https://github.com/tubbo/dots/blob/master/config/gitconfig#L1921:13
HelloShitty the folder created is not the same has the folder that i have at this moment21:14
how can i fix this?21:14
tubbo HelloShitty: git clone <repo> .21:14
that '.' on the end is short for the current working directory to the shell, and specifying a folder after the repo will instruct git to clone into that folder21:14
HelloShitty For example: my working dir is program1 and when i clone my repo from bitbucket it comes like program-121:14
mmlac-bv joined21:15
HelloShitty How do i change that it bitbucket/git?21:15
FernandoBasso joined21:16
HelloShitty tubbo- i didn't understood your reply21:16
eijk_ left21:16
frege joined21:16
frege how do I tell git to not keep track a file anymore that used to be in the repo?21:17
konundra joined21:17
devth left21:18
johndo frege: add it to .gitignore and remove it from the repo21:18
frege johndo: remove with 'git rm x' ?21:18
Rescue9 joined21:18
johndo yes21:18
snow_ru who is julio hamano ?21:19
tubbo HelloShitty: you know how you do `git clone <repo>`?21:19
alvaro_o left21:19
HelloShitty i'm making a clone of some repo to my disk21:20
but the link to clone my repo has a different name than my working directory21:20
aberrant joined21:20
aryzing joined21:21
jackdempsey left21:21
HelloShitty can't i make the link to clone be case sensitive?21:21
aryzing hi, is it possible to run a diff on two files with different names on different commits?21:22
johndo HelloShitty: you can't change the link as this is the remote address of the repository21:22
but you can change the directory21:22
HelloShitty: man git clone21:22
gitinfo HelloShitty: the git-clone manpage is available at http://jk.gs/git-clone.html21:22
hellopat left21:22
hwrd|work left21:23
johndo aryzing: yes, you can diff any file at any revision (commit)21:23
LuxuryMode left21:23
johndo use commit:path21:23
HelloShitty So, i can't use working directories that are case sensitive?21:24
modInfo3 joined21:24
johndo HelloShitty: as I said, you can use as local directory what you want21:25
tylerker_ joined21:25
johndo see the last parameter of git clone in that man page21:25
aryzing johnda: thanks, ill try it out21:26
frege left21:26
Skrypt joined21:27
mizu_no_oto joined21:27
zhost left21:27
HelloShitty johndo- thanks21:28
donmichelangelo left21:30
lamarus joined21:30
PaulCapestany joined21:30
HelloShitty shit21:30
donmichelangelo joined21:30
mike_af left21:31
rednaks left21:31
HelloShitty is there any problem if i change the repo name in bitbucket repo settings?21:31
Fernando1asso joined21:32
szx left21:32
jeffery_ joined21:33
maslowbeer joined21:33
psoo left21:35
kesha__ left21:36
FernandoBasso left21:36
frege joined21:37
frege I did 'git rm file' it removed my file physically!!!!!!21:37
how can I get it back?21:37
I just didn't want to keep track of changes on that file21:37
Dante2k left21:37
johndo frege: did you already commit?21:38
frege johndo: yes :(21:38
johndo: you said add it to gitignore and do git rm21:38
I did that and it removed my file!21:38
rabellamy joined21:39
teejmya joined21:39
skylamer` left21:39
frege johndo: how do I bring it back?21:39
ah shit now it's gonna fuck with my other changes21:40
mfulz joined21:40
johndo git reset HEAD~ file21:40
git checkout file21:41
breck7_ joined21:41
johndo there's probably a one-line command ...21:41
frege but then it will revert all of my other changes21:41
tylerkern left21:41
breck7 left21:41
johndo frege: not if you add the file (with path)21:42
frege is there a way to just revert rm?21:42
m0viefreak git checkout HEAD -- file21:42
frege ah ok21:42
aard_ left21:42
johndo and use rm --cached for deleting it after21:42
tylerker_ left21:42
frege ) git checkout HEAD -- ./settings.py21:42
error: pathspec 'settings.py' did not match any file(s) known to git.21:42
m0viefreak if it was never actually tracked by git its gone for good21:43
frege no it was tracked by git21:43
OMGOMG there ought to be a git-subtract that did the opposite of add21:43
johndo frege: of course :), you already committed that removal21:43
frege: you need HEAD~21:43
ej joined21:44
frege right21:44
johndo: then?21:44
m0viefreak oh there was a commit, yeah then use 'git checkout HEAD~ -- file'21:44
frege Unstaged changes after reset:21:44
D mindlogs/mindlogs/settings.py21:44
m0viefreak or whatever revision contains it21:44
frege I got this now21:44
but I still don't see the file21:44
m0viefreak why did you reset?21:44
frege because johndo said21:44
mutex_mutex21:45
frege jiizz I'm panicing right now21:45
johndo maybe my fault21:45
emergion joined21:45
OMGOMG !dontpanic21:45
frege I really don't want to lose this file or my other changes, it was two days work21:45
OMGOMG !panic21:45
gitinfo [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts. Carefully go through the conflicts. Picking one side verbatim is not always the right choice!21:45
johndo frege: dont panic, everything you commited to git is not lost21:45
alvaro_o joined21:45
frege okay now I need a step by step approach to get out of this crisis :(21:46
m0viefreak what does your git status tell you right now?21:46
frege right now after that commit I ran johndo's command "git reset HEAD~ settings.py"21:46
PengooSabey21:46
m0viefreak so when you do 'git status' settings.py is the only file mentioned?21:47
frege let me paste somewhere21:47
yeah new https://dpaste.de/ek9Oy/21:47
mohoree_: https://dpaste.de/ek9Oy/21:47
oh shit21:47
sorry21:47
m0viefreak: https://dpaste.de/ek9Oy/21:47
ej left21:48
frege what should I do now?21:48
Dougie187 left21:48
m0viefreak whats the last commit? (git show / git log)21:48
is that the one of the removal?21:49
onethfour left21:49
frege commit 68fe70c96be369919fe5265dc76cefc3e86d9c7321:49
comment : 'the new search on topnav and git rm settings.py'21:49
glosoli left21:50
m0viefreak ok nothing lost then21:50
just need to clean up the index/ working directory21:50
johndo frege: looks like you only have to checkout settings.py21:50
godgodgodgo joined21:50
m0viefreak yep21:50
just do git checkout HEAD~ -- settings.py21:51
and it should be fine21:51
johndo but I'm not sure what is with the untracked files21:51
mishok13 left21:51
m0viefreak johndo: he doesnt seem to be using a .gitignore21:51
Hoosier2016 left21:51
johndo m0viefreak: he should since the last commit :), but probably an incomplete one21:52
frege I am using a .gitignore21:52
Dante2k joined21:52
frege and that file is still in my .gitignore21:52
johndo frege: that's ok21:53
frege oh cool21:53
it's back now21:53
satazor_ joined21:53
frege now how do I make it invisible to git?21:53
johndo but if you don't want all the files and directories git shows you as untracked you could add those also to the .gitignore21:53
m0viefreak post another 'git status'21:53
frege I don't want git to see changes21:53
new file: settings.py21:53
m0viefreak you need to unstage them21:53
git reset HEAD21:54
do that21:54
and make sure the file is still there21:54
and then make sure 'git status' is clean21:54
frege done21:54
awesome!21:54
there is no new file anymore21:54
and the file is still there21:54
m0viefreak all good then?21:54
frege thanks:)21:55
jacoluta joined21:55
frege johndo: thank you too21:55
m0viefreak one more thing, tho:21:55
if you push that removal and other people pull21:55
it WILL get deleted on THEIR end21:55
emergion left21:55
frege nice21:55
aldodelgado left21:55
frege that's exactly what I want :)21:55
johndo so does "git reset HEAD~ filename" reset the whole tree or only the given file?21:56
JSharpe left21:56
m0viefreak only the file21:56
it works for --mixed, but not for --hard21:56
i try to use checkout -- file instead of reset whenever possible21:56
johndo yes, git refuses --hard with a file21:57
that's why I suggested the two step with checkout as 2nd21:57
did not know it better :)21:57
m0viefreak giving a file spec to reset (--mixed) does NOT move the branch pointer21:58
onethfour joined21:59
mechanicalduck joined21:59
devth joined22:01
natechan left22:02
rabellamy left22:03
iAsterisk left22:03
Sonderblade left22:03
huoxito joined22:05
Ragnor left22:05
satazor_ left22:05
Nicholas_Rishel left22:06
lamarus left22:07
ll_ joined22:08
ll_ hello.22:08
gitinfo ll_: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.22:08
gitinfo set mode: +v22:08
ll_ hello.22:08
Ragnor joined22:09
ll_ i'd like git to refuse commits to a certain branch in a repository if it isn't signed (with gpg, using -S). what hook could i use for this?22:09
iAsterisk joined22:10
drizzd_ left22:10
foist joined22:10
lamarus joined22:11
pantsman left22:11
tpollard left22:12
rudak left22:12
TeckniX left22:13
kermit left22:14
trungqtran left22:14
|Freeman| left22:14
juanmabc joined22:14
kermit joined22:16
d2dchat joined22:16
Destos left22:16
normanrichards left22:17
jeffery_ left22:17
Nicholas_Rishel joined22:17
anonymuse left22:18
satazor_ joined22:19
foist left22:19
satazor_ left22:19
mizu_no_oto left22:19
satazor_ joined22:19
rednaks joined22:20
snow_ru ?22:20
comps ll_: hmm, git-commit doesn't seem to be able to sign commits using GPG .. or do I just have an old version?22:20
devoldmx3 joined22:20
foist joined22:20
tpollard joined22:21
devoldmx left22:21
ll_ comps: git commit -S. works with 1.7.10.4.22:21
comps ll_: as for the hook, that would be "update"22:21
probably22:21
ll_: I have 1.7.10.4, but there's no -S in git-commit manpage22:22
just -s for sign-off22:22
ll_ comps: it isn't documented, but it works.22:22
mechanicalduck left22:23
mizu_no_oto joined22:23
ll_ update is for pushes though, isn't it? i want something for the local repository.22:23
comps pre-commit ?22:24
just list the hooks directory22:24
and read the examples22:24
ll_ pre-commit runs before the commit message is set, and the message is one of the things that are being signed.22:25
comps then post-commit ... ?22:25
ll_ that says it can't affect the outcome of a commit... but i suppose it could force a reset.22:25
comps why do you even want to restrict users in such a way? ... this kind of enforcement makes sense on a remote repo22:25
ll_ i know, it doesn't add any security sincee anyone who can do commits can also edit the hooks.22:26
m0viefreak you probably want a commit-msg hook22:27
gittish joined22:27
m0viefreak hmm, nope, that does not get the sha22:27
anonymuse joined22:27
melee left22:28
ll_ i just want something that makes sure that i don't forget to sign commits to the master branch, so i don't have to sign them all when i eventually push them.22:29
willob left22:29
ll_ which (in maximal paranoia mode) would include going through all the committed unsigned code and make sure that it hadn't been modified).22:29
m0viefreak how about a simple post-commit hook then?22:29
you can have it simply spit something like "you did not sign your last commit, please ammend"22:30
or whatever22:30
melee joined22:30
m0viefreak so it doesn't block your workflow if you dont feel like signing at the time22:30
michaelarestad left22:30
ll_ yeah, i'll probably do that. maybe check it out to a separate branch and reset the master branch to the parent if it isn't signed.22:30
verysoftoiletppr joined22:31
SocalNick left22:31
verysoftoiletppr left22:31
verysoftoiletppr joined22:31
melee_ joined22:31
SocalNick joined22:32
comps or fire up git commit --amend -S -C HEAD22:32
or so22:32
SocalNick left22:33
foist left22:33
SocalNick_ joined22:33
jamiis joined22:34
melee left22:34
foist joined22:34
frege left22:36
foist left22:36
pdx left22:36
sampiero left22:36
Thra11_ left22:37
foist joined22:37
chuckharmston left22:38
Balliad joined22:38
pr0ton joined22:39
jerius left22:39
darinm joined22:39
GT4066 joined22:40
voiceofgrog joined22:40
Hoosier2016 joined22:41
foist left22:41
foist joined22:42
mklappstuhl left22:43
madewokherd joined22:43
melee_melee22:44
ej joined22:44
lamarus left22:45
godgodgodgo left22:45
Kabaka left22:45
xpirator joined22:47
foist left22:47
train_or joined22:47
foist joined22:48
ej left22:49
Hoosier2016 left22:49
Kabaka joined22:50
simesy joined22:50
gittish left22:51
foist left22:51
emergion joined22:52
rabellamy joined22:52
jon_r joined22:53
Tuna-Fish left22:53
foist joined22:53
groglogic left22:55
foist left22:55
anonymuse left22:56
foist joined22:56
Tuna-Fish joined22:57
foist left22:58
emergion left22:58
HariboPenguinHariboPenguin|Of22:58
tylerkern joined22:58
Balliad left22:59
ll_ left22:59
jamiis left22:59
foist joined22:59
lavaman left23:00
Joshi3s` joined23:00
warlock_mza joined23:02
foist left23:02
devoldmx3 left23:02
devoldmx joined23:02
hide_ joined23:03
foist joined23:03
tatsuya_o left23:03
Bucciarati joined23:03
Tuna-Fish left23:03
iveqy joined23:03
Kamal_ joined23:03
Tuna-Fish joined23:03
BeerSerc joined23:04
Kamal_Guest6542523:04
enr joined23:04
LuxuryMode joined23:04
tubbo left23:04
tubbo joined23:04
halfie joined23:04
luto joined23:05
pygmael joined23:05
RichardBronosky joined23:05
SocalNick_ left23:06
foist left23:06
LuxuryMode left23:06
foist joined23:08
enr left23:08
ukgamer left23:08
acharlieh left23:09
acharlieh joined23:09
m8 left23:10
nova_ left23:10
teejmya left23:10
acharlieh left23:10
SuperDMP left23:11
Guest93127nitrodex23:12
foist left23:12
Rescue9 question: my system broke so I had to rebuild. I have patches submitted to a gerrit. the SHA of the patch doesn't match the SHA of the checkout I just did on the package. Is there a way to change the SHA "Change ID"? Is having a different SHA going to be an issue when I reupload the patch to a gerrit?23:12
verysoftoiletppr left23:13
foist joined23:13
ukgamer joined23:14
g0bl1n joined23:15
foist left23:15
raf_ left23:16
dik_dak joined23:16
foist joined23:16
_iron left23:18
foist left23:18
devoldmx left23:19
foist joined23:19
strictlyb left23:20
enr^ left23:20
chrob left23:21
LBV_User joined23:21
iveqy Rescue9: do you know what a sha1 is?23:23
foist left23:23
michaelarestad joined23:24
rabellamy left23:24
foist joined23:24
SocalNick joined23:25
Rescue9 Well...... lol. not really. I'm just curious if a different SHA is going to be a problem when I push my next patch23:25
LuxuryMode joined23:25
iveqy Rescue9: a sha1 is a hash, it's a fingerprint of your commit, unique to every commit in existense23:25
aryzing hi, one of my commits has a short and a long message, but the longer message gets cut off with $ git log, how can I view the entire message?23:26
iveqy Rescue9: if your the uploaded commits sha1 differs from your local rebuilt sha1, it's not the same commit23:26
Rescue9: and that means that you've failed with your rebuild and needs to find the error23:26
Skrypt left23:26
iveqy aryzing: man git log or man git show23:27
gitinfo aryzing: the git-log manpage is available at http://jk.gs/git-log.html23:27
aryzing: the git-show manpage is available at http://jk.gs/git-show.html23:27
DolpheenDream joined23:28
foist left23:28
jamiis joined23:28
zbcm_ joined23:28
raf_ joined23:29
LuxuryMode left23:29
foist joined23:30
KernelPanicMK2 joined23:31
Rescue9 iveqy: thanks for the info! I found the issue. I downloaded the wrong patch set. I now have the correct one and the hash matches.23:31
Nice to finally understand.... the 'fingerprint' analogy helped.23:31
devoldmx3 joined23:32
foist left23:32
PeterBooker left23:33
iliketurtles left23:33
foist joined23:34
sampiero joined23:36
tinti_ joined23:36
_BJFreeman joined23:36
decotii left23:37
foist left23:37
_BJFreemanBJfreeman23:38
primitive left23:39
foist joined23:39
teejmya joined23:40
teejmya left23:41
teejmya joined23:41
PeterBooker joined23:42
HelloShitty left23:43
aberrant left23:44
jayfk left23:44
maroloccio joined23:44
ej joined23:45
rurufufuss left23:45
SocalNick left23:45
Inside joined23:45
gmac left23:46
ZujkisNx left23:47
iliketurtles joined23:47
devoldmx joined23:48
devoldmx_ joined23:48
ej left23:49
Noldorin left23:49
oriba joined23:49
Fernando1assoFernandoBasso23:49
Noldorin joined23:50
mmlac-bv left23:50
bandroidx left23:50
squentin joined23:50
bandroidx joined23:51
devoldmx3 left23:51
enr joined23:51
zacts joined23:52
melee left23:52
devoldmx_ left23:53
joshsmith left23:54
mcepl left23:54
foist left23:55
Joshi3s` left23:56
scorphus git grep rocks! wow23:56
foist joined23:56
Rylai Hey, #git. I was thinking about symlinking all of the conf files I need for a specific application (nginx with php) to a folder in /root/ or somewhere and using git to track changes made to them. Is there any way to do this?23:57
juanmabc left23:57
R1KRDO joined23:58
R1KRDO left23:58
deuterium left23:59
jon_r left23:59
tubbo left23:59

Logs Search ←Prev date Next date→ Channels Documentation