IRCloggy #git 2016-04-26

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.

2016-04-26

aspiers_ joined00:00
imachuchu left00:00
raijin left00:00
MattMaker left00:01
_wwwBukoLaycom left00:03
madewokherd joined00:03
ToBeCloud left00:03
mustmodify not...00:05
kasisnu left00:07
aspiers_ left00:07
foul_owl Thank you00:07
kasisnu joined00:08
kasisnu_ joined00:09
timvisher left00:09
gitinfo set mode: +v00:10
timvisher joined00:10
kasisnu__ joined00:10
kasisn___ joined00:12
kasisnu left00:12
kasisnu joined00:13
kasisnu_ left00:14
kasisnu__ left00:14
abyx left00:15
kasisnu_ joined00:15
sangy Hello everyone. I have a theoretical question: If you have a merge without conflicts, can you assume that all blobs in the resulting tree must either be in the tree of branch A or in the tree of branch B? That is, could new blobs be created by an automatic merge?00:15
fuchstronaut joined00:15
ojacobson Yes, non-conflicting merges can generate novel blobs.00:16
neonKow joined00:16
kasisn___ left00:17
zZap-X joined00:17
kasisnu left00:17
zZap-X git init00:17
git status00:17
git add .00:18
jimi_ joined00:18
zZap-X git commit -m "I'm learning GIT"00:18
sangy ojacobson: that's what I tought, do you know where I can find an example?00:18
akushner left00:18
sangy zZap-X: ?00:18
zZap-X :D00:18
Boniche joined00:18
tvw left00:19
cyphase left00:19
arahael zZap-X: excwellent progress. now you just gotta do that in the bash shell, rather than your irc shell.00:19
zZap-X aye good point00:19
diegoaguilar left00:20
zZap-X I trying to figure out merge, its getting complicated now00:20
kasisnu_ left00:20
zZap-X Rule No.1 type: git status _BEFORE_ anything you do00:20
fuchstronaut left00:20
zZap-X is it possible to mess up the whole repo if git is used incorrectly?00:21
vishal zZap-X: git is pretty resilient, but yeah, anything is possible :)00:22
sangy zZap-X: yep, but you can copy the repo and try when you are not sure about what could happen00:22
zZap-X: http://gitolite.com/tias.html00:23
!tias00:23
gitinfo Try it and see™. You learn much more by experimentation than by asking without having even tried. If in doubt, make backups before you experiment (see !backup). http://gitolite.com/tias.html may help with git-specific TIAS.00:23
raijin joined00:23
abyx joined00:23
livingstn left00:23
cagedwisdom left00:24
mischat left00:24
zZap-X commit should be called snapshot00:24
slappymcfry joined00:25
bremner make an alias, if you like00:25
zZap-X how does GIT respond when working with large files?00:26
eletuchy joined00:26
orlock zZap-X: poorly, generally00:27
zZap-X ok00:27
knighthawk left00:27
orlock depends on how large00:27
theres a thing called LFS00:27
zZap-X imagine i had 6GB photoshops files00:27
lots of them00:27
mischat joined00:27
zZap-X i think git is more designed for text and code00:28
orlock yes00:29
not for binary blobs00:29
look at git lfs00:29
zZap-X ok00:29
abyx left00:29
zZap-X oh interesting00:29
orlock i'm here because i have to implement it at work00:30
staticshock left00:30
orlock one of the products we use implements an LFS file server however00:30
peepsalot left00:31
jjido joined00:31
mellernoia left00:31
eletuchy left00:31
jjido After pull I have both modified: tests.js00:31
what do I do now?00:32
s00pcan left00:32
ojacobson !eek00:32
gitinfo [!eekaconflict] Merge conflicts are a natural part of collaboration. When facing one, *don't panic*. Read "How to resolve conflicts" in man git-merge and http://git-scm.com/book/ch3-2.html#Basic-Merge-Conflicts then carefully go through the conflicts. Picking one side verbatim is not always the right choice! A nice video explaining merge conflicts: https://www.youtube.com/watch?v=zz7NuSCH6II00:32
zZap-X I think one can edit the affected file manually when there is a merge conflict?00:33
JanC_ joined00:33
s00pcan joined00:34
jeffreylevesque joined00:34
s00pcan left00:35
JanC left00:35
bremner zZap-X: yes, that's what the links about talk about. It just doesn't work well with most binary files00:35
zZap-X indeed00:35
mellernoia joined00:36
zZap-X git could damage a binary if it writes into it?!00:36
s00pcan joined00:36
cagedwisdom joined00:36
jjido ok sorted thanks!00:37
staticshock joined00:37
timvisher left00:37
kandinski joined00:38
timvisher joined00:38
JanC_ left00:38
Nikesh joined00:38
JanC joined00:39
mwhooker left00:41
kandinski I'm trying to learn about git-subtree, and I can't find anything about it either on git-scm.com/docs nor on git-scm.com/book; they both talk about git-submodule. Where is something more tutorial-y than `man git-subtree` that isn't a Medium post? (best result so far: https://medium.com/@v/git-subtrees-a-tutorial-6ff568381844#.l6e3arykq)00:41
livingstn joined00:41
cagmz left00:44
SporkWitch kandinski: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/00:45
bruce_lee left00:45
kandinski SporkWitch: thanks a bunch.00:45
s00pcan_ joined00:45
SporkWitch kandinski: no problem, and thanks for mentioning it, because i was about to add an API we want to support as a submodule, and now i might not, once i read that article and the follow-up linked at the top of it lol00:45
kandinski yeah00:45
SporkWitch (still need to read, i just found that article now, because i knew atlassian has a ton of great git tutorials, since they make bitbucket and want you to pay them lol)00:46
kandinski I came upon it when trying to decide how to integrate an OS library I'm working on with two lower-level upstream libraries00:46
SporkWitch exactly; we have a service we want to integrate into a bot. so we wrote a wrapper for the API in python, now we need that API in the main bot project.00:47
the wrapper in the bot, that is00:47
kandinski yeah, in my case I need to make lockstep changes into all three projects and manage upstream adoption/rejection of my patches00:47
unbalancedparen left00:47
kandinski which reminds me that tutorials are fine, but "why/when to use X" is as important or more as "how to use X"00:48
username17 left00:48
kandinski `man X` already does the latter, and can never cover the former extensively enough00:49
Yarne left00:49
mingwandroid left00:49
SporkWitch hear hear00:49
it's the hardest thing to teach, as well00:49
i can teach someone to do pretty much anything, what is hard to teach is how to THINK00:50
kaiza left00:55
s00pcan_ left00:56
kandinski I recently got a workmate on my day job, and we learn "how to do X" separately, but we put our heads together for all our "why do X and not Y" decisions00:57
cyphase joined00:57
cyphase left00:57
cyphase joined00:57
SwiftMatt left00:58
harish_ left00:59
jjido left01:00
bronson joined01:02
username17 joined01:02
s00pcan_ joined01:02
espindola joined01:06
bronson left01:06
ferr left01:08
ncd|leeN left01:08
durham left01:08
radsy left01:08
livingstn left01:08
radsy joined01:09
jbitdrop left01:09
carif joined01:10
russoneto joined01:10
timvisher left01:10
cyphase left01:10
timvisher joined01:11
jaguarmagenta joined01:11
russoneto I need to understand something here... I cloned my project that has a few branches. The thing is, my "master" local branch (fresh clone) is showing me all commits from remote/alpha branch... does it make sense?01:13
espindola left01:13
Seban left01:13
ojacobson I would assume the remote has alpha set up to be its default branch01:15
harish_ joined01:16
fuchstronaut joined01:16
russoneto no it's not...01:17
SporkWitch that should just have you start on the alpha branch, not have master match the contents of the alpha branch01:17
russoneto but I entered some commands before (my previous local git got corrupted).. in order: git clone --depth 1 / git fetch --unshallow01:18
does it explains?01:18
SimonNaa joined01:19
peeps[lappy] left01:20
digidog left01:20
CheckDavid joined01:21
weox joined01:21
hwrdprknshwrd[away]01:21
fuchstronaut left01:22
SimonNa left01:22
theskillwithin joined01:23
hwrd[away] left01:23
hwrdprkns joined01:23
rewt why not do a normal clone?01:24
deadnull_ joined01:25
jimi_ left01:25
deadnull_ left01:25
harish_ left01:25
deadnull_ joined01:25
fahadash joined01:25
deadnull left01:26
deadnull_ left01:27
deadnull joined01:28
russoneto rewt I followed a brief guide on stack overflow.. I was having this error: fatal: early EOF fatal: index-pack failed01:28
hwrdprknshwrd[away]01:28
russoneto This is what I did (most voted answer): http://stackoverflow.com/questions/21277806/fatal-early-eof-fatal-index-pack-failed01:28
anyway01:28
hwrd[away]hwrdprkns01:29
deadnull left01:29
rewt i'd go with the 2nd answer01:29
as for your original question, that does seem weird01:30
deadnull joined01:30
rewt maybe have a look at what `gitk --all` shows01:30
acton left01:32
JanC left01:33
russoneto gitk --all says I'm on master and all commits are in fact from remote/alpha01:34
Lewoco__ joined01:34
hwrdprknshwrd[away]01:34
russoneto even the hash is the same lol01:34
Lewoco__ Suppose I add a subtree with a prefix. If the upstream adds new files and I merge them will the new files automagically get the prefix used when the subtree was originally added?01:35
hwrd[away] left01:35
haoli joined01:35
user083 left01:35
russoneto wait, what? this is VERY weird. (wait a sec)01:36
rewt where are the branch pointers?01:36
is remote/alpha at the same point as master?01:36
russoneto http://i.imgur.com/I9ZjR5T.png01:37
how weird is that? check commiters, log messages and the hash01:38
jagob left01:38
mablae__ joined01:38
russoneto go home git, you are drunk lol01:38
rewt is this a public repo?01:38
that does look weird01:39
where's remote/alpha in gitk?01:39
remotes/origin/alpha01:39
kadoban joined01:40
russoneto when I browser remote, there is NOTHING01:40
just master01:40
cyphase joined01:40
russoneto its not a public repo01:40
mablae_ left01:41
rewt remotes/origin/alpha should show in `gitk --all`01:41
peeps[lappy] joined01:41
rewt oh01:41
maybe that's right, and 0bf3a1e is the start of alpha01:42
raijin left01:42
rewt anything prior to where alpha branched from master is still "in alpha"01:42
russoneto no man..01:42
let me try other thing01:42
joki left01:43
russoneto This is the log from the corrupted repo: http://i.imgur.com/dJLc01V.png (using tortoise git)01:43
all of that is remote/alpha01:43
ojdo left01:46
rewt i just tried that --depth 1 / --unshallow method, and it doesn't seem to fetch remote branches for me01:47
russoneto hm!01:48
so if I just do a normal clone everything should work01:48
rewt i would think so, yeah01:48
pks left01:48
russoneto cool..01:49
hwrdprkns joined01:49
joki joined01:49
kam270 left01:50
deadnull left01:50
pks joined01:50
ojdo joined01:52
mischat left01:55
mikiones left01:58
knighthawk joined01:58
SwiftMatt joined01:58
EvilPenguin left01:59
astrofog joined02:00
SwiftMatt left02:00
bitkiller left02:00
The_Phoenix joined02:01
_xor Ok, another dumb question.02:03
I'm trying to do this: git diff --no-index --summary ":(top,exclude).git" "../T"02:03
I'm trying to do a diff between the root of the tracked working tree & a directory outside of the repo.02:04
JBlazeCoder21 left02:04
astrofog left02:04
Dazzyp left02:04
_xor It's complaining though with "error: Could not access ':(top,exclude).git'02:04
knighthawk left02:05
_xor I'm either messing up the pathspec somehow or something else is going on.02:05
Dazzyp joined02:05
_xor Without that path spec (that is: git diff --no-index -summary . ../T) it works as I want it to, but it includes the .git directory in the diff and I don't want that obviously.02:05
axisys left02:07
axisys joined02:08
naitsirhc_ left02:08
hwrdprknshwrd[away]02:08
hwrd[away] left02:09
staticshock left02:12
whomp_ joined02:13
whomp_ how can i see all of the commits i've recently set head to?02:13
jaguarmagenta left02:13
whomp_ even better, how can i see all of the commits that a branch's tip has been set to?02:14
jaguarmagenta joined02:14
hwrdprkns joined02:15
CEnnis91 left02:16
fracting joined02:16
fracting left02:17
staticshock joined02:17
dreiss joined02:18
al-damiri left02:19
mofai left02:19
naitsirhc joined02:20
naitsirhc left02:20
naitsirhc joined02:21
The_Phoenix left02:21
jpleau whomp_: is "git reflog" what you might be after?02:22
ericvw left02:23
SwiftMatt joined02:23
mofai joined02:23
fracting joined02:25
Saylen joined02:26
robogoat joined02:26
SwiftMatt left02:26
Shentino joined02:26
fracting left02:26
SwiftMatt joined02:27
Shentino left02:27
fracting joined02:27
locrian9 joined02:28
livingstn joined02:28
fracting left02:28
fracting joined02:29
Saylen left02:30
fracting left02:30
bilb_ono joined02:30
Dreamer3 joined02:32
Dreamer3 left02:32
bilb_ono can someone help me undestand this? https://bpaste.net/show/33998684d1c802:32
I clearly commited tons of stuff02:32
but when I push it says everything up to date02:32
I want to push those changes to develop02:33
ojacobson > [detached HEAD ab558d9]02:33
jpleau bilb_ono: looks like you are not working on the develop branch02:33
ojacobson you're not on any branch, and unqualified 'git push' pushes branches only02:33
bilb_ono ah ok. git branch says * (HEAD detached from 8104488)02:33
ojacobson either be explicit or be on a branch (and then be explicit)02:33
bilb_ono so how do I get back onto develop, push my changes up02:33
ojacobson !reattach02:33
gitinfo Letters refer to !detached. (a) and (b): 'git checkout branchname' to continue working on another branch, or 'git checkout -b branchname' to start a new one here; (c) git am --continue; (d) git rebase --continue02:33
a_thakur joined02:34
josuebrunel left02:34
bilb_ono if I just do a git checkout develop, I will loose the changes I just made no?02:34
oh like git reattach?02:34
ojacobson you should probably start by giving the current, anonymous branch a name (see above)02:34
bilb_ono does that make the changes I just made change to develop as well?02:34
ok how do I do that?02:34
ojacobson then, once it has a name and you can reason about it, decide how you want to integrate it into the upstream02:34
bilb_ono how would I rename by branch?02:35
or I guess this is just naming it02:35
Sasazuka left02:36
ojacobson 'git checkout -b some-name'02:36
will check out the current commit, creating a branch in the process02:36
AndroidVaan joined02:36
ojacobson s/a branch/a named branch/02:36
_xor He's saying that you should name the implicit branch that you're on, and then figure out what you want to do with it. For you, that sounds like you want to merge or rebase it to the develop branch.02:37
bilb_ono sure02:37
git checkout -b some-name won’t loose my changes because of the -b right02:38
because its a new branch02:38
and now that I do git checkout -b new-branch, how do I push new branch up to bitbucket?02:39
AndroidVaan left02:39
mmlb left02:39
bilb_ono when I do git status, there is nothing new added02:39
rkazak joined02:41
josuebrunel joined02:42
d4rklit3 left02:42
josuebrunel left02:42
AndroidVaan joined02:42
_xor ojacobson: Dumb question, but when doing a push --force from a new local branch, does that create a new branch on the remote if it doesn't exist?02:43
mangolisk joined02:43
_xor Oh, nevermind, found my answer.02:43
moei left02:43
mangolisk_ left02:43
ojacobson yes; push --force blindly copies the values of refs, ignoring any value already present if one _is_ present02:44
_xor ojacobson: I'm reading the man page and trying to figure out when to use --force and when to use --set-upstream.02:45
ojacobson I... I'm not sure I know how to help with that. They're so different that I can't imagine confusing the two, so I don't think I can reconstruct your mental state. :)02:46
Clearly they can be confused -- you just did -- so consider this a failure of my imagination, not of you02:46
lolmac left02:46
jeffreylevesque left02:47
Bruce____ left02:47
harish_ joined02:47
AndroidVaan left02:47
_xor Lol, no you're right. I just misread it hah.02:47
ojacobson _xor: 'git push --force remote foo:bar' blindly copies the 'foo' ref (or ref pattern) to the 'bar' ref (or ref pattern) in the repo 'remote'02:47
'git push --set-upstream remote foo:bar' non-blindly copies as above, and amends the repo's git-config to make bar the upstream branch, and remote the upstream remote, of the local foo branch02:47
_xor Ah ok, so it sounds like I'd probably want to use both then?02:49
ojacobson Depends on your goals02:49
livingstn left02:49
ojacobson They're "just tools," so there's no generic advice to give besides "--force is a really big hammer, use --force-with-lease if you can"02:49
(and only use either if you have to)02:49
_xor The workflow I'm thinking of in my head is when I'm working in my local repo, create a new branch, make some changes & commit them. This new branch doesn't exist in the remote repo.02:49
ojacobson Creating a branch doesn't require --force02:50
_xor I want to push this new branch to the remote repo such that in the remote repo, it's created and the changes are accepted.02:50
ojacobson ("Creating" a branch with --force runs a risk of overwriting someone else's branch)02:50
xaa left02:50
_xor Yup, I'm not really wanting to use --force, just looking to understand it all better. I'm still pretty newbish.02:50
Es0teric joined02:50
aidalgole1f02:51
e1faidalgol02:52
hexagoxel left02:53
_xor Ah ok, I was under the mistaken impression that the remote would flately refuse to accept a push to a branch that doesn't exist already.02:53
ojacobson By default, git will accept any push that ensures that all reachable objects remain reachable02:53
new branches can't possibly render objects unreachable, so they're accepted02:54
italoacasas1 left02:54
_xor Ah ok, that makes sense.02:54
Goplat joined02:54
hexagoxel joined02:54
_xor Some of my initial confusion was coming from this: "In all these cases, you first have to explicitly push the new branch (git push <remote> <branch>), and some do require an upstream (git push -u <remote> <branch>)."02:54
I read another comment that said --force would be required, but that's obviously incorrect.02:55
sdothum left02:55
harish_ left02:55
madewokherd left02:55
Bruce____ joined02:56
akiva joined02:58
chachasmooth left02:59
chachasmooth joined03:01
Sasazuka joined03:01
nnyk joined03:02
mehola joined03:02
MattMaker joined03:02
bilb_ono left03:03
bronson joined03:04
albel727 left03:04
AndroidVaan joined03:05
AndroidVaan left03:05
AndroidVaan joined03:05
AndroidVaan left03:05
AndroidVaan joined03:06
AndroidVaan left03:06
watabou left03:06
AndroidVaan joined03:07
diegoviola left03:07
bronson left03:09
watabou joined03:10
MattMaker left03:11
chachasmooth left03:11
chachasmooth joined03:12
stantonk joined03:16
fuchstronaut joined03:19
akiva left03:20
whomp_ left03:23
fuchstronaut left03:23
radsy left03:26
gravitron joined03:26
whomp joined03:28
username17 left03:28
arahael _xor: Consider also the case where you push a change, but someone else has already pushed a newer change to the same branch.03:28
fedexo joined03:28
arahael _xor: You absolutely don't want to be using --force in this case, as you'll loose changes.03:29
Noldorin left03:29
whomp left03:32
Sasazuka left03:33
whomp joined03:33
ensyde left03:33
Nikesh left03:33
SteffanW2 joined03:35
whomp left03:38
irqq joined03:40
username17 joined03:41
hwrdprknshwrd[away]03:42
whomp joined03:43
foodtooth joined03:44
cyphase left03:44
bb010g joined03:44
gitinfo set mode: +v03:44
nidr0x left03:45
fscala left03:46
foodtooth left03:46
hwrd[away] left03:47
fscala joined03:47
MattMaker joined03:49
CheckDavid left03:52
axisys left03:54
cwong_on_irc joined03:54
knighthawk joined03:54
SwiftMatt left03:55
Joanna___ left03:56
Peter__ joined03:57
nevodka joined03:58
hwrdprkns joined03:58
knighthawk left03:58
mikiones joined03:58
ome left03:58
axisys joined04:00
ariel_17 left04:00
Peter__ left04:01
Sleepy63 left04:01
mellernoia left04:02
sagerdearia left04:02
eletuchy joined04:03
mikiones left04:03
Tylak left04:04
sagerdearia joined04:05
robotroll left04:06
eletuchy left04:07
Gamecubic_ left04:08
muthu joined04:10
cyphase joined04:10
_rht joined04:11
CEnnis91 joined04:11
rscata joined04:13
cyphase left04:15
SteffanW2 left04:16
irqq left04:17
timvisher left04:20
t-mart__ joined04:21
timvisher joined04:21
MattMaker left04:22
Sleepy63 joined04:22
cagmz joined04:22
harish_ joined04:22
SimonNaa left04:23
harish_ left04:24
t-mart_ left04:24
robogoat left04:25
robogoat joined04:25
stantonk left04:26
stantonk joined04:26
harish_ joined04:27
stantonk left04:28
Cabanossi left04:28
mohabaks joined04:28
lindenle left04:31
Cabanossi joined04:31
robogoat left04:31
SimonNa joined04:33
peeps[lappy] left04:33
robogoat joined04:34
IWishIKnew joined04:34
IWishIKnew left04:35
a_thakur left04:36
a_thakur_ joined04:36
SwiftMatt joined04:37
thiago left04:39
cyyuen joined04:42
mohabaks left04:42
fracting joined04:43
whomp_ joined04:44
voice_of_me joined04:44
whomp left04:45
ewet joined04:45
arescorpio left04:45
caudill joined04:47
FuzzySockets left04:49
whomp_ left04:49
bilb_ono joined04:51
dreiss left04:52
caudill left04:55
IWishIKnew joined04:55
timvisher left04:55
rossome left04:56
timvisher joined04:56
mohabaks joined04:56
nitin_ joined04:57
circ-user-m8dfI joined04:57
skylite left05:00
subhojit777 joined05:01
nitin_ left05:02
skylite joined05:03
Bruce____ left05:05
bronson joined05:06
Bruce____ joined05:07
sauvin joined05:07
a_thakur_ left05:07
bronson left05:11
Bruce____ left05:12
fracting left05:12
eletuchy joined05:14
fracting joined05:14
mohabaks left05:15
fracting left05:15
fracting joined05:16
thiago joined05:16
gravitron left05:16
gravitron joined05:16
victortyau joined05:18
whomp joined05:20
IWishIKnew left05:20
fuchstronaut joined05:20
inflames joined05:21
xaa joined05:21
harish_ left05:24
arooni left05:25
fuchstronaut left05:25
whomp left05:26
harish_ joined05:27
tvw joined05:28
IWishIKnew joined05:28
stantonk joined05:28
mohabaks joined05:29
PryMar56 left05:30
d4rklit3 joined05:30
cyyuen left05:30
IWishIKnew left05:31
fahadash left05:32
a_thakur joined05:33
timvisher left05:34
stantonk left05:34
BrunoSaboia joined05:34
weox left05:34
timvisher joined05:34
cyphase joined05:36
nnyk left05:36
BSaboia left05:37
mohabaks left05:38
tyreld left05:40
d4rklit3 left05:43
rossome joined05:44
Macaveli joined05:45
cagedwisdom left05:46
albel727 joined05:46
phaleth joined05:48
xelxebar_ joined05:50
grawity left05:50
cagedwisdom joined05:50
serapath left05:51
grawity joined05:51
abyx joined05:52
bilb_ono left05:52
grawity left05:54
freimatz joined05:54
grawity joined05:55
knighthawk joined05:55
mauzilla left05:56
mikiones joined05:59
aidalgol left05:59
hwrdprkns left06:00
dermoth left06:00
ahr3n left06:00
knighthawk left06:00
dermoth joined06:00
algun joined06:01
ciampix joined06:02
s841 joined06:02
fracting left06:02
mikiones left06:03
emPi joined06:04
s84 left06:04
Es0teric left06:05
dineshp joined06:05
drbean_ joined06:06
dineshp People who contribute to the git repo itself, which email client do you use to import/send patches to the git mailing list?06:06
Olipro left06:07
drbean left06:07
cyan__ joined06:07
timvisher left06:08
dineshp I assume a commandline based email client would make the process of working with patches easier06:08
timvisher joined06:09
grawity I think most people just use git-send-email06:09
voice_of_me left06:09
przemoc left06:10
sangy dineshp: git-send-mail is usually the best way to go06:11
drbean joined06:11
sangy dineshp: also check git-format-patch.06:11
send-email*06:11
przemoc joined06:12
solars joined06:12
dineshp git-send-mail is used to send the patch to the mailing list, but what about importing patches from your inbox? I have a gmail account and what I do is to view the source of the email in gmail and save the file as a .mbox file to import it06:13
Is there a better way?06:13
drbean- joined06:13
sangy dineshp: I use mutt for that06:13
Strout left06:13
dotpot joined06:13
grawity dunno what clients the maintainers use, but as long as it can export messages to mbox-ish files, passing those through `git am` should work06:13
Joanna___ joined06:13
nevyn fetchmail?06:14
neonKow left06:14
nevyn or offlineimap (does gmail still do imap?06:15
drbean_ left06:15
ksinkar joined06:15
nevyn it does06:15
drbean_ joined06:15
grawity I'd go with Mutt tbh06:15
drbean left06:15
nevyn mutt is overkill.06:16
grawity and fetchmail isn't.06:16
nnyk joined06:16
ksinkar I had a big repository and I was happily splitting it into smaller repositories using the git subtree command, when suddenly the git command stopped identifying my mother repo on the local machine as a valid git repo. After that I am not unable to push changes from my other unrelated git repos to the remote git servers. How do I debug this?06:17
nevyn grawity: fetchmail is probably worse but offline imap is probably the sweet spot.06:17
drbean- left06:18
nevyn http://www.offlineimap.org/doc/use_cases.html#sync-from-gmail-to-a-local-maildir-with-labels06:18
ksinkar edit "am not unable" -> "am unable"06:18
dineshp Another question, so when sending an email using git-send-mail, it asks for the email and password for authentication, but sometime back gmail switched to 2 factor/stage login process as the default, so git-send-mail fails to authenticate with the gmail servers. I found a workaround by enabling "legacy login" through gmail. Is there a way to get git-send-mail to work with 2 factor/stage login for gmail?06:18
nevyn ksinkar: can you still clone it?06:18
tpollard left06:19
sangy So, Junio seems to use Gnu's06:19
the other maintainers i can't see their UA string06:19
dineshp sangy: thanks, i'll checkout gnu's as well06:20
nevyn dineshp: use a credential store and setup a application password for it06:20
Strout joined06:20
lamppid joined06:20
ksinkar nevyn: clone a new repo? No I can't. It seems to be a credential problem that suddenly arose06:21
dineshp nevyn: any pointers to some guide/article explaining this process as I am not familiar with it?06:21
fuchstronaut joined06:21
ksinkar I can see in my bash history the last time the git command worked as expected.06:21
dreiss joined06:22
sangy dineshp: https://support.google.com/accounts/answer/185833?hl=en06:22
nevyn dineshp: http://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-on-github/5343146#534314606:23
that's for https.. but it works for imap too.06:23
dineshp: oh.. which bit? app passwords or a credential store?06:23
acolson joined06:23
harish_ left06:23
nevyn sangy's url is for the former (guess) mine is for the latter06:24
sangy unintended teamwork06:24
dineshp nevyn: thanks06:24
sangy: thanks06:24
harish_ joined06:25
fedexo left06:25
fuchstronaut left06:26
nevyn ksinkar: how many git repo's are you dealing with here?06:26
SimonNa left06:27
nevyn dineshp: if you're recieving a lot of patches then a local imap client or clone tool might be handy06:27
Es0teric joined06:27
jrmiah joined06:29
ksinkar nevyn: around 20. Another observation: I am able to push to github, but the problem seems to persist for gitlab. Also, while doing subtreeing, we generally pull from the repo on our local filesystem 'git pull ../frameworks pascal'. This was working and then it suddenly stopped working. It gives me 'repo does not exist or I have insufficient rights error'. Same issue with remote gitlab server as well. I am not able t06:29
o push code changes to the remote gitlab server.06:29
mase-tech joined06:30
nevyn pull?06:30
barduck joined06:30
mase-tech left06:30
sangy left06:31
nevyn if you have any local changes that's going to get... interesting06:31
!pull06:31
gitinfo pull=fetch+merge (or with flags/config also fetch+rebase). It is thus *not* the opposite of push in any sense. A good article that explains the difference between fetch and pull: http://longair.net/blog/2009/04/16/git-fetch-and-merge/06:31
jrmiah how many questions do you guys get for something thats easy in other SCMs? like .. i have a commit that needs merged with remote .. and boy that sure seems simple .. why is git tough?06:31
nevyn jrmiah: most people don't read any of the docs.06:31
operating git based on a flawed model of what it's doing ends badly.06:32
once you know how it works. which requires a passing familiartiy with the internal data structures things are actually really simple06:32
jrmiah: some people like !book I personally prefer !gcs06:33
gitinfo jrmiah: 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 !parable06:33
jrmiah: [!concepts] "Git Concepts Simplified" explains the basic structures used by git, which is very helpful for understanding its concepts. http://gitolite.com/gcs.html06:33
PCatinean joined06:33
jrmiah is that the right place to start?06:33
I mean some of us have been in silicon software engineering using things like perforce that while they dont allow offline interaction, rule git in every other way for usage.06:34
not debatable thats just a fact.06:34
yes I get it .. its a local atomic version of scm .. yay! its only better than SVN its not a good model for a small team is it?06:34
nevyn git's ui is a horror.. it's author has publicly stated that if he were stranded on a island and the only way to get off the island was to build a graphical ui he'd die there.06:34
cyan__ left06:35
ksinkar nevyn: this is what I was doing (http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository/17864475#17864475). I have done this many times before, but this time it seems some configuration file has changed that my access is suddenly being denied.06:35
grawity it's getting better06:35
...slowly.06:35
Alienpruts joined06:35
jrmiah ney: 'gits authoer"? Linus? yeah Ive been using linux since 2.206:35
nevyn grawity: I'm not sure about that the reflog is really useful in practial use. but nonsense unless you understand the DAG06:36
jrmiah see, git was developed because of Linus's problem: he had to merge 200 commits a day to the kernel from arbitrary sources and somehow keep track of which versions those diffs went to. Makes sense to make a pretty good distributed system. But what are you lunatics using this shit for to develop a website with 4 guys for? haha06:36
sorry just venting ;)06:36
nevyn jrmiah: sure. but it's eating the world (for better or worse)06:36
grawity nevyn: what do you mean, not useful in practical use06:37
osse the reflog is useful if you need to use rebase --onto06:37
jrmiah nevyn: http://stackoverflow.com/questions/449541/how-do-you-merge-selective-files-with-git-merge06:37
radsy joined06:37
grawity nevyn: are you saying people should just not make mistakes in the first place?06:37
jrmiah is that really the answer to something that's a one liner with a 'unified' scm?06:37
timvisher left06:37
jrmiah grawity: yes he is06:37
grawity: he has a beard too06:37
nevyn understanding the contents of the reflog requires understandingwhat it is. (a history of where HEAD has been)06:37
timvisher joined06:38
nevyn which requires understanding what HEAD is.06:38
which requires knowlege of the DAG06:38
shmuli joined06:38
nevyn and how commits are attomic and that's why wen you commit --amend you get a entry in the reflog06:39
gravitron: ^^06:39
ugh sorry06:39
grawity: ^^06:39
NeverDie left06:40
nevyn jrmiah: so the right answer is that commits should be atomic and then it's a simple matter of getting the required commits.06:40
NeverDie joined06:40
jrmiah http://stackoverflow.com/questions/449541/how-do-you-merge-selective-files-with-git-merge06:40
yeah .. well actually its more like this: deal with commits in a way that still gives you a lot of granularity. Folks that use client-server systems just dont think that way..06:41
nevyn you can't have certain garuntees that git provides AND arbitary file merging behaviors into other branches06:41
jrmiah you guys avoid the 'remove a file from a commit' problem probably by having 20 commits for 10 files in an hour right?06:41
zeroed joined06:41
nevyn jrmiah: because I signed of commit X to file A B and C which implements feature Y06:42
jrmiah no its just that unlike other SCMs git doesnt allow for files to be managed easily within a commit .. a commit is king I think06:42
nevyn if you merged b and c missing A and it's busted...06:42
or if you missed a prerequisite commit in my tree that's your problem too06:42
jrmiah: commits are IMMUTABLE06:43
jrmiah yup, which is _sound_06:43
and how all other systems are too06:43
nevyn nope06:43
well06:43
jrmiah so .. commit is a commit in any SCM, true06:43
nevyn in git commits are universally immutable06:43
jrmiah yup .. i think that kinda solves it06:44
nitin_ joined06:44
jrmiah the problem being that remote and local out of wack leads to learning a whole base of lore thats needless06:44
just for merging - thats broken06:44
nevyn so..06:44
shmuli left06:44
nevyn if you want06:44
jrmiah so... whats the benefit heh06:44
offline, local committing?06:44
i have that in my IDE heh06:44
nevyn and imo preferable..06:44
is to rebase private trees onto public trees06:45
MrWoohoo joined06:45
jrmiah well its all well and good mna06:45
nevyn and this is still a merge.06:45
jrmiah and a million 25 year old ruby programmers cant be wrong06:46
nevyn I did say it's eating the world ;)06:46
nnyk left06:46
jrmiah insanity06:46
i think you will see that while yeah .. a16z bought into it .. this wont last long06:46
this is _terrible_ for small teams not doing mass merges06:46
from random sources. the worst in fact.. Im convinced they just dont know better06:47
osse I work in a small team and have no problems06:47
nevyn jrmiah: it's got some benefits.06:47
osse wait, what are we discussing?06:47
nevyn jrmiah: offline is nice (A copy on my laptop / in the test env /blah)06:48
abyx left06:48
nevyn jrmiah: most small orgs end up using a central server model rather than a peer to peer model06:48
cyan__ joined06:49
nevyn either bitbucket/github or a hosted solution such as github appliance, gitolite, or gitlab06:49
jrmiah: the interactions of the graph in peer to peer get scary.06:49
kareeoleez joined06:49
shmuli joined06:50
voice_of_me joined06:50
kareeoleez I have a branch "setup" and "master". I usually do some changes in "Setup" and then push them, then checkout "master" and merge setup. I realised I can also do rebase setup. What is the difference between rebase and merge ?06:50
Is it wrong to do a rebase in master always ?06:50
nevyn 5 people in the team 5! remote relationships06:50
dineshp Where can I access the logs for this channel(so I can view the past conversations without logging it myself)?06:51
osse kareeoleez: https://raw.githubusercontent.com/Osse/git-stuff/master/merge-vs-rebase.txt06:51
nevyn !log06:51
gitinfo [!irclog] Public logs of #git are kept at: http://colabti.org/irclogger/irclogger_log/git or look at stats for the last 30 days: http://itvends.com/irc/git.html or since Jan 1, 2012: http://itvends.com/irc/git-all.html06:51
kadoban left06:51
dineshp *sorry to interrupt06:51
nevyn ooh that was neat06:51
kareeoleez what is the common way to do this?06:52
jrmiah baloney: thanks for the insights..06:52
nitin_ left06:52
jrmiah nevyn: thanks for convo was just venting06:52
kareeoleez I just want master to be updated with the latest commits always06:52
nitin_ joined06:52
jast !merge_vs_rebase06:52
gitinfo [!merge_or_rebase] For a detailed discussion of the dis-/advantages of merge and rebase, and when to best use which, see: https://coderwall.com/p/ny1hia -- and here's how Linus explains which one to use: http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg39091.html06:52
osse sounds like you want rebase06:52
JeroenT joined06:52
cagmz left06:53
jrmiah nevyn: fact is that I cant even ask you for quick help with mine and my buddy's merge stuff cuz honestly its all abotu the state of a tree - it will take 30 minutes to resolve I guarantee06:53
jceb joined06:53
jrmiah nevyn: so whats the command for pave push? -f ? I've had that erally screw stuff up before06:53
kareeoleez osse: thanks for the references06:53
againcode joined06:53
weox joined06:53
nevyn jrmiah: so there are two things I'd say06:53
jrmiah: use more branches. and write more commits (not too many)06:54
jrmiah exactly06:54
nevyn jrmiah: have a look at !gitflow06:54
gitinfo jrmiah: The description of the gitflow branch workflow model is at http://nvie.com/posts/a-successful-git-branching-model/ while a tool to help implement this workflow is at https://github.com/petervanderdoes/gitflow See http://sethrobertson.github.com/GitBestPractices/#workflow for other workflow suggestions/references06:54
JeroenT left06:54
jrmiah thats the thing that our convo helped with ... and its stuff I know but no one will typically take their local branch 'serious' because its not pushed to main yet06:54
pantsman- joined06:55
jrmiah thats just normal for people using every other SCM for 20 years heh. its not even my fault. Then you go to push your local commit (err ok whatever) and its completely insane what has to be done.06:55
nevyn jrmiah: one of the challenges is that git is a raw mechanism which doesn't dictate aything about workflow06:55
you really do need one06:56
SimonNa joined06:56
nevyn but git doesn't provide out of the box a workflow for working with multiple repos06:56
duderonomy left06:56
nevyn you can pick one (the kernel have one using lots of humans)06:56
but in the same way 'don't break the build' was the catchcry of traditional scm's forever06:57
Sceorem joined06:57
nevyn 'don't forcemerge and push ancient shit into the canonical repo' is the git version06:57
jrmiah: force push is particularly nasty06:58
jrmiah: get back from 4 weeks off git pull && git push -f makes everyone want to stab you.06:59
Fijit joined06:59
jrmiah and I can even tell you why :)07:00
see I dont like it cuz I understand it ;)07:00
JeroenT joined07:00
nevyn jrmiah: rebase private repos merge public repos07:01
zeroed left07:01
nevyn jrmiah: so. options07:01
osse actually, if the pull goes without a hitch then there shouldn't be any difference between push and push -f07:01
nevyn osse: 4 weeks off...07:01
osse yes...07:02
nevyn you just rewrote the cannonical repo with 4 weeks ago plus a giant merge of everything in the last 4 weeks and your work07:02
dreiss left07:02
Brain joined07:02
nitin_ left07:02
osse yes...07:03
there doesn't have to be any "rewritey" about it07:03
dan2k3k4 joined07:03
nevyn oh right so you get a new merge commit on top07:05
but eww.07:05
nevyn likes rebase ;)07:05
victortyau left07:05
harish_ left07:06
arahael nevyn: what's wrong with merges?07:06
osse there are much worse things: the other day I had to help a colleague because one of his collaborators had apparently done a pull, but made a copy of all the file and then replaced them when finishing the merge. effectively doing a -s ours07:06
victortyau joined07:06
ubuntu joined07:07
ubuntuGuest1271107:07
dineshp left07:08
barduck left07:10
shmuli left07:10
fracting joined07:11
Es0teric left07:12
cyan__ left07:13
The_Rebel_G0d left07:14
The_Rebel_G0d joined07:14
nevyn arahael: mostly I don't like the effect on bisect07:14
osse: that's common07:14
arahael what effect is that?07:15
fracting left07:15
nevyn bisect on a linear history is a thing of beauty.07:15
againcode left07:15
nevyn bisect on a more 'correct' merge history can be horrible07:16
Gonzo89 joined07:16
againcode joined07:16
ki0 joined07:16
josuebrunel joined07:17
nnyk joined07:18
[Brain] joined07:18
ayaz joined07:19
lamppid left07:20
ahmedelgabri joined07:20
Brain left07:21
lamppid joined07:21
SporkWitch is it possible to pull with interactive rebase? it doesn't seem to like the -i flag...07:21
jast no, it's not07:22
osse wasn't that added recently=07:22
fuchstronaut joined07:22
nevyn SporkWitch: at that point just fetch & rebase -i ?07:22
SporkWitch grrr07:22
osse SporkWitch: it's fixed in 2.8.007:23
SporkWitch osse: is that available packaged for debian or am i building from source?07:23
osse i don't know07:23
SporkWitch because being able to do a pull with interactive rebase, that would make my life much easier right now07:23
testild joined07:23
osse there are probably .debs somewhere.07:24
if not, the setting up an alias to do fetch and rebase is probably easier07:24
SporkWitch how would the procedure differ? i didn't think fetch actually grabbed any data? sorry, still pretty new to the more advanced features of git, learning it as i go07:26
osse SporkWitch: pull = fetch + merge07:26
SporkWitch: pull --rebase = fetch + rebase07:26
voice_of_me left07:26
SporkWitch i have a file i rewrote about 70% of, butt had a hotfix upstream that i need07:26
ah, ok07:26
osse fetch is the one that actually retrieves data07:26
SporkWitch ah, ok07:27
fuchstronaut left07:27
Goplat left07:27
SporkWitch so doing fetch and then rebase -i would be the same as pull with interactive rebase07:27
osse yes07:27
assuming you just want 'git pull -i' and not 'git pull -i otheremote fancybranch'07:28
fracting joined07:28
SporkWitch nope, i'm on my feature branch, and i want to rebase it to the current head of release/testing07:28
so then i would just either squash or pick everything (and pick on the one listed on bottom, the most recent commit) and update the comment to summarize all the changes, yes?07:29
threeminutemonta left07:35
voice_of_me joined07:36
d4rklit3 joined07:37
nnyk left07:38
pantsman- left07:41
staticshock left07:42
wviana left07:42
MattMaker joined07:45
bruce_lee joined07:46
Darcidride joined07:48
ffio joined07:48
mikiones joined07:48
circ-user-m8dfI left07:53
circ-user-m8dfI joined07:54
Balliad joined07:54
Sazhen86 left07:55
encod3 joined07:57
theskillwithin left07:57
Jellyg00se joined07:57
fees joined07:58
knighthawk joined07:59
xcesariox joined08:00
jbitdrop joined08:02
rossome left08:02
trudko joined08:02
encod3 left08:03
trudko Hi, how can I setup filters in git ? something like this http://pastie.org/10813247. Is this what git config is for? if yes how would the command look like exactly ?08:03
encod3 joined08:04
josuebrunel left08:04
josuebrunel joined08:05
bongjovi joined08:05
radsy_ joined08:05
thiago left08:05
radsy_ left08:05
nnyk joined08:06
trudko ou nvm i can paste it into ~/.gitconfig I did realize thats the folder with the config08:06
d4rklit3 left08:07
afuentes joined08:08
cagedwisdom left08:08
radsy left08:08
metalraiden joined08:10
_pix joined08:11
chll joined08:11
rossome joined08:12
Shashikant86 joined08:13
nilg joined08:14
ahmed_elgabri joined08:15
bongjoviZGD08:16
nilg` joined08:16
nilg left08:16
Raging_Hog joined08:17
ahmedelgabri left08:18
sathya joined08:18
nilg` left08:19
LiohAu_ joined08:20
bollullera joined08:20
timvisher left08:20
a_thakur left08:21
LiohAu_ Hey guys, someone has started a "feature branch" and has pushed it on the main repo, how do I get this branch and complete it ?08:21
ferr joined08:21
timvisher joined08:21
selckin what does complete it mean08:21
LiohAu_ selckin: I want to add some stuff, and share what I added with the branch author08:21
but I won't finish that feature08:22
intelly joined08:22
selckin git fetch; git checkout -b localbranchname origin/branch-name08:22
LiohAu_ I have done this : "git pull origin feature-branch-name" should I undo this?08:22
fuchstronaut joined08:23
selckin probably08:24
tlaxkit joined08:24
selckin pull = fetch + merge (or rebase)08:24
subhojit777 left08:24
Rish joined08:25
FuzzySockets joined08:25
CrypticGator left08:25
tvw left08:25
dcpc007 joined08:26
LiohAu_ selckin: so you mean that if I push, I will send the merge of the branch on the branch that was active locally ?08:27
a_thakur joined08:27
fuchstronaut left08:27
josuebrunel left08:28
ahmed_elgabri left08:28
cybernite left08:28
Anupkumar joined08:29
jottr joined08:30
MattMaker left08:30
marcogmonteiro joined08:30
acton joined08:30
t4nk531 joined08:31
gitinfo set mode: +v08:31
troulouliou_div2 joined08:31
jottr left08:31
jottr joined08:31
t4nk531 Does anyone use git-shell? How do you set umask for this shell? Whenever files are pushed to the repository, files under the subfolders in Objects are created with permissions 444 causing subsequent commits to fail.08:33
ksinkar LiohAu_: yes08:33
LiohAu_ ksinkar: ok so how do I undo what I did ?08:33
ksinkar LiohAu_: what branch are you on now?08:34
LiohAu_ "develop"08:34
lindenle joined08:34
ksinkar do you have any local changes on develop?08:34
LiohAu_ git status says : On branch develop Your branch is ahead of 'origin/develop' by 4 commits. (use "git push" to publish your local commits)nothing to commit, working directory clean08:35
so I guess I have no local changes, right?08:35
and here are my branches : https://gist.github.com/LiohAu/71d538dd9bff055478581f7996d30e13 (if that helps)08:36
mar77i joined08:37
harish_ joined08:37
lindenle left08:38
mikiones left08:38
staticshock joined08:38
ksinkar An easier way out of this mess is to check out my comment on your gist.08:39
ahmed_elgabri joined08:39
jimi_ joined08:41
LiohAu_ ok08:41
ksinkar: so git checkout change the active branch right?08:43
Darcidride left08:43
ncd|leeN joined08:44
staticshock left08:44
ahr3n joined08:44
LiohAu_ ksinkar: also what is the difference between doing "git checkout feature-branch-name" and "git checkout remotes/origin/feature-branch-name" ?08:45
robbyoconnor left08:45
timvisher left08:45
robbyoconnor joined08:46
timvisher joined08:46
SimonNa left08:46
Macaveli left08:48
jimi_ left08:48
jimi_ joined08:48
Rish_ joined08:48
intelly left08:48
clarens joined08:50
jaguarmagenta left08:50
Rish left08:51
subhojit777 joined08:51
eletuchy left08:52
Macaveli joined08:52
IndigoTiger joined08:53
CheckDavid joined08:53
whomp joined08:53
eletuchy joined08:54
metalraiden left08:54
metalraiden joined08:54
rominronin joined08:55
strk joined08:55
dineshp joined08:57
mahendra_ joined08:58
mahendra_ left08:58
whomp left08:58
LiohAu_ ok I understood that I needed to add a "-b feature-branch-name" with the 2nd syntax08:58
Macaveli left09:00
jimi_ left09:02
ferr left09:03
moei joined09:04
dineshp left09:04
CEnnis91 left09:06
mase-tech joined09:06
jottr left09:06
King_Hual joined09:08
randomgry joined09:08
eletuchy left09:09
whomp joined09:10
mrkat joined09:10
timvisher left09:11
timvisher joined09:11
Macaveli joined09:11
elementalest left09:11
elementalest joined09:12
isxek joined09:12
randomgry left09:13
isxek left09:13
strk does "git push" also push annotated tags ?09:14
nevodka left09:14
strk or is there any way to push only annotated tags with no light tags ?09:14
whomp left09:14
eletuchy joined09:14
irqq joined09:15
fuchstronaut joined09:15
isxek joined09:15
Joanna___ left09:16
SwiftMatt left09:18
_rht left09:20
Sceorem left09:20
knighthawk left09:20
wxg joined09:22
fracting left09:23
clmsy joined09:25
solars quick question: I need to revert an older commit, and I'd like to extend it before adding it again - how can I get the changes of this commit into a separate (uptodate) branch?09:25
aidalgol joined09:26
doppo left09:28
redasus joined09:29
redasus2 joined09:30
stantonk joined09:32
solars nevermind, I'll do it in 2 commits09:33
lindenle joined09:35
mattfoo left09:36
stantonk left09:36
doppo joined09:36
johnwhitton left09:36
strk rebase -i09:36
use "e" for edit09:36
voice_of_me left09:37
mdw joined09:37
strk "how can I get the changes of this commit into a separate (uptodate) branch?" <-- using `git cherry-pick <that_commit>` from the uptodate branch09:37
fracting joined09:39
mehola left09:39
lindenle left09:39
timvisher left09:40
staticshock joined09:41
solars thanks strk09:41
timvisher joined09:41
josuebrunel joined09:41
doppo left09:41
Rish joined09:45
dsdeiz joined09:45
Rish_ left09:45
cdg left09:45
staticshock left09:45
grift left09:47
johnny56_ joined09:47
Rish left09:47
SwiftMatt joined09:47
mikiones joined09:47
grift joined09:49
Olipro joined09:49
johnny56 left09:49
metalraiden left09:49
digidog joined09:50
mattfoo joined09:50
doppo joined09:52
clarens left09:52
cwong_on_irc left09:53
ManDay joined09:53
clarens0000 joined09:53
ManDay Little oops: I git commit -a'ed, then `git checkout @^ some/file`. Expectation: Replaced some/file in the working tree by the old version. Reality: `git diff` shows nothing. Did I break somethiing?09:54
isxek left09:54
jceb left09:54
krnex joined09:55
cyan__ joined09:55
ManDay Uhm well, `git status` says that some/file is modified, as I'd have expected.09:56
But why does that not show up in `git diff` ?09:56
acetakwas joined09:57
clarens0000 left09:57
cwong_on_irc joined09:57
redasus2 left09:58
redasus left09:58
doppo left09:58
klear joined10:00
mkoskar left10:01
Shashikant86 left10:02
acetakwas left10:04
isxek joined10:04
Borkr joined10:05
klear left10:06
acetakwas joined10:06
MrWoohoo left10:06
King_Hual left10:06
Sceorem joined10:07
osse ManDay: diff --staged10:08
cwong_on_irc left10:08
cyan__ left10:09
JeroenT left10:09
ManDay Osse: So git checkout ... some/file automatically added some/file?10:09
kits joined10:09
osse yes10:10
git status tells you this10:10
bronson joined10:10
timvisher left10:10
cyan__ joined10:10
doppo joined10:10
timvisher joined10:11
victortyau left10:11
t4nk531 I'm using sharedrepository = true but files are still being created with 444 permissions10:12
~/.bashrc has umask 002 but I'm not convinced that git-shell uses .bashrc10:12
Yarne joined10:12
Lomex joined10:13
arahael t4nk531: it doesn't. but it still inherits the env.10:13
sgambino joined10:13
t4nk531 arahael: Have I missed some setting somewhere then?10:13
Additionally, the folder has the owner and group to the git-shell user10:14
^owner and group set to the git-shell user10:14
bronson left10:15
fracting left10:15
doppo left10:16
mdw left10:16
arahael wow, the man page is hard to jnderstand on this topic.10:17
t4nk531 The man page isn't particularly helpful10:17
arahael what does umask say?10:17
t4nk531 I've set umask to 002 in .bashrc but I'm not sure that's what's read by git-shell10:18
arahael no, run "umask"10:18
MadHatter42 joined10:18
osse is it a bare repo that people push to ?10:18
t4nk531 I can't read umask from the user because it's using git-shell10:18
raijin joined10:18
arahael t4nk531: irrelevant.10:18
t4nk531 It's a bare repo that other users will push to10:18
arahael: You can't get an interactive shell with git-shell10:18
ki0 left10:18
arahael ah. you're right, sorry.10:18
osse do they all push as the same user?10:19
t4nk531 arahael: It's why I can't find out if it's reading .bashrc (which I'm pretty sure it's not)10:19
ki0 joined10:19
t4nk531 They do push as the same user, osse10:19
osse then what does it matter?10:19
you may want to set the sticky bit on some dirs10:19
arahael t4nk531: man git-shell looks hopeful. you could perhaps source it explicitly.10:20
gitinfo t4nk531: the git-shell manpage is available at http://jk.gs/git-shell.html10:20
t4nk531 Because all files are currently created 44410:20
osse and?10:20
t4nk531 Files within the Object/subfolder/files are created 44410:20
ykrons left10:20
t4nk531 The user can't overwrite their own files10:20
osse they won't ever be overwritten10:20
t4nk531 So subsequent push commands say 'Permission denied'10:21
osse that's strange10:21
t4nk531 When I chmod 774 -R the objects folder, then they can push10:21
ahr3n left10:21
osse O don't think it's a permission problem on objects/xy/abc though10:21
CrypticGator joined10:21
t4nk531 Until new files are created, and then it's the permission error again10:21
rdvdet joined10:22
jstimm joined10:23
mdw joined10:24
jceb joined10:25
t4nk531 osse: If not a permissions issue, in the object folder, what do you reckon it could be?10:25
eletuchy left10:26
Shashikant86 joined10:26
radsy joined10:26
Isla_de_Muerte joined10:27
josuebrunel left10:27
attila_ joined10:28
sgambino left10:29
ki0_ joined10:29
fracting joined10:30
againcode left10:30
NwS left10:30
ki0 left10:32
dan2k3k4 left10:34
NwS joined10:35
Shashikant86 left10:35
_ikke_ anything in .git/refs10:36
packs10:36
redasus2 joined10:36
redasus joined10:36
jast pack files are not usually updated during a push10:36
_ikke_ Right10:36
Isla_de_Muerte left10:37
mehola joined10:39
st0opkid joined10:39
t4nk531 _ikke_: Nothing in refs that doesn't have r/w access to the user10:40
mischat joined10:42
mandrex joined10:42
Anupkumar left10:43
mandrex left10:43
mehola left10:44
ki0_ left10:44
doppo joined10:45
comps what's the safe way of repacking on the server-side? .. just repack (creating duplicate packs) and git-pack-redundant at a later date?10:45
fracting left10:45
comps I seem to remember that repack -a caused a race-condition10:45
jimi_ joined10:49
Linkandzelda joined10:50
dan2k3k4 joined10:50
JeroenT joined10:51
ki0 joined10:51
jaguarmagenta joined10:51
JeroenT left10:52
gniourf left10:52
Shashikant86 joined10:52
ahmed_elgabri left10:53
eletuchy joined10:54
doppo left10:54
boombatower left10:55
al-damiri joined10:55
ahmed_elgabri joined10:55
jaguarmagenta left10:56
johnmilton joined10:56
eletuchy left10:58
gniourf joined10:58
ki0 left11:00
osse t4nk531: What about the objects/xy dirs themselves?11:00
jefus left11:00
circ-user-m8dfI left11:01
Lomex left11:02
fracting joined11:02
jceb left11:02
jefus joined11:03
ewet left11:03
Shashikant86 left11:04
aidalgol left11:05
a_thakur left11:07
JeroenT joined11:07
a_thakur joined11:07
pwnawannab[NE] joined11:07
pwnawannab_ joined11:07
Lomex joined11:09
JeroenT left11:09
JeroenT joined11:09
ewet joined11:11
Linkandzelda hi, im quite new to git. i forked a repo and added/changed/restructured some code, then the repo i forked had some changes and new code added. can i use git to bring those changes into the fork and still keep my additions/changes/restructuring?11:11
canton7 Linkandzelda, https://help.github.com/articles/syncing-a-fork/11:11
Linkandzelda thanks11:12
doppo joined11:13
SwiftMatt left11:14
Novitsh joined11:14
krnex left11:14
Lomex left11:14
realz left11:15
mdw_ joined11:15
encod3 left11:15
krnex joined11:15
wxg left11:17
ffio left11:18
krnex1 joined11:18
timvisher left11:18
jceb joined11:18
mdw left11:18
timvisher joined11:19
ki0 joined11:19
doppo left11:19
krnex1 left11:19
ffio joined11:19
krnex left11:20
bsanford left11:20
krnex joined11:21
fuchstronaut left11:23
zZap-X is git merge the hardest part of git to figure out?11:24
frogonwheels_ zZap-X: !git11:25
errm.11:25
zZap-X: !simple11:25
gitinfo zZap-X: At its heart git is made up of many concepts that are individually simple. Getting the whole picture right is often tricky, and it is usually about breaking up the complex concept into its simple, individual parts and grokking those. Both !bottomup and !cs will help with that.11:25
frogonwheels_ zZap-X: Rebase is potentially.11:25
doppo joined11:25
chris64 joined11:25
otho joined11:25
zZap-X i am learning git as a single user, i can imagine things could get complicated if there are 100 developers working on the same project?11:25
frogonwheels_ zZap-X: or n-way merges. or rerere :)11:26
chris64 hi. Altough I know that this channel is about git mainly.. Do you know if there's a way to update a github pull request if the corresponding branch was deleted?11:26
frogonwheels_ zZap-X: git scales pretty well. learning to use it in a small group gives you a pretty good insight into using it in a large group.11:27
st0opkid left11:27
frogonwheels_ chris64: have you tried on #github ??11:28
rnsanchez joined11:28
chris64 frogonwheels_: Oh, I tried ##github only. Thank you!11:29
frogonwheels_ zZap-X: My tip is to learn to make good commits in git. My preferred way is commit early, commit often and !sausage make the branch to look good.11:29
gitinfo zZap-X: [!sausage_making] Some developers like to "hide the sausage making", transforming their commits before presenting them to the outside world. See http://sethrobertson.github.com/GitBestPractices/#sausage and !perfect11:29
nnyk left11:29
zZap-X am i right in thinking, that _BEFORE_ anything you do, always do a: git status ?11:30
bremner it doesn't hurt, but it depends what you are doing11:31
bilb_ono joined11:31
bremner for example, not much point before running "git add -p"11:31
zZap-X aye ok11:31
doppo left11:31
bremner before running "git commit -a", definitely. But I'd also say avoid git commit -a11:32
zZap-X there are 3x parts to git, [WORKING DIRECTORY] + [STAGING] + [HISTORY]11:32
doppo joined11:32
knighthawk joined11:33
zZap-X if i modify a file in working directory and commit the change, does GIT overwrite the file or does GIT edit the change in the file?11:33
grawity neither11:33
zZap-X it snapshots / commits and goes into HISTORY11:33
ciampix left11:33
grawity yes – it copies a whole new snapshot into the history11:33
zZap-X so it takes a snapshot of the file and that is stored in the .git database11:33
grawity yes11:33
zZap-X ok11:34
so that means .git repos could get quite big over time?11:34
grawity possibly, but every now and then individual objects get packed11:34
zZap-X oh compressed?11:34
grawity yeah11:34
zZap-X oh thats good11:34
grawity with delta-compression, .git/objects usually ends up like 1% or 0.1% of its original size11:35
zZap-X wow nice11:35
grawity I don't remember which, I measured it a few months ago, but I forgot11:35
zZap-X i wonder what clever guy invented git11:35
grawity the same guy who invented linux11:35
zZap-X :D11:35
osse jesus?11:35
zZap-X god11:35
grawity linux.git is around 1.3 GB, at least my copy11:36
mizu_no_oto joined11:36
zZap-X so in the old days there was subversion but that only had 1 central repro11:36
but git is distributed11:36
so git is designed for scale11:37
grawity git isn't the first DVCS – it was inspired by bitkeeper; there was also monotone (which was seriously slow though); and mercurial got created at roughly the same time as git11:37
zZap-X ok11:37
lb joined11:37
knighthawk left11:37
lb left11:37
lb joined11:37
grawity ah yeah and bzr11:37
nnyk joined11:37
grawity not that anyone cares about bzr anymore11:38
Sceorem left11:38
zZap-X when i was creating websites a few years ago, i had another directory for website testing, etc with different version of files named v1, v2, v3, a proper mess11:38
LiohAu_ left11:38
gitinfo set mode: +v11:38
zZap-X now i can have a master and devel branch11:38
doppo left11:38
zZap-X do some testing in devel branch, then once im happy merge the changes into master :D11:39
doppo joined11:39
zZap-X can git be used to make the repro have remote access without using github? so i could git clone my source code onto another box?11:41
chris64 frogonwheels_: no one there atm11:41
josuebrunel joined11:41
grawity zZap-X: yeah, you can clone any repo directly11:42
zZap-X ace, so if you want private repos you dont need to use github and have a private account11:42
grawity well, for multi-user stuff you still want something like gitolite or gogs; makes configuration easier11:42
zZap-X oh yeah11:42
grawity but for personal ones, plain old SSH will do11:42
zZap-X ive heard of gogs, looks goo11:42
good11:42
grawity as in, `git clone myserver:path/to/repo`11:43
zZap-X looks identical to github11:43
ok, so i can use ssh to clone a repo11:43
grawity (there's also Gitlab, BitBucket, etc.)11:43
Shashikant86 joined11:43
encod3 joined11:43
zZap-X yep, i heard gitlab is dog slow11:43
grawity it actually is11:43
arahael gitosis or the like, too.11:43
grawity I thought gitosis was dead11:44
zZap-X gogs looks good if i wanted to ever get social lol11:44
grawity anyway, yeah, the "git@github.com:foo/bar" addresses are just SSH11:44
and cloning over HTTP is just git-http-backend11:44
dv_ joined11:44
sgambino joined11:44
zZap-X i think its nice to see a graphical view of all the commits and branches11:44
dv_ hi11:45
zZap-X but not essential11:45
Shashikant86 left11:45
grawity for that, local tools often do a better job11:45
like tig or gitk11:45
zZap-X oh ok11:45
dv_ after rebasing my branch, I like to compare the rebased version with the upstream version of that branch to see that rebasing didnt break anything. however, other changes may have happened upstream.11:45
I know what commits contain these changes. and I compare the rebased version with the upstream one by using git diff scratch/<branch>..<branch>11:46
is it somehow possible to "reverse-apply" certain commits to the output of git diff scratch/<branch>..<branch> ?11:46
so that I do not see these changes?11:46
mizu_no_oto left11:47
timvisher left11:48
timvisher joined11:49
jstimm left11:49
t4nk531 left11:51
gechr joined11:51
ThomasLocke joined11:52
doppo left11:53
mdw_ left11:53
kristofferR joined11:54
luke_penn joined11:55
mdw joined11:55
Lomex joined11:56
Macaveli left11:57
zarel joined11:58
Darcidride joined11:58
mikiones_ joined11:58
josuebrunel left11:59
josuebrunel joined11:59
ki0 left11:59
mikiones_ left11:59
mikar joined11:59
mikiones left11:59
_rht joined12:00
mikiones joined12:00
zZap-X wonders if Linus Torvalds has got angry with developers using Git the incorrect way12:01
grawity well not much12:01
ki0 joined12:02
grawity Git doesn't have much of "the correct way" in its design12:02
zZap-X aye ok12:02
solars left12:02
italoacasas joined12:02
grawity well there are some things, but generally it was just written as a "data tracking" thing with VCS commands glued on top of it12:02
osse dv_: you want to undo your own work=12:03
grawity (see also 'cogito')12:03
osse ?12:03
josuebrunel left12:03
gechr_ joined12:05
Debyte joined12:05
threeminutemonta joined12:05
strk dv_: rewriting history ?12:06
dv_: or see git revert12:06
gechr left12:07
gechr_gechr12:07
lindenle joined12:08
otho left12:08
shymega joined12:08
st0opkid joined12:09
Sceorem joined12:09
lindenle left12:10
sdothum joined12:10
mbrzuzy joined12:10
peroht joined12:10
doppo joined12:11
Guest12711 left12:11
josuebrunel joined12:11
CheckDavid left12:12
bronson joined12:12
synthroid joined12:13
ksinkar left12:15
rwb joined12:16
doppo left12:16
bronson left12:17
doppo joined12:17
timvisher left12:17
timvisher joined12:18
rafalcpp joined12:18
sgambino left12:19
Wysi joined12:19
mkoskar joined12:20
elsevero joined12:20
zarel left12:21
Jellyg00se left12:21
rafalcpp_ joined12:22
doppo left12:22
ht joined12:22
a_thakur left12:23
doppo joined12:23
fuchstronaut joined12:23
rafalcpp left12:23
ewet left12:23
k-man how do i update my local branch so my local changes get moved to be after the latest commites on origin/master? (and what is this process called?)12:26
trudko left12:26
selckin git rebase origin/master12:26
toogley joined12:27
fuchstronaut left12:28
k-man ok that's what I was doing, but I think i have another problem, i changed the name of the branch but i need to somehow update that on the remote12:28
ncd|leeN left12:28
selckin push new branch, delete remote one12:28
k-man http://sprunge.us/JFSi12:28
jimi_ left12:28
ki0 left12:29
ewet joined12:29
selckin think you want the bottom one12:29
ivan_on_trac I want to see only the modified lines of each file in each commit. I do not want the author metadata.12:29
otho joined12:30
selckin git log --pretty:format:12:31
git log --pretty=format:12:31
Gamecubic joined12:31
ki0 joined12:32
bremner orly?12:32
a_thakur joined12:32
selckin k-man: read up on setting remote tracking branch12:32
k-man selckin, ok thanks12:32
bremner selckin: I get a whole lotta blank with that12:33
selckin bremner: add -p12:33
bremner selckin: right, good.12:33
st0opkid left12:33
st0opkid joined12:34
nikolai_ joined12:35
josue joined12:35
doppo left12:35
nikolai_ "gitk --author=Foo" seems to also show the parent (but "git log --author=Foo" not) - is this a bug? https://paste.kde.org/pqmps02fe/e49omd/raw12:36
doppo joined12:36
josuebrunel left12:36
josuejosuebrunel12:36
sathya hi. I did a rebase after making two fixup commits to the same previous commit. then I get this "It looks like you may be committing a cherry-pick. If this is not correct, please remove the file .git/CHERRY_PICK_HEAD and try again." message when running "git rebase --continue". what does it mean? am I about to throw one commit away?12:36
ivan_on_trac selckin: But I want to see the changed lines.12:37
siaw left12:37
sathya is it not possible to make multiple fixups to the same commit prior to the same "rebase -i --autosquash"?12:37
selckin ivan_on_trac: add -p12:37
ariel_17 joined12:40
st0opkid left12:40
st0opkid joined12:40
bitkiller joined12:40
mehola joined12:41
doppo left12:41
ayaz left12:41
sathya or it may be that I did two fixups to two different commits, but the second fixup addresses farther back to a sha that has changed after the rebase has reached it?12:41
I'm really guessing at random stuff here.12:41
doppo joined12:42
eletuchy joined12:42
selckin or you aborted a cherry-pick incorrectly last week12:42
MarkyC joined12:44
sathya I never did a cherry-pick.12:44
sathya aborted the rebase. it seems something's messy with my fixups.12:44
raijin left12:45
timvisher left12:45
timvisher joined12:46
axelitus joined12:46
sathya tries to fixup and rebase them one at a time and gain insight.12:46
mehola left12:46
crose joined12:47
eletuchy left12:47
st0opkid left12:48
sto0pkid joined12:48
radsy left12:48
livingstn joined12:48
sto0pkid left12:48
fuchstronaut joined12:49
ariel_17 left12:50
livingstn left12:50
doppo left12:51
algae joined12:52
doppo joined12:52
m8 joined12:52
jaguarmagenta joined12:52
sathya meh, works when I do them one at a time. so the lesson learned is that I should probably commit --fixup in the order that they address commits backwards in history.12:54
bilb_ono left12:55
subhojit777 left12:55
jaguarmagenta left12:56
abyx joined12:58
kristofferR left12:59
abyx left12:59
rscata left13:00
doppo left13:01
bsanford joined13:01
cwong_on_irc joined13:01
doppo joined13:02
algae left13:03
kam270 joined13:03
kam270 left13:03
bsanford left13:04
ariel_17 joined13:04
kam270 joined13:04
crameth joined13:04
crameth left13:04
crameth joined13:04
newjersey joined13:05
CEnnis91 joined13:05
kam270 left13:05
WayToDoor left13:05
kam270 joined13:06
JagaJaga joined13:06
peroht left13:06
madewokherd joined13:06
timvisher left13:07
doppo left13:07
strk left13:07
timvisher joined13:07
doppo joined13:08
wviana joined13:08
stantonk joined13:08
nnyk_ joined13:09
confusedguy joined13:09
wviana left13:09
wviana joined13:09
mustmodify left13:09
gitinfo set mode: +v13:10
confusedguy hi everyone, does anyone know if there's a way to check if a merge was done fastforwardly or with --no-ff?13:11
otho left13:11
osse confusedguy: if a merge was a fast-forward there won't be any trace of it.13:11
if there is a merge commit but one of the branches has no unique commits then it must have been --no-ff.13:12
otherwise, you cannot tell.13:12
confusedguy hmm13:12
nnyk left13:12
confusedguy so if it was with fast-forward the branch log won't show any additional commit, right?13:12
the "target" branch, I mean13:13
TriXLegacy joined13:13
tobiasvl well it will show the commits that were merged in, but nothing else, yes13:13
stantonk left13:13
rnsanchez left13:13
confusedguy thank you guys13:14
slappymcfry left13:14
doppo left13:14
sgambino joined13:15
TriXLegacy left13:15
confusedguy something weird happened here the other day, I merged my dev branch with no-ff into my master, but github and teamcity won't show the commits that were merged13:15
jimi_ joined13:16
diegoaguilar joined13:16
mostlybadfly left13:16
rnsanchez joined13:17
tobiasvl you pushed your master?13:17
confusedguy yes13:17
osse !lol13:18
gitinfo A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all13:18
JagaJaga left13:18
tobiasvl and github/teamcity accepted the push? it didn't reject it because it was a non-ff?13:18
!repro if you still have the output (maybe not since it was "the other day")13:19
gitinfo [!transcript] Please paste (using https://gist.github.com/ or https://vomitb.in/ ) a transcript ( https://gist.github.com/2415442 ) of your terminal session so we can see exactly what you see13:19
confusedguy it was yesterday, i'll try it out13:19
al-damiri left13:19
nnyk_ left13:19
jakwong joined13:20
italoacasas left13:20
nnyk_ joined13:20
tobiasvl (when I say that the remote might have rejected because it was non-ff, I don't mean that your merge was no-ff, but that the push would lead to a no-ff merge on the remote…)13:20
anyway, hard for us to know, see if you can dig up the output or reproduce13:20
italoacasas joined13:21
a_thakur left13:21
neonKow joined13:21
aspiers_ joined13:21
elsevero left13:22
elsevero joined13:22
a_thakur joined13:22
Macaveli joined13:22
neonKow left13:23
victortyau joined13:24
confusedguy couln't get the output, I'll try and reproduce13:24
zeroed joined13:26
a_thakur_ joined13:26
doppo joined13:27
confusedguy hey man, thanks again, gotta go13:27
bye13:27
confusedguy left13:28
timvisher left13:29
a_thaku__ joined13:29
josuebrunel left13:29
timvisher joined13:29
a_thak___ joined13:30
a_thakur left13:30
tobiasvl aight13:31
Xooi joined13:31
bremner joined13:32
bremner left13:32
bremner joined13:32
sanketdg joined13:33
chitopunk joined13:33
chitopunk left13:33
chitopunk joined13:33
chitopunk left13:33
chitopunk1 joined13:33
chitopunk1 left13:33
a_thakur_ left13:33
chitopunk joined13:33
Xooi left13:33
a_thaku__ left13:34
gechr left13:35
eletuchy joined13:36
zeroed left13:37
otho joined13:37
cwong_on_irc left13:39
texasmynsted anybody use git reset —soft very often?13:39
selckin never13:39
russo joined13:39
i7c sometimes13:39
texasmynsted It just pulls the last commits back as local changes, right?13:39
i7c It resets HEAD without changing index or working tree.13:40
Which renders the difference as "changes to be committed"13:40
augustold joined13:40
douglascorrea joined13:40
texasmynsted are the changes staged?13:41
Macaveli left13:41
i7c yup13:41
eletuchy left13:41
Dougie187 joined13:41
russoneto left13:42
abyx joined13:42
russorussoneto13:42
threeminutemonta left13:42
Macaveli joined13:42
mehola joined13:43
augustold left13:43
Wysi left13:44
Wysi joined13:44
youser joined13:47
mehola left13:48
netcarver left13:48
mischat left13:48
mischat joined13:49
timvisher left13:51
timvisher joined13:51
mdw left13:52
Sonderblade left13:53
Raging_Hog left13:54
dhollinger joined13:54
rwb left13:54
rwb joined13:55
davisonio joined13:58
josuebrunel joined13:58
lb texasmynsted more on reset and the manipulation options with it can be viewed in this talk. https://www.youtube.com/watch?v=V7RIvj9tB64 slides are here: https://speakerdeck.com/schacon/a-tale-of-three-trees13:58
bremner left13:58
bremner` joined13:58
fmcgeough joined13:58
bremner` left13:58
bremner` joined13:58
texasmynsted :-) Thank you13:59
mattfoo left13:59
bremner` left14:01
bremner joined14:01
bremner left14:01
bremner joined14:01
ash_workz joined14:01
IWishIKnew joined14:01
mizu_no_oto joined14:02
JeroenT left14:03
bremner left14:03
bremner joined14:03
bremner left14:03
bremner joined14:03
algun left14:04
mattfoo joined14:05
ewet left14:05
a_thak___ left14:05
jokke hi14:05
testild left14:06
Sonderblade joined14:06
jokke i kind of messed up my history by trying to keep it linear using rebase on a branch. Is it somehow possible to merge only unique and missing commits from another branch14:06
youser left14:07
JeroenT joined14:07
threeminutemonta joined14:07
mizu_no_oto left14:08
ash_workz left14:09
clmsy left14:10
groundnuty hey, I'm having tround understaiding the -all flag in fetch14:10
I have a bare repo. I do it fetch --prune --tags --all14:11
and I would expect that all tangs/brances will be updated14:11
lindenle joined14:11
groundnuty what I get is just one line: * branch HEAD -> FETCH_HEAD14:11
Gonzo89_ joined14:11
groundnuty insted when I did git fetch origin +refs/heads/*:refs/heads* --tags --prune14:12
it worked14:12
I thought that --all will cover all refspecs14:12
mizu_no_oto joined14:12
Gonzo89 left14:12
blue_lizzard joined14:14
bronson joined14:14
troulouliou_div2 left14:14
fbwnd left14:14
stantonk joined14:15
timvisher left14:15
a_thakur joined14:15
tobiasvl all remotes14:15
stantonk left14:15
tobiasvl --all: Fetch all remotes.14:15
groundnuty tobiasvl: yes I did read the manual :)14:15
tobiasvl hehe. all righty.14:15
timvisher joined14:15
mizu_no_oto left14:15
lindenle left14:15
groundnuty I'm just saying it's not working as expected :(14:15
or I miss something14:16
stantonk joined14:16
italoacasas left14:16
nZac joined14:16
subhojit777 joined14:16
groundnuty git fetch origin '*:*' --tags --prune, should be the same as git fetch --all --tags --prune, yes?14:17
ncd|leeN joined14:17
nZac I am trying to pull down all the tags for a specific repo on Github. I see the tag on the site but the tags is not appearing in my local list of tags. Any thoughts?14:17
italoacasas joined14:18
bronson left14:18
tobiasvl groundnuty: hmmmmmm let's see if !fetch4 is relevant14:20
gitinfo groundnuty: [!fetchfour] [pre 1.8.4 only] We recommend against using 'git fetch/pull <remote> <refspec>' (i.e. with branch argument), because it doesn't update the <remote>/<branch> ref. The easy way to fetch things properly is to get everything: 'git fetch' or 'git pull' are sufficient if you have one remote; otherwise we recommend 'git fetch <remote>' (plus 'git merge <remote>/<branch>' if you wanted to pull/merge).14:20
tobiasvl maybe not14:20
but maybe for nZac14:20
nZac: what command did you run?14:20
nZac tobiasvl: git fetch <remote> --tags14:20
groundnuty no no no guys14:21
stantonk left14:21
groundnuty I started with clone --bare14:21
got a bare repo14:21
i call git fetch --all --tags --prune14:21
and changes are not fetched14:21
nZac tobiasvl: when I run git fetch --all --tags I get the tags from a different remote, while in this case that works, I was trying to get them from the upstream not my fork.14:22
col joined14:22
nZac Are tags only connected to the "origin" remote. My understanding was the "origin" remote name had no special meaning.14:22
kareeoleez left14:23
ferr joined14:23
guampa joined14:23
inflames left14:23
espindola joined14:24
i7c jokke, git will notice if commits don't introduce changes and will ask you if you want to skip them or make them empty commits when doing rebase or cherry-pick.14:24
stantonk joined14:24
i7c jokke, however, if you apply them in different order it might get all screwed up. :)14:25
That is, some patches might not be applicable.14:25
jokke, how exactly did you mess up the history?14:26
javaJake Hey guys. Is there a way to ask git to apply the difference between two commits as a commit on my current branch?14:26
jokke meh i just merged with --squash14:26
javaJake git diff hash1..hash2 | git apply #?14:26
j`ey joined14:26
anli_ joined14:26
j`ey is there an easy way to use the hashes from git reflog and look at the changes to a certain file?14:27
anli_ git filter-branch --tree-filter 'git rm --cached .;git add .' -- HEAD gave me the error message fatal: bad revision 'rm', why?14:27
i7c j`ey, git show <hash>:file14:27
fuchstronaut left14:27
i7c ah changes14:27
j`ey Ill just script the output of git reflog14:27
i7c j`ey, git show <hash> -- file14:28
j`ey nvm14:28
i7c what?14:28
grawity anli_: if you're running this from Windows cmd.exe/powershell, only " " will work14:28
anli_ Ah, must run from bash14:28
i7c j`ey, git show $(git branch@{7}) -- file14:28
nnyk_ left14:28
grawity bash accepts both kinds of quotes, cmd.exe only single quotes14:28
i7c derp14:28
grawity er, only double quotes14:28
j`ey: git reflog -p14:28
i7c without the $() ofc14:29
I'm being silly right now.14:29
j`ey grawity: cool thanks14:29
should have guessed -p14:29
troulouliou_div2 joined14:29
al-damiri joined14:30
a_thakur left14:30
anli_ Running git filter-branch --tree-filter 'git rm --cached -r .;git add .' -- HEAD from bash, did not get any error message but I did not get rid of an ignored file14:30
mrkat left14:30
anli_ Does git add need a recursive flag as well?14:30
eletuchy joined14:31
selckin tracked files are never ignroed14:31
anli_ But they become untracked when I git rm --cached -r .14:31
jstimm joined14:31
selckin possibly14:32
anli_ Why possibly?14:32
selckin globally ignored? .git/info/exclude?14:32
anli_ ...14:32
My problem is that a file that should be ignored by the .gitignore file is not14:33
selckin and when did you add it to gitignore, in the first commit?14:33
fstd joined14:33
anli_ yes14:33
Kicer86 joined14:34
timvisher left14:34
eletuchy left14:35
timvisher joined14:35
j`ey left14:35
troulouliou_div2 left14:36
stantonk left14:36
ash_workz joined14:36
redasus2 left14:38
kpease joined14:38
IWishIKnew left14:39
redasus left14:39
a_thakur joined14:40
sangy joined14:40
crameth left14:41
elsevero left14:42
anli_ git filter-branch -f --tree-filter 'git rm --cached -r .' seems to not alter the tree14:42
elsevero joined14:42
selckin this my remove-from-history script: git filter-branch --index-filter "git rm --cached --ignore-unmatch ${pattern}" --tag-name-filter cat -f -- --all14:43
lss9 left14:43
stantonk joined14:44
solars joined14:44
anli_ It seems like git filter-branch stages all unstaged files automatically for every commit14:44
staticshock joined14:44
mbrzuzy left14:45
solars can anyone tell me why git mergetool -t kdiff3 returns without opening kdiff3 and I still have an incomplete merge left? what does that mean?14:45
Macaveli left14:45
selckin no output?14:45
solars nope14:46
dotpot left14:46
solars I have the merge files left (.BACKUP, .orig, etc)14:46
troulouliou_div2 joined14:47
selckin are you sure you still have a conflict, sometiems kdiff3 can automerge it where git can't, then it doesn't open the gui14:47
solars I thought the files disappear then?14:47
do I have to mark it?14:47
hobodave joined14:47
puff Hm,I have this nifty line in my .bash_profile some my shell prompt always shows me what branch I'm in. I'd like to add a bit that shows me how long it's been since I did a git pull on that branch.14:47
deavid left14:47
bilb_ono joined14:47
solars selckin, ^14:48
shiriru joined14:48
selckin solars: no they stay14:48
puff Is there an existing shell script for that?14:48
selckin solars: git status will tell you14:48
solars selckin, git status shows the .orig etc files - how can I complete the merge now?14:48
selckin puff: there a million fancy git prompts on google, one might have something like that14:48
staticshock left14:49
puff selckin: Thanks.14:49
nidr0x joined14:49
A8316-Guest joined14:49
deavid joined14:49
Wysi left14:49
selckin solars: status will say if something is still in conflict state, if its just the .orig file untracked etc, you can ignroe that and just merge --continue (or commit)14:49
puff Anyone use IDEA's git support? I tried it out the other night, but there appears to be no IDEA equivalent of "git status" other than browsing through the file hiearchy pane (and expanding all of your hierachries).14:49
anli_ left14:49
nidr0x left14:49
mostlybadfly joined14:49
gsingh joined14:49
solars selckin, its BACKUP BASE REMOTE LOCAL orig14:50
selckin puff: alt-9 i think14:50
a3Dman left14:50
selckin solars: if you can redo the merge and compare status before and after mergetool you will see (i think)14:50
shiriru left14:50
elsevero left14:50
solars selckin, hm okay14:51
justinqblake joined14:53
jaguarmagenta joined14:53
efco joined14:53
nnyk_ joined14:54
justinqblake left14:54
cyan__ left14:54
knighthawk joined14:54
a3Dman joined14:54
mbrzuzy joined14:55
fragMent1 left14:55
kilo_bravo joined14:55
chrisshattuck joined14:55
solars left14:55
gsingh left14:55
acolson left14:55
timvisher left14:55
Thorn__ joined14:55
timvisher joined14:56
racket joined14:56
fragMental joined14:56
kam270 left14:57
Noldorin joined14:57
fragMental I wanted to amend the second-last commit, so I did `git stash; git reset --hard HEAD^; git stash apply; git commit --amend; git stash drop` now I'm kind of stuck on how to apply the last commit again. I did `git log` before all this, so I have the sha of it, I just don't know which command to use.14:57
AndroidVaan left14:57
Thorn left14:57
jaguarmagenta left14:57
troulouliou_div2 left14:57
A8316-Guest left14:57
selckin cherry-pick it14:58
nnyk_ left14:58
selckin and next time, create a new commit with the changes you want to amend, and use rebase -i to combine it with the previous commit14:59
puff selckin: Thanks.14:59
nnyk_ joined14:59
subhojit777 left14:59
bango2 joined14:59
crose left14:59
jceb left15:00
wrouesnel1 joined15:01
lamppid left15:03
synthroid left15:04
johnwhitton joined15:04
chrisshattuck left15:05
madewokherd left15:07
MarkyC left15:08
ThomasLocke left15:09
MarkyC joined15:09
fragMental selckin: Thank you!15:09
todd_dsm_w joined15:10
todd_dsmw left15:10
todd_dsm_w left15:10
todd_dsm_w joined15:11
todd_dsm joined15:11
ki0_ joined15:11
Debyte left15:11
todd_dsm_w left15:11
mdw joined15:11
todd_dsm left15:11
Raging_Hog joined15:11
todd_dsm joined15:12
lindenle joined15:12
WayToDoor joined15:12
kpease left15:13
Sceorem left15:14
ki0 left15:14
Alienpruts left15:14
h12o joined15:14
timvisher left15:15
ki0_ left15:15
JeroenT left15:15
mrkat joined15:16
thiago joined15:16
ki0 joined15:16
solars joined15:17
staticshock joined15:17
lindenle left15:17
timvisher joined15:17
threeminutemonta left15:17
shymega left15:18
ki0_ joined15:19
ki0_ left15:19
ki0 left15:19
gsingh joined15:20
ki0 joined15:20
_rht left15:20
Bruce____ joined15:20
nnyk_ left15:20
redasus2 joined15:21
redasus joined15:21
a_thakur left15:24
deadnull joined15:24
davisonio left15:24
eletuchy joined15:25
Bruce____ left15:25
infra-red joined15:26
nnyk_ joined15:26
MrWoohoo joined15:26
ki0 left15:27
i7c selckin helps ALL the people? \o/15:27
fuchstronaut joined15:28
davisonio joined15:29
eletuchy left15:29
Eryn_1983_FL left15:30
[Brain] left15:30
kits left15:30
MadHatter42 left15:30
Euus joined15:31
Balliad left15:32
dreiss joined15:32
fuchstronaut left15:32
dan2k3k4 left15:33
akushner joined15:33
diegoaguilar left15:35
Euus left15:36
Raging_Hog left15:37
timvisher left15:37
timvisher joined15:37
Tylak joined15:39
infra-red left15:39
kogol joined15:39
a_thakur joined15:39
Macaveli joined15:39
solars left15:40
shymega joined15:40
blue_lizzard left15:40
Macaveli left15:40
solars joined15:41
kogol left15:42
deadnull left15:42
ariel_17 left15:43
redasus left15:43
redasus2 left15:43
tyreld joined15:44
mehola joined15:45
synthroid joined15:45
IWishIKnew joined15:47
diegoaguilar joined15:47
lindenle joined15:48
stantonk left15:48
ueberall joined15:48
a_thakur left15:49
mehola left15:49
Macaveli joined15:50
gsingh left15:50
whomp joined15:51
cwong_on_irc joined15:51
stasmakarov left15:51
raijin joined15:52
jceb joined15:52
gsingh joined15:52
SporkWitch left15:52
ahmed_elgabri left15:52
ochorocho__ joined15:53
solars left15:53
luke_penn left15:53
Gonzo89_ left15:55
mbrzuzy left15:56
Darcidride left15:57
victortyau left15:57
kpease joined15:58
timvisher left16:00
timvisher joined16:00
soee_ joined16:00
whomp left16:01
s00pcan left16:01
Macaveli left16:01
livingstn joined16:01
armyriad left16:01
MarkyC_ joined16:01
armyriad joined16:02
Thorn__Thorn16:02
Walex joined16:03
madewokherd joined16:03
MarkyC left16:03
SimonNa joined16:03
ToBeCloud joined16:03
gitinfo set mode: +v16:03
stantonk joined16:05
IWishIKnew left16:05
elastix joined16:05
algun joined16:06
bollullera left16:07
jceb left16:07
tlaxkit left16:09
_rht joined16:09
s00pcan joined16:10
specing joined16:10
rdvdet left16:11
sathya left16:11
Lewoco_ joined16:11
staticshock left16:11
ciampix joined16:11
Bruce____ joined16:12
stantonk left16:13
Lewoco__ left16:14
weox left16:14
Virox Is it just me or does it feel like a bug that `git clean -fd` would wipe out a folder that's marked in .gitignore ?16:14
crose joined16:14
Virox I could `git clean -i` but I feel like -fd should be fine16:15
bilb_ono left16:15
imachuchu joined16:16
bronson joined16:16
nnyk_ left16:16
selckin it doesn't wipe out gitignored files16:16
_ikke_ git clean should honor .gitignore, unless -x is passed16:16
IWishIKnew joined16:17
chrisshattuck joined16:17
raijin left16:17
freimatz left16:18
Virox Interesting... So in my .gitignore I have "Carthage/Build" which is a directory that contains a bunch of .framework files Any ideas why it's still trashing those .framework files?16:19
staticshock joined16:19
timvisher left16:20
Virox So I need to explicitly add .framework to .gitignore?16:20
timvisher joined16:20
thiago you need to explicitly add anythiing that you want ignored.16:20
mbrzuzy joined16:20
nZac left16:20
bronson left16:21
Virox I assumed adding the containing folder would be enough... I guess not16:21
thiago what do you mean by "trashing" ?16:21
Virox Its deleting them all16:21
chrisshattuck left16:21
thiago pastebin the output of git status when those files/dirs are present16:21
hwrdprkns joined16:22
SporkWitch joined16:22
chrisshattuck joined16:23
mdw left16:23
PCatinean left16:23
_ikke_ For me it works as it should16:24
ncd|leeN left16:24
thiago which means that there's something that Virox didn't tell us16:25
Linkandzelda just did my first fork merge... what an amazing tool16:25
Virox ;D16:25
stantonk joined16:25
Virox Okay lemmie rebuild a few things, try again then paste the output16:25
dsdeiz left16:26
blue_lizzard joined16:26
_ikke_ mkdir foo && touch foo/bar && touch baz && echo -e "foo\n.gitignore" >.gitignore && git clean -fd -> removing bar16:26
sorry16:26
dsdeiz joined16:26
_ikke_ removing baz16:26
so foo/bar is still there16:26
raijin joined16:26
thiago what happens if you create a file inside foo and track it?16:26
_pix left16:28
dsantiago left16:29
mikar left16:29
jimi_ left16:30
ueberall left16:30
stantonk_ joined16:31
ciampix left16:32
durham joined16:32
durham left16:32
deadnull joined16:32
encod3 left16:32
ueberall joined16:33
durham joined16:33
stantonk left16:34
deadnull left16:34
ueberalluebera||16:35
dsdeiz_ joined16:35
deadnull joined16:35
gsingh left16:35
dsdeiz left16:36
gsingh joined16:37
muthu left16:37
subhojit777 joined16:37
deadnull left16:38
armyriad left16:38
armyriad joined16:38
whomp joined16:39
kadoban joined16:39
dsdeiz_ left16:39
dsdeiz joined16:40
ariel_17 joined16:40
dreiss left16:40
wrouesnel1 left16:41
editshare-ericf joined16:41
timvisher left16:42
bernardio joined16:43
timvisher joined16:43
mikiones left16:45
armyriad left16:45
aard_ joined16:45
nitin joined16:45
mehola joined16:45
armyriad joined16:45
ManDay left16:46
armyriad left16:46
whomp left16:46
Lomex left16:47
acetakwas left16:47
armyriad joined16:48
jstimm left16:49
mehola left16:50
Virox So this is what I get https://gist.githubusercontent.com/JamieWhite/6f415eef859902c17bba5e93ac124b9c/raw/2cf6e724cb44236766c5ff60683c90c2a7a719f7/blah16:50
I'm guessing I need Carthage in the .gitignore16:50
t-mart_ joined16:50
_ikke_ What do you have in your .gitignore16:51
jstimm joined16:51
Virox https://gist.githubusercontent.com/JamieWhite/d1949c691017bd2d3f323c2fb1b5023a/raw/ba116bf6be741fb1330ce04f0947cec174d3697e/test16:51
nitin left16:51
bilb_ono joined16:52
_ikke_ And what are the exact contents of Carthage16:52
?16:52
Virox The two folders Checkout and Build16:52
_ikke_ And do they contain files16:53
?16:53
ffio left16:53
solars joined16:53
Virox Build has folders Mac and iOS which both contain .framework files16:53
jaguarmagenta joined16:53
srcerer joined16:54
irqq left16:54
t-mart__ left16:54
glen joined16:54
glen hey. i'm abit confused about commit author encoding16:54
b1tchcakes joined16:54
chll left16:54
glen this commit looks okay in github https://github.com/file/file/commit/8e9094a92c4eee790a9bd8910fceada2677f0c06.patch16:54
ffio joined16:54
glen and with git client (git show)16:54
SteffanW2 joined16:55
glen but if i look with fast export, i see latin1 string16:55
➔ git fast-export --all|grep -a glen@pld|less -r16:55
author Elan Ruusam<E4>e [email@hidden.address] 1461687883 +000016:55
and so it broken on travis too https://travis-ci.org/file/file/builds/12588313116:56
stantonk_ left16:56
glen i used git cvsimport to convert it when user file was latin1 encoded:16:56
git -c i18n.commitencoding=iso8859-1 cvsimport ...16:57
stantonk joined16:57
Lomex joined16:57
thiago left16:58
glen now, should i worry, do it differently? complain to travis-ci?16:58
jaguarmagenta left16:58
hwrdprknshwrd[away]16:58
synthroid left16:59
blue_lizzard left16:59
glen git-commit man page says i'm doing all correctly16:59
nitin joined17:00
hwrd[away] left17:00
hwrdprkns joined17:00
peroht joined17:01
chrisshattuck left17:02
jagob joined17:02
Lomex left17:02
Synthead left17:02
Synthead joined17:03
gsingh left17:04
otho left17:04
Virox _ikke_: Nailed it by adding `Carthage` to .gitignore17:05
Thanks for your help !17:05
timvisher left17:05
zarel joined17:05
timvisher joined17:05
gsingh joined17:06
TomyWork left17:06
cyphase left17:06
gsingh left17:07
khelkun left17:07
gsingh joined17:08
cyphase joined17:09
cyphaseGuest3955317:09
noteness left17:11
sagerdearia left17:11
CrypticGator left17:12
nitin left17:12
josuebrunel left17:12
zarel left17:12
subhojit777 left17:14
Eryn_1983_FL joined17:16
toogley left17:16
efco left17:17
ZGD left17:18
noteness joined17:18
shmuli joined17:18
bernardio left17:20
slayerjain joined17:20
dsantiago joined17:20
aspiers_ left17:22
Guest39553 left17:22
cyphase_ joined17:23
shmuli left17:23
TSS_ joined17:24
mdw joined17:24
d4rklit3 joined17:24
timvisher left17:25
rominronin left17:25
timvisher joined17:25
zarel joined17:25
IWishIKnew left17:27
PryMar56 joined17:28
cyphase_cyphase17:28
rominron_ joined17:29
rkazak left17:29
Macaveli joined17:29
WayToDoor left17:29
fuchstronaut joined17:29
Darcidride joined17:30
dreiss joined17:32
marcogmonteiro left17:32
imachuchu left17:32
zarel left17:33
peroht left17:33
oink joined17:33
imachuchu joined17:34
pantsman- joined17:34
fuchstronaut left17:34
gsingh left17:36
elastix left17:36
DanZ3 joined17:36
cagmz joined17:36
davisonio left17:37
rominron_rominronin_17:37
gsingh joined17:37
elastix joined17:37
synthroid joined17:37
rominronin_rominronin17:38
annoymouse joined17:38
elsevero joined17:38
gitinfo set mode: +v17:38
jimi_ joined17:39
elastix left17:39
ferr left17:40
attila_ left17:40
Isla_de_Muerte joined17:41
whomp joined17:41
nnyk_ joined17:41
ZeDestructor left17:43
raijin left17:43
xelxebar left17:43
hwrdprknshwrd[away]17:43
teresko joined17:44
realz joined17:44
thiago joined17:44
hwrd[away]hwrdprkns17:44
NwS left17:44
jakwong left17:44
ZeDestructor joined17:45
ZeDestructor left17:45
ZeDestructor joined17:45
oink does anyone know if there are any restrictions on which repos can be imported with git-fetch? the man pages make it sound like branches from any repo can be added to any project; but that doesn't make any sense to me; shouldn't there be some rules for making sure that only branches with a common ancestor to the current project can be downloaded?17:46
skunkz joined17:46
tobiasvl oink: that's correct, they need a common ancestor17:46
timvisher left17:47
skunkz Hi everyone, I'm new to big project management, releases tracking and stuff.. Are there any "best practices" or general rules to follow ?17:47
Trieste joined17:48
preaction as little as possible, but no littler17:48
Eugene skunkz - !flow and !semver are good reads17:48
gitinfo skunkz: [!gitflow] The description of the gitflow branch workflow model is at http://nvie.com/posts/a-successful-git-branching-model/ while a tool to help implement this workflow is at https://github.com/petervanderdoes/gitflow See http://sethrobertson.github.com/GitBestPractices/#workflow for other workflow suggestions/references17:48
skunkz: The Semantic Versioning standard is widely used for version numbering. You may find it useful when creating git tags: http://semver.org/17:48
tobiasvl oink: that is, you can fetch (although you'll get a warning) from a remote branch with no common ancestor17:48
into a remote-tracking branch17:48
but it'll effectively be an orphan branch, and it can't be merged17:49
TomyLobo joined17:49
kdeal joined17:49
timvisher joined17:49
Seveas it can absolutely be merged17:49
tobiasvl oh wait17:49
yes it can17:49
skunkz thanks Eugene that's the kind of readings I needed17:49
Bruce____ left17:50
oink I think I get it now; If I want to integrate a module stored in an unrelated remote repository with my current branch; I would fetch it, ignore the warning, and then merge it with my current branch?17:51
Bruce____ joined17:51
tobiasvl !xy17:51
gitinfo Woah, slow down for a bit. Are you sure that you need to jump through that particular hoop to achieve your goal? We suspect you don't, so why don't you back up a bit and tell us about the overall objective...17:51
Dyonisos joined17:52
Macaveli left17:53
jstimm left17:53
oink I don't intend to use it this way, I'm just reading through the documentation and I wanted to make sure I didn't misinterpret it17:54
oink left17:55
puff Hm, I just made some changes and then realized that I should have done this on a feature branch. If I recall/understand correctly, I should: 1) git stash 2) git checkout -b newfeaturebranch, 3) git stash pop, 4) git add/commit my changes.17:55
Is the above correct?17:55
Sasazuka joined17:56
hwrdprknshwrd[away]17:56
xelxebar joined17:56
hwrd[away] left17:57
Sasazuka left17:58
nidr0x joined17:59
SwiftMatt joined17:59
subhojit777 joined17:59
Eugene puff - !float18:00
gitinfo puff: If you have made a change in your working directory and have NOT YET COMMITTED, you may "float" that change over to another (`git checkout oldbranch`) or new (`git checkout -b newbranch`) branch and commit it there. If the files you changed differ between branches, the checkout will fail. In that case, `git stash` then checkout, and `git stash apply` and go through normal conflict resolution.18:00
hwrdprkns joined18:00
Eugene Assuming you start your feature branch from HEAD, no stash is needed.18:01
hust921 joined18:01
leonarth joined18:02
kdeal left18:04
elsevero left18:04
davisonio joined18:04
elsevero joined18:04
IWishIKnew joined18:04
russo joined18:04
tvw joined18:05
nydel07 left18:05
stantonk_ joined18:05
rominronin left18:05
stantonk left18:05
clivejo joined18:06
russoneto left18:07
russorussoneto18:07
clivejo hi folks, Im trying to copy a collection of git archives to my local computer and then to a new host, anyone know of a fast easy way to do this?18:08
col_ joined18:08
ojacobson rsync18:09
timvisher left18:09
timvisher joined18:09
clivejo ojacobson: can you point me in the direction of how to do that?18:10
acton left18:10
ericvw joined18:10
col__ joined18:10
mwhooker joined18:10
ojacobson rsync -rza --progress path/to/sources/ user@host:path/to/destination/ # trailing slashes matter18:10
man rsync for an explanation of the details18:10
acton joined18:10
stantonk joined18:11
stantonk_ left18:11
col left18:11
voice_of_me joined18:12
mdw left18:12
ivan_on_trac which the path of a server-side file ("bare").18:12
?18:12
irqq joined18:12
nofacade joined18:13
_ikke_ ivan_on_trac: ?18:13
col_ left18:13
mbrzuzy left18:14
stantonk left18:15
MattMaker joined18:16
hwrdprkns left18:16
synthroi_ joined18:17
hwrdprkns joined18:17
gsingh left18:17
jakwong joined18:17
DanZ3 left18:17
mizu_no_oto joined18:18
bronson joined18:18
nydel07 joined18:18
mikiones joined18:19
Scriptonaut left18:19
digidog left18:20
synthroid left18:20
stantonk joined18:20
_rht left18:20
chris64 left18:20
jost joined18:21
hwrdprkns left18:22
bronson left18:22
moei left18:23
przemoc left18:23
sauvin left18:23
stantonk_ joined18:24
Sasazuka joined18:24
stantonk left18:24
jbitdrop left18:25
irqq left18:25
_rht joined18:26
xcesariox left18:26
leonarth left18:27
stantonk_ left18:28
mbrzuzy joined18:28
josuebrunel joined18:28
IWishIKnew left18:28
subhojit777 left18:30
toogley joined18:31
fuchstronaut joined18:31
wviana left18:32
timvisher left18:32
moei joined18:32
timvisher joined18:33
wviana joined18:33
stantonk joined18:34
newjersey left18:34
newjersey joined18:35
fuchstronaut left18:36
NeverDie_ joined18:37
NeverDie left18:38
nwkj86 joined18:38
Zeranoe joined18:39
diegoaguilar left18:39
Zeranoe Is there a git command that could show me the date of a specific commit?18:39
Seveas Zeranoe: git show commit-sha118:41
NeverDie joined18:41
NeverDi__ joined18:43
stantonk_ joined18:43
stantonk left18:43
dsantiago left18:43
NeverDie_ left18:44
dsantiago joined18:44
shinnya joined18:44
ahmed_elgabri joined18:45
newjersey left18:45
leehambley joined18:45
NeverDie left18:46
dsdeiz left18:46
aspiers_ joined18:47
infra-red joined18:47
stantonk_ left18:47
Joanna___ joined18:47
digidog joined18:47
NeverDie joined18:47
stantonk joined18:47
oregonduckman joined18:48
leehambley hi all - I wonder if someone can confirm something for me? "Refs don't have their own datetime" -- I'm trying to get the time a *ref* created with `upadte-ref ...` (e.g it's specifically not a tag) if I run something like `git log -1 --format=%ai refs/myrefs/foo` does that print the time of what "foo" points to (it must, as far as I understand) as the `.git/refs/myrefs/foo` contains nothing but a treeish sha118:49
infra-red left18:49
ojacobson leehambley: git log prints info from commits (normally) or the reflog (with the right option)18:50
NeverDi__ left18:50
Seveas leehambley: if you have enabled the reflog for that ref or all refs, it will have that information18:51
ojacobson there is no meaningful record -at all- of the ref creation date -- loose refs have a ctime and mtime in the filesystem, but they're not guaranteed to have meaningful values, and they go away when the ref gets transported or packed18:51
leehambley alright, thanks for that confirmation. does that hold true for annotatied tags too ?18:51
username17 left18:51
m0viefreak joined18:51
peepsalot joined18:52
Seveas leehambley: the reflog bit holds true for those, but annotated tags do store time of creation18:52
leehambley cool, so probably there's something I can do to make an "annotated ref"18:52
or is the annotation of tags a special case ?18:52
noteness left18:52
Seveas they're a special case18:53
stantonk left18:53
Seveas an annotated tag is a combination of a tag object (that's the bit that has the date) and a tag ref18:53
ojacobson !xy18:53
gitinfo Woah, slow down for a bit. Are you sure that you need to jump through that particular hoop to achieve your goal? We suspect you don't, so why don't you back up a bit and tell us about the overall objective...18:53
leehambley we have some automated options that may run one or more times against the same commit18:54
ferr joined18:54
jaguarmagenta joined18:54
timvisher left18:55
dhollinger left18:55
leehambley we'd like to record the results of that in refs in the repo (at least, we'd like to avoid tracking another file in the repo, subject to conflicts, etc), and since it's 1:1 mapped to which ref was "current" at the time, we need the "time of the tag/ref/etc" not the "time of the referenced commit"18:55
timvisher joined18:55
leehambley bah s/automated options/automated processes/g sorry18:55
Seveas That sounds backwards18:56
leehambley :) alright, nice to have a second opinion18:56
ojacobson what about notes?18:56
Seveas you're automation processes what the ref points to, not the ref itself18:56
so why not 'attach' the results to what the ref points to? As with notes like ojacobson says18:57
SteffanW2 left18:57
leehambley I'd have to read into notes abit18:57
abyx left18:57
knighthawk left18:57
noteness joined18:57
leehambley `git notes append .... `seems like it might be decent for m18:59
my usecase*18:59
jaguarmagenta left18:59
jparness joined18:59
knighthawk joined19:00
stantonk joined19:00
nidr0x left19:01
dhollinger joined19:01
knighthawk left19:01
jparness left19:03
oregondu_ joined19:03
ojacobson You could also take the model notes use and alter it - git ultimately doesn't care what you do with the tools it gives you19:04
oregonduckman left19:04
leehambley absolutely, I was just wondering what the plumbing behind notes looked like19:04
oregondu_ left19:04
leehambley I'd assume that's also just `update-ref`19:04
oregonduckman joined19:05
_ikke_ It's different things19:05
nidr0x joined19:05
_ikke_ it involves creating trees and commit objects19:06
nilg joined19:06
leehambley alright, I thought so19:06
actually, otherwise where is the info :)19:06
stantonk left19:06
stantonk joined19:06
robbyoconnor left19:06
Joanna___ left19:07
CrypticGator joined19:08
ferr left19:10
multi_io left19:10
ferr joined19:10
racket left19:10
SwiftMatt left19:10
multi_io joined19:11
b1tchcakes left19:11
nnyk_ left19:12
abyx joined19:12
b1tchcakes joined19:12
deadnull joined19:12
akiva joined19:13
Zeranoe left19:13
oregonduckman left19:14
deadnull left19:14
oregonduckman joined19:14
deadnull joined19:15
deadnull left19:15
dsdeiz joined19:15
dsdeiz left19:15
dsdeiz joined19:15
sdothum left19:15
knighthawk joined19:15
oregonduckman left19:16
sdothum joined19:16
timvisher left19:18
cwillu_at_work left19:18
timvisher joined19:18
cwillu_at_work joined19:19
knighthawk left19:20
mikiones left19:20
DanZ3 joined19:21
mikiones joined19:21
jimi_ left19:22
IWishIKnew joined19:22
przemoc joined19:23
hust921 left19:23
staticshock left19:24
Sound joined19:25
stantonk_ joined19:29
rahmen86 joined19:30
NwS joined19:30
mwhooker left19:32
bronson joined19:32
stantonk_ left19:32
CrypticGator left19:32
stantonk left19:32
stantonk joined19:32
rahmen86 Hi! I've setup my git repo on my debian server. On my windows computer I now want to push my changes to that server. But instead of providing username and pass I want to work with ssh keys. Can I get some help here? Thanks!19:33
Isla_de_Muerte left19:33
mariuscc left19:35
javaJake puff: I use IDEA's git tool19:36
puff: use the 'Version Control' tool window19:36
puff: that's IDEA's equivalent of 'git status'19:36
Cassiopaya joined19:37
sagerdearia joined19:38
stantonk left19:40
timvisher left19:41
weox joined19:41
jeffreylevesque joined19:41
blue_lizzard joined19:41
timvisher joined19:42
IlNominePatre joined19:42
apotry joined19:43
m8 left19:43
mwhooker joined19:46
barduck joined19:46
JBlazeCoder21 joined19:48
toogley left19:48
d5sx43 joined19:48
annoymouse left19:49
bremner left19:49
soee joined19:49
bremner joined19:49
bremner left19:49
bremner joined19:49
NeonSynth joined19:50
nofacade left19:51
isxek left19:51
knighthawk joined19:51
barduck left19:52
skelterjohn left19:52
gsingh joined19:52
AndroidSynth joined19:53
bernardio joined19:53
bernardio left19:53
soee_ left19:54
livingstn left19:54
netj left19:54
ajf- joined19:54
moei left19:55
deadnull joined19:55
deadnull left19:55
blahdodo left19:55
yarnfive8 left19:56
blue_lizzard left19:56
stantonk joined19:56
akushner_ joined19:56
netj joined19:57
Shentino joined19:57
tyreld left19:58
akushner left19:58
jon-mac left19:58
AndroidSynth left19:58
stantonk left19:59
NeonSynth left19:59
blahdodo joined20:01
diegoviola joined20:02
timvisher left20:02
timvisher joined20:03
bremner` joined20:03
bremner` left20:03
bremner` joined20:03
noteness left20:04
bremner left20:04
Bruce____ left20:04
newjersey joined20:04
newjersey left20:04
bremner`bremner20:05
stantonk joined20:05
solars left20:05
wviana left20:05
d5sx43 left20:05
voice_of_me left20:05
zacts joined20:06
aard_ left20:06
nidr0x left20:06
voice_of_me joined20:07
UrsoBranco joined20:07
nidr0x joined20:07
Borkr left20:07
noteness joined20:10
basiclaser joined20:10
jeffreylevesque left20:10
puff javaJake: Thanks.20:11
tyreld joined20:11
puff rahmen86: Did you get that sorted out?20:11
leprechau joined20:11
puff rahmen86: I wrote this thing about setting up ssh keys for using rsync, if you follow the steps it'll work for git too.20:12
Sound left20:12
puff rahmen86: http://www.darksleep.com/notablog/articles/Using_ssh_agent20:13
bronson left20:13
peroht joined20:13
staticshock joined20:13
CussBot_ joined20:13
CussBotGuest7550820:13
Guest75508 left20:13
CussBot_CussBot20:13
davisonio left20:13
nfk joined20:14
akiva left20:14
voice_of_me left20:14
deadnull joined20:15
puff Eugene: Wait, so you're saying that until the first commit on a new branch, I can change branches without disturbing my working tree?20:16
Eugene: Is there any difference between doing it with float and doing it with stash?20:16
Eugene puff - checkout will do anything you ask, unless it interferes with uncommited changes(in which case it will tell you to stash).20:17
mizu_no_oto left20:17
Eugene puff - in most cases this means that yes, you can make a new branch to commit your not-yet-commited changes onto.20:17
AndroidSynth joined20:18
AndroidSynth left20:18
leonarth joined20:18
AndroidSynth joined20:18
AndroidSynth left20:18
cdg joined20:18
AndroidSynth joined20:19
AndroidSynth left20:19
deadnull left20:19
Eugene stash actually creates a new commit(and a special ref to keep it for you), then `stash pop` re-applies the changes from that commit to your working tree. checkout(in this manner) just tries to switch branches. If the starting-point for the new branch is not the same thing as your current HEAD it will try to checkout whatever it is you've asked, but abort if that would lose anything uncommited20:19
Does that answer your question?20:19
SwiftMatt joined20:19
AndroidSynth joined20:19
wviana joined20:20
Komislav joined20:20
deadnull joined20:20
deadnull_deadnull20:21
_deadnulldeadnull20:21
voice_of_me joined20:22
deadnull left20:22
deadnull joined20:22
UrsoBranco left20:24
dsantiago left20:24
akiva joined20:24
timvisher left20:25
dsantiago joined20:25
puff Eugene: Mostly, I have more questions but I need to get this thing done. I would like to follow up later.20:25
timvisher joined20:25
gajus joined20:26
Eugene We're here all day20:26
Not necessarily me, though20:26
gajus How do I get a commit hash of a specific line in code?20:26
i.e. I want to know the last commit that changed that line of code20:27
specing left20:27
rwb left20:27
glen left20:28
Bruce____ joined20:28
CussBot_ joined20:28
CussBot left20:28
CussBot_CussBot20:28
alex1a joined20:28
johnmilton left20:29
st0opkid joined20:30
ffio left20:30
leprechau left20:30
afuentes left20:31
mdw joined20:31
satifant joined20:32
mofai left20:32
_ikke_ gajus: git blame can do that20:32
rahmen86 @puff thanks I will look at it20:33
sgrover joined20:33
abyx left20:33
fuchstronaut joined20:34
sgrover Odd. I merge my develop branch into my feature branch to get the latest core files (not related to files I'm chaning in the branch). After cleaning up conflicts, and getting the merge commit in place, I'm noticing that my branch is 222 commits ahead of my origin/feature branch. Is this normal? Should I be doing a rebase instead?20:34
vF3hNGxc47h8 joined20:34
Kicer86 left20:35
nbari joined20:35
nbari hi all, at work I did a git checkout --orphan test20:35
gajus `git blame -L 12,12 posts/using-mysql-in-node-js/index.md` that seem to do it20:35
leprechau joined20:35
gajus Is there a way to get a full, and just the hash?20:35
nbari I am in home and and wondering if I need to do also git checkout --orphan test o I can just do a git checkout test and will continue orphan ?20:35
nnyk_ joined20:36
gajus -l gives long hash20:37
voice_of_me_ joined20:37
_ikke_ Not sure if you can get just the hash20:37
gajus and -p makes it ~easier to extract just the hahs.20:37
hash*20:37
gsingh left20:38
mar77i left20:38
Bruce____ left20:38
Komislav left20:38
fuchstronaut left20:39
gsingh joined20:39
_rht left20:40
voice_of_me left20:40
ajf- So I've been working on a project and tracking it on git and now that project becomes part of another which is not tracked on git (yet). What is the standard way of "moving files into a subdirectory" and allowing git to englobe more things ?20:40
choki joined20:41
gsingh left20:41
phaleth left20:41
osse ajf-: i don't think there is a standard way. just moving them would be fine20:42
ajf- how about moving .git/ back to one parent instead?20:42
synthroi_ left20:42
osse same thing20:43
ajf- cool20:43
thanks20:43
mar77i joined20:43
zacts hi gits20:46
I <3 this Ry's git tutorial thus far20:46
I'm going to check out Pro Git next20:46
nbari left20:46
zacts are there any good online resources for collaborative workflows with git?20:46
like I feel I'm learning the commands20:46
but I want to have a more macro viewpoint on how to collaborate with others via various workflows20:47
gsingh joined20:47
zacts versus the micro command line way of viewing git20:47
timvisher left20:47
timvisher joined20:48
puff clivejo: You also might find handy my rsync tutorial ("Enough rope...") at darksleep.com/notablog20:48
clivejo I dont think rsync will work20:49
barduck joined20:49
gsingh left20:49
clivejo the 3rd party has many more repo's than I want20:49
deadnull left20:50
gsingh joined20:50
mbrzuzy left20:50
puff clivejo: Then don't rsync them.20:51
clivejo: a repo is a .git directory.20:51
clivejo ideally I need a way to get all branches and tag locally and them push them to another remote20:51
gsingh left20:51
puff clivejo: Do you mean you only want a subset of the branches in their repo?20:51
clivejo yes20:52
kubuntu_*20:52
abyx joined20:52
puff clivejo: Ah, that's a whole different ball of wax.20:52
JBlazeCoder21 left20:52
gsingh joined20:53
puff clivejo: A bit beyond my present knowledge of git, but for example if you'd cloned this repo at the start, and then the other guy added a zillion branches, you could list them with "git branch -r" and then pull them.20:53
tsherman joined20:53
clivejo I have them cloned localled20:53
barduck left20:53
MagicTurtle joined20:53
clivejo and I can checkout and push a branch at a time20:53
Macaveli joined20:54
puff clivejo: Ah.20:54
clivejo but I need tags as well20:54
stantonk left20:54
clivejo and Im just totally lost :(20:54
puff clivejo: Okay, again, that's a very different question.20:54
ochorocho__ left20:54
puff clivejo: Sounds like you need more help than I have.20:54
elastix joined20:54
gsingh left20:54
MarkyC_ left20:54
puff clivejo: So to restate, your problem is that you cloned a remote repo to your local machine, and you want to push some of the branches up to a remote machine?20:55
jaguarmagenta joined20:55
puff clivejo: do you already have a repo on machine 3?20:55
sagerdearia left20:55
puff clivejo: git tags are objects just like the commit object, I would assume they'd get copied across with a git push.20:55
clivejo I have few hundred repos on a machine and I want to copy them and put them on another remote20:56
puff You said you already had them cloned locally.20:56
clivejo I have them all in a folder called gitmove20:56
mizu_no_oto joined20:56
clivejo but I can only seem to do one branch at a time20:56
puff clivejo: So write a simple bash script that invokes the branches one at a time.20:57
clivejo: git branch -a > listofbranches.txt20:57
clivejo but the tags dont seem to be carried over20:57
puff clivejo: Yeah, that's beyond me right now, sorry.20:57
clivejo: I've gotta get back to work.20:57
clivejo I have 6-7 branches Im concerned about, the rest isnt needed20:58
Macaveli left20:59
akiva left20:59
jaguarmagenta left20:59
alex1a left21:00
stantonk joined21:01
voice_of_me joined21:01
pantsman- left21:02
stantonk left21:02
jeffreylevesque joined21:03
stantonk joined21:03
ivan_on_trac In bare repositories where it is stored the files?21:03
I have a hook and need to make a script "cat myfile".21:04
voice_of_me_ left21:04
sgrover ivan_on_trac: in the .git directory inside your local repository folder.21:04
moritz ivan_on_trac: you can always 'git show HEAD:path/to/file'21:04
rojosh joined21:05
jchonig joined21:05
CussBot_ joined21:05
CussBotGuest3947421:05
Guest39474 left21:05
CussBot_CussBot21:05
mostlybadfly left21:06
teresko left21:06
zacts left21:07
tomog999_ joined21:08
timvisher left21:09
fmcgeough left21:09
timvisher joined21:09
mwhooker left21:09
markmarkmark !gitolite21:09
gitinfo Gitolite is a tool to host git repos on a server. It features fine-grained access control, custom hooks, and can be installed without root. Download: https://github.com/sitaramc/gitolite Docs: http://gitolite.com/gitolite/21:09
jakwong left21:10
mwhooker joined21:10
noteness left21:10
tomog999 left21:11
rnsanchez left21:12
nnyk_ left21:12
moei joined21:13
cagedwisdom joined21:13
nidr0x left21:13
bronson joined21:14
fuchstronaut joined21:14
jmpp left21:14
jmpp joined21:14
nidr0x joined21:14
Bruce____ joined21:16
dhollinger left21:17
mellernoia joined21:17
choki left21:18
bronson left21:19
Silenced joined21:19
fuchstronaut left21:19
ivan_on_trac moritz: But I want to do the "cat" from a script. Without using direct commands git.21:19
ojacobson You'll need to use at least one git command, even if you use a non-bare repo for this21:20
_ikke_ ivan_on_trac: A bare repository does not have a working tree21:20
noteness joined21:20
_ikke_ So the files do not exist as just plain files21:20
they're stored in gits internal format21:20
ahmed_elgabri left21:21
diegoaguilar joined21:21
MagicTurtle left21:21
jeffmjack joined21:22
peroht left21:23
mwhooker left21:23
vF3hNGxc47h8 left21:24
aidalgol joined21:24
IWishIKnew left21:25
nwkj86 left21:26
foul_owl How do I list all commit hashes between commit xyz and head? I want to include head but exclude xyz21:26
I know there is a some git log command that can specify a range but unsure how to use it21:27
Thanks!21:27
noteness left21:27
crose left21:27
johnwhitton left21:27
frem_ joined21:27
nwkj86 joined21:28
ash_workz left21:28
CrypticGator joined21:28
SwiftMatt left21:28
kadoban foul_owl: Sounds like xyz..HEAD , which is from man gitrevisions21:28
gitinfo foul_owl: the gitrevisions manpage is available at http://jk.gs/gitrevisions.html21:28
foul_owl THank you!21:29
kadoban (note that the dot notations work differently in 'git diff', which is … fun :-/21:29
)21:29
Isla_de_Muerte joined21:29
foul_owl Good to know!21:30
aspiers_ left21:30
mdw left21:30
satifant left21:30
mwhooker joined21:31
courrier joined21:31
timvisher left21:32
NwS left21:32
hobodave left21:32
timvisher joined21:32
JBlazeCoder21 joined21:32
mdw joined21:33
courrier Hey guys, does "git merge dev -s ours" in the branch master actually ignore all new commits made in master to replace it by branch dev?21:34
noteness joined21:34
TomyLobo left21:36
tsherman left21:37
daynaskully left21:37
tsherman joined21:38
apotry left21:40
_ikke_ It does not ignore commits, it ignores changes in the commits21:40
madewokherd left21:40
zacts joined21:41
osse courrier: and it ignores dev, not master21:41
noteness left21:41
kadoban -s ours … there's little reason to ever use that, is there?21:41
mdw left21:41
bollullera joined21:42
eletuchy joined21:43
daynaskully joined21:43
_ikke_ I would not know of a proper reason21:43
osse to record a merge so that a ref cannot be accidentally be merged again21:44
and so that git describe works21:44
e.g. if you branch out to work on version 2 while version 1 is not completed then you might want to merge -s our v1.0 or something21:45
but even then it's likely you actually want a regular merge21:45
noteness joined21:46
Dougie187 left21:47
eletuchy left21:48
Fijit left21:48
bango2 left21:49
raijin joined21:50
col__ left21:51
ochorocho__ joined21:52
mofai_ joined21:52
mofai_ left21:54
elastix left21:54
ahr3n joined21:54
yarnfive8 joined21:56
mischat left21:56
ochorocho__ left21:56
timvisher left21:56
mischat joined21:57
timvisher joined21:57
mase-tech left21:57
mofai_ joined21:58
mofai_ left21:59
akiva joined21:59
foul_owl does git rev-list --all show in date order?21:59
sangy left22:00
osse dunno, but it does if you do --date-order22:00
aspiers_ joined22:00
waveclaw_ joined22:00
b1tchcakes left22:01
deadnull joined22:01
mischat left22:02
abyx left22:05
soee guys how can i push branch with all tags to remote ?22:06
frem_frem22:06
espindola left22:06
abyx joined22:08
emPi left22:08
milki push --tags22:08
radsy joined22:09
HenriettaSalt joined22:09
sanketdg left22:10
soee milki: thanks22:11
madewokherd joined22:11
deadnull left22:12
waveclaw_ left22:13
clivejo is it possible to checkout all branches with a certain pattern?22:13
ie git checkout mybranch_*22:14
CussBotGuest5767122:14
Guest57671 left22:14
preaction at the same time?22:14
fuchstronaut joined22:15
clivejo to grab them all from the remote and have them locally22:15
CussBot joined22:15
josuebrunel left22:16
basiclaser left22:17
sagerdearia joined22:19
IlNominePatre left22:19
Cassiopaya left22:19
sagerdearia left22:19
pwnawannab[NE] left22:20
nidr0x left22:20
pwnawannab_ left22:20
fuchstronaut left22:20
osse clivejo: No22:20
waveclaw joined22:20
johnwhitton joined22:20
osse You already have them all locally, in a way22:20
!remote_tr22:21
gitinfo [!remote_tracking_branch] Remote-tracking branches (branches which start with e.g. 'origin/', listed by 'git branch -r') are read-only mirrors of the corresponding branches in another repository. They're updated by 'git fetch'. You can't edit them directly (trying to check them out results in a !detached HEAD), but you can create a new local branch based on a remote-tracking branch using e.g. 'git checkout -b <branch> <remote22:21
timvisher left22:21
sgrover left22:21
clevodearia joined22:21
johnwhitton left22:22
devdearia joined22:22
timvisher joined22:22
johnwhitton joined22:22
clivejo osse: Im trying to copy certain branches from one remote to another22:22
based on a pattern in the branch name ( ie mybranch_* )22:23
nidr0x joined22:23
osse clivejo: You don't have to check them out to do that22:25
mofai_ joined22:25
clivejo Ive a folder with all the repo's I want22:25
I used git clone22:25
and have added my new remote22:25
but I cant seem to push over the branches I want/need22:26
raininja joined22:26
raijin left22:26
mischat joined22:27
Aerosonic left22:27
jstimm joined22:28
mischat left22:28
osse git push remote2 remote1/mybranch:mybranch22:28
mischat joined22:29
editshare-ericf left22:29
DanZ3 left22:29
mofai_ left22:32
liamonade joined22:32
bronson joined22:33
abyx left22:34
fscala left22:34
akushner_ left22:35
fscala joined22:35
soee left22:35
jstimm left22:36
mwhooker left22:37
rxo left22:37
mofai_ joined22:37
mizu_no_oto left22:37
mwhooker joined22:38
stantonk left22:38
ril joined22:39
zZap-X left22:39
voice_of_me left22:40
rxo joined22:42
clivejo osse: error: unable to push to unqualified destination: master22:42
courrier osse _ikke_: my master is old and is my v1, my dev branch must become the new master and the old master must become a new old_v1 branch22:42
but I actually ignored dev, not master, and fucked up the repo :(22:42
I do have a copy though...22:43
I don't do a regular merge cause there are hge differences and that would be a hell to solve conflicts22:43
Darcidride left22:44
courrier I just want to force dev to be the new master somehow22:44
zZap-X joined22:44
timvisher left22:45
digidog left22:45
timvisher joined22:45
sangy joined22:46
noser joined22:46
mofai_ left22:48
mofai joined22:50
leehambley left22:51
sgambino left22:51
ash_workz joined22:51
sentriz left22:52
eggoez left22:53
HenriettaSalt left22:53
poz3idon left22:55
jaguarmagenta joined22:56
HenriettaSalt joined22:56
eggoez joined22:58
voice_of_me joined22:58
duderonomy joined22:58
tsherman left22:59
jaguarmagenta left23:00
eletuchy joined23:00
leonarth left23:00
HenriettaSalt left23:02
MarkyC joined23:02
ncd|leeN joined23:02
_rht joined23:07
ejnahc left23:08
ejnahc joined23:08
mizu_no_oto joined23:08
threeminutemonta joined23:08
timvisher left23:11
devdearia left23:11
devdearia joined23:11
kpease left23:11
timvisher joined23:11
clevodearia left23:12
nevyn courrier: do a force update if nobody has pulled it.23:12
git push remote dev:master23:12
courrier nevyn: with -f then?23:14
Fortunately I am the only one using that repo ^^23:14
ffabi left23:15
mwhooker left23:15
CEnnis91 left23:16
tvon joined23:17
courrier Actually I would prefer fix my local repo first23:18
ariel_17 left23:18
courrier In master I've tried "git merge -X theirs dev" to force dev to become the new master23:18
bilb_ono left23:18
a3Dman left23:18
courrier The merge went well but for some reason my tests fail while they were not in the dev branch23:19
mwhooker joined23:19
courrier it's odd23:19
nevyn oh man that's awful23:19
ok23:19
I'd fix the remote first as it's the biggest exposure23:19
saidelike left23:19
courrier nevyn: but after the push, what should I do locally to fix my local stuff?23:20
ffabi joined23:20
courrier just pull?23:20
mischat left23:20
noser left23:21
chitopunk left23:21
axisys left23:22
axisys joined23:23
bob1 joined23:23
noser joined23:24
bob1 left23:24
aspiers_ left23:25
CrypticGator left23:26
xcesariox joined23:26
dsantiago left23:26
CussBot_ joined23:26
CussBot left23:26
CussBot_CussBot23:26
Dyonisos left23:26
dsantiago joined23:27
CrypticGator joined23:28
CrypticGator left23:29
user083 joined23:29
CrypticGator joined23:29
dsantiago left23:30
CrypticGator left23:30
dsantiago joined23:30
saidelike joined23:30
a3Dman joined23:31
user083 left23:31
CussBot left23:31
CrypticGator joined23:31
xaa left23:31
timvisher left23:33
timvisher joined23:34
_wwwBukoLaycom joined23:34
CussBot_ joined23:35
CussBot_CussBot23:35
robbyoconnor joined23:35
MarkyC left23:35
Kaisyu joined23:37
johnmilton joined23:37
nevyn no. reset --hard dev while on master.23:38
but I'd make a backup branch first23:38
so on master checkout -b backup-broken23:38
reset --hard dev23:38
ugh23:38
checkout master again first23:38
courrier: ^^23:38
klep left23:39
nevyn so checkout master create a backup branch for justin.23:39
robbyoconnor left23:39
nevyn the checkout master again and reset --hard to dev23:39
bronson left23:40
bronson joined23:41
Stummi left23:41
nwkj86 left23:41
CEnnis91 joined23:41
rahmen86 left23:41
noser_ joined23:41
johnmilton left23:42
ams_ left23:43
mattfoo left23:43
noser_ left23:43
eletuchy left23:44
dsantiago left23:45
eletuchy joined23:46
fees left23:46
Stummi joined23:47
cwong_on_irc left23:48
mattfoo joined23:49
realz__ joined23:49
peepsalot left23:49
rkazak joined23:49
skapunker joined23:50
cagedwisdom left23:50
threeminutemonta left23:50
diegoaguilar left23:50
threeminutemonta joined23:51
crime joined23:51
crime does .gitignore need to be in the root directory of the project, or of the machine?23:51
BtbN left23:51
languitar left23:52
crime where does it go23:52
realz left23:52
BtbN joined23:53
crime nvm, it's in .git/info/exclude. that's obnoxious23:53
ril left23:53
crime left23:53
mellernoia left23:53
courrier nevyn: thanks, that's fixed both remotely and locally23:53
ril joined23:53
roflin left23:53
rilril[away]23:53
ril[away]ril23:53
asd5a left23:54
i7c left23:54
johnwhitton left23:54
ochorocho__ joined23:54
aspiers_ joined23:54
johnmilton joined23:54
bollullera left23:55
CrypticGator left23:55
mellernoia joined23:55
timvisher left23:55
mwhooker left23:56
noser left23:56
johnwhitton joined23:56
timvisher joined23:56
McNozes left23:57
languitar joined23:57
krnex left23:58
nfk left23:58
johnwhitton left23:58
stevenbenner left23:58
mizu_no_oto left23:58
fstd left23:59
threeminutemonta left23:59
gitinfo joined23:59
ChanServ set mode: +o23:59
fstd joined23:59
threeminutemonta joined23:59
ochorocho__ left23:59
wviana_ joined23:59
asd5a joined23:59

Logs Search ←Prev date Next date→ Channels Documentation