IRCloggy #git 2014-09-26

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.

2014-09-26

fstd left00:00
afhammad joined00:00
fstd joined00:00
ColKurtz left00:01
MistuhKurtz joined00:01
ianbrandt left00:03
kristofferR joined00:04
Vivekananda_y510 joined00:04
revyd joined00:04
KrofDrakula left00:05
tmcmahon left00:06
PaulCapestany left00:06
HedgeMage joined00:06
jdrumheller left00:06
Sebtoast joined00:06
Motoko joined00:06
ropav joined00:07
kristoff_ left00:07
danemacmillan left00:08
PaulCapestany joined00:08
ki0 joined00:08
moritzschaefer joined00:09
endiruna left00:09
hahuang65 left00:09
MistuhKurtz left00:10
Sebtoast left00:10
jenni_naiaretti left00:11
danemacmillan joined00:11
Drool joined00:12
Sebtoast joined00:12
Peuc2 joined00:12
mribeirodantas joined00:12
ki0 left00:12
ecky--ptang-zoob left00:12
Droolio left00:13
booboy left00:13
ecky--ptang-zoob joined00:13
bedouin_bedouin00:13
booboy joined00:15
ropav left00:15
ColKurtz joined00:15
Peuc left00:15
Peuc2Peuc00:15
damccull joined00:16
howitdo left00:16
amikiri joined00:16
imkmf left00:16
Apocalis_ left00:16
nodekid left00:19
howitdo joined00:23
ropav joined00:23
ehmatthes joined00:24
howitdo left00:24
CheckDavid left00:24
AdrianGuenter_ left00:25
ropav left00:25
nodekid joined00:26
boombatower left00:26
amalloy left00:27
howitdo joined00:27
howitdo left00:27
noonian left00:29
GreZephyr1123 joined00:29
ropav joined00:30
jonr22 left00:30
hahuang65 joined00:30
imachuchu left00:31
archdori joined00:32
robarelli joined00:32
eletuchy joined00:34
ropav left00:34
sean_ joined00:34
maslowbeer left00:34
zanchoPa1sa left00:35
baweaver left00:35
Quevin left00:36
fatalhalt joined00:36
baweaver joined00:36
jonr22 joined00:36
tokik joined00:37
moritzschaefer left00:37
robarelli left00:37
ropav joined00:38
GreZephyr1123 left00:39
nath_schwarz left00:40
skynxnex joined00:40
MattMake_ left00:40
nb_bez__ joined00:41
MattMaker joined00:41
ropav left00:41
harish_ left00:42
martinklepsch left00:43
jonmorehouse joined00:44
sean_ left00:45
MattMake_ joined00:45
skynxnex left00:45
am0khuman left00:45
simesy joined00:45
jottr left00:46
wakd joined00:46
ropav joined00:47
neonixcoder joined00:47
simesy left00:47
simesy joined00:47
thiago left00:48
MattMaker left00:48
ropav left00:48
msmith_ joined00:48
mueslo left00:49
simesy left00:49
simesy joined00:49
kballou left00:50
decompiled left00:50
neonixcoder left00:51
loz-- left00:51
loz--_ joined00:51
Macaveli joined00:51
nodekid_ joined00:51
ErKa left00:52
Neozonz joined00:53
msmith_ left00:53
nodekid left00:53
snuffeluffegus joined00:54
wrouesnel1 joined00:54
seanmerron left00:54
zivester joined00:55
Sasazuka left00:55
EminenceHC joined00:56
marscher joined00:56
ajustrun joined00:58
jon_r left00:58
zahlman left00:59
ehmatthes left00:59
roflin left01:00
roflin joined01:00
EminenceHC left01:01
eto left01:01
dccc left01:01
akushner__ joined01:01
ferreum` joined01:03
eto joined01:03
einonm left01:03
kaendfinger joined01:04
Mobutils joined01:05
akushner_ left01:05
baweaver left01:05
johtso left01:05
pheaver joined01:05
akushner__ left01:05
kpease joined01:06
ferreum_ left01:06
afhammad left01:06
hyperair left01:07
MattMake_ left01:07
hmsimha_ left01:08
lukeholder joined01:08
jon_r joined01:08
ki0 joined01:09
howitdo joined01:09
msmith_ joined01:09
veebers left01:09
kpease left01:10
tinti left01:10
watabou joined01:10
MattMaker joined01:12
ki0 left01:13
ColKurtz left01:14
ColKurtz joined01:15
einonm joined01:15
mellernoia joined01:16
Mso150_u joined01:17
zahlman joined01:18
gitinfo set mode: +v01:18
MattMaker left01:18
zahlman how can I purge the repository of normally unreachable commits? I happen to have recorded some commit IDs for branches 'left behind in detached HEAD mode', and have found that I can actually `checkout` them again; I'd like them really gone.01:19
hahuang65 left01:19
sgen_ left01:19
k_sze[work] joined01:20
smccarthy joined01:20
zahlman I thought `git prune` would do the trick, but it seems not to have.01:21
maestrojed left01:23
hahuang65 joined01:23
pombreda left01:24
Macaveli left01:24
gfixlerGuest9460601:25
refried_ joined01:25
sgen_ joined01:25
gfixler_ git gc01:26
jhassjhass|off01:27
ajustrun left01:27
daito joined01:27
helgikrs3 joined01:28
Neozonz left01:30
imMute zahlman: git gc with some options, or just wait a month.01:30
Vampire0_ joined01:30
nettoweb joined01:30
Warrior-kk joined01:30
Goplat joined01:31
nath_schwarz joined01:31
mdel left01:32
Sebtoast left01:33
toothrot joined01:33
Vampire0 left01:34
zahlman imMute: I tried that. After setting the appropriate config option, the total number of objects went way down, but I can still reach my test 'zombie' commit o_O01:34
robarelli joined01:34
jonr22 left01:35
zahlman (and doing so seems to have added some objects...)01:35
imMute does "git fsck --unreachable" list that commit as unreachable?01:35
pwnz0r left01:37
zahlman Yes.01:37
imMute and you did "git gc --aggressive --prune=all" ?01:38
Pyrogerg joined01:38
robarelli left01:39
zahlman ... not after making the config change; let me try it again.01:39
ok; now nothing is reported unreachable; so if that means what it ought to...01:39
rchavik joined01:40
zahlman excellent, everything's clean now.01:40
dgpalmer left01:41
harish_ joined01:41
skynxnex joined01:41
zahlman why isn't `git remote -v` showing me a url for the remote?01:42
lyang0 left01:43
imMute becaues you need to tell it *which* remote you want verbose info about01:43
er01:43
you need "git remote -v show"01:43
zahlman it just says 'origin'. Are there 0..N urls associated with a remote or something?01:44
MutSbeta left01:44
imMute no, just one.01:44
well, two (one for push, one for pull)01:45
even "git remote -v" shows the URL for me. what version of Git do you have?01:45
zahlman ...so then what am I to make of `git remote set-url --add` o_O01:45
skynxnex left01:46
zahlman I just updated by getting github's current windows package, which claims to have 1.9.4.01:46
(.msysgit.1, if it matters)01:46
rdbell left01:46
imMute ... uh. maybe it does support multiple URLs...01:46
learn something new every day01:46
rdbell joined01:47
zahlman I can *vaguely* imagine how it would be useful.01:47
lyang0 joined01:47
otter768 joined01:47
jon_r left01:49
hyperair joined01:49
dsdeiz_ left01:50
Mso150_u left01:50
refried_ left01:50
rdbell left01:52
veebers joined01:52
hahuang65 left01:52
mribeirodantas left01:52
otter768 left01:53
darkbasic left01:54
darkbasic joined01:55
listochkin joined01:55
zahlman When I do `git rev-list HEAD`, that only shows commits on the current branch, right? Is there a direct way to list the entire repository?01:57
jonr22 joined01:58
imMute git log --all ?01:58
hell, git rev-list --all01:58
jpf_ joined01:59
_lrh_ left01:59
DolpheenDream left01:59
listochkin left02:00
msmith_ left02:00
zahlman aha, rev-list also accepts --all, excellent.02:01
dreiss left02:01
zahlman so I can feed that to wc -l for statistical purposes, for example.02:01
EminenceHC joined02:01
booboy left02:01
msmith_ joined02:02
desposo left02:02
jpf left02:02
pheaver left02:02
m0viefreak left02:02
jpf_ left02:03
it0a joined02:03
JosephFerano left02:04
JosephFerano joined02:04
EminenceHC left02:05
msonntag left02:06
kaendfinger left02:06
zacg joined02:07
zacg left02:07
zacg joined02:07
diegoviola joined02:07
msonntag joined02:08
yacks joined02:08
ki0 joined02:08
tanath left02:09
JosephFerano left02:09
mscook left02:09
joelteon joined02:09
joelteon is it possible to ignore, but not remove with git clean -X, certain files?02:10
jon_r joined02:10
tanath joined02:11
msmith_ left02:13
ColKurtz left02:13
ki0 left02:13
zivester left02:16
atomx_ left02:19
acharlieh joined02:19
jonr22 left02:21
howitdo left02:23
marscher left02:24
alvaro_o left02:26
mscook joined02:26
robbyoconnor left02:27
msmith_ joined02:27
mscook left02:27
robbyoconnor joined02:27
mscook joined02:28
mellernoia left02:29
cads joined02:29
jonmorehouse left02:29
maestrojed joined02:29
joelm left02:31
maslowbeer joined02:32
Quevin joined02:32
jonr22 joined02:33
Noldorin left02:33
joelm joined02:33
iamjarvo joined02:33
Xiti left02:33
devoldmx joined02:34
robarelli joined02:35
Darkle joined02:35
Quevin left02:36
otter768 joined02:36
jonr22 left02:36
Nazrhom_ joined02:37
amikiri left02:37
jonr22 joined02:37
howitdo joined02:37
devoldmx3 left02:38
Dougie187 left02:38
msmith_ left02:39
robarelli left02:39
acharlieh left02:40
Dougie187 joined02:41
Nazrhom_ left02:41
muhaha03__ joined02:41
skynxnex joined02:42
DolpheenDream joined02:43
howitdo left02:44
it0a left02:44
Enekk left02:45
hagabaka left02:46
skynxnex left02:47
acharlieh joined02:48
jpf joined02:48
hagabaka joined02:49
jpf left02:50
acharlieh left02:51
pwnz0r joined02:52
jpf joined02:53
arup_r joined02:56
howitdo joined02:57
xp_prg what is the command to see all the differences in a particular directory, I tried git diff but it did all directories, not the one I was currently in02:57
c0ded left02:57
imMute git diff .02:58
arup_r left02:58
xp_prg I heart you inMute :>02:58
Mitchbones left02:58
nettoweb left02:58
pheaver joined02:59
nb_bez__ left03:01
ome joined03:04
jitendravyas joined03:04
EminenceHC joined03:04
c0ded joined03:05
maestrojed left03:06
msmith_ joined03:07
msmith_ left03:08
EminenceHC left03:08
xcyclist left03:09
maestrojed joined03:14
sgen_ left03:16
blakbunnie27 left03:17
jonr22 left03:17
Consuela left03:18
fission6 joined03:18
LucasTT left03:18
lng Hi! Merge failed because the file was deleted in a branch while it was modified on master. How to force merge to delete this file?03:19
Hello71 !eek03:19
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 then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II03:19
Carl_ joined03:20
lng Hello71: this info is too basic03:20
Hello71: you just learnt how to query bot?03:21
pheaver left03:22
maestrojed left03:23
maestrojed joined03:23
pheaver joined03:25
BuenGenio joined03:26
imMute lng: no, we just get the same questions over and over, so we made a FAQ bot03:28
toothrot left03:30
Pyrogerg left03:31
kukks left03:31
Pyrogerg joined03:31
lng solved with rebasing03:32
maestrojed left03:32
BuenGenio_ joined03:33
BuenGenio left03:34
otter768 left03:35
otter768 joined03:36
kermit left03:36
rdbell joined03:36
robarelli joined03:37
Xiti joined03:37
kermit joined03:37
BuenGenio_ left03:37
iamjarvo left03:37
zahlman left03:39
otter768 left03:40
Dougie187 left03:41
hagabaka left03:41
robarelli left03:42
skynxnex joined03:42
lindenle left03:43
DolpheenDream left03:43
lindenle joined03:43
hagabaka joined03:45
worc left03:46
DolpheenDream joined03:46
skynxnex left03:47
marchelzo_ left03:47
worc joined03:47
mscook left03:47
glosoli joined03:48
TwoSheds joined03:49
gitinfo set mode: +v03:49
TwoSheds hi all03:49
Carl_ left03:49
TwoSheds left03:51
joelm left03:52
mscook joined03:52
jerius joined03:53
blakbunnie27 joined03:53
listochkin joined03:54
joelm joined03:55
jonmorehouse joined03:56
GT4066 joined03:58
lindenle left03:58
listochkin left03:59
monitti joined03:59
awkwardusername joined03:59
glosoli left04:00
smw joined04:00
thiago joined04:00
smw left04:01
smw joined04:01
nodekid_ left04:01
Tuna-Fish left04:02
Darkle left04:04
lacrymology joined04:04
nodekid joined04:04
Darkle joined04:04
amikiri joined04:05
lacrymology I've got TOPIC which has been merged into DEVELOP, how can I see only the changes introduced by TOPIC? I'm doing `git diff DEVELOP...TOPIC` but it's returning empty, I guess because it's merged already04:05
BuenGenio_ joined04:05
lacrymology and if I do TOPIC...DEVELOP I get what's NOT in TOPIC04:06
Darkle left04:06
chessguy joined04:06
fission6 left04:07
lacrymology if I do DEVELOP^...TOPIC it works04:08
DEVELOP^2...TOPIC actually04:09
EminenceHC joined04:09
thiago there you go04:09
ChanServ set mode: +o04:10
thiago set mode: +b04:10
thiago kicked monitti (spamming the channel)04:10
thiago set mode: -o04:10
daito left04:11
shauna left04:11
daito joined04:12
lindenle joined04:12
fatalhalt left04:12
allouis________ left04:13
titusjose_______ left04:13
smw left04:13
Tuna-Fish joined04:13
smw joined04:13
watabou left04:13
shennyg__ left04:13
allouis________ joined04:13
EminenceHC left04:13
titusjose_______ joined04:14
shauna joined04:14
ande joined04:15
andeGuest393404:15
shennyg__ joined04:15
daito left04:16
irqq joined04:16
watabou joined04:16
watabou left04:16
watabou joined04:16
JosephFerano joined04:17
imMute thiago: delayed reaction?04:18
DolpheenDream left04:19
msmith_ joined04:19
ItSANgo left04:20
chessguy left04:20
lindenle left04:21
smw left04:21
dropdrive left04:22
asakura left04:22
jitendravyas left04:23
hagabaka left04:23
bbloom left04:23
msmith_ left04:23
lindenle joined04:24
farn left04:25
kpreid left04:25
kpreid joined04:26
dv_ joined04:27
dv__ left04:27
hagabaka joined04:28
BuenGenio_ left04:29
a_le left04:32
lindenle left04:33
Quevin joined04:33
pwnz0r left04:34
nonmadden left04:36
lindenle joined04:37
BuenGenio joined04:38
Quevin left04:38
robarelli joined04:39
jimmyy left04:40
amikiri left04:41
glosoli joined04:41
zumba_ad_ joined04:42
lindenle left04:43
robarelli left04:43
subhojit777 joined04:43
skynxnex joined04:43
lindenle joined04:45
tvw joined04:45
zumba_addict left04:46
jimmyy joined04:47
skynxnex left04:48
jimmyy left04:48
BuenGenio left04:49
irqq left04:50
kiran joined04:51
lindenle left04:57
simesy left04:59
smw joined04:59
DanMAbraham joined04:59
lindenle joined05:00
simesy joined05:01
thiago imMute: no, it wasn't delayed05:01
zoso joined05:01
Gamecubic left05:02
danemacmillan left05:02
UmbraMalison_ left05:03
snuffeluffegus left05:03
unglid left05:04
MattMaker joined05:04
mscook left05:04
UmbraMalison joined05:05
mennea joined05:06
lindenle left05:07
lindenle joined05:08
PinkSpecs joined05:08
smccarthy left05:08
veebers left05:09
unglid joined05:09
sinkensabe joined05:12
EminenceHC joined05:13
zacg left05:14
koderok joined05:15
Lyqyd left05:15
Jarboe left05:16
BuenGenio joined05:16
BuenGenio left05:16
beautifulmind joined05:17
EminenceHC left05:18
BuenGenio joined05:18
madewokherd left05:18
RogerWS_ left05:18
ecky--ptang-zoob left05:19
RogerWS joined05:19
mmattice joined05:19
ecky--ptang-zoob joined05:19
mscook joined05:21
kopparam joined05:21
BuenGenio left05:21
asakura joined05:23
jceb joined05:23
sinkensabe left05:24
daito joined05:25
mscook left05:26
PinkSpecs left05:28
lindenle left05:29
sinkensabe joined05:29
jontmorehouse joined05:31
astrofog joined05:33
gargola left05:33
jonmorehouse left05:33
mennea left05:33
sinkensabe left05:33
vital joined05:35
mscook joined05:35
watabou left05:36
astrofog left05:36
dreiss joined05:37
thevishy joined05:38
thevishy_home joined05:38
tpollard left05:38
BuenGenio joined05:38
justinmburrous joined05:38
wrouesnel3 joined05:39
mennea joined05:39
robarelli joined05:39
nonmadden joined05:40
mscook left05:40
Junior` joined05:40
robarelli left05:45
starkhalo left05:45
ThomasLocke joined05:45
dreiss left05:46
arup_r joined05:46
kyb3r_ joined05:46
Fissure left05:47
JosephFerano left05:47
Mobutils left05:47
Guest12022 left05:48
sdrfnord1 left05:48
Fissure joined05:49
olspookishmagus joined05:49
lindenle joined05:49
nonmadden left05:49
nonmadden joined05:50
kopparam left05:51
kopparam joined05:51
rob_w joined05:52
rob_w left05:52
rob_w joined05:53
smw left05:54
smw joined05:55
Silmarilion joined05:55
kopparam left05:56
lindenle left05:58
chessguy joined05:58
thevishy_home left05:59
thevishy left06:00
saurabh joined06:00
saurabhGuest7362506:00
lindenle joined06:03
darkbasic left06:03
mscook joined06:04
darkbasic joined06:04
Sasazuka joined06:04
kopparam joined06:04
chessguy left06:05
mscook left06:08
ItSANgo joined06:09
jontmorehouse left06:09
Streward left06:11
daito left06:11
daito joined06:11
ciampix joined06:12
lindenle left06:12
dreiss joined06:12
FilipNortic joined06:12
lindenle joined06:12
KeelOfSteel joined06:13
blubberbop left06:14
roelmonnens joined06:15
Sasazuka left06:15
daito left06:15
GluonQuark joined06:17
booboy joined06:17
Sasazuka joined06:18
Mobutils joined06:18
EminenceHC joined06:18
vgarg joined06:18
mscook joined06:19
acolson joined06:20
gfixler_ left06:20
mennea left06:20
mennea joined06:20
skynxnex joined06:20
northfurr left06:21
skynxnex left06:21
skynxnex joined06:21
LeMike joined06:21
daito joined06:22
freimatz joined06:22
oojacoboo left06:22
govg left06:23
nnyk joined06:23
EminenceHC left06:23
thevishy joined06:23
thevishy_home joined06:23
mscook left06:24
Goplat left06:24
govg joined06:24
lindenle left06:27
jontmorehouse joined06:28
jwmann left06:28
piccata left06:28
jwmann joined06:28
sitaram joined06:29
sitaram left06:29
sitaram joined06:29
snuttilatti_ joined06:29
joevandyk left06:29
piccata joined06:29
LLaurent left06:29
olspookishmagus left06:29
Floatingman left06:29
tank100 left06:29
ToxicFrog left06:29
cite joined06:30
qdii joined06:30
jimmyy joined06:31
purpleidea joined06:31
joevandyk joined06:31
esc joined06:31
olspookishmagus joined06:31
esc left06:31
esc joined06:31
tank100 joined06:31
olspookishmagusGuest2179006:32
jontmorehouse left06:33
lindenle joined06:33
dreiss left06:33
Quevin joined06:34
Mso150_u joined06:35
heavystorm joined06:35
jagob joined06:35
ToxicFrog joined06:35
lacrymology left06:35
__main__ joined06:36
Bucciarati joined06:36
uber joined06:36
uber left06:36
nfk joined06:36
uber joined06:36
jontmorehouse joined06:37
lacrymology joined06:37
lun_ left06:38
Quevin left06:38
nilg joined06:40
sohail left06:41
robarelli joined06:41
lindenle left06:42
lun_ joined06:42
Floatingman joined06:43
gauke joined06:44
pheaver left06:45
Vivekananda left06:45
mscook joined06:46
jagob left06:47
robarelli left06:47
King_Hual joined06:47
mennea left06:50
encod3 joined06:50
mscook left06:50
mennea joined06:50
awkwardusername left06:52
awkwardusername joined06:53
mlechner joined06:53
t4nk598 joined06:54
nnyk left06:55
t4nk598 hi guys, short question: if i want to create a new repository on a server i would need to log in via ssh right?06:55
Sajbar if you don't have direct access to the server yes:)06:56
lacrymology left06:56
t4nk598 i exist as a git user. (whatever that exactly means)06:56
so that is not sufficient?06:56
FunkyAss joined06:57
jpf left06:59
_ikke_ nope07:00
Sasazuka left07:00
otter768 joined07:00
ThomasLocke left07:01
ThomasLocke joined07:02
osse t4nk598: does the server have a web interface or something like that? stash? gitlab? github? gitorious?07:02
jon_r left07:02
mscook joined07:02
Sasazuka joined07:02
encod3 left07:03
t4nk598 osse: no :(07:03
avvs joined07:04
osse t4nk598: then you need shell access07:04
mscook_ joined07:04
dropdrive joined07:04
hebz0rl joined07:04
osse something like curl -U '() { :;}; cd /repos; mkdir project; git init --bare' https://companygitserver.com should do the trick07:05
Sasazuka left07:05
otter768 left07:05
luto left07:05
luto joined07:05
luto osse: lol.07:05
osse woops, forgot to cd into the project07:05
Gabri joined07:05
Warrior-kk left07:06
Warrior-kk joined07:07
acl_ left07:07
bbloom joined07:07
mscook left07:07
sdrfnord1 joined07:07
kristofferR left07:08
mscook_ left07:09
farn joined07:09
t4nk598 osse: k thx07:09
eletuchy left07:09
Xiti` joined07:09
osse t4nk598: but in reality I assume it means sending an email to the server admin or something like that07:09
t4nk598: CC your boss, so the admin knows it's serious stuff07:09
thevishy_home left07:09
thevishy left07:10
avvs left07:10
jceb left07:11
aswen joined07:12
Nazrhom joined07:12
Xiti left07:13
Nazrhom left07:13
cvanball joined07:13
alorence joined07:13
Nazrhom joined07:13
t4nk598 osse: lol now i got it ^^07:14
i dont think the server admins would be super happy if i did that ;)07:15
kopparam left07:15
piccata left07:15
koderok left07:16
piccata joined07:16
lacrymology joined07:17
skylite joined07:18
smw left07:18
robbyoconnor left07:18
mennea left07:20
mennea joined07:21
durre joined07:21
petersr joined07:21
intellix joined07:21
endiruna joined07:21
GGflags joined07:22
EminenceHC joined07:22
thiago left07:23
avvs joined07:23
zapb_ joined07:24
mkaesz joined07:25
kriks joined07:25
gua_ould joined07:26
jargon joined07:26
cbr_ joined07:26
EminenceHC left07:27
EminenceHC joined07:31
seschwar joined07:31
Marcus joined07:34
subhojit777 left07:34
xobb left07:35
polyzen left07:36
justinmburrous left07:36
Malsasa_ joined07:36
WormDrink joined07:37
subhojit777 joined07:37
noxd joined07:37
Malsasa left07:37
encod3 joined07:38
Malsasa_Malsasa07:38
harish_ left07:38
prettyd joined07:38
ghostlin_ joined07:39
mennea left07:40
encod3 left07:40
encod3 joined07:40
xobb joined07:41
EminenceHC left07:42
jnavila joined07:42
Trudko joined07:42
EminenceHC joined07:42
mlnppy joined07:43
jnavila left07:43
jnavila_ joined07:43
robarelli joined07:44
lindenle joined07:44
prettyd left07:44
nnyk joined07:45
prettyd joined07:45
rchavik left07:46
himikof left07:46
EminenceHC left07:47
hebz0rl left07:48
jitendravyas joined07:48
lindenle left07:48
prettyd left07:48
prettyd joined07:49
jitendravyas Hi07:49
Everytime I run git pull --rebase gerrit master07:49
p4trix joined07:49
jitendravyas want to run Bundle install after that automatically07:49
How can I do that07:49
robarelli left07:49
jonmorehouse joined07:49
rchavik joined07:49
jas4711 left07:50
j416 jitendravyas: git pull --rebase gerrit master ; Bundle install07:50
jitendravyas I want to do it using hook07:50
jontmorehouse left07:50
kopparam joined07:50
j416 not sure you want to but07:51
mennea joined07:51
j416 !deploy was it07:51
gitinfo Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html07:51
j416 I would use a wrapper script, not a git hook07:51
beautifulmind left07:51
j416 jitendravyas: because it sounds like a deploy thing -- is it?07:52
osse jitendravyas: echo 'Bundle install' > .git/hooks/post-rewrite; chmod +x .git/hooks/post-rewrite07:52
jitendravyas no want to run just on my local07:52
j416 ok07:53
then what osse said should do it but I'd avoid it07:53
feels like it'd slow things down..07:53
hebz0rl joined07:54
gitinfo set mode: +v07:54
prettyd hi there07:54
gitinfo prettyd: 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.07:54
prettyd hi there07:54
j416 you already said that07:54
govg left07:55
prettyd hi07:55
j416 off to work afk o/07:55
prettyd left07:55
robbyoconnor joined07:58
prettyd joined07:58
gitinfo set mode: +v07:58
prettyd hi there07:58
Sonderblade joined07:58
Sonderblade left07:59
Sonderblade joined07:59
arup_r left07:59
prettyd im trying to figure out how to setup git-daemon on debian, my git been installed and working for a week now, wanted to automatize some things, but cant seem to find git-daemon ? isn't it supposed to come with the package?08:00
arup_r joined08:01
arup_r left08:01
P4_Denis joined08:02
chessguy joined08:02
CheckDavid joined08:03
mikecmpbll joined08:04
jnavila_ left08:04
jottr joined08:05
chessguy left08:06
ki0 joined08:07
Suchit joined08:07
jceb joined08:08
_ikke_ You mean the binary?08:08
Drool left08:08
Suchit left08:08
nour joined08:09
prettyd yup08:09
TititaTitutu joined08:09
Suchit joined08:09
prettyd apt-get did not get anything looking like a daemon to me.08:09
though it was outside but ? where08:09
Gonzo89 joined08:10
jitendravyas left08:11
osse maybe it's in a seperate package08:11
maxb It's in the 'git' package08:12
Try 'git daemon --help'08:13
anaran joined08:13
jenni_naiaretti joined08:13
zumba_ad_ left08:14
prettyd hum yes that work. damn ther emust be something i dont do right so :)08:14
La0 joined08:14
osse prettyd: it is probably located in the directory printed by 'git -exec-path'08:15
'git --exec-path'08:15
La0 left08:15
prettyd ok trying to figure out :) brb08:16
La0 joined08:17
La0 left08:17
La0 joined08:17
La0 left08:17
h0bbit joined08:18
BuenGenio left08:19
mennea left08:20
Motoko left08:21
mennea joined08:21
multi_io left08:22
maslowbeer left08:22
jenni_naiaretti left08:22
jceb left08:23
jnavila_ joined08:24
shruggar joined08:24
Macaveli joined08:25
hexagoxel joined08:26
shruggar left08:27
thevishy_home joined08:27
thevishy joined08:27
jenni_naiaretti joined08:28
Skapadapaduu joined08:29
Gabri left08:30
BuenGenio joined08:32
mongag joined08:32
tomseek joined08:33
avvs left08:34
tanath left08:34
Quevin joined08:35
eletuchy joined08:35
johnny2600 joined08:36
Gizburdt joined08:36
thibaultcha left08:37
petersr left08:38
LeMike left08:39
Quevin left08:39
intellix left08:40
Macaveli left08:40
LeMike joined08:40
wakd left08:44
amcsi_work joined08:44
darkbasic left08:44
Tuna-Fish left08:44
darkbasic joined08:45
oskarkv joined08:45
Suchit left08:45
Suchit joined08:45
robarelli joined08:46
tanath joined08:46
wakd joined08:46
liamkeily joined08:46
avvs joined08:46
wakd left08:47
emrox joined08:47
wakd joined08:48
joki left08:48
chovy joined08:48
chovy `git config --local user.name "chovy"` doesn't work for me.08:48
jatt joined08:49
chovy ok, nm08:49
it works08:49
you can only do one setting at a time.08:49
jatt left08:49
jatt joined08:49
chovy but this is weird, i was able to commit to my repo as another user.08:49
mongag left08:49
chovy how is that possible?08:49
mennea left08:50
piccata left08:50
mennea joined08:51
seanmerron joined08:51
robarelli left08:51
osse chovy: git doesn't care. you can commit under any name you like. don't confuse git's "user names" with actual usernames/accounts on a system08:51
Dudi joined08:51
piccata joined08:52
DanMAbraham left08:52
osse chovy: user.name is simply your name, the human that is using git.08:52
chovy oh i see08:53
bremner set user.name to "Edward Snowden" and you're good to go.08:53
chovy https://github.com/chovy/humanparser/commit/1a3b6255a063d2cb8b12372de84cf5f48579c4c908:53
this is a little weird though08:53
it was commited by 'chovy' but everything looks like it was committed by 'anthonyettinger'08:53
earthdog joined08:54
joki joined08:54
chovy is there anyway to tell who really committed?08:54
tobiasvl chovy: are you anthonyettinger?08:55
chovy yes. i'm both users08:55
Tuna-Fish joined08:55
chovy i had ~/.gitconfig set with user.name and user.email to my corporate account08:55
tobiasvl github associates commits to github accounts by using the e-mail address that it was commited with08:56
bremner chovy: you can use "git log --pretty=fuller" on the command line08:56
tobiasvl so the reason those commits are associated to anthonyettinger instead of chovy is that you commited them with one of anthonyettinger's e-mail addresses08:56
Mso150_u left08:56
osse chovy: if a commit author also has a github user then the github user stuff is shown instead of the "real" data08:57
FYI, the user.name setting is usally set to your full name08:57
chovy so i can just figure out who i want to pretend to be and make it look like they are commiting to my project??08:57
osse yep08:58
chovy awesome :)08:58
BuenGenio left08:58
chovy TJ is back on js guys!08:58
sitaram left08:59
evildmp joined09:00
zarubin left09:01
Nijikokun left09:01
sitaram joined09:01
endiruna left09:01
tanath left09:03
tanath joined09:04
chessguy joined09:04
shuaib joined09:04
BuenGenio joined09:06
Nijikokun joined09:06
Vivekananda_y510 left09:06
DrSkyLizard left09:07
joo-_ joined09:07
a_l_e joined09:08
archdori left09:08
chessguy left09:08
GT4066 left09:10
johnny2600 left09:10
h0bbit left09:12
johnny2600 joined09:13
PinkSpecs joined09:13
dharrigan left09:14
dharrigan joined09:15
BuenGenio left09:15
iiiinzg left09:17
Nijikokun left09:17
FabTG_ left09:17
gitinfo set mode: +v09:17
tomseek nice web based git GUI : https://github.com/alberthier/git-webui09:17
martinklepsch joined09:18
Nijikokun joined09:18
Nijikokun left09:18
johnny2600 left09:18
FabTG_ joined09:19
Nijikokun joined09:19
mnavratil joined09:19
vtunka joined09:19
PinkSpecs left09:20
bremner sorry, you lost me at wget | bash09:20
TititaTitutu left09:20
mennea left09:20
bremner even before shellshock ;). wget | some_other_shell is not better.09:21
mennea joined09:21
TititaTitutu joined09:21
PinkSpecs joined09:23
earthdog left09:24
canton7 I don't like what that install script does, either :P09:25
majoh "Copyright 2015" it's from the future!09:26
canton7 :O09:26
UmbraMalison left09:26
chovy heh09:26
i just jumped on someone today for installing a process on my machine w/o telling me.09:26
boots up and starts this nsa process.09:27
FreezingCold joined09:27
UmbraMalison joined09:27
hebz0rl left09:28
hebz0rl joined09:29
Dudi left09:29
Marcus___ joined09:30
harish joined09:32
pasky so what's the difference between wget | bash and downloading the software, compiling it if applicable and running it?09:32
either way you need to trust the author09:33
hexagoxel left09:33
Marcus left09:33
PinkSpecs_ joined09:33
palcu joined09:33
PinkSpecs left09:34
PinkSpecs_PinkSpecs09:34
chovy you can't see the code09:34
ockham joined09:34
chovy especially with shadowbox bug09:35
jitendravyas joined09:35
Gabri joined09:35
stamina joined09:36
mueslo joined09:38
ki0 left09:38
ki0 joined09:38
jonmorehouse left09:40
robustusrobustus|Off09:41
ngw joined09:43
martinkl_ joined09:43
_ikke_ shadowbox bug?09:44
moritz also, with a pipe, wget might lose the connection09:44
and bash executes an incomplete script09:44
like rm -rf /home/ instead of rm -rf /home/somehting/much/more/specific09:44
chovy oh man, that would suck09:45
so it pipes it before it receives a complete response?09:45
is it like a stream?09:45
moritz yes09:45
lindenle joined09:45
amcsi_work_ joined09:45
chovy is it just wget? or anything | anything09:46
bremner it's a feature.09:46
martinklepsch left09:46
amcsi_work__ joined09:47
_ikke_ There is a buffer, but this buffer is limited in size. But I guess if the process dies, the buffer still gets sent to the proces09:47
Advocation joined09:47
_ikke_ other process*09:47
bremner heh. nice typo.09:47
robarelli joined09:48
uffiole joined09:48
teran left09:49
amcsi_work left09:50
nettoweb joined09:50
booboy left09:50
lindenle left09:50
mennea left09:50
amcsi_work_ left09:51
silverfix joined09:51
mennea joined09:51
silverfix hello guys09:51
but why git pull doesn't delete a file from my filesystem if it's deleted from repo ?09:51
canton7 !repro09:51
gitinfo 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 raise the odds of getting your problem fixed from about 30% to about 90%.09:51
hexagoxel joined09:52
samtuke joined09:52
cbr_ left09:52
robarelli left09:52
ki0 left09:52
cbr_ joined09:53
Gizburdt left09:53
Gizburdt joined09:53
Gizburdt left09:54
amcsi_work__ left09:54
rchavik left09:54
ki0 joined09:56
harish left09:56
Malsasa left09:57
FilipNortic left09:58
moritzschaefer joined09:58
Blaguvest joined10:00
simesy left10:00
beautifulmind joined10:01
liamkeily left10:01
robustus|Offrobustus10:03
martinklepsch joined10:03
endiruna joined10:03
endiruna left10:03
brewmaster left10:03
endiruna joined10:04
Gizburdt joined10:06
interrobangd joined10:06
Malsasa joined10:06
martinkl_ left10:07
Peuc left10:07
daito left10:08
israelpattison left10:08
Peuc joined10:09
israelpattison joined10:09
daito joined10:09
bug_sniper left10:09
rchavik joined10:10
kopparam left10:10
hebz0rl left10:11
hebz0rl joined10:12
Gizburdt left10:13
daito left10:13
ItSANgo left10:18
kopparam joined10:18
jck joined10:18
Advocation left10:19
kopparam left10:20
mennea left10:20
tokik left10:21
kopparam joined10:21
freimatz left10:21
mennea joined10:21
jhass|offjhass10:22
liamkeily joined10:22
listochkin joined10:22
nour left10:23
TititaTitutu left10:23
g4r37h joined10:23
samtuke left10:23
nour joined10:24
Malsasa left10:24
Dudi joined10:24
mennea left10:24
lukeholder left10:25
sdousley joined10:25
gitinfo set mode: +v10:26
sdousley Hey all, would there be any expected issues with upgrading a single client to git 1.8 that will only do a pull if there's other clients that will be pushing git 1.7 versions?10:26
Malsasa joined10:27
paul424 joined10:27
Wiz_KeeD joined10:27
Guest21790 left10:27
canton7 git's extremely good at compatibility in terms of the network format, and repo forms10:27
olspookishmagus joined10:27
canton7 so no problem at all with 1.7 and 1.8 interacting10:28
shuaib left10:28
sdousley canton7: cool, I've just checked anyway, and our local git client is actually 1.8.3 anyway, rather than 1.7.x10:28
olspookishmagusGuest6467310:28
Guest64673 left10:28
canton7 s/repo forms/repo formats10:28
Xiti` left10:28
uffiole left10:28
k_sze[work] left10:28
TititaTitutu joined10:29
olspookishmagus joined10:29
EminenceHC joined10:30
sdousley left10:31
TomyWork joined10:31
Xiti joined10:32
BuenGenio joined10:33
Advocation joined10:33
brewmaster joined10:33
Hello71 left10:35
EminenceHC left10:35
Quevin joined10:36
rchavik left10:36
Marcus joined10:36
samtuke joined10:37
Nijikokun left10:37
Hello71 joined10:37
cvanball left10:37
TomyWork can "git cherry-pick --strategy=ours" be used for grafting?10:37
Marcus___ left10:37
olspookishmagus please, pardon my part-join flood10:37
Malsasa_ joined10:37
olspookishmagus left10:37
hauron left10:38
silverfix left10:38
Nijikokun joined10:38
Malsasa left10:38
TomyWork basically i have a bunch of commits on a branch and i want to keep the trees but change the parents10:38
trees and messages*10:39
CussBot left10:39
CussBot joined10:40
Quevin left10:40
rchavik joined10:40
g4r37h left10:40
prettyd left10:40
aarcane left10:40
carandraug joined10:41
Macaveli joined10:42
FilipNortic joined10:43
Warrior-kk left10:43
cntrl joined10:44
cbr_ left10:46
Silex joined10:46
endiruna left10:46
Gizburdt joined10:46
alorence left10:46
cbr_ joined10:47
alorence joined10:47
robarelli joined10:48
jds joined10:48
endiruna joined10:49
mennea joined10:51
mennea left10:51
awkwardusername left10:52
mennea joined10:52
awkwardusername joined10:52
Malsasa_Malsasa10:53
robarelli left10:53
jdmf left10:54
scarcry left10:54
scarcry joined10:54
PinkSpecs left10:54
robustusrobustus|Off10:55
samtuke left10:56
samtuke joined10:56
kyb3r_ left10:57
jottr_ joined10:58
aidalgol left10:58
Suchit left10:59
Suchit joined10:59
teran joined11:00
jottr left11:01
samtuke left11:02
chessguy joined11:02
irqq joined11:03
g4r37h joined11:04
amikiri joined11:06
Advocation left11:07
kotk joined11:08
Mitchbones joined11:08
chessguy left11:09
chessguy joined11:09
Advocation joined11:13
mieko joined11:13
Advocation left11:15
GarethAdams left11:15
osse TomyWork: I think it might be easier to use the actual grafting mechanism11:16
TomyWork osse it's more to type though :)11:17
and it appears to work nicely for my single-file repo11:17
govg joined11:17
TomyWork git cherry-pick --strategy=recursive -Xours11:17
err theirs11:17
osse that won't replicate the behaviour11:18
TheMadMechanic left11:18
mlnppy left11:21
harish joined11:25
afhkga joined11:25
Gamecubic joined11:26
looper joined11:27
Behi_ joined11:28
Behi left11:29
Guest73625 left11:29
fission6 joined11:29
autochthon joined11:29
Advocation joined11:29
i_ron joined11:31
GarethAdams joined11:32
mennea left11:32
mennea joined11:33
samtuke joined11:33
ItSANgo joined11:33
EminenceHC joined11:34
TititaTitutu left11:34
stormwild joined11:35
Kartagis left11:36
intellix joined11:38
TomyWork i'm looking for a permanent graft11:38
Kartagis joined11:38
lacrymology left11:39
paulweb515 left11:39
EminenceHC left11:39
mennea left11:39
_ikke_ it can be made permanent11:40
with filter-branch11:40
g4r37h left11:40
bAnt_ joined11:40
PinkSpecs joined11:41
zapb_ left11:42
esc anyone have details on how the bash bug may affect git and related software11:42
e.g. cgit or gitolite?11:42
TomyWork _ikke_ yeah i was lookign for a solution with less typing, for quick and dirty grafting :)11:42
canton7 esc, it comes down to how ssh is affected11:43
xolubi joined11:43
osse esc: server-side git doesn't run any scripts afaik. the last one (git-repack) was converted to C recently. Hooks are another story :P11:43
esc okay, I was wondering if it may affect gitolite11:44
raboof left11:45
esc but I couldn't find any ForceCommand directive in the sshd config11:45
osse TERM='() { :;}; echo vulnerable' ssh somewhere11:46
joo-_ left11:46
lindenle joined11:47
sitaram esc: check on the gitolite mailing list archives at groups.google.com11:47
it *does* affect gitolite and such software11:47
osse gitolite can be vulnerable if it uses `foo` or system("foo")11:48
esc osse: i checked with ssh, but got no 'vulnerable'11:48
sitaram osse: any ssh based "restricted" environment is vulnerable if the user's shell is bash. Gitolite doesn't even gain control before the shit happens11:48
tincan joined11:48
bukagija joined11:49
osse sitaram: hmm, I was hoping SSH would execute gitolite directly without a shell between them11:49
txdv basically all the honey pots env are vunerable to exploits11:49
irqq left11:49
txdv which is funny11:49
DARSCODE joined11:49
txdv because they get fucked for trying to fuck over hackers11:49
esc the 'git' users shell on a system that I am looking at is /bin/bash11:50
irqq joined11:50
robarelli joined11:50
encod3 left11:51
kopparam left11:51
ItSANgo left11:51
sitaram osse, esc: my current solution is http://paste.fedoraproject.org/136710/1173231411:52
kopparam joined11:52
Marcus___ joined11:52
sitaram osse: it uses $SHELL -c11:52
lindenle left11:52
cntrl left11:52
BuenGenio left11:52
Marcu____ joined11:53
zburns joined11:53
Advocation left11:53
sitaram esc, osse: note that solution mitigates both the problems (the one that bash already has a fix for and the one they're still working on)11:53
lacrymology joined11:53
Marcus left11:53
TititaTitutu joined11:54
robarelli left11:55
esc oss: when I try the thing you suggest above, I only get: PTY allocation request failed on channel 011:55
afhammad joined11:56
Marcus___ left11:56
kopparam left11:57
esc i get the same thing when I try to ssh to github.com11:57
Mitchbones left11:58
lsiv568 joined11:58
fstd left12:00
fstd joined12:00
joo-_ joined12:01
Gizburdt_ joined12:03
nettoweb left12:03
TititaTitutu left12:03
fission6 left12:04
listochk_ joined12:04
Gizburdt left12:04
darkbasic_ joined12:04
Dudi left12:05
darkbasic left12:05
plitzenberger joined12:05
bukagija left12:05
lukeholder joined12:05
lukeholder left12:05
toothrot joined12:05
kriks left12:05
philipd joined12:06
philipd left12:06
lukeholder joined12:06
lukeholder left12:06
kopparam joined12:06
lukeholder joined12:07
m0ltar joined12:07
lukeholder left12:07
Gabri left12:07
lukeholder joined12:08
esc i couldn't get it to work over ssh, so I made dash the login shell of the git user12:08
jatt left12:08
esc as a precautionary measure12:08
listochkin left12:08
esc back later12:08
lukeholder left12:08
Advocation joined12:08
kopparam_ joined12:09
lukeholder joined12:09
encod3 joined12:09
kriks joined12:10
kopparam left12:11
robustus|Offrobustus12:12
autochthon left12:12
Gabri joined12:13
nettoweb joined12:13
Suchit left12:14
kopparam_ left12:14
Suchit joined12:15
zoso left12:16
infernix joined12:16
samtuke left12:18
sohail joined12:19
lacrymology left12:20
cannonball joined12:20
amikiri left12:20
JDHawke joined12:21
King_Hual left12:21
tristanp joined12:21
King_Hual joined12:22
jottr_jottr12:22
atamanroman joined12:23
Skapadapaduu left12:24
plitzenberger left12:25
PsciCOdeliXHAt joined12:25
shizzle joined12:25
t4nk598 left12:26
Xiti left12:26
michelangelo joined12:27
seanmerron left12:28
listochk_ left12:29
listochkin joined12:30
donmichelangelo left12:30
PinkSpecs left12:32
mechanicalduck left12:32
gccostab_gccostabr12:33
paulweb515 joined12:33
ItSANgo joined12:34
jitendravyas left12:34
listochkin left12:34
samtuke joined12:34
nettoweb left12:35
Talisman joined12:35
samtuke left12:36
mechanicalduck joined12:36
gitinfo set mode: +v12:36
samtuke joined12:37
vgarg left12:37
samtuke left12:38
livingstn joined12:38
kopparam joined12:38
samtuke joined12:39
EminenceHC joined12:39
paulweb515 left12:40
Kartagis left12:40
LeMike left12:40
PinkSpecs joined12:40
xolubi left12:40
Kartagis joined12:40
daedeloth joined12:41
fission6 joined12:42
cagedwisdom left12:42
kopparam left12:43
teran left12:43
EminenceHC left12:44
fission6 left12:44
Gizburdt joined12:44
jenni_naiaretti left12:46
Droolio joined12:46
nimdAsyS joined12:46
Gizburdt_ left12:47
knobo I did "git add file", then realized I should not have done that. How do I un add it. I want to have it in a separate commit12:48
mlechner left12:48
knobo I though "git rm --cached file" would do it12:48
PinkSpecs left12:49
knobo but now "git status" says "changes to be committed: \n deleted: file"12:49
That is not so good...12:49
DolphinDream left12:50
madduck left12:50
knobo reset fixed it...12:51
robarelli joined12:51
muhaha03__ left12:51
_ikke_ yup12:51
git status would show you what to do12:51
BuenGenio joined12:52
dangerousdave joined12:52
jenni_naiaretti joined12:52
paulweb515 joined12:53
Advocation left12:53
a_le joined12:54
knobo Nice to know what _reset_ actually does.12:54
teran joined12:55
mixandgo joined12:55
_ikke_ git reset (without any parameters) will reset the index to the state of HEAD12:55
teran_ joined12:55
_ikke_ basically unstaging everything12:55
dangerousdave left12:56
martinklepsch left12:56
robarelli left12:56
dangerousdave joined12:56
hide joined12:57
hide left12:57
danemacmillan joined12:57
knobo And HEAD, is that the state of my current non-committed changes?12:57
aha.. no..12:57
the index to HEAD... not my files.12:57
ome left12:57
nioncode joined12:57
jimmyy left12:58
toothrot left12:58
knobo one day I'll be as fluent in git as I once was in rcs ;)12:58
hide joined12:58
hide left12:58
_ikke_ !reset12:58
gitinfo A good resource explaining git-reset is http://git-scm.com/2011/07/11/reset.html12:58
_ikke_ read that12:58
martinklepsch joined12:59
dangerousdave left12:59
hide joined12:59
hide left12:59
teran left12:59
knobo three roles :) I like that kind of clear explenations :)12:59
hide joined12:59
hide left12:59
roflik joined12:59
_ikke_ That's the post that made me actually understand it all13:00
hide joined13:00
hide left13:00
zacg joined13:00
rob_w left13:00
Sebtoast joined13:01
fission6 joined13:01
styx_ joined13:01
jenni_naiaretti left13:01
darkbasic_ left13:02
Peuc left13:02
hide joined13:02
hide left13:02
knobo Thaks for the help13:02
darkbasic joined13:02
hide joined13:03
hide left13:03
martinklepsch left13:03
hide joined13:04
_ikke_ You'r welcome13:04
Peuc joined13:04
albel727 hey. what's the best way to remember current tree state, checkout something else, and then return back AUTOMATICALLY? i.e. some combination of git stash; /* remember current branch or SHA for detached head */; ... checkout something else ... ; git checkout $remembered_branch_or_sha; git stash pop13:05
I can't seem to find an elegant solution for /* remember current branch or SHA for detached head */13:05
_ikke_ There is nothing in git really13:05
Imdsm joined13:06
hexagoxel left13:06
TomyWork left13:07
_ikke_ albel727: You could try to use the reflog13:08
afhammad left13:08
afhammad joined13:08
albel727 but git checkout HEAD@{1} would leave me in a detached head state, even if I were on a branch previously.13:09
martinklepsch joined13:10
ErKa joined13:10
jerius left13:10
kirin` joined13:11
Imdsm left13:11
albel727 guess I can just remember old_head=$(cat .git/HEAD), and then cat $old_head > .git/HEAD13:11
but that's ugly13:11
tanath left13:12
beautifulmind left13:12
moparsthbest joined13:12
brandonw left13:12
tanath joined13:12
madduck joined13:12
jenni_naiaretti joined13:12
Dougie187 joined13:13
brandonw joined13:13
afhammad left13:13
jenni_naiaretti left13:13
listochkin joined13:14
lsiv568 left13:14
moparisthebest left13:15
tomseek left13:15
jenni_naiaretti joined13:15
listochkin left13:16
afhammad joined13:16
glosoli left13:17
it0a joined13:17
nettoweb joined13:17
nettoweb left13:17
nettoweb joined13:18
Gizburdt left13:19
Peuc left13:20
mnavratil left13:21
monbro joined13:22
nikita left13:22
Peuc joined13:22
listochkin joined13:23
philipd joined13:23
philipd left13:23
Macaveli left13:23
wdkevin joined13:24
mennea joined13:24
nikita joined13:24
wdkevin I'm using github and I have merge conflicts when trying to merge a branch into Master. Are there any Windows dekstop tools that will let me handle these conflicts (its very large branch) and do the merge on GitHub for me?13:24
osse albel727: to get back, you can git checkout branchname13:24
or maybe I'm misunderstanding something13:25
TititaTitutu joined13:25
samtuke left13:25
Dougie187 wdkevin: if there are merge conflicts, your best bet is to handle the merge on a command line by hand.13:26
there are mergetools that can help13:26
like p4merge (I think that's the name)13:26
wdkevin hmm13:26
Dougie187 But they won't do the merge on github for you13:26
wdkevin i suppose. i was hoping for a gui to make it a little easier13:26
yea13:26
Dougie187 because there are conflicts, and github doesn't know how to do it.13:26
wdkevin i have to mwerge on my mahcine and then push13:26
Dougie187 yeah13:26
wdkevin i was just hoping there was an easier way13:27
stamina left13:27
osse albel727: old_head=$(git rev-parse --symbolic-full-name HEAD); ...; git checkout $old_head13:27
wdkevin my branch is massive13:27
Dougie187 http://www.perforce.com/product/components/perforce-visual-merge-and-diff-tools13:27
wdkevin thank you Dougie18713:27
mizu_no_oto joined13:27
Dougie187 There are other ones.13:27
but that's probably one of the most gui friendly merge tools around13:27
msmith_ joined13:27
dusted joined13:28
dmarkham joined13:28
jerius joined13:29
hexagoxel joined13:29
lsiv568 joined13:29
albel727 osse: not only would leave us in detached head state (as a result of checkouting by full-ref and not branch name), but that would break if you originally were on detached head, b/c git rev-parse --symbolic-full-name returns on detached head just... "HEAD"13:29
BSaboia joined13:29
albel727 *not only that13:29
zumba_addict joined13:29
jatt joined13:30
jatt left13:30
jatt joined13:30
albel727 now I'm working on solution based around git symbolic-ref --short HEAD and falling back to git rev-parse HEAD if the former doesn't succeed13:30
liamkeily left13:30
albel727 so, my solution is old_head=$(git symbolic-ref --quiet --short HEAD || git rev-parse HEAD)13:31
irqq left13:32
wdkevin Dougie187, these GUI tools need to be ran on the same server as the repo though, right?13:32
osse albel727: old_head=$(git rev-parse --symbolic-full-name HEAD); ...; git checkout ${old_head##*/}13:32
=)13:32
jatt left13:32
Dougie187 wdkevin: no, they have to be run locally.13:32
wdkevin so if i work on a windows desktop but have my own VM for web server, it needs to run on that VM?13:33
Dougie187 Regardless, you have to do the merge locally and push.13:33
Advocation joined13:33
Gizburdt joined13:33
dccc joined13:33
mnavratil joined13:34
StarManta joined13:34
dangerousdave joined13:34
Xiti joined13:34
albel727 osse: "git rev-parse --symbolic-full-name HEAD" still fails if head is detached.13:34
zumba_ad_ joined13:34
albel727 it returns just "HEAD" instead of a SHA13:34
TititaTitutu left13:35
listochkin left13:35
albel727 and naturally, once you checked out some other commit git checkout HEAD ain't gonna return you back to where you were.13:35
zumba_addict left13:35
osse albel727: well, if you're *already* detached, then you can't attach without an explicit branch name13:35
my latest will leave you where you began.13:36
albel727 I don't want to attach if I were detached. I just want to return the detached head to where it was.13:36
osse mine does that13:36
listochkin joined13:37
albel727 nope it doesn't. /* on detached head with $sha1 */ ; git checkout $sha2 ; ... ; git checkout HEAD ; /* still on detached head with $sha2 */13:37
jenni_naiaretti left13:37
osse ho i see what you mean now13:38
tesaf joined13:39
dangerousdave left13:39
Peuc2 joined13:39
dangerousdave joined13:40
osse albel727: old_head=$(git rev-parse --symbolic-full-name HEAD); if [[ $old_head = HEAD ]]; then old_head=$(git rev-parse HEAD); fi13:40
cbr_ left13:40
cbr_ joined13:41
bAnt_ left13:41
ockham left13:41
albel727 mine is shorter, and yours still needs checkout ${old_head##*/} :P13:41
Pyrogerg left13:41
Segfault_ left13:41
osse ahh, didn't notice that one13:41
yeah yours is better13:41
albel727 anyway, thanks for trying to help13:42
Peuc left13:42
osse i always forget symbolif-ref exists :(13:43
albel727: waaait, a minute. I think you can do simply 'git checkout -' and it will do The Right Thing13:44
Peuc2 left13:44
osse but not 100% sure13:44
HanClinto_ joined13:44
wdkevin Dougie187, This Perforce is asking for a server and it has "perforce:1666" entered. does that mean i need to install something on the linux server for this perforce client to connect to?13:45
jonr22 joined13:45
Peuc joined13:45
Gizburdt left13:45
Dougie187 wdkevin: I've never used the perforce merge tool. I just know people who want a gui like it. I live in the cli :P...13:45
zumba_ad_ left13:46
wdkevin haha, ok13:46
im not opposed to the CLI, i just thought a GUI would be easier in this case13:46
everything else i do is CLI13:46
Gizburdt joined13:46
dangerousdave left13:46
iamjarvo joined13:46
iamjarvo left13:46
albel727 interesting. it seems to work, but doesn't seem to be documented.13:46
ockham joined13:47
osse albel727: it's in man git-checkout udner <branch>13:47
gitinfo albel727: the git-checkout manpage is available at http://jk.gs/git-checkout.html13:47
iamjarvo joined13:47
mike_af joined13:47
samtuke joined13:47
HanClinto left13:47
Gizburdt left13:48
Gizburdt joined13:48
Dougie187 wdkevin: the cli isn't that bad.13:48
albel727 I don't see it. all I see there is >You could omit <branch>, in which case the command degenerates to "check out the current branch",13:48
wdkevin Dougie187, yea i dont mind it normally13:49
lindenle joined13:49
wdkevin ive never fixed a merge conflict though :-X13:49
albel727 but nothing there seems to describe the behaviour like cd -13:49
jenni_naiaretti joined13:49
zumba_addict joined13:50
albel727 and git checkout - seems to behave exactly like cd - for directories. i.e. it flips you between two dirs indefinitely.13:50
jitendravyas joined13:51
Ankhers joined13:51
Dougie187 wdkevin: Have you used svn to fix merge conflicts before?13:51
wdkevin: if so, it's almost the same.13:51
_Vi left13:51
Dougie187 although you can use other tools (like p4merge) to help deal with the conflicts.13:51
wdkevin no i havent13:52
osse albel727: As a special case, the "@{-N}" syntax for the N-th last branch/commit checks out branches (instead of detaching). You mayalso specify - which is synonymous with "@{-1}".13:52
mennea left13:52
liamkeily joined13:53
lindenle left13:53
robarelli joined13:53
mennea joined13:53
marscher joined13:54
martinklepsch left13:55
johtso joined13:56
nettoweb left13:56
kukks joined13:56
kukks left13:56
kukks joined13:56
Malsasa left13:56
zapb_ joined13:56
AaronMT joined13:57
Gizburdt left13:57
albel727 whoa whoa, I completely missed @{-N} syntax. on the surface it looks just like @{N}, but it looks like it can check out symbolic refs too.13:57
samtuke left13:57
albel727 s/check out/refer to/13:58
kukks left13:58
zumba_ad_ joined13:58
robarelli left13:58
Gizburdt joined13:58
MutSbeta joined13:58
mennea left13:58
kukks joined13:59
zerofun joined13:59
zumba_addict left13:59
albel727 learn something new every day13:59
osse++13:59
j416 albel727: what is the underlying problem you're solving?13:59
modcure joined14:00
tristanp left14:00
BuenGenio left14:00
gauke left14:01
paul424 left14:01
kpease joined14:01
wagle left14:01
Ankhers left14:02
tgies left14:02
Gizburdt left14:02
wagle joined14:02
albel727 I want a helper command that would generate for me some stuff from the state of the tree in the past. a one that I can run and then continue working, obviously.14:02
zerofun left14:02
j416 hmm14:02
ki0_ joined14:02
albel727 well, I'm almost there anyway.14:02
ki0 left14:02
j416 alright14:02
you _could_ check that out into a separate worktree (--work-tree), do what you need there, then throw it away, maybe14:03
Neozonz joined14:03
j416 not sure if that helps.14:04
zumba_ad_ left14:04
marscher left14:04
skylite left14:04
eburcat joined14:04
Malsasa joined14:05
jceb joined14:05
m0ltar left14:06
tgies joined14:06
albel727 I'm not sure how would it help. either I'd need to do git checkout to init the new worktree, but then I still have to restore HEAD afterwards. or I'd need to do git read-index git checkout-index dance14:06
noxd left14:06
Neozonz|Disc joined14:06
dvdchr joined14:07
albel727 and I'm not talking about copying overhead.14:07
j416 yeah, just thought I'd throw it out there as an option14:07
PinkSpecs joined14:07
albel727 if outside tree were really a good option, I'd just git clone --local somewhere14:08
j416 there's also git-archive fwiw14:08
ehmatthes joined14:08
m0ltar joined14:09
thiago_ joined14:09
thiago_ left14:09
thiago joined14:09
mdel joined14:10
mennea joined14:10
cure_ joined14:11
Trudko left14:11
cure_Guest4267614:11
albel727 s/git read-index/git read-tree/14:11
zivester joined14:12
nettoweb joined14:12
albel727 now if only git stash just had an option to allow producing an empty stash, instead of "check if there's something to stash, and only then do stash/stash pop" dance that is necessary otherwise.14:12
jdrumheller joined14:13
jitendravyas left14:13
Pyrogerg joined14:13
modcure left14:14
polyzen joined14:14
Ankhers joined14:14
tristanp joined14:15
bezet joined14:15
seschwar left14:16
monbro left14:17
FortySix2 joined14:17
_Vi joined14:19
SumDude joined14:19
hmsimha_ joined14:19
j416 albel727: you _could_ create a commit manually instead of doing stash..14:19
samtuke joined14:19
zumba_addict joined14:20
WormDrink left14:21
Vasastan joined14:21
Gizburdt joined14:22
jonr22 left14:22
albel727 that would require two commits, one for staging area and one for worktree changes. and a dance with git commit while trying to avoid corner cases like committing untracked files etc, with the end result of... emulating git stash just with the empty commit option.14:22
zivester left14:23
mennea left14:23
tang^ joined14:23
albel727 it's easier to check if there's anything to stash with git diff --quiet --exit-code HEAD14:23
mennea joined14:23
xolubi joined14:23
robustusrobustus|Off14:24
Gabri left14:24
diegoviola left14:25
Suchit left14:26
Suchit joined14:27
milkohol joined14:27
EminenceHC joined14:28
pheaver joined14:28
xolubi left14:29
gargola joined14:31
d10n-work joined14:31
Suchit left14:32
d10n-work Is there a nice tool to automatically git fetch or git remote update specified repositories at an interval?14:32
eletuchy left14:32
milkohol left14:33
_ikke_ cron14:33
Macaveli joined14:33
FortySix2 left14:35
jonr22 joined14:36
jonr22 left14:36
lsiv568 left14:36
diegoviola joined14:37
m0ltar left14:37
samtuke left14:37
Quevin joined14:37
nettoweb left14:38
petersr joined14:38
milkohol joined14:38
Sivil joined14:38
starkhalo joined14:38
dreiss joined14:39
glosoli joined14:39
pheaver left14:40
parcs joined14:40
parcs hello14:40
xolubi joined14:40
hmsimha_ left14:41
skelterjohn is there a nice place to get older releases of git? I'm looking at https://www.kernel.org/pub/software/scm/git/ but there is a gap between 0.7 and 1.8.2. i specifically want 1.7.1 :)14:41
kevwil joined14:41
Quevin left14:42
Nizumzen joined14:42
jiggerypokery joined14:42
_ikke_ Do you want source releases?14:42
parcs when i clone a repository and then do a fetch (which updated origin/master), "git show origin/master@{1}" fails with "fatal: Log for 'origin/master' only has 1 entries." why is that?14:42
a_le left14:43
StarManta is there any way to see how much space a repository is taking up on my drive?14:43
_ikke_ StarManta: windows or linux/14:43
?14:43
StarManta os x14:43
using sourcetree14:43
parcs shouldn't the reflog have more than 1 entry? the first entry would correspond to the initial clone, and the 2nd to the subsequent fetch14:43
_ikke_ du -sch should work14:43
atamanroman left14:43
lsiv568 joined14:45
milkohol left14:46
StarManta i guess i should rephrase the question. any way to tell _where_ a repository is on my hard drive?14:47
skelterjohn _ikke_: source release is fine, yes14:47
StarManta it's all the sort of abstracted away and hidden somewhere14:47
acolson left14:47
tang^ StarManta: whereever you checked it out to14:47
skelterjohn _ikke_: does the git git repo have nice takes? i guess i can just go check14:47
StarManta not the working versino14:47
version14:47
i mean the whole repository14:47
Junior` left14:48
tang^ repo is stored with the working directory14:48
kkuno joined14:48
skelterjohn _ikke_: nice takes = nice tags14:48
kkuno hello14:48
Kicer86 joined14:48
kkuno I have often this problem:14:48
joelrobichaud joined14:48
acharlieh joined14:49
kkuno I make a change in the readme in github and I often don't remember to pull locally14:49
then I make a commit locally14:49
dvdchr left14:49
kkuno and I can't push anymore14:49
afhammad left14:49
ToxicFrog kkuno: why is that a problem? Fetch your changes from github, merge, push14:49
kkuno If I try to pull the readme change, I need to merge it14:49
Sonderblade why does git config --list list core.autocrlf twice?14:50
kkuno mmh ok, I don't like much merges14:50
parcs kkuno: you need to rebase your local changes on top of the already pushed changes14:50
upene joined14:50
StarManta er....that doesn't seem to be the case. i don't see any unaccounted-for folders in here and the folder size is not nearly what i would expect if it contained all the past versions of the project14:50
kkuno parcs: so git rebase master origin/master?14:50
tang^ StarManta: using ls -a?14:50
_ikke_ StarManta: Even in compressed form?14:50
tang^ StarManta: .git is a hidden folder by default14:51
parcs kkuno: that will probably be enough14:51
_ikke_ StarManta: Git uses delta compression14:51
Pyrogerg left14:51
parcs kkuno: actually just do "git rebase origin/master"14:51
afhkga left14:51
parcs not really sure what master origin/master does14:51
roelmonnens left14:51
Pyrogerg joined14:51
_ikke_ it refers to the latest changes you fetched for master from the origin repostiory14:51
repository14:51
zyla joined14:52
rchavik left14:52
mennea left14:53
mennea joined14:53
kkuno yeah it did the reverse of what I need14:53
_ikke_ reverse?14:53
kkuno mmmh14:54
StarManta ok, thanks. it was hidden14:54
Advocation left14:54
kkuno now locally I have local change --> update readme14:54
robarelli joined14:54
sdrfnord1 left14:54
kkuno and github won't let me push because I'm violating its timeline14:54
ifdm_ left14:55
_ikke_ lol14:55
kkuno I would need readme --> local change14:55
parcs what does that mean???14:55
please read http://git-scm.com/book/ch3-6.html14:55
ToxicFrog kkuno: git rebase master origin/master rebases origin/master onto master. You wanted the opposite: git checkout master; git rebase origin/master14:55
As parcs said earlier.14:56
robustus|Offrobustus14:56
kkuno yeah14:56
I'm rebasing again to remove the readme commit14:56
a_le joined14:56
kkuno so that I can rebase correctly afterwards14:56
lol14:56
robustusrobustus|Off14:56
WormDrink joined14:56
upene left14:57
kpease left14:57
kpease joined14:57
kkuno no wait14:58
it's just a reset14:58
I'm too tired14:58
jmichaelward joined14:59
emrox left14:59
robarelli left14:59
brandonw left15:00
Gizburdt left15:00
thiago left15:00
LeMike joined15:00
msmith_ left15:00
cuppscakes joined15:01
Macaveli left15:01
ghostlin_ left15:01
kkuno ok, now it seems all ok, but github keeps rejecting my push15:01
don't know why it should be a simple fastforward15:01
kpease left15:01
AnujSharma joined15:02
kpease joined15:02
GGflags left15:02
AnujSharma left15:02
logix812 joined15:02
treehug88 joined15:03
osfe left15:03
ToxicFrog kkuno: check the shas. You may have screwed things up with all the rebasing and resulted in divergent history even if the commit contents are the same.15:03
eletuchy joined15:03
msmith_ joined15:03
zumba_addict left15:03
ToxicFrog kkuno: IMO, your best option here is just to reset master back to origin/master, cherry-pick the commits you wanted, push that, and then rebase properly next time.15:03
listochkin left15:04
ghostlin_ joined15:04
eletuchy left15:05
kkuno yeah solved15:05
Pyrogerg left15:05
kkuno actually I was on no branches15:05
maybe I screwed up things playing with rebase15:05
eletuchy joined15:05
milkohol joined15:05
Silmarilion left15:06
Suchit joined15:06
alorence left15:07
killtheliterate joined15:09
eletuchy left15:10
eburcat left15:11
xSmurf joined15:11
pooh22 left15:11
Dudi joined15:11
eburcat joined15:12
AaronMT left15:12
BuenGenio joined15:12
AaronMT joined15:12
BuenGenio left15:12
bukagija joined15:13
m0ltar joined15:14
Suchit left15:14
Marcu____ left15:14
kukks left15:15
Suchit joined15:15
Marcus joined15:15
LeMike left15:15
fold joined15:15
jnavila_ left15:15
ErKa left15:16
msankhala joined15:16
Marcus_ joined15:16
Frodosagbag joined15:18
lsiv568 left15:19
thedodd joined15:19
Suchit left15:19
jnavila_ joined15:19
ThomasLocke left15:20
gitinfo set mode: +v15:20
Frodosagbag Having trouble excluding files from an archive, I have a .gitattributes file in the root directory of my site (same directory as .git) with the following contents: http://pastebin.com/4Tht0fDp15:20
Then I run sudo git archive --worktree-attributes -o dfegit-qa.zip develop15:20
Marcus left15:21
Frodosagbag I'm committing before the archive, and I've tried without worktree attributes15:21
interrobangd left15:21
msankhala left15:22
lsiv568 joined15:23
mennea left15:23
PinkSpecs left15:23
mennea_ joined15:23
zyla left15:24
punchagan joined15:24
ojacobson joined15:24
cubeport joined15:25
m0viefreak joined15:25
zyla joined15:25
chen__ joined15:26
vtunka left15:26
mizu_no_oto left15:27
kermit left15:27
jiggerypokery left15:28
listochkin joined15:28
gua_ould left15:28
robustus|Offrobustus15:28
lukeholder left15:29
Marcus_ left15:29
jottr left15:30
iiiinzg joined15:31
kermit joined15:31
jonr22 joined15:32
jonr22 left15:32
a_l_e left15:32
nour left15:33
Pyrogerg joined15:34
CheckDavid left15:34
avvs left15:35
chen__ left15:37
cure_ joined15:37
nour joined15:37
cure_Guest5321115:37
cbr_ left15:38
morphix0 joined15:40
smccarthy joined15:40
Guest42676 left15:41
Trindaz joined15:41
atomx joined15:42
jottr joined15:43
logix812 left15:44
n-st joined15:44
lindenle joined15:44
blubberbop joined15:44
LeMike joined15:45
p4trix left15:45
roaet joined15:45
Gonzo89 left15:45
roaet hello git masters!15:45
morphix0 left15:46
Trindaz how do I remove just one commit from about 5 commits ago?15:46
do I have to rebase to do that15:46
roaet What is the relationship between merge commits and the commit that was in the merge?15:46
if I revert the commit do I revert both? Or just the merge?15:46
ToxicFrog Trindaz: depends on what you mean by "remove". See !revert15:47
gitinfo Trindaz: That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?15:47
ToxicFrog If you want to completely excise it from history, yes, rebase -i is the easiest way to do that.15:47
Pyrogerg left15:48
Trindaz THanks ToxicFrog, I want the last option15:48
Pyrogerg_ joined15:48
roaet I believe I need git-revert then15:48
but I don't know how to undo multiple commits then keep some in between15:48
and I'm confused about the difference between a merge commit and a regular commit15:48
kermit left15:49
smw joined15:49
jonalmeida joined15:49
ehmatthes left15:49
cubeport left15:50
stormwild left15:50
roflik i want to see all objectids affected by a certain commit. how should i go about this? git rev-list --objects withholds information about moves.15:51
Malsasa_ joined15:52
kermit joined15:52
mennea_ left15:53
mennea joined15:53
Malsasa left15:53
pheaver joined15:53
nilg left15:53
Nazrhom left15:54
bukagija left15:56
robarelli joined15:56
Quevin joined16:00
a_le left16:00
lsiv568 left16:01
Mso150_u joined16:01
maslowbeer joined16:01
mikecmpbll left16:02
robarelli left16:02
aswen left16:02
zumba_addict joined16:02
thevishy left16:03
listochkin left16:03
thevishy_home left16:03
ghostlin_ left16:04
diegoviola left16:04
nettoweb joined16:04
diegoviola joined16:05
DARSCODE left16:06
Malsasa_ left16:07
robustusrobustus|Off16:08
Trindaz left16:08
rdbell left16:08
BuenGenio joined16:09
rdbell joined16:09
Quevin left16:09
smw left16:10
Quevin joined16:10
desposo joined16:10
smw joined16:11
akushner__ joined16:11
burhan joined16:11
mnavratil left16:12
burhan left16:12
burhan joined16:12
burhan I have a repository cloned and then from another computer I cleaned up the branches on the remote - how can I synchronize my computer so that it only has those branches that are in the remote (origin)?16:12
mnavratil joined16:12
canton7 burhan, 'git fetch --prune' will delete remote-tracking branches which are no longer on the remote16:13
burhan doing git pull just pulls changes from the branches that exist, but it doesn't remove the references to the non-existing branches.16:13
canton7 git won't automatically delete local branches16:13
imachuchu joined16:13
canton7 ...but you shouldn't have tons of unused local branches lying around anyway16:13
rdbell left16:13
elasticdog left16:14
burhan no I don't, I was developing on two laptops and then one machine was repurposed now its back so I am trying to bring it up to date.16:14
ki0_ left16:14
canton7 like I say, try 'git fetch --prune'16:14
kiran left16:14
burhan I think that does it - need to specify all my remotes as it does it for origin only by default, thanks.16:15
elasticdog joined16:15
mikehaas763 joined16:15
burhan I guess its upto me to clean the local branches.16:15
canton7 yeah, though you can script something up pretty quickly16:15
__TheDodd__ joined16:16
LeMike left16:16
a_le joined16:16
burhan thanks canton716:16
GluonQuark left16:16
mikehaas763 at http://git-scm.com/about/staging-area it says that "Now you can just stage the change you need for the current commit and stage the other change for the next commit. " This page implies to me that you can edit a file and then stage just some of the edits. Is what it's actually saying is: (to come in next message)16:16
thedodd left16:17
mikehaas763 That you can edit a file, stage it.. then edit it again and those changes are not staged?16:17
Nizumzen left16:17
ToxicFrog mikehaas763: both, actually.16:18
jenni_naiaretti left16:18
ToxicFrog mikehaas763: 'git add' adds the current state of the file, so you can make some edits, stage them, and then make more and those changes are not staged; if you did a commit at that point, only the first batch of changes would be committed.16:18
mikehaas763: you can also stage only some of the changes to a file using 'git add -p' or using graphical tools like 'git gui' or 'git cola'.16:19
(at a resolution of individual diff hunks or even individual lines)16:19
Cheaterman1 joined16:19
fritti_tailchase joined16:19
mikehaas763 ToxicFrog, ahhh.. didn't know about the -p flag16:19
jargon left16:20
PinkSpecs joined16:20
HanClinto__ joined16:20
fritti_tailchasetang^216:20
__TheDodd__ left16:20
punchagan left16:21
ErKa joined16:22
mikehaas763 All very interesting.. I don't know how I ended up on that page but when I read "This allows you to stage only portions of a modified file. Gone are the days of making two logically unrelated modifications to a file before you realized that you forgot to commit one of them" I was like what is this sorcery... not that I'm surprised I've just never attempted to make a partial file commit16:22
rdbell joined16:22
ToxicFrog mikehaas763: I use it all the time, because I have a bad habit of making several commits worth of changes and then needing to disentangle them16:22
sdrfnord1 joined16:22
mennea left16:23
ToxicFrog I find 'add -p' kind of awkward but I use the graphical tools constantly.16:23
mennea joined16:23
hebz0rl_ joined16:24
imachuchu left16:24
ciampix left16:24
HanClinto_ left16:24
iiiinzg left16:24
mikehaas763 ToxicFrog, I'm sure it's not so much of an actual problem but that would kind of worry me that I would be checking in something that unknowingly broke the build, or something similar16:25
*When going through all the modified files and checking in only certain parts.16:25
ToxicFrog mikehaas763: this is where a benefit of distributed version control comes in -- after making the commits but before pushing them, you can test each commit locally and fix any that broke things.16:25
pcypher joined16:26
Nizumzen joined16:26
mikehaas763 ToxicFrog, I always thought that modifying a commit (even before pushing) was quite dangerous16:27
dreiss left16:27
uberGuest7187916:27
Guest71879 left16:27
a_le left16:27
uber_ joined16:27
uber_ left16:27
jnavila_ left16:27
a_le joined16:28
ToxicFrog mikehaas763: no, not at all. Modifying it after pushing is a problem because other people may have seen it. But modifying local history is quite common.16:28
uber joined16:28
uber left16:28
ToxicFrog mikehaas763: Lots of people make many intermediate commits and then squash them down before pushing, or constantly rebase against upstream to maintain a linear history, or use --amend with wild abandon.16:29
uber joined16:29
uber left16:29
dusted left16:29
uber joined16:29
uber left16:29
dsdeiz joined16:30
Advocation joined16:30
uber joined16:30
swahili joined16:30
swahili hi16:30
gitinfo swahili: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.16:30
swahili Q: If I checkout `foobar`, from there, can I go up a commit or keep going up from there ? the same way we do with ^^ and stuff like that from HEAD (I never do it anyway, not sure if correct). Any tips ? thanks !16:31
maestrojed joined16:31
mikehaas763 I've only used amend. I've worked with team members that rebased and squashed but I never partook. I thought that even local commits though, if you modify your 2nd to last commit, it can mess things up because you commited after it.16:32
chovy left16:32
tobiasvl swahili: foobar^ works fine16:32
swahili: foobar^^^ is the same as foobar~3 btw16:32
ToxicFrog mikehaas763: no, if it can safely reconcile the later commits against the earlier ones it will, and if it can't it'll pause and ask you to either resolve conflicts or abort16:32
swahili tobiasvl: oh cool : D awesome! That is to go up right ?16:32
tobiasvl swahili: yes16:33
DARSCODE joined16:33
swahili tobiasvl: wait maybe I explained myself wrongly. what I mean is I go in history -2 and then from that ocmmit I want to go +2 ?16:33
tobiasvl ahh... no, you can only go one way unfortunately. a commit only knows its parent16:34
swahili tobiasvl: oh makes sense : )16:34
thanks!16:34
robbyoconnor left16:34
swahili Thanks a lot for your attention anyway : )16:34
tobiasvl np16:35
ToxicFrog mikehaas763: my workflow at work actually rebases my local commits against upstream daily. Then when the changes are ready they get squashed into a single commit and pushed.16:35
zizzfizzix left16:35
swahili is it possible to know how many commits exist ? that would be handy to actually know more or less in time I'd like.. based on number of commits (I know not perfect)16:35
JosephFerano joined16:37
tang^ left16:39
tang^2 left16:39
tang^ joined16:39
jmichaelward left16:40
tang^ left16:40
thedodd joined16:40
tang^ joined16:40
reyha joined16:40
Gizburdt joined16:41
liamkeily left16:41
glosoli left16:41
mnavratil left16:41
cablop joined16:41
zizzfizzix joined16:42
ajustrun joined16:42
cablop hello16:42
moritz swahili: in a given repo? git log --all -1|wc -l16:44
erm no16:44
--online instead of -116:44
swahili moritz: cool thanks : D16:44
moritz git rev-list --all|wc -l # faster, same result16:45
jenni_naiaretti joined16:45
ojacobson left16:45
PinkSpecs left16:45
cablop i have this issue: i have a rebase that is failing because one of the previous scommits is not receiving me all the changes on some files, i need for that commit to accept changes even at newline level, but it is ignoring the fact one file has unix new lines, the other has windows new lines, and it does nothing, i need to replace the old unix newlines with windows newlines AND the git to send thos16:47
those new lines in the commit!16:47
P4_Denis left16:47
teran_ left16:47
skeuomorf joined16:50
carandraug left16:50
thedodd left16:51
mnavratil joined16:51
Advocation left16:51
Bilge joined16:52
Advocation joined16:52
nour left16:52
mnavratil left16:52
mkaesz left16:53
Advocation left16:54
fragamus joined16:54
batrick_ left16:54
batrick joined16:55
skeuomorf Hey folks, I have a directory .vim that wasn't tracked using git, however I have a bunch of plugins inside .vim/bundle/ with each one of them tracking a remote branch, I would like to `git init` my .vim directory and make each one of these plugins a submodule, how would I go about doing that?16:55
batrickGuest3743916:55
swahili left16:55
cuppscakes left16:55
mnavratil joined16:57
mizu_no_oto joined16:57
SethM joined16:57
Guest37439 left16:58
cuppscakes joined16:58
cuppscakes left16:58
xolubi left16:58
robarelli joined16:58
cuppscakes joined16:58
msankhala joined16:58
cablop how do i force commiting breaklines?16:59
thedodd joined16:59
forwchen joined16:59
place left17:01
imachuchu joined17:01
hexagoxel left17:01
pcypher left17:01
fission6 left17:03
robarelli left17:03
refried_ joined17:03
tobiasvl skeuomorf: read up on !submodules17:04
gitinfo skeuomorf: [!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://www.git-scm.com/book/en/Git-Tools-Submodules17:04
mennea left17:04
fold left17:04
imkmf joined17:04
mikecmpbll joined17:04
mennea joined17:04
kkuno left17:05
fragamus left17:05
vgarg joined17:05
fragamus joined17:05
skeuomorf tobiasvl: I've read that actually before asking here and the information conveyed there was mostly for adding submodules from scratch after having an existing git directory, will reread though17:05
dgpalmer joined17:06
robustus|Offrobustus17:06
DolphinDream joined17:07
msankhala left17:07
_Vi left17:07
m0viefreak left17:09
logix812 joined17:09
mizu_no_oto left17:09
Gamecubic left17:10
Gamecubic joined17:11
StarManta left17:11
fission6 joined17:11
davividal joined17:11
Advocation joined17:11
Vasastan left17:11
subhojit777 left17:12
jeremyheiler joined17:12
dreiss joined17:12
HanClinto_ joined17:12
forwchen left17:13
Gizburdt left17:13
P4_Denis joined17:13
chessguy left17:13
skeuomorf left17:13
a_le_ joined17:14
a_le left17:14
robustusrobustus|Off17:15
HanClinto__ left17:15
bbloom left17:16
baweaver joined17:16
Gizburdt joined17:16
Sample joined17:17
wagle_ joined17:17
HanClinto__ joined17:17
wagle left17:17
palcu left17:18
lsiv568 joined17:18
hmsimha_ joined17:18
Mobutils left17:19
palcu joined17:19
HanClinto_ left17:19
rutnop joined17:20
leeN joined17:20
thevishy_home joined17:21
thevishy joined17:21
ojacobson joined17:21
mieko left17:21
a_le_ left17:21
akagr joined17:22
joelteon left17:22
palcu left17:23
msmith_ left17:23
subhojit777 joined17:23
thiago_ joined17:23
subhojit777 left17:24
ropav joined17:25
teran joined17:25
daedeloth left17:26
encod3 left17:26
Gizburdt left17:26
Gizburdt joined17:27
palcu joined17:28
pcypher joined17:28
Gizburdt_ joined17:28
subhojit777 joined17:28
palcu left17:28
ncthom91 joined17:29
palcu joined17:29
ncthom91 left17:30
fragamus left17:31
skynxnex left17:31
Sample_ joined17:31
Sample_ left17:31
Sample_ joined17:31
maestrojed left17:31
Gizburdt left17:31
a_le joined17:31
joo-_ Can i use git to check out to blame for a specific json item while handling json in php or some other technology?17:31
__TheDodd__ joined17:32
Sample left17:32
forwchen joined17:32
thedodd left17:32
ropav left17:32
kermit left17:33
jenni_naiaretti left17:33
_ikke_ what?17:33
jwmann left17:33
palcu left17:34
cuppscakes left17:34
BuenGenio left17:34
subhojit777 left17:34
mennea left17:34
joo-_ when iterating through elements in php that i was decoded in some json that is under version control, i want to know what operator can be blamed for committing the specific json, but i suppose i will just embed the operator and commit date inside the data also17:34
cuppscakes joined17:34
mennea joined17:35
Sample joined17:35
thedodd joined17:35
tobiasvl haha what17:35
PerlJam "json under version control" sounds a little weird.17:35
awkwardusername left17:36
kermit joined17:36
kermit1 joined17:36
joo-_ i have been going wild on the pain medicate i must admit maybe i cannot help17:36
but i think i kinda need it17:36
kermit1 left17:37
kermit1 joined17:37
koderok joined17:37
kermit left17:37
kermit1kermit17:37
msmith_ joined17:37
__TheDodd__ left17:38
WaReZ joined17:38
wagle_wagle17:38
jitendravyas joined17:38
maestrojed joined17:39
Dudi left17:40
mnavratil left17:40
lsiv568 left17:41
cablop left17:41
evildmp left17:41
__TheDodd__ joined17:41
akagr joo-_: can you break down what you are trying to do? Do you have json file checked in git? It is generally difficult/discourged to access git functions from inside a running app17:41
evildmp joined17:41
akagr git is for managing code... it should not participate in it17:42
ojacobson "can I invoke git from some other program" yes, that's how git works internally, too17:42
however, yeah, using git as a data store for your app is likely to end in tears17:42
subhojit777 joined17:43
parcs left17:43
koderok left17:43
lsiv568 joined17:43
thedodd left17:44
cuppscakes left17:45
Guest53211 left17:45
joo-_ left17:45
gccostab_ joined17:47
CheckDavid joined17:48
thiago_ left17:48
thiago joined17:48
mizu_no_oto joined17:48
ecky--ptang-zoob left17:49
gccostabr left17:49
Mobutils joined17:49
vgarg left17:49
ecky--ptang-zoob joined17:49
mixandgo left17:49
Aikar joined17:50
__TheDodd__ left17:50
beaky joined17:50
beaky hello17:50
martinklepsch joined17:51
Gizburdt_ left17:51
beaky how do i modify an earlier commit to include my staged changes17:51
_ikke_ Last commit you made?17:51
beaky second last :D17:51
Gizburdt joined17:51
_ikke_ git stash; git rebase -i HEAD~2; change pick to edit for the commit, save, quit; When in the shell: git stash pop; git commit --amend; git rebase --continue17:52
worc left17:53
Cassiopaya joined17:53
Dudi joined17:54
Not_Whatever joined17:54
_ikke_ (don't forget to add the changes before the commit17:54
)17:54
Aikar Hi - I’m desperately trying to get a git-svn workflow going so I can use git at work where we use SVN. Migrating to Git just isnt on the companies plans. My issue is that git svn clone does not work with specifying revisions and a path that was not changed by that revision. Sure I can fix the revision on the svn side… but I’m trying to work up some scripts that will full clone the svn repo and handle the externals. If an external of my project also does the sa17:55
thing… i cant really go chasing down and updating the revision of every depth level :/ - so for example this checks out no files: git svn clone -r 26 svn+ssh://svn01.colo/repo/tags/v1.4/lib lib/repo - any way to work around this?17:55
jaeckel joined17:55
Fomina joined17:55
nezZario what the heck would this do in a config under [remote "all"]17:55
url = access-3:/var/www/html.git17:56
Gizburdt left17:56
Sonderblade can you get git to convert to lf but never to crlf?17:56
ojacobson ssh protocol, host/config access-3, path /var/www/html.git17:56
sq-one joined17:56
Suchit joined17:56
jdrumheller left17:57
thedodd joined17:57
EminenceHC left17:57
EminenceHC joined17:58
gitinfo set mode: +v17:59
btanaka joined17:59
_ikke_ Sonderblade: Use dos2unix as a clean filter, and cat as a smudge filter?17:59
Sonderblade: see man gitattributes17:59
gitinfo Sonderblade: the gitattributes manpage is available at http://jk.gs/gitattributes.html17:59
robarelli joined17:59
ropav joined17:59
forwchen left18:01
cuppscakes joined18:01
nezZario ojacobson: holy .. thanks18:01
would of never got that18:01
Sonderblade _ikke_: im on windows18:01
nezZario trying to reverse engineer some guy's stuff here18:01
forwchen joined18:01
diegoviola left18:02
EminenceHC left18:02
Sonderblade basically i want core.autocrlf=true but without crlf insertion18:02
jpf joined18:03
jpf left18:03
jpf joined18:03
pcypher left18:04
mennea left18:04
Suchit left18:04
Pyrogerg_ left18:04
mennea joined18:05
Suchit joined18:05
ropav left18:05
robarelli left18:05
killtheliterate left18:06
CEnnis91 joined18:06
ropav joined18:06
Blaster joined18:07
skeuomorf joined18:07
cuppscakes left18:07
Blaster Someone made a PR on my GH repository from their fork.18:08
worc joined18:08
Blaster How do I pull that forked branch down to my local machine?18:08
I want to fast-forward it, because we try to avoid merge commits.18:08
Sonderblade left18:09
burhan left18:09
forwchen left18:09
TititaTitutu joined18:10
_ikke_ github has instrunction on it18:11
aidalgol joined18:11
_ikke_ It says it on the pull request18:11
martinklepsch left18:11
burhan joined18:11
_ikke_ This pull request can be automatically merged.18:12
You can also merge branches on the command line.18:12
Guest3934 left18:12
Pyrogerg joined18:12
bihi joined18:12
mixandgo joined18:12
JeanCarloMachado joined18:13
maqr left18:13
mixandgo left18:13
JeanCarloMachado left18:13
gitinfo set mode: +v18:13
SirSilence joined18:13
ande_ joined18:14
lorenx joined18:15
tristanp left18:16
zamabe joined18:16
sevenless joined18:16
lorenx hi all. excuse me for the silly question... i need to slipt the root commit and i'm following this hint: http://goo.gl/Y9OvHz18:17
dmarkham left18:17
lorenx but i don't understand how to use the second command, "git commit --amend"18:17
how can i slipt the commit with the amend option?18:18
noxd joined18:18
sevenless Hi. I don't understand how you're supposed to merge something on Github.18:19
Seveas lorenx: 'slipt'?18:19
lorenx i've also tried with "git rebase -i --root"18:19
Seveas: split18:19
Seveas ah!18:19
lorenx :D18:19
Seveas that's tricky. How many commits do you have in total?18:19
lorenx not many18:20
why?18:20
Seveas sevenless: pull requests that can be merged automattically will show a merge button. Other's you'll have to fetch and merge manually18:20
cagedwisdom joined18:20
avocado joined18:20
gitinfo set mode: +v18:21
Sample left18:21
Sample_ left18:21
zyla left18:22
sevenless Seveas: OK, how do you do that? I've forked the master.18:22
Sample joined18:22
Seveas lorenx: in that case I suggest tagging what you have now, doing a reset --hard to the root commit. Then edit to remove what you don't want in the root and committing that. And then reverting that commit with revert. And then rebase -i to squash the root and the second commit, and give the third commit a better commit message18:22
lorenx: and then cherry-pick all the other commits.18:22
thibaultcha joined18:22
sevenless Seveas: I go git fetch <master>, right18:22
Seveas no18:22
if you've forked a repo and want to merge from it, ready !sync18:22
gitinfo [!fork_sync] You can read a nice guide on how to update your fork with the upstream repository here: https://help.github.com/articles/syncing-a-fork18:22
decompiled joined18:23
Dudi left18:23
EminenceHC joined18:23
lorenx Seveas: sorry but what do you mean, at that stage, when you say "Then edit to remove what you don't want"18:25
cnj joined18:25
sevenless Seveas: reading, thanks18:25
lorenx i mean, if i set my root commit to be edited, how do i actually split it18:25
sevenless Seveas: I can use "git clone" to check out my own fork, then "git fetch upstream" to fetch the master.18:26
oskarkv left18:26
lorenx i usually do a reset HEAD^ but i cannot do it at the root stage, right?18:26
nour joined18:26
bihi Hi, is there a way to have a master branch that follows origin/master without needing to pull or rebase or merge --ff to get to the new stuff?18:26
ColKurtz joined18:26
bihi I tried git symbolic-ref refs/heads/master refs/remotes/origin/master18:27
Seveas lorenx: yeah, so what I said will sort-of do a reverse split: if you merge the root commit with the second commit, it'll have the effect of the split, as the third commit reverts the split18:27
bihi it's basically what I need, but things like git branch --merged don't work if I do that18:28
Seveas lorenx: e.g. if your root commit has a file with just two lines "a" and "b", and in the second commit you remove "b" and the third commit reverts that removal, sqaushing root and the second commit together later will make it look like you've split the root18:28
baweaver left18:28
nnyk left18:29
Remram Why is 'status' super-fast while 'checkout -- .' and 'stash -p' are super-slow? Don't they use the same mechanism to find changed files?18:29
lorenx Seveas: wait, let's say that my root commit has 2 files and i need it to have just one of them and then the second file in a "new" second commit18:30
Seveas lorenx: so your second commit would remove that second file18:30
and the third commit reverts that removal18:30
and then you squash 1 and 2 together18:31
evildmp left18:31
lorenx sorry, maybe i don't understand :)18:31
dan64 joined18:31
lorenx my root commit has file a and file b, then my second commit has file c18:31
Seveas that's why you reset --hard to your root commit first18:31
so you don't have all these commits that get in the way18:31
ojacobson Remram: what makes you think 'git checkout -- .' only looks at changed files?18:32
Seveas and after you've cleaned up your root commit, you cherry-pick all your other commits18:32
Sasazuka joined18:32
lorenx i need to have 3 commits, the first with file a, the "new" second commit with file b and the third (ex second) with c18:32
Seveas (so don't forget to tag your current HEAD, that way you can find those commits again!)18:32
jgardella joined18:32
Seveas git tag pre-reworked-root; git reset --hard shaq_of_root_commit; git rm file_i_dont_want_in_root; git commit -am "fixup root"; git revert HEAD; git rebase to squash root and second commit18:34
but if it's really that simple, you can do a simpler dance18:34
mennea left18:34
mennea joined18:35
skeuomor1 joined18:35
jgardella left18:35
Seveas git tag pre-reworked-root; git reset --hard shaq_of_root_commit; git rm --cached file_i_dont_want; git commit --amend; git add file_i_didn't_want_but_want_now; git commit18:35
bezet left18:35
cuppscakes joined18:35
Seveas and then cherry-pick the other commits18:35
cuppscakes left18:35
lorenx well, let me try ;)18:35
jgardella joined18:35
Seveas remember to !backup :)18:36
gitinfo Worried about your data while trying stuff out in your repo? The repository in its entirety lives inside the .git directory in the root of your work tree so to backup everything `cp -a path/to/workdir path/to/backup` or equivalent will suffice as long as the repo is not modified during backup. See also http://sethrobertson.github.com/GitBestPractices/#backups18:36
cuppscakes joined18:36
milkohol left18:36
lorenx Seveas: anyway, can i also use "git rebase -i --root"?18:36
Seveas not for splitting the root commit18:37
skeuomorf left18:37
lorenx what about this then: http://goo.gl/qrd0In18:38
Sasazuka left18:38
lorenx it is just to reword it?18:38
Sasazuka joined18:38
endiruna left18:39
joo-_ joined18:39
Tuna-Fish left18:39
Pyrogerg left18:40
Seveas lorenx: hmm. It may work if you set the root commit to 'edit', and then when you get to edit that comit, git rm --cached that_file; git commit; git add that_file; git commit; git rebase --continue18:40
sevenless Seveas: So how do I fetch the master from the repo that I forked?18:41
Toaster` joined18:41
Seveas sevenless: !sync explains that18:41
gitinfo sevenless: [!fork_sync] You can read a nice guide on how to update your fork with the upstream repository here: https://help.github.com/articles/syncing-a-fork18:41
shinnya left18:41
Seveas lorenx: let me experiment a bit with that :)18:41
irqq joined18:41
Manny joined18:41
Manny left18:42
EminenceHC left18:42
Pyrogerg joined18:42
killtheliterate joined18:42
Manny joined18:43
Seveas lorenx: yeah that works18:43
even easier than my convoluted tag/cherry-pick dance18:43
Sebtoast left18:44
Sasazuka left18:44
lorenx ok, let me try the easier one then18:44
zyla joined18:44
epifanio joined18:44
lorenx i should do rebase -i --root and edit the root commit, right?18:44
mieko joined18:44
Seveas yes18:45
Sasazuka joined18:45
reyha left18:46
Seveas and the edit process should be: git rm --cached file_i_dont_want_in_the_root; git commit --amend; git add file_i_dont_want_in_the_root; git commit18:46
and then git rebase --continue18:46
subhojit777 left18:47
lorenx it seems i have 2 root commit now :D18:47
baweaver joined18:48
Sasazuka left18:48
lorenx ok, it seems i got it ;)18:49
Bilge left18:49
lorenx thanks a lot18:49
Seveas no problem, and sorry for the confusion18:49
vgarg joined18:49
Tuna-Fish joined18:50
aard_ joined18:50
lorenx left18:50
Sasazuka joined18:50
tristanp joined18:50
TititaTitutu left18:51
vgarg left18:51
vgarg joined18:51
listochkin joined18:51
avocado left18:52
_Atom_ joined18:52
Nizumzen left18:53
joo-_ left18:53
TititaTitutu joined18:53
_Vi joined18:54
joo-_ joined18:54
akagr left18:55
ropav left18:55
Bilge joined18:56
EminenceHC joined18:57
bug_sniper joined18:57
robustus|Off left18:57
lsiv568 left18:58
JDHawke afternoon folks....18:59
Remram ojacobson: it doesn't18:59
robbyoconnor joined18:59
Remram ojacobson: reset --hard is fast, status is fast, but stash -p is slow, checkout -- is slow18:59
JDHawke I have a working copy of a website, and I want to convert it to a sparse checkout without having to remove the whole thing and re-clone it....I just want to exclude some folders and have them removed from the disk in this case19:00
grawity Remram: run all of them under `strace`, it'll show how they differ19:00
akkad left19:00
Remram whereas I can't see any reason they can use the same (fast) approach at determining which files changed19:00
grawity JDHawke: a sparse checkout is only applied on the "checkout" step, so just... create the checkout-list file and run `git checkout -f` or something19:00
salgotrav left19:00
jitendravyas left19:01
JDHawke thanks19:01
vgarg left19:01
robarelli joined19:01
ropav joined19:02
Eminence_ joined19:02
robustus joined19:02
Sasazuka left19:03
EminenceHC left19:03
akkad joined19:03
mennea left19:04
Eminence_ left19:04
mennea joined19:05
pcypher joined19:05
Sasazuka joined19:05
cuppscak_ joined19:05
cuppscak_ left19:06
PsciCOdeliXHAt left19:06
jgardella left19:06
cuppscak_ joined19:06
cuppscak_ left19:06
ropav left19:07
cuppscak_ joined19:07
robarelli left19:07
ojacobson left19:07
ojacobson joined19:08
TititaTitutu left19:08
Sasazuka left19:08
TititaTitutu joined19:09
dmarkham joined19:09
cuppscakes left19:09
wrouesnel1 left19:10
pcypher left19:10
Mso150_u_n joined19:10
aswen joined19:10
Sasazuka joined19:10
jdrumheller joined19:10
Mso150_u left19:11
Bilge left19:11
intellix left19:11
sq-one left19:13
sevenless OK. I don't get the line endings thing. If I have CR-LF line endings, and my .gitattributes says to make text=auto, is that OK?19:14
vgarg joined19:15
martinklepsch joined19:15
vgarg left19:16
jenni_naiaretti joined19:16
Bilge joined19:16
vgarg joined19:16
vire joined19:16
akushner__ left19:17
martinklepsch left19:18
ianbrandt joined19:18
hexagoxel joined19:18
jdrumheller left19:19
skeuomor1 left19:20
ropav joined19:20
squirrel left19:20
skeuomorf joined19:20
sqrrl joined19:21
skelterjohn anyone know when credential.helper was introduced? having trouble looking that up19:21
seu_barriga joined19:21
t4nk059 joined19:22
seu_barriga hello19:22
EminenceHC joined19:22
sevenless Help. I don't know what's up with the line endings here.19:22
liamkeily joined19:23
pandeiro joined19:23
seu_barriga someone made a commit that deleted some important files on my repository. I can reset to a previous commit to restore the files, but i can't find a way to "recommit" them over19:23
I'v e already tried rebasing19:23
Suchit left19:24
seu_barriga is it possible?19:24
darkbasic left19:24
Suchit joined19:24
darkbasic joined19:25
thiago left19:25
johtso left19:25
milkohol joined19:25
nimdAsyS left19:25
pcypher joined19:26
hexagoxel left19:26
Sample left19:27
t4nk059 left19:27
himikof joined19:27
vgarg left19:28
jstimm joined19:28
someplace seu_barriga, do you want to revert the entire commit?19:28
_ikke_ skelterjohn: 1.7.9 is what I can find19:28
Suchit left19:29
MutSbeta left19:29
cablop joined19:29
himikof left19:29
sLite left19:29
cablop how good is git at resolving path changes?19:29
someplace git can't store path changes in its database19:29
seu_barriga someplace, yes, but i want to keep my current changes19:29
_Atom_ left19:30
someplace seu_barriga, you should be able to do "git revert [commit]" for that19:30
himikof joined19:30
MutSbeta joined19:30
Seveas skelterjohn: abca927dbef2c310056b8a1a8be5561212b3243a - 1.7.919:30
someplace if it's complaining about working tree, !stash19:30
maybe that's not at hing19:30
_ikke_ Seveas: Beat you :P19:30
Seveas _ikke_: but with less complete info :P19:30
_Atom_ joined19:30
pcypher left19:30
cablop someplace: i mean, i have a file .../dirA/file.ext then i move it to .../dirB/dirC/file.ext19:30
marchelzo_ joined19:31
_ikke_ v1.7.9-rc2~3^2~1619:31
Seveas cablop: pretty decent, given that it doesn't store rename info.19:31
Nerd42 joined19:31
_ikke_ Seveas: That complete enough?19:31
seu_barriga someplace, by [commit] do you mean the commit that deleted the file or the one before it?19:31
someplace seu_barriga, the one that removed the file.19:31
cablop, it depends on the tool, the tool needs to guess that the file was moved19:31
paulweb515 left19:31
someplace git can't store renames or moves19:31
_ikke_ It doesn't by design19:31
cablop o.o19:31
_ikke_ You can tell git to infer it19:32
someplace it's generally pretty good though, as long as the file wasn't modified too much in the same commit that it was moved19:32
_ikke_, I'm aware, and it's a lot cleaner for it :)19:32
seu_barriga ok19:32
i'm gonna try it19:32
vgarg joined19:32
cablop what if instead of moving i move and copy it, i.e., dirA/file.01 becomes dirB/file.01 and dirC/file.0119:33
?19:33
Seveas cablop: git's log/blame etc. will detect that too19:33
_ikke_ https://lkml.org/lkml/2005/4/10/7019:33
sevenless I don't get it. Git merge created two complete copies of the same file. Is this because the line endings changed?19:33
cablop Seveas: so i can reach the repo history of file.01 from both files, right?19:34
Sample joined19:34
ItSANgo left19:34
jgardella joined19:34
aidalgol left19:34
mennea left19:34
mennea joined19:35
Seveas _ikke_: "19:35
But it clearly is the only right way. The fact that everybody else does it19:35
some other way only means that they are wrong."19:35
someplace cablop, I don't believe so.19:35
Quevin left19:36
Seveas cablop: good question. I don't know. I don't store duplicates :)19:36
thiago joined19:36
cablop hmmm19:36
sohail left19:36
cablop we don't need to duplicate, but to fork a file instead19:36
robertodecurnex joined19:36
cablop svg files, but we need to keep the history of both19:36
sohail joined19:36
baweaver left19:37
hmsimha_ left19:37
Nerd42 left19:37
Seveas you don't lose history19:38
sevenless Ah. I can use git reset --hard HEAD; git push -f19:38
jenni_naiaretti left19:38
baweaver joined19:39
Nizumzen joined19:40
jgardella left19:42
sr____ joined19:42
jgardella joined19:42
Diemuzi joined19:43
ropav left19:43
Diemuzi left19:43
jeremyhe_ joined19:43
seu_barriga sevenless , something weird happenned19:44
cablop i need to force commiting line endings19:44
Steve_Jobs is it possible to do a shallow mirror of a bare repo that includes only 1 snapshot of 1 branch?19:44
seu_barriga the file is being deleted after a specific commit, but the log shows no reference of deleting it19:44
cablop how can i force the commit of line endings? i have a rebase that it's failing because of line endings!19:45
jds left19:45
nettoweb left19:46
joo-_ left19:46
jeremyheiler left19:47
Walex left19:47
ropav joined19:47
dmarkham left19:47
martinklepsch joined19:48
mizu_no_oto left19:48
cuppscakes joined19:49
cablop is there no way for that?19:49
cuppscakes left19:49
paul424 joined19:49
damccull left19:50
zburns left19:50
someplace cablop, force the commit..?19:50
_ikke_ Seveas: btw19:50
Seveas: http://tinyurl.com/git-changes19:50
cuppscakes joined19:50
cuppscakes left19:51
vgarg left19:51
cablop someplace: i have a file that i need to store with windows line endings, it currently has linux line endings, git says, nothing to commit19:51
someplace unix2dos file19:51
git add file && git commit?19:51
xender cablop: !lf19:51
gitinfo cablop: [!use_lf] To eliminate all issues with line-endings in a repo it is recommended to change all files to use LF, and then convince all contributors to use LF-aware editors (Notepad++ works well for Windows), by force if necessary. !crlf has some tips if this is not feasible.19:51
xender !crlf19:51
gitinfo to fix problems with line endings on different platforms, check out http://line-endings.gitrecipes.de/19:51
xender I meant the second one I think19:52
!line-endings19:52
gitinfo [!crlf] to fix problems with line endings on different platforms, check out http://line-endings.gitrecipes.de/19:52
cuppscak_ left19:52
xender Sorry, I don't remember those keywords19:52
ItSANgo joined19:53
ecky--ptang-zoob left19:53
ecky--ptang-zoob joined19:54
jjasinski left19:54
sevenless God, fuck line endings on git19:54
ecky--ptang-zoob left19:54
sevenless Are you supposed to use core.autocrlf false?19:54
PinkSpecs joined19:54
xender Depends on use case?19:54
ecky--ptang-zoob joined19:55
sevenless Say I want to use LF everywhere, which seems to be the standard19:55
And I'm editing on Windows19:55
maslowbeer hello. so i'm doing a merge of a pull request from BB where there are a ton of conflicts but they're all easily resolved since the same source should prevail with each conflict. i just want to clarify which is "ours" and which is "theirs" before executing. Also clarifying the difference between git merge --theirs vs git merge --strategy-option theirs19:55
sevenless I just need to use core.autocrlf false and make sure Notepad++ uses LF too... right?19:55
cablop xender, sadly it is a rebase... so, i cannot change the lf in the past with no pain... 200 commits to rebase... :/19:55
xender cablop: filter-branch maybe?19:56
maslowbeer i'm on develop now and I want to merge lite-changes into develop. the pull request was done in BB19:56
_ikke_ maslowbeer: When merging, ours is the branch you're on, theirs is the branch you are merging19:56
maslowbeer: git merge --theirs doesn't exist..19:56
xender sevenless: autocrlf is just for use in that situations - it automatically commits with LF and checkouts with CRLF19:56
sevenless: So I'd say set it to true19:56
_ikke_ maslowbeer: git merge --strategy-option theirs means it will always choose the 'theirs' side when a conflict happens19:57
sevenless xender: So what happens if something's committed with CRLF, checked out on windows, then merged with something committed with LF19:57
It seems to screw up.19:57
cablop sevenless: in fact it screws up!19:57
xender sevenless: That's why autocrlf never commits with CRLF19:58
It does conversion between LF repo and CRLF workspace19:58
sevenless cablop: Yes. I just had a "WTF" reaction when I noticed my push had entirely replaced the entire code base.19:58
cablop my repo says, rebasing... when it is, say in the commit 170... it says, i cannot commit it because you have changes in your workspace...19:58
kukks joined19:58
maslowbeer _ikke_, ok great. in the diffs on the pull request which is source and which is destination? I presume source would be the branch we're merging (theirs) into the destination (ours). that right?19:58
doitjay joined19:58
cablop commit them.... but it refuses to commit them, cause git believe line endings are no issue19:58
sevenless Why isn't git smart enough to just turn CRLF into LF19:59
if this is an issue19:59
petersr left19:59
lsiv568 joined19:59
_ikke_ maslowbeer: I would think so, yes19:59
xender sevenless: But it does it... When you have autocrlf set to true19:59
cablop git is openning the files and saying, oh, i have nothing to do, files are the same, but when rebasing, oh, stop, the files are different! i cannot continue!19:59
ColKurtz left20:00
sevenless xender: But it doesn't. I tried to merge a remote committed with LF and an origin committed with CRLF.20:00
sdrfnord1 left20:00
dmarkham joined20:00
cablop crlf... auto?20:00
xender sevenless: something that is actually committed with CRLF is another matter20:00
cablop hmmm20:01
xender sevenless: And another problem20:01
cablop ah, no, it is not going to work... once i rebase... then the rebase is going to delete the gitpreferences!20:01
thevishy left20:01
xender sevenless: autocrlf will only convert line endings when checking out and committing. No more20:01
sevenless xender: it only takes one push to contaminate the repo with CRLF and you only find out when your merges don't work.20:02
thevishy_home left20:02
jdrumheller joined20:02
baweaver left20:02
bihi left20:02
xender sevenless: Yes20:02
skeuomorf left20:02
xender sevenless: As it takes "only" one force push to do much worse things with repo20:03
sevenless xender: this is particularly pernicious because it's invisible20:03
mieko left20:03
dgpalmer left20:03
xender Actually, at work we have problems with some poeple overseas committing binaries to repo...20:03
lsiv568 left20:03
pcypher joined20:04
xender And they use force push sometimes too. As in "I don't know what's going on, so --force"20:04
m0ltar left20:04
robarelli joined20:04
xender sevenless: You may try a mergetool which can ignore LF differences20:04
mennea left20:04
cuppscakes joined20:04
cuppscakes left20:04
xender p4merge can be set to do that... And for sure there are some other tools20:04
mechanicalduck_ joined20:05
xender But yeah, it may still produce ugly diff20:05
cablop xender, sevenless: afaik autocrlf true could damage my binaries, couldn't it?20:05
mennea joined20:05
Toaster` left20:05
cuppscakes joined20:05
pheaver left20:05
cuppscakes left20:05
sevenless cablop: iirc it tries to only do it to things that look like text20:05
Advocation left20:06
sdrfnord1 joined20:06
xender cablop: Dunno. That's unrelated to CRLF. More like "committers should be qualified" thing20:06
whaley joined20:06
cablop yep20:06
mechanicalduck left20:07
txdv left20:07
ropav left20:08
baweaver joined20:08
mechanicalduck_mechanicalduck20:09
robarelli left20:09
mollitz joined20:10
Noldorin joined20:10
nettoweb joined20:10
nettoweb left20:11
havanamint left20:11
jottr left20:11
seu_barriga left20:11
nettoweb joined20:11
nettoweb left20:12
eliasr left20:12
rezrov left20:12
Guest37896 left20:12
nettoweb joined20:12
nettoweb left20:12
rezrov joined20:12
ropav joined20:13
nettoweb joined20:13
nettoweb left20:13
sdrfnord1 left20:13
txdv joined20:13
nettoweb joined20:13
kukuuu joined20:14
thevishy_home joined20:14
moritzschaefer left20:14
thevishy joined20:14
cuppscakes joined20:14
cuppscakes left20:14
cuppscakes joined20:15
cuppscakes left20:15
fabiobik joined20:16
cuppscakes joined20:16
cuppscakes left20:16
pheaver joined20:16
fabiobik Hello guys20:16
gitinfo fabiobik: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.20:16
cuppscakes joined20:17
cuppscakes left20:17
jonmorehouse joined20:17
nour left20:17
fabiobik Does someone here uses bitbucket? its possible to use git:// intead of https:// ?20:17
cuppscakes joined20:17
cuppscakes left20:17
ajustrun left20:17
belak fabiobik: bitbucket supports ssh and https.20:17
xender fabiobik: You have to have ssh key set up to use git protocol I think20:18
cuppscakes joined20:18
EminenceHC left20:18
D-Boy left20:18
epifanio left20:19
EminenceHC joined20:19
belak xender: the git:// and ssh:// protocols are very different.20:19
Well, they act similarly, but are very different in how they run.20:19
xender But doesn't git:// use ssh for auth anyway?20:19
_ikke_ no20:19
belak xender: http://git-scm.com/book/en/Git-on-the-Server-The-Protocols20:19
_ikke_ git uses no auth at all20:19
git://20:19
It's meant for 'public' read-only access20:20
martinklepsch left20:20
xender Oh, nvm20:20
nour joined20:20
belak fabiobik: are you running into any issues with https or git?20:20
Er or ssh20:20
_ikke_ there is the internal git protocol which is used to transfer objects, and there is the git:// protocol, which is basically a plain git protocol over a specific port20:21
Marcus joined20:22
fabiobik does anyone knows a service that runs that ? excluding github?20:22
Wiz_KeeD left20:22
MatrixiumnHAL900120:22
belak fabiobik: why, out of curiosity?20:23
EminenceHC left20:23
jenni_naiaretti joined20:23
_ikke_ fabiobik: that runs what?20:23
paulweb515 joined20:23
D-Boy joined20:23
_ikke_ github doesn't use git://20:23
fabiobik _ikke_, yes it does20:23
Quevin joined20:24
belak https://gist.github.com/grawity/439274720:24
fabiobik belak, because i'm running a package that download his source from git://20:24
mizu_no_oto joined20:25
_ikke_ https://git.kernel.org/cgit/ uses it too20:25
wrouesnel3 left20:25
belak Yeah, makes sense for kernel.org because everything's public...20:25
beaky left20:26
_ikke_ there are more like that20:26
basically using cgit / gitweb plus git-daemon20:26
jenni_naiaretti left20:27
_ikke_ hmm, since git 2.1, merge.defaultToUpstream is by default true instead of false20:27
imkmf left20:27
freeman42 joined20:27
thevishy left20:28
baweaver left20:28
baweaver joined20:29
thevishy_home left20:29
Neozonz|Disc left20:31
Neozonz left20:31
jenni_naiaretti joined20:31
jceb left20:31
dgpalmer joined20:31
_ikke_ cool, fast-export --anonymize20:32
jottr joined20:32
_ikke_ git 2.220:32
liamkeily left20:32
tvw left20:32
fabiobik left20:33
gauke joined20:33
TheFuzzball joined20:34
mennea left20:34
n-st left20:35
rnaveiras joined20:35
nnyk joined20:35
mennea joined20:35
gauke left20:35
lun__ joined20:35
imkmf joined20:35
HAL9001Xack20:35
alvaro_o joined20:35
TititaTitutu left20:35
bezet joined20:35
killtheliterate left20:36
nour left20:36
jeremyhe_ left20:36
lazarus477 left20:36
rnaveiras left20:36
jeremyheiler joined20:37
zapb_ left20:37
n-st joined20:37
bgerber left20:38
ropav left20:38
lun_ left20:38
zamabe left20:39
bezet left20:39
Neozonz joined20:40
rnaveiras joined20:41
ropav joined20:41
r0bby_ joined20:41
r0bby_ left20:41
r0bby_ joined20:41
mscook joined20:41
rnaveiras left20:41
ropav left20:42
kriskropd left20:42
robbyoconnor left20:42
kriskropd joined20:42
chessguy joined20:43
tbxyz joined20:43
Manny left20:43
Manny joined20:43
DrShoggoth joined20:44
jas4711 joined20:44
bug_sniper left20:44
thedodd left20:45
shinnya joined20:45
HanClinto_ joined20:45
Blaguvest left20:45
ropav joined20:45
gitinfo set mode: +v20:45
Ankhers Someone just made a commit to origin/master that broke the repo. How would I go about changing origin/master to what my local master looks like?20:45
bgerber joined20:46
ojacobson that is a terrible way to fix that20:46
nnyk_ joined20:46
Ankhers What is the suggested way to fix?20:46
ojacobson if you don't want to make everyone do a bunch of work in their clones, fix it normally and push yet more commits20:46
and leave the broken bits in history20:46
tobiasvl Ankhers: !revert20:46
gitinfo Ankhers: That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?20:46
ojacobson minimally, 'git revert <commit>' will back out the offending commit (assuming it's not a merge).20:47
by creating a new commit that exactly reverses it.20:47
nnyk left20:47
baweaver left20:47
Ankhers It was a merge. So the best option at this point is to just clean in manually?20:47
baweaver joined20:47
tobiasvl Ankhers: just for learning purposes, git DOES allow you to rewrite origin's master with your master with a !force_push20:47
gitinfo Ankhers: If you need to overwrite the history of a remote git repository (very bad idea, see !rewrite), you can do so with `git push -f`. Note the remote server may reject this. See man git-config and search for receive.denyNonFastForwards. Best practice is for upstream servers to denyNonFastForwards.20:47
tobiasvl Ankhers: but it's not recommended because it's a !rewrite of history20:47
gitinfo Ankhers: Rewriting public history is not recommended. Everyone who has pulled the old history have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push -f <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum20:47
Nizumzen left20:48
kukuuu left20:48
HanClinto__ left20:48
tobiasvl Ankhers: just revert the merge commit. something like `git revert -m 1 <commit>` will do it (where -m is the child that was the mainline before the merge)20:48
Ankhers Alright. I guess I will try and fix it than. Thanks for the tips.20:48
TititaTitutu joined20:49
fabiobik joined20:49
TititaTitutu left20:49
thedodd joined20:49
upene joined20:49
mustmodify joined20:50
blubberbop left20:51
cads left20:51
nnyk joined20:51
evildmp joined20:51
ropav left20:52
killtheliterate joined20:52
AaronMT left20:52
ropav joined20:53
epifanio joined20:53
Cheaterman1 left20:53
lsiv568 joined20:53
darrennnn joined20:54
cjwilburn joined20:54
nnyk_ left20:54
robertodecurnex left20:55
darrennnn hi #git, i am a small time web developer. i use shared hosting for my few clients. i want to integrate git into my workflow but i am not sure how because i would like to learn how to deploy to the server. my question is -- should i be looking into how to PUSH changes to my server, or should i look into how to set up my servers to PULL from the "master" branch for that project?20:56
_ikke_ darrennnn: !deploy20:56
gitinfo darrennnn: Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html20:56
ojacobson !deploy20:56
darrennnn i am going to use bitbucket as my private repo for my projects20:56
nnyk left20:56
damccull joined20:56
nnyk joined20:57
nnyk left20:57
ropav left20:57
lsiv568 left20:57
fission6 how do i checkout a remote branch20:58
darrennnn _ikke_: ojacobson : thanks ill read. i guess this question is pretty common lol.20:58
_ikke_ it is20:58
tbxyz left20:59
Seveas fission6: git checkout remotename/branchname20:59
mizu_no_oto left20:59
_ikke_ That will leave you in a detached HEAD though20:59
Seveas indeed20:59
fission6 thanks20:59
zumba_addict left20:59
Seveas but my head doesn't feel very attached anyway :)20:59
_ikke_ If you just do git checkout branchname, and there is no ambiguity, git will just create a branch on it though21:00
jargon joined21:00
tesaf left21:00
mustmodify left21:00
d10n-work left21:00
fission6 that seems towork oddly Seveas gives me a detached head21:01
davividal left21:01
grawity that is normal when checking out remote-tracking branches.21:02
livingstn left21:02
King_Hual left21:02
pr0ton joined21:04
fission6 hmmm21:04
LucasTT joined21:04
mennea left21:04
baweaver left21:04
mennea joined21:05
cads joined21:05
cjwilbur_ joined21:05
_ikke_ Checking out anything except branches (refs/heads/foo), will leave you in a detached HEAD21:05
Seveas fission6: you can check out any sha/tag/ref, but only if it matches a local branch, will HEAD not be detached. So if you want an attached head, create a branch that matches (and possibly tracks) the remote one. e.g. git checkout -b local_branchname remotename/remote_branchname21:05
robarelli joined21:05
fission6 will review21:06
ColKurtz joined21:06
hazeltree joined21:06
milkohol left21:06
darrennnn can someone ELI5 what "export GIT_WORK_TREE=/deploy/dir" is21:06
Seveas in newer gits, git checkout branchname, will check if any remote/*/branchname exists and create a tracking branch for you if it does21:06
fission6 so this is in a fab file to move some code over to a server, i kept getting merge commit editors popping up and i relized it was because if my server was on branch topic-A and i told it to pull topic-B, well I was merging! ideally i want to checkout a branch and then pull21:07
Seveas darrennnn: that doesn't parse...21:07
stevenvalladolid joined21:07
hazeltree left21:07
darrennnn Seveas: sorry? i dont understand21:07
_ikke_ fission6: Automatic pulling leads to pain21:07
jerius left21:08
Seveas darrennnn: that's what I was saying :)21:08
fission6 whts the best way to issue commands to say hey, i need you to checkout out branch-whatever and if you don't haveit get it from origin, then pull latest code, right now i have git checkout somebranch, and then git pull origin somebranch21:08
which is fine if the branch already exists and is being tracked ont he box21:08
Seveas fission6: !xy21:08
gitinfo fission6: Woah, slow down for a bit. Are you sure that you need to jump through 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...21:08
mikehaas763 left21:08
darrennnn Seveas: .... it's in the "git as a deployment tool" guide that i was just sent.21:08
_ikke_ darrennnn: It sets an environment variable, which gits read over override the work tree directory21:08
cjwilburn left21:09
jdrumheller left21:09
cuppscakes left21:09
cjwilbur_ left21:10
robarelli left21:10
pcypher left21:10
darrennnn _ikke_: so if my shared environment the folder lives at "~/www/git_tracked_folder" i should "export GIT_WORK_TREE=/www/git_tracked_folder" ?21:10
shared hosting environment21:10
fission6 i want to make sure i am on a specific branch before i pull21:11
jason237 left21:11
fission6 when issuing remote commands using a fabfile21:11
Cheaterman1 joined21:11
_ikke_ It should be the directory where the webserver looks21:11
Seveas automated pulling is not a good idea21:11
_ikke_ git checkout <branch>21:11
Mixologic left21:11
Seveas fission6: are you trying to !deploy?21:11
gitinfo fission6: Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html21:11
jason237 joined21:11
fission6 yes it is21:12
well its widly used, haha21:12
Seveas fission6: no it is not a good idea.21:12
doitjay left21:12
hexagoxel joined21:12
Not_Whatever left21:12
fission6 how do you deploy your code then Seveas21:12
aswen left21:12
noxd left21:12
_ikke_ I use capistrano21:12
Seveas definitely *not* with git pull. either git-deploy (at work) or git archive (for simpler things)21:12
pcypher joined21:12
fission6 _ikke_: what do you do inside of capistranro your answer is pretty ambiguas21:14
zumba_addict joined21:14
_ikke_ I use a plugin called railsless-deploy, but other than that, use the default strategy21:15
darrennnn ugh this shit is so complicated. i just don't understand it.21:16
sigh21:16
gccostab_ left21:16
doitjay joined21:16
danemacmillan left21:16
ojacobson left21:16
Seveas darrennnn: then don't use git for deploying, but an actual deployment tool21:16
_ikke_ fission6: It basically places the code in a timestamped directory, and then symlinks it to the webroot21:16
darrennnn Seveas: an actual deployment too is even MORE complicated21:17
Seveas well, that's what you get paid for :)21:17
upene left21:17
fission6 _ikke_: how does it place the code, thats sort of the whole point of my question21:17
_ikke_ darrennnn: git archive, and extract it to your webdir21:17
mscook left21:18
fission6 rad21:18
darrennnn _ikke_: obviously i'm hopeless because i don't see what that gets me. the idea is to simply push a new update and have it work instantly. one step from my desktop.21:19
i might as well ftp up a zip21:19
Ankhers left21:20
_ikke_ darrennnn: If that works for you :-)21:20
Droolio left21:20
jrnieder darrennnn: yep, git was not invented as a deployment tool21:20
it turns out different kinds of deployments have different requirements21:20
kballou joined21:20
jrnieder so some people use a package manager, some people use something like rsync, some people ftp up a zip :)21:21
hebz0rl_ left21:21
darrennnn at the end of the day all i want to do is have a directory with simple html and css and what not and be able to push to it. i don't necessarily understand the "not a deployment tool" rally cry for my relatively simple needs.21:22
so yeah i get it, in over my head, obviously i should stick to ftping everything.21:22
jrnieder well, no, you should stick to rsyncing everything. :)21:22
dccc left21:22
jrnieder it's like if you talk to some wrench afficionados and say it's doing a bad job of drilling a hole in the wall21:22
DrShoggoth left21:23
Mso150_u_n left21:23
zumba_addict left21:23
Seveas jrnieder: but if you look at a wrench in just the right way, it does look like a drill!21:23
zumba_addict joined21:24
darrennnn nah i mean simple example i have clients 1 2 and 3 on their own hosting packages. i use a color-picker for all three sites that lives in a folder /color-picker/ in the root of each.21:24
evildmp left21:24
darrennnn so when i update it, now i'm ftping to 3 sites. rather than having 3 sites pull the change.21:25
pandeiro left21:25
darrennnn is that a crazy bad way to look at it?21:25
_ikke_ fission6: capistrano uses git too. It fetches master, and then uses git reset --hard21:25
fission6 what do you mean21:25
_ikke_ fission6: Then it extracts those files to the timestamped dir21:25
Seveas darrennnn: no, but that's already different than your original deployment needs. And everybody's needs are different, so ther are different deployment tools.21:25
fission6 isn't that using git to deploy21:25
Seveas Git is not one of them.21:25
fission6: it uses git to prepare the deploy, not to actually deploy.21:26
Mso150 joined21:26
darrennnn Seveas: it's not any different than my original deployment needs. it's exactly what i said above unless i misrepresented myself somehow unclearly.21:26
fission6 why are peopel so against git being a dpeloyment tool, part of its value prob is distributing code right21:26
_ikke_ fission6: No, it uses git to get the latest data. The deploy happens after it21:26
fission6 how do you deploy the code21:26
how are you moving the code from one box to the other21:26
Seveas rsync21:26
zumba_ad_ joined21:26
zumba_addict left21:27
Seveas hundreds of rsyncs to hundreds of boxes, coordinated with func21:27
fission6 func?21:27
Seveas func21:27
_ikke_ fission6: it's not the sync part that's the problem, it's the consquent deployment part21:27
martinklepsch joined21:27
kukks left21:27
Seveas an obsolete RPC system from fedora. We'll be moving to salt.21:27
_ikke_ git pull inside a webroot for example21:27
hexagoxel left21:27
zumba_ad_ left21:27
zumba_addict joined21:28
fission6 ^ what21:28
it0a_ joined21:28
palcu joined21:29
_ikke_ fission6: That's what people try to do. Put a repository in the webroot, and then use git pull to update (or push from another repo)21:29
it0a_ left21:29
fission6 thats using git to deploy!21:30
_ikke_: i get that i am asking how you move code from one box to another21:30
your answers suck btw to all my questinos21:30
irqq left21:30
_ikke_ fission6: No need to be rude here21:30
fission6 ok21:30
tristanp left21:31
_ikke_ In my case, I push my code to a repo on the server, and capistrano uses that to deploy it to the webroot21:31
roaet left21:31
it0a left21:32
palcu left21:32
_ikke_ They are two seperate steps21:32
aard_ left21:32
thedodd left21:32
zumba_addict left21:32
palcu joined21:32
darrennnn so _ikke_ i dont understand what advantage or risk that prefvents as opposed to pushing to repo, and then pushing to a "deploy" branch that the server is on21:32
do you mind explaining that?21:32
fission6 darrennnn: i dont think he understands the notion of using git to deploy21:32
Seveas mine has some more step: developer does git pull on staging server, tests, calls git-deploy to tag the release and then another tool to do the rsync and coordinated restart dance21:33
darrennnn: pushing doesn't update a working tree, so it doesn't deploy anything21:33
darrennnn fission6: respectfully, im sure he does i just am not connecting the dots and maybe you too21:33
mennea left21:34
pheaver left21:34
_ikke_ Deploying commonly involves more then just updating files. Using just git to 'deployments' is bound to leave you in an inconsistent state (files that don't get deleted for example)21:34
Seveas darrennnn: you're trying to connect unconnectable dots. Version control and code deploy are two different things with different requirements. Use appropriate tools for each. git is appropriate for version control, not for deploying.21:35
fabiobik left21:35
darrennnn Seveas: i just dont understand especially on a developer environment why in the world it would require developers to manually PULL a change to test it unless you wanted to test a branch.21:35
which... arent you doing that locally?21:35
Seveas _ikke_: also: server restarts, loadbalancer actions, schema changes... :)21:35
thibaultcha The git bot says to read this, I've read it one day and I think they make some good points. http://gitolite.com/deploy.html21:35
mennea joined21:35
d2dchat joined21:35
Mso150_l joined21:35
_ikke_ Seveas: Indeed21:36
darrennnn Seveas: you're speaking in riddles. at the end of the day i want the files on my server to look like the files on my machine. (permission issues aside)21:36
_ikke_ Things like cache breakers21:36
HanClinto__ joined21:36
evildmp joined21:36
Seveas darrennnn: that's a *very* limited view of what deploying is.21:36
_ikke_ Seveas: though, common the reality on shared hosting21:36
palcu left21:37
nettoweb left21:37
darrennnn Seveas: that's my view from here. i dont need it for anything else. say i develop a wordpress theme or something simple. it lives in /wp-content/themes/my_git_tracked_theme/21:37
FunkyAss left21:37
Mso150 left21:37
darrennnn nothing more nothing less really.21:37
roflik left21:37
Seveas well, if you use wordpress you have bigger issues :)21:38
ok, low blow, sorry.21:38
jrnieder darrennnn: I think what you want is reasonable21:38
darrennnn or lets say i'm working on something more complicated like a set of classes that i use for multiple sites. again, i want them all updated on 5 different client websites.21:38
Seveas darrennnn: then don't bother with deploying. Just git pull manually.21:38
jrnieder darrennnn: it's possible some day someone will teach "git push" to do that21:38
darrennnn: Johannes Schildelin wrote a rough patch to do it before21:39
darrennnn: the trouble is, there are cases where that does confusing things21:39
Seveas jrnieder: push --update-work-tree?21:39
dgpalmer left21:39
jrnieder it was just 'push' into the checked out branch of a non-bare repository21:39
Seveas eww21:39
HanClinto_ left21:39
jrnieder yeah, blocking the push is a better behavior21:39
I think this patch was before git knew to block the push21:40
_ikke_ The problem is that you often have to deal with things like configuration files and cache files / assets / uploads, so the files on the server are almost never going to be exactly the same as you have them locally21:40
Hello_ joined21:40
baweaver joined21:40
jrnieder so, as a user, the basic task is to figure out what you want to happen during deployment21:40
mellernoia joined21:40
jrnieder then the usual building blocks for automating that are actually pretty straightforward21:40
darrennnn but _ikke_ isn't that handled in git by not modifying untracked files?21:40
jrnieder the hard part is figuring out what you want to happen (ordering, what to do with untracked files, etc etc)21:40
_ikke_ darrennnn: What about files you have deleted?21:41
jrnieder as lots of people mentioned before, http://gitolite.com/deploy.html does an excellent job of explaining the building blocks21:41
DARSCODE left21:41
evildmp left21:41
_ikke_ In your repo, that shouldn't be there anymore21:41
jrnieder unfortunately there's no way around just reading something like that, internalizing it, and making choices21:41
there's no one way to deploy21:41
dgpalmer joined21:41
darrennnn _ikke_: this may be due to unfamiliarity with git in general, but doesn't git know when you delete a tracked file? making it a different case than it being untracked?21:41
jrnieder in the case of local changes, detecting the local changes is not the hard part21:42
the hard part is figuring out what should then happen21:42
do you block deployment?21:42
_ikke_ What my deploy process does is just basically a fresh checkout every time, and then symlink the things that you need to keep (config files, cache, etc)21:43
mennea left21:43
_ikke_ (checkout being a copy of all the files in a new dir)21:43
oojacoboo joined21:43
darrennnn what i don't understand from that guide is how the process actually works. is this set up automatically somehow, or is this manually controlled through a push on my end. am i executing git commands from my machine or sshing into the server and doing them. that's where my confusion with that gudes lies... but ill read it again.21:43
gccostabr joined21:43
_ikke_ darrennnn: Most of the time, this is triggered in a git post-receive hook21:44
That has been put on the server21:44
jeremyheiler left21:44
Seveas and in our case by hand21:44
darrennnn _ikke_: is a post-receive hook set up on the server, or the repo, or on my machine?21:44
_ikke_ darrennnn: on the repo on the server21:44
jrnieder the server. see man githooks21:44
gitinfo the githooks manpage is available at http://jk.gs/githooks.html21:44
darrennnn oh okay you answered21:44
iamjarvo left21:44
_ikke_ Seveas: Yeah, my case too21:45
I'm calling it a day21:45
later21:45
Seveas enjoy your weekend!21:45
darrennnn _ikke_: thanks i do genuinely appreciate it21:45
_ikke_ thanks21:45
pheaver joined21:46
darrennnn i know youre taking your time, all of you. i'm just dumb and dont know this stuff.21:46
_ikke_ darrennnn: you're welcome. Sucess with deploying21:46
darrennnn: Not dumb, just inexperienced21:46
SethM left21:46
zumba_addict joined21:46
pr0ton left21:47
cablop to solve my issue...21:47
i cannot perform some rebase and merges properly...21:47
m0viefreak joined21:48
cablop should i globally set autocrlf = true, then reset hard my current heads, then merge and/or rebase?21:48
hmsimha_ joined21:48
evildmp joined21:48
chessguy left21:49
evildmp left21:49
_Atom_ left21:49
[M7] joined21:49
ropav joined21:50
n-st left21:51
ncthom91 joined21:52
SethM joined21:52
ropav left21:53
nour joined21:53
ropav joined21:54
killtheliterate left21:54
Neozonz left21:55
Neozonz joined21:55
mueslo left21:55
joelrobichaud left21:56
evildmp joined21:56
mueslo joined21:57
TheFuzzball left21:57
mizu_no_oto joined21:58
olspookishmagus joined21:59
paul424 left21:59
nettoweb joined21:59
nettoweb left21:59
nettoweb joined22:00
gfixler joined22:00
Steve_Jobs cablop: set it to false22:00
don't let scm manipulate your line endings22:00
rely on parameters to ignore them as differences22:01
let the editors on each platform handle them as needed22:01
pcypher_ joined22:01
cablop Steve_Jobs: i have the problem that a rebase is failing because of that! and i cannot pass parameters to the inner instructions22:01
r0bby_ left22:02
killtheliterate joined22:02
fission6 left22:03
Steve_Jobs cablop: why are you rebasing?22:04
ropav left22:04
Steve_Jobs try adding this strategy: -s recursive -Xignore-space-at-eol22:04
PaulCapestany left22:05
Steve_Jobs or this if that doesn't work: -Xignore-space-change22:05
pcypher left22:05
revyd left22:05
teran_ joined22:05
Steve_Jobs but this seems to be the modern way of doing things: -s recursive -X renormalize22:06
treehug88 left22:06
wakd left22:06
wakd joined22:06
PaulCapestany joined22:07
Steve_Jobs you could also touch all files making them have the same endings22:07
teran left22:07
Steve_Jobs find . -exec touch {}\;22:07
hmsimha_ left22:07
revyd joined22:08
Steve_Jobs but from then on don't rely on autocrlf=true. Set it to false and let the editors be configured to what they need22:08
hagabaka left22:08
zumba_addict left22:09
sohail left22:10
martinklepsch left22:10
jenni_naiaretti left22:11
zumba_addict joined22:11
hagabaka joined22:11
booboy joined22:12
mizu_no_oto left22:14
Neozonz left22:15
PinkSpecs left22:16
jenni_naiaretti joined22:17
acharlieh left22:18
EminenceHC joined22:18
Kicer86 left22:20
_Atom_ joined22:20
Cheaterman1 left22:21
pheaver left22:21
mizu_no_oto joined22:22
mdel left22:22
nettoweb left22:22
EminenceHC left22:22
nettoweb joined22:23
Quevin left22:23
nettoweb left22:23
naturally left22:25
nettoweb joined22:26
liamkeily joined22:27
liamkeily left22:28
jfran joined22:28
liamkeily joined22:28
kermit left22:29
kevin-brown left22:29
kevin-brown joined22:29
kermit joined22:30
mike_af left22:30
sevenless left22:32
nour left22:32
_Atom_ left22:32
d2dchat left22:32
pheaver joined22:33
pcypher_ left22:33
ockham left22:34
listochkin left22:35
listochkin joined22:36
bezet joined22:36
Thorn joined22:36
sqrrl left22:36
darrennnn left22:36
zumba_addict left22:38
bezet left22:40
listochkin left22:40
ropav joined22:41
sqrrl joined22:41
danemacmillan joined22:42
Neozonz joined22:42
Neozonz left22:42
Neozonz joined22:42
eletuchy joined22:42
ropav left22:43
Manny_ joined22:43
Manny left22:43
doitjay_ joined22:44
lun__ left22:44
vire left22:45
doitjay left22:47
toothrot joined22:47
Segfault_ joined22:48
kpease left22:48
Geo joined22:48
endiruna joined22:48
Geo I'm looking to merge my develop branch into my master, and I'm noticing some people advise first merging master to develop, then back to master. What is the logic behind this?22:49
doitjay_ left22:49
SumDude left22:50
msmith_ left22:52
afhammad joined22:52
Xackspanner22:52
jfran left22:53
xender Geo: doesn't look as a sensible workflow in general for me22:54
THere might be some specific use case22:54
maestrojed left22:55
Malsasa joined22:57
Neozonz left22:57
tang^ left22:58
evildmp left23:00
smccarthy left23:01
cads2 joined23:02
gfg joined23:02
jenni_naiaretti left23:02
gfg left23:02
WaReZ left23:04
tristanp joined23:05
pheaver left23:05
ropav joined23:05
jonmorehouse left23:06
miceiken joined23:06
evildmp joined23:07
miceiken What happens if I do git add and then not commit? Do I need to reset somehow?23:07
zumba_addict joined23:07
jfcaron joined23:07
liamkeily left23:07
robarelli joined23:07
Quevin joined23:07
kriks left23:08
jfcaron I have a local clone of a repo, and I made some changes, but now I want to also pull in more recent changes from upstream. How do I do that?/I don't know the proper terms to search for this.23:08
a_le left23:09
eletuchy left23:10
ropav left23:10
eletuchy joined23:10
jonmorehouse joined23:10
ropav joined23:10
epifanio left23:11
shizzle left23:11
eburcat left23:11
eburcat joined23:12
robarelli left23:13
evildmp left23:14
ropav left23:14
evildmp joined23:14
evildmp left23:14
tobiasvl miceiken: you don't have to do anything, no. what do you mean? the changes will be staged but not commited.23:15
evildmp joined23:15
tobiasvl jfcaron: !sync23:15
gitinfo jfcaron: [!fork_sync] You can read a nice guide on how to update your fork with the upstream repository here: https://help.github.com/articles/syncing-a-fork23:15
eletuchy left23:15
miceiken how do i "unstage" them?23:15
jfcaron When I did "git clone", that's not the same as a fork, is it?23:15
tobiasvl jfcaron: or if you mean you just want to pull from origin, just pull. the changes from the upstream will be fast forward merged (unless there's a conflict)23:16
killtheliterate left23:16
tobiasvl jfcaron: a "fork" is a #github concept. but no. a clone is not a github fork.23:16
Hello_ left23:16
tobiasvl it can be considered a fork of the code, of course. git is distributed. your clone can diverge from the upstream and thus become a true fork of the source23:16
miceiken: !unstage23:17
gitinfo miceiken: To unstage a file from the index(in other words, to undo an accidental `git add foo/bar.txt`), use: git reset -- foo/bar.txt23:17
miceiken thanks23:17
tristanp left23:18
imkmf left23:18
dgpalmer trying to use the techniques in here….http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/23:19
nonmadden left23:19
dgpalmer but i am getting this error when i try to update my subproject23:19
tangle001 $ git subtree pull --prefix docroot/sites/all/modules/custom/iga_album_release/ igaalbumrelease master --squash23:19
From https://bitbucket.org/interscoperecords/iga_album_release23:19
* branch master -> FETCH_HEAD23:19
fatal: entry not found in tree 2d6be611a194c4a01389c35ce2248ea5b054b3f623:19
any ideas?23:19
EminenceHC joined23:19
Sivil left23:21
ropav joined23:21
refried_ left23:22
madewokherd joined23:22
jenni_naiaretti joined23:23
logix812 left23:24
EminenceHC left23:24
refried_ joined23:25
moritzs joined23:27
danemacmillan left23:28
ropav left23:28
ferreum_` joined23:28
pwnz0r joined23:28
kukks joined23:29
brandonw joined23:30
ferreum` left23:30
ropav joined23:31
xSmurf left23:32
ferreum_` left23:33
pwnz0r left23:34
mizu_no_oto left23:34
jottr left23:35
HanClinto__ left23:35
ropav left23:36
gitinfo set mode: +v23:37
ropav joined23:37
ncthom91 hi all. Can anyone explain to me *why* git's hash algorithm is this: http://stackoverflow.com/a/552725?23:37
jenni_naiaretti left23:37
jgardella left23:37
ncthom91 particularly, why "blob" and the filesize?23:37
and the null byte?23:37
jottr joined23:37
ropav left23:37
ropav joined23:37
dccc joined23:38
afhammad left23:38
Dougie187 left23:39
jrnieder ncthom91: why not? ;-)23:39
ncthom91 jrnieder does it decrease the chance of collision at all?23:40
not that that chance is very high to begin with...23:40
thesquib joined23:40
ropav left23:40
tmcmahon joined23:40
brandonw left23:41
brandonw joined23:41
eletuchy joined23:42
ErKa left23:42
ropav joined23:43
nfk left23:44
magic_ joined23:45
ropav left23:45
tincan left23:46
Baluse left23:46
ferreum_` joined23:47
anaran left23:47
zumba_addict left23:47
zumba_addict joined23:48
ropav joined23:48
cablop left23:48
btanaka left23:48
Baluse joined23:49
nettoweb left23:51
Mitchbones joined23:51
ianbrandt left23:51
ferreum_` left23:52
ropav left23:52
ropav joined23:54
kukks left23:54
NfNitLoop joined23:54
Neozonz|Disc joined23:55
amikiri joined23:55
NfNitLoop Do I remember correctly that there's some git command you should (periodically?) run to optimize your git repo for serving via HTTP? I'm googling but not finding anything. Wondering if I'm losing my mind. :p23:56
Quevin left23:58
ropav left23:59

Logs Search ←Prev date Next date→ Channels Documentation