IRCloggy #git 2022-09-05

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2022-09-05

paddymahoney2 left00:02
Schrostfutz left00:04
nate1 left00:10
Soni left00:11
nate1 joined00:11
g2anj left00:14
nivag joined00:16
The_Blode_ left00:17
rgrinberg left00:19
minimal left00:21
g2anj joined00:29
Soni joined00:36
FinnElija left00:39
gxt left00:39
ghost43 joined00:39
ghost43_ left00:40
b2j left00:40
vertreko left00:40
GNUmoon2 left00:40
b2j joined00:40
vertreko joined00:41
gxt joined00:41
FinnElija joined00:42
ghost43 left00:44
ghost43 joined00:44
twb left00:45
dyamito joined00:52
GNUmoon2 joined00:53
lucasta joined00:57
lucasta left00:57
xv8 left00:58
gas51627 left00:59
hamburgler joined01:02
twb joined01:06
rgrinberg joined01:12
Schrostfutz joined01:18
YellowSuB left01:21
xx left01:30
gsi_ joined01:47
Soni has anyone made a FUSE-based git web interface yet?01:49
gsi left01:50
nate1 left01:51
mackerman FUSE and web is an interesting combination. Most FUSE APIs are file system based.01:54
dyamito i'm working on very large projects recently and finding that git log -S is very slow. are there any suggestions for speeding it up? (other than adding additional filters)01:55
mackerman Soni: At least 9 file system interfaces to git have existed: https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Filesystem_interfaces01:56
Soni mackerman: a webserver is just another filesystem viewer01:56
rama_ joined01:58
lemonsnicks left02:03
mackerman dyamito: Perhaps profile git to find where the limiting factor is for performance. Exactly how is operating system specific.02:03
Put the repo on the fastest disk you have available.02:03
dyamito i'm on an SSD on linux, but given how slow it is i'm thinking it might just be how git is on these size repos.02:05
mackerman Text search in files back to the beginning is going to take a while02:07
nate1 joined02:08
nedbat dyamito: how large is your repo?02:08
Visne left02:08
dyamito ~150k commits, 350k loc02:09
Visne joined02:09
nedbat dyamito: and how long are searches taking?02:11
dyamito usually 2-3 mins02:12
mackerman That is order of magnitude what I expect for that size of database-like activity02:13
nate1 left02:17
rgrinberg left02:19
ghost43 left02:21
ghost43 joined02:21
lemonsnicks joined02:21
Null_A joined02:24
f451 joined02:24
roadie joined02:41
loulou joined02:44
loulou left02:44
loulou joined02:44
keypusher left02:46
keypusher joined02:48
rama_ left02:49
furrymcg1e joined02:51
loulou left02:51
zebrag left02:54
furrymcgee left02:54
rama joined02:55
Schrostfutz left02:56
rama left03:00
nate1 joined03:02
Night_Wulfe left03:03
GNUmoon2 left03:05
vertreko left03:05
GNUmoon2 joined03:06
Guest35 joined03:10
rama joined03:12
Guest35 left03:13
Null_A left03:14
ywnkmn left03:15
ywnkmn joined03:15
rama left03:16
ChmEarl left03:21
Night_Wulfe joined03:21
Night_Wulfe left03:21
fling left03:26
cdown_ joined03:27
fling joined03:27
Night_Wulfe joined03:28
cdown left03:30
cdown_cdown03:30
Night_Wulfe left03:34
rgrinberg joined03:38
Night_Wulfe joined03:38
agowa joined03:40
cdown left03:43
tyson2 left03:44
agowa338 left03:44
rama joined03:44
FH_thecat joined03:45
Null_A joined03:48
rama left03:48
cristiioan joined03:49
igemnace joined03:50
sydbarret joined03:51
sydbarret how can I check which account im connected in ?03:51
in the terminal03:51
im on windows03:51
caveman joined03:51
bookworm git remote -v + git config --list or such03:52
if it's ssh, the ssh config of the host03:52
there's a bunch of places you can configure creds, so it depends03:53
skapata left03:53
cristiioan left03:53
sydbarret im getting repository does not exist03:54
but it does on github03:54
I have 2 different accounts in github03:54
so perhaps im still connected to older one03:55
git remote -v shows correct url03:55
bookworm which is what, ssh or https?03:55
sydbarret https03:55
bookworm and the url has a user part?03:55
or is it just the normal url?03:56
sydbarret it has user name03:56
Null_A left03:58
sydbarret is there a command to disconnect? and then provide the credentials again?04:00
bookworm assuming you are using the git credential helper of Microsoft, that ought to be enough https://github.com/GitCredentialManager/git-credential-manager/blob/main/docs/multiple-users.md04:00
You can check the manpage of the credential helper if there's an easy way to clear the auth04:01
rama joined04:01
cristiioan joined04:04
bookworm sydbarret: and just to make sure, by user part I mean that https://employee9999@github.com/big-company/secret-repo.git (the employee9999 is the user, not big-company04:10
roadie left04:11
sydbarret im not clonning but pushing04:13
rgrinberg left04:13
sydbarret i m using that syntax04:13
but it says04:13
remote: Support for password authentication was removed on August 14, 2021.04:14
remote: Please see https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls for information on currently recommended modes of authentication.04:14
bookworm does your url also contain the password?04:15
sydbarret they changed to a token04:15
i have to create a token now i guess04:15
bookworm better would be to log in with the cred manager linked above, it can do oauth204:16
set that up according to their readme, remove any token/pw parts from the url and it should pip up an auth prompt the first time you try to access the remote04:16
or just use ssh, up to you04:17
_xor left04:18
sydbarret it think its better tojust delete the credentials from windows credential manager04:18
Null_A joined04:18
sydbarret but its unconfortable to do that everytime i have to change users04:18
bookworm if you have a pw part in your url, ypu aren't using it04:18
git literally asks the cred manager for the pw, it doesn't modify the url04:19
sydbarret i dont get it there is no pwd in the url04:19
Skypl left04:19
roadie joined04:20
bookworm then why answer my question if it's there with "it's a token"?04:20
rgrinberg joined04:20
bookworm and the cred manager uses the configured user identity, you don't have to log out if you configured all repos with the user part04:21
sydbarret cred manager wont install04:22
bookworm highly doubtful04:22
it's literally built for windows first04:22
sydbarret Deploying from 'C:\Program Files\Git\mingw64\libexec\git-core' to 'C:\Program Files\Git'. deployment failed. U_U04:22
bookworm and comes by default nowdays with the installer04:22
fix your installation then04:23
sydbarret you mean is the same as the one in windows>?04:23
hqdruxn08__ joined04:23
sydbarret i have that already opened04:23
bookworm eh?04:23
"git for windows" is a fork of git that allows you to use git on windows04:24
else you could not use git there04:24
meaning if you installed git from an exe on your system, fetched from the official website, that was the installer I'm referring to04:25
ywnkmn left04:25
sydbarret we are talking about credentials not git04:25
ywnkmn joined04:25
sydbarret let me ask you this, the cred manager link yhou gave me04:25
bookworm no shit Sherlock... it is bundled in the installer04:25
sydbarret is the one that comes already in windows?04:26
hqdruxn08 joined04:26
bookworm windows doesn't ship either git nor the cred manager core04:26
sydbarret in windows search I already have a credential manager04:26
hqdruxn08_ left04:27
sydbarret when i open it it has web cred and windows cred tab04:27
bookworm yes, assuming you hit all the next buttons on the installer, that's what happens04:27
ikke That's the built-in credential manager04:28
sydbarret i already have this https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac004:28
bookworm ah, not that one no04:28
the git cred manager doesn't have a fancy UI last I checked04:28
hqdruxn08__ left04:29
sydbarret well that one wont install04:29
i sent you the error msg04:29
bookworm that's not an install log output is it? As in when you run the installer (the exe)?04:29
if it is, file a bug04:29
ikke bookworm: the credential manager plugin shipped with git-for-windows uses the windows credential manager04:31
manin891 joined04:31
ikke (still reading backlog)04:31
bookworm that's the pw storage though, the configuration which account to select is still based on the remote url right?04:32
ikke That's one option, but not necessary04:32
credential.username and credential.<url>.username can specify it as well04:33
vdamewood joined04:35
igemnace left04:35
coldmountain joined04:36
bookworm heh, that's missing from the gcm docs04:37
neither in the multi user nor config docs is any mention of that04:37
FH_thecat left04:38
kenanmarasli joined04:39
igemnace joined04:44
zumba_addict left04:46
vyryls joined04:47
gast0n left04:53
coot joined04:54
ferdna left04:55
sydbarret left04:55
cristiioan left04:56
atrigent joined04:56
madewokherd joined05:00
rgrinberg left05:00
^vanessa^vanessa05:01
madewokherd` left05:04
Sulky_ joined05:05
analoq left05:06
Sulky__ left05:07
analoq joined05:08
paddymahoney2 joined05:09
cristiioan joined05:14
Matt|home i have 2 branches.. main with old code and a new one where im doing my current work. i need to do something very different though, so what should i do.. merge the two branches and create a new one?05:17
cristiioan left05:19
FH_thecat joined05:20
bookworm git worktrees / stash / commit with -m 'wip' and then go back to it when you can05:26
any of those will work05:26
Null_A left05:31
paddymahoney2 left05:32
Matt|home ty05:33
paddymahoney2 joined05:34
caveman left05:34
Matt|home hm. how do i see the changes that were made before i make a commit05:34
ah git diff05:35
bookworm git status / git diff05:35
Matt|home thanks yeah05:36
sudoforge left05:37
otisolsen70 joined05:38
otisolsen70 left05:39
otisolsen70 joined05:40
kenanmarasli left05:42
paddymahoney2 left05:44
Null_A joined05:47
srinidhi joined05:51
zeenk joined05:53
Jong joined06:00
wyre_wyre06:02
YuGiOhJCJ left06:07
dvanloon9 joined06:10
rfuentess joined06:12
dvanloon left06:12
dvanloon9dvanloon06:12
atrigent left06:12
atrigent joined06:13
nate1 left06:15
wallabra left06:20
rsx joined06:25
vyryls left06:26
hamburgler left06:30
bigGopher left06:32
arch-angel left06:34
arch-angel joined06:36
codeDude joined06:41
codeDude hello06:41
I found this https://stackoverflow.com/questions/5126765/how-to-get-rid-of-git-submodules-untracked-status06:41
nate1 joined06:41
codeDude I'd like to know if the top answer is correct06:41
Is this the best practice?06:42
vyryls joined06:42
rhe left06:43
codeDude left06:45
FinnElija left06:46
fling left06:46
GNUmoon2 left06:46
FinnElija joined06:46
GNUmoon2 joined06:46
fling joined06:46
nate1 left06:47
OnkelTem joined06:50
rama left06:52
feriman joined06:55
vyryls left06:56
fling left06:59
fling_ joined06:59
DibbTubberOne joined07:02
Anticom joined07:03
RiFo joined07:03
fling_fling07:07
Murr left07:08
Murr joined07:09
Anticom left07:12
OnkelBlade joined07:12
Anticom joined07:13
nate1 joined07:14
Anticom left07:14
Anticom joined07:14
OnkelTem left07:15
vanessa left07:16
rhe joined07:17
nate1 left07:19
pulse left07:20
pulse joined07:20
mexen_ joined07:21
OnkelBlade left07:21
nizzan left07:22
jargan joined07:22
nizzan3 joined07:22
jast left07:22
deepy joined07:23
OnkelBlade joined07:23
carl- joined07:24
Masklin_Gurder joined07:25
hans_ joined07:26
jazzy left07:28
mexen_mexen07:29
mexen left07:29
mexen joined07:29
mncheck joined07:30
Sulky_ left07:30
Quietus left07:32
Quietus joined07:33
erarnitox left07:33
theoceaniscool joined07:34
erarnitox joined07:35
JanC left07:38
JanC joined07:38
enoq joined07:40
wallabra joined07:42
roadie left07:43
vanessa joined07:43
coldmountain left07:46
Jong left07:49
dionysus69 joined07:53
feriman left07:56
bloody left07:56
Misotauros left08:06
Sulky joined08:08
rkta_ joined08:08
rkta left08:08
roadie joined08:08
ywnkmn left08:10
ywnkmn joined08:10
DibbTubberOne left08:11
remyabel2 joined08:11
roadie left08:14
atrigent left08:18
Null_A left08:25
Null_A joined08:26
feriman joined08:30
DaTa left08:30
Anticom left08:34
iamtheranger joined08:34
Anticom joined08:34
jim87 joined08:35
jim87 left08:35
austin987 left08:35
roadie joined08:38
Null_A left08:38
Misotauros joined08:38
roadie left08:46
nwoob joined08:47
k_sze `git stash` seems stuck when I'm trying to stash changes across a few hundred files. What should I do?08:47
oh, nvm08:48
nwoob I have personal access token and in my local repo when I use it to download repo as packages I don't see errors and it works, but in gitlab ci/cd pipeline CI_JOB_TOKEN gives me 40408:48
osse k_sze: if you're on an older git you can consider uprading. git-stash was reimplemented in C and the old shell-based code is legacy08:50
Jong joined08:50
junebug left08:50
osse hmm, that was 2.5 years ago.08:51
Git 2.2208:51
k_sze osse, I have the latest git. And it wasn't stuck after all. I *thought* it was, but it turns out that the console was not moving at all because I accidentally hit ctrl-enter instead of enter.08:51
geirha oh wow, git stash used to be implemented in sh?08:51
nwoob being a member of that repo fixes the issue. But why was it working locally when fetching npm packages via npmrc08:52
osse geirha: lots of things were08:52
even git-commit in the earliest days08:53
git show 86c9cfa0c7a9a6b3b1f9d956084c65164b7b5e4b08:55
ikke git::86c9cfa0c7a9a6b3b1f9d956084c65164b7b5e4b08:56
gitinfo Git web link: https://github.com/git/git/commit/86c9cfa0c7a9a6b3b1f9d956084c65164b7b5e4b08:56
osse rekt08:56
how to blob08:56
ikke oh, it's a blob08:56
osse Bob Loblaw08:57
ikke I don't think it supports linking to blobs by hash08:58
the github interface probably does not even support it08:58
KnoP joined08:58
osse hmm, no. supports treehash/path08:59
which I guess gitinfo does too08:59
git::90bbd502d54fe920356fa9278055dc9c9bfe9a56/contrib/examples/git-commit.sh08:59
gitinfo Git web link: https://github.com/git/git/commits/90bbd502d54fe920356fa9278055dc9c9bfe9a56/contrib/examples/git-commit.sh08:59
osse hmm08:59
remyabel2 left09:00
KnoP left09:01
osse git::90bbd502d54fe920356fa9278055dc9c9bfe9a56:contrib/examples/git-commit.sh09:02
gitinfo Git web link: https://github.com/git/git/blob/90bbd502d54fe920356fa9278055dc9c9bfe9a56/contrib/examples/git-commit.sh09:02
osse there we go09:02
allison_chains left09:04
allison_chains joined09:04
remyabel2 joined09:05
osse geirha: ran it through shellcheck. not bad actually09:05
Jong left09:05
osse but it's been improved a lot after it was deprecated09:06
roadie joined09:07
rkta_rkta09:07
osse ok not that much09:08
DibbTubberOne joined09:08
Murr left09:08
Murr joined09:09
nwoob left09:09
nwoob joined09:11
dyamito left09:12
roadie left09:12
Jong joined09:13
geirha Yeah, it doesn't look that bad. I've seen much worse sh code. If I were to make any changes though, the first would likely be to get rid of those expr calls09:18
ikke geirha: note that git has to work on quite some platforms09:19
So you need to use things that are available broadly09:19
tulpa_ joined09:20
geirha sure, and expr is a mine-field09:21
cristiioan joined09:22
geirha Without looking at the history at that file, I'd guess it started out as a bourne script and slowly evolved to a posix script09:24
given that it's using $() now, it'll also have ${param#pattern} and ${param%pattern} available, which will be much simpler and more efficient than $(expr...)09:27
mbalmer left09:28
xkoncek left09:29
xkoncek joined09:30
samuelb left09:30
mbalmer_ joined09:31
jab416171 left09:34
mbalmer_ left09:36
Sulky left09:37
Sulky joined09:37
osse git::a3e870f2e2bcacc80d5b81d7b77c15a7928a908209:39
gitinfo Git web link: https://github.com/git/git/commit/a3e870f2e2bcacc80d5b81d7b77c15a7928a908209:39
Rashad joined09:39
jab416171 joined09:40
geirha ok, so the bourne style was a ruse09:40
mbalmer_ joined09:40
nwoob_ joined09:41
k_sze left09:41
DibbTubberOne left09:41
Anticom left09:44
nwoob left09:44
Anticom joined09:44
DrowningElysium joined09:45
mbalmer_ left09:50
jinsl left09:50
jinsl joined09:50
OnkelBlade left09:51
TomyWork joined09:54
Anticom left09:55
Anticom joined09:57
remyabel2 left09:57
OnkelBlade joined09:58
john_johnk joined10:00
Anticom left10:01
hayalialialip10:05
vishal left10:09
FH_thecat left10:11
FH_thecat joined10:11
vishal joined10:12
FH_thecat left10:13
FH_thecat joined10:13
remyabel2 joined10:13
FH_thecat left10:15
FH_thecat joined10:15
FH_thecat left10:17
EvilDMP left10:17
FH_thecat joined10:18
EvilDMP joined10:19
Swahili joined10:20
FH_thecat left10:20
roadie joined10:24
UNIX left10:26
OpenSource joined10:28
robo- joined10:34
zmt01 joined10:35
roadie left10:35
bodicceaII joined10:35
vinleod joined10:36
vdamewood left10:36
vinleodvdamewood10:36
johncs7 joined10:36
ninjin_ joined10:36
ddevault_ joined10:36
AndrewYu joined10:37
Tobbi_ joined10:37
finalriposte joined10:37
ninjin_ left10:37
ddevault left10:37
ddevault_ddevault10:37
ninjin_ joined10:37
john_johnk left10:38
Sulky_ joined10:44
Swahili left10:44
nwoob_ left10:44
jab416171 left10:44
feriman left10:44
dionysus69 left10:44
RiFo left10:44
zeenk left10:44
srinidhi left10:44
analoq left10:44
hqdruxn08 left10:44
furrymcg1e left10:44
f451 left10:44
twb left10:44
bremner left10:44
Raito_Bezarius left10:44
hexadecagram left10:44
koolazer left10:44
sa left10:44
krushia left10:44
webstrand left10:44
elastic_dog left10:44
donofrio_ left10:44
hendry left10:44
flying_sausages left10:44
nyuszika7h left10:44
Quack left10:44
gdd1 left10:44
jakesyl____ left10:44
alip left10:44
zachel_ left10:44
tonitch_ left10:44
MrC left10:44
defjam left10:44
Teacup left10:44
ajak left10:44
shokohsc left10:44
Noisytoot left10:44
llh left10:44
realies left10:44
farn left10:44
foul_owl left10:44
mns left10:44
robo left10:44
rewt left10:44
wolfdale83 left10:44
phundrak left10:44
human_g33k left10:44
bodiccea_ left10:44
NightMonkey left10:44
skered left10:44
m1dnight left10:44
CAT_S left10:44
jimklimov left10:44
HelloShitty left10:44
Matt|home left10:44
dharrigan left10:44
hrberg left10:44
rapmoc left10:44
Ajax146 left10:44
mlaga97 left10:44
Coop left10:44
zmt00 left10:44
Oblomov left10:44
johncs left10:44
Andrew left10:44
frojnd left10:44
kaichiuchi left10:44
avar left10:44
ndim left10:44
riposte left10:44
lericson left10:44
magic_ninja left10:44
vancz left10:44
m5zs7k left10:44
alfredb left10:44
Tobbi left10:44
ninjin left10:44
catern left10:44
kilobyte_ch left10:44
leah2 left10:44
johncs7johncs10:44
Tobbi_Tobbi10:44
AndrewYuAndrew10:44
Sulky left10:45
donofrio_ joined10:47
Swahili joined10:49
nwoob_ joined10:49
jab416171 joined10:49
feriman joined10:49
dionysus69 joined10:49
RiFo joined10:49
zeenk joined10:49
srinidhi joined10:49
analoq joined10:49
hqdruxn08 joined10:49
furrymcg1e joined10:49
f451 joined10:49
twb joined10:49
bremner joined10:49
Raito_Bezarius joined10:49
hexadecagram joined10:49
koolazer joined10:49
sa joined10:49
krushia joined10:49
webstrand joined10:49
elastic_dog joined10:49
hendry joined10:49
flying_sausages joined10:49
nyuszika7h joined10:49
Quack joined10:49
gdd1 joined10:49
jakesyl____ joined10:49
zachel_ joined10:49
alip joined10:49
tonitch_ joined10:49
MrC joined10:49
defjam joined10:49
Teacup joined10:49
ajak joined10:49
shokohsc joined10:49
Noisytoot joined10:49
foul_owl joined10:49
llh joined10:49
realies joined10:49
farn joined10:49
mns joined10:49
rewt joined10:49
wolfdale83 joined10:49
phundrak joined10:49
human_g33k joined10:49
NightMonkey joined10:49
skered joined10:49
m1dnight joined10:49
CAT_S joined10:49
jimklimov joined10:49
HelloShitty joined10:49
Matt|home joined10:49
dharrigan joined10:49
hrberg joined10:49
rapmoc joined10:49
Ajax146 joined10:49
mlaga97 joined10:49
Coop joined10:49
Oblomov joined10:49
frojnd joined10:49
kaichiuchi joined10:49
ndim joined10:49
avar joined10:49
lericson joined10:49
magic_ninja joined10:49
vancz joined10:49
m5zs7k joined10:49
alfredb joined10:49
kilobyte_ch joined10:49
leah2 joined10:49
kek_ joined10:49
kek_ hi10:49
m5zs7k left10:49
koolazer left10:49
defjam left10:49
gdd1 left10:49
Noisytoot left10:49
elastic_dog left10:49
realies left10:49
Raito_Bezarius left10:49
foul_owl left10:49
hexadecagram left10:49
llh left10:49
Noisytoot_ joined10:49
m5zs7k_ joined10:49
realies joined10:49
llh joined10:49
defjam joined10:49
foul_owl joined10:50
kek_ I'm about to start a new project/research paper and I like to make a repo for it. There are three parts to it: 1. Latex/the paper itself 2. some code 3. papers. Do you think it's bad practice to actually add the PDFs of the papers to my git repository?10:50
Anticom joined10:50
selckin probably not10:51
gdd1 joined10:51
sa left10:52
jakesyl____ left10:52
hendry left10:53
jakesyl____ joined10:53
sa joined10:54
xx joined10:54
koolazer joined10:54
elastic_dog joined10:54
twb kek_: you mean PDFs of other people's papers?10:54
hendry joined10:54
twb kek_: why can't you just save the URL (arxiv.org or doi: or whatever010:55
tyson2 joined10:55
twb Those links would be in your bibtex already, right?10:55
selckin always good to have a copy10:58
m5zs7k_m5zs7k10:58
kek_ twb, yes - why not? I might edit stuff, highlight things, add notes etc.10:59
twb Only the ideological reason that committing build products is a bit shit11:00
If those PDFs won't change and they're not like 100MB each, it's probably not a big deal in this case11:00
But I once had someone commit the entire Visual Studio install DVD, because "this project only compiles with this exact compiler"...11:01
vyryls joined11:02
Misotauros left11:03
csm3105 joined11:07
Murr left11:08
Murr joined11:09
ghost43 left11:10
ghost43 joined11:11
hexadecagram joined11:14
Raito_Bezarius joined11:16
nate1 joined11:16
cdown joined11:17
nwoob_ On my current branch I have only one commit that I pushed. Now I want to revert it, if I do git revert head~111:19
git says ambiguous argument 'head~1': unknown revision or path not in the working tree.11:19
why is that?11:19
ikke HEAD~111:19
Rashad left11:19
nwoob_ oh, does head has to be in caps?11:20
nate1 left11:20
ikke yes11:20
nwoob_ ok, thanks ikke11:21
kek_ twb, haha11:21
thanks11:21
kek_ left11:22
remyabel2 left11:25
nyah joined11:27
twb left11:27
Anticom left11:29
Anticom joined11:29
Misotauros joined11:30
DaTa joined11:31
ninjin_ left11:38
ninjin joined11:38
madewokherd left11:38
jarganjast11:40
jast nwoob_: I don't think that's what you want though :)11:40
xx left11:41
Assault joined11:42
jast what "git revert HEAD~1" does is reverse the effects of the commit at HEAD~1 and create a new commit from that on top11:42
just to clarify...11:42
!revert11:42
gitinfo That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?11:42
Rashad joined11:43
Assault hi...this is not really a git question, but sort of: I'm trying to write a github cron job that checks out its own repo, appends a line to a text file and then commits and pushes the change back to the repo. Should be possible right?11:43
but im puzzled about how to do the commit and push part. I was thinking of a bash script like this: https://hastebin.com/uqiquliteg.bash11:44
but how do I now run this bash file as the last step of my cron job? Do I just simply add -run: myBashScript.sh11:45
?11:45
jast in principle that looks okay, though "git add ." is a superset of what the "-a" flag for "git commit" does (assuming you're running it from the top level of the repo)11:45
so you don't need both :)11:45
Assault ok ill try11:46
jast and I have no idea what "-run" is in the context of cronjobs. do you have some kind of special interface for defining cronjobs that works differently from a traditional crontab?11:46
LuKaRo left11:48
bremner I guess here "github cron job" is a misnomer11:49
something about github actions?11:49
LuKaRo_ joined11:49
jast if it's github actions, you probably won't be able to do this, unless they have some kind of specialized action to do this kind of thing11:52
that said I've never actually used github actions11:52
mackerman Ask ##github channel if it is GitHub actions11:53
jast also if you do manage to make it work with actions, I suppose in that context no SSH key with push access might be available, so that's something to figure out potentially11:54
coot left11:59
roadie joined12:00
ferdna joined12:01
nyuszika7h I have a repo called foo and a repo called foo-private both checked out in one directory. I want the local main branch to go to foo/main, and the local private branch to go to foo-private/main. I managed to set it up for pulls, but pushes keep going to foo-private/private instead. how do I fix this?12:02
I've done `git branch --set-upstream-to=private/main private` and `git push -u private private:main`12:02
git 2.31.0 btw, in case this is a bug in an older version (I should probably update)12:03
nvm, `git config --global push.default upstream` did it12:04
potash joined12:06
roadie left12:09
antani joined12:11
FatGogeta joined12:12
thiago joined12:12
dskull joined12:13
Assault bremner, yeah, I mean github actions12:14
antani left12:15
vyryls left12:15
vyryls joined12:16
Noisytoot_Noisytoot12:19
xx joined12:20
dcpc007 joined12:21
roadie joined12:21
vyryls left12:23
momomo joined12:24
Visne left12:26
dionysus69 left12:27
Visne joined12:28
cbreak left12:28
zer0bitz joined12:31
cbreak joined12:31
dionysus69 joined12:32
gryffus joined12:36
dionysus69 left12:36
maret joined12:37
cdown_ joined12:37
momomo Is there a way to avoid having to copy and paste on create new branch and first push ?12:38
git push --set-upstream origin remove-continuum-flag-for-sa-links12:38
it should get it in my opinion, it is suggesting it12:39
osse momomo: git push -u origin HEAD12:39
or even @ in recent versions12:40
cdown left12:40
cdown_cdown12:40
cristiioan left12:42
dionysus69 joined12:42
momomo osse even longer12:43
how am I going to remember that12:43
catern joined12:46
osse momomo: ?12:48
is HEAD longer than remove-continuum-flag-for-sa-links ?12:48
osse rubs eyes12:48
ikke git config alias.pushu 'push -u origin HEAD'12:49
git pushu12:49
minimal joined12:50
cristiioan joined13:05
Albright left13:10
Albright joined13:11
madewokherd joined13:13
roadie left13:18
skapata joined13:19
Assault left13:19
tulpa_ left13:21
lucasta joined13:28
adelfino joined13:32
adelfino Hi! Question: is there a command that let me recover changes from past commits? Basically: diff against previous commit, do some changes, and commit changes. Similar to dealing with conflicts13:33
The_Blode_ joined13:35
mfiano left13:35
feriman left13:35
mfiano joined13:36
dionysus69 left13:40
nwoob_ left13:41
cdown_ joined13:41
mackerman adelfino: You may diff against previous commits, revert them which commits a patch that undoes them, or cherry-pick the changes of a commit and apply it somewhere else13:41
f451 left13:41
cristiioan left13:42
roadie joined13:43
shokohsc left13:43
OnkelBlade left13:44
cdown left13:44
cdown_cdown13:44
shokohsc joined13:45
lucasta left13:45
f451 joined13:45
lucasta joined13:46
iomari891 joined13:47
lgc joined13:48
Assault joined13:48
Sulky_ left13:49
mackerman Maybe sketch out a brief history, and describe what you want to do, so we can discuss specifics.13:49
keypusher left13:50
keypusher joined13:53
Assault left13:53
lgc left13:54
roadie left13:55
lucasta left13:58
lucasta joined14:01
FatGogeta left14:02
Visor left14:02
dionysus69 joined14:03
adelfino mackerman, yeah, I thinking a git diff + interactive git apply could work14:03
Not finding an interactive git apply though :P14:03
sa0 joined14:05
adelfino It's okay, I can handle it, thanks for your help14:06
oriba joined14:06
_sa0sin_ left14:08
Rashad left14:10
Visor joined14:12
cristiioan joined14:13
iomari891 left14:16
Visor left14:18
roadie joined14:20
Visor joined14:20
adelfino left14:22
roadie left14:25
Rashad joined14:25
vladoski joined14:26
gas51627 joined14:27
iomari891 joined14:28
gast0n joined14:29
tulpa_ joined14:35
lucasta left14:43
roadie joined14:45
gryffus left14:47
iomari891 left14:47
maret left14:48
iomari891 joined14:50
cristiioan left14:55
rfuentess left14:56
Anticom left15:01
cristiioan joined15:01
anddam I have a repo with two branches, one public one private with stuff that should not go public15:03
vicecea left15:03
vicecea joined15:04
anddam I do occasional merges of private into public and I manually check that the files that have to be private are not committed, I am passing off this repo, how can I guard future maintainer from publishing unwanted files?15:04
ikke anddam: pre-receive hook on the server15:04
anddam I figure the answer is some pre-commit hook,15:04
ikke: oh beated me to my own question15:05
on the server?15:05
ikke yes15:05
anddam no this has to be on the local clone15:05
ikke client-side hooks are optional. If someone would clone the repo again, you'd not have the hooks15:05
roadie left15:05
anddam unless I put it into README.md15:05
to be more clear I was maintaining this for current employer, I am leaving and passing this over15:06
optional is fine as long as I document it and provide the script15:07
public repo is third party on github15:07
dviola joined15:07
Murr left15:08
Murr joined15:09
whatsupdoc joined15:09
roadie joined15:12
csm3105 left15:16
nate1 joined15:17
anddam ikke: any more wisdom for me?15:18
even if it's "drop it, you are doomed"15:18
rgrinberg joined15:18
BrianBlaze left15:19
Kangie joined15:19
nate1 left15:22
BrianBlaze joined15:23
madewokherd` joined15:23
zebrag joined15:25
Assault joined15:26
madewokherd left15:27
dcpc007 left15:27
rgrinberg left15:30
ghost43 left15:32
rgrinberg joined15:32
ghost43 joined15:32
mackerman You are doomed, client side hooks are not reliable as access control15:33
clime joined15:34
feriman joined15:34
rgrinberg left15:34
mackerman Split the public part off to a seperate repo, and restrict access to the private repo15:35
OpenSourceUNIX15:36
coot joined15:43
Assault left15:48
tyson2 left15:48
mncheck left15:48
cdown_ joined15:51
nate1 joined15:53
cdown left15:54
cdown_cdown15:54
RiFo left16:05
OnkelBlade joined16:06
iomari891 left16:09
kenanmarasli joined16:09
rsx left16:10
anddam splitting is easy, the point is then merging off of a different repo16:10
oh wait I can just use local fs and network URIs for remotes16:11
me and $AnotherGuy were sharing tools so we added "private" stuff to the repo, stuff only meant for building or certificates for authentication to internal tools16:12
hays is there a way to collapse a series of embarrassing commits into one? :)16:13
iomari891 joined16:13
anddam then we need to "polish & publish" so we devised to "let's just not push the private stuff"16:13
hays: squashing16:13
ikke !fixup16:14
gitinfo So you lost or broke something or need to otherwise find, fix, or delete commits? Look at https://sukima.github.io/GitFixUm/ for full instructions, or !fixup_hints for the tl;dr. Warning: changing old commits will require you to !rewrite published history!16:14
ikke oh, wrong16:14
!perfect16:14
gitinfo [!postproduction] So, you want to make your commit history look pretty before pushing? http://sethrobertson.github.io/GitPostProduction talks you through how to use 'rebase -i' to do this.16:14
anddam hays: there's the Law of Embarrass Conservation though, the total embarassment won't get less, it's just concentrated in that one commit16:14
hays lol16:14
the commit history shows me slowly learning boto3 from a boto example.. very bad16:15
knowing neither, porting the code16:15
nate1 left16:15
Matt|home left16:16
hays hmm googling shows me maybe the best way is make a new branch and merge --squash into it16:18
mackerman In reality, few people will look at your commits, and fewer will be offended or even care that much.16:19
ikke git rebase -i master16:19
hays mackerman: probably true16:19
Assault joined16:21
tulpa_ left16:21
tulpa__ joined16:21
iomari891 left16:22
rsx joined16:22
Assault left16:25
coldmountain joined16:25
crabbedhaloablut left16:26
hans_ left16:26
crabbedhaloablut joined16:27
hays ikke: clean16:27
cdown_ joined16:30
cdown left16:32
cdown_cdown16:33
feriman left16:34
feriman joined16:35
jazzy joined16:35
Guest70 joined16:36
Betal joined16:37
dionysus69 left16:39
rgrinberg joined16:39
erarnitox left16:39
vladoski left16:40
erarnitox joined16:41
iomari891 joined16:41
ghost43 left16:42
nate1 joined16:42
ghost43 joined16:43
SleePy left16:44
prime- left16:44
astlep550 joined16:44
astlep55 left16:45
justache- joined16:45
Fischmie1 left16:45
SleePy joined16:45
berkay joined16:45
berkay_ left16:45
Linkandzelda left16:46
Henry151 left16:46
_qw left16:46
justache left16:46
Linkandzelda_ joined16:46
iomari891 left16:46
Linkandzelda_Linkandzelda16:47
Fischmie1 joined16:47
_qw joined16:48
iomari891 joined16:48
prime joined16:48
Henry151 joined16:48
tyson2 joined16:51
cdown_ joined16:52
ghost43 left16:53
ghost43 joined16:54
iomari891 left16:54
iomari891 joined16:55
cdown left16:55
cdown_cdown16:55
pulse when i do: git branch --sort=-committerdate -r16:56
wootehfoot joined16:56
pulse is the first line the most recent one16:56
(first line of output)16:56
dtux joined16:56
pulse i want to find the branch with most recent changes16:56
am i doing this right16:56
carl- left16:57
pulse nvm i found git branch -v17:00
Guest70 left17:02
dionysus69 joined17:04
maret joined17:07
Wh0 joined17:08
Murr left17:08
Matt|home joined17:08
Murr joined17:09
coot left17:09
Null_A joined17:19
fling left17:23
ghost43 left17:23
crabbedhaloablut left17:23
ghost43 joined17:24
crabbedhaloablut joined17:24
fling joined17:25
ghost43 left17:26
rgrinberg left17:26
ghost43 joined17:26
dionysus69 left17:29
rgrinberg joined17:30
rgrinberg left17:31
rgrinberg joined17:34
rsx left17:41
ferr_ joined17:41
fercell left17:43
rektide_ left17:44
nate1 left17:44
rgrinberg left17:46
EvilDMP left17:47
iomari891 left17:48
rgrinberg joined17:49
TonyStone left17:50
cristiioan left17:50
TonyStone joined17:51
lucasta joined17:51
nate1 joined17:52
remyabel2 joined17:53
Null_A left17:54
mven left17:57
mven joined17:58
Null_A joined17:59
Null_A_ joined18:00
hamburgler joined18:03
tulpa__ left18:03
dsrt^ left18:03
ChmEarl joined18:03
Null_A left18:03
tulpa_ joined18:04
TomyWork left18:04
ferdna left18:07
igemnace left18:10
hoochmonger joined18:10
FH_thecat joined18:10
dsrt^ joined18:13
velix joined18:13
velix Does anyone know a GIT gui, where I can commit specific lines only? For example, I've added one functions and changed another and I want two commits for these two changes. Sure, lots of copy+paste will do. But I'd love to just commit function 1 and then function 2.18:14
ikke git gui18:14
remyabel2 left18:16
maret left18:17
roadie left18:17
wootehfoot left18:18
maret joined18:18
maret left18:18
maret joined18:19
remyabel2 joined18:19
coot joined18:19
maret left18:21
Assault joined18:21
maret joined18:21
lolok joined18:22
crabbedhaloablut left18:26
Swahili left18:27
crabbedhaloablut joined18:27
crabbedhaloablut left18:28
crabbedhaloablut joined18:28
Wh0 left18:29
Wh0 joined18:29
epony left18:31
tyson2 left18:32
epony joined18:33
bookworm fugitive/ magit18:34
ikke tig18:34
vicecea left18:35
Rashad left18:35
bookworm turtoise ? Or some such18:35
gitextension18:36
vicecea joined18:36
enoq left18:36
Masklin left18:37
erarnitox left18:39
erarnitox joined18:40
Lord_of_Life_ joined18:40
Lord_of_Life left18:41
FH_thecat left18:41
roadie joined18:42
Lord_of_Life_Lord_of_Life18:43
remyabel2 left18:44
puff Good afternoon.18:44
bookworm time appropriate greetings, can we help?18:46
roadie left18:47
cristiioan joined18:47
potash Good afternoon.18:47
puff I was talking to a friend yesterday and he was complaining about how git's CLI doesn't make it easy to analyze the changes from a larger commit.18:48
He wasn't very coherent about what he was having a problem with, I'm still working on that.18:48
bookworm luckily for us there $EDITOR18:48
there's*18:48
puff But one thing that came out of the conversation was that I'm wondering if there's some option to set an environment variable or otherwise be able to pass in commithashA:commithashB other than by typing it on the command line.18:48
bookworm why would you want an env var? You can just expand that in your script in the arg position18:49
or in other words, already exists 🤷‍♂️18:49
it's called basic shell18:49
puff He acutally has no problem with the patch format, etc... though I did try to tell him that some GUI diff tools (meld and intellij idea I think off the top of my head) let you specify a file and play forward/backward.18:49
bookworm: Can you explain that in more detail?18:49
The only git shell I'm aware of is the limited shell for remote access.18:50
bookworm normal™ people eventually get fed up and write git aliases, because no sane™ person would ever type it all out manually18:50
ikke puff: what would a hypothetical env variable like that do?18:50
remyabel2 joined18:51
bookworm you can use whatever expansion you fancy in a git-$whatever script and shove that in your PATH18:51
puff ikke: export COMMITDIFF="commithashA commithashB", and then "git diff" diffs between those commits.18:51
bookworm then git whatever can expand whatever env var make sense for you, do arg validation, defaults etc. It's all just bash or sh or whatever else you want18:52
puff Ah, okay, so you're saying just do it in a shell script.18:52
bookworm or alias, yes18:52
or just use the cli18:52
an env var won't be faster18:52
puff Yeah, that's basically what I was thinking about, writing a shell script that's sort of a stateful git front end.18:52
Though honestly I'd rather write it in python or something.18:53
bookworm ooor, just use your editor18:53
puff How does that solve the problem?18:53
bookworm because you can tell it to open up diffs in tabs / splits / whatever?18:54
remyabel2 left18:54
bookworm and then navigate there from one command invocation18:54
puff That's not solving the problem I'm talking about.18:54
It's not about just viewing diffs of a file from two different commits.18:54
It's about browsing many files in a large commit.18:54
bookworm yeah?18:54
puff Yes.18:55
bookworm $EDITOR can do that18:55
rather effectively18:55
puff I don't see how that applies.18:55
Or to put it another way, it's orthogonal to the problem, at least as far as I can see.18:56
cristiioan left18:57
cristiioan joined18:57
roadie joined18:59
Murr- joined18:59
furrymcg1e try git difftool -d -t meld <commit>19:00
cristiioan left19:00
cdown_ joined19:00
remyabel2 joined19:01
cdown left19:01
cdown_cdown19:01
Murr left19:02
Murr-Murr19:02
Rashad joined19:02
rgrinberg left19:04
dsrt^ left19:04
zeenk left19:05
xaxas left19:05
xaxas joined19:05
coldmountain left19:05
puff furrymcg1e: Yeah, I'm familiar with meld and I love it for visual diffs. Again, that's not what I'm asking about.19:06
roadie left19:07
roadie joined19:07
furrymcg1e git difftool -d compares large commits in browsable directories19:10
puff Yeah, I'm aware. It's really handy, and in general I like meld's UI for complex diffs.19:12
And I did tell my friend to try out diffing with meld.19:12
tuxayo joined19:12
ulmanak joined19:12
puff But some people like the CLI better... frankly so do I, I generally only use meld for complex diffs, or directory diffs (which are certainly complex).19:13
manin891 left19:13
OnkelBlade left19:15
furrymcg1e tig is a very good for text-mode interface for git19:15
roadie left19:15
puff Yeah, it looks neat.19:16
I really have to take another look at magit, one of these days.19:17
pulse left19:18
puff Hm. This web page seems to be implying (but doesn't state explicitly) that if you create a shell script named git-something and put it in your path (and chmod it etc) then "git something" will (presumably as long as there's no standard git subcommand named "something") then run that shell script.19:19
http://thediscoblog.com/blog/2014/03/29/custom-git-commands-in-3-steps/19:20
tuxayo Hi :)19:20
Does anyone know a way to rebase a branch on another one commit at a time and stop when there is a conflict?19:20
I'm rebasing a branch left for a year while the main upstream branch moved on. I rebase month by month (taking the 1st commit of dec, jan, feb, etc) to avoid getting unnecessarily complex conflict that are the merge of multiple conflicting changed.19:20
That make conflict sections too large and too much diverging changes to process at the same time when examining the conflict section.19:20
So I wonder if there is a way to rebase one by one automatically until hitting a conflict.19:20
ikke !imerge19:20
gitinfo https://github.com/mhagger/git-imerge -- a tool to split a large merge with many conflicts into many smaller merges, hopefully each with easier-to-understand small conflicts.19:20
ikke You can choose if the end result is a merge or a rebase19:21
shailangsa left19:22
pulse joined19:22
tuxayo Interesting!19:22
ntz left19:23
ntz joined19:23
tuxayo > figure out exactly which pairs of commits conflict19:24
Great! That does what I wanted via a commit by commit rebase19:24
momomo left19:25
momomo joined19:26
tuxayo Even with a talk to present the tool :)19:28
Thanks ikke !19:28
ikke :)19:28
coot left19:29
Assault left19:35
roadie joined19:41
Guest11 joined19:45
Guest11 left19:46
roadie left19:46
dsrt^ joined19:47
Trieste joined19:47
Jong left19:48
shailangsa joined19:51
remyabel2 left19:51
roadie joined19:55
cdown left19:57
otisolsen70 left20:00
bloody joined20:00
paddymahoney left20:03
m0viefreak joined20:04
Null_A_ left20:09
Null_A joined20:09
srinidhi left20:12
remyabel2 joined20:15
feriman left20:15
Jong joined20:16
momomo I am trying to google but having difficulty finding any quality responses. Are there any closed source, propertiary and commercial licenses for code released on github? It means I want to publish it but to use it you need to contact us and pay first. For any kind of commercial utilization. Personal / private utilization might be ok.20:18
ajak momomo: let's maybe look at it this way: what are you trying to do?20:19
Assault joined20:21
ikke SSPL is a AGPL like license20:21
mir3272 joined20:23
mir3272 after a potential fs corruption, how do I check my working copies are intact? objects is easy (git fsck), but working copies may have delta that would be unrecognised because the metadata like mtime didn’t change20:23
Assault left20:26
ulmanak left20:26
dsrt^ left20:26
chexum left20:28
crabbedhaloablut left20:28
chexum joined20:29
nivag left20:30
ikke mir3272: crude method is rm .git/index && git reset20:30
nivag joined20:30
oriba left20:33
chexum left20:33
chexum joined20:33
V__ joined20:33
crabbedhaloablut joined20:34
ikke I can't find an option for update-index for something like this20:34
m0viefreak maybe git read-tree HEAD?20:35
rgrinberg joined20:35
ikke m0viefreak: that writes HEAD into the index20:35
not the working tree20:36
m0viefreak yes, isn't that the idea?20:36
ikke no20:36
they want to verify the working tree matches the index20:37
crabbedhaloablut left20:37
mir3272 exactly, and without any caching of info20:37
ikke git stores stat info in the index. if the stat info matches, git won't check the contents of the files20:38
m0viefreak ah, yeah then the crude way, or 'git read-tree --empty && git reset' if you don't want to mess around in file-system manually20:38
mir3272 no option to invalidate the cached info?20:38
bambanxx joined20:40
ikke rm .git/index :P20:41
ChmEarl left20:41
hoochmonger left20:42
cweiss07653212 joined20:42
hans_ joined20:42
mir3272 that’s what I thought at first, but it’ll show everything as deleted/added20:43
ZacSharp joined20:43
ikke then run git reset20:44
or git read-tree HEAD20:44
terminaldweller left20:45
cweiss07653212 left20:45
lucasta left20:45
zer0bitz left20:45
Ajax1460 joined20:46
justache-justache20:46
Ajax146 left20:48
Ajax1460Ajax14620:48
crabbedhaloablut joined20:48
Rashad left20:50
terminaldweller joined20:50
cweiss07653212 joined20:55
forgotmynick joined20:55
roadie left20:55
roadie joined20:55
ChmEarl joined20:58
roadie left21:01
ZacSharp left21:04
ldericher not sure if this is the right place to ask ... but does adding a license to a software repository apply it retroactively? like what about the first N commits that don't have a license file?21:05
mackerman ldericher: Ask an IP lawyer21:07
mir3272 not normally; ask the owner for a licence for the old versions21:09
kenanmarasli left21:17
cweiss07653212 left21:21
EvilDMP joined21:21
V__ left21:22
roadie joined21:26
rama joined21:27
Wh0 left21:28
coot joined21:28
llh left21:29
velix left21:30
maret left21:34
roadie left21:35
llh joined21:36
zebrag left21:36
bambanxx left21:40
crabbedhaloablut left21:45
crabbedhaloablut joined21:45
coot left21:52
tuxayo I wonder if I can use git imerge for backporting. (currently I'm just cherry-picking) I think not.21:57
To use imerge it would have to revert hundreds of commits from the upstream branch to get it back to the point the old release branch forked with the upstream branch.21:57
All while keeping applied the commits that one wants to backport. And then when at the point of the fork, we need to apply the patches that the old release branch got since the 1st release/fork at least that part is regular imerge operation.21:57
It might cause to get unnecessary conflicts when undoing patches that the old branch got via backport. Because the patches will be applied again. And then there are dependencies. Like patch 1 is backported and patch 2 depends on patch 1 but isn't yet backported. When backporting patch 2, undoing patch 1 will cause a mess.21:58
Ok so my idea isn't practical. Maybe with matching the commits messages between the upstream and old branch to not undo those already present? That seems very messy.21:58
Anyway, can git imerge be of use for backporting? Could a tool with similar principles be done for backporting or is the problem inherently incompatible?21:58
roadie joined22:01
stewie925 joined22:01
skapata left22:04
nate1 left22:04
skapata joined22:10
cweiss07653212 joined22:12
roadie left22:12
mir3272 left22:23
Murr- joined22:26
ZacSharp joined22:26
Murr left22:28
Murr-Murr22:28
nate1 joined22:30
bigGopher joined22:33
crabbedhaloablut left22:39
Novi left22:39
roadie joined22:39
crabbedhaloablut joined22:39
nate1 left22:41
roadie left22:43
riposte joined22:44
finalriposte left22:45
rgrinberg left22:49
vdamewood left22:50
hans_ left22:52
lucasta joined22:53
ofl^ joined22:57
tulpa_ left23:02
ZacSharp left23:03
gas51627 left23:06
Murr left23:08
Murr joined23:08
Novi joined23:09
m0viefreak left23:10
theoceaniscool left23:11
clime left23:12
stewie925 left23:18
vyryls joined23:19
hoochmonger joined23:20
_vanessa_ joined23:21
lolok left23:22
vyryls left23:23
vanessa left23:23
P1RATEZ joined23:24
ofl^ left23:27
The_Blode_ left23:32
vyryls joined23:33
crundar joined23:34
sudoforge joined23:43
nate1 joined23:47
FinnElija left23:48
Aminda left23:49
FinnElija joined23:49
Aminda joined23:50
roadie joined23:51
LuKaRo_ left23:52
YuGiOhJCJ joined23:56
alfredb left23:57
alfredb joined23:59
agrosant joined23:59
agrosant left23:59
nyah left23:59
LuKaRo joined23:59
Jong left23:59

Logs Search ←Prev date Next date→ Channels Documentation