IRCloggy #git 2021-08-10

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.

2021-08-10

planetcall joined00:00
planetcalls|work left00:04
kingjulian joined00:11
zebrag left00:18
christall joined00:25
christall left00:31
adlternative joined00:33
clime left00:33
shokohsc left00:34
shokohsc joined00:35
kingjulian left00:35
Xenguy joined00:42
nyah left00:45
nyah joined00:47
ninjin joined00:52
BlessJah joined00:55
roadie joined01:01
roadie left01:06
jwillikers left01:10
blahboybaz left01:10
gast0n left01:12
gast0n joined01:12
fjmorazan joined01:15
natechan left01:19
natechan joined01:19
pcarphin joined01:19
planetcalls|work joined01:20
elichai2_ joined01:20
cespare_ joined01:21
jrm2 joined01:21
ketas- joined01:21
milosz_ joined01:21
Xenguy_ joined01:21
Drool joined01:22
cespare_ left01:22
dittid[m] joined01:22
ludovicchabant_ joined01:22
Xenguy left01:22
howdoi_ joined01:22
Xenguy_Xenguy01:22
Milos_ joined01:22
cespare_ joined01:22
mjorgensen_ joined01:22
pizdets_ joined01:22
Misotauros joined01:23
average_ joined01:23
cyberpear_ joined01:23
kurtthem1ker joined01:23
irrgit_ joined01:23
fjmorazan_ joined01:23
t3nj1n_ joined01:23
hgl- joined01:24
debsan joined01:24
charly_ joined01:24
fflam_ joined01:25
ackyshake left01:25
pcarphin1 left01:25
planetcall left01:25
elichai2 left01:25
ketas left01:25
ludovicchabant left01:25
jrm left01:25
cespare left01:25
Droolio left01:25
mjorgensen left01:25
average left01:25
pizdets left01:25
Lord_of_Life left01:25
hgl left01:25
Milos left01:25
Misanthropos left01:25
bn_work left01:25
cyberpear left01:25
howdoi left01:25
fjmorazan left01:25
kurtthemaker left01:25
t3nj1n left01:25
paruh left01:25
irrgit left01:25
HumanG33k left01:25
cambrian_invader left01:25
pretty_dumm_guy left01:25
BUSY left01:25
milosz left01:25
fflam left01:25
charly left01:25
elichai2_elichai201:25
jrm2jrm01:25
ludovicchabant_ludovicchabant01:25
howdoi_howdoi01:25
average_average01:25
Jonno_FTW left01:25
cyberpear_cyberpear01:25
Jonno_FTW joined01:25
Lord_of_Life joined01:25
BUSY joined01:25
pretty_dumm_guy joined01:25
bn_work joined01:25
cambrian_invader joined01:25
ackyshake joined01:26
paruh joined01:26
human_g33k joined01:27
eternalromance joined01:28
Strom left01:34
Strom joined01:36
odoood joined01:37
pretty_dumm_guy left01:46
howdoi left01:50
gnoo joined01:54
jazzy joined02:00
Milos_Milos02:09
hbautista joined02:15
rewrit3 left02:17
rewrit3 joined02:20
Izem joined02:24
vysn left02:25
christall joined02:28
zumba_addict joined02:28
finn_elija joined02:28
FinnElija left02:28
finn_elijaFinnElija02:28
vdamewood joined02:29
bambanxx joined02:31
AnAverageHuman left02:36
vinleod joined02:37
christall left02:37
vdamewood left02:40
durham joined02:42
AnAverageHuman joined02:42
paddymahoney joined02:45
durham left02:46
eternalromance left02:51
arxanas joined02:52
arxanas left02:52
arxanas joined02:53
arxanas left02:53
ash_worksi joined02:55
beencubed joined02:57
Izem left03:00
roadie joined03:02
roadie left03:07
Crispy left03:07
Crispy joined03:08
vinleodvdamewood03:08
roadie joined03:09
pulse left03:10
Bombe joined03:23
planetcall joined03:25
planetcalls|work left03:29
durham joined03:33
cespare_ left03:36
cespare joined03:36
durham left03:37
clime joined03:45
odoood left03:53
fjmorazan_fjmorazan03:59
Hax0r left04:02
fling left04:03
ferdna joined04:06
igemnace left04:07
bambanxx left04:08
bambanxx joined04:09
bn_work left04:09
hbautista left04:12
hbautista joined04:12
zumba_addict left04:12
durham joined04:16
odoood joined04:20
durham left04:21
roadie left04:22
planetcalls|work joined04:25
planetcall left04:29
igemnace joined04:31
mci64 joined04:31
chovy joined04:32
mci64 left04:32
chovy i need help04:32
my tech lead merged my PR and then reverted it. now all the code is issing ont he branch04:32
missing*04:32
how do i get it back?04:32
odoood left04:33
ikke What do you mean with source missing on the branch?04:33
Merging a branch and reverting it does not affect the branch at all, at most, it affects the branch that it was being merged04:34
If you try to create another PR from the same branch, than it's correct that you do not see any new changes04:34
What you can do is rebase your branch on the latest version of the target branch04:35
YuGiOhJCJ joined04:40
christall joined04:41
ByteHackr joined04:44
christall left04:46
lightstalker left04:47
bam32_ joined04:47
roadie joined04:48
mci64 joined04:49
blahboybaz joined04:50
bam32 left04:50
roadie left04:54
shokohsc left05:00
shokohsc joined05:01
debsan left05:01
roadie joined05:02
vishal left05:05
vishal joined05:07
mci64 left05:08
bambanxx left05:08
mci64 joined05:10
adlternative left05:17
Shentino joined05:17
adlternative joined05:17
planetcall joined05:25
AnAverageHuman left05:25
planetcalls|work left05:29
Xaldafax left05:37
FH_thecat joined05:47
roadie left05:48
blahboybaz left05:50
ferdna left05:56
ByteHackr left06:01
ByteHackr joined06:03
snappy left06:04
snappy joined06:04
Shentino left06:05
hbautista left06:11
gast0n left06:13
planetcalls|work joined06:25
ham left06:28
Lord_of_Life_ joined06:28
planetcall left06:29
Lord_of_Life left06:29
Lord_of_Life_Lord_of_Life06:31
zmt00 left06:31
EvilDMP joined06:34
thiago left06:36
ham joined06:36
SirRippovMaple joined06:39
rfuentess joined06:56
tirnanog joined06:58
bam32_ left07:00
velo left07:02
velo joined07:04
unluckyshrubbery left07:04
palasso joined07:11
OnkelTem joined07:15
AbleBacon left07:15
kaisyu joined07:18
randomuser joined07:20
planetcall joined07:25
xx joined07:27
vysn joined07:28
planetcalls|work left07:30
christall joined07:30
ham2 joined07:31
lgc joined07:31
ham left07:32
caveman left07:32
caveman joined07:32
christall left07:35
christall joined07:36
alkino joined07:37
bam32_ joined07:39
christall left07:40
reset left07:41
eamanu left07:44
eamanu joined07:45
bam32_ left07:45
mat001 left07:51
bam32_ joined07:53
Shentino joined07:54
mbalmer joined07:54
mbalmer_ left07:57
Anticom joined08:00
roxlu I'm using gitk with a i3 (linux, tiling window manager) and every time I open gitk I have to drag the columns of the author/date to make them visible. Someone around who knows if there is a fix for this?08:13
ksynwa joined08:14
durham joined08:18
skapata left08:21
durham left08:22
adlternative left08:22
adlternative joined08:23
planetcalls|work joined08:25
planetcall left08:29
gnoo roxlu: i3 has a similar problem with imagemagick, last i saw, they refused to fix it.08:34
roxlu is it a i3 issue? I thought it was more likely something in gitk08:36
alkino left08:44
theoceaniscool joined08:50
Betal left08:51
t_unix[m] joined08:58
t_unix[m] hi08:58
davve_ does floating the window fix it?09:00
i3 supports float by wm class I think09:00
randomuser left09:01
t_unix[m] does git support some kind of global configuration to automatically use reference repositories (https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---reference-if-ableltrepositorygt) if the remote url matches some pattern?09:04
unluckyshrubbery joined09:07
almarwazi joined09:09
almarwazi left09:09
almarwazi joined09:10
hnOsmium0001 left09:12
mbalmer_ joined09:15
mbalmer left09:16
nyah left09:20
nyah joined09:24
tolot joined09:26
t_unix[m] just to be sure: this is the "git scm" users channel, correct?09:26
j416 t_unix[m]: you're in the right channel.09:27
kaisyu left09:28
enoq joined09:32
enoq hi, are tags bound to a branch?09:32
like can you have the same tag in different branches09:33
ikke no09:33
tags are global09:33
enoq thanks09:34
Nomikos "source code management" TIL09:39
j416 enoq: you can print a raw tag with git cat-file; you'll see that it references a commit hash09:40
enoq: git cat-file -p tagname09:41
enoq yeah, that's what I've figured as well09:41
my company has a weird tag/branch/release strategy though09:41
j416 enoq: if it's a tag object (annotated tag).09:41
enoq like 4 branches for develop, acceptance, integration and production09:41
j416 enoq: if it's not annotated, it's just a reference (similar to a branch name) to a commit hash09:41
randomuser joined09:42
enoq j416: where do I find that annotation09:43
j416 enoq: man git-tag look for -a09:44
gitinfo enoq: the git-tag manpage is available at https://gitirc.eu/git-tag.html09:44
j416 -a means create a tag object, without -a it's just a ref09:44
FH_thecat left09:44
enoq so git tag XXX creates a non annotated tag09:44
j416 yes09:44
enoq ok, thanks09:44
j416 I'd avoid that09:45
enoq so technically it's a commit message for a tag09:45
j416 enoq: if you see that a tag has its own hash (git show yourtag), then it's an annotated tag09:45
enoq: technically it's a tag object which in turn references a commit09:45
or any other object for that matter (you can tag any object)09:45
enoq ok, and that object contains the message right?09:46
j416 yes09:46
enoq thank you09:46
Marmotte also, tags are global (refs/tags) while branches are by repo (refs/heads and refs/remotes/remote_name)09:47
ikke remote tracking branches are by repo (remote)09:48
Oddly joined09:48
christall joined10:04
christall left10:09
christall joined10:10
j416 Marmotte: I think by that you mean that they are automatically created by default on fetch10:10
Marmotte: or?10:10
christall left10:14
kikijiki joined10:19
rewrit3 left10:20
furrymcgee joined10:21
reset joined10:28
blaisebool joined10:33
osse tsdh: Nice!10:36
shailangsa left10:37
austin987 left10:39
palasso left10:47
tsdh osse: Your prediction about the test was exactly right and made me discover that type parameter declarations and arrays in return types weren't recognized, too.10:49
austin987 joined10:57
rewrit3 joined11:02
nyah left11:02
ano left11:07
shailangsa joined11:12
nyah joined11:12
kingjulian joined11:15
ano joined11:21
Zubin joined11:22
pulse joined11:31
christall joined11:31
christall left11:34
lgc left11:38
michele_ joined11:42
ThorMojito1 joined11:43
roman joined11:43
DrowningElysium_ joined11:44
Manouchehri_ joined11:44
wyre_ joined11:44
pupskucheen joined11:44
bingos_ joined11:44
reillybrogan_ joined11:44
terrorjack4 joined11:45
spaceplo_ joined11:45
noord_ joined11:45
jwillikers joined11:45
polyrob_ joined11:46
indy_ joined11:46
ndorf_ joined11:46
PinealGl1ndOptic joined11:46
foo_ joined11:47
MrBenC joined11:47
MrC left11:47
MrBenCMrC11:47
BinGOs left11:47
bingos_BinGOs11:47
BinGOs left11:47
BinGOs joined11:47
francis_ joined11:47
OMGOMG joined11:47
imMute^ joined11:48
magic_ninja1 joined11:48
ericnoan_ joined11:50
guardian` joined11:50
terrorjack4 left11:50
leib joined11:51
kingjulian left11:51
terrorjack7 joined11:51
velo left11:51
tirnanog left11:51
vdamewood left11:51
Samian left11:51
t_unix[m] left11:51
silvio[m] left11:51
sa left11:51
bdeshi left11:51
dob1 left11:51
Arokh left11:51
phroa left11:51
s1b1 left11:51
axisys_ left11:51
imMute left11:51
przemoc86 left11:51
elibrokeit left11:51
earthbreaker left11:51
FFY00_ left11:51
guardian left11:51
treefrob left11:51
lucerne left11:51
reillybrogan left11:51
DrowningElysium left11:51
Manouchehri left11:51
indy left11:51
keypusher left11:51
wolfdale left11:51
hendry left11:51
mweckbecker left11:51
avar left11:51
jsatk left11:51
jkl left11:51
Bombe left11:51
jazzy left11:51
TJ- left11:51
bodiccea left11:51
lechner left11:51
ThorMojito left11:51
leah2 left11:51
unclechu left11:51
ringo_ left11:51
reprazent left11:51
PinealGlandOptic left11:51
geirha left11:51
harv left11:51
itok left11:51
daddy left11:51
fingercomp left11:51
derfj left11:51
tofran left11:51
circuitbone left11:51
m1dnight left11:51
hquirinosmith left11:51
strudl left11:51
jiffe left11:51
yuljk left11:51
shored1 left11:51
gitinfo left11:51
blaisebool left11:51
reset left11:51
navidr left11:51
tuxayo left11:51
Ody[m] left11:51
cpackham[m] left11:51
cmn left11:51
energizer left11:51
berndj left11:51
colona left11:51
Soliton left11:51
foo left11:51
bket left11:51
SpacePlod left11:51
yksi left11:51
ElKowar549 left11:51
Jck_true left11:51
Timvde left11:51
jor left11:51
rossome left11:51
SleePy left11:51
mackerman left11:51
niyawe left11:51
catern left11:51
zmotaj left11:51
ServerStatsDisco left11:51
s0dyy[m] left11:51
zfnmxt left11:51
morguldir left11:51
AnisBarghouthi[m left11:51
happy-dude left11:51
elemongw[m] left11:51
Ekho left11:51
LogicAside left11:51
dmc left11:51
greyrat left11:51
seanBE left11:51
chemsmith left11:51
nuala left11:51
ikke left11:51
andreas3- left11:51
splud left11:51
Tykling left11:51
frobnic left11:51
soifou left11:51
Ragnor left11:51
sitaramc_ left11:51
teddyc left11:51
polyrob left11:51
rudi_s left11:51
obiwahn left11:51
rapha left11:51
xD- left11:51
ndorf left11:51
Puyo left11:51
ericnoan left11:51
LordLion left11:51
cation left11:51
nesmysl left11:51
michele left11:51
tkazi left11:51
dustinm left11:51
noord left11:51
mirai left11:51
Quack left11:51
bencevans left11:51
FLHerne left11:51
CommunistWolf left11:51
reillybrogan_reillybrogan11:51
fstd_ left11:51
jimklimov left11:51
magic_ninja left11:51
g2anj_ left11:51
casaca left11:51
Black left11:51
i7c left11:51
niluje left11:51
terrorjack7terrorjack11:51
francis_francis11:51
indy_indy11:52
DrowningElysium_DrowningElysium11:52
Manouchehri_Manouchehri11:52
wyre_wyre11:52
polyrob_polyrob11:52
pupskucheenpupskuchen11:52
pupskuchenpupskucheen11:53
t_unix[m] joined11:53
velo joined11:53
tirnanog joined11:53
vdamewood joined11:53
Samian joined11:53
silvio[m] joined11:53
sa joined11:53
bdeshi joined11:53
Arokh joined11:53
dob1 joined11:53
phroa joined11:53
axisys_ joined11:53
przemoc86 joined11:53
elibrokeit joined11:53
earthbreaker joined11:53
FFY00_ joined11:53
lucerne joined11:53
keypusher joined11:53
wolfdale joined11:53
hendry joined11:53
mweckbecker joined11:53
avar joined11:53
jsatk joined11:53
jkl joined11:53
dfg joined11:53
tonitch joined11:53
fructose joined11:53
jpnurmi joined11:53
Celelibi joined11:53
ch joined11:53
dupondje joined11:53
mgedmin joined11:53
dfg left11:53
dfg joined11:53
dfg left11:53
dfg joined11:53
pupskucheenpupskuchen11:54
psydroid left11:55
Helmholtz left11:55
heftig[m] left11:55
ronny left11:55
dittid[m] left11:55
kadoban left11:56
pinage404 left11:56
viral_mutant[m] left11:56
Rubin left11:56
t_unix[m] left11:56
silvio[m] left11:56
dieggsy left11:56
charly_charly11:57
fstd_ joined11:57
jimklimov joined11:57
g2anj_ joined11:57
casaca joined11:57
Black joined11:57
i7c joined11:57
niluje joined11:57
Peng joined11:57
Arsen joined11:57
fsg joined11:57
xkr47 joined11:57
extor joined11:57
hinderaker joined11:57
bkhl joined11:57
bookworm joined11:57
ecs joined11:57
jle joined11:57
raghavgururajan joined11:57
joj_ joined11:57
Frogging101 joined11:57
mspe joined11:57
Bilge joined11:57
Seveas joined11:57
ThiefMaster joined11:57
Eustachy_Kapusta joined11:57
Exa joined11:57
Bombe joined11:57
jazzy joined11:57
TJ- joined11:57
bodiccea joined11:57
lechner joined11:57
leah2 joined11:57
ringo_ joined11:57
reprazent joined11:57
geirha joined11:57
harv joined11:57
itok joined11:57
tofran joined11:57
fingercomp joined11:57
derfj joined11:57
circuitbone joined11:57
m1dnight joined11:57
hquirinosmith joined11:57
strudl joined11:57
jiffe joined11:57
yuljk joined11:57
shored1 joined11:57
gitinfo joined11:57
sunyibo joined11:57
AACIKF joined11:57
qsx joined11:57
AlexKalopsia joined11:57
mw_ joined11:57
Peng_ joined11:57
mx08 joined11:57
ephemer0l joined11:57
bin joined11:57
yourfate joined11:57
simon816 joined11:57
calcium.libera.chat set mode: +o11:57
tofran left11:57
zfnmxt joined11:57
morguldir joined11:57
AnisBarghouthi[m joined11:57
happy-dude joined11:57
elemongw[m] joined11:57
Ekho joined11:57
LogicAside joined11:57
greyrat joined11:57
seanBE joined11:57
chemsmith joined11:57
nuala joined11:57
ikke joined11:57
andreas3- joined11:57
splud joined11:57
Tykling joined11:57
Ragnor joined11:57
frobnic joined11:57
soifou joined11:57
sitaramc_ joined11:57
teddyc joined11:57
rudi_s joined11:57
obiwahn joined11:57
rapha joined11:57
xD- joined11:57
Puyo joined11:57
LordLion joined11:57
cation joined11:57
tkazi joined11:57
dustinm joined11:57
mirai joined11:57
Quack joined11:57
bencevans joined11:57
FLHerne joined11:57
CommunistWolf joined11:57
Fusl joined11:57
anddam joined11:57
marw joined11:57
stark joined11:57
Dragoon joined11:57
selckin joined11:57
dodo joined11:57
wacko joined11:57
catbeard joined11:57
nsh joined11:57
RichiH joined11:57
eldritch_ joined11:57
happy-dude left11:57
blaisebool joined11:57
navidr joined11:57
tuxayo joined11:57
yksi joined11:57
cmn joined11:57
energizer joined11:57
colona joined11:57
berndj joined11:57
Soliton joined11:57
bket joined11:57
ElKowar549 joined11:57
Jck_true joined11:57
quesker joined11:57
infernix joined11:57
Timvde joined11:57
jor joined11:57
rossome joined11:57
SleePy joined11:57
catern joined11:57
zmotaj joined11:57
mackerman joined11:57
niyawe joined11:57
rkta joined11:57
waterkip joined11:57
phylaz joined11:57
vodkra joined11:57
Henry151 joined11:57
wolf joined11:57
n-st joined11:57
limon joined11:57
shalok joined11:57
barlas joined11:57
Soni joined11:57
davidfetter joined11:57
n-st left11:58
treefrob joined11:58
tofran joined11:58
n-st- joined11:58
dmc joined11:58
n-st-n-st11:59
daddy joined11:59
reset joined11:59
zfnmxt left12:00
morguldir left12:00
AnisBarghouthi[m left12:00
elemongw[m] left12:00
tuxayo left12:01
Guest526 left12:01
lasr[m] left12:01
cameron[m] left12:01
Industrial[m] left12:01
Vipulk left12:01
smuise[m] left12:01
s1b1 joined12:01
Dragoon left12:02
mbalmer_ left12:03
Dragoon joined12:04
christall joined12:05
leib left12:05
leib joined12:06
viral_mutant[m] joined12:07
dittid[m] joined12:07
christall left12:09
leib left12:14
christall joined12:16
natrys joined12:16
bam32 joined12:19
dviola joined12:19
durham joined12:19
mat001 joined12:20
ronny joined12:21
heftig[m] joined12:21
bam32_ left12:21
durham left12:24
adlternative left12:27
AnAverageHuman joined12:36
filePeter joined12:36
christall left12:37
Arokh left12:44
Arokh joined12:45
kingjulian joined12:48
danisanti joined12:49
FFY00 joined12:50
danisanti Now there is a git channel for git translators. It is the #git-l10n channel12:50
christall joined12:52
FFY00_ left12:52
adlternative joined12:54
randomuser left12:54
eternalromance joined12:56
Industrial[m] joined12:56
lasr[m] joined12:56
unclechu joined13:01
psydroid joined13:04
kingjulian left13:04
Ody[m] joined13:05
cpackham[m] joined13:08
durham joined13:09
AnisBarghouthi[m joined13:10
t_unix[m] joined13:12
travisghansen left13:13
ServerStatsDisco joined13:14
travisghansen joined13:15
Vipulk joined13:16
cameron[m] joined13:16
randomuser joined13:16
smuise[m] joined13:17
AnapodoPsalidi left13:20
Rubin joined13:21
kadoban joined13:21
Helmholtz joined13:21
epolanski joined13:22
AACS48 joined13:23
AADHCH joined13:23
randomuser left13:23
randomuser joined13:24
pinage404 joined13:25
dieggsy joined13:25
Xenguy left13:25
s0dyy[m] joined13:27
almarwazi left13:28
almarwazi joined13:29
jazzy left13:29
darkbit joined13:29
silvio[m] joined13:31
elemongw[m] joined13:31
rapid16 joined13:32
rapid16 left13:32
rapid16 joined13:32
durham_ joined13:32
zfnmxt joined13:32
tuxayo joined13:33
adl_ joined13:33
durham left13:34
adlternative left13:34
Guest526 joined13:35
morguldir joined13:36
randomuser left13:37
enoq left13:37
gh34 joined13:41
Helmholtz left13:43
Helmholtz joined13:43
OnkelTem left13:44
Samian if I have remotes/upstream/master and remotes/origin/master, and I type git switch master, which does it get?13:44
argh, I want the upstream master to just overwrite origin/master13:44
j416 Samian: try it, and check with git branch -vv13:44
it might say ambiguous13:45
Samian git branch -vv master13:45
like that?13:45
j416 just git branch -vv13:45
OnkelTem joined13:45
Samian it shows * master cad3b15 [origin/master] data module cean-up13:46
j416 looks like you have your answer13:46
also note that origin/master and master are different branhes13:46
branches*, even13:46
master is set up to track origin/master, that's all13:47
Samian argh13:48
github doesn't let me make two forks13:48
j416 no need13:48
Samian I want a new clean fork so it's in sync with master13:48
j416 fork is just a github concept13:48
Samian this is what I'm seeing: https://imgur.com/a/jy2x6zY13:48
j416 I want to archive or detach my current fork, and make a new fork that's a copy of the upstream repo13:49
after I have my perfect clone, I'll make a single new branch, commit my changes to it, and then tell the gods of the upstream repo I'm making a pull request13:49
j416 are you saying that you want a fork that's not labelled fork?13:49
Samian j416 yes13:50
j416 I don't know if you can make GH PRs that way, can you?13:50
Samian with all the branches kept. because some of the branches have code I like13:50
j416 no sure13:50
*not sure13:50
j416 clone it with --mirror, push it with --mirror, iirc13:50
romannesmysl13:51
Samian j416 it looks like --mirror is a way to archive a fork and create a fresh one13:52
eternalromance left13:56
Guest92 joined13:56
Guest92 left13:58
hubble joined13:58
hubble63 joined14:00
hubble left14:03
junktext joined14:10
enoq joined14:13
Murr left14:13
Murr joined14:14
imMute^imMute14:15
vodkra left14:16
Misotauros left14:20
s1b1 left14:20
Misotauros joined14:20
Rudde_ left14:21
danisanti left14:21
Rudde joined14:22
lgc joined14:22
vodkra joined14:23
adl_ left14:26
kingjulian joined14:26
s1b1 joined14:26
Crassus joined14:27
ByteHackr left14:29
durham_ left14:30
zebrag joined14:31
durham joined14:32
durham left14:34
durham joined14:34
The_Blode_ joined14:34
The_Blode left14:35
YuGiOhJCJ left14:35
randomuser joined14:36
molt left14:37
daoudr joined14:37
hubble63 left14:39
thiago joined14:41
lpapp_ joined14:42
lpapp_ osse: do I need to do git-rebase -i to rebase my branch for merge to main?14:42
it is happening now14:42
do I need some first-parent hackery?14:42
hubble joined14:43
ikke lpapp_: what do you want to achieve exactly?14:43
Soni how do you add a submodule without doing the clone operation?14:44
lpapp_ ikke: my colleague did merge from main into this topic branch a few weeks ago14:44
erochow[hehim][m joined14:45
lpapp_ I want to use rebase to clean up the history14:45
e.g. let merge commits go14:45
from personal topic branches merged into the shared topic branch14:45
also merge commits from main to the topic branch14:45
also rewrite commit messages, etc.14:45
Soni this is to use git submodule update --init --jobs as a parallel variant of git fetch, but without corrupting the repo14:45
lpapp_ squash commits, too.14:45
Soni (submodules do share objects with the parent repo yeah?)14:45
Crassus left14:46
ikke no14:46
lpapp_ ikke: I am preparing a few months old long-lived branch for integration into main14:47
hubble left14:47
hubble joined14:47
skapata joined14:47
skapata left14:47
skapata joined14:47
lpapp_ we all used to merge into this topic branch from our personal topic branches and gitlab created a merge commit for each MR. They have to go.14:47
but not merge commits that we got from main into the topic branch when my colleague merged main into the long-lived shared topic branch14:48
dittid[m] < https://libera.ems.host/_matrix/media/r0/download/libera.chat/d867819a1c5556936880a6afccb93f2f69e145db/message.txt >14:48
jess joined14:48
hubble98 joined14:48
hubble98 left14:48
lpapp_ I guess I want to get the usual git rebase -i, but only for commits that we added to this long-lived branch, not for commits from main14:48
considering that the linear history was broken by the merge from main to the topic branch.14:49
so, I can no longer just use git rebase -i 100 or similar stuff.14:49
hubble26 joined14:49
imMute dittid[m]: in the parent repo 'git checkout $SHA' where $SHA is the revision you want to explore. Then do 'git submodule update' to have git checkout the version of the submodules that was committed in that revision.14:50
ikke lpapp_: you cannot selectively rebase commits14:50
lpapp_ ikke: git rebase -i XXX would have worked if my colleague had not merged main into our branch, right?14:51
if he had rebased from main?14:51
imMute lpapp_: if main was merged into your branch, and you then rebase your branch on a newer main, it'll be fine. it'll just skip that merge commit.14:51
lpapp_ will it change the topic branch history back to linear?14:52
if I rebase from main now?14:52
hubble left14:52
dittid[m] imMute: is there a way to do that in a different worktree? Like something `git archive` but also exporting the submodules content?14:52
Or adding an additional worktree but without downloading the submodules from scratch.14:52
imMute lpapp_: yeah, the rebased branch will be linear. there's a flag to preserve merges I believe.14:52
lgc left14:52
lpapp_ --keep-base14:52
imMute dittid[m]: I do not know how submodules interact with worktrees, sorry.14:52
lpapp_: no, it's --preserve-merges or --rebase-merges14:52
lpapp_ ok, thanks14:53
dittid[m] I just need to `git archive` all the content of a revision recursively with submodules. Is there a way to do this? Because I've been searching for a while and it doesn't seem possible.14:53
lpapp_ so, after rebase, I no longer need to use git log --first-parent topic?14:53
imMute lpapp_: --keep-base is not a valid flag. (at least not in 2.20.1)14:53
lpapp_ it is a valid flag for git rebase14:53
I have 2.24.3 here14:53
imMute lpapp_: ah, it's a new flag.14:54
hubble26 left14:54
lpapp_ imMute: so, git merge from main to topic breaks git log, and one needs to start usign --first-parent14:54
but if I rebase from main, it gets back to linear, and I no longer need --first-parent on git log?14:55
imMute lpapp_: it's not "broken", it's just non linear. and yes, rebase will make the rebased commits linear (unless you preserve merges with the flag mentioned)14:55
lpapp_ thanks14:55
do I have a nicer way than git bisect -i FIRST_COMMIT_IN_THE_BRANCH?14:56
git rebase -i FIRST_COMMIT_IN_THE_BRANCH*14:56
just so that I do not make a mistake with the commit hash14:56
mci64 left14:56
lpapp_ or number back in the history14:56
imMute lpapp_: git rebase -i origin/main ???14:56
lpapp_ thanks, I did not know :)14:56
Soni do submodules share objects with supermodules?14:58
and if not, why not?14:59
molt joined15:02
kurtthem1ker left15:02
clime left15:02
lpapp_ imMute: why is git rebase showing commits in a different order to git log?15:03
bambanxx joined15:03
imMute Soni: I don't think so. They don't because they're logically separate repositories.15:04
Soni sure but deduplication?15:04
imMute lpapp_: no idea, I would expect them to be in the same order.15:04
nobody_ joined15:05
lpapp_ imMute: at the top, I see the older commit from the branch, and at the bottom, I see the newest from the branch.15:05
imMute Soni: they're separate repos, you could assume they don't share any objects in common.15:05
Soni imMute: until you start getting submodules of submodules where they're the same repo15:05
imMute lpapp_: oh, log shows in reverse chronological order, rebase shows in the order they're going to be applied (chronological order).15:05
lpapp_ there must be a reverse order option15:05
imMute Soni: why would you do that?15:05
hubble joined15:06
imMute lpapp_: git log --reverse15:06
Soni imMute: because some ppl use submodules to manage deps, like it's a package manager15:06
lpapp_ imMute: revert git rebase15:06
I am more familiar with the daily git log order15:06
by the way, when git rebase -i origin/main removes merge commits on leaving the editor, does it also squash commits in that merge request?15:06
I do not see "address review comments" commits that colleagues made15:06
for a MR.15:06
imMute lpapp_: rebase shows them in the order they'll be applied. it doesn't make sense to show them in any other order.15:07
lpapp_ I wanted to squash them, but I do not see them, so git rebase automatically did that for me?15:07
imMute lpapp_: it picks up the commits on the branch that was merged in.15:07
lpapp_: as if they were all applied on the same branch, linearly.15:07
lpapp_ imMute: so if the MR contained three commits from a personal topic to the long-lived topic, after git rebase -i origin/main, they will only be one commit instead of four (3 for the MR, and the merge commit)?15:08
imMute lpapp_: there will be 3 - the three from the topic branch. only the cmerge commit is skipped.15:08
lpapp_ then something is going on!15:08
Because I do not see each individual commits from MRs.15:09
imMute lpapp_: lets say your branch branched off origin/main, and then some time later merged origin/main into it. the commits that got brought in by that merge will *not* be part of a rebase (a rebase on top of origin/main) because they're already a part of the new base.15:09
lpapp_ sure.15:10
imMute similarly, if you merge a 3rd branch into both your feature branch and main, and then rebase feature on top of main, the 3rd branches commits will not be part of the rebase (because they're already a part of the new base's history)15:11
lpapp_ we only merged into the long-lived topic15:11
not main15:11
imMute then you should see those commits when you do the rebase.15:11
lpapp_ is it possible to edit/fixup/reword commits from rebase -i origin/main based on author?15:12
i.e. all of us clean up their own stuff15:12
commit messages, etc.15:12
imMute not that I know of.15:12
lpapp_ I guess mark all as edit, and what is not mine, skip?15:12
as a workaround unless there is something better?15:12
imMute I don't think there's any built in way to do that.15:13
lpapp_ ok, thanks, so is this how you would also work it around?15:13
Rebase 6273b960c2..1d58b595b7 onto 1d58b595b7 (104 commands)15:14
does it mean 104 commits?15:14
imMute yes.15:14
lpapp_ ok, so in this case, I can do one-by-one and skip what is not authored by me?15:14
Unless there is a way15:14
I own one third or so15:14
imMute you don't want to "skip" those commits - that would drop them from the new branch15:15
lpapp_ or half15:15
by skip, I do not mean the skip word15:15
I mean mark all as reword for example15:15
and if I recognise it is not mine, just :q in vim15:15
imMute yeah, that would work.15:15
lpapp_ thanks15:16
imMute: for some reason, some of the commits do not mention the author in comments15:20
just date15:20
what is the reason for this?15:20
imMute no idea.15:20
lpapp_ how can I know if it is edited by me? :/15:20
hubble left15:20
lgc joined15:21
lpapp_ can I get a hash somehow to check in another window?15:21
zebrag left15:23
foo_foo15:24
lpapp_ oh15:25
maybe, those are mine :D15:25
that is why it is not writing in the comment explicitly.15:25
yeah, that is the rule, apparently15:30
ham2ham15:32
ham left15:32
ham joined15:32
kingjulian left15:35
zmt00 joined15:37
skapate joined15:37
skapate left15:37
skapate joined15:37
skapata left15:37
fling joined15:37
kingjulian joined15:38
ndorf_ left15:38
ndorf joined15:39
LuxuryMode joined15:40
rsrx joined15:43
LuxuryMode I am trying to push to a remote branch using `git push --force-with-lease` and I am getting ` ! [remote rejected]...error: failed to push some refs to 'git@github.com:my-org/my-repo.git'` and I'm not sure why. The remote branch still exists and there are no other commits which have been added to the remote branch that I don't have. Any ideas on what might be the issue here?15:44
oh, it may just be github https://www.githubstatus.com/15:44
imMute nnections received)15:45
[08/10 05:47:58] -!- Mode change [+Zi] for user imMute^15:45
lpapp_ left15:45
imMute oops15:45
rsrx yeah github is down15:46
ubuntu ppa archive too it seems15:46
LuxuryMode ugh15:47
kingjulian left15:47
mci64 joined15:51
lpapp_ joined15:51
lpapp_ imMute: I guess it is a good idea to diff the long-lived topic branch and the rebase branch branched off from it at the end of the rewording to make sure there is no code difference introduced?15:52
if the rebase and rewrite is only about commit messages?15:52
and dropping merge commits15:52
DoofusCanadensis joined15:53
imMute wouldn't be a bad idea to double check that. there might be differences though, since the new branch will have stuff from main that isn't in the old branch.15:53
(unless you merged main into said branch just before doing the rebase)15:53
lpapp_ yeah, sounds like I should create another branch then with main rebase, but without commit message cleanup?15:53
BlessJah left15:53
howdoi joined15:54
Samian any idea why git push --force would fail?15:55
DoofusCanadensis server will give you a good reason in the logs15:55
Samian remote: fatal error in commit_refs ! [remote rejected] fbgemm_gpu -> fbgemm_gpu (failure)15:55
error: failed to push some refs to 'https://github.com/samiwilf/dlrm.git'15:55
DoofusCanadensis remote rejected your push15:56
Samian why though? it's github, and that's my github account15:56
DoofusCanadensis so, I'd say the repo is protected againsts forced pushes15:56
SirRippovMaple left15:56
Samian it's my repo!15:56
DoofusCanadensis doesn't matter. check your repo setttings on github15:56
imMute Samian: github is having issues at the moment.15:56
Samian thanks good idea!15:56
imMute Samian: https://www.githubstatus.com/15:57
Samian crap15:57
I need to do this force push before my manager see the code I linked him!15:57
hubble joined15:57
Samian thanks imMute15:57
Samian bookmarks githubstatus.com15:57
SirRippovMaple joined15:59
AbleBacon joined16:00
hnOsmium0001 joined16:00
Samian I'm tired of copying and pasting my personal access token every push. I'm trying to find a way around it.16:02
What are some key words to google?16:02
imMute SSH keys16:02
DoofusCanadensis use SSH16:02
Samian thanks!16:02
nrg left16:03
Samian I put something in a .ssh folder somewhere?16:03
rsrx left16:03
stkrdknmibalz left16:04
j416 Samian: I think github has instructions, find those16:04
DoofusCanadensis you don't need a PAT when you have SSH16:04
imMute Samian: Samian: https://www.atlassian.com/git/tutorials/git-ssh16:04
DoofusCanadensis PAT is only for HTTPS clones16:04
Samian I hate setting up ssh keys. It's always a nightmare16:04
then again, git was a nightmare until I said enough is enough16:05
imMute Samian: SSH keys are easy. which part is a nightmare for you?16:05
hubble left16:05
DoofusCanadensis you're a bright boy. SSH should be childs play for you16:05
Samian I forgot the details, but remember the overall frustration. Maybe it'll be smooth this time.16:05
gordonfish- joined16:06
trace1918 joined16:06
DoofusCanadensis the github tutorials are top notch16:06
gordonfish left16:08
kurtthemaker joined16:12
nrg joined16:12
shabius joined16:12
molt left16:12
molt joined16:13
Anticom left16:17
Lyn joined16:18
darkbit left16:20
Samian github is seriously down. I can't push a regular commit16:23
DoofusCanadensis yup16:24
trace1918 left16:24
ikke "The cloud is just somone elses computer"16:24
j416 good thing git is distributed \^^/16:24
trace1918 joined16:24
samuelbernardo joined16:28
EvilDMP left16:29
lpapp_ imMute: just out of curiosity, without rebase -i origin/main, is it possible to see the commits in our branch that is not in main?16:30
my colleague started arguing that I should not have rebased on main, as it is "much more complex" :D16:30
So, I would like to understand the alternative better in details. I do not know it is complex to do git rebase -i origin/main.16:30
or at least the "much more complex" is a bit heavy to say.16:31
orbyt joined16:31
bambanxx left16:32
zebrag joined16:32
j416 lpapp_: git log main..ourbranch16:34
lpapp_ j416: when I tried that, it did not work for non-linear history.16:34
j416 define did not work16:34
lpapp_ it would give intermingled commits16:35
but in this case, I asked about rebase16:35
not log.16:35
j416 but none from main16:35
lpapp_ yeah, some from main.16:35
j416 you asked to see the commits in a branch16:35
rebase doesn't do this16:35
lpapp_ see the commits in rebase, not log.16:35
Guest448 joined16:36
j416 what do you mean by that?16:36
lpapp_ git rebase -i brings up commits for you.16:36
j416 yes16:36
(this is called the todo list, for reference)16:36
lpapp_ in that list, I would only like to see the commits from the long-lived topic branch.16:36
ok, thanks, I did not know that.16:36
trace1918 left16:36
j416 the commits in that list depends on what commit you rebase on16:37
trace1918 joined16:37
Samian woohoo github is working now16:37
j416 git rebase -i HEAD~3 would show 3 commits, for instance.16:37
lpapp_ yeah, so I do not know how to show the commits from the branch in the rebase todo list without rebasing on main.16:38
j416 (i.e. all commits since HEAD~3)16:38
OnkelTem left16:38
j416 lpapp_: find the common ancestor (merge base) and rebase on that16:38
rsx joined16:38
ikke lpapp_: git log --oneline base...<branch>16:38
lpapp_ ah, that would be quite tiresome or error-prone16:38
ikke lpapp_: git log --oneline base..<branch>16:38
lpapp_ and*16:38
j416 lpapp_: there's --keep-base for rebase, but I haven't used it.16:39
lpapp_ also, because main was merged earlier into the long-lived topic branhc16:39
I am not sure if this works, as the history at that point was not linear16:39
without rebasing on main.16:39
j416 lpapp_: you can also manually find the merge base with git merge-base branchA branchB16:39
planetcalls|work left16:39
j416 rebase will eat merges by default16:39
you can make it not to but beware of dragons16:40
OnkelTem joined16:40
lpapp_ so, what strategy would you use in this case16:41
to prepare for merge git rebase -i origin/main or without rebasing on main first?16:41
I guess he has the issue of diff comparison before commit rewrites and after to make sure no code has changed.16:41
but as far as I know, this can easily be done by creating another rebase-original branch which gets rabsed on main without rewording, and diffing those two rebase branches?16:42
is this not the preferred way?16:42
Guest448 left16:42
j416 it looks like you're trying to do two things at once16:43
lpapp_ two substeps, but ultimately one goal, merge the topic branch back to main16:44
j416 while certainly possible, I mostly prefer to do squashing first, and then rebase on a different base as a second step, because it makes it easier to grasp conflicts16:44
lpapp_ which means: 1) Rebasing on top of main 2) Rewording the commit messages.16:44
j416 less brain power spent16:44
lpapp_ I am not sure if it requires branch to rebase16:45
maybe, if you have conflicts, but we do not have any.16:45
brain*16:45
j416 I'd reword first anyway16:45
lpapp_ brain power, even16:45
why?16:45
actually, I still do not see a clear way how to reword simply16:45
git rebase -i origin/main will bring up all the commits you have made, for you.16:46
j416 if there are conflicts and you decide to bail out, you'd have to redo the rewording unless you make sure to keep track of or find later the commit chain that has the rewording16:46
lpapp_ but if you do not want to rebase, I do not know how exactly you would get the same todo list with that ease.16:46
j416 lpapp_: see above16:46
lpapp_ there are no conflicts.16:46
yeah, I saw a lot of manual git magic16:46
but if I am honest, that is very error-prone16:46
j416 then by all means have fun doing them both in one step; I'm just saying what I'd do16:46
lpapp_ ok, thanks, but I still have no clue how you would do it your way :)16:47
j416 git rebase -i $(git merge-base main HEAD) # reword16:47
git rebase main # rebase on main16:47
you might be able to achieve the former with git rebase -i --keep-base, but I have never used it so I don't know.16:48
rsx left16:48
lpapp_ would that also work for non-linear topic branch history?16:48
j416 yes16:48
although it'd eat the merges as I said16:49
lpapp_ what is wrong about that?16:49
They should be binned like anything, they are so silly16:49
j416 ?16:49
I generally avoid merging into topic branches if I can. I don't have much experience rebasing merges. sorry.16:50
not sure if maybe rebasing on main first and then doing the reword (same but opposite order) would mean less potential conflicts16:50
lpapp_ git rebase -i $(git merge-base main HEAD) worked, amazing.16:50
j416 magic16:51
ikke why did git rebase -i main not work?16:51
oh, --keep-base16:51
lpapp_ git rebase -i --keep-base origin/main or what?16:52
or HEAD?16:52
Betal joined16:52
ikke git rebase -i --keep-base main16:53
j416 git rebase -i main would of course work just fine most of the time; I just said it's often easier to split squashing/rewording etc. and rebasing onto a new base into two operations16:53
ikke should be the same as: git rebase -i $(git merge-base main HEAD)16:53
j416 (in my experience)16:53
ikke: thanks for confirming16:53
thebombzen joined16:54
ikke "Set the starting point at which to create the new commits to the merge base of <upstream> <branch>."16:54
j416 yes yes. I read it but I've never used it so I don't know if I might be missing something :)16:54
ikke "This option is useful in the case where one is developing a feature on top of an upstream branch. While the feature is being worked on, the upstream branch may advance and it may not be the best idea to keep rebasing on top of the upstream but to keep the base commit as-is."16:55
lpapp_ hmm, no --keep-base does not work for me16:55
EvilDMP joined16:55
ikke What happens then?16:55
lpapp_ it also linearises the history16:55
ikke rebase by default linearises history16:55
j416 ^16:55
lpapp_ yeah, but j416 said that is not how he would do things16:56
he would first reword, and only when that is done, rebase.16:56
j416 it'll linearise nonetheless16:56
lpapp_ so, I am a bit confused if I am honest.16:56
how you would actually split this step into two different ones.16:56
j416 lpapp_: did you understand why I said to split them?16:56
lpapp_ j416: maybe not, were you concerned about conflict resolution?16:57
j416 it just makes it two steps instead of one, so as to reduce complexity16:57
if you're done with one step, you have a good state16:57
lpapp_ I am sorry, maybe I am dumb, but I am unable to follow16:57
you are saying not to rebase16:58
first squash/reword16:58
but for that, you need to run rebase -i16:58
j416 rather than doing two things at once, ending up with a conflict or whatnot, having to abort, and then redo both the squashing and the rebase, see16:58
lpapp_ but if you are doing that against main, you will get rebased against main16:58
so, you would not separate it.16:58
j416 both use the rebase command, but the former isn't a rebase per-se (it doesn't base the branch on a new base), you just run it for the side-effect of being able to reword16:58
anyway, do whichever you feel is easiest16:59
you don't have to split it into two steps.16:59
rfuentess left17:01
lpapp_ for me, it is a rebase17:01
after that, my history becomes linear17:01
before that, the history is non-linear17:02
Have I missed something?17:02
j416 problem solved?17:02
lpapp_ No, sorry, I am struggling to get it17:02
and I would like to17:02
I see a rebase going on, but you say no rebase going on for git rebase -i --keep-base main17:02
j416 would you state your question again?17:02
lpapp_ I did git rebase -i origin/main17:02
and my colleague started complaining that how he can diff now17:03
after he rewords17:03
to make sure the code itself has not changed17:03
j416 diff what to what?17:03
lpapp_ I suggested to create another branch off from the topic branch that only gets main rebase without rewording17:03
and diff against that17:03
but he said, it is much more complex than not changing the base, reword, and then rebase on main17:03
j416 the commit messages won't appear in the diff17:03
lpapp_ but I do not know how to do the latter.17:03
I would like to understand why it is much more complex what I did.17:03
yes, you are right, commit messages will not appear in the diff.17:04
j416 so he wants you to first do the reword, then do the rebase onto main?17:04
lpapp_ we want to make sure we do not change code while integrating into main17:04
and git diff sounds like a good canditate for that17:04
we are only aiming to reword17:04
and squash17:04
j416 that's difficult, since rebase will by definition re-apply all commits onto a new base, potentially changing something17:04
lpapp_ I think he thinks that is "much more simpler"17:05
j416 so you should always verify that the result is correct17:05
lpapp_ I would like to understand how 1. It is done 2. Why it is much more complex what I did17:05
j416 how is what done?17:05
lpapp_ reword the commits done by us in the topic branch, without moving the base to the latest stage of main17:05
j416 just like I suggested above17:06
lpapp_ but it does not work for me17:06
j416 it sounds like your colleague is saying the same thing17:06
lpapp_ it rewrites the commit history in the git log output17:06
j416 because it lineariese the history you mean?17:06
lpapp_ yes, but I believe it will also pull in new commits, surely?17:07
j416 no17:07
lpapp_ from main.17:07
j416 you're not rebasing on main17:07
"git rebase main" rebases on main17:07
"git rebase -i $(git merge-base main HEAD)" or "git rebase -i --keep-base main" does not17:07
lpapp_ git rebase --keep-base main does not actually rebase on main, just linearises the history?17:07
j416 correct17:08
you might try your luck with adding --rebase-merges to the latter, to try and keep those as well17:08
man git-rebase look for --rebase-merges for more info17:08
gitinfo the git-rebase manpage is available at https://gitirc.eu/git-rebase.html17:08
lpapp_ merges should not matter for diff, right?17:08
j416 merges are regular commits17:09
they matter17:09
lpapp_ ?17:09
They do not bring code changes...17:09
j416 yes they do17:09
ikke They can17:09
lpapp_ unless there is a conflict resolution, which we do not have.17:09
j416 the only difference between a merge commit and any other commit is that a merge commit has more than one parent17:09
lpapp_ but I assume --rebase-merges would not drop code change merges...17:09
that would be a bit dumb...17:09
j416 if the merge commit brings in any changes at all from the branch merged in, those will be part of that merge commit17:10
furrymcgee left17:10
j416 I'd assume that too, yes.17:10
it should do the right thing.17:10
but I have yet to try it.17:10
lpapp_ ok, so, maybe for next time, I can use git rebase -i --keep-base main17:10
and once I reworded things, I can do git rebase origin/main?17:11
j416 yes17:11
lpapp_ but honestly, I do feel reword should be the last thing17:11
after the code is settled17:11
j416 that'll work too17:11
lpapp_ to me, it is the wrong order to reword, and then, if there is conflict, make code changes, and then potentially reword again17:11
j416 yep17:11
makes sense17:11
since you have merges17:12
there's a reason you merged something into your branch, and by rebasing (even with --keep-base) those changes will go away and potentially break something17:12
lgc left17:13
lpapp_ the only reason was that it was a shared long-lived topic branch multiple devs working in it.17:13
I was pushing for rebase, but my colleague preferred merge, and I gave in.17:13
to avoid arguing to eternity :)17:13
lgc joined17:13
lpapp_ it was just a few of us, so I did not see rebase a big deal instead of merge.17:13
but that is the only reason why we had merges.17:13
no conflicts, etc.17:13
j416 rebase effectively resets to the commit you give it, then cherry-picks each commit one by one, skipping over merge commits17:13
!backup17:14
gitinfo Worried about your data while trying stuff out in your repo? The repository in its entirety lives inside the .git directory in the root of your work tree so to backup everything `cp -a path/to/workdir path/to/backup` or equivalent will suffice as long as the repo is not modified during backup. See also http://sethrobertson.github.com/GitBestPractices/#backups17:14
j416 then, try it and see™17:14
:)17:14
I often create backup branches when I'm not sure whether I'll need to re-do a rebase or go back to check something17:15
like, git branch foo-before-rebase17:15
spaceplo_SpacePlod17:15
j416 that way I can easily go back to that state if needed17:15
and if not, I just delete that branch17:15
ludovicchabant left17:16
gnoo left17:17
merpnderp left17:17
nobody_ left17:17
lgc left17:17
christall left17:20
Pr0phet left17:20
christall joined17:21
lpapp_ j416: yes, that is what I did17:21
feature-rebase and feature-rebase-original17:21
feature-rebase contains the rewording and rebasing17:22
feature-rebase-original contains the rebase17:22
and feature is before rebase and rewording17:22
I feel that my colleague was a bit harsh when he said this is much more complex than it should be as branches are cheap in git.17:22
and also, well-separated with worktrees as I learnt the other day.17:22
and when it is only a handful of devs, like 3, I would say, rebase is not too bad in a shared branch either17:23
imMute lpapp_: if it's a long lived branch worked on by multiple people? yeah a rebase is going to be more work than a merge.17:23
lpapp_ since git pull --rebase will adjust automatically based on my experience17:23
Pr0phet joined17:23
nomicon_nomicon17:23
lpapp_ imMute: there was no conflict between main and topic17:24
we work on a fairly separate area that no one else touches17:24
JayDoubleu left17:24
imMute still. just merge and be done with it.17:24
ludovicchabant joined17:24
lpapp_ ?17:24
do you mean merge for catchup?17:24
from main to the feature branch?17:25
imMute if that's the whole point of this, yes.17:25
lpapp_ sure17:25
jakesyl left17:25
Manouchehri left17:25
average left17:26
arxanas joined17:26
arxanas How exactly does duplicate commit connection for `git rebase` work? The man-pages suggest that the patch will be skipped if it has the same textual content as any upstream patch, but how does it determine this? Does it compute the patch IDs of all upstream commits and compare them?17:27
jimklimov1 joined17:27
christall left17:28
Pr0phet left17:28
Manouchehri joined17:29
bremner arxanas: man git-patch-id17:29
gitinfo arxanas: the git-patch-id manpage is available at https://gitirc.eu/git-patch-id.html17:29
randomuser left17:29
jimklimov left17:30
cespare left17:30
odoood joined17:30
Pr0phet joined17:30
j416 arxanas: I don't _think_ it's patch ID (but I may be mistaken, perhaps there are multiple things in place), because it'll also not apply a commit that say, introduces a change that is just _part_ of a commit on which it is being applied. Rather, I think it's git apply or such, seeing that applying it would make no difference. How, I don't know.17:31
Lyn left17:31
randomuser joined17:31
j416 lpapp_: note that even though Git says there are no _syntactical_ conflicts, there may be _semantic_ conflicts.17:32
Manouchehri left17:32
j416 lpapp_: e.g., branch A depends on a function that was removed in branch B; rebasing branch A on branch B might work just fine syntactically, but the code won't compile because branch A is calling a function that no longer exists. Always check the result after rebasing.17:33
elichai2 left17:33
imMute same thing applies to merging as well.17:34
JayDoubleu joined17:34
j416 indeed17:34
Manouchehri joined17:34
lpapp_ yes, agree17:34
this is being checked17:34
orbyt left17:34
lpapp_ thanks for the reassurance.17:34
it can even be more subtle17:35
it could compile, but misbehave, isn't it?17:35
j416 sure.17:35
cespare joined17:35
average joined17:35
j416 Git doesn't know what your program does. It just merges lines of text.17:36
elichai2 joined17:36
j416 but it would be cool if it did.17:36
jakesyl joined17:37
merpnderp joined17:39
Duckle joined17:39
lgc joined17:40
lpapp_ haha :D17:43
DoofusCanadensis left17:48
lechner left17:48
sniperwolf joined17:49
lechner joined17:51
christall joined17:52
arxanas left17:52
christall left18:00
clime joined18:02
clime left18:02
bn_work joined18:04
kingjulian joined18:05
gast0n joined18:12
lgc left18:18
lgc joined18:19
lgc left18:19
christall joined18:20
kingjulian left18:28
sniperwolf left18:32
odoood left18:40
sniperwolf joined18:43
jetchisel joined18:49
BlessJah joined18:49
almarwazi left18:53
mci64 left18:56
Betal left18:56
mci64 joined18:56
fnurkla left18:56
Pr0phet_ joined18:57
Pr0phet left18:57
ludovicchabant left18:57
Pr0phet_Pr0phet18:57
ludovicchabant joined18:57
jakesyl left18:57
JayDoubleu left18:57
jakesyl joined18:58
Manouchehri_ joined18:58
JayDoubleu joined18:58
Manouchehri left18:58
Manouchehri_Manouchehri18:58
Betal joined18:59
dviola left19:01
tolot left19:01
tejr left19:06
tejr joined19:07
SmashingX joined19:11
nvmd joined19:12
SmashingX I have an issue in which I had a subdirectory which it was added to the .gitignore file, then I remove it from there and when I enter 'git status' git is still ignoring that path.19:12
j`ey joined19:15
j`ey I have commits: A B C D E F, can i easily push A-E to a new repo, while losing all the history from E-F19:15
j416 j`ey: what do you mean by losing?19:16
j`ey basically I have a few commits on top of the linux kernel, and I just want to push my few commits, and then a single big commit for kernel19:16
j416 j`ey: so you want to push your branch as if it were at D?19:17
j`ey (while keeping the history locally..)19:17
I want to see: A B C D EF(squashed)19:17
j416 you want to squash E and F into one commit and then push the result?19:17
j`ey as if I first checkout out the kernel with --depth 1, and put my changes on top19:17
randomuser left19:20
randomuser joined19:21
orbyt joined19:22
j`ey hmm, maybe I can make a new branch, and then git pull --depth N ?19:26
austin987 left19:26
SmashingX is there anybody that knows why git is still ignoring a path?19:27
dodo SmashingX: are files inside the dir?19:28
ikke git check-ignore -v <path>19:30
cvmn joined19:33
rwp joined19:34
SmashingX ikke: git check-ignore -v wp-content/themes/terrachips/lib/19:35
I did this and I got nothing back19:36
ikke ls -al wp-content/themes/terrachips/lib/19:36
absc joined19:36
SmashingX ikke: I got a bunch of php files listed19:36
ikke and git ls-files wp-content/themes/terrachips/lib/19:37
SmashingX ups19:37
ops it was a different directory19:37
git check-ignore -v wp-content/themes/terrachips/dist19:37
wp-content/themes/terrachips/.gitignore:3:dist wp-content/themes/terrachips/dist19:37
oh so there's another .gitignore?19:38
ikke yes19:38
SmashingX wth19:38
I didn't know you can have more than 1 .gitignore19:38
ikke You can have one in every directory19:38
SmashingX dang, now I have to do a search for every .gitignore in the repo. Ok thank you so much19:39
and then I think I have to do something after I remove the .gitignore contents or the file, right?19:39
ikke find -name .gitignore19:39
SmashingX I think I have to clear the cache or just commiting the file and pushing will do?19:40
austin987 joined19:40
ikke There is no cache to clear19:40
average left19:41
SmashingX so the steps are, delete the .gitignore file, commit and push, then if I do git status would do it?19:41
j`ey left19:41
SmashingX Ok, I should try it first.19:41
Thank you ikke!19:41
ikke yw19:42
SmashingX oh I just did 'git rm path to the .gitignore file' and I haven't even commited but I checked the status and the paths that the .gitignore file was trying to ignore are now showing up as new.19:43
absc left19:44
ikke good19:44
that's expectec19:45
lavos joined19:46
SmashingX so what 'git check-ignore -v' tells you is what .gitignore file is making that path to be ignored?19:46
and the location of that .gitignore file19:47
molt left19:47
ikke correct19:47
absc joined19:47
SmashingX TIL19:47
sorry git for swearing at you.19:48
pizdets_ left19:49
pizdets joined19:50
odoood joined19:53
SmashingX if a .gitignore file has in its contents a path that starts with a '/' means that git will ignore that path at root?19:53
ikke yes19:54
well19:54
arxanas joined19:54
ikke relative to that .gitignore file19:54
natrys left19:54
ikke a .gitignore file in a subdirectory cannot affect anything outside of that directory19:55
arxanas bremner: I've seen the documentation on patch IDs, but it's not said where it's used it, if anywhere, and I want to know if it's used specifically in `git rebase` at present. The man-pages make is sound like it is, but I don't see anything in the source code to back that up. Is the documentation out of date? Is there someone who knows who I can19:55
ask?19:55
bam32 left19:55
SmashingX gotcha19:55
that's clear19:55
Nomikos what happens if you `git add .git`?19:55
ikke Nomikos: nothing, git will ignore it19:55
Nomikos awww19:56
absc left19:57
arxanas j416: I think in those case, it just attempts to apply the patch, and if it results in an empty commit, it skips it (unless configured otherwise). But I'm curious about specifically the patch ID mechanism19:57
absc joined19:57
daoudr left19:57
randomuser left19:58
bremner arxanas: dunno. When I was building a rebase-like-thing, I started with patch-ids, but then ended up doing trial application19:58
arxanas I have trial application, I'm just trying to match the behavior of Git, but computing patch IDs on large repos can end up taking quite a while if your branch is stale19:59
SmashingX Nomikos: Just curious, why do you want to add it?20:01
ikke arxanas: that's something I've wondered about myself before, and at some point, I just came to accept it kind of just meant skipping empty patches, but not sure if this is some old documentation or not20:01
Nomikos SmashingX: I like testing things to see if they will or will not break like that20:02
and if they do break, if there will be shiny glitter shards all over the place20:02
like some version 1 compact discs, you ever bend one of those outward to their breaking point?20:03
SmashingX In my mind there isn't a situation where that might be necessary.20:03
Nomikos well, no, not "necessary"20:03
kurtthemaker left20:04
Nomikos it's just a "what if" experiment20:04
randomuser joined20:05
ikke Nomikos: the low-hanging fruit should be long gone20:05
kurtthemaker joined20:06
SmashingX I don't understand the analogy but well.20:06
ikke what analogy?20:07
low-hanging fruit?20:07
SmashingX about the fruit20:07
yup20:07
ikke It's an idiom20:07
arxanas ikke: the trouble is that if it's *just* skipping empty patches, then if you try something like commit A, revert A, and then rebase A again onto that branch, then A doesn't get applied a second time. I don't see why that would happen without a patch ID deduplication mechanism. Or maybe I'm just misunderstanding something about how the merge20:07
happens?20:07
^ in the above case, I would expect A to apply again, instead of being skipped, because it should no longer produce an empty patch20:07
ikke SmashingX: low-hanging fruit is easy to pick20:07
SmashingX lmgt20:07
what is that actually mean in this case with what Nomikos is doing?20:08
ikke SmashingX: trying to add / track .git is fairly basic20:08
Nomikos adding the .git directory to the .git directory is something not intended, but easily done - but also easily prevented20:09
ikke (in the sense of looking for things that break20:09
SmashingX basic but also useless I think20:09
ikke: got it20:09
enoq left20:09
Nomikos it's like an OS preventing you from copying a directory into itself, or a browser preventing html frames from loading themselves20:09
*framesets20:09
theoceaniscool left20:10
randomuser left20:10
SmashingX ok, I just should get back to keep fighting with my .gitignore files, sorry Nomikos.20:10
Nomikos SmashingX: no apologies needed, good luck :-)20:11
m0viefreak joined20:12
Murr left20:13
Murr joined20:14
gh34 left20:14
theoceaniscool joined20:21
anton joined20:22
cvmn left20:25
caveman left20:25
anton left20:26
bambanxx joined20:27
nobody_ joined20:28
anton joined20:28
reprazent left20:29
anton left20:30
reprazent joined20:31
Narrat joined20:36
odoood left20:38
kingjulian joined20:39
tejr left20:39
wootehfoot joined20:39
odoood joined20:40
tejr joined20:41
vysn left20:43
trace1918 left20:51
sniperwolf left20:53
__jmcantrell__ joined20:53
absc left20:57
circuitbone i start with a template https://github.com/github/gitignore SmashingX21:00
ikke I just ignore the things I need to ignore21:01
durham left21:02
lavos left21:05
molt joined21:05
ash_worksi left21:12
malteger left21:16
malteger_ joined21:16
EvilDMP left21:21
ash_worksi joined21:25
lavos joined21:29
lavos left21:29
lavos joined21:30
molt left21:33
bambanxx left21:35
jmcantre1 joined21:36
__jmcantrell__ left21:39
__jmcantrell__ joined21:40
jmcantre2 joined21:42
jmcantre1 left21:43
pretty_dumm_guy joined21:43
__jmcantrell__ left21:45
lpapp_ left21:49
lavos left21:50
SmashingX circuitbone: nice templates! thank you for sharing!21:55
circuitbone welcome SmashingX21:57
I used the toptal generator before that https://www.toptal.com/developers/gitignore21:58
humanface joined22:02
__jmcantrell__ joined22:03
m0viefreak left22:06
jmcantre2 left22:06
mci64 left22:06
wootehfoot left22:08
kingjulian left22:09
anton joined22:10
jmcantre1 joined22:11
Murr left22:13
frobnic left22:13
Murr joined22:13
frobnic joined22:13
junktext left22:13
__jmcantrell__ left22:15
Arokh left22:15
lpapp_ joined22:15
Arokh joined22:16
ferdna joined22:16
christall left22:18
__jmcantrell__ joined22:22
__jmcantrell__ left22:22
AnAverageHuman left22:23
jimklimov1 left22:23
jmcantre1 left22:25
Xenguy joined22:29
Narrat left22:29
AnAverageHuman joined22:29
AnAverageHuman left22:34
AnAverageHuman joined22:39
BlessJah_ joined22:44
BlessJah left22:47
__jmcantrell__ joined22:48
debsan joined22:48
LuxuryMode left22:49
Duckle left22:56
Duckle joined22:58
humanface left22:59
jmcantre1 joined23:03
jmcantre1jmcantrell23:04
theoceaniscool left23:05
__jmcantrell__ left23:06
christall joined23:08
dermato left23:09
dermato joined23:12
reprazent left23:13
reprazent joined23:16
christall left23:16
Raguile left23:17
christall joined23:21
christall left23:22
reprazent left23:23
christall joined23:23
shokohsc left23:23
SuperLag left23:24
reprazent joined23:24
shokohsc joined23:24
__jmcantrell__ joined23:25
christall left23:27
jmcantrell left23:29
dermato left23:32
arxanas left23:33
pretty_dumm_guy left23:34
dermato joined23:35
christall joined23:35
jmcantrell joined23:37
skapate left23:37
christall left23:39
__jmcantrell__ left23:40
PinealGl1ndOptic left23:41
Misotauros left23:46
Misotauros joined23:47
jstein joined23:48
mrteals joined23:48
rossome left23:48
orbyt left23:48
wgrant joined23:48
rossome joined23:49
treefrob left23:55
xx left23:56
frobnic left23:57
treefrob joined23:57

Logs Search ←Prev date Next date→ Channels Documentation