IRCloggy #git 2019-09-24

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

xcm left00:01
squirrel left00:01
justanotheruser left00:01
FernandoBasso left00:02
xcm joined00:02
squirrel joined00:03
localhorse left00:05
nuala left00:07
daurnimator left00:08
wreed joined00:08
gordonfish left00:11
shabius left00:14
daurnimator joined00:15
blackmesa left00:15
shabius joined00:17
lucasb left00:17
justanotheruser joined00:22
igemnace left00:22
dartmouthed left00:24
xall_ left00:25
kotisky joined00:25
omnireq joined00:29
m0viefreak left00:30
kotisky left00:30
vdamewood joined00:34
budonyc left00:42
amcclure left00:43
is_null left00:44
amcclure joined00:49
jottr_ joined00:49
kotisky joined00:57
jottr_ left01:01
boombatower left01:01
thomasross left01:01
bitwinery left01:04
Sasazuka left01:05
bitwinery joined01:05
nabil__ joined01:09
stitched_unicorn joined01:11
jottr_ joined01:11
nabil_ left01:12
jackkall joined01:13
macaronus joined01:15
jottr_ left01:16
a0s510 joined01:25
xcm left01:30
xcm joined01:31
ferdna left01:33
jackkall left01:33
protektwar left01:34
protektwar joined01:36
Guest79846 left01:37
Guest79846 joined01:37
tgunr left01:44
learningc joined01:44
wreed left01:45
F0rTex left01:46
wreed joined01:46
cbreak left01:47
F0rTex joined01:47
cbreak joined01:48
a0s510 left01:59
fphilipe_ joined02:00
Envil left02:03
fphilipe_ left02:04
jguddas-tr2 joined02:04
atrigent joined02:05
jguddas-tr2 left02:08
Envil joined02:10
Cabanossi left02:10
wreed left02:13
computeiro joined02:14
lagothrix left02:15
lagothrix joined02:15
computeiro I deleted a file. `git status` -> deleted: article/s0144.pdf02:15
How to revert this delete?02:15
mns_ joined02:16
rewt git checkout -- article/s0144.pdf02:17
(with that -- before the file)02:17
Cabanossi joined02:18
computeiro ty rewt02:18
rewt np02:18
wreed joined02:18
mns left02:19
computeiro left02:21
bambanx left02:22
pR0Ps left02:27
a0s510 joined02:29
SkarmoutsosV joined02:31
pR0Ps joined02:32
a0s510 left02:40
edwardly left02:45
b1tninja joined02:47
b1tninja Is there a way to find the commit that closest resembles my working directory02:47
Number of matching files would be good enough metric, don't need diff distance of similar files02:49
edwardly joined02:50
rople joined02:52
b1tninja Basically trying to match a fork initial commit to it's parent02:56
G left03:01
nic-hartley left03:03
Guest79846 left03:04
Guest79846 joined03:05
crose left03:05
glosoli joined03:09
rwp b1tninja, I had to do something similar in an svn repository not that long ago. I found a file that had comment changes and used it to bracket the versions from earliest to latest. That narrowed it down.03:11
b1tninja I know it's near Android kernel 3.10.62 but so many commits03:11
glosoli left03:17
a0s510 joined03:17
jnewt left03:20
SJr If I look at a git diff between two branches I see a perfect PR, however if I try and merge or rebase I get a ton of conflicts I don't care about. It seems like I can just make a new branch off master and apply the diff, however it seems there shoulld be a way of doing this more naturally.03:27
atrigent left03:29
a0s510 left03:31
nic-hartley joined03:32
igemnace joined03:33
howaboutsynergy joined03:34
howaboutsynergy I'm trying to get the diff of a specific file which is inside a submodule. How could I do that without chdir-ing to the submodule dir first? ie. this works: `cd third_party/perfetto/ && git diff gn/BUILD.gn` but this doesn't: `git --git-dir=third_party/perfetto/.git diff --submodule=diff third_party/perfetto/gn/BUILD.gn` especially without the --git-dir03:34
igemnace left03:35
yonder left03:36
pie__ left03:37
g00s joined03:41
yonder joined03:41
b1tninja Try without specifying submodule03:43
You also have eq diff03:43
Don't think that's what you meant03:43
howaboutsynergy eq diff?03:44
no effect(ie. no diff) with just `git diff third_party/perfetto/gn/BUILD.gn`03:44
b1tninja With git dir03:44
Or use -C03:45
howaboutsynergy no effect like: $ git --git-dir=third_party/perfetto/.git diff -C third_party/perfetto/gn/BUILD.gn03:46
though, even if it worked, would the diff show like:03:47
--- a/gn/BUILD.gn03:47
or:03:47
--- a/third_party/perfetto/gn/BUILD.gn03:47
the latter I'd prefer, but i don't see how it would do that03:48
I guess I'm stuck having to sed the diff, after I get the former output by first chdir-ing to where the BUILD.gn file is03:48
though it's kinda odd that --git-dir= doesn't seem to have effect, oh waitttttt it's the path03:51
with git-dir, the path to the file isn't third_party/perfetto/ anymore03:51
ok this doesn't work: $ git --git-dir=third_party/perfetto/.git diff gn/BUILD.gn03:51
fatal: ambiguous argument 'gn/BUILD.gn': unknown revision or path not in the working tree.03:52
this sort of works but it compares it to /dev/null : $ git --git-dir=third_party/perfetto/.git diff -- gn/BUILD.gn03:52
e^1 joined03:53
howaboutsynergy This $ git --git-dir=third_party/perfetto/.git diff .clang-format03:55
Actually compares third_party/perfetto/.clang-format with ./.clang-format oh boy03:55
motoko-chan joined03:55
libertyprime left03:56
howaboutsynergy I guess I'd need a --git-dir arg for the file to compare with too03:56
SCHAPiE left03:57
SCHAPiE joined03:59
pie_ joined04:01
lankanmon left04:02
gavlee joined04:03
lankanmon joined04:06
nic-hartley left04:06
publio left04:08
bambanx joined04:10
SkarmoutsosV left04:11
igemnace joined04:13
snappy joined04:14
e^1 is it a good practise to source gitignore and gitattributes files from gitconfig ?04:14
snappy how do i import a git repository and history to another git repo? i have a separate origin setup for the repo i want to merge in, but i don't know what to do to bring it in04:14
e^1 I am version controling my git files, current structure is, gitconfig ( file ), git-conf (dir) where i have kept all the other necesary git* related files04:15
snappy i'm thinking maybe (1) create branch with the new repo, put it in the right directory, then try to rebase it on the mainline repo?04:16
donofrio left04:16
howaboutsynergy left04:17
dartmouthed joined04:21
Cabanossi left04:25
shored left04:26
shored joined04:26
igemnace left04:29
igemnace joined04:30
neunon left04:30
wreed left04:32
Cabanossi joined04:38
tryte left04:45
tryte joined04:45
a0s510 joined04:47
dustinm left04:53
hojang joined04:54
dustinm joined04:56
g00s left04:57
igemnace left04:58
dustinm` joined04:59
SmashingX left05:00
dustinm left05:00
igemnace joined05:01
dijitol joined05:01
pks_ joined05:02
yokisuci joined05:03
comptroller left05:04
pks left05:04
pks_pks05:04
glosoli joined05:07
hojang left05:10
Wetmelon left05:13
Inline left05:14
vdamewood left05:15
comptroller joined05:16
pie_ left05:19
igemnace left05:19
SkarmoutsosV joined05:22
igemnace joined05:25
jackkall joined05:28
yonder left05:29
comptroller left05:31
SkarmoutsosV left05:31
dijitol left05:31
a0s510 left05:32
blackmesa joined05:34
steven left05:35
steven joined05:38
libertyprime joined05:38
omnireq_ joined05:41
omnireq left05:43
igemnace left05:44
comptroller joined05:49
roadie left05:50
n3wborn joined05:53
feriman joined05:56
fphilipe_ joined06:00
comptroller left06:01
comptroller joined06:03
fphilipe_ left06:04
g00s joined06:07
sQVe joined06:08
rfuentess joined06:08
roadie joined06:10
TomTom joined06:11
feep[work] joined06:13
feep[work] yo06:13
does anyone have a script to show the disk use of each commit in a git history? by this I mean the amount of space used by objects first referenced in the commit06:14
I have a repo that has a big file *somewhere* in its history that I want to rebase out, but I don't know where.06:14
markzen_markzen06:19
feep[work] updated question: I just found rebase --exec, is there an env var that contains the id of the commit?06:19
yokisuci left06:20
j416 feep[work]: you might want to look into filter-branch instead06:20
feep[work] nm just found $GIT_COMMIT06:20
j416: yeah that's what I'll do once I've found what file it is06:20
j416 yeah you said rebase, that's why I suggested it.06:20
feep[work] hm I suppose I can just not make any changes in filter-branch06:21
j416 you could probably script something around something like git ls-tree -l <commit> | sort -k 406:22
feep[work] hm, if I could get a list of all commits06:22
j416 man git-rev-list06:22
gitinfo the git-rev-list manpage is available at https://gitirc.eu/git-rev-list.html06:22
bitwinery left06:22
Noti joined06:22
feep[work] thanks06:23
j416 a start: git rev-list --all | while read commit; do git ls-tree -rl $commit | sort -k 4; sleep 1; done06:24
clime joined06:24
cd left06:26
feep[work] found the commit06:26
j416 o/06:26
blackmesa left06:27
thefatma joined06:27
feep[work] j416: spoiler: 865357824 Sep 24 08:26 core06:27
think that might be contributing, lol06:28
j416 I don't have that commit so I don't know what you mean, sorry06:31
feep[work] it's a corefile06:31
j416 oh it's the size06:31
feep[work] somebody committed a corefile06:31
>.<06:31
j416 haha.06:31
feep[work] tbf it's mostly sparse.. still. why.06:31
cdown joined06:34
motoko-chan left06:35
comptroller left06:36
clime left06:37
mojisun_ left06:45
mojisun_ joined06:46
gloomy joined06:51
gloomy left06:52
nabil__nabil06:52
jackkall left06:53
comptroller joined06:53
TomyWork joined06:54
chele joined06:56
gloomy joined06:56
lankanmon left06:56
gloomy left06:56
lankanmon joined06:59
yokisuci joined07:01
SteffanW joined07:02
Noti left07:02
feep[work] hm. new question: I have a commit in my repo, and I cannot for the life of me get rid of it no matter what arcane flags I pass to git gc. it's not in the log of master, and there's no other branches07:03
how do I find what gc root keeps it alive?07:03
(it's not in git log --reflog)07:04
(or in git fsck)07:05
Mattiaslndstrm joined07:06
cbreak feep[work]: git clone07:06
and throw away the original :)07:07
oxymoron93 joined07:07
feep[work] ... huh07:07
cbreak (be sure to fetch all tags / branches you want to keep, for example using --mirror ( read the fine print ))07:07
feep[work] that actually worked.07:07
repo size before: 66M07:08
repo size after: 1.6M lol07:08
cbreak for a local clone, you might have to do a file:// url clone in some situations07:08
yokisuci left07:09
Heirlung- left07:10
thiago left07:11
jguddas-tr2 joined07:11
bambanx left07:12
arunkumar413 joined07:14
yokisuci joined07:15
feep[work] cbreak: thanks for that hack :D07:18
it's a lot easier than messing with gc07:18
cbreak you'll be sure to lose everything local though07:19
feep[work] meh07:19
:D07:19
cbreak including local config, local ignores, hooks, ...07:19
feep[work] thanks for the warning, but I am trying to clean up this repo so..07:20
alright, now I'm finally at a point where the biggest blob is actual source code07:20
Luyin left07:20
feep[work] also the repo is ~20 times smaller :D07:20
emanuelvirca joined07:21
mobidrop joined07:21
cdown left07:23
blackmesa joined07:23
abraxxas joined07:23
kotisky left07:24
abraxxas left07:24
abraxxas joined07:24
gloomy joined07:25
cdown joined07:26
mobidrop left07:27
kent\n left07:27
nerosnm joined07:27
mobidrop joined07:27
emanuelvirca Hi everybody, I have a situation I would like to get some directions. I have the main master branch and i came upon the situation that can be seen in this picture: https://imgur.com/MX68UOP . I do not know exactly how it happend and I am interested in moving commits from red master. Both of the branches are master, trancking the remote master. The07:27
changes have been pushed to remote.07:28
I would appreciate any direction or starting point for this. Thanks a lot ;)07:28
kent\n joined07:29
rfuentess emanuelvirca: that history happened after a `git pull origin master` ?07:30
fphilipe_ joined07:31
pie_ joined07:31
nerosnm left07:31
emanuelvirca I am not pretty sure about this. It was one of my colleague that initiated this.07:32
I have updated the picture07:32
emanuelvirca74 joined07:35
emanuelvirca74 left07:36
is_null joined07:36
emanuelvirca left07:37
tufteddeer joined07:38
feep[work] left07:41
emanuelvirca joined07:46
emanuelvirca left07:48
emanuelvirca joined07:49
nabil left07:50
emanuelvirca sorry guys, my connection went off07:50
yokisuci left07:52
rfuentess emanuelvirca: the thing is that is master. Normally the suggestion is let it go as rewriting master is unwise07:52
(or complex if there are many contributors)07:52
cdown left07:52
rfuentess !rewrite history07:53
gitinfo Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum07:53
blackmesa left07:57
mobidrop hey I have a question about the git!07:57
I did a git pull and noticed a 26.76 MiB, now I want to know which clown decided to put a file that big in the git!07:57
bookworm git log / git show07:58
gxt joined07:58
nabil joined07:59
mobidrop the file could be on any branch though07:59
ah whatever I've forgiven them08:00
jottr_ joined08:00
brethil left08:01
jguddas-tr2 left08:06
c0c0 joined08:11
pengpengxp joined08:14
brethil joined08:15
Noti joined08:17
SteffanW left08:17
pengpengxp left08:18
jguddas-tr2 joined08:21
nabil_ joined08:24
heftig did git 2.23 stop applying diff.interHunkContext to format-patch output?08:25
jguddas-tr2 left08:26
Makaveli7 joined08:26
nabil left08:27
g00s left08:27
hojang joined08:37
n3wborn left08:39
tsdh joined08:41
geek1011 left08:42
mrCyborg left08:42
Kronuz left08:42
uebera|| left08:43
geek1011 joined08:43
mrCyborg joined08:43
uebera|| joined08:43
brethil_ joined08:44
topdownjimmy left08:44
Envil left08:44
brethil left08:44
F0rTex left08:44
squirrel left08:44
cjohnson left08:44
irrgit left08:44
jstimm left08:44
eb0t_ left08:44
wgrant left08:45
topdownjimmy joined08:45
cjohnson joined08:45
clime joined08:45
zulutango left08:45
irrgit joined08:45
squirrel joined08:45
zulutango joined08:45
Envil joined08:45
laerte joined08:46
F0rTex joined08:46
teward left08:46
wgrant joined08:46
eb0t_ joined08:47
emanuelvirca left08:48
Kronuz joined08:48
hojang left08:49
teward joined08:51
jguddas-tr2 joined08:56
stitched_unicorn left08:57
mimajof joined08:58
tufteddeer left08:59
nerosnm joined09:01
javashin joined09:02
tufteddeer joined09:03
jottr_ left09:05
gloomy left09:05
enoq joined09:05
Joel left09:05
e^1 left09:06
Joel joined09:07
cbreak left09:08
cbreak joined09:09
hojang joined09:09
nabil__ joined09:10
glosoli left09:11
jstimm joined09:11
rossome joined09:12
nabil_ left09:13
mSSM left09:15
stitched_unicorn joined09:17
zamba left09:20
gschwind joined09:21
T_UNIX joined09:22
gschwind Hello, I did git submodule add, then git reset HEAD, how can I recover my submodule, I still having .gitmodules, and .git/config look to hava submodule initialized, but git submodule does not list my submodule09:23
hojang left09:25
yokisuci joined09:25
Makaveli7 left09:26
figuinhas joined09:27
figuinhas left09:28
zamba joined09:28
pi- gschwind: I'm a (perennial) git-noob, but don't you need something like `git submodule update --init --recursive`? (https://stackoverflow.com/questions/3796927/how-to-git-clone-including-submodules)09:28
Makaveli7 joined09:28
figuinhas joined09:28
figuinhas left09:28
figuinhas joined09:29
gschwind pi-, this has no effect I do not know why09:31
pi- oh, maybe resetting HEAD removed the submodule-add, because you never pushed the submodule-add upstream09:32
catsup left09:33
gschwind I do not know what happened but for sure I did not commited submodule add, it was the intend :D09:33
catsup joined09:34
gschwind but I still having config file set up, thus I hope I can re-add my submodules easily09:34
other wise I have to do it manualy, but I have about ~50 sub module :D09:35
pi- ouf09:35
yokisuci left09:37
Cabanossi left09:37
cfoch joined09:41
Cabanossi joined09:42
hojang joined09:42
gschwind if that happen that I have no easy way to readd them, I will write a script that read .gitmodules ;)09:43
that will be faster than re-adding them manually09:44
yokisuci joined09:44
pSouper joined09:44
pSouper hey all o/09:44
stitched_unicorn left09:45
pSouper not entirly understanding git I've got myself in a pickle... I have 2 branches: master & develop. my develop branch has 26ahead and 15behind and i'd like to just replace all of devlop with master to make then the same again. (I've not done anything i need to keep)09:46
any thoughts/help please?09:46
vlt pSouper: In other words you want to delete develop and re-create it on master?09:47
pSouper yup. recrease it with files from master09:47
vlt pSouper: I don't understand "with files from master".09:48
pSouper i tihnk it;s the same as you said but i would still like to branches (master & develop). it's just they should be the same (both the same as master)09:49
but thanks for checking with me as i know getting git wrong can be very dagerous thing09:49
fstd_ joined09:50
vlt pSouper: A bit shorter than what I suggested earlier could be: `git reset --hard master`09:50
oxymoron93 if you are currently on `develop` ^09:51
pSouper which branch should i be on before i run that?09:52
oxymoron93 on develop09:52
pSouper ah, i get it09:52
thanks. doin now09:52
2mins09:52
blackmesa joined09:53
oxymoron93 branches are just pointers, if you want to develop points to same revision as master does, you can recreate it there.09:54
fstd left09:54
fstd_fstd09:54
hojang left09:56
vlt That's what I suggested first to make it more clear what actually happens.09:58
pSouper: ^09:58
gschwind if you really want lost your develop branch you can : git checkout -f -b develop master09:58
oxymoron93 There are many ways to accomplish this.09:58
gschwind this command also switch to develop branch09:58
javashin left09:59
glosoli joined09:59
pSouper thanks guys. I;ve notice there are so many way to achieve similar/same things which only adds to my confusion :D09:59
blackmesa left09:59
pSouper I've just tried: git reset --hard master10:00
it's still saying I have 25ahed and 15behind10:01
@gschanuel59 "git checkout -f -b develop master" errors with a fatal: A branch named 'develop' already exists. I guess i need to delete this branch first for it to work?10:02
oxymoron93 `git checkout -B develop master` would work10:03
agowa338 joined10:04
nerosnm left10:04
pSouper on a related not. it would be the same as deleteing the project then cloning it from git right?10:04
on a related note*10:04
oxymoron93 again this is the problem? Message you have has to do with remote counterpart.10:04
practically yes pSouper10:05
pSouper coolio.10:05
oxymoron93 you should grab a !book :)10:05
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 !parable10:05
pSouper i definately will grab a book. I'm quite a fan of o'reilly book.10:06
gloomy joined10:10
fphilipe_ left10:11
kerframil joined10:12
steven is there a ref pointing to the commit of which I've branched off?10:12
florekm joined10:14
sinhue left10:15
liberiga joined10:17
localhorse joined10:17
AtumT joined10:19
oxymoron93 steven you can probably find it in `git reflog <branch>`10:19
Hello71 left10:19
oxymoron93 but yeah, I have nothing better than searching. Maybe `git merge-base --fork-point ...`10:20
Makaveli7 left10:21
oxymoron93 you can probably formulate your question more widely as to what you want. There might be other ways for you to do it.10:21
amerigo joined10:22
abraxxas left10:23
yokisuci left10:25
Hello71 joined10:25
kjartan_Kjartan10:26
steven I honestly don't know how to formulate it more "widely" :D10:31
I want the commit from which I did "git checkout -b new-branch"10:32
igemnace joined10:32
cdunklau steven: there's no ref, no10:32
pandem you can use git merge-base10:32
cdown joined10:33
cdunklau steven: a git branch is just a (moveable) reference to a particular commit, nothing else10:33
pandem https://git-scm.com/docs/git-merge-base#_discussion10:34
cdunklau so the branch doesn't know where it was forked from... but the commit's *history* can be used to find that out10:34
gschwind I did a python script that re-add my submodule from .gitmodule10:34
cdunklau it's just not an explicit thing10:35
steven I konw what it is cdunklau .. thanks pandem that's what I was looking for10:35
cdunklau steven: k, sorry, that's just a really common misconception :)10:36
steven I get it, always imply the person asking is a complete idiot10:38
its freenode, chances are quite high for it to be true ;)10:38
yokisuci joined10:42
blackmesa joined10:46
SteffanW joined10:49
Noti left10:50
igemnace left10:52
learningc left10:53
escherial left11:01
blackmesa left11:02
blackmesa joined11:03
emsjessec joined11:05
mns_mns11:06
rople left11:06
Stoot97 joined11:12
Raging_Hog joined11:12
Stoot left11:13
b1tninja left11:17
xcm left11:20
xcm joined11:20
gloomy left11:22
zxcat joined11:26
zxcat hi all, I wish to kow if is possible and howto, include external directories / files ( that are not in the same dir of .git )11:26
osse zxcat: no it's not possible11:28
yokisuci left11:28
osse zxcat: if you need that maybe you can keep the actual files in git and then have symlinks where the files are supposed to be11:28
zxcat hmm.. so for my needs, maybe is better if I simple exclude what I don't need and git will syncronize everything else.11:30
bremner you can also use something like !vcsh11:30
gitinfo https://github.com/RichiH/vcsh - Version Control System for $HOME - multiple Git repositories in $HOME -- abusing fake bare Git repositories for fun and profit11:30
zxcat the propose in fact is to update all files that had some change of a linux system. Is a "bad" idea to setup a git repository at / and exclude what I don't wish to "monitorize" ?11:32
nerosnm joined11:32
computer2000 joined11:32
gschwind zxcat, can you describe your use case ?11:37
kotisky joined11:37
gschwind zxcat, if you git init / by default all file are excluded11:37
you need to add then manually11:37
rodorgas joined11:38
ASDX left11:39
rodorgas Hi! Where can I find the changelog of the new Git version? It's hard to google it because "git changelog" doesn't return what I want :p11:40
c0c0 left11:41
yokisuci joined11:41
zxcat gschwind: I guess excluding directories would be simpler. Therefor I can simply 'git add . ' and it will work fine as well. Ok cool! Thnk11:41
rodorgas Found it! https://github.com/git/git/blob/master/Documentation/RelNotes/2.23.0.txt11:42
random_yanek left11:44
cdown left11:44
yokisuci left11:47
yokisuci joined11:47
random_yanek joined11:51
jottr_ joined11:51
fphilipe_ joined11:53
azwieg103 joined11:58
macaronus left11:59
cdunklau steven: i know you're joking, but it's really astonishing how long one can use git without knowing relatively basic things about it11:59
like, i didn't realize that bit about a branch just being a commit for, i dunno, five years?12:00
vlt cdunklau: Coming from another VCS?12:05
cdunklau vlt: nope!12:07
fphilipe_ left12:07
cdunklau coming from "i wish i could go back in time before i screwed this all up"12:08
fphilipe_ joined12:09
cfoch left12:10
blackmesa left12:11
blackmesa joined12:13
azwieg103 left12:16
Stoot97Stoot12:16
mowcat joined12:17
cdown joined12:22
CodeSlingerPaul joined12:22
yokisuci left12:24
vlt :D12:25
boombatower joined12:26
cfxd joined12:30
amerigo left12:31
nerosnm left12:33
Ranhir joined12:33
igemnace joined12:34
nurdie joined12:35
Dave-Ins joined12:39
cdown left12:41
jottr_ left12:41
Dave-Ins left12:42
gxt left12:43
Atlenohen joined12:46
rodorgas left12:48
rodorgas joined12:48
jottr_ joined12:49
lucasb joined12:49
glosoli left12:51
gschwind cdunklau, branch also avoid gd to drop commit dependancy :D12:51
gc*12:51
rodorgas left12:53
fphilipe_ left13:00
javashin joined13:00
learningc joined13:01
tmager joined13:01
blackmesa left13:03
Heirlung joined13:03
pSouper left13:03
xcm left13:04
xcm joined13:05
iNs left13:05
iNs joined13:06
rodorgas joined13:08
ExeciN joined13:08
sQVe left13:09
sQVe joined13:09
sQVe left13:09
comptroller left13:10
Mattiaslndstrm left13:10
sQVe joined13:10
jottr_ left13:10
nerosnm joined13:11
hojang joined13:11
ExeciN left13:11
henrebotha[m] What's the intended way to obtain the shell completion scripts from the contrib dir in the Git source?13:12
ExeciN joined13:12
henrebotha[m] Like… I assume installing Git through e.g. apt doesn't also save those scripts somewhere13:12
bremner dpkg -L git | grep complet13:13
Hello71 apt search git complet13:14
nerosnm left13:15
nerosnm joined13:15
henrebotha[m] Thanks13:16
I pretend to know computers but secretly I'm just fooling everyone13:16
yokisuci joined13:16
xcm left13:16
xcm joined13:17
anddam while doing some test on rebasing I got https://gist.github.com/anddam/6fb02fd58a53168f36a53b18f93606ee13:17
I expected to have a linear history with feature-Y coming after feature-X, should I have "carried" master at the same commit of feature-X ?13:18
this was git checkout feature-Y; git rebase master13:18
SuperL4g joined13:19
comptroller joined13:19
SuperLag left13:21
fphilipe_ joined13:22
henrebotha[m] Weird, dpkg says there's only Bash completions? Nothing for Zsh?13:22
howdoi joined13:22
Mattiaslndstrm joined13:24
bremner iirc, git completions for zsh ship with zsh13:24
cdunklau anddam: that looks kinda strange, could you do `git log --graph --oneline --decorate` ?13:25
bremner dpkg -L zsh-common| grep git13:25
henrebotha[m] Yeah that's true, but I want to use the script from git.git13:27
steven__ left13:29
steven__ joined13:29
z8z joined13:29
nurdie left13:31
imigunov joined13:32
xcm left13:34
xcm joined13:34
scrote joined13:35
scrote hello13:35
Cabanossi left13:37
scrote suppose master updates by several commits while in the middle of your branch, and then decide to merge that branch into master, will it work (other than conflicts)?13:38
apetresc left13:42
osse scrote: yes13:42
malina joined13:42
scrote do I have to rebase ?13:43
xcm left13:43
osse no13:44
xcm joined13:44
crose joined13:44
apetresc joined13:45
arunkumar413 left13:46
malina left13:46
br4z joined13:48
learningc left13:49
scrote if my branch consists of more than 1 commit, must I squash them all into 1 commit before merging into master in order for all changes go in to master13:50
tgunr joined13:50
scrote no, if you merge a branch, you'll merge all of its commits.13:50
Cabanossi joined13:51
dgw left13:52
czart joined13:52
oxymoron93 left13:53
nic-hartley joined13:53
xcm left13:53
imigunov left13:53
xcm joined13:54
Dougie187 joined13:54
f3r70rr35f joined13:54
onmeac joined13:58
malmalmal joined14:00
gschwind scrote, your are right14:01
anddam cdunklau: yep, but I progressed further already squashing feature-Y to a single commit with a rebase --interactive14:03
cdunklau: do you still want the git log output?14:03
onmeac left14:04
br4z left14:04
hojang left14:05
mobidrop left14:05
cdleonard joined14:06
mobidrop joined14:06
anddam cdunklau: update the gist14:07
ericfreese joined14:08
thefatma left14:09
sQVe left14:12
nerosnm left14:14
thefatma joined14:16
jottr_ joined14:16
SuperL4gSuperLag14:17
cdleonard left14:20
Mattiaslndstrm left14:23
omnireq_ left14:25
greggerz joined14:25
SkarmoutsosV joined14:26
gschwind left14:26
zumba_addict joined14:27
zumba_addict Hi all. Is it possible to retrieve info about the committer on a remote non-master branch?14:27
clime left14:28
zumba_addict like seeing commits on the remote branch14:28
magic_ninja_work joined14:28
gloomy joined14:28
planetcall|work joined14:29
Newami joined14:29
ExeciN left14:29
zumba_addict or list committer's name of remote branches14:29
cdunklau anddam: oooh i see, it's because of --all14:29
anddam: you rebased feature-Y, but you didn't touch feature-X14:31
anddam well I did, feature-X itself was rebased onto master14:31
both feature-X and feature-Y were branched at first commit14:31
cdunklau anddam: right?14:32
anddam: you didn't merge feature-X14:32
donofrio joined14:32
anddam I should have kept a list of the commands I ran, basically "init, first commit, branch X, branch Y, commit on master, commit on X, commit on Y, rebase X on master, rebase Y on master"14:33
I have not merged anything yet14:33
cdunklau anddam: run `history` in your terminal?14:34
anddam now I should merge if feature X is complete, right?14:34
cdunklau: I am not on bash14:34
cdunklau :/14:34
gloomy left14:34
royal_screwup21 joined14:34
anddam once I complete X I checkout master, and merge feature-X. Then I am not sure if I should delete branch feature-X or not14:34
nurdie joined14:36
cdunklau anddam: erm, did you branch Y off of X? or off of master?14:36
moldy anddam: git branch --merged will will show you the branches that are merged into your current branch14:36
henrebotha[m] zumba_addict: you can use `git fetch` to retrieve information about remote branches14:36
cdunklau anddam: because it looks like you branched Y from master14:37
usbguy1 joined14:38
ericfreese left14:38
ericfreese joined14:39
ericfreese left14:40
imigunov joined14:40
ericfreese joined14:40
anddam cdunklau: Y off of master14:41
cdunklau okay, and you didn't merge or rebase feature-X14:41
ericfreese left14:41
anddam I did rebase feature-X14:41
I was exactly doing this as rebasing exercise14:42
ericfreese joined14:42
anddam this is a gimmick repo14:42
cdunklau apparently not, otherwise 6c7260b wouldn't show up as a fork there14:42
nuala joined14:43
anddam why not? I branched X off of 73a1221 then rebased on ed2968e squashing a couple commits into what became 6c7260b14:43
when I rebased master stayed at ed2968e and feature-X at 6c7260b14:44
that part seems quite linear to me, I mean it's what I expected14:44
nic-hartley left14:44
malmalmal left14:44
cdunklau anddam: okay, well, that doesn't agree with what's showing up14:44
anddam should I try and reproduce?14:45
cdunklau anddam: master is currently at ed2968e, feature-Y is at 0c5ed7a (parent being ed2968e), and feature-X is at 6c7260b (also parent being ed2968e)14:45
oh okay, i think i see what your confused about14:46
gloomy joined14:46
cdunklau so you separately rebased X and Y against master14:46
but you haven't merged anything. all three branches have a linear history, but X and Y diverge from one another14:47
so if you want master to have that linear history, you need to merge one of the branches into master, then rebase the other branch again, and then merge that into master14:48
gloomy left14:50
royal_screwup21 left14:50
anddam yes, I think I get that, I am not confused (atm)14:50
cdunklau maybe i was confused :)14:50
anddam with the rebase I only incorporated additional changes into master into both features that at this moment are still separate feature branches14:50
once I complete each of them I will merge into master14:51
what I do not know is if I should then delete the merged branch or not14:51
cdunklau you don't have a merged branch14:51
or do you mean after you do your merging14:51
anddam yes, that was an hypothetical sentence14:52
cdunklau ok14:52
i mean, you can, if you want14:52
anddam but should I?14:52
cdunklau i usually delete those14:52
anddam ok, the "short lived" or "light" branch approach of git14:53
(I'm used to mercurial)14:53
cdunklau isn't it the same kind of thing in hg?14:53
fphilipe_ left14:53
anddam cdunklau: I think I am all set for now14:53
different topic, given the last log in second-test.txt in my gist, is there a way to tell git "set master tip to e3ce91f"?14:55
lmariscal8 left14:55
mimajof left14:55
lmariscal joined14:55
cdunklau anddam: sure, merge feature-X14:56
it'll be a FF merge14:56
(so there shouldn't be a merge commit)14:56
nika_ joined14:57
cdunklau anddam: and to be sure about that, --ff-only14:57
malmalmal joined14:58
justanotheruser left14:58
anddam cdunklau: the 'merge-commit' would be the newly created one for the merge, that is absent in a fast-forward operation, right?14:59
rodorgas left15:00
anddam this is somehow starting to make sense15:00
cdunklau anddam: right.15:00
im0nde1 left15:00
cdunklau anddam: say you merged feature-X as it is now, you'd get an FF merge15:01
so master would just be updated to point at the tip of feature-X, no commit15:01
im0nde_ joined15:01
cdunklau anddam: but then you merged feature-Y, without rebasing. that wouldn't be a FF merge since feature-X's commit isn't in feature-Y15:01
so then you'd get a merge commit15:02
(and it would show up in the graph)15:02
shored left15:02
shored joined15:02
Atlenohen left15:04
anddam unless I merge -ff-only then rebase Y on master (that now has X in it)15:04
SkarmoutsosV left15:04
anddam for the --ff-only should I be on master and merge feature-X or be on feature-X and merge master?15:05
oatmealraisin joined15:05
SteffanW left15:06
omnireq joined15:06
thiago joined15:07
yokisuci left15:07
yokisuci joined15:07
anddam TIAS, I had to be on master and merge the feature branch15:08
cdunklau: and apropos that double fast-forward without rebasing Y on master I get "fatal: Not possible to fast-forward, aborting"15:09
this is brilliant, makes even more sense15:09
cfxd left15:10
malina joined15:10
achen_ joined15:14
anddam cdunklau: thanks so much15:14
usbguy1 left15:14
cdunklau anddam: \o/ np15:14
achen_ left15:15
Celmor[m] is there a way to copy a file I want to adapt for a new "component" and keep it's git history so I can differentiate between edited changes and copied stuff via git blame (or IDE highlights)?15:15
thefatma left15:16
gloomy joined15:16
enoq left15:17
moldy Celmor[m]: afaik, no15:18
Celmor[m]: in such cases i make a copy, commit it with an appropriate commit message, than start editing from there15:18
anddam cdunklau: last question last, apropos the figure at "Integrating an Approved Feature" https://www.atlassian.com/git/tutorials/merging-vs-rebasing15:18
Dougie187 Celmor[m]: you could always filter-branch the file, and then merge the filtered branch into the other branch you want it in.15:19
If that makes any sense.15:19
anddam cdunklau: the initial state has the head of feature with two parents, one from master. That would mean a merge of master in feature has happened already, right?15:20
Celmor[m] moldy: but the copy in the new place will cause errors if left unchanged15:20
moldy Celmor[m]: what kind of errors?15:20
usbguy1 joined15:20
anddam I am clear about the two following scenarios but that image seems a bit off, I would have guessed the two branch would have un-connected heads15:20
cdown joined15:20
Celmor[m] paths/package/module specifications, it's just not intended to be "there"15:21
Dougie187 Celmor[m]: I actually think (after re-reading your question) that I don't understand fully what you're looking for. So hopefully moldy knows and can help you instead. :P15:21
moldy Celmor[m]: who cares? :)15:21
Celmor[m]: not each individual commit needs to be a working state15:21
mobidrop left15:22
zumba_addict left15:22
computer2000 left15:22
jguddas-tr2 left15:22
Celmor[m] I like to keep the code in my commits in a working state so if something breaks I see exactly made it break15:22
chele left15:23
Celmor[m] so filter-branch just copies the history of the path?15:24
scrote If i'm squashing via interactive rebase, can I change the final commit's (the one everything is squashed into)'s commit message right there during the interactive rebase? Or must it remain the same, and do an additional --ammend if I want to change it15:27
_xor joined15:28
royal_screwup21 joined15:31
gxt joined15:32
czart_ joined15:33
cdown left15:33
czart left15:36
_xor left15:36
_xor joined15:37
justanotheruser joined15:37
glosoli joined15:38
agg joined15:39
threenuc joined15:40
blackmesa joined15:41
ExeciN joined15:42
glosoli left15:42
dijitol joined15:43
threenuc Hi. I have this repo - https://github.com/3nuc/dotfiles . Recently it's possible to use git submodules as a plugin manager for Vim, so I tried to take advantage of that. I clone the repo using `git clone [url] --recursive` but it the folders in ~/dotfiles/.vim/plugins/start/[anyplugin] are empty. Meaning the clone didn't recursively load submodules. Why is that the case? My .gitmodules file is in dotfiles/.vim folder15:43
imigunov left15:43
tsaka__ left15:45
moldy Celmor[m]: you still see exactly what broke if you commit the copied file in a single commit15:46
tsaka__ joined15:46
teward left15:46
rfuentess left15:46
cdunklau anddam: yes, that's correct. master was merged into Feature15:47
moldy scrote: not sure from the top of my head, but if you rebase one commit further back, it should definitely be possible15:47
cdunklau anddam: you don't _have_ to do that before rebasing, IIRC, but it's probably a good idea, since you'd want to make sure the merge would actually work, test it, etc15:49
i'm off15:50
_xor left15:51
_xor joined15:51
shored left15:52
shored joined15:52
oxymoron93 joined15:52
_xor left15:53
nerosnm joined15:53
_xor joined15:53
tharkun joined15:55
teward joined15:56
tharkun Good $DAY some idiot erased a branch from our git server. Is there a way to figure out who did it?15:56
e^1 joined15:58
bin_bash linux server?15:59
igemnace not from within git, no. are you using some git hosting provider?15:59
ed_peguillan left16:01
gxt left16:05
gloomy left16:07
malina left16:15
malina joined16:17
jguddas-tr2 joined16:17
jguddas-tr3 joined16:18
threenuc left16:19
thiago left16:19
glosoli joined16:20
tgunr left16:20
agowa338 left16:20
lupine left16:21
lupine joined16:21
jguddas-tr2 left16:21
glosoli left16:22
jottr_ left16:25
gareppa joined16:28
im0nde_im0nde116:28
jottr_ joined16:28
javashin left16:29
jottr joined16:31
liberiga left16:32
jottr__ joined16:33
im0nde_ joined16:33
jottr_ left16:33
gareppa left16:34
tgunr joined16:34
im0nde1 left16:35
tgunr left16:35
jottr left16:36
Cabanossi left16:38
veegee left16:38
fphilipe_ joined16:40
tsaka__ left16:42
Cabanossi joined16:44
mindveg joined16:44
tsaka__ joined16:45
glosoli joined16:46
im0nde_ left16:47
wootehfoot joined16:49
im0nde_ joined16:49
justan0theruser joined16:50
clime joined16:51
gajah joined16:51
justanotheruser left16:51
e^1 left16:53
alonkli left16:54
tharkun bin_bash: Yes, it is a linux server.16:55
igemnace: no, it is company hosted.16:56
Do I need to dive into ssh logs?16:56
moldy probably, yup16:56
or http, depending16:57
gloomy joined16:58
tharkun Ok, :(16:58
bin_bash yep and then bash history16:59
thiago joined17:00
tharkun bash_history? Why so?17:02
NwS joined17:05
igemnace are you using some git hosting software?17:05
tharkun plain git17:05
git init -bare iirc17:05
Mattiaslndstrm joined17:06
gareppa joined17:07
igemnace right. yep, will have to dive into any sort of audit logs you have on the server17:09
gloomy left17:10
malmalmal left17:10
moldy and ask yourself why people have write permissions if you don't trust them ;)17:11
oxymoron93 thankfully this is why distributed vcs exist. Nothing is lost.17:12
nabil_ joined17:15
millerti joined17:16
TomyWork left17:16
tsaka__ left17:16
igemnace and if you're on git init --bare, it's not like any commits are lost. you can just recreate the branch17:17
justan0theruser left17:17
tsaka__ joined17:17
gloomy joined17:17
Raging_Hog left17:17
SkarmoutsosV joined17:18
nabil__ left17:18
planetcall|work left17:18
bin_bash tharkun: ssh logs aren't going to tell what commands someone ran while ssh'd in.17:20
tsaka__ left17:23
tsaka__ joined17:25
gxt joined17:25
tharkun bin_bash: the git user has /usr/bin/git-shell so actually noone can log in as it. Hence my lack of understanding how it got wiped out.17:26
malmalmal joined17:27
figuinhas left17:28
gordonfish joined17:28
POQDavid left17:29
nikivi left17:29
marklite left17:29
pikapika left17:29
bin_bash i haven't used git-shell, does it not allow removing of branches?17:30
CryptoDavid joined17:30
Phylock joined17:31
POQDavid joined17:31
nikivi joined17:32
marklite joined17:32
tsaka__ left17:33
justan0theruser joined17:34
tsaka__ joined17:34
SkarmoutsosV left17:35
pikapika joined17:35
jottr__ left17:38
rodorgas joined17:39
nika_ left17:40
fphilipe_ left17:43
igemnace left17:44
tsaka__ left17:46
tsaka__ joined17:47
tharkun It does not allow login at all.17:47
bin_bash ¯\_(ツ)_/¯17:48
have you confirmed that tharkun?17:48
jguddas-tr3 left17:49
tharkun Yes :)17:50
Anyway, I will have to take some backup actions outside of the repositorie to find differences and correlate that to the ssh logs. I hope that does not take me a lot of time.17:51
bin_bash: Thanks for taking care of my situation.17:51
bin_bash seems really weird... ive not used git-shell, but looking at the docs it seems like something may be misconfigured https://git-scm.com/docs/git-shell17:52
Superfox_il_volp joined17:52
tsaka__ left17:52
dglambert joined17:53
T_UNIX left17:53
dglambert yo17:53
quick questino17:53
someone accidentally merged a branch in to their branch when they shouldn't have17:53
tharkun bin_bash: I am looking into it. Thanks again.17:53
dglambert I can revert the merge commit17:53
but what if I reset the head to the commit before the merge commit17:53
bin_bash np gl17:53
pSouper joined17:55
dglambert my concern is the timeline, let say the last commit of the developer was yesterday 9/23, the merge commit was today 9/24, but lets say that the merge commit brought in commits from a week prior, lets say 9/1317:55
would the 9/13 commit still be in if I reset to the 9/23 commit17:55
tsaka__ joined17:56
gareppa left17:58
igemnace joined17:58
tribly left17:59
tribly joined17:59
tsaka__ left18:00
tsaka__ joined18:00
tsaka__ left18:04
tsaka__ joined18:05
Sasazuka joined18:06
usbguy1 left18:07
fflam left18:08
leeN joined18:09
fflam joined18:09
gloomy left18:10
tsaka__ left18:13
czart_ left18:13
tribly left18:13
tsaka__ joined18:14
vishal dglambert: git works on ancestry of commits, not their dates18:16
so resetting to one before the merge will remove everything the merge brought in, regardless of the date18:17
troulouliou_dev joined18:19
bolovanos joined18:20
pie_ left18:21
tsaka__ left18:22
sauvin left18:29
f3r70rr35f left18:30
gareppa joined18:34
shabius left18:34
Sasazuka left18:35
tufteddeer left18:36
dglambert vishal thank you, I thought that would be the case18:36
gh00p joined18:36
tribly joined18:37
gh00p Hi folks. I've lost an alias and I miss it. I used to have a `gls` bash alias that basically gave me `ls` style ouput but with git hash and last update date per file. I seem to recall that it was a pipe, perhaps something that ran `git ls-files` through xargs for another git command to apply formatting per-file. Does this sound like something you might have?18:38
fuzzybear3965 joined18:38
fuzzybear3965 I just did a `git merge master` on a `feature` branch.18:39
I was 4 commits behind `master`.18:39
cdown joined18:39
dglambert left18:39
fuzzybear3965 I was 1 commit ahead of the remote feature branch.18:39
ghoti gh00p: so you're basically looking for a `-l` (long format) version of `git ls-files`?18:39
fuzzybear3965 Now, I'm 5 commits ahead of the remote feature branch.18:39
This all makes sense, except for that `git log` shows `origin/feature` as being only one commit behind my local `feature` branch....18:40
I don't see the 4 commits that were merged in from `master`.18:40
millerti left18:40
fuzzybear3965 Would anyone know why this is happening?18:40
gh00p ghoti: yes, kinda. I don't need file size or filesystem timestamp, but it would be great to be able to review files in the directory and their status (staged, changed) with a single commend.18:40
ghoti gh00p: sounds useful. I'd like that too. Hope someone else answers you. :-)18:41
fphilipe_ joined18:41
gschanuel59gschanuel18:42
jottr__ joined18:42
millerti joined18:42
ericfreese left18:42
shabius joined18:43
glosoli left18:44
Sasazuka joined18:45
cd joined18:45
cdown_ joined18:45
nabil_ left18:47
ExeciN left18:47
cdown left18:48
cdown_cdown18:48
im0nde_im0nde118:48
fphilipe_ left18:48
jottr__ left18:50
fuzzybear3965 ... anybody?18:51
millerti left18:53
EnJohnGee joined18:53
vishal gh00p: something like this:18:53
git ls-files | while read -r file; do git --no-pager log --format="format:%h %s" -1 -- "$file"; printf "%s\n" "$file"; done18:53
millerti joined18:54
SkarmoutsosV joined18:56
shabius left18:59
is_null_ joined19:00
millerti left19:01
pSouper left19:01
jottr__ joined19:01
fuzzybear3965 left19:02
rodorgas left19:02
millerti joined19:03
blackmesa left19:03
nerosnm left19:06
g00s joined19:06
gloomy joined19:06
blackmesa joined19:08
jottr__ left19:08
pie_ joined19:12
imigunov joined19:14
is_null left19:15
is_null_ left19:15
kantlivelong left19:16
gloomy left19:18
jnewt joined19:19
shabius joined19:19
rsrx joined19:20
caskd-dev left19:20
kantlivelong joined19:23
imigunov left19:26
nerosnm joined19:26
caskd joined19:27
malmalmal left19:29
nerosnm left19:31
nurdie left19:32
emsjessec left19:32
gloomy joined19:34
nerosnm joined19:35
comptroller left19:36
fuzzybear3965 joined19:37
fuzzybear3965 left19:37
troulouliou_div2 joined19:38
jottr__ joined19:39
nabil joined19:42
malmalmal joined19:44
nerosnm left19:44
anddam left19:46
comptroller joined19:46
jottr__ left19:49
nabil left19:52
anddam joined20:00
Fernando-Basso joined20:05
CryptoDavid left20:06
owlscientist joined20:07
n3wborn joined20:09
Lucas_Gray joined20:11
EnJohnGee left20:13
bitwinery joined20:14
tobiasBora left20:15
Dougie187 left20:16
nerosnm joined20:18
DoDU joined20:20
kerframil left20:22
chris11 joined20:22
limarfrek joined20:22
limarfrekkerframil20:22
chris11 I've got a repo on GitHub with subfolders. The subfolders are themselves repos. Can I point fetch and push urls to those subfolders?20:23
troulouliou_div2 left20:27
Lucas_Gray left20:27
Lucas_Gray joined20:29
saint_ left20:30
bitwinery left20:31
feriman left20:31
nerosnm left20:33
jnewt left20:35
saint_ joined20:35
dege joined20:39
gh00p left20:40
ghoti gh00p, vishal, you inspired me. What about this?20:40
gls() { git ls-files | while read -r file; do git --no-pager log --format=$'format:%h\t%ai\t<%aE>\t' -1 -- "$file"; printf "%s\n" "$file"; done | column -s $'\t' -t; }20:40
JanC left20:40
pi- left20:41
ghoti gh00p, you dropped off. What about:20:41
gls() { git ls-files | while read -r file; do git --no-pager log --format=$'format:%h\t%ai\t<%aE>\t' -1 -- "$file"; printf "%s\n" "$file"; done | column -s $'\t' -t; }20:42
Phylock left20:42
ghoti gah, he's still gone.20:42
JanC joined20:44
oatmealraisin left20:44
JanC left20:45
courrier joined20:46
JanC joined20:46
i^migunov joined20:49
dgw joined20:51
ericfreese joined20:52
gareppa left20:53
Phylock joined20:56
m0viefreak joined20:56
inkbottle left21:02
chris11 left21:02
oxymoron93 left21:05
SkarmoutsosV left21:06
prg318 left21:07
gloomy left21:07
prg318 joined21:08
Phylock left21:08
Stoot left21:09
nurdie joined21:10
nurdie_ joined21:12
yonder joined21:13
moldybits left21:13
nerosnm joined21:14
nurdie left21:15
inkbottle joined21:15
rodorgas joined21:17
n3wborn left21:17
durham joined21:18
n3wborn joined21:19
nerosnm left21:21
tmager left21:22
bambanx joined21:23
nerosnm joined21:24
Qizzy joined21:27
tgunr joined21:36
g00s left21:37
imigunov joined21:38
malmalmal left21:40
leeN left21:43
i^migunov left21:46
dijitol left21:46
i^migunov joined21:47
imigunov left21:50
imigunov joined21:51
i^migunov left21:51
nerosnm left21:52
troulouliou_dev left21:53
kerframil left21:54
Superfox_il_volp left21:54
rsrx left21:55
imigunov left21:56
i^migunov joined21:56
kerframil joined21:57
wootehfoot left21:59
nerosnm joined22:00
nurdie_ left22:00
Envil left22:01
clime left22:01
oatmealraisin joined22:02
Raimondii joined22:03
nerosnm left22:04
bolovanos left22:04
vavkamil left22:05
Raimondi left22:06
RaimondiiRaimondi22:06
Envil joined22:07
Stoot joined22:08
greggerz left22:08
CodeSlingerPaul left22:10
POQDavid left22:10
igemnace left22:10
nikivi left22:11
marklite left22:11
pikapika left22:11
Lucas_Gray left22:12
Raimondi left22:14
nerosnm joined22:16
Raimondi joined22:19
imigunov joined22:19
Stoot left22:20
i^migunov left22:21
nabil joined22:22
kerframil left22:22
imigunov left22:22
Newami left22:22
nerosnm left22:22
nerosnm joined22:24
xcm left22:27
is_null joined22:27
is_null_ joined22:27
xcm joined22:28
nerosnm left22:29
oatmealraisin left22:29
Stoot joined22:32
bitwinery joined22:34
ferdna joined22:37
nuxdie left22:38
justan0theruser left22:40
justanotheruser joined22:40
nuxdie joined22:40
igemnace joined22:41
owlscientist left22:43
SmashingX joined22:44
Stoot left22:45
Wetmelon joined22:47
is_null left22:48
is_null joined22:49
nerosnm joined22:49
royal_screwup21 left22:50
nerosnm left22:54
omnireq left22:54
ericfreese left22:55
Stoot joined23:01
wwalker I can find in my .git/config "[branch "8221-3540"]; remote = upstream; merge = refs/heads/release_3.5.40" what is the git command that would show me that same data about the current branch?23:01
igemnace left23:01
nerosnm joined23:01
thiago left23:02
nerosnm left23:06
thiago joined23:06
nurdie joined23:06
cdown left23:10
nerosnm joined23:10
cdown joined23:11
nurdie left23:11
cd left23:11
nurdie joined23:13
nerosnm left23:14
nurdie left23:17
nerosnm joined23:17
nerosnm left23:22
publio joined23:23
nerosnm joined23:27
perrier-jouet left23:29
justan0theruser joined23:30
justanotheruser left23:31
m0viefreak left23:32
nerosnm left23:33
n3wborn left23:33
dege left23:34
z8z left23:35
jtmusky joined23:42
moldybits joined23:44
nerosnm joined23:45
jguddas-tr3 joined23:47
nerosnm left23:49
blackmesa left23:49
jguddas-tr3 left23:51
oatmealraisin joined23:51
nerosnm joined23:52
nerosnm left23:57
SmashingX left23:57

Logs Search ←Prev date Next date→ Channels Documentation