IRCloggy #git 2019-08-23

Logs Search ←Prev date Next date→ Channels Documentation

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

2019-08-23

de-facto left00:01
de-facto joined00:01
hussam left00:02
m0viefreak left00:04
stitched_unicorn joined00:05
random_yanek left00:05
lankanmon left00:07
CarlFK joined00:08
rafasc jadax: are master is correct here: git push master? HEAD:refs/for/master ?00:09
jcbitter left00:09
jadax sorry, should be git push remote HEAD:refs/for/master00:09
rafasc you probably meant your remote. But in any case, it should be the same.00:09
jadax so regardless of whether I'm on the branch or in detached HEAD state, the push command would always be the same?00:10
jcbitter joined00:10
rafasc yes. the part HEAD:refs/for/master, is called a refspec and is basically a push instruction.00:11
libertyprime joined00:11
jadax would it work if I did git push remote master:refs/for/master ?00:11
rafasc meaning make refs/for/master in the remote point to the commit my local HEAD is pointing.00:11
jadax for simple local master to remote master push00:11
rafasc jadax: yes. That's the gist of it.00:12
jadax I see00:12
mowcat left00:12
rafasc jadax: you can also delete branches on the remote by pushing nothing to it: git push remote :ref/to/be/deleted00:12
jadax that's dangerous00:12
bluezone left00:12
rafasc git push remote :master; would delete master on the remote.00:13
thought I would mention it in case you were doing things like push remote $VAR:ref/bla/bla00:13
jadax thanks00:14
CarlFK help? http://paste.ubuntu.com/p/YndYtrM2GD/ error: inflate: data stream error (incorrect header check)00:14
rafasc CarlFK: corrupt object :/00:16
dege left00:17
rafasc do you have another clone of the project? where git cat-file -p 4648502e38141ece2fdc9fdae19c007019557409 succeds?00:17
CarlFK probably - gh is pretty up to date.. let me clone it somewhere00:18
Emperor_Earth left00:20
CarlFK http://paste.ubuntu.com/p/nd7VYvscBG/ it's the root dir00:20
Bobdude joined00:21
drbean joined00:23
drbean_ left00:25
rafasc hmmm. it's at tree object.. I think you'll need to unpack it...00:26
lankanmon joined00:26
drbean_ joined00:28
rafasc CarlFK: have you try running git fsck?00:29
CarlFK no. neat. didn't know that was a thing00:30
drbean left00:31
rafasc on your new clone how many files do you have on .git/objects/pack ?00:31
CarlFK 2 carl@twist:~/temp/veyepar$ ls .git/objects/pack; pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.idx pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.pack00:32
rafasc If that's the only corrupt object, git unpack-objects < pack-<some-hash>.pack00:32
diogenese joined00:32
rafasc that should recreate the file at .git/objects/e5/3ea....00:33
copy it to the other repo.00:33
rinse and repeat00:33
CarlFK how do I cp .git? (trying to make a backup in ~/temp00:34
rafasc !backup00:34
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/#backups00:34
CarlFK oh.. my fault.. not enough ..'s00:35
rafasc I think you could also tranfers the .pack files and run git repack, but I can't remember how exactly.00:36
CarlFK git fsck http://paste.ubuntu.com/p/nMKghhqQBX/00:37
rafasc I think with -ad, but not sure. It's been a while since I experienced corruption.00:37
greatgatsby left00:37
rafasc That's just 5 commits, doable if they're in the other repo.00:38
pie_ left00:39
duderonomy left00:40
beastDiv_ joined00:43
libertyprime left00:43
CarlFK my new clone does00:47
jadax how many clones do you have?00:47
CarlFK my new clone does' have .git/objects/??00:47
rafasc No, new clones have the objects in a packfile.00:48
you need to run $git unpack-objects <.git/objects/pack/pack-<some-hash>.pack00:49
lungaro left00:49
CarlFK I have my original, a copy in temp/-borked and a clone from gh in temp/-good00:49
lungaro joined00:49
finalbeta left00:50
Guest459543effprime00:50
rafasc go to temp/-good and run the unpack-objects I mentioned.00:50
CarlFK ~/temp/veyepar-good$ git unpack-objects < .git/objects/pack/pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.pack00:50
Unpacking objects: 100% (17382/17382), done.00:50
temp/veyepar-good$ ls .git/objects/ -> info pack00:51
rafasc then transfer the offending objects to your original00:51
CarlFK I stil don't see .git/objects/??00:52
rafasc hmm. Sorry, my mistake...00:53
copy that .pack file to your original repo.00:53
then try git repack -a00:53
CarlFK ls veyepar-bork/.git/objects/pack/ has 5 sets of idx/pack and none have the same hash http://paste.ubuntu.com/p/GmKRms4MXD/00:57
is that ok?00:58
I haven't done the repack yet00:58
rafasc or alternatively, move that *.pack file out of the pack directory, and run unpack00:58
mv .git/objects/pack/pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.pack /tmp/git.pack00:59
then $git unpack-objects </tmp/git.pack00:59
CarlFK: yes, that is to be expected.01:00
CarlFK: and after the repack, you'll probably will get just one.01:01
CarlFK in stead of moving to /tmp, this is ok? temp/veyepar-bork$ git unpack-objects < ../veyepar-good/.git/objects/pack/pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.pack01:01
Giant81 joined01:03
rafasc Not sure if that'll work.01:03
Giszmo joined01:03
rafasc because you have the objects, they just happen to be corrupt.01:03
CarlFK how is that differnt from mv ... /tmp; git unpack.. ?01:04
pack-e53 is from the fresh clone I just made01:04
rafasc because if you move the pack away from the good repo, it will unpack everything.01:04
CarlFK ah01:04
rafasc but if you try to unpack inside bork, it may check that it already has those objects, and skip the unpack.01:05
so your files remain corrupt.01:05
CarlFK oh, I thought $git unpack-object was done in -borked - I get it now01:07
freeman42y joined01:08
CarlFK ok, that woked01:09
rafasc run fsck again to make sure01:11
maybe with --full even,01:11
freeman42x left01:11
Sasazuka left01:14
CarlFK i've only create the ?? dirs with veyepar-good$ git unpack-objects < /tmp/pack-e53ea3ef2ff5418ec61a831709b60065b3147fa8.pack01:15
git fsck - Checking object directories: 100% (256/256), done. (no errors)01:15
ghormoon left01:18
dartmouthed left01:18
CarlFK -borked git fsck http://paste.ubuntu.com/p/nMKghhqQBX/ (from before) do I cp .git/objects/3c/69dbd55866477120ad44062b1a113e161b8a34 from -good and then ... ok, im lost01:18
rafasc CarlFK: in your borked, run fsck like before.01:20
CarlFK I haven't changed anything in it yet01:21
rafasc does it complain about unable to unpack header of .git/objects/3c/69dbd55866477120ad44062b1a113e161b8a34 ?01:21
fairuz joined01:21
rafasc if yes, transfer that 3c/69db from good to borked. Do that for every commit.01:21
beastDiv_ left01:22
ghormoon joined01:24
thiago joined01:25
iam730 left01:27
CarlFK git repack -a ... fatal: unable to read 94595a5a2c884ebec2799e0ee27e02561b28734f01:28
01:28
BonusPlay left01:28
CarlFK which is the 2nd in broken link from tree 687d8ffd28d5b7616f46affbd82c326a671ac4c7 to blob 94595a5a2c884ebec2799e0ee27e02561b28734f01:28
BonusPlay joined01:28
rafasc is 94/59... in the good repo?01:29
misuto left01:29
daurnimator left01:29
rafasc I think, going the git-repack route is probably easier.01:30
CarlFK no hits: veyepar-good$ find .git/ -name 94595a5a2c884ebec2799e0ee27e02561b28734f01:30
rafasc If this works: https://git-annex.branchable.com/tips/recovering_from_a_corrupt_git_repository/01:30
CarlFK: that doesn't work like that. Because objects are stored in directories01:30
94595a5a2c884ebec2799e0ee27e02561b28734f will be at 94/595a5a2c884ebec2799e0ee27e02561b28734f01:31
CarlFK ah01:31
kegster left01:31
kegster joined01:32
CarlFK then yes, I have -good .git/objects/94/595a5a2c884ebec2799e0ee27e02561b28734f01:32
rafasc CarlFK: I think the link I posted is worth a try, on a separate copy.01:32
as it will be much easier than copying everything manually, if you have lots of corrupted files.01:32
CarlFK that might be the last one01:33
kezimo left01:33
rafasc CarlFK: the problem is that if the corrupt object was a tree, it stopped the transversal.01:34
and now that you recovered it, it can progress further into finding more corrupt objects.01:34
kezimo joined01:34
CarlFK how does this look http://paste.ubuntu.com/p/zb6gSjnSss/01:36
wildlander left01:37
cd joined01:38
rafasc CarlFK: looks good01:38
CarlFK yay!01:38
thank you for all your time01:39
BonusPlay left01:39
BonusPlay joined01:39
rafasc yw01:40
Giszmo left01:41
beastDiv_ joined01:44
diogenese left01:52
Giszmo joined01:52
keepLearning512 joined01:56
daurnimator joined01:56
Goplat joined02:00
F0rTex left02:00
F0rTex joined02:01
misuto joined02:02
lankanmon left02:02
Enphuego left02:09
neightchan joined02:09
diogenese joined02:25
beastDiv_ left02:26
causa_sui left02:27
beastDiv_ joined02:29
duderonomy joined02:39
lagothrix left02:44
lagothrix joined02:44
stitched_unicorn left02:45
nabil_ joined02:45
Giszmo left02:48
is_null_1 joined02:49
is_null__ left02:49
is_null_ left02:49
beastDiv_ left02:50
lankanmon joined02:50
finalbeta joined02:51
rafasc left02:58
kneeki left03:04
tempate joined03:05
tempate Hello. I am having trouble pushing a commit to git. https://bpaste.net/show/zWqQ03:06
I have removed the vgcore file from src but the problem remains03:06
Ori_B hm, is there any documentation on the format of a patch exported with git-format-patch?03:07
especially around what happens with merge commits.03:07
Giszmo joined03:08
CarlFK tempate: I'm guessing it is still in your commit history03:10
tempate CarlFK: yes, but I don't know how to remove it03:10
CarlFK (don't ask me how to remove it.. im not great.. yeah, that.03:10
tempate oh, aite03:11
CarlFK https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History "or change the actual content of the commit by adding, removing and modifying files"03:12
did you git rm vgcore ?03:12
tempate it says it doesn't match any files03:14
I am not sure why03:14
CarlFK did you just rm the file?03:14
tempate nope03:15
It says "fatal: pathspec 'vgcore' did not match any files"03:15
CarlFK what do you mean by "I have removed the vgcore file from src "03:15
btw - when I ask if you have done something, that is a question, not advice03:16
tempate noted03:16
I meant I had removed the file from the system, not from git's history03:16
CarlFK pretty sure you want to put it back, then use "git rm" to remove it from the fs and git, but im not really sure where you are at now in regards to " don’t amend your last commit if you’ve already pushed it."03:18
tempate I can't unremove it though03:19
it's probably too late for that03:19
isn't there a way to just cancel the commit?03:19
CarlFK (pre-receive hook declined) sounds like you didn't really push03:19
tempate nope, I didn't really push03:20
causa_sui joined03:20
CarlFK try: git checkout src/vgcore.2427203:20
beastDiv_ joined03:20
tempate pathsec did not find any file known to git03:21
Aelius left03:22
CarlFK is this the dir/file name that you deleted? src/vgcore.2427203:23
nabil__ joined03:23
tempate yes03:23
CarlFK well.. if you committed it (which you did else you wouldn't get the error) you can restore it over whatever change you made (like deleting it)03:24
Aelius joined03:25
bn_work left03:25
nabil_ left03:27
supernovah is there a way to get a terse list of untracked files03:27
CarlFK git status ?03:27
Giszmo left03:28
beastDiv_ left03:28
supernovah for external processing though03:30
Tawonga left03:30
preaction git status --porcelain03:30
supernovah tyty03:31
tempate CarlFK: how can I?03:31
raatiniemi joined03:31
tempate can't I just remove the whole commit and start over?03:31
CarlFK probably. I don't know how03:32
Tawonga joined03:32
neightchan left03:39
nabil_ joined03:42
diogenese left03:43
libertyprime joined03:43
nabil__ left03:45
neightchan joined03:49
beastDiv_ joined03:50
Freshnuts left03:55
lankanmon left03:57
lankanmon joined03:58
CarlFK git status --untracked-files=no does what I want. how do I do that with -u?04:01
git status -u=no ... fatal: Invalid untracked files mode '=no'04:02
ah: nvm git status -uno04:03
Ekho left04:05
is_null_1 left04:21
kneeki joined04:24
walbo joined04:26
neightchan left04:28
hellauer left04:29
fjellfras joined04:29
neightchan joined04:33
fphilipe_ joined04:37
neightchan left04:39
beastDiv_ left04:41
Giant81 left04:42
jaeckel left04:43
clime joined04:48
lalitmee joined04:51
orbyt_ left04:58
walbo left05:01
pks_ joined05:02
pks left05:03
pks_pks05:03
pr100|afkpr10005:03
hussam joined05:06
dartmouthed joined05:06
kneeki|a joined05:06
neightchan joined05:06
jaeckel joined05:07
ilmostro left05:07
diogenese joined05:09
kneeki left05:10
finn0 joined05:11
neightchan left05:12
fairuz left05:13
Viking667 joined05:13
Viking667 'llo again.05:13
sauvin joined05:14
finn0 Mistakely, I've committed a file which I don't want to. I've a solution, reset head to HEAD~1 by git reset HEAD~1 then, add only those file in staging area which have to commit. But, wonder is there any better solution present than this?05:18
Means I don't have to go to my previous commit.05:19
JeffH joined05:19
pycer joined05:25
finn0 *go-back05:26
yonder left05:31
JeffH left05:32
TomTom joined05:33
yonder joined05:37
igemnace you can git rm the file then git commit --amend05:40
finn0: ^05:40
neightchan joined05:43
orbyt_ joined05:47
vdl How can I find the merge commit which added a given file? Or even all merge commits which touched that file?05:48
neightchan left05:48
abbiya joined05:49
vdl I can find the commit which added the file with git log --diff-filter=A -- <path> but not the merge commit which took that commit05:52
DWestCoast joined05:54
lalitmee left05:55
lalitmee joined05:55
Sasazuka joined05:55
j416 vdl: --merges05:56
rewt left05:57
j416 vdl: but you might mean --first-parent05:58
lalit joined05:58
rewt joined06:00
lalitmee left06:00
vdl j416: doesn't work06:00
n3wborn joined06:01
vdl I expected git log --merges --diff-filter=A -- <path> to work but it doesn't06:03
(--first-parent neither)06:03
orbyt_ left06:04
pycer left06:05
j416 !doesntwork06:06
gitinfo Sorry to hear it doesn't work, but how about some details? At this point we don't even know whether it did nothing, spit out an error message, or abducted your pet unicorn in a flying saucer. That makes it hard to troubleshoot – unicorn abduction requires a completely different solution than an error message, for instance. So, please be specific...06:06
j416 vdl: try without the --diff-filter06:06
crose joined06:10
sQVe joined06:14
kjartan left06:14
kjartan joined06:16
rfuentess joined06:18
Noti joined06:19
quizzi left06:22
Sasazuka left06:22
random_yanek joined06:23
vals_ joined06:25
sozuba joined06:25
n3wborn left06:26
tango_ left06:28
fjellfras_ joined06:31
fjellfras left06:32
kneeki|aa joined06:33
quizzi joined06:33
Mattiaslndstrm joined06:34
kneeki|a left06:37
random_yanek left06:38
kegster left06:39
kegster joined06:40
mase-tech joined06:40
thiago left06:41
jubal left06:41
jubal_ joined06:41
jcbitter left06:42
fairuz joined06:42
oatmealraisin joined06:43
kegster left06:43
gareppa joined06:43
kegster joined06:44
jubal joined06:45
jubal_ left06:45
causa_sui left06:45
jcbitter joined06:46
gareppa left06:47
neightchan joined06:51
iNs left06:51
jcbitter left06:51
iNs joined06:51
jcbitter joined06:54
sQVe left06:54
sQVe joined06:55
neightchan left06:56
pr100pr100|afk06:59
jcbitter left07:00
rkta left07:00
rkta joined07:01
jcbitter joined07:01
TomyWork joined07:01
Eryn_1983_FL left07:01
clime left07:04
pr100|afk left07:06
Giszmo joined07:07
random_yanek joined07:07
SkarmoutsosV joined07:07
freeman42y left07:11
fphilipe_ left07:14
Giszmo left07:16
Anthaas left07:16
Anthaas joined07:18
crose left07:24
database2 joined07:24
Wulf left07:25
DWestCoast left07:30
fphilipe_ joined07:31
barteks2x_ joined07:33
barteks2x left07:33
oxymoron93 joined07:33
barteks2x_barteks2x07:33
lalit left07:34
lungaro_ joined07:36
donofrio_ joined07:36
Ekho joined07:36
Nokurn_ joined07:36
jomo_9 joined07:36
lungaro left07:37
donofrio left07:37
jomo_ left07:37
archpc left07:37
Nokurn left07:37
Viking667 left07:37
wagle left07:37
archpc joined07:37
wagle joined07:38
database2 left07:38
fjellfras_ left07:41
hellauer joined07:42
hellauer left07:43
arecaceae left07:48
mimajof joined07:48
arecaceae joined07:49
yonder left07:51
Makaveli7 joined07:51
keepLearning512 left07:51
stitched_unicorn joined07:54
Joel left07:59
stitched_unicorn left08:00
joebobjoe joined08:01
joebobjoe hi when I'm doing an interactive rebase am I in a detached head mode?08:02
someone told me I'm not in detached head mode I'm in rebase mode08:02
_ikke_ during the rebaes you are certainly in a detached HEAD state08:03
joebobjoe knew they were a dumb fucker08:05
thanks08:05
Joel joined08:06
dodobrain lol08:15
is_null left08:15
floppydh joined08:16
alystair left08:17
nabil__ joined08:19
nabil_ left08:22
nabil_ joined08:22
SwiftMatt left08:23
stitched_unicorn joined08:23
alystair joined08:24
stitched_unicorn left08:24
lalit joined08:24
nabil__ left08:24
Joel left08:31
cdown_ joined08:31
def_jam joined08:33
Joel joined08:34
cdown left08:34
cdown_cdown08:34
eb0t_ joined08:34
eb0t left08:34
eblip left08:34
firas joined08:36
firas left08:36
finn0 left08:37
Goplat left08:38
dre_ joined08:38
barteks2x left08:39
rkta left08:41
rkta joined08:41
feriman joined08:42
libertyprime left08:42
Eryn_1983_FL joined08:43
keepLearning512 joined08:48
mase-tech left08:48
fairuz left08:50
joebobjoe left08:50
T_UNIX joined08:50
joebobjoe joined08:53
fairuz joined08:53
jottr joined08:54
Fusl left08:55
Fusl joined08:56
joebobjoe left08:59
finalbeta left09:01
finalbeta joined09:01
Bobdude left09:04
fairuz left09:04
polman joined09:05
Lucas_Gray joined09:06
ave_milia joined09:07
Viking667 joined09:10
Lucas_Gray left09:11
Lucas_Gray joined09:12
kegster left09:12
barteks2x joined09:12
kegster joined09:12
royal_screwup21 joined09:13
clime joined09:15
Bobdude joined09:16
hojang joined09:17
zamba left09:22
Bobdude left09:22
SkarmoutsosV left09:24
zamba joined09:25
figuinhas joined09:27
Wryhder joined09:29
Lucas_Gray left09:30
WryhderLucas_Gray09:30
raatiniemi left09:37
Atlenohen joined09:37
fjellfras joined09:39
fjellfras left09:39
fjellfras joined09:40
hojang left09:41
howdoi joined09:45
Lucas_Gray left09:48
hojang joined09:52
zamba left09:56
Noti left09:56
SteffanW joined09:56
cdown_ joined09:58
zamba joined09:58
Lucas_Gray joined09:58
alystair left10:00
cdown left10:01
cdown_cdown10:01
inkbottle left10:02
inkbottle joined10:02
dre_ left10:05
crose joined10:06
ryouba joined10:07
ryouba it's a stupid question, but just to (hopefully) alleviate my fears:10:07
royal_screwup21 left10:07
ryouba files under git lfs control *do* get stored in multiple version on the server somewhere, right?10:07
or only ever the latest version and all prior ones are lost forever?10:07
lalitlalitmee10:12
fstd_ joined10:14
jomo_9jomo_10:17
dre_ joined10:18
fstd left10:18
fstd_fstd10:18
neightchan joined10:18
Fischmop joined10:18
dre_ left10:19
malmalmal joined10:19
mrtnt I cloned a repo from GitHub and made some changes to some files. Now I would need to make a pull request. As I understand, I need to first create a branch. However, what happens with my changes when I create a new branch? Or should I first commit my changes to master and then create a new branch?10:19
dre_ joined10:19
canton7 mrtnt, if you create a new branch from your current commit and check it out, your changes will stay just as they are in your working copy10:20
mrtnt, so you can 'git checkout -b mybranch', then add and commit as normal10:20
dre_ left10:20
dre_ joined10:21
mrtnt canton7: thanks!10:22
randomdude999 joined10:23
neightchan left10:24
lankanmon left10:32
keepLearning512 left10:32
fling ryouba: `git clone /on/the/server/somewhere` and see for yourself10:33
nuala joined10:34
lankanmon joined10:34
Fischmop left10:34
nuala left10:34
lalitmee left10:34
nuala joined10:35
lalitmee joined10:35
nuala left10:35
nuala joined10:35
randomdude999 left10:36
randomdude999 joined10:36
randomdude999 left10:38
randomdude999 joined10:38
nuala left10:39
omry left10:40
Fischmop joined10:42
randomdude999 left10:42
randomdude999 joined10:43
randomdude999 left10:44
randomdude999 joined10:45
Lucas_Gray left10:46
Fischmop left10:47
keepLearning512 joined10:49
royal_screwup21 joined10:51
randomdude999 left10:53
randomdude999 joined10:53
randomdude999 left10:56
finn0 joined10:57
randomdude999 joined10:57
malmalmal left10:58
nuala joined10:59
randomdude999 left11:01
randomdude999 joined11:01
troulouliou_div2 joined11:02
randomdude999 left11:03
randomdude999 joined11:03
randomdude999 left11:05
lacrymol1gy left11:05
emsjessec joined11:05
randomdude999 joined11:05
randomdude999 left11:06
randomdude999 joined11:06
nerosnm joined11:06
randomdude999 left11:10
randomdude999 joined11:10
royal_screwup21 left11:12
Lucas_Gray joined11:15
nuala left11:17
Lucas_Gray left11:19
randomdude999 left11:20
randomdude999 joined11:20
nuala joined11:22
randomdude999 left11:22
randomdude999 joined11:22
randomdude999 left11:23
fjellfras left11:23
randomdude999 joined11:23
Lucas_Gray joined11:24
tonythomas left11:25
dre_ left11:26
leeN joined11:27
Viking667 left11:27
totte left11:28
finn0 left11:30
finn0 joined11:31
randomdude999 left11:35
abbiya left11:35
randomdude999 joined11:36
randomdude999 left11:37
randomdude999 joined11:38
Aquazi joined11:42
subopt joined11:42
ryouba fling: there's thousands of files with paths/names like /var/opt/gitlab/gitlab-rails/shared/lfs-objects/ff/c7 ... they don't really answer my question.11:44
randomdude999 left11:45
tempate Hello. I am having trouble pushing my latest commit. https://bpaste.net/show/zWqQ11:46
randomdude999 joined11:46
tempate I have deleted the vgcore file on src but it is still not letting me push11:46
it looks like it is in the commit's history or something11:46
randomdude999 left11:47
tgunr joined11:47
randomdude999 joined11:47
fling ryouba: I thought the files are there if a path is clonable11:47
ryouba hmm11:49
i'll have to test without gitlab and some pristine repo via ssh11:49
winny left11:49
tempate I would like to remove all the commits that haven't yet been pushed, but I don't know how to do it11:50
royal_screwup21 joined11:52
randomdude999 left11:52
randomdude999 joined11:53
VladGh joined11:53
beastDiv_ joined11:56
MACscr joined11:56
randomdude999 left11:56
randomdude999 joined11:56
tempate can someone help me out?11:57
Laban joined11:57
beastDiv_ left11:57
ryouba tempate: crude but effective (i don't know a better way myself unfortunately) if you really want to irreversibly erase all that info: "cd your-clone ; rm -rf * ; git checkout *". i'm sure i'll be lynched now.11:59
Laban Howdy! How can I see when a specific line was changed across commits? It's a version line and I'd like to go back in history and tag each version change.11:59
randomdude999 left12:00
randomdude999 joined12:00
AtumT joined12:00
Lucas_Gray left12:02
randomdude999 left12:02
randomdude999 joined12:03
Lucas_Gray joined12:03
tempate ryouba: what would rm -rf * do?12:04
I don't want to remove the files themselves, just restart git's history to the latest commit12:04
ryouba tempate: what it says on the packaging - it deletes the entire working copy. but then the next command restores the entire working copy to the state of the latest (locally available) commit. of course, if you had created new files that had never been committed, those are then gone, too.12:07
tempate I have...12:08
learningc joined12:08
ryouba okay, then don't run that. in my crude world, i would manually move those onto my desktop first and then move them back afterwards.12:09
randomdude999 left12:09
randomdude999 joined12:09
tempate I would expect it to be a command for such a simple task12:09
SkarmoutsosV joined12:11
Lucas_Gray left12:12
ryouba like i said, that's just *my* lazy, redneck, crude, way of dealing with this.12:13
(still hoping for someone knowledgable to bash my head in)12:13
hojang left12:18
neightchan joined12:19
VladGh left12:20
neightchan left12:24
randomdude999 left12:26
randomdude999 joined12:27
Lucas_Gray joined12:28
bremner left12:30
pyfgcr joined12:31
igemnace left12:31
randomdude999 left12:32
henrebotha[m] Laban: `git log -L1,2:README.md` will show you the history of commits that touched lines 1 through 2 of README.md12:32
bremner joined12:32
randomdude999 joined12:32
randomdude999 left12:36
randomdude999 joined12:37
rsrx joined12:38
rafasc joined12:38
sz0 joined12:39
Makaveli7 left12:42
neightchan joined12:43
neightchan left12:49
randomdude999 left12:52
randomdude999 joined12:52
xcm left12:54
randomdude999 left12:54
randomdude999 joined12:54
xcm joined12:56
SkarmoutsosV left12:58
random_y1 joined13:00
Laban Thanks henrebotha[m]13:02
Any idea on how to find which commit set a line to 'MinorVersion = 51' ?13:03
inkbottle left13:03
random_yanek left13:03
randomdude999 left13:03
inkbottle joined13:03
lalitmee left13:03
randomdude999 joined13:04
As4xk left13:06
Laban I'm strongly thinking that my previous co-workers just skipped that version :p13:06
As4xk joined13:06
abraxxas joined13:07
randomdude999 left13:08
randomdude999 joined13:08
cbreak left13:11
cbreak joined13:12
rafasc Laban: git log -S or -G13:12
randomdude999 left13:13
randomdude999 joined13:13
caskd left13:14
randomdude999 left13:18
randomdude999 joined13:18
caskd joined13:19
randomdude999 left13:21
randomdude999 joined13:22
canton7 Laban, 'git gui blame path/to/file'13:22
(or just 'git blame', but it's a little harder to use)13:22
rafasc canton7: also forgot git log -L, which may be the best one for this use case.13:24
kerframil joined13:25
keepLearning512 left13:25
randomdude999 left13:26
randomdude999 joined13:26
oxymoron93 it was mentioned few lines before you came rafasc , so you guys covered it all now :D13:27
Laban Found it by narrowing down the commits of version 50 and 52. :)13:28
hellauer joined13:29
leeN left13:32
finn0 left13:35
finn0 joined13:35
randomdude999 left13:36
randomdude999 joined13:36
randomdude999 left13:39
randomdude999 joined13:39
Mike11 joined13:41
floppydh left13:42
john2496 joined13:43
finn0 left13:45
Mike11 left13:45
randomdude999 left13:47
randomdude999 joined13:47
finn0 joined13:48
caskd left13:53
kadz[m] Hi. I just realized that my feature branch is based on an older master branch. I have pushed the branch to GitHub and opened a pull request. I have updated my master branch and done a `git rebase master` on my feature branch. Will running `git push` affect my commit history or will it just update the branch and keep the commit logs intact?13:54
randomdude999 left13:54
kadz[m] By intact I mean that the logs would show my commits at the top as new and the older commits as those from the new master branch?13:54
randomdude999 joined13:54
comptroller left13:57
randomdude999 left13:57
randomdude999 joined13:57
caskd joined13:57
greggerz joined13:59
caskd left14:01
keepLearning512 joined14:02
caskd joined14:02
moritz what you'll get from a git push is a [rejected]14:02
because you've re-written history that had been published before14:03
if nobody else has worked on that, you can git push --force-with-lease14:03
rafasc the "branch" and the "logs" are the same thing.. It is not something that is kept on the side.14:03
boombatower joined14:05
BeerLover joined14:05
oxymoron93 also, commits will be new, their datestamp will change, but authorship datestamp should remain?14:05
omnireq left14:05
rafasc By same I mean that git log is a tool that lets visualize the commits in a branch. It isn't some sort of logfile that tracks commits made.14:05
comptroller joined14:06
randomdude999 left14:08
randomdude999 joined14:08
Xiti left14:09
shored left14:10
shored joined14:10
Xiti joined14:10
courrier joined14:11
finn0 left14:13
markzen in this commnd: git push origin origin:refs/heads/new_feature_name14:13
how is the src part of the refspec resolved?14:13
I understand "git push origin master:/ref/heads/meister"14:14
randomdude999 left14:14
markzen ie. when the src part if a ref14:14
_ikke_ afaik it resolves to the default branch (pointed to by HEAD) for that remote14:14
rafasc markzen: some commands resolve remote names to refs/remotes/<remote_name>/HEAD14:14
_ikke_ ^14:14
randomdude999 joined14:14
markzen makes sense, thks14:15
rafasc But I am not sure if it would work in refspecs, I assume it does from your question.14:15
markzen yeah14:15
rafasc I would not rely on that, because the presence is remote_name/HEAD is not very reliable.14:16
royal_screwup21 left14:16
randomdude999 left14:16
rafasc if you clone, it creates it, but if you init+remote add, it doesn't.14:16
randomdude999 joined14:16
rafasc it's also different on normal vs bare repos...14:17
markzen good point14:17
not planning on using it, just wanted to understand it14:17
rafasc sure, that is certainly something that caught me offguard the first time I encountered.14:18
nerosnm left14:24
learningc left14:24
Xiti left14:25
thiago joined14:25
tempate left14:25
figuinhas left14:27
figuinhas joined14:28
royal_screwup21 joined14:28
randomdude999 left14:30
randomdude999 joined14:31
clime left14:32
randomdude999 left14:34
randomdude999 joined14:34
mikeputnam left14:36
sweatsuit left14:36
figuinhas left14:37
randomdude999 left14:37
randomdude999 joined14:37
figuinhas joined14:38
Giant81 joined14:38
sweatsuit joined14:41
finn0 joined14:42
__that__ joined14:44
__that__ HI all14:44
is there a way to import the content of one branch into another and only the content and not the history, via git?14:45
learningc joined14:45
__that__ I have been doing plenty of tests on a branch in which I am only interested in the final content... Not the commits14:46
rafasc __that__: yes, use merge --squash other_branch14:46
__that__ wow --squash, never heard of. Thanks14:47
oxymoron93 left14:48
abraxxas left14:48
abraxxas joined14:53
nerosnm joined14:53
Xiti joined14:54
sQVe left14:57
nerosnm left14:57
dege joined14:57
nuala left14:58
subopt_ joined15:00
subopt left15:02
finn0 left15:03
finn0 joined15:04
randomdude999 left15:05
randomdude999 joined15:05
randomdude999 left15:06
randomdude999 joined15:07
SteffanW left15:07
feriman left15:08
mrtnt I have a 2FA in GitHub enabled. Am I correct, that personal access tokens are the only way to authenticate in case of HTTPS and 2FA?15:09
jast mrtnt: yes15:13
assuming you're talking about repo fetch/push15:14
randomdude999 left15:14
randomdude999 joined15:15
mrtnt jast: yes. So I guess if 2FA is enabled, then one should use SSH protocol for fetch/push?15:15
randomdude999 left15:16
randomdude999 joined15:16
jast mrtnt: it certainly makes things easier15:16
mrtnt jast: mhmh. Thanks!15:16
jast I very much prefer SSH anyway - I use SSH keys for a bunch of things already, so I don't really have any extra effort compared to typing an HTTP password all the time or storing it on the filesystem somewhere15:18
nerosnm joined15:18
bluezone joined15:18
mimajof left15:20
realies left15:21
greggerz left15:22
raffo joined15:27
nerosnm left15:29
rfuentess left15:31
finn0 left15:31
BeerLover left15:32
finn0 joined15:32
kezimo left15:34
jottr left15:35
randomdude999 left15:39
randomdude999 joined15:40
jottr joined15:40
mowcat joined15:43
mowcat left15:43
TomyWork left15:43
mowcat joined15:43
User_ joined15:46
polman left15:46
polman joined15:46
randomdude999 left15:48
randomdude999 joined15:48
learningc left15:48
thiago left15:50
royal_screwup21 left15:50
randomdude999 left15:52
jottr left15:52
randomdude999 joined15:53
invisbl joined15:53
jottr joined15:54
Bobdude joined15:56
jottr left15:59
dijitol joined16:00
escherial joined16:01
escherial left16:01
randomdude999 left16:01
randomdude999 joined16:02
subopt_ left16:03
nerosnm joined16:03
javaJake left16:05
User_ left16:06
escherial joined16:06
javaJake joined16:07
abraxxas left16:10
omnireq joined16:12
nerosnm left16:13
Lucas_Gray left16:14
vavkamil left16:14
randomdude999 left16:15
randomdude999 joined16:15
subopt joined16:19
finn0 left16:27
igemnace joined16:27
thiago joined16:30
randomdude999 left16:32
randomdude999 joined16:32
jottr joined16:33
Tie-1000 joined16:33
pyfgcr left16:35
jottr left16:37
clime joined16:37
sz0 left16:39
__that__ left16:39
randomdude999 left16:39
sweatsuit left16:39
randomdude999 joined16:39
sweatsuit joined16:41
impermanence joined16:42
TimWolla left16:43
Inline joined16:45
n3wborn joined16:46
pie_ joined16:46
nerosnm joined16:49
TimWolla joined16:50
randomdude999 left16:51
randomdude999 joined16:52
Phylock joined16:53
Atlenohen left16:55
irrgit left16:59
is_null joined16:59
emg left16:59
randomdude999 left17:01
randomdude999 joined17:01
flaviodesousa joined17:01
flaviodesousa left17:02
pie_ left17:02
nerosnm left17:03
irrgit joined17:04
randomdude999 left17:04
Tie-1000 left17:04
Tie-1000 joined17:05
randomdude999 joined17:05
dijitol left17:08
crose left17:10
jottr joined17:10
kneeki|a joined17:10
shored left17:10
shored joined17:10
kneeki|aa left17:12
fphilipe_ left17:12
keepLearning512 left17:13
nerosnm joined17:15
jottr left17:16
randomdude999_ joined17:19
randomdude999 left17:19
randomdude999_randomdude99917:19
nerosnm left17:22
shored left17:22
shored joined17:23
sphalerite is there a way to show dates in git reflog?17:23
_ikke_ sphalerite: git log -g17:23
sphalerite _ikke_: awesome, thanks! Amazing response time :D17:24
_ikke_ :-)17:24
man git as a service ;-)17:24
gitinfo the git manpage is available at https://gitirc.eu/git.html17:24
jottr joined17:26
sphalerite _ikke_: oh, hm, that shows commit dates, not reflog dates :/ I want to find out when I moved from one branch to another, so I can go back to a zfs snapshot before I broke stuff. Oh hey, I'm XYing, aren't I??17:28
_ikke_ ;-)17:30
sphalerite any idea how I can do that? ;)17:30
pie_ joined17:30
_ikke_ hold on17:30
jottr left17:31
vishal something like git reflog --pretty='%cd %h %gd %gs'17:31
orbyt_ joined17:31
sphalerite vishal: hm nope, that displays the commit date, not the checkout date17:32
alystair joined17:32
nerosnm joined17:32
_ikke_ Strange, the only thing I can think of is directly looking at .git/logs/HEAD17:32
rafasc the reflog does store the date..17:32
vishal hmm true17:33
_ikke_ it does, but I don't see any option to show the reflog date17:33
rafasc but yeah, I don't think log is able to parse it.17:33
_ikke_ It does parse reflog entries, it just does not expose it for some reason17:33
maybe someones scratch to it17:33
TomTom left17:34
nerosnm left17:36
_ikke_ Am I crazy? What's the git mailing list archive maintained by Eric Wong?17:37
ah17:37
https://public-inbox.org/git/17:37
Somehow I had public-info.org in my head17:37
dijitol joined17:39
m1rror left17:39
m1rror joined17:40
rafasc is public inbox from maintained by Eric Wong?17:41
nerosnm joined17:41
rafasc strange sense of dejavu there, I was reading his email on deprecating git-filter-branch when you asked. spooky17:42
vlooe joined17:43
dijitol left17:43
dijitol joined17:44
_ikke_ yes, it is17:44
dijitol left17:45
liori left17:46
liori joined17:47
nerosnm left17:48
wildlander joined17:53
vlooe I have a really slow repo here on windows/cygwin. a simple git status needs 10s. Other repos on this machine are much "faster"17:55
duderonomy left17:55
bin_bash rip17:55
nerosnm joined17:56
vlooe i guess it is related to the amount of submodules in this repo17:56
Tie-1000 left17:56
Tie-1000 joined17:57
figuinhas left17:57
thiago left17:58
nerosnm left18:00
Sasazuka joined18:01
TomyLobo joined18:01
cd left18:01
jottr joined18:04
ave_milia left18:05
gareppa joined18:08
keepLearning512 joined18:08
jottr left18:09
randomdude999 left18:09
randomdude999_ joined18:09
randomdude999_randomdude99918:09
thiago joined18:10
randomdude999 left18:11
randomdude999 joined18:11
Tie-1000 left18:15
Tie-1000 joined18:17
pie_ left18:17
courrier left18:18
randomdude999 left18:19
randomdude999 joined18:20
randomdude999 left18:23
randomdude999 joined18:23
randomdude999 left18:24
haasn left18:24
randomdude999 joined18:25
john2496 left18:27
jottr joined18:28
Aquazi left18:28
sauvin left18:28
freeman42x joined18:29
haasn joined18:30
orbyt_ left18:30
T_UNIX left18:30
randomdude999 left18:31
randomdude999 joined18:31
SpeakerToMeat joined18:32
randomdude999 left18:32
randomdude999 joined18:33
SpeakerToMeat left18:35
clime left18:40
randomdude999 left18:40
randomdude999 joined18:41
troulouliou_div2 left18:42
SpeakerToMeat joined18:43
shored left18:43
shored joined18:44
randomdude999 left18:45
randomdude999 joined18:45
pie_ joined18:46
lalitmee joined18:47
lalitmee left18:48
lalitmee joined18:49
shored left18:49
shored joined18:50
nuala joined18:51
shiza joined18:51
randomdude999 left18:52
thiago left18:52
realies joined18:52
randomdude999 joined18:52
pie_ left18:55
n3wborn left18:55
randomdude999 left18:55
randomdude999 joined18:56
finn0 joined18:57
SkarmoutsosV joined18:57
Giant81 left18:59
nerosnm joined19:02
nerosnm left19:04
nerosnm joined19:05
Revan- joined19:08
Giant81 joined19:11
pie_ joined19:14
iam730 joined19:16
thiago joined19:17
clime joined19:20
JanC left19:21
JanC joined19:21
pie_ left19:23
justanotheruser left19:23
fflam left19:23
MACscr left19:24
justanotheruser joined19:24
shored left19:24
shored joined19:24
MACscr joined19:25
pie_ joined19:26
omnireq left19:26
omnireq joined19:28
vlooe left19:28
Cabanossi left19:30
pie_ left19:31
Cabanossi joined19:32
Mattiaslndstrm left19:32
fflam joined19:36
randomdude999 left19:37
randomdude999 joined19:38
savolla joined19:38
savolla left19:39
is_null left19:39
randomdude999 left19:42
randomdude999 joined19:42
randomdude999 left19:43
tomaw left19:44
randomdude999 joined19:44
nuala left19:45
tomaw joined19:46
khisanth_ left19:46
orbyt_ joined19:49
nerosnm left19:51
nowhere_man joined19:53
rafasc left19:54
nerosnm joined19:55
d1rewolf joined19:55
raatiniemi joined19:55
emsjessec left19:56
fphilipe_ joined19:57
kneeki joined19:58
randomdude999 left19:58
randomdude999 joined19:59
khisanth_ joined19:59
kneeki|a left20:00
is_null joined20:00
pie_ joined20:01
Ignacy joined20:06
nerosnm left20:07
randomdude999 left20:08
gareppa left20:08
randomdude999 joined20:09
orbyt_ left20:10
daydreamm joined20:10
daydreamm hello friends, I have deleted a file from my `master` branch and pushed it, but then on another branch the file exists (and I want it to exist) but then when I merge than other branch to master, the file doesn' appear, and it's not being recognised by git, what do?20:11
randomdude999 left20:12
TomTom joined20:12
randomdude999 joined20:12
troulouliou_div2 joined20:13
keepLearning512 left20:15
randomdude999 left20:15
alystair what's the correct way to squash two commits that weren't one after the other?20:15
_ikke_ alystair: interactive rebase20:15
randomdude999 joined20:15
SpeakerToMeat left20:17
m0viefreak joined20:19
Tie-1000 left20:19
SpeakerToMeat joined20:19
Tie-1000 joined20:21
orbyt_ joined20:23
nerosnm joined20:25
cbreak left20:31
nabil__ joined20:31
cbreak joined20:32
nabil_ left20:33
nerosnm left20:34
mase-tech joined20:34
nabil_ joined20:37
keepLearning512 joined20:38
keepLearning512 left20:39
shored1 joined20:39
nabil__ left20:40
shored left20:40
Freshnuts joined20:40
kneeki left20:40
kneeki joined20:42
MACscr left20:44
arinov joined20:45
howdoi left20:45
randomdude999 left20:47
randomdude999 joined20:48
sozuba left20:50
daydreamm left20:51
polman left20:52
nowhere_man left20:55
lmariscal joined20:57
kneeki left20:58
Narrat joined20:59
kneeki joined20:59
randomdude999 left21:00
subopt left21:00
randomdude999 joined21:00
randomdude999 left21:01
randomdude999 joined21:02
shabius left21:03
daydreamm joined21:04
daydreamm left21:12
is_null left21:13
shabius joined21:14
shabius left21:14
shabius joined21:15
abraxxas joined21:15
randomdude999 left21:15
randomdude999 joined21:15
randomdude999 left21:16
SkarmoutsosV left21:16
randomdude999 joined21:17
feriman joined21:18
hellauer left21:19
seven-eleven if I force pushed an ammended commit during a pull request, do I have to notify people that I rewrote the history? i noticed that the changes on the pull request on github were instantly, but someone might have pulled the old version right?21:20
meLon left21:20
vishal seven-eleven: someone might have, in case they're basing workl on your in-progress work (ususally unlikely, but there are valid exceptions of course)21:21
pie_ left21:21
vishal normally if the flow is fork/commit/push/pull-request, then force pushing is ok21:22
dijitol joined21:22
seven-eleven mhm21:22
vishal the PR gets updated automatically, and nothing is a problem since nothing has been merged into upstream at that point21:22
seven-eleven right21:22
sounds like i dont need to notify anybody, they just see the suggested changes immediately21:22
diogenese left21:22
vishal right21:22
seven-eleven oh it actually says in the PR that I "forced pushed ...:master branch from ..."21:23
randomdude999 left21:24
randomdude999 joined21:24
daydreamm joined21:25
mase-tech left21:26
greatgatsby joined21:28
randomdude999 left21:32
randomdude999 joined21:33
randomdude999 left21:34
randomdude999 joined21:35
octav1a left21:36
Cabanossi left21:37
MoziM joined21:38
randomdude999 left21:40
randomdude999 joined21:41
pie_ joined21:42
Cabanossi joined21:42
randomdude999 left21:42
yonder joined21:43
randomdude999 joined21:43
MACscr joined21:45
pie_ left21:50
randomdude999 left21:51
pie_ joined21:52
randomdude999 joined21:52
randomdude999 left21:54
randomdude999 joined21:54
invisbl left21:55
dege left21:58
greatgatsby left21:59
daydreamm left22:02
freeman42x left22:02
archpc left22:03
_xor left22:04
_xor joined22:04
Oatmeal joined22:06
rafasc joined22:07
shored1 left22:10
shored joined22:10
randomdude999 left22:14
lalitmee left22:16
Phylock left22:17
archpc joined22:18
im0nde left22:23
im0nde joined22:23
invisbl joined22:24
invisbl left22:28
daydreamm joined22:28
daydreamm left22:33
scientes joined22:34
pie_ left22:35
finn0 left22:37
pie_ joined22:40
abraxxas left22:40
arinov left22:42
dijitol left22:42
Guess59061 joined22:43
iam730 left22:48
thiago left22:49
Guess59061 Where do I see the history of a release post on GitHub? https://github.com/dtag-dev-sec/tpotce/releases/tag/16.10 This is a release post. In the title it says "Deprecated". Presumably it didn't have that before, so where can I see when that piece of information was edited in?22:49
BonusPlay left22:50
BonusPlay joined22:50
diogenese joined22:51
jast Guess59061: I believe GitHub has its own metadata (i.e. outside the git repo) for releases and I'm not seeing them making a history of the changes available anywhere22:52
Guess59061 jast: Oh, I see... Okay, thank you very much. I couldn't find that information anywhere either...22:54
jast btw in git itself, tags don't have history, either22:56
so if you were to overwrite a git tag, the old one is kind of gone22:56
Guess59061 Thanks for telling me.22:56
Guess59061 left22:57
ravndal left22:59
ravndal joined23:02
omnireq left23:05
feriman left23:07
BonusPlay left23:07
BonusPlay joined23:07
braderhart joined23:08
cbreak left23:12
cbreak joined23:12
boombatower left23:14
duderonomy joined23:23
dartmouthed left23:26
shored left23:29
shored joined23:29
rsrx left23:32
dre_ joined23:34
sgen joined23:34
dre_ left23:37
Atlenohen joined23:41
kezimo joined23:42
rwp joined23:43
rwp I have a sandbox on master that is behind origin/master by several commits. How can I advance it exactly one commit toward origin/master?23:45
thiago joined23:48
rwp Nevermind. Eventually I deduced that "git merge <commit>" where <commit> was the next toward origin/master was the way to do this.23:54
iam730 joined23:58
kezimo left23:58
pie_ left23:59

Logs Search ←Prev date Next date→ Channels Documentation