IRCloggy #git 2022-03-09

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

kadoban joined00:00
Sulky__ left00:00
Saloframes left00:02
austin987 left00:02
winter is there a way to expire reflog entires that are unreachable from all branches, not just the current one? (seems a bit overly destructive otherwise)00:03
or does `git reflog expire` only act on the reflog for the current HEAD, therefore any other branch's reflog isn't touched?00:03
wilz left00:08
Saloframes joined00:09
sa0 left00:09
sa0 joined00:10
bambanxx joined00:10
Tobbi_ left00:13
sa0 left00:14
bertvvvs left00:17
bertvvvs joined00:17
bertvvvs left00:17
hoochmonger left00:18
donofrio joined00:20
wilz joined00:21
Saloframes left00:22
bertvvvs joined00:23
sobkas left00:29
geowiesnot joined00:30
sobkas joined00:30
reprazent joined00:32
vakera_pingveno left00:33
rairden left00:33
Sulky__ joined00:35
sobkas left00:35
kaiseisei joined00:35
sobkas joined00:36
jmcb left00:37
jmcb joined00:37
Sulky_ left00:38
kaiseisei left00:39
kaiseisei joined00:39
kaiseisei left00:40
kaiseisei1 joined00:40
kaiseisei1kaiseisei00:42
R2robot joined00:46
emf left00:47
Xenguy joined00:47
reprazent left00:48
foul_owl left00:48
foul_owl joined00:51
emf joined00:53
sobkas left00:55
reprazent joined00:55
Tangent-Man left00:57
foul_owl left01:00
vdamewood left01:02
dsrt^ left01:03
nattiestnate joined01:03
vdamewood joined01:03
nattiestnate left01:04
kaiseisei left01:05
kaiseisei joined01:06
analoq left01:07
bambanxx left01:11
geowiesnot left01:14
foul_owl joined01:15
kaiseisei left01:15
x88x88x left01:16
kaiseisei joined01:18
kaiseisei left01:18
kaiseisei joined01:19
structoha joined01:21
jstein left01:22
jstein joined01:22
structoha1 left01:24
ThorMojito joined01:28
Yruama left01:30
kaiseisei left01:30
kaiseisei joined01:33
sa0 joined01:35
jmcb left01:37
sa0 left01:40
capn joined01:40
alt-romes joined01:44
bertvvvs left01:44
ThorMojito left01:45
tehenderz left01:46
off^ joined01:46
tehenderz joined01:46
romesrf left01:47
rgrinberg joined01:49
ishutin left01:50
ishutin joined01:51
jstein left01:53
jazzy joined01:56
magic_ninja left01:59
magic_ninja joined02:00
analoq joined02:03
rgrinberg left02:04
rgrinberg joined02:07
nyah left02:08
srinidhi joined02:17
Saloframes joined02:22
vysn joined02:22
emf left02:30
mgedmin left02:30
mgedmin joined02:33
ColdKeyboard joined02:44
alt-romes left02:45
kaiseisei left02:50
kaiseisei joined02:50
Erisa joined02:58
bloody left03:01
tchan left03:05
Jacques joined03:08
saroy joined03:09
tchan joined03:10
nivag left03:14
nivag joined03:15
tehenderz left03:36
tehenderz joined03:36
luke-jr left03:40
irc_user joined03:48
luke-jr joined03:50
led_belly_ left04:05
Jacques left04:06
ThorMojito joined04:08
forgotmynick joined04:15
ThorMojito left04:23
anaveragehuman joined04:35
structoha left04:40
structoha joined04:46
DoofusCanadensis left04:56
mra90 git show --name-only also gives commit message how to get ride of that and make it truly "file name only"?04:56
k8yun joined04:59
vakera_pingveno joined05:04
Betal left05:06
Betal joined05:08
tyson2 left05:16
ferdna left05:23
off^ left05:24
mcpackey joined05:26
ChmEarl left05:27
hbautista joined05:27
analoq left05:30
analoq joined05:32
Thanatermesis left05:36
xkuru left05:38
great_taste left05:38
rgrinberg left05:48
crabbedhaloablut left05:48
crabbedhaloablut joined05:48
Gustavo6046 left05:50
omero left05:51
xkuru joined05:53
Gustavo6046 joined05:56
chenqisu1 left05:59
omero joined05:59
k8yun left06:01
coot joined06:01
mra90 how to return to some entry from git reflog?06:03
just git checkout <hash> ?06:03
madewokherd joined06:04
pulse left06:05
mra90 ok looks like git reset --hard <hash> is the way to go06:06
madewokherd` left06:08
Gustavo6046 left06:10
mra90 I have an issue with gerrit - it says "! [remote rejected] ..." but yet the gerrit review page has been updated oO06:14
CATS left06:17
tejr left06:17
bindu left06:17
szymon joined06:18
bindu joined06:18
tejr joined06:18
Gustavo6046 joined06:25
xkuru left06:27
structoha left06:28
vicecea left06:40
szymon left06:40
vicecea joined06:40
tsujp joined06:44
kaiseisei left06:44
kaiseisei joined06:44
kaiseisei left06:45
xkuru joined06:45
xkuru left06:46
xkuru joined06:47
kaiseisei joined06:47
hendry i have this weird issue where git log is not the same as my `tig` view, is it because of merging? ... -very confused06:47
pyeveryt_ left06:52
forgotmynick left06:55
Betal left06:55
tehenderz left06:58
tehenderz joined06:59
bigGopher left07:00
Intelo joined07:02
skapata left07:02
AnapodoPsalidaki joined07:03
xkuru left07:05
carl- joined07:05
austin987 joined07:08
donofrio left07:16
thiago left07:19
whatsupdoc left07:21
l4s8g joined07:22
khronosschoty question if I git clone -b master --depth=1 --recurse-submodules.. wiil the shallow depth apply to all the sub modules as well?07:23
masoudd joined07:26
ishutin left07:27
l4s8g left07:28
ishutin joined07:29
nazarewk[m] is it just for me or cloning GH repos tops out at 2 MB/s?07:36
mannequin joined07:37
palasso joined07:38
EvilDMP joined07:38
hendry nazarewk[m]: i get similar performance in Singapore on my gigabit line07:39
nazarewk[m] yeah i'm on gigabit, but in EU07:39
maybe it's time to set up some kind of local proxy for GH :D07:40
carl-- joined07:44
carl- left07:47
stats4647 joined07:47
enzo_lim joined07:47
enzo_lim left07:47
sudoforge left07:48
hendry I have a strange issue where git log is showing merge commits. I've tried git log --first-parent --no-merges, but I still see the commits I don't want to see. They are not shown in tig.07:48
enzo_lim joined07:48
enzo_lim left07:49
Enzo_LIM28 joined07:49
hbautista left07:50
Enzo_LIM28 left07:50
vanessa joined07:51
stats4647 left07:51
enzo_lim joined07:57
enzo_lim left07:57
Enzo_LIM joined08:02
Enzo_LIM left08:02
realies2 joined08:03
ColdKeyboard left08:04
ColdKeybo[a]rd joined08:04
realies left08:04
realies2realies08:04
jazzy2 joined08:06
unluckyshrubbery left08:06
vimal joined08:08
jazzy left08:09
jazzy2jazzy08:09
carl-- left08:10
stats4647 joined08:12
sa0 joined08:14
sa0 left08:18
john_johnk joined08:23
sh0ne joined08:23
duxsco joined08:24
Guest84 joined08:29
Guest84 left08:30
vladoski joined08:31
john_johnk left08:34
Furai left08:37
AnapodoPsalidi joined08:38
Haohmaru joined08:39
enoq joined08:39
arch-angel joined08:40
AnapodoPsalidaki left08:41
Furai joined08:42
jmcb joined08:52
fercell joined08:57
kaiseisei left08:59
kaiseisei joined09:00
aLeSD joined09:02
Tobbi_ joined09:03
iomari891 joined09:06
pretty_dumm_guy joined09:06
jmcb left09:07
cliluw left09:09
cliluw joined09:10
ueberall left09:12
ueberall joined09:14
stats4647 left09:15
Guest31 joined09:23
anaveragehuman left09:25
Guest31 left09:25
anaveragehuman joined09:25
crabbedhaloablut left09:26
coot left09:29
crabbedhaloablut joined09:30
john_johnk joined09:35
ishutin left09:39
ishutin joined09:40
john_johnk left09:42
cvmn joined09:44
mra90 left09:51
cdown joined09:53
unluckyshrubbery joined09:59
paul424 joined10:02
AbleBacon left10:02
cvmn left10:03
MajorBiscuit joined10:06
paul424 I changed the project name recently to OpenDungeonsPlus and don't know whwat do I need to change in my config file ,,,10:07
probably url = https://github.com/johndoe/OpenDungeons.git -> url = https://github.com/johndoe/OpenDungeonsPlus.git10:08
right ?10:08
Enzo_LIM joined10:09
Enzo_LIM left10:09
cart_ joined10:10
cdown left10:10
cart_ Is it possible to host my Rust docs froma sub folder in the repo of the code?10:10
enzo_lim joined10:10
RiFo joined10:14
phylaz joined10:15
dob1 if I clone a repository that I don't own, and I change remote of it to a repository that I own, what I am doing ? I am doing something similar to a fork?10:17
romesrf joined10:20
tehenderz left10:22
tehenderz joined10:22
Akiva left10:25
iomari892 joined10:26
austin987 left10:26
iomari891 left10:29
tsujp left10:30
cart_ It tells me that my Repo is private but my published site will be public and I can not find a way to change that. Also the docs do not seem to match up with what I am seeing10:37
menace joined10:39
menace left10:39
menace joined10:39
l4s8g_ joined10:42
lgc joined10:44
kaiseisei left10:46
jazzy left10:51
rkta_ joined10:53
rkta_rkta10:53
faceface join #code10:54
oops10:55
iomari891 joined10:56
iomari892 left11:00
lgc left11:00
bookworm paul424: git remote --set-url origin $url11:02
dob1: a "fork" in the classical sense is just a diverging codebase. Every repo you develop code in breaks from the origin and can be considered a fork11:04
bertvvvs joined11:07
zulutango left11:09
l4s8g_ left11:11
enzo_lim left11:12
menaceDeknos11:13
_vanessa_ joined11:15
coot joined11:15
Luminos joined11:16
wilz left11:17
Intelo left11:17
vanessa left11:18
zeenk left11:21
walterwhip joined11:22
Gustavo6046 left11:22
walterwhip left11:22
l4s8g_ joined11:23
geowiesnot joined11:24
paul424 left11:31
omero left11:32
ishutin left11:34
ishutin joined11:36
vishal left11:43
vishal joined11:45
anotheranother|11:54
enzo_lim joined11:57
enzo_lim left11:59
enzo_lim joined11:59
nyah joined11:59
enoq left11:59
jmcb joined12:00
enzo_lim left12:02
makara left12:04
makara1 left12:04
coot left12:05
coot joined12:05
makara joined12:05
cart_ Is there an easy way to redirect pages to subfolders in github pages?12:06
makara_ joined12:06
tyson2 joined12:08
vitali64 joined12:12
tehenderz left12:13
tehenderz joined12:13
vitali64 left12:16
vitali64 joined12:17
^vanessa^ joined12:20
_vanessa_ left12:23
Jong left12:23
_vanessa_ joined12:24
bambanxx joined12:24
^vanessa^ left12:27
cperrin joined12:27
lpapp joined12:32
cperrin HI. I have an odd problem and I am trying to find out if there is a good solution. I have a git repo where sometimes a release branch is created and during that time commits from the main branch are cherry-picked into the release branch and after the release it gets merged back into the main branch. Now the problem is that when I create a git log12:33
of a range that includes this branch and merge, the cherry-picked commits appear twice, once for the main and once for the release branch. Is there any way to exclude these commits from the log?12:33
lpapp ikke: does glab work for you? I am trying to create a merge request, but I get no warning, but it also does not fill in the assignee, reviewers, label, etc. Instead, it puts things like /label ~mylabel in the description or /assign laszlo.papp12:33
ikke: this is the command I tried using glab mr create -a laszlo.papp -l team_ultraviolet --reviewer joe.biden,vladimir.putin -b my_target_branch -f --fill-commit-body --wip -w12:34
the only thing it does right is picking up the desired target branch.12:34
also, no errors with "failed to find user by name :" or something.12:36
So, the user names are fine, I think.12:36
glab version 1.22.0 (2022-01-10)12:36
tejr left12:37
lpapp `glab auth login` was successful.12:37
cperrin lpapp: I don't think this is the correct IRC channel for you. This is for Git the software not GitLab.12:37
lpapp cperrin: well, ikke suggested it yesterday, so he may know how to use it.12:38
xkr47 joined12:38
lpapp strictly speaking, gitlab is an integral part of the git ecosystem12:38
tejr joined12:38
cperrin Not realy12:38
GitLab is a software that uses Git.12:39
lpapp are you a channel op?12:40
cperrin no12:40
lpapp then, never mind.12:40
bertvvvs lol12:40
OMGOMG lol12:46
cperrin ???12:47
vysn left12:49
cerill joined12:50
Swahili joined12:58
Rashad joined13:00
bloody joined13:01
lpapp left13:04
GeorgeK left13:05
canton7 cperrin, not really: they're entirely separate commits as far as git is concerned: they just happen to look similar13:11
anaveragehuman left13:12
stats4647 joined13:12
Sulky__ left13:13
Willtech joined13:13
Sulky joined13:15
stats4647 left13:17
jstein joined13:18
The_Blode_ joined13:18
masoudd left13:19
The_Blode left13:19
ikke Note that it's not an issue to ask about tools related to git here13:23
cerill left13:25
humanface joined13:27
cperrin canton7: I thought so.13:27
ThorMojito joined13:32
duxsco left13:35
hoochmonger joined13:36
duxsco joined13:37
epony left13:39
Guest5018 joined13:39
Guest5018 left13:40
duxsco left13:44
cart_ left13:44
duxsco joined13:44
aniruddha joined13:44
bigGopher joined13:57
bambanxx left13:58
skapata joined14:03
skapata left14:03
skapata joined14:03
Baphomet left14:04
ishutin left14:04
john_johnk joined14:06
ishutin joined14:07
sh0ne left14:07
gh34 joined14:07
Xenguy left14:09
Oblomov left14:23
otisolsen70 joined14:23
Thanatermesis joined14:23
darkbit joined14:23
john_johnk left14:24
zer0bitz joined14:24
^vanessa^ joined14:25
nickel715 left14:27
sudoforge joined14:27
_vanessa_ left14:28
The_Blode_ left14:32
The_Blode joined14:33
nickel715 joined14:35
bigGopher left14:36
epony joined14:39
pulse joined14:40
sidy joined14:41
m0viefreak joined14:43
WilltechNOD32Admin14:43
o[_] joined14:43
o[_] left14:44
sco1 joined14:44
NOD32AdminWilltech14:44
_vanessa_ joined14:45
Willtech left14:46
zulutango joined14:46
omero joined14:46
Willtech joined14:46
omero left14:47
^vanessa^ left14:48
o[_] joined14:49
Rashad left14:49
o[_] left14:49
omero joined14:52
omero left14:52
o[_] joined14:55
o[_] left14:55
omero joined14:57
omero left14:57
mcpackey left14:58
cperrin left15:02
_vanessa_ left15:05
madewokherd` joined15:08
bigGopher joined15:10
madewokherd left15:11
sa0 joined15:11
rgrinberg joined15:12
humanface left15:12
sa0 left15:16
tehenderz left15:16
tehenderz joined15:17
GNUtoo joined15:18
GNUtoo Hi, does mediawiki:// respects the http.sslVerify parameters?15:18
txtsd left15:19
bambanxx joined15:20
sh4_ left15:20
Thanatermesis left15:23
txtsd joined15:24
rgrinberg left15:25
pyevery__ joined15:26
neilthereildeil joined15:26
neilthereildeil hey guys15:26
i have 2 branches. one is master and the other is based on a tag with a few more commits on top of it15:26
duxsco left15:26
neilthereildeil how can i copy those few changes since the tag into my master branch?15:27
imMute neilthereildeil: you could merge that other branch into master15:27
neilthereildeil how would that be different than rebase?15:27
imMute rebase "replays" the commits as if they were made against master instead of the original base (the tag)15:28
the end result in the files is the same, but the history is different.15:28
neilthereildeil ok so ura saying the dates of those commits are preserved in merge?15:29
Willtech left15:29
duxsco joined15:30
vysn joined15:31
imMute merge preserves the history exactly as it was15:31
neilthereildeil ok so then merge is what i wanna do15:32
imMute rebase recreates the commits. so the committer/commit date on the new ones will be different, but the original author/author date will be preserved.15:32
neilthereildeil how can i specify that i want everything in the source branch AFTER the tag?15:32
imMute you get everything in that branch's history, including stuff before the tag (if it wasn't merged into master already)15:33
Kulrak joined15:33
neilthereildeil ahh thats not what i want15:33
theres only 3 commits after the tag, and i just want those 3 commits15:33
imMute might be best to just cherry-pick those three commits onto the master branch then15:34
neilthereildeil ok15:34
makara left15:34
makara_ left15:34
neilthereildeil would cherrypick preserve commit dates etc?15:34
Thanatermesis joined15:35
imMute it would preserve authorship dates, but new commit date/name would be used. but that's likely what you want even if you don't know it yet15:35
neilthereildeil whats the difference?15:36
makara joined15:36
osse a commit has two timestamps (and two authors). one is fixed forever, the other is updated when cherry-picks etc. occur15:36
duxsco left15:36
makara1 joined15:36
Misotauros joined15:37
neilthereildeil what does git log show?15:37
osse the fixed one15:37
imMute I think most things show the Author name/date (unless it shows both)15:37
neilthereildeil i just want git log output to match15:37
imMute and it's not fixed forever, you can ask to have it changed when doing a rebase/cherry-pick15:37
thiago joined15:38
imMute neilthereildeil: git log shows the author name/date by default. which wont change if you do a rebase or cherry-pick15:38
neilthereildeil ok so authorshipdate = fixed date?15:39
duxsco joined15:39
imMute yes, the author name/date is the "fixed" information that osse was referring to15:39
neilthereildeil ok15:39
imMute if you do 'git show --format=fuller <branch/tag/sha>' it will show you both. if you leave off the --format=fuller it'll only show you the Author15:40
neilthereildeil ok yea see that15:41
so how do i tell cherrypick to take all the commits since a certain commit?15:41
DoofusCanadensis joined15:41
imMute I think you can do 'git cherry-pick <tag>..<last commit>' where <tag> is the tag or commit just before the first commit you want to pick, and <last commit> is the 3rd of the 3 you want.15:42
otherwise you can do 'git cherry-pick <sha>' 3 times - one for each of the 3 commits you want to pick (do the oldest one first)15:42
neilthereildeil left15:43
neilthereildeil joined15:45
neilthereildeil ok lemme try that15:45
jmcb left15:48
OnlineCop !submodule15:49
gitinfo git-submodule is ideal to add subsidiary git repositories to a git superproject when you do not control the subprojects or more specifically wish to fix the subproject at a specific revision even as the subproject changes upstream. See http://www.git-scm.com/book/en/Git-Tools-Submodules15:49
neilthereildeil ok i got a Merge conflict15:50
imMute okay, so one of the commits doesn't apply cleanly. you'll have to fix that conflict yourself and then commit the conflict resolution and the original commit with "git commit"15:51
zer0bitz left15:53
sobkas joined15:53
jumpcutking left15:54
zer0bitz joined15:55
bn_work joined15:56
OnlineCop !vscode15:57
ThorMojito left15:57
taylan joined15:57
OnlineCop Is there a guide to indicate whether any `.vscode/` files should be committed to a repo?15:58
taylan hey all, just out of curiosity: why does 'git reset --hard' not reset the submodule commit being referenced by the parent repo?15:58
imMute taylan: submodules are fucky and have a bad UX.16:00
ThorMojito joined16:00
RiFo left16:00
The_Blode_ joined16:01
DoofusCanadensis OnlineCop: try https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore16:01
rgrinberg joined16:01
The_Blode left16:02
mackerman OnlineCop: Like anything else, if you would share the official version of something with collaborators, it might beling in version control16:03
imMute mackerman: I think the problem is knowing whether or not something needs to be shared.16:04
ThorMojito left16:04
mackerman Or, projects exist that gitignore .vscode because it isn't the official tool and they don't want it committed by accident16:05
HelloShitty left16:06
Dreadnaught joined16:07
Kulrak left16:08
HelloShitty joined16:11
masoudd joined16:11
The_Blode joined16:12
Luminos left16:13
donofrio joined16:14
Luminos joined16:15
ishutin left16:15
The_Blode_ left16:16
Luminos left16:17
neverfindme joined16:17
ishutin joined16:17
OnlineCop To understand this .gitignore: `.vscode/*` should be ignored, but... lines starting with '!.vscode/...' should NOT be ignored?16:17
structoha joined16:17
imMute correct.16:19
"ignore everything in .vscode except these files"16:19
OnlineCop I was merging across submodules and I've now got an untracked `.vscode/c_cpp_properties.json` file showing up. That one should be user-specific and not part of the project?16:19
imMute according to that gitignore project that DoofusCanadensis mentioned earlier, yes, that's correct.16:20
nuh^ joined16:20
vysn left16:21
omero joined16:24
o[_] joined16:25
The_Blode left16:26
duxsco left16:27
duxsco joined16:27
mra90 joined16:27
GNUtoo left16:27
ano left16:27
gxt_ left16:27
chexum left16:27
hololeap left16:27
GNUmoon left16:27
ano joined16:28
GNUmoon joined16:28
gxt_ joined16:28
OnlineCop I wasn't aware there was even a dedicated `gitignore` repo on github.16:28
!gitignore16:28
gitinfo [!gitignore_template] Github has compiled a set of good .gitignore templates, and licensed them very liberally. https://github.com/github/gitignore16:28
hololeap joined16:29
chexum joined16:29
geowiesnot left16:29
avu left16:30
thekingofbandit left16:30
avu joined16:31
thekingofbandit joined16:31
GNUtoo joined16:32
jmcb joined16:34
Codaraxis left16:37
Murr left16:37
Murr joined16:37
rgrinberg left16:37
bambanxx left16:42
otisolsen70 left16:43
vicfred joined16:43
tyson2 left16:43
saroy left16:43
great_taste joined16:43
lungaro can I make a alias for "git push --set-upstream origin XXX" where XXX is the current branch name somehow?16:44
"git push_upstream" or something16:44
humanface joined16:44
igemnace left16:44
Sulky left16:45
Sulky joined16:45
structoha left16:45
OnlineCop !alias16:46
gitinfo You can set up alias to be used by git, see: http://git-scm.com/book/en/v2/Git-Basics-Git-Aliases16:46
ikke lungaro: you can use HEAD or @ to refer to the current branch (assuming you have a branch checked out, not on a detached HEAD)16:47
lungaro alias's dont support arguments or have the ability to get the current branch name... that's why i'm asking.16:47
arch-angel left16:47
lungaro oh. Sweet!16:47
ikke lungaro: they do if you start with a !16:47
lungaro so 'git push --set-upstream @'16:47
OnlineCop When the alias starts with `! git ...` then it runs the full command.16:47
lungaro oops. Thanks16:48
ikke lungaro: you first need to specify a remote16:48
lungaro yeh...16:48
ikke and even without a !, arguments are appended to aliases16:48
imMute lungaro: aliases support arguments, though they're simply appended to the end of the alias16:48
nyah left16:48
OnlineCop I'm actually a fan of the `alias` alias. :)16:49
nyah joined16:49
bambanxx joined16:49
rgrinberg joined16:50
lungaro it says its a bad line in my config. Under [alias] I have this push_upstream = "push --set-upstream @"16:50
OnlineCop Within my .gitconfig_global file, it's: `alias = ! git config --get-regexp ^alias[.] | sed -e 's/^alias[.]\\([^ ]*\\) \(.*\\)/\\1=\"\\2\"/'` so you can then see what other `git alias`-es you have. :)16:50
Remove the double quotes?16:51
lungaro same thing16:51
ikke OnlineCop: you need to at least quote the entire string16:51
And then escape inner quotes16:51
lungaro oh weird, is underscore reserved?16:52
OnlineCop I just did a `grep alias ~/.gitconfig_global` and ^ that was what I had.16:52
ikke It's easier to use git config to set it, not edit the config file directly16:52
OnlineCop True.16:52
vicfred left16:52
rsx joined16:52
lungaro yeah, i guess key's cant' have underscores. Oh well16:53
k16:53
OnlineCop What would that be for lungaro then? `git config --global alias.push_upstream 'push --set-upstream @'` perhaps?16:53
AbleBacon joined16:53
neverfindme left16:53
OnlineCop Looks like underscore is being rejected on mine too.16:54
nyah left16:54
madewokherd` left16:54
nyah joined16:55
lungaro i can remove it, no worries16:55
ikke It's more common to use -16:55
lungaro i have hundreds of lines of bash automating my git workflow. Another function bites the dust16:56
ThorMojito joined16:59
coot left17:02
The_Blode joined17:03
rgrinberg left17:03
john_johnk joined17:04
ThorMojito left17:09
neilthereildeil left17:10
tyson2 joined17:13
Akiva joined17:13
bambanxx left17:13
bambanxx joined17:13
zer0bitz left17:13
stats4647 joined17:14
wowi421309 joined17:14
wowi421309wowi4213017:15
duxsco left17:16
pretty_dumm_guy left17:17
stats4647 left17:18
bambanxx left17:19
pretty_dumm_guy joined17:19
kenanmarasli joined17:20
vysn joined17:23
zer0bitz joined17:25
vladoski left17:25
Haohmaru left17:25
ThorMojito joined17:26
zumba_addict joined17:26
Codaraxis joined17:27
Codaraxis_ joined17:27
madewokherd joined17:27
DoofusCanadensis OnlineCop: there are tools to automate fetching from that gitignore project into your .gitignore file17:27
I have a fish function that lets me do `getignore maven eclipse jetbrains` for work projects17:28
john_johnk left17:29
Codaraxis left17:32
skapata left17:32
k8yun joined17:32
bambanxx joined17:33
bambanxx left17:34
sadtaco joined17:34
sadtaco left17:34
aLeSD left17:35
Akiva left17:35
sadtaco joined17:35
duxsco joined17:36
duxsco left17:37
romesrf left17:37
bambanxx joined17:37
kadobanana left17:38
kadobanana joined17:39
humanface left17:39
stenno joined17:40
stenno good day, assume i create feature branch F from main. i commit FC1 to F. then, MC1 gets committed to main. i am rebasing F onto master so Fs history now looks like MC1->FC1.now i am merging F into main.17:43
will MC1 now appear twice in mains history?17:43
s/master/main/17:44
imMute main and master are two separate branches?17:44
stenno nope, typo17:44
imMute no, MC1 won't appear twice.17:44
stenno great, thanks17:44
imMute because it's already in master. so merging F into master won't consider that commit17:44
stenno thats smart17:45
i assume it works the same for cherry-picking17:45
imMute cherry-picking just copy/pastes a commit17:45
stenno with the same hash17:46
imMute no17:46
stenno oh ok, so it wont work for cherry picking17:46
imMute I'm not sure what you think "won't work" for cherry picking17:47
ThorMojito left17:47
stenno sorry17:47
imMute cherry-picked and rebased commits will not have teh same commit hashes as the originals. because the commits have different parents, so it's impossible for them to have the same hashes17:47
stenno how exactly does git determine if a commit is already in a branch?17:47
thiago if you rebased F onto main, then F's history contains MC117:48
F will be a superset of main and you can fast-forward17:48
arand___ joined17:48
thiago that's what merge will do17:48
darkbit left17:48
stenno if instead of rebasing, i would have cherry-picked MC1, and then merge F into main, would it _then_ be twice in mains history?17:49
jmcb left17:49
imMute if you had cherry-picked MC1 into F and then merged F into main, yes, MC1 will appear twice (because it's two different commits)17:49
stenno gotcha, thanks again17:50
imMute because it's actually MC1' that's in F, not MC117:50
stenno right17:50
thiago if you cherry-pick MC1 into F, then *merge* F into main, it'll appear twice17:50
if you rebase F on top of main before merging, the rebase will drop the MC1 copy17:50
imMute (git people like to use ' as a way to indicate that a commit was rebased / cherry-picked. as it has the same "contents" but the hashes are different, so it helps to differentiate which commit exactly is being talked about)17:51
stenno ohh right17:51
thats quite the important caveat for cherry-picking though that i wasn't really aware of17:52
imMute what is? (just for my own understanding. personally I don't see any "caveats" to using cherry-pick)17:52
stenno this assumes that having that kind of 'duplicate' commits in your history is bad17:53
imMute it's not necessarily "bad" to have duplicated commits, but most people probably try to avoid them17:54
stenno so if F1 and F2 are branched off main, and F1 cherry-picks from F2, then F1 gets rebased + merged into main, now if F2 gets merged into main it will be in mains history twice even if F2 gets rebased onto main first17:55
hm or does it17:55
sorry i am confused lol17:56
imMute if you rebase F2 after merging F1, it will drop the duplicate commit17:56
sa0 joined17:56
stenno oh yeah17:56
so a feature branch should always rebase onto master before merge17:57
imMute eh, maybe, maybe not. depends on what kind of workflow you want17:58
there is no "best" workflow17:58
thiago the best is the one you're most comfortable with and achieves your goals17:58
stenno noted17:58
i guess i will figure this out from using git more17:58
great_taste left18:00
nightstrike how do you do a "git cp" that retains history? There doesn't seem to be a cp subcommand18:01
ishutin left18:03
thiago cp always writes a new commit18:03
it can't not18:03
(sorry for the double negative)18:03
git rebase is a sequence of git cp, but it's smart enough to know when you haven't changed anything up until a point, so it doesn't cp those commits18:04
that's just an optimisation. In ages past, it would rewrite18:04
imMute "git cp" isn't a git command...18:04
arand___ nightstrike: Git does not track moves or copies, but you can use heuristics to make log and diff guess that the new file was a copy since it looks very similar to another one.18:05
thiago $ git config --global alias.cp18:05
cherry-pick18:05
ishutin joined18:05
imMute thiago: ah.18:05
thiago I assume everyone has the same aliases as I do... cp, ci, co, br, sw18:05
imMute thiago: I have all of those except cp. maybe I should add that one lol18:05
nightstrike imMute: that's what I said :)18:05
arand___: that seems like a terrible idea18:06
so if I change my file too much, I lose its history?18:06
thiago yes and no18:06
since there's no history to be kept in the first place (git doesn't track that way), nothing is actually lost18:06
nightstrike well that sounds like a management answer18:06
zebrag joined18:06
DoofusCanadensis if you move a file, try to move it without changes... makes it easier for git to follow18:06
thiago all that tracking is done by the log/blame tools after the fact18:06
so it's entirely possible to convince them that two files actually should be shared history18:07
in practice, yes, you'd "lose" history18:07
imMute nightstrike: it's ony a concern when you rename/copy files. you can modify a file all you want otherwise and it'll never lose history18:07
thiago so my recommendation when renaming or copying a file is that you keep changes to a bare minimum. Preferably no changes.18:07
nightstrike from a user perspective, there's history, and I don't care what magic git does to retain history, but I do expect that it's actually retained18:07
imMute nightstrike: even when you rename a file, the history is never *lost*, it just might take a bit of work on top of what git does to find it18:08
nightstrike I'll take your suggestion, but that's a frustrating, unexpected, and terribly designed feature18:08
DoofusCanadensis possibly18:08
thiago it's one of the features that make Git fast18:09
arand___ nightstrike you have for example a `--find-renames[=<n>]` option to git log, so you can tweak the percent likeness needed for git to show it as a match in that command instance.18:09
thiago one of the core features of Git even, what set it apart from almost everything that came before18:09
great_taste joined18:10
crashrep joined18:10
nightstrike different is not guaranteed to be better18:10
it can be a core git feature that's different than everything else, and still suck18:11
imMute it's not guaranteed to be worse either. but different is definitely a PITA if you're expecting it to be something it's not18:11
thiago sure, it can be different, faster, and an incredibly horrible UX18:12
nightstrike fast also is a funny thing.... remember debian and ssh and their performance improvement?18:12
thiago yep18:12
FFY00_ joined18:13
imMute nightstrike: do you trust the Linux kernel developers?18:14
nightstrike I trust them to make tools that work for them18:14
thiago indeed18:14
nightstrike I do not trust them to make general purpose tools that work for a wide audience, which is what git has become. And I attribute most of my issues with git to that18:14
thiago just look at the number of people who aren't kernel developers and attempt to use Git for deployment, and then complain about files getting overwritten or somesuch18:15
mackerman There is no git cp comamnd, as it would be in effect copying a file to a different name at the OS level, and adding that.18:15
Differently named blob that happens to have the same content.18:15
imMute thiago: you'd have the same problem with SVN (if SVN were cabable of pushing anywhere except the central server)18:16
FFY00 left18:16
arand___ left18:16
arand___ joined18:17
nightstrike svn has "svn cp" :)18:17
DoofusCanadensis then use svn?18:17
nightstrike svn also handles binary files perfectly, which is a big plus for a general purpose tool18:18
I wish I could. But I don't make those decisions on most projects18:18
thiago git handles binary files just fine too18:19
better than text files, TBH18:19
DoofusCanadensis dunno about that18:19
DoofusCan joined18:20
thiago Git was designed by and for Linux (kernel) developers, meaning that for them all files were binary18:21
great_taste left18:21
thiago like renames, diffs are an afterthought18:21
but handling the content is easy: never transform anything, ever.18:21
retrofitting it to make Windows experience moderately tolerable took effort18:22
ThorMojito joined18:23
k8yun left18:23
rgrinberg joined18:24
GNUmoon left18:25
DrowningElysium joined18:25
GNUmoon joined18:25
k8yun joined18:28
ThorMojito left18:28
coot joined18:28
neilthereildeil joined18:29
nightstrike thiago: git doesn't handle binaries well18:32
donofrio left18:33
nightstrike I'm on one project that stores binaries that are hundreds of megs (AI models), and cloning the repo is becoming a non-starter18:33
k8yun left18:33
mackerman git diff has been a tool, since what, pre git 1.0 ? Friendly string tools on top of the blobs has been a thing since the beginning.18:34
thiago it hanbdles binaries very well18:34
the problem is cloning the entire repository18:34
if you did that with SVN, you'd have the same problem18:34
pretty_d1 joined18:34
pretty_dumm_guy left18:34
MajorBiscuit left18:36
Murr left18:36
jmcb joined18:36
Murr joined18:37
___nick___ joined18:37
neilthereildeil left18:38
DoofusCan That's why Microsoft wrote their own VFS layer for Git when they converted their repos to Git... the need to handle massive amount of binaries in the repository18:41
thiago there's nothing wrong with how Git handles binaries. The problem is checking binaries into the repository in the first place.18:42
great_taste joined18:43
rgrinberg left18:43
thiago by design18:43
you may disagree with the design (and a lot of people do), but the fact is that this is the design and, following from there, Git is operating properly18:44
mackerman Microsoft's enormous repo and VFS layer is not for binaries. Its for 300 GB of history of something like 6 million files.18:46
thiago I understand18:47
but again, a different use philosophy18:47
most people wouldn't have checked out the entire 6 million files in the prior VCS, would they?18:47
sa0 left18:48
mackerman No, because most cannot scale that large at all.18:48
DoofusCan mackerman: ah, I misremembered the blog entry then18:51
duxsco joined18:53
iomari891 left18:53
structoha joined19:02
zumba_addict left19:03
bambanxx left19:03
pretty_dumm_guy joined19:05
rsx left19:05
pretty_d1 left19:05
bambanxx joined19:07
bambanxx left19:07
rsx joined19:09
rsx left19:11
crashrep left19:17
Crispy left19:17
___nick___ left19:19
___nick___ joined19:22
bambanxx joined19:23
tyson2 left19:23
ThorMojito joined19:27
ThorMojito left19:27
fflam left19:31
fflam joined19:32
hbautista joined19:35
great_taste left19:35
duxsco left19:36
canton7 joined19:39
arand___ left19:43
fflam left19:44
cdown joined19:46
great_taste joined19:46
fflam joined19:46
ishutin left19:47
ishutin joined19:49
vitali64 left19:52
kenanmarasli left19:53
nightstrike What did Microsoft convert from?19:55
As for binaries in git vs svn, svn handles binary diffs, so dB size is more manageable19:56
DoofusCan TFS19:56
Lord_of_Life_ joined19:56
l4s8g_ left19:56
Lord_of_Life left19:57
Lord_of_Life_Lord_of_Life19:57
Rashad joined19:58
nightstrike Also, thiago, you know you're being pedantic. You know the difference between handling binaries without corruption or some other critical issue and delivering a user experience that is easy and scalable and intuitive19:59
imMute the only intuitive interface is the nipple. everything else is learned.20:01
Crispy joined20:04
nightstrike hah!20:13
sa0 joined20:14
structoha left20:15
hbautista left20:16
sa0 left20:18
___nick___ left20:18
l4s8g joined20:19
tyson2 joined20:19
___nick___ joined20:20
hbautista joined20:21
makara1 left20:26
makara left20:26
makara joined20:27
mannequin left20:27
makara1 joined20:27
ChmEarl joined20:28
bambanxx left20:29
donofrio joined20:34
bindu left20:36
bambanxx joined20:36
bindu joined20:36
otisolsen70 joined20:37
GNUmoon left20:38
john_johnk joined20:39
yuljk left20:40
yuljk joined20:42
bambanxx left20:44
causasui joined20:51
pyevery__ left20:57
john_johnk left20:58
m0viefreak2 joined21:00
m0viefreak left21:00
m0viefreak2m0viefreak21:00
l4s8g left21:01
___nick___ left21:03
xkuru joined21:06
jinsun left21:11
Gustavo6046 joined21:11
sobkas left21:12
bigGopher left21:12
Gustavo6046 left21:12
Gustavo6046 joined21:13
jinsun joined21:15
stats4647 joined21:15
mra90 git run in msys2 on windows changes my line endings!21:16
I also noticed that when I do git status in gitbahs & msys2 it shows different output (different files modified) and those that were modified have line endings changed! WHy is that?21:17
stats4647 left21:20
canton7 mra90, check the output of 'git config core.eol' in both?21:21
mra90 canton7, no output21:21
canton7 Maybe it's being auto-detected incorrectly on msys?21:22
mra90 auto-detected what?21:22
canton7 Try setting it explicitly to either lf or crlf (depending on what line endings you want in your checked-out files)21:22
As in, git bash is auto-detecting it as crlf, and msys is auto-detecting it as lf. Or vice versa I guess, but that would surprise me21:23
aniruddha left21:24
mra90 even so neither one should change the line endings on its own right?21:24
I mean changing line endings of the file21:24
nuh^ left21:25
canton7 No, but... If core.eol = crlf and a file has CRLF line endings in the working copy but LF in the repo, that's not something that 'git diff' would show. But if core.eol = lf, that would be a difference21:26
srinidhi left21:27
mra90 core.eol in my case is not even set21:27
canton7 I'm a little hazy on how exactly git diff and core.eol interact, but I feel like it must be taken into account on some level. And if core.eol is different between your two environments, and you've got a mix of line endings, it wouldn't surprise me if that's causing some fun21:27
mra90, if it's not set, git auto-detects whether you're on Windows or Linux, and sets it appropriately21:27
cdown left21:27
canton7 mra90, my guess is that, since core.eol isn't set, git on msys is auto-detecting that you're on linux, therefore that it should use lf21:28
That's why I suggested setting it explicitly in both msys and git bash21:28
see core.eol in man git-config21:28
gitinfo the git-config manpage is available at https://gitirc.eu/git-config.html21:28
xkuru left21:28
canton7 "Alternatives are lf, crlf and native, which uses the platform’s native line ending. The default value is native."21:29
rgrinberg joined21:30
mra90 hmm autocrlf says -> Set to true if you want to have CRLF line endings in your working directory and the repository has LF line endings.21:30
GNUmoon joined21:30
mra90 does it mean on git coommit, git will convert line endings?21:31
ikke mra90: git add21:32
the conversion happens between the working tree and the index21:33
git has so called smudge and clean filters21:34
bertvvvs left21:35
ikke clean filters happen when git adds things from the workingtree to the index21:35
and smudge filters happen when things are copied in the opposite direction21:35
mra90 ok, ikke how do you explain different status output in msys2 and gitbash?21:43
m0viefreak left21:46
rgrinberg left21:49
dsrt^ joined21:51
romesrf joined21:52
rgrinberg joined21:52
hbautista left21:53
cliluw left21:55
cliluw joined21:56
xkuru joined21:56
ThorMojito joined21:57
ThorMojito left21:57
ishutin left21:59
sa0 joined22:00
ishutin joined22:00
coot left22:01
hbautista joined22:02
junktext_ left22:03
analoq left22:03
hololeap left22:04
junktext_ joined22:04
analoq joined22:05
hololeap joined22:05
madewokherd left22:07
pyeveryt_ joined22:14
hbautista left22:17
xkuru left22:19
canton7 mra90, I tried to explain that before. Have you just tried setting core.eol to the same value in both environments?22:22
I'm off now anyway, good luck! And, maybe, if you ask for help, try listening to the suggestions you get :)22:23
gh34 left22:24
Rashad left22:24
pyeveryt_ left22:25
mra90 canton7, I appreciate your suggestion and will check in a momement. I asked ikke as I was curious if he has some idea as well22:25
phryk left22:27
pyevery__ joined22:28
phryk joined22:28
cdown joined22:29
hbautista joined22:30
xkuru joined22:31
cdown left22:33
Murr left22:36
Murr joined22:37
x_kuru joined22:42
x_kuru_ joined22:43
madewokherd joined22:44
xkuru left22:45
x_kuru left22:47
x_kuru_ left22:48
rgrinberg left22:59
otisolsen70 left23:01
romesrf left23:01
ThorMojito joined23:02
igemnace joined23:02
pizdets left23:02
ThorMojito left23:02
pizdets joined23:04
Anu4 joined23:06
Anu4Anu23:08
OnlineCop mra90: Git bash on my system is found under C:\Program Files\Git\ and within its /etc/ directory, there's a 'gitconfig' file with [core] `autocrlf = true` set. If you check msys2's /etc/ (or whatever) path, does it have any kind of gitconfig file?23:08
Xenguy joined23:11
cebor joined23:11
mra90 OnlineCop, yes it has .gitconfig under /home/username/23:14
but it has autocrlf = false23:14
LuKaRo_ joined23:14
LuKaRo left23:14
OnlineCop Looks like Git Bash and msys2 aren't agreeing on it then.23:15
cebor left23:15
cebor joined23:16
pretty_dumm_guy left23:16
ferdna joined23:16
kadobanana left23:17
mud joined23:18
mra90 OnlineCop, well if both have autocrlf=false then it should be no problem then?23:18
causasui left23:19
vakera_pingveno left23:22
palasso left23:23
Xenguy left23:24
fabs joined23:26
Xenguy joined23:30
madewokherd left23:34
OnlineCop I expect that as long as both get set to the same, that it should take care of the problems that you're seeing.23:37
mra90 it definitely doesn't happen on git add or git commit as I see all files changed in git diff23:41
which suggests me that this is the editor fault but this is unlikely...23:41
vakera_pingveno joined23:43
LuKaRo_ left23:45
LuKaRo joined23:47
ThorMojito joined23:56
ThorMojito left23:57

Logs Search ←Prev date Next date→ Channels Documentation