IRCloggy #git 2020-05-28

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.

2020-05-28

ghost43 left00:00
ghost43 joined00:01
dedowsdi joined00:02
misuto left00:07
braj joined00:08
Brainium left00:08
st-gourichon-fid left00:11
justanotheruser joined00:13
st-gourichon-fid joined00:14
ferdna joined00:19
tiin57 left00:20
tiin57 joined00:23
royal_screwup21 left00:24
royal_screwup21 joined00:24
vicfred left00:25
shabius_ left00:26
shabius_ joined00:26
denisse_ joined00:28
denisse left00:28
jayaura left00:28
cpackham left00:28
karlding left00:28
hsiktas[m] left00:28
Celmor[m] left00:28
morguldir left00:28
Olipro_ joined00:29
Olipro left00:29
Benzi-Junior left00:29
Olipro_Olipro00:29
denisse_denisse00:29
donofrio_ left00:30
Benzi-Junior joined00:30
braj left00:30
donofrio_ joined00:30
Celmor[m] joined00:31
cpackham joined00:31
morguldir joined00:32
crose left00:33
hsiktas[m] joined00:33
orbyt_v7 left00:34
misuto joined00:35
eqw joined00:36
troulouliou_div2 left00:36
jayaura joined00:36
braj joined00:41
kchz left00:45
SpeakerToMeat joined00:47
rsrx left00:48
troulouliou_div2 joined00:48
tiin57 left00:49
tiin57 joined00:53
royal_screwup21 left01:01
royal_screwup21 joined01:01
Heirlung left01:02
lucasb left01:03
Heirlung joined01:03
nuala left01:05
royal_screwup21 left01:06
davispuh left01:09
flex14 left01:18
flex14 joined01:18
shush joined01:19
tiin57 left01:19
tiin57 joined01:23
fission6 joined01:28
lukd left01:30
lukd joined01:31
ShapeShifter499 left01:31
ShapeShifter499 joined01:31
Abbott joined01:34
jwest left01:37
shush left01:41
shush joined01:41
flex14 left01:42
flex14 joined01:42
Sasazuka joined01:43
Sasazuka left01:43
flex14 left01:43
lambda left01:46
tiin57 left01:50
g4570n left01:53
tiin57 joined01:53
orbyt_ joined01:54
fission6 left01:56
ShapeShifter499 left01:56
lambda joined02:04
bitnoize left02:06
shush left02:09
shush joined02:10
shush left02:15
shush joined02:16
rewrited left02:17
nuala joined02:17
tiin57 left02:20
Sleepy63 joined02:21
lambda left02:21
j9 joined02:22
lagothrixGuest7099302:22
Guest70993 left02:22
lagothrix joined02:22
clime left02:23
perrier-jouet left02:23
tiin57 joined02:23
Cabanossi left02:23
j9 Need help please: I am using Visual Studio Code on a Mac and when I push I get remote: permission to (repo name) denied to (name)... error 40302:24
How can I resolve this02:24
I can push pull from GitHub Desk without issues02:24
I think there is a config issue within VSC02:24
any help is appreciated...02:25
rewt check what credentials vscode is using02:27
j9 Okay02:27
is that a simple find? New to VSC02:27
rewt no idea; that's more of a vscode question02:28
j9 LOL okay thank you02:28
rewt maybe somewhere in settings02:28
j9 Thank you02:28
rewt np02:28
chachasmooth left02:29
Cabanossi joined02:30
chachasmooth joined02:33
karab44 joined02:36
ferdna left02:39
shush left02:40
j9 left02:42
shush joined02:42
jetchisel joined02:43
Newami joined02:44
shush left02:47
saml left02:48
tiin57 left02:49
tiin57 joined02:53
Rav3n joined02:58
Sonderblade joined02:58
SpeakerToMeat left03:02
royal_screwup21 joined03:02
denisse left03:02
denisse joined03:03
ShapeShifter499 joined03:03
lambda joined03:04
SpeakerToMeat joined03:05
royal_screwup21 left03:06
troulouliou_div2 left03:08
jwest joined03:10
karab44 left03:15
shush joined03:16
SpeakerToMeat left03:19
SpeakerToMeat joined03:19
tiin57 left03:20
shush left03:20
tiin57 joined03:23
omar_trisquel joined03:26
cbreak left03:31
cbreak joined03:31
Goplat joined03:39
omar_trisquel left03:40
kupi left03:43
aw1_ joined03:45
aw1 left03:47
Muimi joined03:49
tiin57 left03:49
jetchisel left03:51
jetchisel joined03:51
tiin57 joined03:53
bxu joined03:55
Betal left03:59
sostenuto left04:03
MG joined04:03
sostenuto joined04:07
donofrio__ joined04:07
Trieste left04:07
Trieste joined04:09
donofrio_ left04:10
justanotheruser left04:13
fstd_ joined04:14
troulouliou_div2 joined04:14
dmc left04:16
fstd left04:17
fstd_fstd04:17
MG left04:19
tiin57 left04:19
dmc joined04:20
braj left04:21
jetchisel left04:21
tiin57 joined04:23
justanotheruser joined04:23
vicfred joined04:28
Guest20 joined04:33
shush joined04:33
dmc left04:34
shush left04:38
troulouliou_div2 left04:41
causasui left04:42
tiin57 left04:50
dedowsdi left04:52
tiin57 joined04:53
Cabanossi left04:56
Cabanossi joined04:58
Blkt joined04:58
Blkt left05:00
ghost43 left05:00
ghost43 joined05:00
shush joined05:04
shush left05:09
Blkt joined05:10
Muimi left05:12
billyxu joined05:17
billyxu left05:18
calcul0n joined05:18
billyxu joined05:18
billyxu left05:19
billyxu joined05:19
tiin57 left05:19
bxu left05:20
cgi left05:20
tiin57 joined05:23
dmc joined05:24
Junior joined05:28
orbyt_ left05:33
Trieste left05:34
thiago left05:35
Trieste joined05:37
orbyt_ joined05:42
Guest20 left05:44
Trel left05:49
dedowsdi joined05:50
tiin57 left05:50
raven-au_ joined05:50
Guest20 joined05:50
raven-au left05:51
raven-au_raven-au05:51
bettencb joined05:52
tiin57 joined05:53
Intelo left05:54
hexnewbie left05:59
andreas303 left06:01
Trel joined06:02
hexnewbie joined06:04
orbyt_ left06:05
vals_ joined06:13
tango_ left06:15
gp5st_ joined06:18
fitzgerald1337 joined06:18
tiin57 left06:19
Harwood joined06:19
Harwood left06:19
gp5st left06:19
chele joined06:23
NeoCron joined06:23
tiin57 joined06:23
andreas303 joined06:33
inkbottle left06:36
rfuentess joined06:38
tonyj left06:42
hexnewbie left06:42
Goplat left06:45
Phylock joined06:45
mightyjens joined06:47
tiin57 left06:49
clime joined06:52
Heirlung left06:52
tiin57 joined06:52
bettencb left06:57
fabs joined06:59
mobidrop joined07:00
xerox_ left07:03
Heirlung joined07:04
shush joined07:05
shush left07:10
xerox_ joined07:11
tonythomas joined07:11
wootehfoot joined07:13
wootehfoot left07:15
Technodrome left07:16
shomon joined07:18
tiin57 left07:19
shomon hi, I've gotten myself into a git mess... my remote branch has some config files missing from gitignore, but I can't commit back until I fix it. Should I add them to gitignore in the remote as a new commit and then pull again to the local? thanks for any ideas or help!07:21
KnoP joined07:22
tiin57 joined07:23
oprypin left07:24
Sonderblade left07:27
quetz joined07:29
CCR5-D32 left07:30
oprypin joined07:32
dedowsdi left07:35
Rav3n left07:37
zulutango joined07:40
billyxu left07:42
tiin57 left07:49
tiin57 joined07:54
mat001 left07:57
chuffer joined07:57
algun joined07:58
dedowsdi joined07:58
xcm left07:58
famubu joined07:59
algun What's the difference between `git reset (--soft)`, `git reset --heard`, and `git checkout .` and `git clean -f`?07:59
ikke git clean -f removes untracked files08:00
(only)08:00
famubu Hi. I did a commit and realized it was not good and went back to previous commit with `git reset --hard HEAD~1`. Does that mean the bad commit still exists? How can I delete it?08:00
roboirc left08:01
pikapika left08:01
nikivi left08:01
acetakwas left08:01
POQDavid left08:01
ikke famubu: it still exists, yes, but usually you don't have to care about removing it. git will remove it eventually and as long as it's not part of any branch anymore, it will never be shared08:01
wootehfoot joined08:02
famubu ikke: Okay. Thanks.08:03
ikke algun: git reset --soft only changes where you current branch points to08:04
without any arguments it does basically nothing08:05
maryo joined08:05
ikke git reset will do the same thing as soft, but updates the index (staged files) as well08:05
famubu left08:05
algun ikke, doesn't it unstage changes? Or is git reset different from git reset --soft?08:05
ikke algun: yes08:05
git reset is the same as git reset --mixed08:05
onmeac joined08:05
ikke (though, without specifying --mixed you can specify paths as well08:06
)08:06
gordonfish left08:06
ikke git checkout . and git reset --hard are the same in only that specific case08:06
xcm joined08:06
Abbott left08:13
Abbott joined08:16
justanotheruser left08:19
tiin57 left08:19
chachasmooth left08:22
tiin57 joined08:23
shomon left08:27
geowiesnot joined08:28
justanotheruser joined08:28
Muimi__ joined08:32
chachasmooth joined08:32
lem-fr left08:33
d00f joined08:33
lem-fr joined08:35
d00f left08:39
mr_shaman joined08:42
algun ikke, git reset --soft also moves things from the "reverted commits" to the index, right?08:44
ikke git reset --soft does not touch the index08:45
so the content will remain staged08:46
tiin57 left08:50
phcerdan joined08:51
tiin57 joined08:52
tens0r joined08:54
phcerdan Is there a way replace a file in history with a modern version? I have a repo with uncompressed `png`, and I would like to rewrite history, but the references to old pngs to use the compressed version.08:54
KrachbummNT joined08:56
ikke man git replace08:57
gitinfo the git-replace manpage is available at https://gitirc.eu/git-replace.html08:57
ikke combined that with man git filter-branch or !filter-repo08:58
gitinfo A new git add-on that greatly improves on git-filter-branch: https://github.com/newren/git-filter-repo08:58
the git-filter-branch manpage is available at https://gitirc.eu/git-filter-branch.html08:58
tens0r left09:04
shush joined09:06
c0c0 joined09:08
acetakwas joined09:08
pikapika joined09:10
POQDavid joined09:10
chuffer left09:11
shush left09:11
nikivi joined09:12
zulutango left09:13
Newami left09:14
zulutango joined09:14
Metalsutton joined09:18
tiin57 left09:19
bitnoize joined09:21
locrian9 joined09:21
tiin57 joined09:23
sunrunner20 left09:27
jwest_ joined09:31
jwest left09:34
clara97 joined09:39
g00s left09:39
aliss joined09:40
acetakwas left09:41
acetakwas joined09:42
Guest20 left09:44
locrian9 Trying to create a single 'git format-patch' file that has 3 X commits together (http://ix.io/2nzb) and wanted the patch to be one long instruction to patch over the original file. Found that I could issue the 'git format-patch 2655e96^..b11fb1e' command, but it puts all 3 X commits together (single file) in a long segmented patch (http://ix.io/2nzg).09:44
cxl joined09:45
cxl Hi all, I am using git with bash, and I have aliased gi to git because I always miss the `t` when calling the command. How could I get autocompletion working with `gi` too, not only `git`?09:45
ikke cxl: https://stackoverflow.com/a/15009611/2026109:47
Muimi__ left09:48
Muimi__ joined09:49
tiin57 left09:49
Trieste left09:50
Trieste joined09:52
shush joined09:52
tiin57 joined09:53
c0c0 left09:56
shush left09:57
roboirc joined09:59
phcerdan Thanks ikke for the git replace reference09:59
Guest20 joined10:04
Guest20 left10:09
perrier-jouet joined10:10
Muimi__ left10:13
justanotheruser left10:15
algun left10:17
_xor left10:18
tiin57 left10:20
tiin57 joined10:23
justanotheruser joined10:23
sysh joined10:26
locrian9 left10:26
_xor joined10:32
quizzmaster joined10:36
quizzmasterquizzi10:37
locrian9 joined10:41
Aattas joined10:49
tiin57 left10:49
wnbeser joined10:50
mobidrop left10:51
locrian9 left10:52
mobidrop joined10:52
locrian9 joined10:52
alguien joined10:52
tiin57 joined10:53
locrian9 left10:53
locrian9 joined10:54
locrian9 test10:54
set10:54
crose joined10:55
Metalsutton left10:55
wnbeser left10:56
perrier-jouet left11:00
locrian9 left11:03
locrian9 joined11:03
alguien ikke, so what you're saying is that a commit is a reference into the index? So, a commit creates a reference that encompasses previously-unreferenced indexes?11:04
ikke a commit is created from the contents of the index11:04
alguien what does git reset --soft HEAD^ do exactly?11:05
see, I'm not sure about git's abstractions if I need to ask questions like these11:06
(but that's Linus' fault)11:06
ikke It sets the current branch one commit back11:06
but nothing else11:06
alguien yes, but what does that mean11:08
I don't know.11:08
ikke, it's ok to ignore me if you're not in a mood to guess what I need to learn11:09
locrian9 left11:09
davve joined11:11
ikke It's as if you wen't back in time just before you did the commit command11:11
you changed files, you staged them (git add), but not commit yet11:11
davve can a commit message be too long? (I Think i write way too short ones when I see others write them)11:11
or too short11:12
I feel I should be writing longer ones11:12
alguien davve, usual rules of communication apply I guess11:12
davve but not on the first line11:12
ikke for what git matters: no11:12
tiin57 left11:19
tiin57 joined11:23
Trieste left11:30
Trieste joined11:32
sudoforge left11:32
Brainium joined11:33
rfuentess davve: there is a "golden" rule for commit messages: 53/72 (or something like that) basically says first line cannot be longer than 53 chars, the rest of body is for 7211:34
and for the length of the message it "should be useful to understand what was done" (Whatever that means for you)11:35
ikke !clean_commit11:35
gitinfo [!clean_message] It helps to write clean commit messages. http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html explains how.11:35
rfuentess oh, 50/72 it's seems that my main projects used their ad-hoc rule :P11:36
moldy i find 50 too short11:37
ikke I use 50 as a soft limit11:37
moldy i just use the same limit for the subject as for the body11:38
ikke I do try to keep subjects shorter11:38
moldy (78 in my case)11:38
maxwilliamson left11:39
rewrited joined11:39
rewrited left11:39
rewrited joined11:39
maxwilliamson joined11:41
phcerdan left11:43
akem_akem11:44
locrian9 joined11:45
aw1__ joined11:45
AtumT joined11:46
aw1_ left11:47
AtumT left11:47
duderonomy joined11:48
clara97 left11:48
tiin57 left11:49
CodeSlingerPaul joined11:50
AtumT joined11:51
royal_screwup21 joined11:52
ghormoon left11:53
tiin57 joined11:53
Betal joined11:53
ghormoon joined11:53
locrian9 test12:04
bremner !hi12:05
gitinfo [!welcome] Welcome to #git, a place full of helpful gits. If you have a question, feel free to just go ahead and ask—somebody should answer shortly. For more info on this channel, see https://gitirc.eu/ - Take backups (type !backup to learn how) before taking advice.12:05
locrian9 left12:06
locrian9 joined12:06
locrian9 left12:08
locrian9 joined12:09
locrian9 left12:10
locrian9 joined12:10
mark4 joined12:12
mark4 so im trying to do some stuff on github for work and a co-worker has given me some screenshots of where I need to go but im not seeing the same views he is12:12
i clicked on the 'code' tab and in his screenshot this has a bunch of sub tabs where one is 'overview'12:13
i dont have that12:13
is this setting somewhere?12:13
locrian9 left12:14
bakadesusenpai joined12:14
mark4 his sub tabs under code are overview, yours, active, stale, all branches. how do i get those sub tabs?12:14
calcul0n_ joined12:15
xcm left12:16
ghost43 left12:16
xcm joined12:16
phcerdan joined12:16
ghost43 joined12:17
locrian9_ joined12:17
rfuentess mark4: Sadly your questions are about gitHub (a platform) instead of git. I think you could receive better answer in other channels focused over github12:17
locrian9_ left12:18
calcul0n left12:18
tiin57 left12:19
rafasc joined12:22
tiin57 joined12:22
mark4 is there a github channel?12:23
lol i guess there is :)12:23
tyty12:23
mark4 left12:23
locrian9 joined12:27
mns left12:29
Kaivo left12:30
dqx_ joined12:31
Kaivo joined12:32
PyDon joined12:33
ghost43 left12:33
ghost43 joined12:34
PyDon hi, can anyone help me? I am trying to make sense of git-http-backend. I use Flask and made it work in my app, but for bigger pushes I receive "fatal: the remote end hung up unexpectedly"12:34
As far as I understood, I accept the incoming connection and call git-http-backend with the corresponding environment and commands and connect the streams - "that's it"12:35
Do I need to handle anything else?12:36
fission6 joined12:40
locrian9 How can I create a single 'git format-patch' that doesn't separate my 3 X commits (http://ix.io/2nzb) into a combined 3 piece patch, but rather just creates a single unified patch going from my original file (2655e96) to the final version (b11fb1e). When I tried doing this command 'git format-patch 2655e96^..b11fb1e --stdout > foo.patch', the foo.patch patch has all 3 X commits goes into a combined 3 patch12:41
file (http://ix.io/2nzD). Is there any way to just create a patch that has the single instruction patch set, and not divided into 3 X procedures in the patch?12:41
phcerdan left12:43
ikke I think only by squash those 3 commits into one12:45
git format-patch operates on commits, so if you want just one single patch, you need to create on single commit12:45
rafasc Or alternatively, use git diff HEAD~3 output.12:45
ikke Depends on whether you want to get an actual commit out of it, or just apply the changes somewhere12:47
Maxattax joined12:48
tiin57 left12:49
mr_shaman left12:51
tiin57 joined12:53
phcerdan joined12:57
CCR5-D32 joined12:58
royal_screwup21 left12:58
cr4y1 joined12:59
royal_screwup21 joined12:59
tonythomas left13:00
ryszard joined13:01
ryszard hey13:01
when I create a brach is there any way to add any comment/desriprion to this newly created branch in addition to just branch name?13:02
geowiesnot left13:02
maryo_s joined13:03
maryo left13:07
siers joined13:07
siers can I move to more than the last branch with something other than "g checkout -"? can I see last N checkouted branches?13:07
Guest20 joined13:08
geowiesnot joined13:08
ikke git log -g --oneline | grep "checkout: moving13:10
mat001 joined13:11
ikke there is also HEAD@{-N} as shortcut13:11
so git checkout - is the same as git checkout HEAD@{-1}13:11
siers ah, but HEAD isn't tied to branches, so that's why it works13:11
Marmotte you can use git log --walk-reflogs --grep-reflog=checkout13:12
nedbat ryszard: there are branch descriptions, but i've never used them, and not sure if they are useful: https://ericjmritz.wordpress.com/2015/11/13/using-branch-descriptions-in-git/13:12
Marmotte (with --oneline if you prefer)13:12
NeoCron left13:12
rafasc ryszard: you can use git branch --edit-description13:13
ghost43 left13:13
ikke Marmotte: ah, didn't know about --grep-reflog13:13
ghost43 joined13:13
ikke Marmotte: I tried --grep but that didn't work13:13
nice13:13
much bet13:13
ter13:13
rafasc but only a few select things will use the description, and most of them require you enable it explicitly.13:14
Marmotte ikke: I learnt only one thing : git can do anything in a single command, the hardest is to find how :D13:15
rafasc also, the description is stored on gitconfig, so you cannot share the descriptions, which kinda limits its potential.13:16
ikke Marmotte: :D13:16
PyDon does anyone know why I would need git-receive-pack/git-upload-pack if there is git-http-backend?13:17
ikke Because git http-backend still relies on those two commands to do the actual work?13:17
rafasc PyDon: because the http-backend is mostly a wrapper for receive/upload-pack13:18
tiin57 left13:19
tiin57 joined13:23
ryszard thanks13:24
PyDon oh, is that?13:25
thank you!13:26
kadz joined13:27
bettencb joined13:30
rishi left13:36
PyDon I am experimenting with writing a little git server to understand git better. Would you rather implement git-http-backend or directly receive/upload-pack commands?13:37
I have the feeling git-http-backend is just there to support older Git clients and I should directly focus working on the underlying commands13:37
rishi joined13:37
rafasc Why would you break backwards compatibility on purpose?13:38
syr left13:38
syr joined13:38
mns joined13:38
opal left13:38
rafasc There's two pieces in this puzzle. One is how git negotiates what is to be transferred between the remote and the client.13:39
opal joined13:40
ar1el joined13:40
rafasc That is what upload/receive pack does.13:40
PyDon I don't want to break anything, supporting both would be nice13:40
rafasc The other is how is this communication done, (git-http-backend, ssh, w/e).13:40
PyDon I just don't understand exactly what the relation between all these commands is. For instance..13:41
rafasc They're not the same thing.13:41
PyDon That makes sense, but git-http-backend uses the other two commands under the hood, correct?13:41
jaziz left13:44
Narrat joined13:44
PyDon Just one last question, i try to find what SmartHTTP actually means for my CGI calls. Does SmartHTTP mean full duplex connections?13:47
opal left13:47
rafasc PyDon: you can check the source: https://github.com/git/git/blob/master/http-backend.c#L49113:47
smart http just means you have a way to call upload-pack and be smart about what is transferred.13:49
dump http just tries to get the files directly. Asks for master, then looks at the commit, figures it also needs all of its parents, ask for them, rinse repeast.13:49
tiin57 left13:49
rafasc But that logic lives in the 'http remote helper'.13:51
man git-http-fetch13:51
gitinfo the git-http-fetch manpage is available at https://gitirc.eu/git-http-fetch.html13:51
oxymoron93 joined13:51
ShapeShifter499 left13:53
tiin57 joined13:53
ShapeShifter499 joined13:53
PyDon @rafasc thank you!13:54
shush joined13:54
geowiesnot left13:55
kadz left13:55
opal joined13:55
mr_shaman joined13:56
wondiws joined13:56
rafasc PyDon: if you are messing with this, see man git remote-ext as well.13:56
gitinfo PyDon: the git-remote-ext manpage is available at https://gitirc.eu/git-remote-ext.html13:56
wondiws how can I remove my incorrectly entered password from the cache (in Windows)?13:56
sunrunner20 joined13:57
ikke search for credential manager in start13:57
remove the entry from there13:57
shush left13:59
wondiws ikke, thanks13:59
aliss left14:03
oojacoboo left14:03
algun joined14:03
alguien left14:05
sudoforge joined14:06
strk joined14:07
oojacoboo joined14:07
strk git log --pretty=full # omits the commit date, why ?14:07
and, how to show _FULL_ info about a commit ?14:07
"fuller" (found)14:07
geowiesnot joined14:08
gordonfish joined14:10
rafasc strk: or 'raw'14:13
syr left14:16
syr joined14:16
ShapeShifter499 left14:17
royal_screwup21 left14:19
royal_screwup21 joined14:19
tiin57 left14:19
wondiws left14:21
g4570n joined14:21
maryo_s left14:21
tiin57 joined14:23
thiago joined14:24
strk it looks like 'fuller' has more info ?14:25
namely: AuthorDate, CommitDate14:25
ah, it's embedded, I see14:25
as a timestamp14:25
oxymoron93 left14:26
ikke yeah, fuller decodes the information, raw just shows you what's stored in the commit14:29
algun ikke, thanks for trying to explain git reset to me14:30
i think i'll have to read the git book section on it though (think it's called "demistifying reverts" or something)14:30
*reset14:31
ghost43 left14:31
lem-fr left14:31
ayaka joined14:31
ayaka how to recovery some deleted local commit14:32
I have create branch A, it is wrongly merged into branch B14:32
later I delete branch B14:32
ghost43 joined14:32
ayaka but there are some commits in branch A, and from the console history14:32
I can still see those some commits which was from branch A(git show)14:33
lem-fr joined14:35
rafasc strk: raw includes the tree hash, which is helpful sometimes. And depending on your log.date format, having the exact timestap is nice.14:35
ayaka: check git reflog14:36
ayaka I hope it can save me life14:38
rafasc, HEAD@{45} maybe the latest commit I need14:40
so I should git checkout -b foo HEAD@{45} ?14:41
rafasc yeah.14:41
algun left14:41
ayaka Thank you so much, it saves my life14:42
but if I have ever run gc, those record would gone?14:43
ikke it would keep it for 90 days14:44
rafasc I highly recommend not running gc ever.14:44
Unless you are trying to evict sensitive data from your disk.14:44
Trieste left14:46
hexnewbie joined14:46
planetcall|work joined14:47
ayaka of course I won't14:47
I just want to know whether I can try my luckily or I just give up14:47
troulouliou_div2 joined14:47
ikke git runs gc automatically14:49
tiin57 left14:49
Trieste joined14:49
rafasc From my experience, the dangerous ones are "git reset --hard", git checkout -f, and git checkout REF -- FILENAME.14:50
Because they discard things that are not tracked by git yet.14:50
mgedmin an accidental rm -r .git is also dangerous14:51
ikke git checkout .14:51
git clean -f14:51
strk left14:53
tiin57 joined14:53
Ignacy left14:55
rafasc forgot about being bit by git clean -fdx recently.14:56
gxt__gxt14:56
rafasc mgedmin: That and the 'delete and reclone' "solution".14:56
guideX joined14:57
rafasc Damn you xkcd 159714:57
guideX is there a easy care free way to use git? I feel like I must google through so many errors, and git is this huge time suck for me14:58
I keep running back to svn because, I don't want to spend so much time researching git errors14:58
for instance just trying to push up some code, I have to google my way through 6 different problems14:59
mackerman If you like svn, feel free to use it. I don't care what you use.14:59
Feel free to ask about specific git problems here.14:59
gxt If I'm committing a bunch of changes from my workdir as a series of commits, and after having committed some already I notice that some hunk I committed e.g. 3 commits ago should actually only be committed now, what's the quickest way to achieve that?15:00
guideX why do I see this all the time, https://www.datree.io/resources/git-error-fatal-not-a-git-repository15:00
jwest_ left15:00
guideX I have to like, delete all the git studff, and recreate it, and it's really annoying15:00
rafasc guideX: most of the time, people complaining about git being a 'time suck' fall into the trap of trying to using it without taking the time to learn it. If you don't learn the tool you are using, you'll always be fighting it.15:00
guideX idk I'm frustrated with it, I've been "learning" it since 201215:01
jas4711 left15:01
guideX I basically always am learning it, and never using it15:01
gxt I usually fix it by making a --fixup commit for the old commit after using checkout -p to restore the old state, but it feels ugly.15:01
rafasc guideX: the delete and reclone is an antipattern. And that's what is causing you to *not* learn how to use it.15:01
lem-fr left15:01
PyDon left15:02
irrgit joined15:02
rafasc because you quick bail, you never understand what caused the issue and how to avoid it.15:02
That would be like: just download the hello world example and try again. You'll never learn how to progress with the language.15:03
lem-fr joined15:04
rafasc guideX: that just means the directory you are at is not a git repository.15:04
guideX rafasc, typically it is, and then I delete the .git, and go create a new one and move it into place and it works for a while again15:05
sometimes I have to do this multiple times in a row until it works15:05
rafasc never delete .git15:05
guideX it's really obnoxious15:05
rafasc a directory without .git, is not a git repostory.15:05
stdedos joined15:06
guideX so there's that, also I keep seeing this "Can't update: no tracked branch No tracked branch configured for branch master. To make your branch track a remote branch call, for example, git branch --set-upstream master origin/master"15:06
sometimes also "don't know what to push because unknown branch origin/master"15:07
rafasc git told you about the problem, and told you how to fix it. If you don't at least try to understand what it is trying to say, well...15:07
justanotheruser left15:08
mobidrop left15:08
guideX I can go into the cli, but I'm using tortoise git, I have no idea what it's on about the branches, there are no branches15:08
Ignacy joined15:08
guideX it keeps complaining about branches, but I'm not at all using any15:08
ikke guideX: imho, tortoisegit is not the best way to interact with git if you don't already understand how git works15:09
guideX I kinda just want it to shut up and take my code, and it'll appear in the root/trunk etc15:09
ikke git is not svn, trying to treat it as svn is only going to be counter productive15:09
like you experience15:10
benyoo joined15:10
jwest joined15:10
rafasc guideX: Then I suggest you keep svn... If you just want to "upload my changes", the advantages of git won't probably apply to you.15:10
benyoo Hello, can I delete the complete history below the HEAD?15:11
mackerman Strange that tortisegit would make the commit to only one branch use case difficult.15:11
rafasc Also, it is almost mandatory to learn git via cli. Guis make so many abstractions, and hide so many aspects of the workflow, that it makes it really hard to actually learn the tool.15:12
guideX I'm also constantly getting stuck with obscure errors getting to github, it'll get to that halfway point to my local machine, then code changes get stuck there, and I have very obscure errors to work with, like "Git did not exit cleanly error #" and there's nothing more to work with15:12
thyat's just really super frustrating, and I'm never sure what to do next15:12
typically happens when I've been working on a project for a while, and somewhere in the middle of development, gets stuck on my local machine forever15:13
usually I delete the whole github repo, and create a new one, and recommit the newest code, or something drastic like that, but what do I do next time it happens?15:14
rafasc when you have some spare time, go to the !book, with a laptop on the side.15:14
gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable15:14
rafasc guideX: you will never now how to fix the next time it happens, if you don't understand what is happening and resort to delete and reclone.15:15
delete and reclone is *never* the answer.15:15
guideX when this happens, I basically have the "git did not exit cleanly" with generic error number, which is not helpful diagnosing the problem15:16
and my code changes won't go all the way to github, only to that first step on your local pc15:17
rafasc guideX: use the cli instead. It's not clear that those are git errors, they could be turtoise ones.. Now you are fighting two tools instead of one.15:18
Once you understand git, by all means, feel free to use a gui that makes some part of the process easier.15:18
tiin57 left15:19
mowcat joined15:20
rafasc benyoo: you could use: git checkout --orphan=new_master HEAD; git commit; then if you really want to proceed, git checkout -B master new_master;15:22
Guest20 left15:22
tolland left15:22
tiin57 joined15:22
robink left15:23
tolland joined15:23
guideX well anyways, thanks for the tips, guess I'll just keep bumbling around with it15:24
robink joined15:24
troulouliou_div2 left15:25
mightyjens left15:25
rafasc guideX: Don't bumble with it. Dedicate a small ammount of time trying to learn it. Make a dummy repo and experiment around. Resit the temptation to rm and reclone. !book !learn_git_branching and https://gitexercises.fracz.com/ are good resources to learn.15:26
gitinfo guideX: There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable15:26
guideX: A nice tutorial visualizing git branching: http://pcottle.github.io/learnGitBranching/15:26
rafasc benyoo: The easiest way would be to init a new repo and copy the files there. But I won't suggest that because it makes the point I was trying to make to guideX weaker. :^)15:27
guideX well I have repositories for my home project so I can learn git, but I'm not able to use git in the workplace or with other developers etc15:27
I have a few books, but I'll try those out15:28
rafasc guideX: forget about using it in a useful project. Try with a dummy repo first.15:28
it will be harder to solve a conflict in file with actual code, than fixing it in a file with a list of "fruits" one per line.15:29
or whatever you use as a dummy example.15:29
Sasazuka joined15:29
dedowsdi left15:30
justanotheruser joined15:37
zebrag joined15:37
troulouliou_div2 joined15:38
xcm left15:39
xcm joined15:40
Muimi joined15:41
chele left15:46
tiin57 left15:49
geowiesnot left15:49
ghost43 left15:53
tiin57 joined15:53
ghost43 joined15:53
shush joined15:55
shush left15:59
shush joined16:00
f4bi joined16:01
geowiesnot joined16:03
hbautista joined16:05
justanotheruser left16:08
CoolerX joined16:15
CoolerX how do you change remote?16:15
I want to change the remote to a different github repo16:15
Enphuego joined16:15
dqx_ left16:17
rewt man git remote16:18
gitinfo the git-remote manpage is available at https://gitirc.eu/git-remote.html16:18
rewt git remote set-url16:19
you can also add another remote, so you have 2 upstreams16:19
tiin57 left16:19
tiin57 joined16:22
benyoo I drive crazy! I added .idea to my .gitignore file, but why I always see some files in my stage from that directory?? :*(16:23
ikke !ignore_tracked16:24
gitinfo Git only applies ignore patterns to untracked files. You can't use ignore patterns to ignore changes to files that are already tracked by git. To remove files only from git, but keeping them on disk, use git rm --cached <file>. Still, see https://gist.github.com/1423106 for ways people have worked around the problem.16:24
CoolerX hint: Updates were rejected because the remote contains work that you do16:24
hint: not have locally. This is usually caused by another repository push16:24
hmm16:24
can I just force push?16:24
how do I force push?16:24
ikke git push --force16:24
justanotheruser joined16:24
CoolerX ok16:25
ikke Use at your own risc16:25
CoolerX how do I add stuff that shows up red to my .gitignore?16:25
benyoo ok thank you !16:25
CoolerX when I do git status some things show up red16:25
rewt edit .gitignore16:26
CoolerX I mean automatically16:26
git ignore16:26
ikke You have to be a bit more specific16:26
there are different things that show up red16:26
CoolerX there are some untracked files that show up red16:26
ikke, right I just want the untracked files to be added to .gitignore16:26
ikke CoolerX: does git ls-files -o return those files?16:27
git ls-files -o --exclude-standard16:27
shush left16:27
shush joined16:28
CoolerX ikke, yes16:28
git ls-files -o --exclude-standard >> .gitignore16:28
?16:28
ikke yes16:29
jrnieder left16:30
CoolerX thanks16:30
CoolerX left16:30
nikivi left16:30
nikivi joined16:31
shush left16:31
yashiJabraalElite16:32
theoceaniscool joined16:33
shush joined16:33
f4bi left16:40
NeoCron joined16:41
maryo joined16:41
Seveas joined16:42
dpflick left16:47
tiin57 left16:49
ghost43 left16:51
ghost43 joined16:51
tiin57 joined16:53
theoceaniscool left16:53
albel727 left16:57
orbyt_v7 joined16:59
mobidrop joined17:00
jwest left17:00
orbyt_ joined17:01
spluddementia17:04
mobidrop left17:04
dementiasplud17:06
JabraalEliteyashi17:07
jwest joined17:11
NeoCron left17:13
Muimi left17:13
Newami joined17:14
Newami left17:18
Guest20 joined17:19
tiin57 left17:19
tiin57 joined17:22
rfuentess left17:33
navidr joined17:35
dob1 left17:45
fitzgerald1337 left17:45
DolphinDream joined17:45
tiin57 left17:49
f4bi joined17:53
tiin57 joined17:53
crose left17:55
theoceaniscool joined17:55
orbyt_ left17:56
orbyt_v7 left17:56
gp5st_ left17:58
captain42 joined17:59
mr_shaman left18:05
jimi_ joined18:06
Junior left18:07
ohmyfromage left18:10
phcerdan left18:11
ohmyfromage joined18:12
gp5st_ joined18:13
goldmund joined18:14
tiin57 left18:19
xerox_ left18:22
xerox_ joined18:22
tiin57 joined18:22
sauvin left18:23
mns left18:25
mns joined18:25
g00s joined18:27
stdedos left18:32
planetcall|work left18:36
orbyt_ joined18:36
BPL joined18:38
aspiers joined18:38
vladoski joined18:39
vladoski Hi guys, I have a project where I need to "export" git to another project. I mean i need to have the history of the first project into the second one18:40
ikke you can add one as a remote to the other and fetch18:41
vladoski ah okay let me try then18:42
thanks18:42
orbyt_v7 joined18:42
ikke You still have to decide what you want to happen next18:43
they are still unrelated18:43
iffraff joined18:44
tiin57 left18:49
goldmund left18:50
lucasb joined18:51
tiin57 joined18:52
aspiers left18:57
theoceaniscool left19:00
cd left19:01
wootehfoot left19:01
jwest left19:02
vladoski ikke, okay it worked, thanks!19:02
imMute vladoski: like have one project become a subdirectory of the other (along with all the history of both) ?19:07
vladoski imMute, no i have a svelte project that I have to put into phonegap19:07
so I used a boilerplate found on github and put all the svelte files in that boilerplate19:07
the majority of the files went to a subdirectory, but not everything19:08
jimi_ left19:11
wootehfoot joined19:12
mekhami joined19:13
mekhami is there a way to commit without affecting the blame for the changed files/lines? i want to run a massive code reformat, and running filter-branch to rewrite the history takes many many many hours19:14
imMute mekhami: I don't think so since the blame is made by looking at the commit history for each line19:16
ikke You can add configuration to specify the path to a file that contains a list of hashes of commits to ignore for blame19:17
blame.ignoreRevsFile19:17
mekhami I just discovered that on an article, looking at that option now19:17
tiin57 left19:19
tiin57 joined19:23
vladoski okay i've done something bad, now i have 2 duplicate commits and a merge that I cannot understand from where's coming19:24
ikke !situation19:26
gitinfo Please post the url returned by `git log -n 20 --all --graph --format="%h %p %d %s" | curl -F text=@- https://upaste.de/` to give us an idea about what your situation is (increase the -n argument if your problem is more complex than 20 commits can explain)19:26
vladoski ikke, https://upaste.de/LTJ19:27
ikke did you do a rebase and then a git pull?19:27
Xiti left19:27
ikke most likely you did19:28
or git commit --amend19:28
vladoski i've done just a git pull from the "local" remote repo and then i've dove a git reset HEAD~ git commit -C because i've edited something, and yes then i've did a git pull19:31
I've tried to revert to the first phonegap commit but doesn't work. I've used this: git revert --no-commit <hash> HEAD19:32
surial okay, so you have the state of your repo as it was (after the commit 'created Profile route'. Then on that code base, you've done roughly the exact same thing, twice, with no or small differences, due to that rebase. Presumably, exactly one of those two commits is 'correct' and the other is 'incorrect'. reset your master to the correct one, push (with -f if you have to, though note that if you pushed this already and others have19:32
been writing code off of the 'wrong' one, this needs coordination between everybody with a copy of this repo) - and you're good to go.19:32
sysh left19:32
surial vladoski: revert, IIRC, creates a new commit that undoes another commit. you don't want that, you want reset.19:32
m0viefreak joined19:33
surial but first presumably git show b1135e3 and git show 2cddc2b, or possibly git diff b1135e3..2cddc2b to see which of the two similar commits is the 'right' one and which is the 'wrong' one (or if they both are partly right partly wrong, that's possible, perhaps).19:33
jimi_ joined19:38
dob1 joined19:39
Guest20 left19:43
cdown_ joined19:43
cdown left19:44
cdown_cdown19:44
vladoski surial, okay now everything works, thanks for the reset19:44
aw1_ joined19:46
aw1__ left19:48
surial vladoski: \O/ - let's hope you didn't delete any history :/ (if you're missing stuff, it'll be there for a while, but eventually git will remove it. "git reflog" prints all commits, 'dead end' or not still available, it'll be one of those, and you can update your dir to it with 'git checkout abcdef' where abcdef is the git commit name listed in reflog. So, if within the next week you find you're missing something, that's your out.19:48
After that, it'll just be gone.19:48
tiin57 left19:49
cgi joined19:49
aw1_ left19:49
aw1_ joined19:50
tiin57 joined19:52
crose joined19:52
xcm left19:54
xcm joined19:55
f4bi left19:59
Maxattax left20:04
nabil left20:06
Abbott left20:10
oatmealraisin left20:10
vladoski left20:11
Xiti joined20:11
tiin57 left20:19
tiin57 joined20:23
Hello71 left20:24
benyoo left20:25
Abbott joined20:30
Abbott left20:33
Aattas left20:36
Hello71 joined20:36
aw1_ left20:41
aw1_ joined20:42
robink left20:42
robink joined20:44
cr4y1 left20:45
Brainium left20:45
tiin57 left20:49
clime left20:50
aw1_ left20:51
tiin57 joined20:52
BPL left21:06
Trieste left21:12
snoyes joined21:13
Trieste joined21:14
snoyes I've cloned a repo from github. Now I've decided I want to fork the original repo. Is there a good way to tell my clone to point to my fork instead, or should I just clone my fork?21:14
ikke you can add your fork as a new remote, or update your current remote21:15
man git remtoe21:15
gitinfo the git manpage is available at https://gitirc.eu/git.html21:15
ikke either git remote add or git remote set-url21:15
snoyes thanks21:16
mowotter joined21:19
cliluw left21:19
tiin57 left21:19
mat001_ joined21:20
mowcat left21:22
jwest joined21:22
tiin57 joined21:23
mat001 left21:24
royal_screwup21 left21:26
gp5st_ left21:26
royal_screwup21 joined21:26
g4570n left21:28
g4570n joined21:29
clime joined21:39
quetz left21:42
oatmealraisin joined21:43
m0viefreak left21:47
troulouliou_div2 left21:49
tiin57 left21:49
snoyes left21:51
onizu left21:52
tiin57 joined21:53
ethernether joined21:53
navidr left21:54
Trieste left21:55
cliluw joined21:55
iffraff left21:57
orbyt_ left21:58
Trieste joined21:58
rewrited left21:59
GreateSMB1 joined21:59
bettencb left22:00
wnbeser joined22:02
GreateSMB1 hi everyone22:03
I need some help about topic - which console tool is the best as 'git mergetool'?22:03
gitinfo GreateSMB1: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.22:03
bettencb joined22:04
bettencb left22:04
bettencb joined22:05
shush left22:05
orbyt_v7 left22:05
orbyt_ joined22:08
rafasc !best22:11
gitinfo [!bestway] You want to know the best way to do X? If you can give us a proper definition of "best", we'll give you a proper way to do X ;)22:11
strobelight joined22:12
fission6 left22:12
bettencb left22:14
CodeSlingerPaul left22:18
sheddy_ joined22:19
jstein joined22:19
tiin57 left22:19
orbyt_v7 joined22:20
tiin57 joined22:23
strobelight left22:24
shush joined22:25
orbyt_ left22:25
Sasazuka left22:27
Sasazuka joined22:27
troulouliou_dev joined22:28
SpeakerToMeat left22:30
SpeakerToMeat joined22:31
xerox_ left22:32
phcerdan joined22:39
phcerdan left22:39
Phylock left22:39
zebrag left22:40
zebrag joined22:43
troulouliou_dev left22:44
calcul0n_ left22:48
tiin57 left22:49
inkbottle joined22:50
zebrag left22:50
tiin57 joined22:52
xelxebar_ left22:55
xelxebar joined22:57
DolphinDream left23:01
DolphinDream joined23:01
DolphinDream left23:01
omar_trisquel joined23:03
wnbeser left23:04
fairuz joined23:06
xerox_ joined23:08
gavlee left23:08
gavlee_ joined23:08
ghost43 left23:08
ghost43 joined23:09
fabs left23:12
sheddy_sheddy23:15
Intelo joined23:15
Intelo I had a changed file, I pulled from origin, the changes were got. How can I recover?23:15
xerox_ left23:18
tiin57 left23:19
sudomake joined23:20
nedbat Intelo: changes were got? what does that mean?23:22
Intelo uncommited23:22
file change23:22
actually i deleted old origin, added new, pulled23:22
I wonder why I didn't got any message saying (your changes will be overwritten)23:22
tiin57 joined23:23
justanotheruser left23:27
ethernether left23:27
gavlee_gavlee23:29
orbyt_ joined23:31
nedbat Intelo: i don;;t think it should overwrite your changes. we'd have to see exactly what you did23:31
Intelo nedbat, exactly what I did https://paste.ubuntu.com/p/R3nNpwzgRd/23:33
wgrant left23:34
Enphuego left23:35
dedowsdi joined23:35
wgrant joined23:35
sudomake left23:40
sudomake joined23:40
justanotheruser joined23:40
lucasb left23:40
mowotter left23:41
Abbott joined23:42
fission6 joined23:45
onmeac left23:47
geowiesnot left23:49
tiin57 left23:49
DogManJr joined23:50
DogManJr left23:51
Narrat left23:52
Rav3n joined23:52
tiin57 joined23:53
AtumT left23:56

Logs Search ←Prev date Next date→ Channels Documentation