IRCloggy #git 2017-02-23

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.

2017-02-23

gigq left00:00
cqi joined00:00
jagob left00:01
cqi left00:01
Neobenedict left00:01
cqi joined00:02
thebope left00:02
humboldt joined00:03
peacememories joined00:03
gugah joined00:04
ash_workz joined00:04
matoro left00:06
humboldt left00:06
humboldt joined00:07
elsevero is there a solution for this: https://gist.github.com/alexszilagyi/9362ab6bcc54d536ec8afcd823353848 ?00:07
whaley joined00:07
gigq joined00:08
zartu left00:08
davidfetter_ge left00:09
elsevero StrongBit: you connect it via its IP (if its local) or hostname which you’ve choosed when you have installed it00:09
StrongBit: on what Operating System have you’ve installed it ?00:10
ESphynx left00:10
Cthalupa left00:11
GT4066 joined00:11
m0viefreak left00:11
m0viefreak joined00:11
intellix left00:12
ShapeShifter499 left00:12
humboldt left00:13
ShapeShifter499 joined00:13
isbotnetcool joined00:13
NwS left00:15
Rodya_ left00:15
NwS joined00:16
tang^_ joined00:17
humboldt joined00:18
Gsham joined00:18
suy joined00:18
KnightsOfNi left00:19
tang^ left00:19
cjbrambo left00:19
KnightsOfNi joined00:19
gopar left00:20
bvcosta joined00:20
cjbrambo joined00:20
tang^_ left00:20
Rodya_ joined00:21
humboldt left00:22
pur3eval joined00:22
LiENUS left00:23
Rodya_ left00:24
matoro joined00:24
m0viefreak left00:26
shinnya joined00:26
pur3eval left00:26
ResidentBiscuit joined00:29
safe left00:29
oaao joined00:30
svara1 left00:30
retroj joined00:30
humboldt joined00:31
lurkashf1ake joined00:32
lurkashf1ake does having a git make sens for two person configuring and installing package in a server00:33
ResidentBiscuit left00:33
rudi_s lurkashf1ake: I use git for /etc on my servers with etckeeper. Should work for two persons too ;-)00:34
lurkashf1ake I am noob to git and realy want to start having different version and getting stuff portable and well commented between user in a readable workflow00:35
rudi_s And a few other repos to document stuff when there are multiple admins so everybody knows how it works.00:35
lurkashf1ake different version of files we edit00:35
oh00:36
hahuang61 left00:36
LosPup left00:36
rudi_s lurkashf1ake: The git used with etckeeper is only stored on a single host and normally not shared between multiple hosts.00:36
lurkashf1ake so if I make a git of /etc/httpd, where will it save the other files. Do I choose?00:37
GT4066 left00:37
xissburg left00:37
rudi_s If you want to do that, I'd recommend using a configuration managment software like ansible, salt, etc. to track the config of the servers and deploy it. YOu can then store the config in git.00:37
lurkashf1ake: Git stores its data in .git in the root of the repository. You can synchronize that over multiple hosts by using remotes.00:38
!progit00:38
gitinfo [!book] There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable00:38
diego1 joined00:38
ResidentBiscuit joined00:39
diego1dviola_00:39
humboldt left00:39
xissburg joined00:39
ResidentBiscuit left00:41
joeco joined00:42
isbotnetcool left00:42
howdoi left00:43
hahuang65 left00:44
marenz joined00:44
matoro left00:45
Levex joined00:45
peacememories left00:46
MattMaker joined00:47
pks joined00:47
Rodya_ joined00:47
StrongBit left00:48
venmx joined00:49
thebope joined00:51
rebrec left00:51
MattMaker left00:52
Atm0spher1c left00:52
svm_invictvs left00:52
mischat joined00:53
humboldt joined00:55
thebope left00:55
rivarun left00:57
nickabbey joined00:57
nickabbey left00:57
humboldt left00:57
rivarun joined00:58
Levex left00:58
chipotle joined00:59
mischat left00:59
rebrec joined01:01
Tobbi left01:02
cdg left01:03
Levex joined01:03
LeBlaaanc left01:04
pur3eval joined01:05
t-mart_ joined01:06
nowhereman joined01:06
vishal left01:06
xaviergmail_ left01:07
clemf left01:08
xaviergmail_ joined01:08
t-mart left01:09
t-mart_ left01:11
dreiss left01:12
thebope joined01:13
oskarkv left01:13
jon-mac joined01:13
cjbrambo left01:13
cjbrambo joined01:15
shinnya left01:15
joshszep left01:16
tvw left01:16
acidjnk left01:21
kasual left01:24
venmx left01:24
whaley left01:26
Derperperd joined01:27
SwiftMatt left01:27
kfoonamalik left01:30
Cthalupa joined01:30
ToBeCloud left01:31
Gsham left01:32
matoro joined01:32
SwiftMatt joined01:32
SwiftMatt left01:35
chardan joined01:38
crayon left01:41
chardan left01:42
chardan joined01:44
Raed left01:47
MattMaker joined01:48
brent__ left01:48
tjbp left01:48
tjbp joined01:49
publio left01:49
MattMaker left01:52
moei left01:52
moei joined01:53
chachasmooth left01:55
DARSCODE joined01:55
Sasazuka left01:55
DARSCODE left01:55
chachasmooth joined01:56
a_thakur joined01:57
bvcosta left01:58
elsevero left01:59
lurkashf1ake left01:59
cqi left01:59
prsn left01:59
_UniFreak joined01:59
svm_invictvs joined01:59
pur3eval left02:01
a_thakur left02:03
Sasazuka joined02:04
zzz joined02:04
raijin joined02:04
Cthalupa left02:06
a_thakur joined02:06
Derperperd left02:07
matoro left02:08
Cthalupa joined02:09
SwiftMatt joined02:09
peacememories joined02:09
MarioBranco left02:10
a_thakur left02:11
peacememories left02:13
madewokherd left02:13
johnny56_ left02:13
zzz left02:13
MarioBranco joined02:14
dreiss joined02:14
Raed joined02:15
SheldonCooper ok, I have a problem02:15
glspi joined02:16
SheldonCooper I have a small git submodule specifically for some test data used in unit testing02:16
running locally is not a problem02:16
but some custom install/check system we use copies everything to a /tmp directory02:17
johnny56_ joined02:17
SheldonCooper there, there is no git config --global user.name user.email02:17
is there a way to tell it to use a local git config in the submodule?02:18
which is only used for the test suite02:18
so that it doesn't matter if I run them from my development checkout or they are run from some other system/installer02:19
Vampire0_ joined02:20
d0nn1e left02:21
d0nn1e joined02:23
cdg joined02:23
CheckDavid left02:24
rrios joined02:24
rrios left02:24
rrios joined02:24
Vampire0 left02:24
svm_invictvs left02:24
r_rios left02:25
dviola left02:28
cagedwisdom joined02:29
dviola joined02:29
Anja left02:30
SheldonCooper hmm GIT_CONFIG environment variable may be a viable option02:31
Sasazuka left02:32
Anja joined02:33
jstimm joined02:33
a_thakur joined02:33
LiftLeft left02:34
gelei007 joined02:34
madewokherd joined02:35
blackwind_123 left02:36
duderonomy left02:37
pbrewczynski left02:37
marenz left02:37
jstimm left02:37
matoro joined02:38
Anja left02:38
gelei007 left02:39
gelei007 joined02:39
Sasazuka joined02:40
ResidentBiscuit joined02:41
a_thakur left02:41
xissburg left02:42
cdg left02:43
wcpan left02:43
d^sh left02:43
Wulf4 joined02:45
d^sh joined02:45
ResidentBiscuit left02:46
amdi_ joined02:46
LiftLeft joined02:46
Ntemis left02:47
Wulf left02:48
Wulf4Wulf02:48
MattMaker joined02:48
Sasazuka left02:49
xissburg joined02:49
DarkPsydeLord joined02:49
wcpan joined02:49
matoro left02:50
clemf joined02:52
Rodya_ left02:52
ojdo left02:52
MattMaker left02:53
hasc left02:53
Rodya_ joined02:54
chardan left02:55
raijin left02:55
pks left02:56
mischat joined02:56
JanC_ joined02:56
humboldt joined02:57
JanCGuest3151602:57
Guest31516 left02:57
JanC_JanC02:57
mehola joined02:58
raijin joined02:58
pks joined02:58
SwiftMatt left02:59
humboldt left03:01
mischat left03:01
lanking joined03:02
pur3eval joined03:02
rkazak left03:02
mehola left03:02
humboldt joined03:02
jameser joined03:03
ojdo joined03:03
Vortex34 left03:04
Rodya_ left03:04
mikecmpbll left03:05
humboldt left03:06
pur3eval left03:06
justan0theruser joined03:07
shgysk8zer0_ left03:08
humboldt joined03:08
fstd_ joined03:08
fstd left03:08
dviola_ left03:08
fstd_fstd03:08
ffilozov joined03:08
justanotheruser left03:09
Rodya_ joined03:09
rivarun left03:10
rivarun joined03:10
humboldt left03:12
cdg joined03:12
gopar joined03:12
hexagoxel left03:13
gopar left03:14
Levex left03:14
hexagoxel joined03:14
t-mart joined03:16
aavrug joined03:17
Vortex34 joined03:17
aavrug left03:18
aavrug joined03:18
cdg left03:18
humboldt joined03:19
cdg joined03:19
lowercas_ left03:20
lowercaseman joined03:20
leeN left03:21
msisay joined03:24
Rodya_ left03:24
microbuild3 joined03:24
jameser left03:24
cqi joined03:24
matoro joined03:25
microbuild3 left03:25
thebope left03:26
exitcode1 left03:26
xall joined03:27
duderonomy joined03:29
gelei007 left03:29
cdg left03:29
jameser joined03:29
cdg joined03:30
Sample left03:31
humboldt left03:36
MarioBranco left03:40
MarioBranco joined03:41
Ryanar joined03:42
chachasmooth left03:42
jimi_ left03:43
lb1c left03:44
chachasmooth joined03:44
lb1c joined03:44
Ryanar left03:45
McKraken_zzzzzMcKraken03:46
xall_ joined03:46
Ryanar joined03:47
humboldt joined03:47
xall left03:48
govg left03:49
MattMaker joined03:49
sunri5e left03:50
brent__ joined03:51
sunri5e joined03:51
Rodya_ joined03:52
humboldt left03:53
MattMaker left03:54
exitcode1 joined03:54
dreiss left03:56
xall_ left03:57
xall joined03:57
mischat joined03:57
mehola joined03:59
humboldt joined04:00
SwiftMatt joined04:00
gugah left04:00
mischat left04:02
humboldt left04:02
pur3eval joined04:02
roelmonnens joined04:03
Goplat joined04:03
mehola left04:04
clemf_ joined04:04
SwiftMatt left04:04
McKrakenMcKraken_zzzzz04:06
hahuang65 joined04:06
clemf left04:07
roelmonnens left04:07
pur3eval left04:07
Anja joined04:11
msisay left04:11
brent__ left04:12
brent__ joined04:13
brent__ left04:13
Gustavo6046 left04:14
fatalhalt left04:14
thebope joined04:15
dreiss joined04:17
DolphinDream left04:17
hexagoxel left04:20
thebope left04:20
hexagoxel joined04:21
Atm0spher1c joined04:21
chipotle left04:22
chipotle joined04:24
a_thakur joined04:24
exitcode1 left04:27
aidalgol left04:32
rchavik joined04:33
SwiftMatt joined04:38
govg joined04:41
ThomasTang joined04:43
chipotle left04:44
a_thakur left04:44
glspi left04:44
rj1 joined04:45
ResidentBiscuit joined04:46
raijin left04:46
a_thakur joined04:46
svm_invictvs joined04:47
jstimm joined04:47
Ryanar left04:47
MattMaker joined04:50
ResidentBiscuit left04:51
jstimm left04:51
ahr3n left04:51
acln left04:55
Cabanoss- joined04:55
MattMaker left04:55
acln joined04:55
jeffreylevesque left04:55
jeffreylevesque joined04:57
ayogi joined04:58
mischat joined04:58
ozmage joined04:58
Cabanossi left04:59
Cabanoss-Cabanossi04:59
dermoth left05:00
menip joined05:00
dermoth joined05:00
mischat left05:03
pur3eval joined05:03
ac joined05:05
acGuest1175705:05
Guest11757 left05:06
pur3eval left05:07
ozmage left05:09
chipotle joined05:10
thebope joined05:10
thebope left05:14
raijin joined05:14
ozmage joined05:15
cdg_ joined05:16
a_thakur left05:16
xall left05:17
a_thakur joined05:17
chipotle left05:17
cdg left05:19
xissburg left05:19
xissburg joined05:20
a_thakur left05:21
durham left05:22
ozmage left05:23
Xenophon1 joined05:27
durham joined05:27
jimi_ joined05:28
ozmage joined05:28
XenophonF left05:29
safe joined05:29
DarkPsydeLord left05:30
ash_workz left05:31
bill99 left05:31
ash_workz joined05:32
MarioBranco left05:33
elementalest joined05:34
hhee joined05:35
Rodya_ left05:35
Rodya_ joined05:36
noteness left05:38
a_thakur joined05:38
noteness joined05:39
rafalcpp left05:39
bocaneri joined05:39
xaviergmail_ left05:39
xaviergmail_ joined05:40
elsevero joined05:40
irqq left05:40
Rodya_ left05:40
MarioBranco joined05:41
ShapeShifter499 left05:45
l4v2 left05:45
ShapeShifter499 joined05:45
kexmex joined05:47
quite joined05:48
quite left05:48
quite joined05:48
ckruczek joined05:48
ThomasTang left05:48
Tatou joined05:48
Tatou Are there any issues with using the git-svn bridge?05:49
gitinfo set mode: +v05:50
ckruczek jop, svn05:50
Tatou What.05:50
MattMaker joined05:51
pur3eval joined05:53
_ikke_ Tatou: #git != #github05:53
Or do you mean just using plain git-svn?05:53
xall joined05:54
netj left05:55
netj joined05:55
MattMaker left05:56
peterbecich joined05:57
mischat joined05:59
ozmage left05:59
DaveTaboola joined06:00
mehola joined06:00
MarioBranco left06:01
ffilozov left06:02
MarioBranco joined06:02
gelei007 joined06:02
mischat left06:03
thebope joined06:04
navidr joined06:04
mehola left06:05
sbulage joined06:05
dminuoso left06:06
dminuoso joined06:06
cyphase left06:07
peterbecich left06:07
thebope left06:08
peterbecich joined06:09
xissburg left06:10
rj1 left06:10
durham left06:10
cyphase joined06:12
rj1 joined06:13
dec0n joined06:13
Sample joined06:14
bill99 joined06:14
MarioBranco left06:14
overlord_tm joined06:15
xall left06:16
xissburg joined06:16
bill99 left06:17
MrC left06:18
MasterNayru left06:18
pur3eval left06:20
murph joined06:20
murphGuest2940306:20
venmx joined06:21
gelei007 left06:24
venmx left06:26
svm_invictvs left06:28
DaveTaboola left06:30
xall joined06:32
qt-x joined06:32
madewokherd left06:33
MrC joined06:37
expl015s_ joined06:37
expl015s_ left06:37
a_thakur left06:41
ahr3n joined06:41
safe left06:42
zeroed joined06:43
ResidentBiscuit joined06:47
circ-user-3LZMN joined06:48
fletom left06:48
mehola joined06:48
fletom joined06:49
Raging_Hog joined06:50
zeroed left06:51
ResidentBiscuit left06:52
MattMaker joined06:52
zefferno joined06:53
a_thakur joined06:53
a_thakur left06:55
a_thakur joined06:56
MattMaker left06:56
zeroed joined06:57
Darren_ joined06:57
thebope joined06:58
xissburg left06:59
a_thakur left06:59
mischat joined06:59
xissburg joined07:00
ahr3n left07:00
pR0Ps left07:02
thebope left07:02
ISmithers left07:03
Junior joined07:04
sarri left07:04
mischat left07:04
a_thakur joined07:07
rlb joined07:07
pR0Ps joined07:08
circ-user-3LZMN left07:09
peterbecich left07:10
a_thakur left07:11
rlb Is there some recommended way to have all of my commit invocations verify "diff --check" by default before comitting (in addition to anything else a given repository might do in its own pre-commit hook)?07:11
gelei007 joined07:11
_ikke_ rlb: You'd add that to the pre-commit hook too07:12
rlb Thanks, though I don't want to need to modify the pre-commit hook (if any) for every repo I work with.07:12
hhee left07:13
rlb Worst case, I can just create my own commit subcommand, but I thought I'd see if there was something preferable.07:13
subcommand(wrapper)07:13
_ikke_ rlb: You can have a pre-commit hook wrapper that calls multiple other checks07:14
rlb You mean a "global" one that runs my check and then looks for the per-repo hook (if any) and runs that?07:14
I suppose as long as I can find the "current repo"'s hook dir from within my global hook, that might work.07:15
Anja left07:15
MattMaker joined07:16
scarabx joined07:17
scarabx left07:17
rlb Suppose I'll also have to see if hooksPath is all-or-nothing, or if it shadows. Ideally, I don't want to have to keep a complete set (as the set evolves) of mostly pass-through hooks, just to wrap pre-commit.07:17
Hmm, the docs seem to imply all-or-nothing.07:19
tripton joined07:20
Vampire0_Vampire007:20
roelmonnens joined07:21
MrWoohoo left07:21
thiago joined07:21
t-mart left07:23
_UniFreak_ joined07:24
JeroenT joined07:24
JeroenT left07:26
_UniFreak left07:26
JeroenT joined07:26
a_thakur joined07:27
Anja joined07:27
roelmonnens left07:27
redhedded1 joined07:28
Anja left07:28
roelmonnens joined07:28
gelei007 left07:28
Anja joined07:28
dreiss left07:29
Vampire0 rlb, you are aware that a repo you clone never had any hooks, until you add them manually, aren't you. hooks are not part of the clone process07:29
pur3eval joined07:30
nidr0x left07:31
Atm0spher1c left07:33
oaao left07:34
dave0x6d left07:35
oaao joined07:35
pur3eval left07:35
a_thakur left07:35
menip left07:38
fewspider joined07:38
a_thakur joined07:39
King_Hual joined07:42
ShapeShifter499 left07:44
jnavila joined07:45
sarri joined07:45
sarri left07:45
sarri joined07:45
mrkake left07:46
Andrew_K joined07:48
troulouliou_div2 joined07:48
a_thakur left07:48
boombatower left07:49
a_thakur joined07:52
thebope joined07:52
mrkake joined07:52
bernardio joined07:52
overlord_tm left07:53
overlord_tm joined07:54
bill99 joined07:54
s1scha joined07:55
a_thakur left07:56
gelei007 joined07:56
MattMaker left07:56
miczac joined07:56
ozmage joined07:56
thebope left07:56
gitinfo set mode: +v07:56
jagob joined07:59
mischat joined08:00
miczac left08:01
elsevero left08:03
tripton left08:03
zeroed left08:04
zeroed joined08:04
Anja left08:05
kexmex left08:05
mischat left08:06
nothingnew joined08:07
peterbecich joined08:07
roelmonn_ joined08:08
rlb left08:09
miczac joined08:09
gitinfo set mode: +v08:09
mischat joined08:10
roelmonnens left08:11
a_thakur joined08:12
mischat left08:12
a_thakur left08:12
nothingnew left08:13
a_thakur joined08:13
zulutango joined08:14
ozmage left08:15
tristanp left08:15
eneasvva left08:16
TomyWork joined08:16
Tobbi joined08:16
Alienpruts joined08:18
zeroed left08:18
Anja joined08:18
elect joined08:18
xaviergmail_ left08:19
zeroed joined08:19
zeroed left08:19
zeroed joined08:19
User458764 joined08:20
rlb joined08:20
xaviergmail_ joined08:20
miczac left08:20
venmx joined08:22
miczac joined08:22
vuoto joined08:23
gitinfo set mode: +v08:23
dedicated_ joined08:25
theoceaniscool joined08:26
venmx left08:26
dedicated left08:27
orbyt_ left08:28
raijin left08:29
donnib joined08:30
Tobbi left08:30
elsevero joined08:30
donnib do i understand correct that in a large repository not only will cloning be slow checkout will also since the pack files are large to unpack ?08:30
Anja left08:31
a_thakur left08:31
cqi left08:33
a_thakur joined08:34
a_thakur left08:34
dminuoso donnib: I have not experienced slow checkouts in large repositories before08:36
govg left08:37
chachasmooth left08:37
Darren_ left08:37
chachasmooth joined08:38
a_thakur joined08:39
chachasmooth_ joined08:39
a_thakur left08:40
a_thakur joined08:41
dvaske joined08:41
chachasm- joined08:42
dvaske_ joined08:42
Anja joined08:43
chachasmooth left08:44
sasamil joined08:44
chachasmooth_ left08:44
Balliad joined08:45
kexmex joined08:45
thebope joined08:46
dvaske left08:46
mikecmpbll joined08:47
chachasm- left08:47
chachasmooth joined08:48
donnib dminuoso: so it's only the Clone who is impacted by big repo ?08:48
kurkale6ka joined08:49
_ikke_ checkouts can take a long time too08:49
but not necessarily due to the packfile format08:49
Tobbi joined08:50
_ikke_ Usually the slowness is in writing the individual files to disk08:50
thebope left08:50
a_thakur left08:51
kexmex left08:52
kyan left08:52
diogenese left08:53
chachasmooth left08:53
tvw joined08:54
ozmage joined08:54
a_thakur joined08:56
MattMaker joined08:57
chachasmooth joined08:57
hhee joined08:58
p4trix joined09:01
p4trix left09:01
MattMaker left09:02
bongjovi joined09:02
dersand joined09:03
ResidentBiscuit joined09:04
fortin joined09:04
govg joined09:05
bernardio left09:07
fortin hello folks. I'm trying to compile 2.11.1 statically linked using this parameters: CFLAGS="${CFLAGS} -static-libgcc" NO_OPENSSL=1 NO_CURL=1. Build succeeds but if I inspect the binary with "file" tool it says it's dynamically linked: "dynamically linked (uses shared libs)". Following suggestions from http://stackoverflow.com/questions/11570188/how-to-build-git-with-static-linking09:07
ResidentBiscuit left09:08
bernardio joined09:08
ckruczek left09:08
clemf_ left09:10
dminuoso _ikke_: but usually a checkout would only be slow if there's huge differences right?09:10
diogenese joined09:12
gelei007 left09:12
miczac left09:12
a_thakur left09:14
zeroed left09:14
brent__ joined09:14
ozmage left09:15
kexmex joined09:17
gtristan joined09:17
marcogmonteiro joined09:18
gtristan How can I get the diff of a specific file between 2 revisions ?09:18
git diff sha1...sha2 file.txt09:18
seems not to be correct09:18
nor is git diff file.txt sha1...sha209:18
brent__ left09:19
grayjoc joined09:19
_ikke_ gtristan: without the dots09:19
git diff sha1 sha2 file09:19
clmsy joined09:20
afuentes joined09:20
redeemed joined09:20
Tobbi left09:20
a_thakur joined09:21
gtristan _ikke_, Ah thanks !09:21
Oh09:22
fatal: ambiguous argument 'file.txt': unknown revision or path not in the working tree.09:22
_ikke_, can I do it in a bare repo ?09:22
MasterNayru joined09:22
zeroed joined09:22
_ikke_ should be possible09:22
miczac joined09:22
_ikke_ try adding --09:22
gtristan ah09:22
_ikke_ git diff sha1 sha2 -- file09:22
gtristan Just did that :)09:22
Indeed09:22
that worked09:23
gitinfo set mode: +v09:23
_ikke_ alright09:23
gtristan thanks again :)09:23
kexmex left09:24
snoo joined09:24
Tobbi joined09:24
snoo Hi, what is the config which determines that "git checkout foo" will automatically create a local branch "foo" tracking "origin/foo" if it doesn't already exist?09:24
_ikke_ snoo: not sure if it's a config option09:24
snoo Seems my Jenkins server isn't having this behaviour, and not sure how to enable it, since it's default in git on my desktop.09:24
canton7 snoo, no config: it's a hard-coded bit of behaviour09:24
_ikke_ snoo: If you have multiple remotes with the same branches, it won't work09:25
snoo well on this one machine "git checkout master" gives an error " pathspec 'master' did not match any file(s) known to git." even though remotes/origin/master is fetched09:25
ah09:25
a_thakur left09:25
_ikke_ snoo: i would not rely on this feature anyway in this case09:25
snoo: it's better to be explicit09:26
a_thakur joined09:26
snoo I don't think it's my code, it's Jenkins behaviour09:26
canton7 from the man page, "09:26
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to $ git checkout -b <branch> --track <remote>/<branch>"09:26
_ikke_ snoo: Did you change the default branch on the remote?09:26
snoo: I think jenkins assumes master exists somehow09:26
canton7 but yeah, the only reason that bit of behaviour exists is to be a bit nicer to new users, I think. 'git checkout -b foo origin/foo' is going to be better09:26
snoo no, the issue is that jenkins is fetching multiple remotes which have "master"09:27
I will hack it to explicitly check out remote_name/branch_name09:27
_ikke_ snoo: why doesn't master exist in the first place?09:27
aard_ joined09:27
a_thakur left09:27
snoo not sure. jenkins sets up a repo and then our job adds the remote09:28
our job doesn't do git init, so it must be baked into jenkins09:28
a_thakur joined09:29
_ikke_ snoo: I would expect jenkins to do a clone09:32
which would also create the default branch (which by default is master)09:32
snoo I'll look into it, I understand the behaviour now anyway so thanks.09:32
SwiftMatt left09:33
MrWoohoo joined09:33
Goplat left09:34
Tobbi left09:34
raijin joined09:34
cdg_ left09:35
pks left09:35
lanking left09:36
xall left09:36
xall_ joined09:37
acidjnk22 joined09:38
fortin left09:39
mischat joined09:40
thebope joined09:40
jimi_ left09:42
jimi_ joined09:43
Tobbi joined09:44
thebope left09:44
codebam how can I configure a webhook to auto update my local repo every time my friend pushes by adding a git hook on his repo?09:47
seni1 joined09:47
codebam ie he pushes, sends a put to me, code is updated, server is restarted09:47
cqi joined09:48
Blkt left09:48
chll_ joined09:49
Blkt joined09:49
xall_ left09:52
Tobbi left09:54
nowhereman left09:55
rafalcpp joined09:56
babilen left09:57
Levex joined09:58
MattMaker joined09:58
irqq joined10:02
khfeng left10:02
Tobbi joined10:02
MattMaker left10:02
babilen joined10:03
Levex left10:05
khfeng joined10:05
cqi left10:05
Levex joined10:05
metalraiden34 joined10:05
Dumblez0r joined10:06
miczac left10:08
snoorory10:08
nothingnew joined10:09
Tobbi left10:11
mrkake left10:11
Guest55219 left10:11
valkyr2e joined10:11
Tobbi joined10:12
acetakwas joined10:13
mrtn joined10:16
mrtn left10:17
LiftLeft left10:17
ferr1 joined10:18
Levex left10:18
mrkake joined10:20
joeco_ joined10:20
User458764 left10:21
venmx joined10:22
chachasmooth left10:23
joeco left10:23
grayjoc left10:24
Tobbi left10:24
marcogmonteiro left10:24
grayjoc joined10:24
oaao left10:25
oaao joined10:25
chachasmooth joined10:25
marcogmonteiro joined10:26
StrongBit joined10:27
a_thakur left10:27
fahadash left10:27
venmx left10:28
nettoweb joined10:28
a_thakur joined10:29
miczac joined10:30
gitinfo set mode: +v10:30
RxMcDonald joined10:31
intellix joined10:31
Snugglebash joined10:31
Snugglebash left10:31
Snugglebash joined10:32
Snugglebash left10:32
Tobbi joined10:32
User458764 joined10:32
nd joined10:33
dsdeiz left10:33
thebope joined10:34
djb-irc left10:35
fewspider left10:36
nd_ left10:36
mehola left10:37
pks joined10:38
thebope left10:38
mindfart left10:41
djb-irc joined10:42
davimore left10:43
metachr0n left10:44
vuoto left10:44
metalraiden34 left10:44
metachr0n joined10:45
oskarkv joined10:46
jimi_ left10:47
bvcosta joined10:47
nettoweb1 joined10:48
nettoweb left10:48
qt-x left10:48
ahr3n joined10:48
rgb-one joined10:50
rgb-one Hey10:50
jameser left10:51
r__rios joined10:52
qt-x joined10:52
bernardio left10:53
r_rios joined10:54
r_rios left10:54
r_rios joined10:54
davimore joined10:54
rrios left10:55
nothingnew left10:55
gitinfo rgb-one: [!welcome] Welcome to #git, a place full of helpful gits. If you have a question, feel free to just go ahead and ask—somebody should answer shortly. For more info on this channel, see http://jk.gs/git/ Take backups (type !backup to learn how) before taking advice.10:55
rgb-one Whenever I change a branch one specific file has a CRLF instead of LF and it shows up as modified10:55
why is this?10:55
gtristan So I have an automated task which will be checking out repos, and one of the steps is to make a diff between two commits for a given file (as I was asking about above)10:56
bernardio joined10:56
gtristan My original thinking, was; I will do nothing if there is no diff output10:56
r__rios left10:56
roelmonn_ left10:56
gtristan But, now I want to parse the diff output because, it's going to be common that a one line change occurs which I want to ignore10:56
+ Version: abc10:57
joeco__ joined10:57
gtristan - Version: def10:57
Like that10:57
leeN joined10:57
gtristan So I can get to parsing, but; is there a way I can tell `git diff` to give me more brief output ?10:57
theoceaniscool left10:57
gtristan So that I only have the 2 lines, if possible10:57
or at least not the `diff --git bla bla` line and not those ---a/path ---b/path lines10:58
What would be the most practical git diff invocation for this ?10:58
MattMaker joined10:59
miczac left10:59
joeco_ left11:00
c0c0 joined11:01
tcorneli joined11:02
MattMaker left11:03
rnsanchez joined11:04
redhedded1 left11:05
StrongBit Hello. I am using GOGs. how can I backup my projects?11:05
selckin good old games?11:05
cdg joined11:06
marcogmonteiro left11:06
Xenophon1 left11:07
Gustavo6046 joined11:07
gtristan fwiw, git diff --unified=0 gets me much closer to something useful :)11:07
think that's good enough for me11:07
ahr3n left11:09
cdg left11:10
theoceaniscool joined11:10
kimorigadommoy joined11:11
User458764 left11:13
theoceaniscool left11:13
XenophonF joined11:13
ThomasLocke joined11:14
bvcosta left11:16
Sample left11:17
tristanp joined11:17
marcogmonteiro joined11:18
gitinfo set mode: +v11:19
kimorigadommoy Hey guys! Me and my colleagues are having an argument about wether ‘cache’ in git is used as ‘cache’ (storing data, for easier access) or not. Can please someone give us a clean answer like: Yes or No! :) Thanks in advance!11:19
osse cache? what cache?11:20
selckin as in rm --cached ?11:20
kimorigadommoy yes11:20
ResidentBiscuit joined11:20
osse the index used to be called the cache11:20
selckin so not really a 'cache'11:21
kimorigadommoy Thas is "No" right ?11:21
selckin yes11:21
flaviodesousa joined11:22
enckse left11:22
storrgie left11:22
rudi_s And now it's called staging area.11:22
tristanp left11:23
acetakwas left11:23
enckse joined11:23
storrgie joined11:25
ResidentBiscuit left11:25
a_thakur left11:26
thebope joined11:28
marenz joined11:29
a_thakur joined11:29
okjdpi joined11:30
_ikke_ Not really11:30
It's still called the index11:30
kimorigadommoy why index is used?11:30
selckin because it was better then cache11:30
kimorigadommoy what is index in this context ?11:31
selckin the staging area11:31
_ikke_ Index of file blobs11:31
kimorigadommoy no, why is it used*11:31
the question is... for easier access, or just to have an understanding of changes?11:31
osse kimorigadommoy: man gitglossary11:32
gitinfo kimorigadommoy: the gitglossary manpage is available at http://jk.gs/gitglossary.html11:32
_ikke_ kimorigadommoy: git ls-files --debug gives you a little bit of insight of what it contains (but it's not complete)\11:32
selckin you stage the changes you want to commit (which files, or which hunks from files), then you can review then and commit11:32
thebope left11:32
_ikke_ But the index contains a complete snapshot11:32
"A collection of files with stat information, whose contents are stored as objects. The index is a stored version of your working tree."11:33
Anja left11:33
_ikke_ Note that .git/index does not contain the contents itself, just a reference to the blobs11:33
sunri5e left11:33
acetakwas joined11:34
User458764 joined11:34
sunri5e joined11:34
Tobbi left11:35
kimorigadommoy if git was a daemon :D it would save those reference in memory? :D11:35
dcpc007 joined11:35
_ikke_ kimorigadommoy: Some things, but it would still need to store things on disk11:36
You don't want your staged changes to be gone when you restart the daemon11:36
DBag joined11:36
cagedwisdom left11:36
DBag left11:37
kimorigadommoy makes sense, but the main question still exists, is it for speed purposes, or it is a logic thing11:37
_ikke_ combination11:37
the stat info is for speed11:37
askb left11:38
_ikke_ The reference snapshot of the working tree is for logical reasons (though, it's also optimized to easily create tree objects from it)11:38
dgonzo joined11:38
tcorneli left11:39
_ikke_ If you delete the index, you lose state (the staged changes)11:40
without the index, certain operations would take much longer (git status for example)11:40
Torrone joined11:41
bvcosta joined11:41
thadtheman joined11:43
kimorigadommoy _ikke_ thank you for your response!11:43
it was what needed11:43
kimorigadommoy left11:43
thadtheman Can you clone multiple repos in one command? git clone repo1 repo2 repo3 ?11:43
_ikke_ no11:44
whaley joined11:44
_UniFreak_ left11:44
thadtheman Thank you.11:44
bremner !myrepos11:44
dedicated joined11:45
nettoweb joined11:45
nettoweb1 left11:46
Anja joined11:46
dedicated_ left11:48
Torrone Hello, this is git-related, but not strictly a git question: I work in a company, I am one of the employees who work from home, I'm on the main project and I'm practically doing it all by myself, I can handle doing everything but sometimes I really would like to have someone else working with me, at least to discuss decisions. There's this guy who works at the office, he's nice and he's supposed to be good at javascript stuff, also sup11:48
posed to work on the project at some point. When I told him he just needed to git clone he said he couldn't use git, that's fine to me but it makes me doubt his competence, and makes me worry about having to do everything on my own without having anyone else to know the project ( this one involves payments, it's pretty important..) how should I deal with this?11:48
cdg joined11:48
donnib Torrone: why can he not use Git ?11:49
nettoweb1 joined11:49
nettoweb left11:50
donnib Torrone: and what do you need him for ? Review ? Send the code thru other channels if he is not confident to use git11:50
Torrone I think he's not accustomed to work at the same standards I'm used to11:50
donnib Torrone: unless he starts to code there might be no reason to push him to use your tool just because you need his help11:51
Torrone since I've been hired I've struggled to have competent confrontations11:51
donnib Torrone: well you are asking for help so he must be skilled in some way or ?11:51
Torrone some guys I know for sure that are incompetent, I'm not sure about this one11:51
I'm worried to do all the work by myself, I am up to higher standards but it's the first time I have to deal with sensitive stuff like payments11:52
donnib Torrone: take it up with the manager or the team and agree on a process of work like integrating Git and integrating review as part of the process to ensure that others also knows about others code11:53
rgb-one left11:53
Torrone donnib, I just introduced the joel test t my manager11:54
donnib Torrone: now, i don't know the country you are in and what culture you are up agains but in a west european culture i would take this issue (formulated most likely different) with the team like guys i am new and i works some things which i am not comfortable with, how can i involve you into this11:54
gtristan left11:54
Torrone I'm from western europe11:56
donnib Torrone: it's really is a bad practice in a team to sit with something on your own without sharing it with other especially if it's areas that are new to you,11:56
roelmonnens joined11:57
donnib Torrone: good, talk to the team. you might have a meeting (retrospective) where you can discuss freely and tell the other your opinion in a constructive way without pointing fingers11:57
elsevero_ joined11:58
Tobbi joined11:58
osse FWIW Git is one of those tools it makes sense to use on a team level. Either everyone is in on it, or you use something else.11:58
donnib Torrone: and if you have a competent manager this will be de dealt with, you can suggest to the team to go to use Source Control (i pressume not all do) and choose Git11:58
Torrone: then help team adapt Pull Request aka Reviews, let the team know you want this for the best interest for the company/product and help them11:59
UniFreak joined11:59
MattMaker joined11:59
donnib Torrone: i meet so many teams not knowing they could do better both process wise but also tools/technology because they don't know about them12:00
selckin sounds like its a small company tho12:00
donnib selckin: yeah i have the same feeling12:00
Torrone donnib, yeah, I'm already doing this with the client's IT guy, but I can't always involve him for obvious reasons12:00
selckin those things don't really work in small companies12:00
Levex joined12:01
donnib selckin: what doesn't work in samll companies ?12:01
elsevero left12:01
elsevero_elsevero12:01
bremner having managers?12:01
osse private armies12:01
bremner outsource!12:01
selckin teams and talking to team lead, and setting up reviews12:02
metalraiden34 joined12:02
osse The nice thing about private armies is that they can't hang you for treason if you no longer wish to work for them.12:02
donnib selckin: i see no reason that it wouldn't work12:02
selckin they don't exist12:02
donnib selckin: what doesn't exist ? be precise12:02
oaao left12:02
dviola left12:03
dviola joined12:03
oaao joined12:03
roelmonnens left12:03
roelmonnens joined12:03
xissburg left12:04
Torrone donnib, the process is fairly organized, I already use source control, pull requests ( since I'm working on other people's code ) and I think I have a pretty decent workflow, my problem is I would sometimes need another competent pair of eyes and I'm not sure I can find them in my company, because I've seen other works from my colleagues and they damn sure are not up to the standards and second because I'm the only one in the company w12:04
ho knows the server side language of this particular project12:04
MattMaker left12:04
Andrew_K left12:05
whaley left12:05
selckin having expertise in a differend area as you does not make them incompetent12:07
be careful before everyone hates you12:07
oaao left12:07
oaao joined12:07
marcogmonteiro left12:07
joeco_ joined12:08
donnib I agree with selckin12:08
Torrone selckin, I'm not saying they're incompetent ( well, I've been handed code from one guy and I can tell that he's incompetent at writing css, but appartently it's the only thing he does). I barely know them and it's difficult for me to estimate their competence12:09
joeco__ left12:10
a_thakur left12:11
a_thakur joined12:11
YuGiOhJCJ joined12:12
Torrone all I know is that they're nice people and they're all seniors12:12
xissburg joined12:12
Torrone anyway I'll try and talk to my manager, thanks for the advice12:12
donnib,12:13
donnib Torrone: sure no problem if not revert to my first comment, use them where they have knowledge experience and share your code/whatever you want input on with them in the way THEY feel comfortable12:13
marcogmonteiro joined12:14
raynold left12:14
cyberz joined12:15
robattila256 left12:15
ismithers joined12:16
a_thakur left12:19
psyb0t left12:19
ayogi left12:19
a_thakur joined12:19
explody left12:21
seni1 left12:21
psyb0t joined12:22
thebope joined12:22
zulutango left12:24
StrongBit left12:24
explody joined12:25
whaley joined12:25
mischat_ joined12:25
zeroed left12:27
al-damiri joined12:27
thebope left12:27
mischat left12:28
acetakwas left12:29
donnib osse: i was discussing with someone else earlier on perfomance cost of big repositories and checkout operations, do you know for sure that there is no gain in performance on a checkout operation on a big vs small repo ?12:30
aavrug left12:32
gtristan joined12:32
cyberz left12:35
d1b_d1b12:36
seni1 joined12:37
nettoweb joined12:37
nettoweb1 left12:37
mahakal joined12:38
Masber joined12:38
marcogmonteiro left12:39
levex_ joined12:42
kristofferR left12:42
zeroed joined12:42
Levex left12:43
Torrone left12:44
osse donnib: what do you mean by performance? MB/s of checked out data during the operation?12:45
marcogmonteiro joined12:48
jimi_ joined12:48
gugah joined12:49
ayogi joined12:49
MrMojit0 joined12:51
Tobbi left12:51
xaviergmail_ left12:53
xissburg left12:53
jeffreylevesque left12:53
a_thakur left12:54
xaviergmail_ joined12:54
Ardethian joined12:55
DolphinDream joined12:56
StrongBit joined12:57
xissburg joined12:57
raijin left12:58
amdi_ left12:58
Tobbi joined13:00
MattMaker joined13:00
donnib osse: i am talking about time to checkout13:00
grayjoc left13:00
r_rios left13:00
donnib osse: i mean does it take more time to checkout in a big repo vs small repo13:01
osse i don't see how it couldn't13:01
Seveas repo size matters a bit, but worktree size matters more13:01
r_rios joined13:01
osse ohhh13:01
donnib osse: my theory without knowing the details in git is that the pack file is bigger so file operations are slower13:01
osse "big repo" = more history?13:01
donnib osse: not necessary but big files13:02
Seveas pack files are indexed13:02
qpdb left13:02
selckin can test this quite easy with like the kernel git repo ? time a bunch of checkouts, then blow away .git, make a single commit, and time again?13:02
Seveas so while a big packfile is slower to read, it's not much slower.13:02
osse I don't know13:02
Seveas "amount of files that need to be checked out" (and their size) will be the biggest cotributing factor13:03
donnib so i am thinking that a repo that has let's say 1.5 gb and i clean it (remove some of the big files that was inside git which devs have removed but are stuck) should give me both a clone performance but also checkout but i am not sure13:03
Seveas opening, writing and closing 100 files is a lot slower than reading a packfile index.13:03
hussam left13:04
whaley left13:05
synthroid joined13:05
MattMaker left13:05
ayogi left13:05
lss8 joined13:06
lss8 left13:06
lss8 joined13:06
rgb-one joined13:06
levex_ left13:08
peacememories joined13:11
rwb left13:11
cyberz joined13:12
gp5st left13:13
Sample joined13:13
jeffreylevesque joined13:13
Dumblez0r left13:14
jameser joined13:15
PrashantJ joined13:16
Tobbi left13:16
thebope joined13:16
Sample left13:17
PrashantJ left13:17
Timvde I'm suddenly totally confused about rebase :( If I have a merge conflict during rebase, do I have to commit manually after fixing, or does git rebase --continue do this for me?13:18
selckin believe continue does it, have to stage it tho13:19
Timvde I guess I could set up a test repo and try, though... But it annoys me that I lack the intuition.13:19
selckin you can also commit if you want13:19
DolphinDream left13:20
explody left13:20
jophish_ left13:20
Timvde https://stackoverflow.com/questions/6457044/forgot-git-rebase-continue-and-did-git-commit-how-to-fix13:20
Okay, looks like I need to just do a rebase --continue13:20
peacememories left13:21
thebope left13:21
Torrone joined13:21
selckin hmm i was sure that was valid to the docs13:21
Tobbi joined13:21
rgb-one left13:21
Timvde selckin: 2011 question, maybe the answers are outdated13:22
venmx joined13:22
star_prone joined13:23
joeco__ joined13:24
selckin differend behavior in rebase and rebase -i, that what trips me on it13:25
dgonzo left13:26
venmx left13:26
joeco_ left13:27
acetakwas joined13:28
Nilesh_ joined13:29
marcogmonteiro left13:29
kritzikratzi joined13:29
aard_ left13:30
explody joined13:30
Levex joined13:31
rvgate left13:33
bvcosta left13:33
rvgate joined13:33
JeroenT_ joined13:33
kexmex joined13:34
reynierpm joined13:34
ash_workz left13:34
Dumblez0r joined13:34
MattMaker joined13:35
xissburg left13:35
guardian hello, when using git rev-list --before=<date> is it the author date or the commiter date?13:35
reynierpm I have a few branches locally with some work but I don't want to push them to the origin because it's an uncompleted work and shouldn't be there, now I am moving from one laptop to a brand new and I need to move also such work, what's the best way to achieve this without push all those branches to the origin?13:35
jameser_ joined13:35
rgb-one joined13:36
hussam joined13:36
ResidentBiscuit joined13:36
JeroenT left13:37
jameser left13:38
jameser joined13:38
pk64 joined13:38
jimi_ left13:39
Ryanar joined13:39
gitinfo set mode: +v13:39
pk64 How do I rebase my patch branch? When I go to rebase, I see commits from what seems to be the master branch, where my patch branch lists my 4 commits, the master has 2 from me + the upsream branch13:40
jameser_ left13:41
GodGinrai left13:41
ismithers left13:41
ResidentBiscuit left13:41
jameser_ joined13:41
marcan joined13:41
xissburg joined13:41
GodGinrai joined13:43
mindfart joined13:43
jameser left13:44
thethorongil joined13:44
jameser_ left13:44
oaao left13:45
oaao joined13:45
marcogmonteiro joined13:46
PrashantJ joined13:46
StrongBit left13:47
bvcosta joined13:47
moritz pk64: generally by checkiing out the branch and doing a "git rebase master"13:47
PrashantJ I recently made a PR on github and ran into merge conflicts. This is my very first pool request and I am newbie. Please suggest ways to resolve. Some reference link is appreciated.13:48
grayjoc joined13:48
scoobertron left13:48
star_prone left13:49
PrashantJ For your kind reference : https://github.com/rtnpro/opencabs/pull/813:49
pk64 moritz: wouldn't that affect master? I just want to squash the commits I see in the patch-4 branch13:49
rwb joined13:50
moritz pk64: no, it affects the branch you're on.13:50
pk64 ah ok, thank you. i'll review the rebase doc again as well13:50
qt-x left13:51
thethorongil left13:51
Raging_Hog left13:51
pk64 left13:52
selckin left13:52
jameser joined13:53
dedicated_ joined13:54
scoobertron joined13:54
aspiers left13:55
rafalcpp sha1 is broken in practice now. https://shattered.it/13:55
when will git move to sha256 or sha512 checksums?13:55
_ikke_ rafalcpp: It's not that easy13:56
dedicated left13:57
_ikke_ rafalcpp: Work is underway to not rely on a fix hash lenght, but it's still a lot of work to actually change the hash algorithm13:57
corentin joined13:57
corentin hello13:57
gitinfo corentin: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.13:57
corentin what about this? http://shattered.io/13:58
_ikke_ corentin: you're #213:58
rafalcpp: corentin Best place is the !mailing_list13:58
gitinfo rafalcpp: The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://j.mp/gitlist13:58
corentin will git use a stronger hash algorithm?13:58
_ikke_ corentin: Probably in the future, but it's not something you can switch over night13:58
gitinfo set mode: +v14:01
mischat_ left14:01
Raging_Hog joined14:01
metalraiden34 left14:01
dvaske_ left14:01
bvcosta left14:01
mischat joined14:02
JeroenT_ left14:02
JeroenT joined14:03
pks left14:03
Ryanar left14:04
pks joined14:04
aspiers joined14:04
star_prone joined14:04
bernardio left14:06
metalraiden34 joined14:07
jameser left14:08
jimi_ joined14:09
star_prone left14:09
jameser joined14:09
kinlo joined14:09
thebope joined14:10
Rodya_ joined14:11
jeffreylevesque left14:12
joeco__ left14:12
jeffreylevesque joined14:12
bgerber left14:14
sbulage left14:15
thebope left14:15
Eryn_1983_FL left14:15
peacememories joined14:15
nioncode left14:16
i7c left14:16
noctux left14:16
bgerber joined14:16
jameser left14:16
DarkPsydeLord joined14:17
Learath2 _ikke_: seems the archive link is broken14:17
peacememories left14:17
jameser joined14:19
peacememories joined14:19
r_rios left14:19
nioncode joined14:19
_ikke_ Hmm, right14:20
r_rios joined14:20
_ikke_ http://public-inbox.org/git14:20
noctux joined14:20
aielima joined14:21
mahakal left14:21
star_prone joined14:22
Vampire0 !list14:23
gitinfo [!mailing_list] The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://public-inbox.org/git14:23
mahakal joined14:23
_ikke_ Vampire0: thanks14:23
aielima left14:26
alexandre9099 left14:26
Darcidride joined14:26
alexandre9099 joined14:26
aielima joined14:26
Murii_ joined14:27
bannakaffalatta left14:27
jsho joined14:27
finalbeta joined14:27
Vampire0 _ikke_, yw14:29
Eryn_1983_FL joined14:29
King_Hual left14:31
King_Hual joined14:32
texinwien_ left14:32
texinwien_ joined14:33
jon-mac left14:33
Guest29403murph14:34
cqi joined14:34
cqi left14:34
Stummi joined14:35
r_rios left14:36
Stummi hey there, just wondering are there any plans for git to rely on other hash algorithms than SHA-1 for commit hashes? (Or maybe is it already possible at all?)14:36
r_rios joined14:37
r_rios left14:37
r_rios joined14:37
osse Stummi: work has been done. not sure how complete it is14:37
e.g. stop hardcoding 20 everywhere14:37
grawity see the mailing list for the heaps of object_id patches14:37
MacGyver left14:38
chigang left14:39
Ryanar joined14:39
_ikke_ Stummi: You're #3 :P14:39
linuxmodder left14:40
peacememories left14:40
rgb-one left14:40
ShekharReddy joined14:40
oaao left14:40
oaao joined14:41
ShekharReddy left14:41
xissburg_ joined14:41
Raging_Hog left14:41
lamont left14:42
mahakal left14:42
kexmex left14:43
xissburg left14:43
publio joined14:44
dragoonis joined14:44
Es0teric joined14:45
dragoonis Hey! I'm building a CI script and would like some advice .. I want to clone down the specific target branch specified by the CI job.. I can clone down the first time, but on the second run I don't want to re-clone the entire repository every time, is there a quicker way? This is my command right now14:45
git clone -b ${FURY_BRANCH} --depth=1 --single-branch [email@hidden.address]14:45
Let's say FURY_BRANCH changes from 'master' to 'develop'14:46
I need it to quickly trash all [potential] dirty changes and switch to the new branch and pull down its code14:46
right now I'm doing "rm -rf fury && git clone -b ..."14:46
but it's slow ..14:46
this repo's .git folder is 900MB14:47
ResidentBiscuit joined14:47
BadHorsie joined14:48
PaulCapestany joined14:49
khfeng left14:49
linuxmodder joined14:50
xissburg_ left14:50
khfeng joined14:50
theoceaniscool joined14:50
yanome oh boy, https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html14:51
crose joined14:51
mahakal joined14:52
xissburg joined14:52
ResidentBiscuit left14:52
peacememories joined14:52
Vampire0 yanome, you're #414:53
nickabbey joined14:53
bremner clearly we need a bot command14:53
moritz !collision14:54
Vampire0 bremner, the bot triggers cannot increase the count on each invocation *g*14:54
xanadu left14:54
yanome wait, really?14:54
sorry14:54
Vampire0 no problem14:54
yanome what?14:54
nobody in my scrollback has posted that link14:55
github051 joined14:55
yanome ah, but i wasn't the first to mention it14:55
osse dragoonis: fetch14:55
Vampire0 yanome, http://shattered.io/14:55
moritz dragoonis: git fetch && git checkout -f origin/FURY_BRANCH14:55
dragoonis: as a good first step14:55
osse dragoonis: the --depth thing will bite you in the end. do a regular clone first and fetch thereafter14:55
yanome Vampire0: wneat14:55
BadHorsie Is there a way to have git fetch use the same flag as clone --reference ? Trying to use Jenkins but it uses git fetch instead of clone so not sure how to use a local cache (mirror --clone)14:55
dragoonis osse, what will happen, the --depth thing saves me SOOO much clone time14:56
imack joined14:56
peacememories left14:56
osse dragoonis: yes, but only the once14:56
rgb-one joined14:56
osse subsequent fetches are fast14:56
and depth make them slower (AFAIK)14:56
kbs joined14:57
tristanp joined14:57
jameser left14:58
dec0n left14:58
mahakal left14:58
dragoonis osse, moritz for my initial clone can I still keep --single-branch, yea?14:59
osse yes14:59
dragoonis cool deal14:59
AaronMT joined15:00
github051 left15:01
texinwien_ left15:01
overlord_tm left15:02
texinwien_ joined15:02
sbulage joined15:02
nettoweb left15:03
r_rios left15:03
r_rios joined15:04
basy joined15:04
thebope joined15:05
ash_workz joined15:05
dragoonis osse, moritz this is what i've whipped up - what do you think?15:05
https://gist.github.com/dragoonis/cd1d45f21121a9f70cbe2f927368909215:05
Masber left15:06
_ikke_ yanome: Nice btw that you link to the blog post instead of the marketing page15:06
mahakal joined15:06
jameser joined15:06
BlueMatt joined15:06
osse dragoonis: you should checkout origin/blah like moritz said15:07
Torrone left15:07
dragoonis cool15:07
jj- left15:07
ferr1 left15:07
shinnya joined15:08
gugah left15:08
BlueMatt heh, re: collision: is there some way to coerce git into giving you a tree hash re-calculated with something other than sha1 (even if super slow)?15:09
Gsham joined15:09
thebope left15:09
Anja left15:09
kbs wondering if that would help (even if done)15:10
jj- joined15:10
msonntag left15:10
lowercas_ joined15:10
BlueMatt kba: not for many things, but eg signed tags you could just sign that tree hash and publish that elsewhere15:10
ResidentBiscuit joined15:10
BlueMatt would be much nicer than going and sha256ing every file in your repo15:11
ravi__ joined15:11
blackwind_123 joined15:12
lowercaseman left15:12
bannakaffalatta joined15:12
ravi__ left15:12
kbs ah, I see15:12
ravi_ joined15:12
gugah joined15:12
lowercas_ left15:13
msonntag joined15:13
Sample joined15:14
Hozy joined15:14
vimal2012 joined15:14
rj1 left15:15
gugah_ joined15:15
MacGyver joined15:15
gtristan left15:16
malt3 left15:16
Torrone joined15:17
jeffreylevesque_ joined15:17
LeBlaaanc joined15:17
rchavik left15:17
sasamil left15:17
malt3 joined15:17
gugah left15:17
Levex left15:17
shgysk8zer0_ joined15:18
jagob left15:18
MattMaker left15:18
basy left15:18
Sample left15:19
jeffreylevesque left15:19
varun joined15:19
aw1 joined15:19
varunGuest6371215:19
texinwien_ left15:20
dsdeiz joined15:20
dsdeiz left15:20
dsdeiz joined15:20
jameser left15:20
shgysk8zer0_ left15:20
texinwien_ joined15:20
whaley joined15:21
kbs Seems reasonable :-) and thinking (naively) correct to assume something like this would need to reformat + then recalculate every object in the full history?15:21
imack left15:22
denisMone joined15:22
kbs (i.e. the embedded 20 byte hashes in each object reference would need to be redone all the way to the starting point)15:22
gugah_ left15:22
marcan I imagine forward-migration should be possible15:23
Hozy left15:23
jameser joined15:23
Dumblez0r left15:24
e14 joined15:24
marcan you'd have to tag and allow both kinds of hashes, then at some point force a cutoff15:24
matoro left15:24
marcan you could do that by naming every leaf SHA1 in a SHA-256 object and forbidding any child commits not using SHA-256 after that15:24
MattMaker joined15:24
Darren_ joined15:24
marcan then, as long as there are no preimage attacks in the future (unlikely), or secret chosen-prefix collision attacks in the present (probably unlikely), you're pretty much safe15:25
metalraiden34 left15:26
marcan I guess git already implements the parent/child commit mechanics to allow this, even if the signed trees are dummies. you'd just have a special commit that has as parents all leaf SHA-1 commits and basically "caps" the SHA1 history15:26
GodGinrai left15:26
nickabbey left15:26
marcan so the main thing would be adding support for more than one hash algorithm and somehow tagging that in the various binary formats15:26
varundath joined15:27
gtristan joined15:27
kbs is a "leaf" sha-1 commit the same as a blob object?15:28
_ikke_ No15:28
marcan I mean a commit object15:28
dealing with trees and blobs is easy15:28
you just enforce that sha-256 commits must reference sha-256 trees and blobs15:29
_ikke_ marcan: there has been a discussion about this on the mailing list15:29
marcan _ikke_: got a link?15:29
MrMojit0 left15:29
Dumblez0r joined15:30
_ikke_ marcan: Not sure if this contains what I mean, but this is at least a discussion about it: http://public-inbox.org/git/CAPp-Vrb_n6z39RLHZ4AeUaBFiJfL3_xX8Utfq7+bTgzZrza58Q@mail.gmail.com/15:30
berndj what practical steps can high-stakes projects take? identify versions by an n-tuple of the most recent commits, n > 1? (would that even help?)15:30
Ryanar left15:31
marcan keep infra secure and sign release tarballs is the obvious way15:31
and don't allow force pushing15:31
_ikke_ Note that git doesn't overwrite existing objects with the same hash15:31
marcan right, this is mostly about fresh clones15:32
also keep in mind that with the *current* attack you're mostly safe if you use git for *code*15:32
_ikke_ right, it's not a pre-image attack15:32
marcan no, it's also not a chosen-prefix attack15:32
_ikke_ so it's still hard to find a collision for an existing object15:32
marcan it's a fixed-prefix attack15:32
so you'd have to have *malicious code* in there from the beginning15:32
if you're using git for binaries then you're at risk unless you're carefully vetting those binaries15:33
LeBlaaanc left15:33
marcan if you use git for code presumably you actually read said code (if you don't then you're already screwed) so you should be fine15:33
for *now*15:33
LeBlaaanc joined15:33
basy joined15:33
marcan using the current attack with code would require malicious code to already be present in the repo, triggered conditionally on the collision block15:33
ghoti left15:33
marcan that's easy with binaries nobody goes around decompiling. it's easy with PDFs. it's rather hard with source code.15:34
berndj marcan, how does signing help? is the signature over something other than the commit id?15:34
gitinfo set mode: +v15:34
marcan you'd have to sign the whole tree, not the commit object15:34
varundath What is the difference between these two git fetch commands.?15:34
Command 1: `git fetch origin refs/pull/ID/merge:BRANCHNAME`15:34
Command 2: `git fetch origin pull/ID/head:BRANCHNAME`15:34
marcan I mean traditional gpg signatures on a tarball15:34
Droolio joined15:35
berndj ok, but making sure that gpg doesn't just use sha1 under the hood15:35
marcan sure15:35
berndj but yes, perspective: it's a collision attack, not (yet) a preimage attack15:35
moritz I think you can configure git to use a message digest algorithm of your choice15:35
marcan again, it's not an arbitrary collision attack15:35
it's a fixed prefix collision attack15:35
the difference is *very* important15:35
berndj although that isn't a guarantee of safety15:35
marcan a preimage attack on SHA-1 will likely never happen15:35
we don't even have collision attacks on MD215:36
but a *fixed prefix* collision attack on MD5 you can compute on a smartphone15:36
Dougie187 joined15:36
marcan a *chosen prefix* collision attack on MD5 is what broke x.509 certs and what the Flame malware used, and you still need a cluster to compute that15:36
Eryn_1983_FL left15:36
berndj an attacker could be (or could compromise) a developer with push access, then generate two colliding trees, one benevolent, one malevolent15:36
marcan this is a *fixed prefix* attack on SHA-115:36
berndj: no15:37
an attacker could generate two colliding trees, *both malevolent*, except one might not actually do anything evil15:37
moritz wouldn't sign "a preimage attack on SHA-1 will likely never happen"15:37
roelmonnens left15:37
berndj well both malevolent wouldn't be useful, as it'd stand out like a sore thumb15:37
basiclaser joined15:37
osse I blame capitalism15:37
berndj unless you mean malevolent at the philosophical level15:37
Eryn_1983_FL joined15:38
marcan moritz: okay, in my lifetime, at least not until brute force compute power advances to the point where it's nearly meaningless15:38
moritz cryptoanalysis *has* made some impressive breakthroughs before15:38
roelmonnens joined15:38
marcan berndj: I mean both malevolent15:38
today's attack lets you create two files which *only* differ in one tiny section15:38
you can *make* the rest of the file check that section and behave differently. that's how you get the "evil binary, good binary" or "evil pdf, good pdf" case - buth both are evil, one just doesn't behave in an evil way15:39
but you can't do that with code because the if(collision == 1) evil(); else not_evil(); would stick out like a sore thumb15:39
you *cannot* collide good(); //collision1 with evil(); //collision2 with today's attack15:39
(you *can* with the MD5 collision attack that Flame used)15:39
*that* is the important difference15:39
mahakal left15:39
berndj printf("Example nonce: 458cbd7fe\n"); /* Show user allowed values. */15:40
printf("Example: yes\n"); system("rm -rf /"); /* 7n29c2==28c7 */15:40
PrashantJ left15:40
marcan moritz: keep in mind that we don't have a preimage attack on MD2 yet15:40
berndj ^ like that, marcan15:40
marcan berndj: you don't get to pick the contents of the section that changes15:40
berndj marcan, that's why it's disguised as a harmless random number15:41
marcan where does the "system("rm -rf /");" come from?15:41
berndj ok, i'll come up with a better example15:42
ispn joined15:42
kbs Just to offer a gentle diversion from the "is the sky really falling" discussion :-) _ikke_ or others in the know - likely to see something like the mailing list proposal emerge in the next versions or two of git?15:42
texinwien_ left15:42
Levex joined15:43
texinwien_ joined15:43
_ikke_ kbs: No, this is a long term thing15:43
mischat_ joined15:44
mischat_ left15:45
mischat_ joined15:46
mischat__ joined15:47
Kumool joined15:48
mischat left15:48
Gsham left15:48
kpease joined15:48
shgysk8zer0_ joined15:48
star_prone left15:48
Tobbi left15:48
PCatinean joined15:49
PCatinean Hello everyone15:49
rgb-one left15:49
PCatinean I got myself into a very complex scenario (not sure how I landed here)15:50
Wind0r joined15:50
Wind0r left15:50
mischat_ left15:50
PCatinean I have a branch that's 20 commits behind the main one, and 48 ahead, after rebase it's 24 commits after, how can thi sbe?15:50
Wind0r joined15:51
zefferno left15:51
berndj marcan, preferred pastebin? pastebin.com ok?15:51
marcan whatever works15:52
miczac joined15:52
marcan I run my own private one :P15:52
gitinfo set mode: +v15:52
moritz PCatinean: does "after" mean "ahead" or "behind"?15:52
miczac left15:53
PCatinean ahead moritz sorry15:53
berndj marcan, here, my better attempt: http://pastebin.com/UGZMJMZn15:53
PCatinean just trying to be sure I don't lose any work15:53
moritz PCatinean: sounds imposible15:53
jstimm joined15:53
hezekiah joined15:53
wizeman joined15:53
moritz PCatinean: did you git fetch or push in the mean time?15:54
marcan berndj: I'd argue that ought to raise eyebrows (also the junk would probably have to be binary)15:54
moritz s/impossible/implausible/15:54
berndj granted, this pseudo-example uses C, and not all 8-bit values are valid even inside a C comment, and the collision-grinding would need to be repeated until it happens to generate the right prefix to those ifdef / comment bits15:54
moritz PCatinean: or did git rebase ask about empty commits several times during the rebase?15:54
berndj and it's just a 5-minute proof of concept from a relative n00b, not a serious assault15:54
jameser left15:54
marcan berndj: this is the kind of thing the underhanded C code contest is for15:55
PCatinean moritz, tehere were 2 conflicts15:55
I solved them and then pushed to a separate branch instead of pushing with force on the original one15:56
synthroid left15:56
Salz joined15:57
PCatinean I wonder what's going on15:58
rgrinberg joined15:58
PCatinean moritz, maybe it omits the merges?15:58
thebope joined15:59
robotroll joined15:59
overlord_tm joined15:59
moritz the rebase might have flattened out some merges15:59
and thus lost some merge commits15:59
which might account for a lower total numer of commits afterwards15:59
PCatinean hmm16:00
The thing is I would want to later merge the changes from dev to master16:00
But right now I need some commits from master on dev16:00
And I think rebase is the best way to go?16:00
moritz it's an option16:01
"best" really depends on many factors16:01
jost__ joined16:01
rgb-one joined16:02
tlaxkit joined16:02
NeXTSUN joined16:02
DreadKnight joined16:02
roelmonn_ joined16:02
roelmonn_ left16:03
xissburg left16:03
thebope left16:03
jagob joined16:03
DreadKnight hey, when cloning a repo in a folder I want, how to stop git from cloning the whole thing into a subfolder?16:03
overlord_tm left16:04
Dumblez0r left16:04
moritz DreadKnight: git clone <url> destination/16:04
khfeng left16:04
jost_ left16:04
moritz DreadKnight: and if into the current directory, git clone <url> .16:04
(. = current directory)16:05
DreadKnight moritz, did just that and it made a nodejs folder with the whole thing, sigh; will try again16:05
metalraiden34 joined16:05
roelmonnens left16:06
Atemu joined16:08
rvgate left16:08
ThomasLocke left16:09
clemf joined16:09
kexmex joined16:09
guest3456 joined16:10
guest3456 is what they say about Git on this page true?16:10
https://shattered.it/16:10
hezekiah left16:11
moritz guest3456: it's been discussed here before; please read the logs starting from https://irclog.perlgeek.de/git/2017-02-23#i_1415096816:12
hahuang65 left16:12
guest3456 will do16:12
moritz (note that there were at least two blocks of discussion about this)16:13
GodGinrai joined16:13
Atemu left16:13
kexmex left16:13
chardan joined16:14
jstimm left16:14
nickabbey joined16:15
whaley_ joined16:16
ayogi joined16:19
whaley left16:19
hasc joined16:19
kbs left16:20
basy left16:21
basy joined16:22
l4v2 joined16:22
Emperor_Earth joined16:23
MattMaker left16:23
qqx left16:23
qqx joined16:23
JeroenT left16:23
dragoonis moritz, osse hey16:23
git fetch && git checkout -b origin/dockerization16:23
fatal: A branch named 'origin/dockerization' already exists.16:23
If I'm already on the target branch, it isn't pulling in latest changes for the target branch16:24
GodGinrai left16:24
GodGinrai joined16:24
thiago left16:25
GodGinrai dragoonis: -b creates a branch. You should not be using that flag16:25
pie__ joined16:26
xaviergmail_ left16:26
texinwien_ left16:26
CheckDavid joined16:26
de-vri-es left16:26
Es0teric left16:26
texinwien_ joined16:26
de-vri-es joined16:27
xaviergmail_ joined16:27
pie__ so, given googles practical collision attack, can we get a push for deprecating sha1 in git now :I16:27
or if you prefer, "practical"16:27
lordjancso joined16:27
Alienpruts left16:28
GodGinrai pie__: sha1's use in git never had anything to do with security, did it? I thought it was just a reliable way to create unique hashes16:28
for git's purpose16:28
nowhereman joined16:28
e14 left16:28
ChanServ changed the topic to: Welcome to #git, the place for git help. Just git help, apparently. | We are aware of the SHA-1 collision |Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.11.0 | Getting "cannot send to channel"? /msg gitinfo .voice | This is serious business. https://madeitwor.se/git-jokes16:29
Ryanar joined16:29
dragoonis GodGinrai, i have a CI script, i'm avoiding deleting and re-cloning the repo every time .. so was looking to have the system just quickly check out the target branch16:29
Es0teric joined16:29
ChanServ changed the topic to: Welcome to #git, the place for git help. Just git help, apparently. | We are aware of the SHA-1 collision | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.11.0 | Getting "cannot send to channel"? /msg gitinfo .voice | This is serious business. https://madeitwor.se/git-jokes16:29
perlpilot heh16:29
dragoonis GodGinrai, so I ended up with this: cd $DIR/fury && git fetch && git checkout -b origin/${FURY_BRANCH}16:29
BSAlb joined16:30
GodGinrai dragoonis: you should never use the -b flag with any remote branch name as an argument16:30
dragoonis: remote branches are created by git. You are not supposed to create them yourself16:30
dragoonis I need something to cover this : a) you're already on the target branch but you want to pull latest changes. b) you're on a branch and want to switch to a new one and pull its latest changes16:30
_ikke_ GodGinrai: Note that this would create a local branch called origin/..16:31
perlpilot dragoonis: you could keep the git clone someplace separate and use rsync to make the branch CI uses match what's in the repo16:31
GodGinrai dragoonis: like I said, get rid of the -b. It has nothing to do with what you want to do16:31
_ikke_ refs/heads/origin/<name> vs refs/remotes/origin/name16:31
GodGinrai _ikke_: I know it will. That's a problem16:31
_ikke_ Just to be sure16:31
dragoonis GodGinrai, so "git fetch && git checkout origin/{$TARGET_BRANCH}" will suffice my requirements that I listed ?16:32
ayogi left16:32
pie__ GodGinrai, well, yeah, i guess. but why not actually make it secure? :/16:32
_ikke_ dragoonis: as long as you are not planning on comitting, then that works16:32
Gsham joined16:32
ayogi joined16:32
mischat joined16:32
GodGinrai pie__: Would you feel the need to secure a stack of free newspapers?16:32
dragoonis _ikke_, no committing here.. pulling down the code .. running some tests .. then passing/failing the jenkins build based on the test suite result16:33
pie__ GodGinrai, secure them from meddling sure16:33
i.n.t.e.g.r.i.t.y.16:33
BSaboia left16:33
l4v2 left16:33
dedicated joined16:33
_ikke_ Right16:33
GodGinrai pie__: you are telling me this attack could allow someone to ruin the integrity of the repo? How?16:33
_ikke_ pie__: Note that this specific attack is not very usable in git16:34
sbulage left16:34
pie__ GodGinrai, i havent done my homework, but even if this concrete attack isnt of interest....16:34
_ikke_ pie__: It's not a pre-image attack, which lets you find a collision for existing data16:34
pie__ though i suppose i did imply that it has immediate raifications, so i apologize16:34
*ramifications16:35
ToBeCloud joined16:35
gitinfo set mode: +v16:35
dragoonis GodGinrai, _ikke_ i removed the -b and I get this now: "warning: refname 'origin/dockerization' is ambiguous."16:35
_ikke_ dragoonis: because you already created a branch called origin/dockerization16:35
dragoonis: git update-ref -d refs/heads/origin/dockerization16:35
dragoonis Is it safe to ignore this ? it will be repeatedly checking out origin/dockerization on every built16:36
elect left16:36
dedicated_ left16:36
GodGinrai dragoonis: see the command _ikke_ just gave you16:36
mischat__ left16:36
dragoonis yeah - msg delays16:36
thanks i will do this before running the checkout16:36
_ikke_ dragoonis: You only need to do this once16:36
dragoonis fetch && update-ref && checkout16:36
_ikke_, not on every CI build?16:36
_ikke_ dragoonis: no16:37
dragoonis: it's because you used -b before16:37
chachasmooth left16:37
DreadKnight left16:37
dragoonis _ikke_, alright16:37
InfoTest joined16:37
dragoonis How's this? https://gist.github.com/dragoonis/ee18195bcca15c2687457fcfb05812e916:38
MattMaker joined16:38
GodGinrai dragoonis: why are you using a pre-existing repo in your CI instead of cloning? Normally, CI is supposed to run stateless16:38
pie__ _ikke_, its not chosen prefix but its getting there i think?16:38
*preimage16:38
dragoonis GodGinrai, coz if you clone it, it takes like 10 minutes bcoz the repo is 1GB in size :P16:39
_ikke_ pie__: Eventually it will, the question is how long it would take16:39
dragoonis so it's a one-time clone then a speedy "switch to this branch" thereafter16:39
chachasmooth joined16:39
GodGinrai dragoonis: but if you are just getting the code to test, you could do a shallow clone16:39
Fallen0223 joined16:39
_ikke_ GodGinrai: What is wrong with this approach?16:39
brent__ joined16:40
pie__ i mean its not like it matters how i feel, but i feel git should have the built in capability to upgrade its algorithm if necessary16:40
and that it should do so before something happens not after...16:40
GodGinrai _ikke_: if something happens to the repo outside of CI, then the CI can fail for reasons that have nothing to do with anything that actually happened in the code16:40
_ikke_ pie__: They are working on it, it just takes time16:40
vimal2012 left16:40
pie__ oh they are?16:40
_ikke_ GodGinrai: same with shallow clones..16:40
pie__ last time i looked into it i got the feeling they didnt want to16:40
GodGinrai _ikke_: that's only if something happens to the remote repo. I'm talking about the repo local to the CI16:41
_ikke_ pie__: Someone has been working over the last months / years removing all the hardcoded references to sha1 (length)16:41
GodGinrai _ikke_: the one he is fetching into16:41
pie__ ok,thats coforting :P16:41
_ikke_ GodGinrai: pie__ The main challenge is backwards compattibility, which they are not sure about yet how to handle)16:41
pie__ comforting16:42
osse cloning takes a long time. fetching takes not as long.16:42
Balliad left16:42
pwndave left16:42
dragoonis the .git folder on this repo is 950MB16:42
_ikke_ I would use git archive then instead of a shallow clone, if you do not require a repo at all..16:42
dragoonis mental16:42
_ikke_ unless you use github, but then you can get an archive from the webinterface16:42
pie__ _ikke_, i presume its more nuanced but id assume you should just upgrade old repos16:42
_ikke_ pie__: Like you said, it's more nuanced16:42
yushyin joined16:43
Gsham left16:43
GodGinrai osse: shallow clone wouldn't take as long. Sure, it might still be longer than fetch. But is it worth it to jeopardize the integrity of the tests for faster speeds?16:43
User458764 left16:43
_ikke_ pie__: It's not that the developers are clueless :)16:43
osse what integrity?16:43
dragoonis I know for a fact that the client won't delete their repository.16:43
pie__ _ikke_, ;)16:44
dragoonis (if that makes a diff)16:44
Ranhir left16:44
pie__ well, thanks i guess16:44
do you happen to have any mailinglist archive links by any chance?16:44
pwndave joined16:44
_ikke_ pie__: https://public-inbox.org/git/CAPp-Vrb_n6z39RLHZ4AeUaBFiJfL3_xX8Utfq7+bTgzZrza58Q@mail.gmail.com/16:44
GodGinrai _ikke_: Continuous integration is supposed to be automatic. Where would you get the archive? Set up a hook that uploads an archive whenever the repo changes?16:44
_ikke_ GodGinrai: git archive16:44
nettoweb joined16:45
oaao left16:45
elsevero left16:45
Vampire0_ joined16:45
matsaman joined16:45
GodGinrai _ikke_: git archive only works from within a git repo. You can't use it to pull the code from a remote repo. (unless there is something I'm missing)16:45
Ranhir joined16:45
Gsham joined16:45
_ikke_ GodGinrai: It does work with remote repos16:46
oaao joined16:46
redeemed left16:46
_ikke_ Only some services disabled it16:46
like github16:46
Vampire0 left16:46
GodGinrai _ikke_: wow. I was not aware of this.16:46
zeroed left16:46
GodGinrai then yes16:46
_ikke_ see --remote= option of git archive16:46
GodGinrai that would obviously be preferable to a shallow clone16:46
assuming that the remote server has this functionality enabled16:47
r_rios left16:47
osse I am confused. Our jenkins at work does git fetch && git checkout origin/master. What's bad about that?16:47
_ikke_ github allows you also to download archives through the webinterface, but that's more limited16:47
r_rios joined16:47
zeroed joined16:49
zeroed left16:49
zeroed joined16:49
_ikke_ http://github.com/org/project/archive/branch.tar.gz16:50
RxMcDonald left16:50
_ikke_ Get's you a tarball of the last commit on the branch16:50
nothingnew joined16:51
e14 joined16:52
NeXTSUN left16:52
moritz but you want meta data like commit hash, last commit etc. for CI purposes, so IMHO that's a poor choice16:52
_ikke_ pie__: Note that not everyone has the possibility to upgrade, so it cannot be a hard cut-off point16:52
thebope joined16:53
moritz I also expect a CI system to keep a reference cache of a repo around so that it avoids a full clone each time.16:53
pie__ _ikke_, what would stop them? though i do like the sound of this zsolt fellows idea but i see in the followup emails that thats probably not whats going to happen16:53
jstimm joined16:53
Hozy joined16:54
elementalest left16:54
synthroid joined16:54
_ikke_ pie__: compattibility16:55
d0nn1e left16:55
_ikke_ pie__: centos 7 still ships git 1.8.x16:55
Kumool left16:55
_ikke_ Going to take a while before all git installations are up-to-date16:55
le_melomane joined16:55
pie__ i guess you cant force people to update but....16:56
give a deprecation deadline16:56
matoro joined16:57
flaviodesousa left16:57
Gsham left16:57
whaley_whaley16:57
d0nn1e joined16:57
thebope left16:57
redhedded1 joined16:57
Cyp___ joined16:58
texinwien_ left17:03
Es0teric left17:03
kbs joined17:03
Es0teric joined17:03
texinwien_ joined17:03
r_rios left17:04
Gsham joined17:05
theoceaniscool left17:05
User458764 joined17:05
lss8 left17:06
Gsham left17:06
_ikke_ pie__: https://public-inbox.org/git/alpine.DEB.2.20.1607180905320.28832@virtualbox/17:06
_xor joined17:06
thiago joined17:07
clemf left17:08
multi_io left17:10
clemf joined17:10
yehowyada joined17:10
madewokherd joined17:11
multi_io joined17:11
ayogi left17:14
shinnya left17:14
Sample joined17:15
_ikke_ pie__: https://public-inbox.org/git/Pine.LNX.4.58.0504291221250.18901@ppc970.osdl.org/17:15
imack joined17:15
_ikke_ (This is what Junio, the git maintainer, replied on the mailing list)17:15
grayjoc left17:16
troulouliou_div2 left17:16
marenz left17:17
MattMaker left17:17
NeXTSUN joined17:17
orbyt_ joined17:17
osse do you mean linus?17:17
bvcosta joined17:18
_xor left17:18
_ikke_ No, I mean junio replied with a link to that post17:18
nickabbey left17:18
orbyt_ left17:18
jnavila left17:19
lordjancso left17:19
chachasmooth left17:19
nickabbey joined17:19
le_melomane left17:19
varundath left17:19
osse it's amazing that i didn't see you posted *two* links17:19
ChanServ changed the topic to: Welcome to #git, the place for git help. Just git help, apparently. | We are aware of the SHA-1 collision. See: http://jk.gs/t/a3 | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.11.0 | Getting "cannot send to channel"? /msg gitinfo .voice | This is serious business. https://madeitwor.se/git-jokes17:19
le_melomane joined17:19
pie__ osse, spacing \o/17:20
Levex left17:20
Sample left17:20
jimi_ left17:21
_ikke_ "In other words, the security isn't in the hash. The hash is an added level17:21
to make it much harder to fool, but it's not "the security". "17:21
durham joined17:21
le_melomane left17:22
aspiers left17:22
le_melomane joined17:23
_ikke_ Junio: "IOW, we want to continue the work to switch from SHA-1, but today's announcement does not fundamentally change anything and we do not panic. "17:23
chachasmooth joined17:23
nickabbey left17:24
nostrora joined17:24
nostrora Git have to change SHA-1 to another hash function17:24
http://shattered.io/17:24
Git use SHA-1 right ?17:24
_ikke_ nostrora: See topic17:24
nostrora: https://public-inbox.org/git/CA+55aFxJGDpJXqpcoPnwvzcn_fB-zaggj=w7P2At-TOt4buOqw@mail.gmail.com/T/#m57b6730ba5afee7100870396504edb8c909d5aad17:24
tyreld joined17:25
texinwien_ left17:25
_ikke_ nostrora: Junio: "IOW, we want to continue the work to switch from SHA-1, but today's announcement does not fundamentally change anything and we do not panic. "17:26
MattMaker joined17:26
markmarkmark left17:27
markmarkmark joined17:27
texinwien_ joined17:27
seemikehack joined17:28
rj1 joined17:28
UniFreak left17:28
aard_ joined17:29
Droolio left17:29
nostrora left17:29
texinwien_ left17:30
texinwien_ joined17:30
MattMaker left17:31
kurkale6ka left17:31
dustinm left17:32
debian joined17:32
seemikehack Hey all. We ran across a strange scenario that I was tasked with tracking down, and even though I now know what's happening, I still don't know why. There is a change to a single line in a file that did not get merged from Branch A to Branch B at some point, and no subsequent merges into Branch B from any branch that has the correct line have brought over the change. The line was not modified on Branch B at the time of the merge, so seemingly no17:32
conflict would have been generated that could have been improperly handled. Why does the change refuse to propagate to this branch? What could have happened during the initial merge to prevent this? What can be done now to fix it?17:32
debianGuest5840417:32
mikecmpbll left17:34
nickabbey joined17:35
svm_invictvs joined17:35
marcogmonteiro left17:37
texinwien_ left17:38
djb-irc left17:38
robotroll left17:38
texinwien_ joined17:38
mgoodwin left17:38
marcogmonteiro joined17:39
rlb Vampire0_: I wasn't (either way) - thanks, but thinking about it; certainly makes sense. Haven't messed with hooks much.17:39
Eugene seemikehack - if the line was deleted as part of conflict-resolution for the merge17:39
Its "merged", so re-merging to bring it in doesn't make sense. Add the line manually and move on with life.17:39
irqq left17:40
seemikehack Eugene, so basically, there had to have been a merge conflict that was resolved incorrectly that I just don't know about.17:41
Eugene seemikehack - or whoever did the merge deleted it. ;-)17:41
seemikehack Eugene, OK, thanks for the tip. There really doesn't seem to be any other way it could have happened.17:41
thiago left17:41
r00twrh joined17:42
boombatower joined17:42
chardan left17:43
clmsy left17:43
thiago joined17:43
okjdpi left17:44
i7c joined17:44
TomyWork left17:45
Ryanar left17:46
dsantiago left17:46
Torrone left17:46
thebope joined17:47
metalraiden34 left17:49
Rodya_ left17:49
thebope left17:51
Ryanar joined17:51
keep_ joined17:51
coreyfarrell joined17:52
marcogmonteiro left17:52
alexandre9099 left17:52
ertesx joined17:53
alexandre9099 joined17:53
chachasmooth left17:54
seni1 left17:54
gtrmtx joined17:55
Hozy left17:55
Rodya_ joined17:55
dustinm joined17:55
chachasmooth joined17:55
gtrmtx how would one go about configuring git to automatically push any time a new commit happens?17:56
coreyfarrell left17:56
texinwien_ left17:56
texinwien_ joined17:56
seemikehack gtrmtx, I've seen clients have an option for that, but otherwise you could probably set up a script to do it for you.17:56
thiago left17:57
gtrmtx a script?17:57
ertes left17:57
ertesxertes17:57
seemikehack gtrmtx, a bash script, or an alias, or something.17:57
thiago joined17:57
gtrmtx ok17:58
ill have to do some googling17:58
User458764 left17:58
seemikehack gtrmtx, see here: http://stackoverflow.com/a/23328996/526915317:58
gtrmtx what about clients? i was unaware that they existed other than gogs...anytime i run git i just do it via ssh17:58
SwiftMatt joined17:59
seemikehack gtrmtx, SourceTree has an option to always commit and push, egit has two buttons for "Commit" and "Commit and Push"17:59
chardan joined17:59
gtrmtx which one do you like more?17:59
Nilesh_ left18:00
mischat left18:00
le_melomane left18:00
shgysk8zer0_ left18:01
seemikehack gtrmtx, I prefer SourceTree, but it's only available on Windows and Mac, so I just use egit in Eclipse. There are some standalone clients that wrap egit. If you're on Linux and doing open source work, or are willing to pay, there's also SmartGit, which I *really* like.18:01
gtrmtx, almost forgot, I ran across GitKraken the other day, but haven't investigated it much. I know they have free and paid tiers.18:02
kritzikratzi hi! is there a good trick to prevent me from checking in by adding a comment in a source file? (something like /*git-blocki regularly tweak things, and then for18:02
cagomez joined18:02
kritzikratzi ooops, hit enter by accident…. um… yea, something that prevents me from committing, as long as a specific text appears in source18:02
kadoban kritzikratzi: You could have a pre-commit hook that checks for banned text of whatever format you like18:02
kritzikratzi kadoban: that sounds like what i want. are you using something like this? i don’t want to reinvent the wheel18:02
seemikehack gtrmtx, also, surprised I haven't been flamed for this already, but there's also ye olde faithefule git gui and gitk. The other solutions are just more self-contained and easier to get started with.18:03
kadoban https://www.emptypath.com/git_pre_commit_testing is what I use (warning: of my own invention). I'm sure there's more well known tools for the job.18:03
gtrmtx seemikehack, running everything in linux so sourcetree wont work18:04
kadoban It's essentially functionality that's available just out of the box in git, but it doesn't work too well unless you add some stuff on top of it. You don't have to read that whole page, you can skip to the end to see the final result.18:04
ResidentBiscuit left18:04
jalr[m] left18:04
Guest58404 left18:04
gtrmtx seemikehack, so i would install smartgit on server, and access it via web interface? or what18:04
shgysk8zer0_ joined18:04
seemikehack gtrmtx, GitEye is the standalone app that wraps egit. It's just an Eclipse RCP app that exposes egit, AFAIK.18:05
gtrmtx, all of these options I mentioned are local clients. Are you looking to administrate your own git repository on a server you control?18:05
gtrmtx yes18:05
i control server18:05
all i want to do is automatically push to github anytime i do a git commit on the server18:06
denisMone left18:06
kadoban kritzikratzi: Let me know if you need assistance beyond what's provided there. If you're familiar with the 'grep' command that'll be enough to do the test you have to set up.18:06
finalbeta left18:07
finalbeta joined18:07
marcogmonteiro joined18:07
seemikehack gtrmtx, Hmm, I think this may be an X/Y problem. Why don't you just set up GitHub as your remote?18:07
hahuang65 joined18:10
ych joined18:10
Es0teric left18:10
grayjoc joined18:10
duderonomy left18:11
ResidentBiscuit joined18:11
Torrone joined18:12
dsantiago joined18:12
Torrone left18:12
hahuang65 left18:14
buckowski left18:15
marcogmonteiro left18:15
User458764 joined18:15
tomaw left18:16
tomaw joined18:16
MattMaker joined18:17
kpease left18:17
seemikehack gtrmtx, I hate to do this to you, but I've gotta go pick the kiddo up from school and head to lunch. I'll be back in about an hour.18:18
matoro left18:19
d0nn1e left18:20
Tobbi joined18:20
orbyt_ joined18:20
buckowski joined18:21
DaveTaboola joined18:21
le_melomane joined18:22
dreiss joined18:22
hahuang65 joined18:23
jnavila joined18:23
crayon joined18:24
chachasmooth left18:24
jimi_ joined18:25
hasc left18:26
DaveTaboola left18:26
chachasmooth joined18:27
MattMaker left18:27
kpease joined18:29
theoceaniscool joined18:30
gtrmtx seemikehack, youre good...when you get back, i think maybe thats how i did it?18:30
HardlySe1n joined18:31
tlaxkit left18:31
HardlySe1n left18:31
durham_ joined18:31
durham_ left18:32
durham_ joined18:32
gtrmtx my first command was git remote add origin [email@hidden.address]18:32
orbyt_ left18:33
jedahan joined18:33
durham left18:35
kpease left18:36
j7k6 joined18:36
oleksiyp joined18:36
d0nn1e joined18:38
zeroed left18:38
Spydar007 left18:38
bongjovi left18:39
Gsham joined18:40
metalraiden34 joined18:40
thebope joined18:41
matoro joined18:41
rj1 left18:42
oleksiyp left18:43
eroux left18:43
texinwien_ left18:43
Spydar007 joined18:43
Spydar007 left18:43
Spydar007 joined18:43
texinwien_ joined18:44
whaley left18:45
MattMaker joined18:45
kpease joined18:45
thebope left18:45
robotroll joined18:46
prg3 left18:46
fatalhalt joined18:47
prg3 joined18:47
nidr0x joined18:47
le_melomane left18:49
jwest left18:49
texinwien_ left18:50
jnavila left18:50
CAPRA-MAU joined18:50
le_melomane joined18:50
basiclaser left18:51
ToBeCloud left18:51
CAPRA-MAU left18:51
texinwien_ joined18:51
aspiers joined18:52
mikecmpbll joined18:52
Vampire0_Vampire018:54
AciD` left18:54
PrashantJ joined18:54
iliekcomputers joined18:55
mablae joined18:55
Es0teric joined18:56
duderonomy joined18:56
timetrex joined18:56
Tobbi left18:57
TomyLobo joined18:58
iliekcomputers left18:58
jedahan left18:58
NullableTruth joined18:58
thiago left18:59
joki joined19:00
alexandre9099 left19:00
alexandre9099 joined19:01
matoro left19:02
InfoTest left19:03
metalraiden34 left19:03
afuentes left19:03
kritzikratzi kadoban: thx, that’s a great start. already playing with it.19:03
durham_ left19:04
OerHeks joined19:05
durham joined19:05
texinwien_ left19:05
jwest joined19:05
texinwien_ joined19:05
kadoban kritzikratzi: Cool, glad to help. Feel free to let me know if you run into any trouble with it.19:06
kritzikratzi a few things are different as i’m on osx, but i’m getting there :)19:07
cdg left19:07
cagomez left19:07
matoro joined19:07
cagomez joined19:07
eroux joined19:07
j7k6_ joined19:08
gopar joined19:08
jedahan joined19:08
kadoban Ahh osx, interesting. *crosses fingers* I definitely never tested there, though as I recall I made some effort to make it vaguely platform-neutral.19:09
kritzikratzi simple things are different, like ln doesn’t support „dash-dash“ arguments19:10
m0viefreak joined19:10
kadoban Ooo, hmm.19:10
That's unfortunate. I should figure those out, probably not too too hard to be more general19:10
j7k6 left19:11
intellix left19:11
kritzikratzi no, but a pain… and no big deal for me to change19:11
e14 left19:12
intellix joined19:12
kadoban I bet that means it's borked on BSDs as well19:13
irqq joined19:13
jimi_ left19:13
hahuang65 left19:14
Sasazuka joined19:14
pjdowson joined19:14
overlord_tm joined19:14
peterbec` joined19:14
jimi_ joined19:14
pjdowson left19:14
dedicated_ joined19:15
Gsham left19:15
wizeman left19:16
nickabbey left19:16
Sample joined19:16
navidr left19:16
nickabbey joined19:16
bvcosta left19:16
dedicated left19:16
theoceaniscool left19:17
oleksiyp joined19:17
oleksiyp left19:17
Mof joined19:18
MattMaker left19:18
eroux left19:18
jnavila joined19:19
Gsham joined19:19
jdl joined19:20
nickabbey left19:20
oleksiyp joined19:20
metalraiden34 joined19:20
nickabbey joined19:20
PrashantJ left19:20
j7k6 joined19:21
durham left19:21
Sample left19:21
bocaneri left19:22
thiago joined19:22
Zialus left19:22
grayjoc left19:22
j7k6_ left19:23
synthroid left19:23
hahuang65 joined19:23
texinwien_ left19:23
synthroid joined19:23
m4sk1n joined19:23
texinwien_ joined19:24
oleksiyp left19:25
joeco joined19:26
timetrex left19:26
orbyt_ joined19:26
kritzikratzi kadoban: i think it does something funny to empty directories19:27
(like…delete them)19:27
synthroid left19:28
thiago left19:28
thiago joined19:28
ojacobson Git does not have a representation of an empty directory (or of directories at all, really). Common convention is to put a .gitkeep or empty .gitignore file in any directory that needs to exist on checkout but has no content19:29
kadoban kritzikratzi: Hmm, interesting. I wonder if I've just never run into that or if the behavior is different.19:29
SwiftMatt left19:29
cdg joined19:29
ojacobson (The database representation can store empty directories, but the staging area can't.)19:29
mischat joined19:29
grawity left19:30
Atm0spher1c joined19:30
hahuang65 left19:30
b1tchcakes joined19:30
r00twrh left19:31
grawity joined19:32
MattMaker joined19:32
dvaske_ joined19:33
aw1 left19:34
Murii_ left19:34
kadoban kritzikratzi: I can't tell if I'd expect that behavior or not, or if so if there's a way I can work around that. I'll take a peek tonight though.19:34
cdg left19:34
cworo joined19:34
Murii_ joined19:35
kritzikratzi kadoban: i don’t think it matters at all! was just a random funky case i came across19:35
thebope joined19:35
kritzikratzi here’s what i got so far: https://asdfg.me/up/git-hooks.zip19:35
oleksiyp joined19:35
Murii_ left19:35
kritzikratzi seems to do what i want, maybe i’ll put it on github soon if it turns out stable and fast enough19:35
now i installed it globally, which i find more convenient19:36
kk, gotta run… dinner time,19:36
kadoban: thx again for your help!19:36
kadoban Ya, if it's a case I can handle better I'd like to though. Cool beans, have a good dinner. Ya, anytime.19:36
acetakwas left19:36
sharpdream joined19:36
e14 joined19:37
Murii_ joined19:37
Murii_ left19:37
imack left19:37
elsevero joined19:37
Murii_ joined19:38
Murii_ left19:38
Sample joined19:39
Murii_ joined19:39
thebope left19:39
Murii_ left19:40
Murii_ joined19:40
roelmonnens joined19:40
Murii_ left19:41
kexmex joined19:41
sieve joined19:42
Murii_ joined19:42
durre joined19:42
lamont` joined19:43
Murii_ left19:43
matoro left19:43
ronny left19:43
Murii_ joined19:43
sieve We currently have some microservices (5 or so) which we are currently deploying with docker and puppet to AWS EC2 instances. I'm wondering if it might be socially acceptable to just deploy the code with git and then have a cron job that pulls master every x mins.19:44
Murii_ left19:44
durham joined19:44
hahuang65 joined19:44
sieve Throw away all the docker and puppet stuff.19:44
texinwien_ left19:44
kexmex left19:44
NeXTSUN left19:44
lamont` left19:44
sieve Which seems to mostly cause annoyance and complications19:44
lamont` joined19:45
thiago left19:45
roelmonnens left19:45
Virox left19:45
Sasazuka left19:46
texinwien_ joined19:46
aw1 joined19:47
sonOfRa Does signing a git commit actually sign the entire object, or just the hash of the commit?19:47
lamont`lamont19:47
grawity it signs the object minus the signature header19:47
dedicated joined19:47
bremner sieve: well, you can have a look at !deploy19:48
gitinfo sieve: 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.html19:48
Virox joined19:48
Sasazuka joined19:48
thiago joined19:49
grawity not that it matters much, since the commit references the *data* by tree hash19:49
dedicated_ left19:49
sonOfRa grawity: it matters if you insert an evil colliding SHA1 :)19:49
The question is whether a signature for a good commit is also valid for an evilly forged commit with the same SHA1, but actually different code changes19:50
grawity sonOfRa: it doesn't, because you can insert colliding sha1's at *any* place19:50
if you sign the commit, you can collide the tree hash19:50
or a subtree hash19:50
or a blob hash19:50
synthroid joined19:51
dedicated_ joined19:51
c0c0 left19:52
dedicated left19:53
OerHeks left19:53
texinwien_ left19:55
bket left19:55
styx__ left19:55
styx_ left19:55
durham left19:55
whaley joined19:56
durham joined19:56
dsantiag_ joined19:56
cworo left19:56
le_melomane left19:57
texinwien_ joined19:57
FilipNortic left19:58
dsantiago left19:58
Sample left19:58
FilipNortic joined19:58
Anja_ joined19:58
jstimm left20:00
chll_ left20:01
kexmex joined20:02
le_melomane joined20:03
rumble joined20:03
sharp_dream joined20:04
livingstn joined20:04
rgrinberg left20:06
meLon left20:06
grumble left20:07
rumblegrumble20:07
jedahan left20:07
rgb-one left20:07
CrypticGator left20:07
sharpdream left20:07
CrypticGator joined20:08
bket joined20:08
dvaske_ left20:08
Ryanar left20:09
khfeng joined20:09
Flaghacker joined20:09
meLon joined20:09
CussBot left20:10
CussBot joined20:10
Fallen0223 left20:10
Fallen0223 joined20:10
le_melomane left20:11
CrypticGator left20:11
le_melomane joined20:12
jedahan joined20:12
grawity left20:12
CussBot left20:14
CussBot_ joined20:14
CussBot_CussBot20:14
PCatinean left20:15
Flaghacker Hey guys! I have a sequence of commit, A -> B -> C, and I would like to remove B. I already tried "git rebase -p --onto B^ B" but that didn't change anything. How can I do this?20:16
Decorater joined20:16
Decorater uh20:16
Eugene Flaghacker - !fixup20:16
gitinfo Flaghacker: So you lost or broke something or need to otherwise find, fix, or delete commits? Look at http://sethrobertson.github.com/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!20:16
Decorater Where can I find the git bugtracker20:16
cagomez left20:16
peterbec` left20:16
Flaghacker Eugene, Yea that was the site that told me to execute that command, but it didn't work.20:16
moritz !bug20:17
gitinfo [!bugtracker] the developers of git don't use a bug tracker. If you want to report a bug, send an e-mail to the mailing list at [email@hidden.address] (no subscription required; everyone uses "reply to all" when responding); you can review past discussions at http://public-inbox.org/git20:17
Eugene !repro20:17
gitinfo [!transcript] Please paste (using https://gist.github.com/ or similar) a transcript ( https://git.io/viMGr ) of your terminal session so we can see exactly what you see20:17
cagomez joined20:17
robotroll left20:17
Decorater I would like to report 2 bugs that I experianced in Windows before on cygwin, cygwin64,mingw, and the mingw64 bit versions20:17
ah20:17
texinwien_ left20:17
cagomez left20:18
rgb-one joined20:19
ahr3n joined20:21
livingstn left20:22
le_melomane left20:22
texinwien_ joined20:23
peterbec` joined20:23
Rodya_ left20:26
Flaghacker Eugene, I'm sorry that took so long, rebase is very slow for some reason: https://gist.github.com/flaghacker/546bbc4d415c1cbaeb3b7c78d10be3c220:26
thebope joined20:26
Rodya_ joined20:27
Decorater there is 2 bugs I encountered with rebase that I am emailing now.20:27
that is on Windows20:27
ok emailed20:27
Es0teric left20:27
chardan left20:28
Decorater Also anyone know if I can somehow use MSVC to compile git to be standalone so users do not have to have cygwin, cygwin64, mingw, or even mingw64?20:28
aidalgol joined20:28
Decorater Also my git version20:29
$ git --version git version 2.11.0.windows.120:29
snowalpaca joined20:29
synthroid left20:30
sharp_dream left20:30
texinwien_ left20:30
s1scha left20:31
jedahan left20:31
Rodya_ left20:31
Wza joined20:31
Flaghacker Eugene, Any idea what I'm doing wrong?20:32
texinwien_ joined20:32
Es0teric joined20:32
perlpilot Flaghacker: you could try an interactive rebase (I don't see that you're doing anything wrong)20:33
Flaghacker: what version of git are you using?20:33
LiftLeft joined20:33
hasc joined20:33
Flaghacker perlpilot, git version 2.5.1.windows.120:34
jedahan joined20:34
hasc left20:34
Flaghacker I'll an interactive rebase (once I figured out whta that id)20:34
hasc joined20:34
perlpilot Flaghacker: git rebase -i d70f2ca # then just remove the commit that you don't want anymore20:34
Sample joined20:35
perlpilot Flaghacker: It will put you in your editor to edit the commits. Dunno what that's likely to be for you.20:35
gugah joined20:35
reynierpm left20:35
texinwien_ left20:36
perlpilot Flaghacker: random thought ... is your shell eating the ^ somehow?20:36
grawity joined20:36
Flaghacker perlpilot, The one that has ":wq" for save-and-exit. I thought it was Linux thing...20:37
mloy vi/m20:37
User458764 left20:37
perlpilot according to my 15 seconds of googling, ^ is special to cmd.exe in some way20:38
Mindi left20:38
texinwien_ joined20:39
UTAN_dev joined20:40
perlpilot Flaghacker: so ... you could try git rebase --onto "769c251^" 769c251 (or whatever the appropriate quoting is)20:40
Eugene Yup, windows ^ would be it20:40
Flaghacker perlpilot, That would expalian a lot of stuff... I've had problems in the past but I always ended up using a workaround instead.20:40
Eugene : and { are also special20:40
shgysk8zer0_ left20:41
yehowyada left20:41
perlpilot Eugene: what does it do with ^ ? I haven't used Windows in forever. : and { make sense, but I don't have a clue about ^20:41
jimsio joined20:41
griffindy joined20:42
LiftLeft left20:42
Eugene http://www.robvanderwoude.com/escapechars.php20:42
Flaghacker Yes it's rebasing, taking a loooong time yet again.20:42
jeffreylevesque_ left20:42
kritzikratzi kadoban: i’ve just put in on github under the same license now: https://github.com/kritzikratzi/git-forbid20:42
perlpilot ah, they use ^ instead of \ because of the path thing. Makes some sense20:42
Eugene Unless you're using a literal \\!20:42
Or worse, a literal "\\\!"20:43
(Which is \!)20:43
dsdeiz left20:43
Eugene (Maybe?)20:43
Lesson: don't trust cmd20:43
perlpilot I thought the lesson was to use Linux? ;)20:43
Eugene Gods no, linux is way worse about insane made-up standards20:44
If you want a well-documented understandable system, find an old copy of System V Unix and type it in yourself20:44
Bonus points if it was photocopied20:44
perlpilot no love for NetBSD or FreeBSD?20:45
Decorater or even OpenBSD^20:45
robattila256 joined20:45
bvcosta joined20:45
Eugene Their source doesnt' fit in a 3-ring binder20:45
Decorater also anyone got an idea with these issues on git rebase (2.11.0.windows.1) http://public-inbox.org/git/CAHikyLoK-h4tY_rxGikaSSv6AmcrBAXiayDFTtLa44A9qMZDqA@mail.gmail.com/20:45
texinwien_ left20:46
Flaghacker perlpilot, Interactive rebase worked, thanks!20:47
texinwien_ joined20:47
Flaghacker Does anyone happen to know why git rebase would be very slow? It doesn't use that much CPU, memory or disk, it just takes a couple of minutes to fininsh.20:48
Decorater https://github.com/AraHaan/TinyURL an repo where the rebase bugs on as well20:48
_ikke_ Flaghacker: What OS?20:48
Flaghacker _ikke_, Windows 1020:49
perlpilot Flaghacker: You aren't using git over an SMB share are you? (or CIFS, if that makes more sense)20:49
askb joined20:49
Decorater I am using Windows 7 Ultimate SP1 Build 760120:49
x64^20:49
Flaghacker perlpilot, The whole project (including .git etc) is 1.6MB if that's what you're asking.20:50
peterbec` left20:50
_ikke_ Flaghacker: What version of git are you using?20:50
Flaghacker oops I misread SMB as 5MB20:50
_ikke_, git version 2.5.1.windows.120:50
perlpilot Flaghacker: get a better font :)20:50
Wza left20:50
GodGinrai left20:50
Flaghacker And no, perlpilot, it's not on a share.20:50
_ikke_ Flaghacker: You might want to use a newer version. THe maintainer of git for windows ported some part of git rebase to native c, increasing it's performance a lot20:51
peterbec` joined20:51
Mindi joined20:51
Decorater on Windows try to use git v 2.11.0.windows.120:51
MicronXD joined20:51
_ikke_ Flaghacker: Rebase is/was written in bash, causing a lot of forks. In linux, this is cheap, in windows, not so20:51
Decorater and then you will notice some bugs I got with rebase20:51
it is not slow for me, it just has bugs20:51
synthroid joined20:51
peterbec` left20:51
_ikke_ Decorater: What kind of bugs?20:51
Flaghacker Is there an easy way to update git?20:52
moritz depends on your OS and/or package manager20:52
Decorater 1 that if I do git rebase -i -root and on all commits change pick to edit and append ``-S`` to every one that all of the commits get merged20:52
Flaghacker moritz, W10 so no package manager :(20:52
ryant joined20:52
_ikke_ Flaghacker: Just download the latest installer20:52
should be pretty easy20:53
Decorater and then there is another one where if I clone a repo on Windows and not on github desktop and that I placed commits to the repo on github web and then when I rebase to squash the commits to 1 commit (some repos are doing it as a requirement for 1 commit PR's) that all of my commits on the remote (fork in this case) that is linked to an open pull request are discarded and then the pull request is somehow and oddly closed. It is super20:53
Dougie187 left20:53
perlpilot Flaghacker: I found https://git-scm.com/download/win from google :)20:53
MicronXD I'm afraid I'm totally screwed. Is there anyone who's managed to unscrew an accidental `stash pop` during a rebase?20:53
moritz Flaghacker: good news for you: https://chocolatey.org/20:53
peterbec` joined20:53
texinwien_ left20:53
prg3 left20:53
diogenese left20:53
_ikke_ MicronXD: Can you post a !transcript?20:53
gitinfo MicronXD: Please paste (using https://gist.github.com/ or similar) a transcript ( https://git.io/viMGr ) of your terminal session so we can see exactly what you see20:53
Flaghacker moritz, That's look very interesting, I've been wishing for this a long time. I'll check it out, thanks.20:54
fatalhalt_ joined20:54
Tobbi joined20:54
perlpilot MicronXD: *Usually* git saves you from screwing yourself. Have hope!20:54
peterbec` left20:54
moritz Flaghacker: full disclosure, I haven't used it myself, but have come across it in several podcasts and/or blog posts20:54
Decorater yeah unless you need to edit every commit from root to gpg sign them to append -S then it acts up and merges all commits you have to 120:54
moritz (not a windows user)20:54
Decorater (where you lose all the history)20:55
perlpilot Decorater: even then you didn't *lose* history, just made it slightly harder to get to.20:55
fatalhalt left20:55
peterbec` joined20:55
MicronXD perlpilot: is there a way to restore my stash and abort my rebase?20:56
peterbec` left20:56
Decorater yeah, at least I did not do git pull --force it before git log to show the commits and signitures20:56
so then all I had to do was reclone20:56
bvcosta left20:56
perlpilot MicronXD: do what _ikke_/gitinfo said.20:57
peterbec` joined20:57
perlpilot MicronXD: it's harder to tell without a transcript.20:57
MicronXD perlpilot: _ikke_: https://gist.github.com/MicronXD/db55d48f3ad6ac81eaa3bedaa91d860e20:58
perlpilot MicronXD: btw, I've found "git stash pop" annoying, so I tend to "git stash apply" and "git stash drop" separately.20:58
MicronXD: you might want to start doing the same :)20:58
sieve left20:58
_ikke_ MicronXD: I don't think the stash got applied20:59
diogenese joined20:59
_ikke_ MicronXD: You can use git stash list to verify20:59
xissburg joined20:59
Decorater also is there a way I can drop an extra merge commit that is shown on github but not in git?21:00
_ikke_ I think you are just in a regular rebase conflict21:00
Decorater even if I open it in rebase21:00
perohig joined21:00
_ikke_ Decorater: rebase by default never shows merges21:00
snowalpaca left21:00
Decorater hmm could you somehow force rebase to show them though?21:00
snowalpaca joined21:01
_ikke_ --preserve-merges21:01
But if you want to get rid of a merge, then you obviously don't want that21:01
Decorater Well lets say the merge commit does nothing21:01
as a few commits on github has the data it has and well when I got the changes from github it wanted to do an merge commit instead21:02
so essentially that merge commit should be deleteable21:02
oleksiyp left21:02
MicronXD _ikke_: I updated this gist. https://gist.github.com/MicronXD/db55d48f3ad6ac81eaa3bedaa91d860e I see a message reading "stash@{0}: WIP on Settings-Flux-Additions: 4bce9bd Setting-Flux" followed by a list of messages that I presume were generated by the GitHub desktop app21:02
peterbec` left21:02
CussBot left21:02
perohig left21:03
dviola left21:03
peterbec` joined21:03
LiftLeft joined21:04
_ikke_ MicronXD: You can run git rebase --abort to get back to the state before the rebase21:04
jeffreylevesque joined21:04
MicronXD I tried `git stash show -p`, but it's only showing 3 modifications (there were a probably 10-15)21:04
CussBot joined21:04
sieve joined21:04
MicronXD _ikke_: will that restore the stash though?21:04
ryant left21:04
Decorater like the top commit on this screenshot contains all the data that I pushed before it and those commits are also in the screenshot. (The top one should be deleted) http://puu.sh/ugO93/6a195377df.png21:05
_ikke_ MicronXD: git stash pop doesn't drop in case of conflicts21:06
livingstn joined21:06
_ikke_ MicronXD: And in this case, it didn't even apply I believe21:06
thiago left21:06
MicronXD _ikke_: oh thank god21:07
Es0teric left21:07
cdesai left21:07
texinwien_ joined21:08
Es0teric joined21:08
aidalgol left21:08
rt left21:08
_ikke_ Decorater: Did you just sent something to the mailing list?21:08
nettoweb left21:08
Decorater yeah21:08
_ikke_ Note that git for windows has it's own bug tracker21:09
Uesg joined21:09
rt joined21:10
Budyn joined21:10
cdesai joined21:10
_ikke_ https://github.com/git-for-windows/git/issues21:10
Decorater: Or do you believe this is not just related to git for windows?21:10
Decorater I think it is related to git in general21:10
Mof left21:10
finalbeta left21:11
finalbeta joined21:11
exitcode1 joined21:12
Flaghacker I updates to 2.11 and rebase still is very slow. It'll probably be something with my pc I gueess.21:12
_ikke_ alright21:12
Decorater: It would have been better if you included what version of git you are using21:13
Decorater 2.11.021:13
xaviergmail_ left21:13
MicronXD left21:14
_ikke_ Right, but the people reading the mailing list don't read this :)21:14
xaviergmail_ joined21:14
mwfires joined21:15
cagomez joined21:15
MicronXD joined21:16
cdg joined21:16
MicronXD left21:16
snowalpaca left21:16
livingstn left21:16
_ikke_ Decorater: So you do git rebase --root -i, and change everything to edit, and then save+exit, and then everything is squashed?21:16
texinwien_ left21:17
kritzikratzi left21:17
mwfires left21:17
Decorater yes21:17
sieve left21:17
Decorater I do edit to add gpg to the commits21:17
_ikke_ Seems to work for me21:17
mwfires joined21:17
Decorater hmm21:18
matoro joined21:18
_ikke_ I had a repo with 2 commits21:18
did git rebase --root -i21:18
changed both to edit21:18
and it allowed me to edit both commits21:18
and the resulting branch still had 2 commits21:18
(I'm on linux btw)21:18
Budyn left21:19
Budyn joined21:19
Budyn left21:20
[Brain] joined21:20
Budyn joined21:20
ronny joined21:21
Shakeel__ left21:21
Decorater hmm21:23
I see21:23
overlord_tm left21:23
Decorater can you reporduce the clone part too where you placed commits using git web and then when you rebase those that are for an PR that it discards those commits magically?21:24
kexmex left21:24
rmb joined21:26
texinwien_ joined21:27
nothingnew left21:28
synthroid left21:28
cgdub joined21:28
cgdub left21:28
ponyofdeath joined21:29
McKraken_zzzzzMcKraken21:29
ponyofdeath hi, trying to figure out how I can change where my cloned master is pointing to? it seems to be pointing to a branch's ref and i want to change that to track what the remote origin master is.21:29
texinwien_ left21:32
jnavila left21:32
_ikke_ ponyofdeath: How did you determine where it's pointing to?21:32
ponyofdeath did a git ref-list21:34
or just cat .git/config21:34
_ikke_ Just trying to determine what you mean by pointing to21:35
ponyofdeath it seems that when it was cloned it's master was set up to be a branch21:35
_ikke_ master is a branch21:35
le_melomane joined21:35
_ikke_ Just a label pointing to a commit21:35
Phylock joined21:35
_ikke_ ponyofdeath: what does git branch -vv show?21:36
ponyofdeath yes but not it a bit confusing for people wokring that commiting to master on that branch is actually not master on the remote21:36
* master d8ea8f0 [origin/feat/saltmole: ahead 1]21:36
rwb left21:36
rnsanchez left21:36
_ikke_ right21:36
ponyofdeath and now trying to merge master back into that branch21:36
_ikke_ git branch master --set-upstream-to origin/master21:37
ponyofdeath i dont know how to do :)21:37
_ikke_ ^^\21:37
ponyofdeath _ikke_: thanks!21:38
crose left21:39
hagridaaron joined21:39
Gsham left21:40
texinwien_ joined21:40
le_melomane left21:40
v0z_ joined21:40
hagridaaron left21:41
chardan joined21:41
mwfires left21:42
Gsham joined21:43
Budyn left21:43
Electrometro joined21:46
Gsham left21:48
texinwien_ left21:48
seemikehack left21:49
texinwien_ joined21:49
gugah left21:49
sieve joined21:50
ych left21:50
livingstn joined21:50
AciD- joined21:52
tg joined21:52
Flaghacker left21:53
rmb left21:53
texinwien_ left21:54
jedahan left21:54
texinwien_ joined21:56
cagomez left21:56
livingstn left21:57
cagomez joined21:57
sieve left21:58
jedahan joined21:59
sieve joined21:59
sieve left22:01
nickabbey left22:01
chipotle joined22:02
kpease left22:02
MattMaker left22:03
texinwien_ left22:04
durre left22:04
scoobertron left22:05
scoobertron joined22:05
kevwil joined22:06
texinwien_ joined22:07
Shakeel_ joined22:07
shgysk8zer0_ joined22:08
hhee left22:09
Tobbi left22:09
sieve joined22:10
elsevero left22:11
Masber joined22:12
elsevero joined22:12
e14 left22:12
YuGiOhJCJ left22:13
not-an-aardvark joined22:14
sieve left22:15
gitinfo set mode: +v22:15
elsevero left22:17
Uesg left22:17
m4sk1n left22:17
aard_ left22:18
GodGinrai joined22:18
ISmithers joined22:19
orbyt_ left22:19
ych joined22:21
texinwien_ left22:21
Sasazuka left22:21
Sasazuka joined22:23
texinwien_ joined22:23
rgb-one left22:23
dave0x6d joined22:23
oleksiyp joined22:25
Masber left22:25
DARSCODE joined22:26
ash_workz left22:27
madewokherd left22:27
griffindy left22:28
LeBlaaanc left22:30
exitcode1 left22:31
jedahan left22:32
Es0teric left22:32
dan2k3k4 left22:32
v0z_ left22:33
tang^ joined22:33
bcc left22:33
Sasazuka left22:34
Sasazuka joined22:34
ych left22:35
bannakaffalatta left22:35
Abbott left22:35
DARSCODE left22:36
gugah joined22:37
joeco left22:37
joeco joined22:37
d^sh left22:38
d^sh joined22:39
dan2k3k4 joined22:39
cdg left22:40
bcc joined22:42
bcc left22:42
bcc joined22:42
jdl_ joined22:44
exitcode1 joined22:44
cbreak so, when's git switching to sha2 or sha3?22:44
anuxivm joined22:45
joshszep joined22:45
cbreak or are annotated signed tags left out to rot?22:45
Eugene !list22:45
gitinfo [!mailing_list] The mailing list can be reached via [email@hidden.address] You don't need to subscribe to the list, you will always be put in cc on reply. Read archives at http://public-inbox.org/git22:45
Eugene That is a great question for the mailign list ;-)22:45
rwb joined22:45
jdl_ I'm glad I'm not on the malign list!22:46
pfrench joined22:46
cbreak well, I don't really use annotated signed tags22:46
durre joined22:46
jdl_ There is still some work to do before a conversion to SHA256 can be done.22:46
cbreak jdl_: sounds like the git devs are slow :(22:46
jdl_ It is in the works, but not fully baked yet.22:47
Sasazuka left22:47
cbreak sha1 has been suspect for over 5 years22:47
jdl_ I'm not telling them that.22:47
jdl left22:47
Sasazuka joined22:47
jdl_ Or, rather, if they are too slow, they could use your help?22:47
cbreak I doubt that22:47
I'm a C++ dev, I don't do C :)22:48
jdl_ Version, um, 5 of the patch series was posted a day or two ago.22:48
jdl_ nods22:48
aidalgol joined22:48
cbreak but I'd expect the change to not be that big22:48
you'd only have to add a new hashing algorithm, change the repo format on disk and in transit22:48
and maybe add transition code22:48
jdl_ The notion of OID == SHA1 is being fully abstracted out.22:48
cbreak the bigger problem would be that there'd be incompatible repositories22:49
jdl_ You would likely have to commit to a conversion or so. Not sure what the expected path there is yet.22:49
cbreak maybe they make object IDs versioned22:50
git describe already uses a g prefix for git hashes22:50
maybe it'll be h for sha2 or 3 :)22:50
jdl_ Dunno.22:50
nettoweb joined22:50
Sasazuka__ joined22:50
cbreak well, what ever, good to hear they're not deciding to give up on protecting repository integrity22:51
jdl_ They are not.22:51
Sasazuka left22:52
chipotle left22:53
livingstn joined22:53
jnewt left22:53
hahuang65 left22:54
oleksiyp left22:55
pfrench left22:55
pfrench joined22:55
SwiftMatt joined22:55
finalbeta left22:56
finalbeta joined22:56
durre left22:57
livingstn left22:58
orbyt_ joined23:00
livingstn joined23:00
fmeerkoetter left23:01
dragoonis I'm looking to forcibly check out a target branch, but i'm being told I can't due to dirty working tree changes .. I'd like to ignore these and just blow away any dirty changes and take whatever is in the branch23:01
see my command here: https://gist.github.com/dragoonis/6c331414a26e984faa0ec6537728917f23:01
fmeerkoetter joined23:01
tg left23:01
afuentes joined23:02
dragoonis will "git checkout -f " suffice?23:02
metalraiden34 left23:03
venmx joined23:03
ResidentBiscuit left23:05
boubou left23:06
dreiss left23:07
Nerbrun left23:08
AaronMT left23:09
tg joined23:10
nettoweb left23:10
gugah left23:10
nettoweb joined23:11
whaley left23:11
livingstn left23:12
King_Hual left23:12
Phylock left23:14
kevwil_ joined23:16
Narwhaal left23:16
cdown left23:17
jimi_ left23:17
kevwil left23:17
Narwhaal joined23:17
bannakaffalatta joined23:18
ToBeCloud joined23:18
gitinfo set mode: +v23:18
gugah joined23:19
cagomez left23:20
cagomez joined23:20
tertu joined23:22
metalraiden34 joined23:22
gitinfo set mode: +v23:23
tertu quick question: i'm having some trouble seeing remote branches on my local copy of a repo that's on github23:23
cagomez left23:23
cagomez joined23:24
afuentes left23:24
qqx tertu: How are you trying to see them? `git branch`? If so use `git branch -r`.23:25
scoobertron left23:25
scoobertron joined23:26
tertu i still only see master when i do that23:27
xissburg_ joined23:27
Krenair joined23:28
m0viefreak left23:28
jagob left23:28
xissburg left23:28
qqx What does `git config --get-all remote.origin.fetch` show?23:29
publio left23:32
dgonzo joined23:32
tertu +refs/heads/master:refs/remotes/origin/master23:33
sentriz left23:33
dersand left23:33
Gustavo6046 left23:34
sentriz joined23:36
Gustavo6046 joined23:36
kevwil_ left23:36
gugah left23:37
metalraiden34 left23:37
qqx Looks like you used --single-branch when cloning. In which case it's doing what you told it to do.23:38
thiago joined23:38
qqx You should be able to use `git remote set-branches '*'` to reconfigure it to get everything. Then `git fetch` to actually do that.23:39
tertu got it23:39
mablae left23:41
dmj` left23:41
Sasazuka__ left23:41
j7k6 left23:41
dmj` joined23:41
tekniq joined23:41
menip joined23:43
tertu thanks!23:43
DarkPsydeLord left23:44
matsaman left23:45
cwre left23:46
cdg joined23:48
Kaisyu joined23:48
Munt joined23:48
Sasazuka joined23:50
cwre joined23:51
jimsio left23:52
cwre left23:54
cwre joined23:54
Munt Hey folks I've made a big mess of my online git repo. I have a backup of the local git repo before I tried to do a lot of merging and inappropriate commands. Is there a way to just replace the online repo with my local backup ? Would it be reasonable to delete the online repo and recreate it with the backed up local copy ? Maybe there's a better way23:55
chipotle joined23:55
explody left23:56
explody joined23:57
rizonz left23:57
madewokherd joined23:58
chardan left23:59

Logs Search ←Prev date Next date→ Channels Documentation