IRCloggy #git 2018-05-25

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.

2018-05-25

Zarthus probably a for loop on `git branch --remote`00:00
rafasc clone already does that by default00:00
rafasc left00:03
maroloccio joined00:05
nitric_ left00:06
ajf- I cherry-picked a bunch of commits that master had differently from develop (which I got using git log master ^develop) into a new branch named develop-cp based off develop00:07
Puffball left00:07
ajf- and now doing git log master ^develop-cp shows the same differences, when it should not since I cherry-picked those commits00:07
I can see that the SHAs resulting from those cherry-picks are different than the originals, maybe because they had conflicts?00:07
Onionnion left00:08
thiago joined00:09
fassl left00:09
afuentes left00:10
medfly thanks. I started with a partial clone which was probably the reason things were weird for me. Fetching the rest.00:10
ProCycle left00:11
banisterfiend joined00:11
tmsmith left00:11
Narrat left00:12
BallChang-CN left00:14
pR0Ps left00:14
shabius left00:16
dreiss left00:16
beginnertest left00:16
pR0Ps joined00:17
lilherc left00:18
shabius joined00:19
dviola left00:19
Oatmeal left00:20
m0viefreak left00:22
venmx joined00:23
zizzfizzix joined00:23
zizzfizzix left00:23
zizzfizzix joined00:23
jessica523 joined00:23
jessica523 left00:23
DaGoaty left00:25
Nizumzen joined00:26
SwiftMatt joined00:27
zizzfizzix left00:28
zizzfizzix joined00:28
zizzfizzix left00:28
zizzfizzix joined00:28
zizzfizzix left00:29
Guest91580 joined00:29
akushner left00:29
cagomez left00:29
cagomez joined00:30
hugobrendow left00:30
hugobrendow joined00:31
orbyt_ joined00:32
cagomez left00:34
JonnyAt joined00:34
venmx left00:35
pity joined00:36
maroloccio left00:37
vdamewood left00:41
lf94 joined00:42
BallChang-CN joined00:43
linuxmodder- left00:48
xmbq joined00:49
dviola joined00:52
venmx joined00:57
medfly left01:01
agowa338 left01:01
bork left01:03
bork joined01:04
tre99 left01:05
dviola left01:08
dviola joined01:08
tvw left01:09
dendazen joined01:10
robattila256 left01:11
Sasazuka left01:11
fission6 joined01:12
frobnic left01:12
frobnic joined01:12
tre99 joined01:12
lf94 left01:13
Guest81203 left01:14
nbmc joined01:14
Milos joined01:15
nbmc left01:18
nbmc joined01:18
Puffball joined01:18
finalbeta joined01:22
igemnace joined01:26
vdamewood joined01:28
_xor left01:31
Lyqyd joined01:32
rivalomega joined01:35
craftyguy left01:36
craftyguy joined01:36
SwiftMatt left01:37
venmx left01:37
rivalomega left01:39
fission6 left01:41
vdamewood left01:43
mel00010 left01:43
goweol joined01:44
ilbot3 left01:45
ferdna joined01:46
doubtful joined01:47
Puffball left01:50
_xor joined01:55
Praxi left01:55
ilbot3 joined01:57
andyhuzhill joined01:57
nutron left02:04
al-damiri left02:05
nutron joined02:07
Goplat joined02:09
sentriz left02:12
sentriz joined02:12
_28_ria left02:17
nurdie joined02:17
j416 left02:19
crmne left02:21
crmne joined02:22
Nizumzen left02:22
kneeki left02:23
Nizumzen joined02:23
nurdie left02:23
mizu_no_oto joined02:25
zlsyx joined02:26
RougeR left02:26
durham left02:27
drodger left02:33
lagothri1 joined02:35
j416 joined02:37
lagothrix left02:37
zlsyx left02:39
drodger joined02:39
zulutango joined02:39
mizu_no_oto left02:39
Bobguy joined02:40
aidalgol left02:41
Bobdude left02:44
YuGiOhJCJ joined02:45
mud joined02:50
jessica523 joined02:51
pR0Ps left02:51
aidalgol joined02:52
pR0Ps joined02:53
Guest21082 left02:54
mizu_no_oto joined02:59
arahael joined03:02
gordonfish left03:03
mizu_no_oto left03:03
nurdie joined03:03
_28_ria joined03:07
m00sehead left03:09
jcarpenter2 left03:10
thiago left03:11
_28_ria left03:12
arahael left03:13
arahael joined03:13
howdoi joined03:15
oojacoboo left03:22
oojacoboo joined03:22
_Patrick_ left03:24
_Patrick_ joined03:29
lf94 joined03:33
cagomez joined03:33
orbyt_ left03:33
Nizumzen left03:39
orbyt_ joined03:40
preyalone joined03:41
jcarpenter2 joined03:42
Mattiaslndstrm left03:43
Gurkenglas joined03:47
tre99 left03:51
\void left03:55
lf94 left03:56
lf94 joined03:57
tre99 joined03:58
\void joined03:59
ZyX-I joined03:59
bjsnider left04:03
Gurkenglas left04:03
Raging_Hog joined04:03
nuka-cola_ left04:04
mikemcowie joined04:04
cagomez left04:11
mad_hatter left04:12
rkazak joined04:13
orbyt_ left04:13
mud left04:17
mikemcowie left04:17
dreiss joined04:18
fr33domlover left04:21
ajf- left04:22
johnny56 left04:22
johnny56_ joined04:22
dreiss left04:24
doubtful left04:24
doubtful joined04:25
pnepe6 joined04:25
dendazen left04:26
amirpro left04:27
Nizumzen joined04:32
doug16k left04:32
thiago joined04:34
linuxmodder- joined04:37
doubtful left04:37
linuxmodder- left04:37
linuxmodder- joined04:38
linuxmodder- left04:39
linuxmodder- joined04:39
doubtful joined04:40
doubtful left04:40
linuxmodder- left04:40
linuxmodder- joined04:41
linuxmodder- left04:41
linuxmodder- joined04:42
cramalho joined04:44
mad_hatter joined04:45
doug16k joined04:46
pabs3 joined04:46
pabs3 I accidentally did a `git reset --hard @` after a `git stash pop`. is there any way to get that git stash restored?04:47
grawity scroll up to where it shows "Dropped refs/stash@{0} (some commit hash here)"04:48
_ikke_ pabs3: git stash pop should show you the hash04:48
grawity run `git stash store $HASH`04:48
justrohu joined04:48
keepLearning512 joined04:48
justrohu Hello I have a query regarding tags04:49
muelleme joined04:49
justrohu I have a master and development branch04:49
pally joined04:50
freimatz joined04:51
justrohu I have applied tag to a commit on master branch ... now after more additions I want to view code which I have tagged how do i do this04:51
please help04:51
_ikke_ git show <tag>04:52
for example04:52
pabs3 bummer, the tree from my stash has been lost: fatal: unable to read tree 2014e0c6cda108c735ccf10d214b495ba865bdbc04:53
_ikke_ Hmm, odd04:54
justrohu _ikke_, thank you04:54
thiago left04:54
_ikke_ pabs3: I wouldn't expect that so soon04:55
TheRuckus joined04:55
justrohu What is Tag is used for04:55
_ikke_ justrohu: It's to give certain commits a specific name, mostly used to tag versions04:56
justrohu clear04:57
thank you04:57
rivalomega joined04:58
jungsubk joined05:02
keepLearning512 left05:05
muelleme left05:06
keepLearning512 joined05:06
jimmyrcom left05:07
arahael pabs3: Is it in the reflog? If it's there, it really shouldn't have been lost so soon.05:07
jungsubk left05:08
pabs3 doesn't look like it05:08
anyway, restored from a backup05:08
Guest49611 left05:14
crtcji joined05:16
keepLearning512 left05:16
pally left05:18
rivalomega left05:18
rivalomega joined05:18
gordonfish joined05:18
djh_ left05:19
pally joined05:20
ArcaTech joined05:21
TheRuckus left05:21
dimi1947 joined05:23
sauvin joined05:24
pabs3 left05:24
crtcji left05:27
Worldexe joined05:30
igemnace left05:32
rkazak left05:32
crtcji joined05:35
KeyJoo joined05:38
pfleck joined05:38
KeyJoo left05:38
KeyJoo joined05:39
crtcji left05:40
dre_ joined05:40
sleepingforest left05:40
phinxy left05:42
subhojit777 joined05:45
mohabaks joined05:48
freimatz left05:50
pfleck left05:51
pfleck joined05:59
preyalone left06:01
muelleme joined06:02
darkcodi joined06:02
darkcodi left06:03
Lyqyd left06:03
darkcodi joined06:04
muelleme left06:07
keepLearning512 joined06:09
jntme joined06:09
muelleme joined06:10
chele joined06:11
inovas left06:11
YuGiOhJCJ left06:15
inovas joined06:17
darkcodi left06:19
pfleck left06:20
schleppel joined06:23
keepLearning512 left06:23
tarkus joined06:24
JeroenT joined06:26
muelleme left06:27
Bobguy left06:28
pfleck joined06:30
dreiss joined06:31
abba joined06:32
eduardas_m joined06:32
RougeR joined06:36
sz0 left06:36
Worldexe left06:37
mohabaks left06:39
linuxmodder- left06:39
JimmyRcom_ left06:40
Tobbi joined06:41
veegee left06:43
pally left06:45
l3dx joined06:48
subhojit777 left06:49
ewitz left06:49
testuser joined06:50
ewitz joined06:50
john-34 joined06:52
nurdie left06:54
JimmyRcom_ joined06:56
Guest8084Cork06:57
g00s joined07:01
JimmyRcom_ left07:01
pally joined07:01
Raging_Hog left07:03
Raging_Hog joined07:03
tvw joined07:04
ferdna left07:06
Phylock joined07:08
mel00010 joined07:08
dege joined07:08
jessica523 left07:10
amirpro joined07:12
MaliusArth joined07:13
dreiss left07:13
Wulfe813 left07:13
jessica523 joined07:13
\void left07:14
oxymoron93 joined07:15
Tobbi_ joined07:16
luckman212 left07:18
pally left07:19
jntme left07:19
pally joined07:20
pally left07:20
charolastra joined07:22
Guest55350 left07:23
muelleme joined07:23
keepLearning512 joined07:24
jntme joined07:24
rivalomega left07:25
luckman212 joined07:25
ArcaTech left07:27
djh joined07:28
muelleme left07:28
Nizumzen left07:30
duderonomy left07:31
Neo4 joined07:35
mikemcowie joined07:36
texinwien_ joined07:36
pfleck left07:37
texinwien left07:40
amirpro left07:44
amirpro joined07:44
dviola left07:45
DaGoaty joined07:47
dre_ left07:48
amirpro left07:48
choice joined07:48
choice Hello! Can I tell git to pull a file from the working dir that is not tracked?07:49
amirpro joined07:49
choice Otherwise I will just scp it.07:49
tarkus left07:50
osse pull from the working dir of where?07:50
choice Of the origin.07:50
osse no07:50
PEG joined07:50
choice Ok, using scp then.07:51
tarkus joined07:53
osse a file that is not tracked can neither be pushed nor pulled07:53
because you don't really push/pull files, you push commits07:53
choice True. But git might have had some convinience function 'copyfilefromremoteworkingdir'.07:54
mosab joined07:55
_ikke_ nope07:59
git is not a file synchornization tool :-)07:59
even though people tend to treat it as one07:59
floppydh joined08:03
jntme left08:04
cbreak choice: if it's not committed, it's probably not ready to be transfered yet08:06
mosab_ joined08:07
cbreak especially if it's untracked08:07
choice It's untracked because it's the config file. I just wanted a copy of the config file so I can edit it to my local needs.08:07
So I fetched it via scp now.08:08
cbreak choice: usually, config file templates are either created by the program when you first start it08:09
or they are committed as explicit template file with documentation on how to customize it08:09
mosab left08:09
mosab_mosab08:09
skisela joined08:09
choice Yeah, there is a config template. But I wanted to use the config of a specific machine because its very similar to my local machine.08:10
Tobbi_ left08:10
Tobbi_ joined08:11
pfleck joined08:12
DaGoaty left08:14
JeroenT left08:19
duderonomy joined08:19
phinxy joined08:20
jntme joined08:21
Guest41156 left08:23
muelleme joined08:24
JeroenT joined08:24
JeroenT left08:25
pfleck left08:26
dreiss joined08:27
KeyJoo left08:28
muelleme left08:29
duderono_ joined08:30
manuelschneid3r joined08:30
duderonomy left08:31
igemnace joined08:31
ustekne joined08:32
choice left08:34
igemnace left08:38
igemnace joined08:38
wandering_vagran joined08:38
keepLearning512 left08:38
igemnace left08:38
igemnace joined08:39
keepLearning512 joined08:40
tarkus left08:40
dre_ joined08:42
tarkus joined08:43
_rgn left08:49
_rgn joined08:49
RichiH joined08:52
antfoo left08:54
arecaceae left08:54
pfleck joined08:54
arecaceae joined08:55
JeroenT joined08:56
keepLearning512 left08:56
keepLearning512 joined08:58
doev joined08:59
pfleck left08:59
_ADN_ joined09:00
dhollinger left09:00
rfuentess joined09:00
dhollinger joined09:01
venmx joined09:01
BallChang-CN left09:01
keepLearning512 left09:03
JeroenT left09:04
dege left09:05
doug16k left09:07
rfuentess left09:09
goweol left09:10
JeroenT joined09:12
afuentes joined09:14
dreiss left09:15
g00s left09:16
antfoo joined09:16
theoceaniscool joined09:18
rfuentess joined09:18
igemnace left09:20
dpyro left09:20
doug16k joined09:20
doug16k left09:20
Naq joined09:21
doug16k joined09:21
keepLearning512 joined09:21
Naq left09:21
raven-au joined09:22
ustekne left09:22
pfleck joined09:24
rivalomega joined09:25
luke_penn joined09:26
energizer left09:26
luke_penn left09:26
BallChang-CN joined09:28
pfleck left09:28
rivalomega left09:30
ZyX-I left09:30
RougeR left09:31
ocds joined09:31
andyhuzhill left09:35
catsup left09:36
catsup joined09:36
duderono_ left09:37
Goplat left09:37
catsup left09:37
duderonomy joined09:37
raven-au left09:37
catsup joined09:37
beerdrop left09:38
raven-au joined09:39
justrohu left09:40
jntme left09:41
tarkus left09:41
raven-au left09:41
jntme joined09:41
keep_learningkeep_away09:42
raven-au joined09:43
thebloggu joined09:44
ronskisika joined09:45
Raging_Hog left09:45
duderonomy left09:45
jntme left09:46
duderonomy joined09:47
fatalhalt left09:48
mel00010 left09:49
leeN joined09:50
mel00010 joined09:51
mosab_ joined09:51
beerdrop joined09:53
justrohu joined09:53
mosab left09:54
mosab_mosab09:54
keepLear_ joined09:54
keepLearning512 left09:55
pity left09:56
tarkus joined09:57
Gurkenglas joined09:58
jessica523 left09:59
lankanmon left10:01
keepLearning512 joined10:05
MarioBranco joined10:05
keepLear_ left10:05
tmsmith joined10:06
thebloggu left10:07
Kaisyu left10:10
shady_traveller joined10:14
Tobbi_ left10:15
rafasc joined10:17
beerdrop left10:18
tmsmith left10:21
JellybeanCantrel joined10:21
JellybeanCantrel left10:21
linuxmodder joined10:21
Mike11 joined10:23
plexigras joined10:24
smallville7123 joined10:24
inovas left10:27
camsbury joined10:27
dimi1947 left10:29
kes joined10:30
pix9 hey folks how get list of commit hash, commited after certain commit ( need this to validate commit hash for given commit")10:30
exotime left10:30
camsbury left10:31
cousteau joined10:33
ghost43 left10:33
osse pix9: after where? In all possible branches ?10:33
inovas joined10:33
pix9 hmm10:33
scenarios is I am creating script to push the code to prod10:34
duderonomy left10:34
ghost43 joined10:34
pix9 here I am trying to verify ig the given commit hash is valid or not10:34
cousteau so let me get this right. `git checkout <paths...>` changes the tree but doesn't switch branch, and `git checkout branch` with no paths or --patch switches branch but does not modify the tree?10:34
or modifies the tree but not the edited files?10:34
pix9 at same time I don't want some one to revert the code to told commit10:34
osse pix9: git rev-parse --verify {hash}10:34
m00sehead joined10:35
pix9 osse will this ensure that hash is not the olde that what is current in production?10:35
beerdrop joined10:35
osse pix9: no it will just make sure it's a valid commit hash10:36
rafasc cousteau: checkout always modifies the tree.10:36
cousteau right now I have both master and corrections pointing to HEAD, with uncommitted changes, and I want to change to branch master without losing the changes, and since I'm paranoid I want to make sure that `git checkout master` won't undo my changes10:36
osse correction: git rev-parse --verify 'abcd1234^{commit}'10:36
justrohu left10:36
osse cousteau: it will work just fine10:37
pix9 hmm I want to do both validate and make sure hash doesn't belong to historic commit10:37
rafasc cousteau: master and corrections pointing to HEAD makes no sese.10:38
sense10:38
osse pix9: i don't understand.10:38
pix9 in terms of svn let's say my production is on revision number 5 now someone passes revision number 4 to my script for code update, it should (script) fail as the code is will be reverted to olders revision that one which is in production.10:39
cousteau so `git checkout master -- .` will delete my changes, but `git checkout master` won't?10:39
pix9 it is easy in svn as there numbers10:39
Gurkenglas left10:39
pix9 I want to achive same in my git script, which pushes code to production.10:39
rafasc cousteau: yes. If checkout another thing needs to overwrite your stuff, git will stop and ask to either commit or stash.10:40
_ikke_ pix9: you can use git merge-base --is-ancestor for that10:40
osse pix9: check if git merge-base --is-ancestor newhash currenthash is true. if it is then report error10:40
pix9 so rite now I ma doing git pull10:40
sorry git fetch10:40
then git log --all10:41
but this gives me all the possible logs10:41
all possible commits10:41
_ikke_ What do you need?10:41
cousteau rafasc, ok, so if checkout would change a file which currently has uncommitted changes it will complain10:41
pix9 I will try merte-base10:41
don't know how it works10:41
thanks you for suggestions guys.10:42
rafasc cousteau: it will abort and error out saying something like "you have uncommited changes, please commit or stash"10:42
duderonomy joined10:42
cousteau ok thanks!10:42
justrohu joined10:42
rafasc cousteau: but only in the case when there's no paths.10:43
cousteau: if there are paths, it will just overwrite.10:43
cousteau makes sense, thanks!10:43
CodeSlingerPaul joined10:43
cousteau ok, step 1, make a backup because I'm paranoid10:44
rafasc cousteau: sometimes when I find myself switching too much between two branches, I just add a new worktree.10:44
cousteau: that way you can work on both branch at the same time, on different directories.10:44
cousteau OK, did the checkout and nothing was lost. Good. Can delete the backup now.10:45
raven-au left10:45
cousteau rafasc, I see... well, in this case it's just that I'm relying on branches as "work markers", although my work is mostly linear10:46
smallville7123 left10:46
rafasc cousteau: that's a bit irrelevant to the issue.10:47
smallville7123 joined10:47
fanhako joined10:47
riemann joined10:48
tarkus left10:48
cousteau what I mean is, I could just not be using branches (and, if anything, use tags to mark different stages of development)10:48
raven-au joined10:48
rafasc you lose nothing by using branches.10:49
cousteau time10:50
crtcji joined10:51
rafasc if you're loosing time by using branches, you're doing something wrong.10:51
lankanmon joined10:51
cousteau at least in my current work flow in which I'm using branches to point to different points of a linear tree, and then have to move them manually... it's just silly by me10:51
not saying branches are useless; in fact I've used them before to have a clearer view of my edit history; it's just that in this case I might be overusing them10:52
but well, it's not like I'm doing something bad; if anything, inefficient; but that's because I'm no git expert yet10:53
rafasc parses overusing branches crashes10:53
nickmc joined10:54
pix9 found the solution10:54
git log --all --after"datestamp"10:54
jhaenche_ joined10:54
jhaenchen left10:54
xmbq left10:55
dimi1947 joined10:55
x1b4 joined10:56
rajkane_prajta joined10:56
rajkane_prajta left10:56
nbmc left10:57
justrohu left10:57
plexigras left10:57
rafasc pix9: --after is not a reliable way to determine ancestry. the right tool for the job is merge-base --is-ancestor as previously suggested.10:58
hegge_ left10:58
plexigras joined10:58
rafasc pix9: git doesn't guarantee a later commit will have a later timestamp.10:59
Mike11 left11:04
fanhako left11:04
rajkane_prajta joined11:07
tarkus joined11:07
topdownjimmy joined11:09
JeroenT_ joined11:11
JeroenT left11:11
pfleck joined11:12
justrohu joined11:12
pix9 dang11:13
linuxmodder- joined11:13
linuxmodder left11:14
hugobrendow left11:14
hugobrendow joined11:14
pix9 git merge-base --is-ancestor ${PROD_HASH} ${GIT_HASH}11:17
FTW11:17
Cavallari joined11:19
sitaram left11:20
TheRuckus joined11:22
duderonomy left11:23
duderono_ joined11:24
TheRuckus left11:27
jimi_sanchez joined11:27
amirpro left11:29
xaa joined11:29
amirpro joined11:30
linuxmodder- left11:31
linuxmodder- joined11:31
rsrx joined11:32
pks_ joined11:32
rsrx left11:33
fr33domlover joined11:34
cousteau left11:34
amirpro left11:34
rsrx joined11:34
amirpro joined11:35
pks left11:36
pks_pks11:36
rsrx left11:36
rsrx joined11:37
dianni joined11:37
moldy left11:37
tvw left11:38
linuxmodder- left11:39
nurdie joined11:39
jottr joined11:40
JeroenT_ left11:41
Guest25333 left11:41
Guest25333 joined11:41
nurdie left11:42
Master__ joined11:42
nurdie joined11:42
Guest25333 left11:43
smallville7123 left11:43
Asassin333 joined11:43
Asassin333 left11:44
pity joined11:44
NerdyPepper left11:44
MarioBranco left11:44
fr33domlover left11:46
nurdie left11:47
smallville7123 joined11:47
NerdyPepper joined11:47
redrabbit left11:47
redrabbit joined11:48
saltlake joined11:48
JeroenT joined11:48
amirpro left11:49
amirpro joined11:50
jottr left11:52
ojdo left11:52
pfleck left11:53
Regon joined11:53
amirpro left11:54
amirpro joined11:55
mightywomble joined11:58
ojdo joined11:59
jrabe left12:00
hegge joined12:00
pity left12:00
jrabe joined12:00
saltlake hi12:02
gitinfo saltlake: 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.12:02
saltlake git push -u origin master, what is -u here?12:02
jgoss joined12:03
wandering_vagran left12:03
tarkus left12:04
keepLearning512 left12:05
wandering_vagran joined12:05
sitaram joined12:06
x1b4 left12:06
sitaramGuest1185112:06
Guest11851 left12:07
Guest11851 joined12:07
rafasc saltlake: have you even tried looking the man page?12:07
widp left12:08
leeN left12:11
mikemcowie left12:11
mightywomble left12:14
mightywomble joined12:15
pfleck joined12:15
keepLearning512 joined12:15
canton7 left12:15
Guest11851 left12:15
keepLearning512 left12:16
leeN joined12:16
keepLearning512 joined12:16
cheater --set-upstream ?12:16
oxymoron93 yes12:16
saltlake cheater: for me?12:19
canton7 joined12:20
oxymoron93 -u is --set-upstream check man git push12:20
gitinfo the git-push manpage is available at https://gitirc.eu/git-push.html12:20
jgoss left12:21
Neo4 left12:23
drbean left12:24
cheater saltlake: yes.12:24
saltlake: next time, look at "man git push" or "git push --help" (same thing)12:25
gitinfo saltlake: the git-push manpage is available at https://gitirc.eu/git-push.html12:25
drbean joined12:25
Binake joined12:26
skisela left12:28
Onionnion joined12:29
TheRuckus joined12:29
justrohu left12:30
ShekharReddy joined12:30
Guest72864sircmpwn12:32
skisela joined12:34
sitaram_ joined12:35
sitaram_ left12:35
sitaram_ joined12:35
pity joined12:36
sitaram_sitaram12:36
skisela left12:36
thiago joined12:40
amirpro left12:40
nurdie joined12:41
theoceaniscool left12:41
pity left12:41
amirpro joined12:42
miklcct_ joined12:46
miklcct left12:46
rotaerk left12:46
amirpro left12:47
amirpro joined12:50
phluks joined12:51
manuelschneid3r left12:53
TMGS joined12:54
theoceaniscool joined12:54
manny_rodriguez joined12:55
manny_rodriguez left12:55
czart__ joined12:56
nurdie left12:57
nurdie joined12:57
Guest21076 left12:58
Guest21076 joined12:59
rfuentess left12:59
Guest21076 left12:59
czart_ left13:00
bitonic joined13:00
Mike11 joined13:00
jgoss joined13:00
bitonic left13:00
bitonic joined13:01
rajkane_prajta left13:01
doev left13:02
widp joined13:02
nurdie left13:02
mud joined13:04
bjsnider joined13:05
Rubin left13:06
rfuentess joined13:07
d1b left13:09
charolastra left13:11
widp left13:13
d1b joined13:14
Kolany joined13:15
quackgyver joined13:15
cheater left13:16
dre_ left13:16
Kolany left13:18
sim590 left13:18
Rubin joined13:19
shinnya joined13:21
pity joined13:23
sim590 joined13:23
mostlybadfly joined13:24
pnepe6 left13:26
smallville7123 left13:26
sim590 left13:29
smallville7123 joined13:29
duderono_ left13:30
duderonomy joined13:30
PioneerAxon_ joined13:30
PioneerAxon left13:30
keepLearning512 left13:31
dimi1947 left13:31
sim590 joined13:34
AndresInSpace joined13:36
AndresInSpace left13:36
AndresInSpace joined13:36
Binake_ joined13:38
ronskisika left13:38
keepLearning512 joined13:39
Steverman joined13:39
Steverman Totally did not expect that13:39
hernan604 joined13:40
Binake left13:40
hernan604 hi!! whats the name of algorithm to create short md5 hash ? (git rev-parse --short)13:40
Es0teric joined13:42
smallville7123 left13:42
mefistofeles joined13:44
Es0teric left13:45
smallville7123 joined13:45
Es0teric joined13:47
igemnace joined13:47
jready joined13:48
TMGS_ joined13:48
TMGS_ left13:50
TMGS_ joined13:50
TMGS left13:50
kneeki joined13:51
TMGS_TMGS13:52
pfleck left13:52
rivalomega joined13:54
ntnn joined13:54
crose joined13:55
cheater joined13:55
robin left13:56
robin joined13:57
rivalomega left13:57
Es0teric left13:57
ocds left13:57
Es0teric joined13:59
ephemera_ left14:00
rsrx left14:00
rafasc hernan604: what's your question really?14:00
git doesn't doesn't use md514:01
camsbury joined14:02
rafasc git currently uses sha1, but there's work in progress to make it hash agnostic.14:02
cr1mson_king joined14:04
relipse joined14:05
Rubin left14:07
dmone left14:08
nurdie joined14:09
Guest31421mawk14:11
AaronMT joined14:11
smallville7123 left14:12
mel00010 left14:13
Steverman Reminds me of the multihash format14:14
venmx left14:16
rafasc nothing will beat emoji based hash.14:16
zulutango left14:16
hernan604 rafasc: right, i mean i see hashes in the form 8d9qu89dqwuy89dqwy89dyq898dqy9w89qwd98 (long) and some shorted ie e89892eu14:17
and they are equivalent14:17
whats the algorithm name that creates the shorter version of the hash ?14:17
i want to search my programming language modules repository for something that generates the shorter version14:18
jedix it's artually the start of the long poart14:18
actually14:18
rafasc hernan604: there's not a name. It's just the prefix of the big one, making sure they're not ambiguous.14:18
keepLearning512 left14:19
hernan604 ok14:19
rafasc also considers a config setting, where you can force a certain number of 'digits' to show.14:20
cramalho left14:22
venmx joined14:22
rafasc hernan604: https://github.com/git/git/blob/e144d126d74f5d2702870ca9423743102eec6fcd/sha1-name.c#L54014:23
Jackneill left14:23
rafasc if you're really interested in the algorithm.14:24
dimi1947 joined14:24
amosbird Hello, why do I get unstaged changes after rebasing ?14:25
dendazen joined14:25
grawity are you sure it's *after* rebasing, and not in the middle of a rebase?14:25
saltlake left14:25
canton7 what does 'git status' say?14:26
thiago_ joined14:26
hernan604 rafasc: oh, great link. thanks!14:27
Nizumzen joined14:27
amosbird grawity: yep14:27
hmm, I have to do git submodule update one by one14:28
thiago left14:28
rafasc hernan604: you'll find that the length actually depends on how many objects your git db has.14:28
chele left14:29
JeroenT left14:29
ashpabb joined14:30
dwmw2dwmw2_gone14:30
thiago_thiago14:30
oxymoron93 left14:31
ToBeFree joined14:32
ToBeFree left14:32
ToBeFree joined14:32
gitinfo set mode: +v14:32
veegee joined14:32
surfist left14:33
cramalho joined14:33
Neo4 joined14:34
surfist joined14:35
ToBeFree left14:35
ashpabb left14:36
Rubin joined14:36
jstimm joined14:39
bitttalkme98 joined14:41
Nizumzen left14:41
jamiejackson joined14:42
jhaenche_ left14:42
Mike11 left14:42
raffo left14:43
olaf_ why does git am fail to handle different line endings,while patch(1) does them just fine?!14:43
jhaenchen joined14:43
inovas left14:43
navidr joined14:43
igemnace left14:44
olaf_ looks like .git/rebase-apply/patch gets converted from correct to wrong ending.14:44
MaliusArth left14:44
bitttalkme98 left14:44
Es0teric left14:44
sitaram left14:45
sleepingforest joined14:46
jhaenchen left14:48
inovas joined14:49
phluks left14:49
pionen joined14:50
thiago left14:50
_ADN_ left14:50
thiago joined14:51
jhaenchen joined14:53
camsbury left14:54
abba left14:55
thiago left14:56
amirpro left14:57
amirpro joined14:57
Onionnion left14:58
phinxy left14:58
beefjoe70 joined14:59
afuentes left15:00
ShekharReddy left15:00
camsbury joined15:00
thiago joined15:01
amirpro left15:01
nurdie left15:01
phinxy joined15:02
amirpro joined15:02
Cavallari left15:03
jhaenchen left15:03
LionsMane joined15:05
dmarr left15:05
AndresInSpace left15:06
mightywomble left15:07
crtcji left15:07
PsychoBoB joined15:08
fstd_ joined15:08
JimmyRcom_ joined15:08
jhaenchen joined15:09
Es0teric joined15:09
XenophonF left15:10
pity left15:10
XenophonF joined15:10
XenophonF left15:11
fstd left15:11
fstd_fstd15:11
XenophonF joined15:12
XenophonF left15:12
PsychoBoB left15:12
XenophonF joined15:14
PioneerAxon joined15:15
PioneerAxon_ left15:15
keepLearning512 joined15:16
cagomez joined15:16
riemann left15:17
rafasc left15:18
al-damiri joined15:18
rafasc joined15:18
cramalho left15:18
keepLearning512 left15:20
AndresInSpace joined15:20
ocds joined15:21
cramalho joined15:23
cagomez left15:25
minionofgozer left15:26
jimi_sanchez left15:29
plexigras left15:30
Gurkenglas joined15:30
rivalomega joined15:30
plexigras joined15:31
rivalomega left15:33
rivalomega joined15:33
dege joined15:33
scorpionillumin joined15:36
scorpionillumin a little help please15:36
_ikke_ !just_ask15:37
gitinfo You can just ask your question. If anybody knows the answer, they will answer soon (most of the time)15:37
palmtree joined15:37
pionen left15:37
scorpionillumin https://bitbucket.org/snippets/scorpionilluminati/aej7py it's not working, the files with those extensions aren't being ignored ex bin/emu/rom.bin15:38
cjohnson gitignore has no effect on files that are already checked in15:39
akushner joined15:40
akushner left15:40
rafasc !ignore_tracked15:40
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.15:40
scorpionillumin i commited .gitignore and then rebuilt my rom, so it should of started ignoring or should i have to commit those files atleast once?15:40
akushner joined15:41
rafasc you actually need to tell git to stop tracking those files.15:41
rivalomega left15:42
rafasc you need to $git rm the files (use --cached if you want to remove from the repo but keep an untracked copy in your directory). Then commit the removal of those files.15:44
only then git will start ignoring.15:45
committing the .gitignore is optional.15:45
leeN left15:45
l3dx left15:48
eduardas_m left15:49
wreed joined15:51
nurdie joined15:55
Praxi joined15:57
skered If a tag is removed from the remote repo and I git pull the tag isn't removed. git pull will auto add tags but it doesn't auto remove them?15:58
rafasc skered: yes. This is by design.15:59
dianni left15:59
skered So at that point you need to 'git tag -d ... ' to remove it?16:00
There not 'git pull --something ...' to keep tags in sync?16:00
There's*16:00
rafasc the point is that a remote should not delete tags after they are set.16:00
skered Fair enough. I think that's going to be case once we start using them.16:01
But it was something I noticed while testing.16:01
mosab left16:01
theoceaniscool left16:01
rafasc one of the mais uses of tags, are declaring versions.16:02
it's a bit silly if a remote could "redeclare" what vX.X is.16:02
rivalomega joined16:02
jamiejackson left16:03
rafasc So, by default, git keeps the tags alone and leaves it up to the user how to proceed from there.16:03
skered We're using it for non-versioning.16:04
rafasc The version is just an example, but the concept applies to non-version tags.16:04
skered If a special even happens we want to record that some how that isn't a commit16:04
howdoi left16:04
rafasc a tag is a immutable reference to a commit. Allowing the deletion would weaken this concept.16:04
skered It's possible that special event can be reverted but most likely it won't. I think I have enough road blocks that if you're tagging you mean it.16:05
durham joined16:06
cjohnson skered: You would follow that up with a followup tag16:06
which is the revert16:06
BTW revert works this way too16:07
it does not rewrite history but introduces a negative commit16:07
This is intentional :)16:07
skered This is all internal and the user base is small. Plus gitlab sends emails on tag adds and removes so it's all recorded some whewre.16:07
Naq joined16:07
Naq left16:07
rafasc you could ask your users to $git fetch origin +refs/tags/*:refs/tags/*16:08
Es0teric left16:08
rafasc but there's no way to force it on users.16:08
skered Yeah, we're small enough to the point someone could just yell (or email) and it's all good.16:09
rafasc it's the users' responsibility to manage the tags.16:09
skered cjohnson: That was another idea I was thinking about too. A follow up tag to invalid tags.16:09
rafasc but ideally you would avoid that.16:09
I think in skered's usecase a namespaced branch would fit better.16:10
instead of using tags, use branches with some naming convention like events/name;16:10
skered That's not a bad idea too.16:11
beefjoe70 left16:11
skered And it might make it easier to see the tree at that point too.16:12
durham left16:12
rafasc not really any easier..16:12
durham joined16:12
floppydh left16:13
lagothri1 left16:15
dimi1947 left16:16
durham left16:17
rfuentess left16:17
energizer joined16:17
TMGS left16:18
jungsubk joined16:18
rafasc skered: even if you come up with a system to "invalidate" with another tag. You're still relying on the user respect it.16:18
crtcji joined16:19
rafasc So it's not that different than asking them to delete their local tag, and fetching the new one.16:19
aciidic__ left16:20
rivalomega left16:20
rivalomega joined16:20
Guest32965 left16:21
lagothrix joined16:23
Es0teric joined16:24
tipyn joined16:26
TheRuckus left16:27
m00sehead left16:27
TheRuckus joined16:29
durham joined16:30
durham left16:30
Onionnion joined16:33
madewokherd left16:34
King_Hual joined16:34
King_Hual left16:34
King_Hual joined16:34
TMGS joined16:35
durham joined16:35
shady_traveller left16:35
rts-sander left16:36
palmtree left16:37
skered Thanks for the input.16:38
DaGoaty joined16:38
Binake_ left16:40
dimi1947 joined16:41
amirpro_ joined16:42
chaosruler joined16:42
amirpro_ left16:43
Neo4 left16:43
tarkus joined16:44
amirpro left16:44
rafasc left16:45
amirpro joined16:45
rafasc joined16:45
smallville7123 joined16:46
qgTG left16:48
qgTG joined16:49
raynold joined16:51
jstimm left16:51
\void joined16:52
dandes joined16:53
PsychoBoB joined16:54
dbear joined16:55
tipyn left16:56
dbear Wondering if there are any high school level teachers using git as a way to track student progress on coding projects?16:56
jready left16:56
Mattiaslndstrm joined16:57
nitric joined16:58
YuGiOhJCJ joined16:58
rsrx joined16:59
AndresInSpace dbear: probably17:00
TheRuckus left17:03
KaitoDaumoto joined17:04
King_Hual left17:05
shinnya left17:06
thinkpad left17:06
King_Hual joined17:06
King_Hual left17:06
King_Hual joined17:06
thinkpad joined17:07
Whiskey left17:07
iNCoNFuN joined17:09
jrnieder left17:10
King_Hual left17:11
relipse left17:11
jready joined17:12
dbear AndresInSpace: thats a good response, then at least I wouldn't be the first to have the idea.. I was just hoping there was a teaching hanging around that could comment on best practices around setting up the repositories..17:13
I was thinking I would have 1 repo per student, then all the coding projects would belong to the one repo17:13
venmx left17:14
flippedouttt question: gitlab or phabricator17:14
for a local install17:14
well, self-hosted install17:14
_ikke_ Haven't used both, so cannot tell17:14
flippedouttt used either?17:14
_ikke_ gitlab likes memory though17:14
I used gitlab, but no experience setting it up / maintaining it17:15
flippedouttt yeah it says min 4gb memory17:15
_ikke_ I hear you even want 8gb min17:15
flippedouttt im leaning towards phab17:15
dreiss joined17:15
_ikke_ gitlab is nice though17:15
but cannot tell you how it compares to phabricator17:15
flippedouttt phab is pretty neat17:16
ChanServ set mode: +o17:17
Zarthus depends on what you need, really17:18
both of them are nice, both of them have demos17:18
Es0teric left17:18
Eugene changed the topic to: Welcome to #git, the place for gitting your ducks in a row | First visit? Read: https://gitirc.eu | Current stable version: 2.17.0 | Getting "cannot send to channel"? /msg gitinfo .voice | https://photos.app.goo.gl/Dwp1yX8rEvsnK6Gf117:18
Eugene set mode: -o17:19
Eugene Duck feedback welcomed17:19
Zarthus for personal projects? gitolite+trello works fine17:19
mda1 left17:19
jnavila joined17:20
TheRuckus joined17:21
Es0teric joined17:22
bambams joined17:22
rafasc in uni we set up a redmine server for students.17:22
but that was before we got all these alternatives.17:22
sjoshi joined17:23
mda1 joined17:23
mostlybadfly left17:24
nachoman joined17:25
jessica523 joined17:25
nuc left17:26
TheRuckus left17:26
Whiskey joined17:26
jstimm joined17:26
Mattiaslndstrm left17:27
beefjoe joined17:27
nuc joined17:27
j416 dbear: github?17:29
TheRuckus joined17:30
akushner_ joined17:30
nachoman left17:30
dbear Looked at github -- they want money for private repos.. Gitlab gives me private repos that I don't have to pay for .. and its all 'git' ..17:31
j416 why not public?17:31
Puffball joined17:31
dbear j416: I didn't want a student project thats is a 'practice programming assignment' becoming .. something that is published .17:32
j416 interesting. Why not?17:32
Es0teric left17:32
dbear sometimes students may do things that we don't want to become 'representative' of the school17:32
j416 why not have them put it on their own account?17:33
dbear we wanted to leverage school SSO, so we have them use the school managed google account17:33
I think there are cipa implications here17:33
sanscoeur joined17:33
akushner left17:33
dbear to comply with law, we have to be able to revoke account access.17:34
j416 doubt that covers their private github accounts.. does it17:34
wreed left17:34
j416 anyway, it's just an idea.17:34
rafasc bitbucket?17:36
mostlybadfly joined17:36
Master__ left17:36
nitric_ joined17:36
_ikke_ bitbucket only allows for 5 collaborators for private repos17:37
nitric left17:37
rafasc 5 students per group is kinda of ok for highschool.17:38
jimi_ joined17:38
sjoshi left17:38
sjoshi joined17:39
King_Hual joined17:40
King_Hual left17:40
King_Hual joined17:40
AndresInSpace dbear: from what i've heard, the tell students to make their own github account, make their own repo for each project17:41
guess it depends on the professor17:41
sanscoeur I have curious question about git history. ... If I created a new repo using the latest version of git, are there older versions of the git client that would be incompatible?17:42
Eugene GitHub has a whole thing for Education https://education.github.com/17:42
sanscoeur - yes, but they'd have to be /really old/17:43
sanscoeur I've read a bit of the technical documentation, so I know that some of the binary formats have changed. (https://github.com/git/git/tree/master/Documentation/technical)17:43
Es0teric joined17:43
Mattiaslndstrm joined17:43
getSomethingGood joined17:43
quackgyver left17:43
Eugene The git protocol is going through some updates, and a bunch of work is being done for the future hash-change away from SHA1, but right now everything will "just work" and you don't need to worry about it.17:43
All the changes are/will be forward-compatible; anything you find that isn't compatible means that you're using an antique `git` binary. Don't do that. ;-)17:44
ali1234 what hash is replacing sha1?17:45
Eugene https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt17:45
sanscoeur Eugene: Any idea how old? I have some Jenkins build nodes running CentOS6. They have git 1.5-1.7 (somewhere in there, don't have access atm) and they work fine. Pretty impresive.17:45
Eugene sanscoeur - pre-1.017:45
preyalone joined17:46
Eugene You'll find some user-facing functions missing from git in CentOS5; anything older than that is... old.17:46
ali1234 tl;dr not decided yet17:46
Eugene ali1234 - indeed. The work is currently focussed on 'oh god we have a 32-character hash hardcoded everywhere'17:46
ali1234 fair enough17:47
Eugene !sha117:47
gitinfo git uses a variant of the SHA1 cryptographic hash algorithm to ensure object integrity. Git v2.13.0 added hardening to the SHA-1 implementation to mitigate SHAttered; work towards a NewHash is underway: https://git.io/vpIMJ | Please note that purposeful SHA1 collisions are computationally expensive, and accidental encounters are more likely with wolves. https://en.wikipedia.org/wiki/Wolf_attacks_on_humans Fear their howl.17:47
Eugene Relevant wikipedia ^17:47
rafasc dbear: since git is pretty much distributed, you can even let them have local repos on their machines. And syncronize over the local network on class.17:48
sanscoeur Very cool. Thanks. ... I have a fascination with VCS and how they store version history. I've looked at CVS and SVN in the past. I just started looking at Mercurial which has a '.hg/requires' (https://www.mercurial-scm.org/wiki/RequiresFile) which dictates necessary client features.17:48
preyalone left17:48
sanscoeur (So, they've had to make backwards incompatible changes.)17:48
rivalomega left17:48
_ikke_ git so far hasn't17:48
preyalone joined17:49
_ikke_ at least, not since a long time17:49
dbear rafasc: exactly17:49
the workflow I had in mind is that after each class they would git commit and git push17:49
then each day I could run some git stats on each of the gitlab repos to see how much code they produced..17:50
ShapeShifter499 left17:50
sanscoeur To my understanding. If every git repo in existence was combined, it would be highly unlikely for there to be any object-hash collisions.17:50
j416 dbear: why not encourage clean and logical commits instead of doing one commit per day?17:50
_ikke_ I agree with j41617:51
dbear j416: good thought.. trouble is I have only so much time in class in a semester17:51
AndresInSpace you do not want one commit per day with everything piled into it17:51
jnavila left17:51
AndresInSpace that is just asking for trouble17:51
getSomethingGood left17:51
_ikke_ I'm trying to force myself to commit early17:51
dbear I could spend more time teaching good git practices -- or time teaching data structures and algorithms17:51
getSomethingGood joined17:52
dbear I a poor git user myself... so ..17:52
preyalone left17:52
AndresInSpace I commit per 'task'/'fix'17:52
_ikke_ That should be pretty explainable17:52
preyalone joined17:53
Salek left17:54
j416 dbear: if you're letting loose a class of people who have not used version control before, you might want to make sure you have a solid enough understanding in order to be able to quickly get them out of tricky situations, that will occur17:54
ali1234 sanscoeur: it's so much more unlikely than that17:54
King_Hual left17:54
j416 dbear: but, perhaps that goes without saying.17:54
NinjaBruxo left17:55
uve joined17:55
uve Hey folks17:55
gitinfo uve: 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.17:55
Eugene sanscoeur - there has been exactly one (publicly known) SHA1 hash collision to be created, ever. A change to the hash function which mitigates this attack(ie, produces a different hash) has already been merged to git. Additionally, git uses not-quite-sha1 to begin with(appends a length) to prevent most theoretical attacks to begin with. Insert "grains of sand" comparison here.17:56
sanscoeur ali1234: Can you quantify it? I've tried to in the past. Even used Google BigQuery's Github data to prove it to myself.17:56
rivalomega joined17:56
M6HZ joined17:56
manuelschneid3r joined17:56
ali1234 sanscoeur: it's so unlikely that it is difficult to quantify17:57
sanscoeur Eugene: Interesting. Somehow, I've missed that SHA1+length detail.17:57
uve I want to join a kind of open source project... Need help.17:57
ShapeShifter499 joined17:57
_ikke_ sanscoeur: http://www.wolframalpha.com/input/?i=number+of+combinations+in+sha117:57
amirpro left17:57
dbear j416: I understand the basics of git and version control. but I have no real world experience of working on coding projects with other groups of people in git -- so I know where I have messed up.. and I know where I have had students in the past mess up (we used it last year for a class project, one repository for the class) But I don't know what I don't know -- and I would prefer to learn from other teachers using git as a means of trackin17:57
amirpro joined17:58
dbear yes, it would be great to teach good git practice to start with ... but I'm too isolated as a high school teacher to know what good 'industry' practices are in place17:59
sanscoeur _ikke_: Nice. That's an awesome use of wolframalpha. I'm going to have to show that off now. ... I would guesstimate that even with all the rebasing and squashing, the entire world has made somewhere in the billions of git objects (possibly, low trillions), so we have a ways to go.17:59
dbear my most immediate concern is to be able to spot students not producing code as a means of identifying those who may need more help than they ask for17:59
sanscoeur Although, there is the birthday problem. Which I did just well enough with statistics to pass the course. I've forgotten how the calculation works.18:00
ali1234 you need 1 * 10^23 commits for a 1% chance of collision with 160 bits18:00
accidental collision that is18:00
j416 dbear: tricky18:00
dbear j416: yes -- students are sometimes not forthcoming about being completely lost..18:01
ali1234 that's 100 billion trillion commits18:01
j416 dbear: is gaining such experience possible? work on an open source project, for instance18:01
Frogging101 left18:01
j416 dbear: indeed; that sounds like an issue18:01
dbear: I'm not sure git alone will solve that problem18:02
preyalone left18:02
jgoss left18:02
j416 dbear: how many students are in your class?18:02
dbear j416: it varies over the years.. cap is 20. low count is 10 .. and yes, git alone won't solve it..18:03
phluks joined18:03
j416 ah, that few18:03
preyalone joined18:03
j416 I'd at least go with one repo per student18:04
sanscoeur shatterd.io calculated they would need 2^63.1 computations (https://shattered.io/static/shattered.pdf) ... I skimmed the paper, I suspect that's for a targeted attack.18:06
ali1234 yes, attacks are different. they reduce the work you need to do to find collisions18:06
sanscoeur ali1234: Nice. Even with that relatively "smaller" number, that's still a lot of hashes.18:07
geoklown joined18:07
sleepingforest left18:08
ali1234 also note that finding two blobs with the same sha1 is a different and easier problem than finding a blob with the same sha1 as some existing blob18:08
the former can't be used to attack git history18:08
_ikke_ and note that this specific attack does not really affect git (because there is a header prepended to each object)18:09
cfoch joined18:09
tipyn joined18:09
sjoshi left18:10
Frogging101 joined18:12
KaitoDaumoto left18:13
ShapeShifter499 left18:13
scorpionillumin how do i rm --cached if the file has a space in it(ex. rom .lst)?18:14
ShapeShifter499 joined18:14
keepLearning512 joined18:15
_ikke_ git rm --cached 'file with spaces'?18:15
cjohnson Or file\ with\ spaces18:16
though that's really more of a shell question18:16
scorpionillumin actually my assembler is doing that which is weird, but no one knows why18:16
ali1234 or file<tab>18:17
_ikke_ cjohnson: correct18:17
ali1234 let the shell figure it out18:17
cjohnson ^18:18
mel00010 joined18:18
scorpionillumin what if the shell is git?18:18
ali1234 git has an interactive mode?18:19
scorpionillumin git bash18:19
DaGoaty left18:19
scorpionillumin thats litterly what it's called18:19
ali1234 not a command here18:19
Eugene git bash is not git. It is bash included with Git for Windows18:19
Karyon joined18:20
ali1234 well in that case, it should have tab completion18:20
jready left18:20
Eugene Git for Windows includes a bunch of UNIX-sourced tools built for Windows. They are not git subcommands either.18:20
scorpionillumin why can't you flat out just use git without bash?18:20
Eugene You can use git.exe just fine in cmd or Powershell, if your PATH includes the git bin directory18:20
ali1234 you can, it's just not very nice18:20
jready joined18:21
scorpionillumin ah ok then18:21
jnavila joined18:21
Eugene bash.exe is provided with a handy shortcut that sets up the UNIX-like environment, so that existing git users will feel a bit at-home. If you're a Windows-centric guy (my company is), just add it to your PATH and use PoSH. ;-)18:22
sanscoeur left18:22
Ademan-work joined18:22
sanscoeur joined18:22
Eugene People seem to forget that Windows makes huge strides for POSIX compatibility... you can even run a NFS client on Windows18:22
Its not that good, but you can18:22
The original Windows netcode subsystem was lifted from BSD. Its been rewritten almost entirely, but that's where it came from18:23
Active Directory's DNS service? Originally forked from BIND18:24
ferdna joined18:24
ali1234 windows used to have an NFS client built in, then they removed it18:24
Mike11 joined18:24
Ademan-work left18:25
sauvin left18:25
Ademan-remote joined18:25
Ademan-remote I just accidentally clobbered an un-annotated tag with a `git fetch --tags`. it was the sole pointer to a bit of history I wanted to keep, is my best bet to go through `git fsck --unreachable` looking for the object it pointed to?18:25
Eugene No they didn't? Its gated behind Pro/Enterprise license18:25
Ademan-remote - git reflog should work on tags IIRC?18:25
Or scroll up in your console and copy-paste the object ID18:25
ali1234 oh they put it back?18:26
sanscoeur left18:26
Eugene It never left18:27
wandering_vagran left18:27
crtcji left18:27
Eugene Its not enabled by default and not available on home SKUs, but it is there and I am actively using it on Windows 1018:27
ali1234 i thought they removed it in vista18:28
Eugene Home SKU ;-)18:28
ali1234 good point18:28
Eugene Actualy, Vista, it may have been gated behind Enterprise (not Pro). I don't remember Vista very well18:29
dviola joined18:29
jnavila left18:30
ali1234 oh i see what happened18:30
the NFS client used to be available in the SFU package, so you could install it on anything pretty much18:30
Salek joined18:31
ali1234 when SFU was replaced by SUA the NFS client was split out and made server-only18:31
Eugene Only in terms of the install package. The subsystem hasn't changed.18:31
ali1234 sure18:31
re1 joined18:31
akushner_ left18:31
ali1234 i was just misremembering18:32
Eugene Very common in IT. S'ok, we all accidentally hate on Microsoft. Its like an IRC hobby.18:32
fr33domlover joined18:32
Eugene I'm currently pissed off at them because my home Print server ate its bootloader. Again.18:33
rsrx left18:34
akushner joined18:34
justanotheruser left18:36
relipse joined18:39
manuelschneid3r left18:39
Radierg joined18:41
gitinfo set mode: +v18:41
dpyro joined18:42
beefjoe left18:42
Radierg I am doing a cherry-pick and while fixing conflicts, git status shows the status "deleted by us" for some files. What does it mean?18:43
D630 joined18:43
Es0teric left18:45
al-damiri left18:46
ilogger2 joined18:47
jimmyrcom joined18:48
Mattiasl_ joined18:50
ilogger2 joined18:53
Ram-Z joined18:53
Mattiaslndstrm joined18:56
dreiss joined18:58
Es0teric joined18:59
dendazen joined19:01
Mattiaslndstrm left19:02
tipyn joined19:02
jnavila joined19:02
Mattiaslndstrm joined19:03
mad_hatter joined19:03
akushner joined19:04
Mattiasl_ joined19:05
dreiss left19:06
Mattiaslndstrm left19:07
Mattiaslndstrm joined19:10
muelleme joined19:10
in1t3r joined19:11
duderonomy joined19:11
Mattiasl_ left19:12
mel00010 joined19:13
thblt Why do git tag objects have a =tag= field with the tag name? It seems git uses the name of the file in refs/tags anyway19:13
... and cannot even refer to a tag by the name in that field in the file in refs has been renamed19:15
muelleme left19:15
dreiss joined19:16
goodafternoon joined19:18
shinnya joined19:28
mel00010 left19:28
Hello71 joined19:28
justanotheruser joined19:29
jnavila left19:29
akushner left19:30
henharm joined19:31
mario_ joined19:33
akushner joined19:35
joeco joined19:35
tombusby joined19:39
jimi_ joined19:40
KeyJoo joined19:40
jenia joined19:41
jenia hello19:41
are there many people using master-only git?19:42
Seveas What do you mean with master-only?19:42
mel00010 joined19:42
jenia a bracnhing strategy that uses master only19:43
Seveas that's not uncommon, especially for smaller projects19:44
ali1234 i prefer to only do fast forward merges19:44
i think that's what you're talking about right?19:44
jenia ali1234, no I mean everyone uses master branch19:45
freimatz joined19:45
rafasc dbear: j416 made a very good point. If you're not savy enough with git to untangle the mess your students will eventually make, or at least explain to them what they did wrong... I think you might end up making things worse. Because they will either get the impression that git is hard and the benefits are not worth the problems you have to deal with.19:45
ali1234 master is just a name for a branch tho19:45
everyone who has a copy of the repo has their own master branch19:45
joeco left19:46
rafasc ali1234: fairly common. People still branch locally to develop features though.19:46
sim590 joined19:47
durham_ joined19:49
jnavila joined19:51
manuelschneid3r joined19:51
henharm left19:52
durham_ left19:54
wreed joined19:56
shinnya left19:57
jimi_ left19:59
dendazen left20:02
manuelschneid3r left20:03
jenia left20:03
Mattiaslndstrm left20:04
Es0teric left20:04
uptime joined20:06
ivs joined20:07
thiago joined20:08
tipyn_ joined20:08
tipyn left20:08
tipyn_ left20:09
manuelschneid3r joined20:10
muelleme joined20:12
Mattiaslndstrm joined20:12
muelleme left20:16
ivs left20:17
camsbury joined20:22
Neo4 joined20:23
goodafternoon left20:23
Es0teric joined20:24
camsbury left20:27
manuelschneid3r left20:29
nd joined20:31
Mattiaslndstrm left20:31
fdnick joined20:34
Cthalupa- joined20:35
fdnick hi all, i have a project that uses two files of data that are in total about 300 MB. I desided to stage them and git got very slow. Now i wonder if i should commit them or if it's better to don't use version control on them. Any advice?20:37
Cthalupa- left20:39
rafasc fdnick: is this 300MB file binary?20:39
Cthalupa joined20:39
rafasc or is something like a txt database dump20:39
fdnick its a csv20:40
just text20:41
akushner left20:41
fdnick will it stay that slow if i commit and push them, or is it just that slow if it's staged but not yet commited?20:42
rafasc Usually I don't notice slowdowns..20:42
freimatz left20:42
fdnick i guess i just commit then and hope the best!?20:43
rafasc problem with big files, is that each time is changed, git effectively creates a new copy of the file.20:43
!balloon20:43
gitinfo [!binary] Storing binary files in git causes repo balloon, because they do not compress/diff well. In other words, each time you change a file the repo will grow by the size of the file. See !annex for some solutions20:43
rafasc but in your case it's text, so it will probably be resolved once $git gc is triggered.20:44
I would say if you can get away with not putting this db under version control, go with that.20:45
madewokherd joined20:45
fdnick hmm, it would make my life easier to commit them though. It's an online repo, and other people use it too. Another point is that those data files are updated weekly20:46
Mattiaslndstrm joined20:47
rafasc you probably can get away with committing it then.20:47
mario_ left20:48
sanscoeur joined20:49
rafasc the question you need to ask is how much this file changes per week.20:52
and do you really need its history baked in the repo forever.20:53
jnavila left20:56
lafleurdubien joined20:57
linuxmodder joined20:59
max3 joined21:00
sanscoeur left21:03
mikhael_k33hl joined21:03
sanscoeur joined21:03
banisterfiend joined21:04
jrnieder joined21:04
fdnick rafasc: it gets extended by about 10000 lines every week21:04
DaGoaty joined21:04
mikhael_k33hl How do I revert something I committed/pushed to a repository?21:06
relipse joined21:06
akushner joined21:06
rafasc mikhael_k33hl: you can either revert the commits you added. This creates a new commit that undoes what you did.21:07
or you need to !rewrite21:07
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/waqum21:07
rafasc !revert21:07
gitinfo That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?21:07
rafasc gitinfo: you explain it better than me !botsnack21:08
gitinfo gitinfo: Om nom nom21:08
fdnick rafasc: thx for the information21:08
fdnick left21:08
mikhael_k33hl so I have to do a git revert21:08
rafasc: So the commit ID before the latest commit should be the parent right?21:09
banisterfiend left21:10
_ikke_ mikhael_k33hl: that sounds tautological21:10
rafasc no. Git revert doesn't revert your repo up to a point.21:10
it reverts the commits you pass to it.21:10
_ikke_ with reverting meaning creating a new commit that is the reverse of the commit being reverted21:11
ZyX-I joined21:11
mikhael_k33hl so I have to manually undo all the changes?21:11
rafasc you can dom something like git revert A..B;21:12
dysfigured joined21:12
rafasc and that will revert all commits in that range. (will create one revert commit per commit reverted)21:12
or git revert --no-commit A..B; if you want just one.21:12
dbear joined21:15
Mattiaslndstrm left21:16
texinwien_ joined21:18
dbear1 joined21:18
porterodoran joined21:18
porterodoran left21:19
dbear1 left21:19
dbear left21:20
dbear joined21:23
Es0teric left21:25
mikhael_k33hl rafasc: I'm sorry but A..B? A being the commit id right?21:25
rafasc !dots21:26
gitinfo A..B = stuff that happened between A and B (if A and B are related; otherwise refer to "man gitrevisions"), A...B = (a) in history viewers: stuff that isn't in both A and B yet; (b) in "git diff": stuff that happened in B since the two diverged; (c) in "git checkout": the merge base of A and B. "master.." is the same as "master..HEAD" and "..master" is the same as "HEAD..master", and so forth.21:26
rafasc mikhael_k33hl: both A and B are commit ids.21:26
it's notation for specifying a range of commits.21:27
mikhael_k33hl but I just want to revert the latest commit21:27
Blkt joined21:27
marlinc joined21:27
dbear left21:28
rafasc then yes, git revert <hash of last commit>;21:28
git revert HEAD; would be an equivalent.21:28
btree joined21:29
TheRuckus joined21:30
dbear joined21:31
m00sehead joined21:32
btree left21:32
pbrewczynski_ joined21:39
sz0 joined21:40
jhaenchen joined21:43
nurdie joined21:44
mikhael_k33hl left21:46
jstimm joined21:46
jhaenchen left21:47
nurdie left21:48
tarkus joined21:50
agowa338 joined21:54
UTAN_dev_ joined21:57
wootehfoot joined21:57
m00sehead left21:58
dendazen joined21:59
akushner left21:59
guide joined22:00
akushner joined22:01
mikemcowie joined22:02
Mattiaslndstrm joined22:03
jstimm left22:07
banisterfiend joined22:10
Karyon joined22:11
paraxial joined22:13
m00sehead joined22:15
esc joined22:20
al-damiri joined22:20
banisterfiend left22:20
venmx joined22:20
SleePy joined22:22
Karyon left22:28
meLon joined22:29
nurdie joined22:29
meLon left22:29
meLon joined22:29
jstimm joined22:32
dbear left22:32
meLon left22:33
wootehfoot left22:35
jimi_ joined22:37
sanscoeur I wasn't aware of `git checkout A..B`. I'll be using that now. :)22:37
Does three dots A...B change any of these other, not log based, semantics? Does `git checkout A...B` still checkout the merge-base?22:38
I guess that's the only "other" scenario, so I'll just try it.22:39
venmx left22:39
meLon joined22:40
jmux joined22:40
meLon left22:41
meLon joined22:41
netlar joined22:41
jimi_ left22:42
sanscoeur facepalm. They answer is right there in the comment. I just wasn't reading closely enough. `git checkout A..B` (two dots) doesn't work at all. `git checkout A...B` (three dots) is correct.22:43
dre_ joined22:43
relipse left22:44
tomfarr joined22:46
m00sehead left22:48
dreiss left22:48
Karyon joined22:50
meLon left22:51
meLon joined22:51
Mattiaslndstrm left22:51
Mattiaslndstrm joined22:52
Mattiaslndstrm left22:54
m00sehead joined22:57
goodafternoon joined22:58
durham joined23:00
durham left23:01
durham joined23:01
alfioemanuele joined23:03
m00sehead left23:04
mel00010 left23:05
karstensrage joined23:09
linuxmodder left23:09
durham left23:09
d3r3k joined23:10
zulutango joined23:11
armin joined23:11
durham joined23:12
orbyt_ joined23:12
ZyX-I left23:13
_ikke_ joined23:16
durham left23:17
Karyon left23:18
ferdna joined23:19
gusnan joined23:23
rafasc sanscoeur: git revert A..B should work.23:23
dreiss joined23:25
nurdie left23:25
rafasc the .. vs ... seeing this image can be helpfull: https://stackoverflow.com/a/24186641/240813023:25
nurdie joined23:26
rafasc sanscoeur: git checkout A...B doesn't make sense, because this denotes a range and you can't checkout multiple commits23:26
sanscoeur I prefer `man gitrevisions` (or `git help revisions`) over SO.23:28
gitinfo the gitrevisions manpage is available at https://gitirc.eu/gitrevisions.html23:28
sanscoeur It only checks out the common ancestor.23:28
rafasc but you seem to be right.23:28
gusnan Is there a simple way to get a list of branch names only separated by a space? I need this for a bash script.23:29
nurdie left23:30
gusnan Something like "git branch", but only on one line, and without the "current branch" marker.23:30
wreed left23:30
sanscoeur I hadn't thought too hard about it until you said it didn't. (Just took it as a fact/quirk) It does make sense because `A..B` only considers commits in B, not in A. `B..A` is the opposite, commits in A, not in B. And, `A...B` is all commits not in A and B. So, the only way git will find the merge-base is with `A...B`.23:31
dreiss left23:31
jmux left23:31
rafasc sanscoeur: I'm not sure if git checkout A..B is defined behaviour.23:32
sanscoeur It's not.23:32
I tested both.23:32
rafasc sanscoeur: does $git checkout deadbeef cafebabe; makes sense to you?23:33
sanscoeur I'm not sure where you're going with this, but that would try to checkout a file 'cafebabe' from the ref 'deadbeef'.23:34
rafasc As a special case, you may use "A...B" as a shortcut for the merge base.23:35
ok, ... is defined as a special case.23:35
I was just getting confused because I never came across checkout A...B23:36
I usually would just git checkout $(git merge-base A B);23:36
I was going to argue that checkout should not work with ranged revisions.23:37
sanscoeur same. I just found out about this use case from the gitinfo bot.23:37
rafasc yo gitinfo !dots23:38
gitinfo A..B = stuff that happened between A and B (if A and B are related; otherwise refer to "man gitrevisions"), A...B = (a) in history viewers: stuff that isn't in both A and B yet; (b) in "git diff": stuff that happened in B since the two diverged; (c) in "git checkout": the merge base of A and B. "master.." is the same as "master..HEAD" and "..master" is the same as "HEAD..master", and so forth.23:38
sanscoeur gusnan: the best I can come up with is `git branch --format="%(refname:short)"` I can't find anything that gets it to a single line so `echo $(git branch --format="%(refname:short)")` will do the trick.23:38
_ikke_ left23:39
sourcream joined23:40
gusnan sanscoeur: thanks! actually I found that I could use tr -d '\n' to remove the newline, so that will work fine. thanks again!23:40
sanscoeur np.23:40
orbyt_ left23:40
rafasc git for-each-ref refs/heads --format='%(refname:lstrip=2)'23:41
but same issue, line based instead of spaces.23:41
gusnan: sanscoeur command will break if you're on a detached head.23:43
cause it will contain an entry saying: (HEAD detached at 5284b7d)23:43
which contains spaces.23:43
sanscoeur Nice catech.23:44
gusnan ahh, thanks23:44
rafasc sanscoeur: thanks for bringing the ... to my attention. I've use the gitinfo a couple of times, I guess I never paid enough attention to it.23:44
gitinfo rafasc: you're welcome, but please note that I'm a bot. I'm not programmed to care.23:44
rafasc you seem to care when I give you !cake23:45
gitinfo [!botsnack] Om nom nom23:45
rafasc silly bot23:45
_ikke_ joined23:46
Lyqyd joined23:46
duderonomy left23:47
texinwien_ left23:48
texinwien_ joined23:49
akushner left23:56
lafleurdubien left23:57
jimi_ joined23:58
jimi_ left23:59

Logs Search ←Prev date Next date→ Channels Documentation