IRCloggy #git 2014-01-12

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.

2014-01-12

p4denis left00:00
Fissure wget: not entirely sure what you're asking00:00
_mtr left00:00
_ikke_ wget: git checkout .00:00
that will put the contents of the index in the working tree00:00
Fissure you want to stash the unstaged changes away, then make some different modifications on top of that, stage those, and then get your unstaged changes back?00:00
prometh joined00:01
Fissure if the unstaged changes and the new ones you're making don't overlap, use git add -p00:01
prometh i'm doing an interactive rebase and i'm getting "1 ahead, 5 behind" bullshit00:01
trying to squash the last 5 commits00:02
matt-chars wonderful. Some of the files in my .git folder are owned by root and cant be overwritten by git.00:02
_ikke_ chown them again00:02
prometh: when do you get that?00:02
prometh after doign the rebase00:02
i can't push00:02
_ikke_ prometh: !rewrite00:03
gitinfo prometh: [!rewriting_public_history] Rewriting public history is usually bad. Everyone who has pulled the old history have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push -f` to force (and the remote may reject that, anyway). See http://goo.gl/waqum00:03
psyl0n joined00:03
prometh ah00:03
Fissure prometh: don't do that if they're already pushed00:03
in the words of walter sobchak, you are entering a world of pain00:03
prometh why not? it'll make it easier for peole to read00:03
matt-chars _ikke_: now it seems to be working. Gotta go into each server and chwon -R all the .git folders and we'll be in business00:03
Fissure prometh: because if someone else has based changes on the unsquashed commits you're pulling the rug out from under them00:04
prometh i'm doing a pull request and it's easier to read 1 commit than 500:04
_ikke_ prometh: is it your own fork?00:04
prometh yes00:04
own branch00:04
_ikke_ ok00:04
then just push -f00:04
wget _ikke_: Ahhh, ok. Indeed, I thought, by index, the author means committed, but indeed, staged is considered as part of the index too. Thanks it works. #masteringGit00:04
prometh cool, thanks00:05
mikecmpbll left00:05
_ikke_ wget: To make it more clear00:05
index and stage refer to the same thing00:05
The stage is a conceptual idea, the index is how it's implemented00:05
`petey` left00:06
prometh thanks guys... worked nicely00:07
prometh left00:07
_mtr joined00:08
phipes joined00:09
Goplat joined00:09
craigp left00:10
oriba joined00:10
chamunks left00:12
petey joined00:12
wbdecker joined00:12
PLejeck left00:13
PLejeck joined00:13
kukks joined00:13
kukks left00:13
kukks joined00:13
PLejecknuck00:13
ingens left00:14
ngladitz left00:15
Cache_Money left00:15
macben joined00:16
dik_dak joined00:18
eijk_ joined00:19
hellopat left00:19
koda left00:20
hellopat joined00:20
King_Hual left00:21
corni left00:21
Goplat left00:22
eijk left00:22
macben left00:22
npatten joined00:22
CheckDavid left00:23
promethazin left00:23
pantsman left00:23
promethazin joined00:23
_mtr left00:24
hellopat left00:24
hwrdprkns joined00:25
valtih left00:25
geomyidae__ left00:25
lindenle left00:26
_mtr joined00:26
geomyidae joined00:27
prometh joined00:27
prometh how do i correct a commit message?00:27
i just did an interactive rebase and forgot to edit the long-ass message00:27
elbeardmorez_ left00:27
hwrdprkns left00:27
Fissure commit --amend00:28
hwrdprkns joined00:28
promethazin left00:28
valtih joined00:28
dik_dak left00:28
jayallen_ joined00:29
dik_dak joined00:29
xiong Damn, I don't think gitslave is the answer, either; it tries to do too much -- way too much. The paradigm bothers me of "do this git command for all subprojects"; it's risky.00:29
jayallen left00:29
jayallen_jayallen00:29
xiong I do not like the idea that devs cannot work on the project without using gits... or risk screwing it up. The gimmick, whatever it is, should only need to be used when doing something particular to the super/sub relationship.00:30
prometh thanks00:30
carbon joined00:31
prometh Fissure: if i push that, will it both be visible in history?00:31
i'm on my own branch, so it's safe to rebase -i and push -f00:31
Fissure no00:31
prometh it will replace the last commit?00:32
Fissure correct00:32
prometh cool, thank you00:32
Fissure: it's telling me that i'm 1 behind and i need to pull00:32
carbon left00:32
xiong May we start over and ask exactly what the risks are if we just nest several repos? What happens then? Changes to any subtree are committed in the super, check; a checkout in a sub dirties the super, check; each sub has its own remotes and history, check.00:32
prometh but the only thing to pull are my previous changes00:33
Guest28458 left00:33
Fissure yes00:33
you rewrote history again00:33
prometh force push?00:33
ok00:33
cool00:33
thanks!00:33
LuxuryMode joined00:33
defdeafy joined00:35
lindenle joined00:36
john2x joined00:36
prometh left00:37
rgr left00:37
phipes left00:37
Nizumzen joined00:38
kukks left00:38
petey left00:39
petey joined00:40
defdeafy left00:42
_mtr_ joined00:42
simesy joined00:42
_mtr left00:43
_mtr_ left00:44
petey left00:44
alexandernst joined00:45
freestyl3r joined00:45
nnyk_ left00:45
ivan\ left00:45
eijk_ left00:46
cmpera joined00:46
alexandernst How can I ignore all files/folders in the current dir, except the file 'a' and the folder 'b'? I'm trying with * \n !.gitignore \n !a \n !b but this is ignoring everything if the folder 'b' aswell.00:46
ivan\ joined00:46
frogonwheels left00:47
Fissure alexandernst: i can't remember if order matters00:47
jkremser left00:47
Fissure tracked files are never ignored, so if you add 'a' to the repo it will always be tracked even if it matches the ignore rules00:47
teran joined00:47
alexandernst Fissure: ah, that's good to know :) But I'd like being able to add my files without -f00:48
It doesn't feel like a clean solution00:48
kcj joined00:49
alexandernst ah, I think I found it :)00:49
Fissure is the -f required if it's already tracked and you're just updating the content? i wouldn't think so00:49
alexandernst it sohuld be '!b/' instead of '!b"00:49
s/sohuld/should/00:50
xiong alexandernst, Why do you want to ignore everything but?00:50
ingens joined00:50
leeN left00:50
alexandernst xiong: I want file 'a' and everything inside folder 'b' to be tracked, but I usually do dirty tests in the root directory, creating files and what not, and I don't want "git st" to "see" them00:51
ariscop left00:51
petey joined00:51
xiong I would do tests in a test/ and ignore that.00:51
alexandernst indeed, I do have a test folder, it's just I don't use it. Bad habits :(00:52
ntio joined00:52
ariscop joined00:52
nw8l joined00:54
teran left00:55
sjohnson joined00:55
Zeelot left00:57
teran joined00:58
Zeelot joined00:58
SeptDePique left00:59
iron_houzi joined00:59
paul424 left01:01
simesy_ joined01:01
simesy left01:01
hwrdprkns left01:02
hwrdprkns joined01:03
toiletbowlJoel joined01:04
Goplat joined01:04
jmct` joined01:04
simesy joined01:05
simesy_ left01:05
HelloShitty left01:06
xnrando01:06
prometh joined01:06
Zeelot left01:06
prometh is it possible to send a PR to an issue that i created on github?01:06
milki prometh: you cant turn an issue into a PR unless you use the api01:07
prometh better wording: is it possible to convert an issue that i created to a pr ?01:07
what api?01:07
milki github api?01:07
prometh javascript?01:07
or?01:07
amcsi left01:07
milki thats not how apis work01:07
gnu-man_ left01:07
prometh i'm not a sevrer-side guy01:07
Exancillatus joined01:08
milki apis arent really server related either01:08
prometh so it's json based?01:08
afhammad_ joined01:08
milki i adjust my answer, you cannot turn an issue into a pr. the api sounds too hard for you01:08
prometh dick.01:09
mribeirodantas joined01:09
acharlieh joined01:09
milki learn to google01:09
and hey, #github01:09
Fandekasp joined01:10
prometh left01:10
simesy left01:11
simesy joined01:11
jmct joined01:13
phipes joined01:13
afhammad_ left01:13
acharlieh left01:14
mklappstuhl left01:15
kukks joined01:15
alexandernst left01:16
Exancillatus left01:16
petey left01:19
drodger joined01:19
hwrdprkns left01:19
petey joined01:19
simesy_ joined01:20
HelloShitty joined01:20
petey left01:21
petey joined01:22
fesoj left01:23
simesy left01:23
valgrind left01:24
hwrdprkns joined01:24
RofricTheBearded is away: he went out and make himself busy. go ye and do likewise.01:24
milki wat01:25
simesy_ left01:25
dougsland left01:25
Vivekananda joined01:26
hellopat joined01:27
ChanServ set mode: +o01:27
bremner set mode: +q01:28
oxnrand01:28
bremner kicked RofricTheBearded (you can be unmuted when you disable your away gimmick)01:28
robbyoconnor joined01:28
ChanServ set mode: -o01:29
dougsland joined01:29
hwrdprkns left01:32
hellopat left01:32
phipes left01:32
simesy joined01:34
Kayra joined01:34
jayallen_ joined01:34
jayallen left01:34
jayallen_jayallen01:34
simesy left01:35
simesy joined01:35
Vivekananda left01:35
simesy left01:36
simesy joined01:37
phipes joined01:37
Vivekananda joined01:38
matt-chars left01:40
psyl0n left01:40
master_j joined01:40
petey left01:40
petey joined01:41
Mars joined01:43
MarsGuest3733901:43
BSaboia left01:43
hahuang65 left01:44
pikaren joined01:44
nerdfiles joined01:45
petey left01:45
simesy left01:46
hwrdprkns joined01:47
daivyk left01:48
ingens left01:48
simesy joined01:52
FerreusR left01:53
jmct left01:53
_mtr joined01:54
p4denis joined01:56
steverandy left01:56
neozonz left01:56
netiul left01:57
thunderbolt left01:57
Roch_ left01:57
raghunayyar__ left01:57
GameGamer43 left01:57
knownasilya left01:57
ddv left01:57
twisted` left01:57
jmcantrell left01:57
raghunayyar__ joined01:58
xerxas left01:58
scalability-junk left01:58
Roch_ joined01:58
steverandy joined01:58
netiul joined01:58
hwrdprkns left01:59
ddv joined01:59
GameGamer43 joined01:59
acharlieh joined01:59
conan left01:59
bwreilly left01:59
thunderbolt__ joined01:59
jmcantrell joined02:00
knownasilya joined02:00
xerxas joined02:00
scalability-junk joined02:00
matt-chars joined02:00
neozonz joined02:00
simesy_ joined02:00
tfnico left02:00
p4denis left02:01
ELLIOTTCABLE left02:01
OliverJAsh left02:01
jab416171 left02:01
lacrosse left02:01
Marenz joined02:01
anarchih left02:01
kapowaz left02:01
ggherdov left02:01
twisted` joined02:01
jayallen left02:03
jayallen_ joined02:03
anarchih joined02:03
tfnico joined02:03
OliverJAsh joined02:03
adambrenecki left02:03
ELLIOTTCABLE_ joined02:03
jab416171 joined02:03
kapowaz joined02:03
lacrosse joined02:03
titusjose_ left02:04
simesy left02:04
adambrenecki_ joined02:04
simesy_ left02:04
M4renz left02:04
Goplat left02:05
titusjose__ joined02:05
akitada left02:05
stealthii left02:05
henrikhodne left02:05
kor__ joined02:06
chamunkstchamunks02:06
looper_ left02:07
henrikhodne joined02:07
stealthii joined02:08
akitada joined02:08
ggherdov joined02:08
prometh joined02:08
prometh how can i remove a tree, but not the whole repo?02:09
Kayra left02:09
looper joined02:09
wbdecker prometh: rm -rf ?02:10
prometh: just don't delete the .git folder02:10
Suprano joined02:10
_mtr left02:10
prometh what's -rf ?02:11
a recursive force02:11
ah*02:11
that can delete a tree?02:12
bremner prometh: what do you mean by a tree?02:12
prometh github.com/user/repo/tree/1298379hasfyq302:12
shinnya joined02:13
bremner can you phrase your question in terms of git, rather than the github web interface?02:13
prometh that's all i know.02:13
Nizumzen left02:14
beyondcreed joined02:14
prometh i have a PR with a commit that i've overwritten (push -f) ... i'm thinking that if i remove the tree that the commit is on, the reference will be removed as well02:14
oriba left02:14
mribeirodantas left02:14
Marenz left02:15
prometh the tree would be a commit hash, i guess02:15
_mtr joined02:16
prometh i'm always using git wrong, but i'm trying to fix my mistakes02:17
why do people always stop helping me when i ask hard questions?02:19
Silmarilion left02:19
bremner I guess you need to wait for someone github savvy with time on their hands.02:20
offby1 embarrassment02:20
thunderbolt__thunderbolt02:20
offby1 prometh: why do you want to "remove the tree"?02:20
hellopat joined02:21
offby1 elbows bremner aside02:21
prometh i have a PR with a commit that i've overwritten (push -f) ... i'm thinking that if i remove the tree that the commit is on, the reference will be removed as well02:21
https://github.com/bitovi/canjs/pull/652#ref-commit-051e45602:21
see those 2 commits above the bottom one? those have been replaced in history02:21
_mtr left02:22
offby1 so it sounds like your goal is to update the pull request, somehow02:22
interesting02:22
prometh it worked with other PRs... my problem is the commist messsages02:22
they have #123 in them02:22
i'm never doing htat again02:22
offby1 unfortunately this is indeed a github question, not a git question; also unfortunately, I don't really know how pull requests work :-|02:22
dyng joined02:22
prometh ok02:22
but here02:22
https://github.com/stevenvachon/canjs/tree/6f689435fa17c8b80e75cb363084ba3044a462df02:23
i want to remove that tree02:23
ArcTanSusan left02:23
bremner you may try #github. It's quiet. But at least people won't yell at you for asking github questions.02:23
prometh that's the PR tree, i take it02:23
offby1 "removing a tree" doesn't make any sense.02:23
prometh i'm in #github too02:23
offby1 you can't really remove anything from a git repository; the most you can do is stop referring to certain commits.02:23
Goplat joined02:23
dyng left02:23
prometh i did a rebase -i and push -f02:23
offby1 you certainly can't delete a tree. That would invalidate every commit that referred to that tree, directly or indirectly.02:24
prometh it's been rewritten02:24
ivan\ left02:24
dyng joined02:24
offby1 what it really sounds like is: you want to create a _new_ pull request that's similar to the old one, except with the updates.02:24
prometh nope, same PR02:24
i want to remove those references02:24
dyng left02:24
offby1 And then you somehow want people to forget about the old PR and start using the new one.02:24
dyng_ joined02:24
prometh i've done this before and it worked perfectly... the problem this time around is that i have #123 in my commits02:24
ivan\ joined02:25
dyng_ left02:25
dyng joined02:26
mtr_ joined02:26
rawtaz in your commits?02:26
mtr_ left02:26
rawtaz prometh: please try to be more specific in your terminology, otherwise ppl just get confused. for example, do you mean your commit *messages*?02:26
prometh yes02:26
kermit joined02:27
tvw left02:28
rawtaz what's #123 btw, some issue number?02:28
prometh issue/PR number02:28
rawtaz ok02:28
dyng left02:30
kermit left02:31
pgokeeffe joined02:32
jmct` left02:33
teran left02:33
Guest37339 left02:33
Mars joined02:34
teran_ joined02:34
MarsGuest476002:34
teran_ left02:34
nw8l left02:35
teran_ joined02:35
acharlieh left02:36
ariscop left02:36
LucasKA left02:37
rurufufuss joined02:37
phipes left02:38
Guest4760 left02:39
LucasKA joined02:40
tajys joined02:40
ArcTanSusan joined02:41
tplaner joined02:41
mizu_no_oto joined02:42
kermit joined02:42
conan joined02:43
sohail left02:43
TDJACR left02:43
girishr joined02:44
cjsarette left02:46
mizu_no_oto left02:47
ariscop joined02:48
tma996 joined02:48
cjsarette joined02:48
dougsland left02:49
tajysTajha02:49
kermit left02:53
dreiss joined02:55
kermit joined02:56
cmpera left02:56
tma996 left02:59
tma996 joined02:59
dsdeiz joined02:59
Chaser left03:00
Chaser joined03:02
sohail joined03:02
sohail left03:02
sohail joined03:02
phipes joined03:03
teran_ left03:04
kor__ left03:05
teran joined03:05
dsdeiz left03:05
teran left03:05
teran joined03:06
dreiss left03:06
kotk1 left03:08
fire joined03:08
yhager joined03:09
marcjs left03:10
CheckDavid joined03:10
TDJACR joined03:11
marhaban joined03:12
tmcmahon joined03:14
mitz joined03:14
simesy joined03:14
tmcmahon left03:16
marhaban left03:18
gwb3 left03:18
simesy left03:20
yhager left03:20
wbdecker left03:21
wbdecker joined03:22
yhager joined03:22
Mars joined03:23
MarsGuest4733903:24
gsvolt joined03:24
MetalMatze left03:24
ariscop left03:25
phipes left03:25
npatten left03:26
yhager left03:27
hesco can I explicitly name the key pair I want to use for a git pull? When I ssh [email@hidden.address] gitolite responds with a list of repos this user has access to, but when I use git pull, I get 'Too many authentication failures for git', I suspect related to the keys forwarded from my desktop.03:27
gwb3 joined03:28
freestyl3r left03:29
ariscop joined03:29
gwb3 left03:31
dsdeiz joined03:31
prometh left03:31
angelsl joined03:32
jayrobot left03:32
zumba_addict_ joined03:32
zumba_addict left03:33
zumba_addict_zumba_addict03:33
teran left03:35
teran joined03:36
teran left03:36
teran joined03:37
jayallen joined03:37
jayallen_ left03:37
wbdecker left03:38
gwb3 joined03:38
Dougie187 joined03:38
thiago hesco: use ~/.ssh/config03:40
LucasKA left03:40
pgokeeffe left03:41
hesco I am using .ssh/config03:41
thiago there you go03:41
problem solved03:41
SHyx0rmZ joined03:41
hesco it seems to be reading the key forwarded from home rather than the key on the remote box intended for this purpose.03:41
petey joined03:42
thiago does ~/.ssh/config specify which key to use for that host?03:42
hesco it does03:42
Dougie187 well, more like it can.03:42
mizu_no_oto joined03:42
hesco but so does the .ssh/config on my home machine from where my key (a different one) is forwarded03:43
thiago hesco: is there a problem if you don't forward the SSH agent?03:43
fire left03:43
GT4066 joined03:44
hesco have not tested that. but the key on the remote box is used for other purposes and has been tested with this git repo, though I do not remember this issue before.03:44
very strange03:45
phipes joined03:45
petey left03:46
ingens joined03:51
robbyoconnor left03:52
robbyoconnor joined03:52
hesco resolved. mismatch between alias and fqdn between .git/config and .ssh/config03:55
p4denis joined03:56
sitaram hesco: I'm getting a strange feeling of deja vu03:56
macben joined03:57
hesco some lessons demand be relearned I suppose.03:57
sitaram yeah... and you have a much more complex ssh setup than most people, I think03:57
hesco apparently so, multiple keys for various purposes.03:58
sitaram oh I have several keys...03:58
David joined03:58
sitaram personally, I don't like ssh forwarding anyway. For me the intermediate host is either trusted, in which case I'll have another priv key on it, or it's untrusted, in which case I won't even use it. Ssh forwarding helps you with untrusted machines only a little03:58
that box can still do something, even if it can't actually get your private key, IIRC03:59
hesco at any rate it finally cloned and so now I can write a useful deploy script.03:59
David Is it possible to have separate identities in git? I have one repo (and only one, so a per-repo solution is fine) that I want to use a different name/email on.04:00
one that doesn't match my global git config04:00
milki David: are you talking about author/commiter name/email?04:00
sitaram David: just run 'git config user.name ...' and user.email within that repo04:00
should work04:00
David milki: yes04:00
thanks sitaram04:00
I'll try that04:00
milki David: gitolite doesnt care about that. thats all local to your git config04:00
p4denis left04:01
sitaram milki: gitolite? he didn't mention gitolite :-)04:01
milki o...this isnt #gitolite04:01
hi sitaram04:01
sitaram :)04:01
David :P04:01
sitaram hi milki04:01
macben left04:01
FleaFlicker joined04:01
milki David: remember git config by default is per repo. you can do global with --global04:02
sitaram hesco: if the intermediate machine is not trustable, I'd simply make a tunnel in one xterm and use that in another; then the intermediate host can only do what any other intermediate *network* node can do04:02
David Right. Thanks again!04:03
Will try that now.04:03
thegorn left04:03
CheckDavid left04:04
LuxuryMode left04:04
ingentis joined04:05
teran left04:07
teran joined04:07
teran left04:07
teran joined04:08
ingens left04:09
dyng joined04:11
David just to be clear - local config will take precedence over global one, right?04:11
MindfulMonk left04:12
Goplat left04:12
tplaner left04:12
mitz left04:13
FleaFlicker left04:15
mitz joined04:15
dyng left04:16
preflex_ joined04:17
preflex left04:18
preflex_preflex04:18
angelsl left04:19
angelsl joined04:21
mizu_no_oto left04:23
ntio left04:25
ingentis left04:25
crazydiamond left04:26
bl33 joined04:27
lindenle left04:28
ajunior joined04:28
SamB David: yes04:29
David thanks04:29
bl33_ joined04:32
dsdeiz left04:32
KeiKun_ joined04:35
KeiKun_ excuse me is there way to git chmod via msys?04:35
elepfonitus joined04:37
lindenle joined04:38
teran left04:38
LucasKA joined04:38
bl33_ left04:39
teran joined04:39
teran left04:39
blast_hardcheese left04:40
teran joined04:40
livingstn joined04:40
dyng joined04:42
dyng left04:46
pekster left04:48
dglambert left04:50
pekster joined04:50
kcj left04:51
kukks left04:56
Noldorin left04:58
matt-chars left05:01
bl33_ joined05:05
kerrick left05:07
rwp left05:07
beyondcreed left05:08
Goplat joined05:08
offby1 what does "git chmod" mean?05:09
teran left05:10
obert it switch git with the public access05:10
teran joined05:10
obert so the whole world can browse your computer05:10
teran left05:11
marcjs joined05:11
teran joined05:11
marcjs left05:15
alezost joined05:16
gordian left05:19
livingstn left05:19
LuxuryMode joined05:20
LuxuryMode left05:20
Nicholas_Rishel left05:21
mitz left05:22
JSharpe2 left05:22
LulzonAwayLulzon05:23
Nicholas_Rishel joined05:24
Goplat left05:25
ojacobson joined05:28
macben joined05:30
lindenle left05:34
macben left05:35
Tommy[D] joined05:35
mitz joined05:36
Tommy[D]_ left05:38
hellopat left05:38
timewa1ker left05:38
hellopat joined05:39
krononaut joined05:39
TDJACR left05:40
kennon joined05:40
john2x left05:40
ajunior left05:41
teran left05:41
john2x joined05:42
teran joined05:42
petey joined05:43
teran left05:43
teran joined05:43
hellopat left05:43
TDJACR joined05:46
petey left05:47
Dougie187 left05:48
TDJACR left05:50
LucasKA left05:50
elepfonitus left05:52
TDJACR joined05:53
mrhooray joined05:54
mrhooray left05:54
mrhooray joined05:55
EugeneKay KeiKun_ - git only tracks the execute bit; this looks like a regualr octal perms mask, but it isn't.05:55
And it's meaningless(mostly) in a msysgit env anyway05:55
TDJACR left05:56
p4denis joined05:57
TDJACR joined05:57
David left05:57
TDJACR left05:58
TDJACR joined05:58
acharlieh joined05:58
macben joined06:01
p4denis left06:01
z^z left06:01
albioner joined06:02
albioner left06:02
albioner joined06:03
albioner left06:03
rue left06:03
albioner joined06:03
albioner left06:03
albioner joined06:04
David joined06:04
TDJACR left06:05
albioner left06:05
macben left06:06
ojacobson left06:07
joki left06:11
marcjs joined06:11
nerdfiles left06:12
teran left06:12
teran joined06:13
teran left06:14
teran joined06:14
KeiKun_ i think msys just doesn't suit for git on windows06:15
Exancillatus joined06:15
marcjs left06:16
theRealGentleman left06:16
joki joined06:17
gitinfo set mode: +v06:17
KeiKun_KeiKun06:17
Atlantic777 joined06:18
Atlantic777 Hey, any ideas why !*.c doesn't work for me in .gitignore?06:18
offby1 not me, nuh-uh06:19
digifiv5e left06:20
Exancillatus left06:20
diegoviola joined06:20
digifiv5e joined06:20
digifiv5eGuest714806:21
craigp joined06:23
Nicholas_Rishel left06:24
LucasKA joined06:25
donmichelangelo left06:25
donmichelangelo joined06:25
the_cybersphinx left06:26
barbles joined06:27
barbles left06:29
barbles joined06:29
LucasKA left06:30
toiletbowlJoel left06:33
MattMake_ joined06:36
MattMaker left06:38
teran left06:40
matanya left06:41
el3ctron joined06:42
DeanH joined06:42
CourtJesterG joined06:46
Guest47339 left06:46
mrhooray left06:48
Mars joined06:49
MarsGuest4283506:49
starkhalo left06:50
Vivekananda left06:51
mrhooray joined06:51
mrhooray left06:52
bdavenport left06:53
bdavenport joined06:53
CourtJesterG left06:57
girishr left06:58
LuxuryMode joined06:59
TDJACR joined07:00
ehmatthes joined07:01
TDJACR left07:07
mitz left07:07
jcvfen left07:07
mitz joined07:08
LulzonLulzonAway07:08
LuxuryMode left07:09
rue joined07:09
robbyoconnor left07:10
rue left07:10
robbyoconnor joined07:10
a-l-e joined07:10
hellopat joined07:11
marcjs joined07:12
hellopat left07:15
sohail left07:15
MattMake_ left07:16
marcjs left07:16
fire joined07:17
fire left07:18
phipes left07:22
angelsl left07:23
ajunior joined07:23
acharlieh left07:24
LucasKA joined07:25
Guest42835 left07:26
Mars joined07:26
MarsGuest2632407:27
kesha joined07:29
LucasKA left07:29
jceb joined07:31
dreiss joined07:31
Tajha left07:31
p3lim joined07:32
Kicer86 joined07:32
ahmedelgabri joined07:33
TDJACR joined07:33
Guest26324 left07:39
tma996 left07:40
petey joined07:43
ahmedelgabri left07:43
ewnd9 joined07:44
ArcTanSusan left07:44
phipes joined07:45
TDJACR left07:45
bondar joined07:46
bondar left07:47
m0viefreak left07:47
ewnd9_ joined07:47
petey left07:49
hoschi joined07:49
ewnd9 left07:49
h0bbit_ joined07:50
tgkokk joined07:54
blast_hardcheese joined07:55
m0ltar joined07:55
p4denis joined07:57
emergion joined07:59
m0ltar left08:00
dsdeiz joined08:01
mvelioglu joined08:01
p4denis left08:02
cjsarette left08:02
tallest_red left08:03
tgkokk left08:04
matanya joined08:06
tgkokk joined08:07
tallest_red joined08:07
rendar joined08:07
dik_dak left08:08
joki left08:09
angelsl joined08:11
tgkokk left08:12
joki joined08:12
marcjs joined08:12
thiago left08:13
jceb left08:13
marcjs left08:17
jackneill joined08:18
ahmedelgabri joined08:19
m0ltar joined08:20
diegoviola left08:23
ehmatthes left08:24
ajunior left08:27
krononaut left08:27
David left08:30
GT4066 left08:30
GT4066 joined08:31
ngladitz joined08:33
tango_ left08:34
macben joined08:36
ewet joined08:36
phipes left08:37
ewet left08:37
dreiss left08:38
ewet joined08:38
ewet left08:38
ewet joined08:39
ewet left08:39
ariscop left08:40
ewet joined08:40
ewet left08:40
ewet joined08:41
ewet left08:41
ewet joined08:41
macben left08:41
tma996 joined08:41
deavid left08:42
deavid joined08:42
tango_ joined08:42
dyng joined08:45
doev joined08:45
xequence joined08:45
jrib left08:46
ianmcorvidae left08:46
ianmcorvidae joined08:47
ewet left08:47
hits joined08:47
kermit left08:48
_tpavel joined08:48
Mars joined08:49
MarsGuest3857108:50
dyng left08:50
King_Hual joined08:50
Simounet left08:50
khmarbaise joined08:51
kcj joined08:54
ahmedelgabri left08:55
Guest38571 left08:55
ahmedelgabri joined08:55
_tpavel left08:56
danicampa901 joined08:58
hellopat joined08:59
quup left09:01
quup joined09:02
khmarbaise left09:04
VinceThePrince joined09:04
ArcTanSusan joined09:04
hellopat left09:05
macben joined09:07
ArcTanSusan left09:09
tma996 left09:11
macben left09:11
tma996 joined09:11
pinage404 joined09:12
jorj left09:12
marcjs joined09:13
ArcTanSusan joined09:16
marcjs left09:18
jorj joined09:18
David joined09:20
albertgrala joined09:21
takamichi joined09:22
elbeardmorez joined09:24
David left09:25
Vortex35 left09:25
Vortex35 joined09:25
thevishy joined09:26
kotk joined09:26
LucasKA joined09:27
tma996 left09:28
noname001__ joined09:30
bl33_ left09:32
bl33 left09:32
JSharpe2 joined09:32
LucasKA left09:32
bl33 joined09:33
zapb joined09:34
bl33_ joined09:34
cbreak Atlantic777: maybe you have the wrong expectations09:34
a-l-e left09:37
phipes joined09:38
Sound joined09:42
phipes left09:43
fphilipe joined09:44
petey joined09:44
hits left09:44
emergion left09:45
diegoviola joined09:45
ahmedelg_ joined09:45
ahmedelgabri left09:46
dyng joined09:47
tarkus joined09:47
ewet joined09:48
ewet left09:48
ewet joined09:48
petey left09:49
dyng left09:52
tgkokk joined09:52
bvi joined09:53
h0bbit_ left09:54
ewet left09:55
ahmedelgabri joined09:55
diegoviola left09:55
ewet joined09:56
tgkokk left09:56
ewet left09:56
ewet joined09:57
p4denis joined09:58
diegoviola joined09:58
m0ltar left09:58
ahmedelg_ left09:59
calcifea_calcifea09:59
scottrb left09:59
tma996 joined09:59
ahmedelg_ joined10:00
ahmedelgabri left10:00
p4denis left10:02
King_Hual` joined10:03
promethazin joined10:04
fphilipe left10:05
tgkokk joined10:05
przemoc left10:07
Freeman42 joined10:08
przemoc joined10:08
pantsman joined10:10
pantsman left10:10
pantsman joined10:10
skorgon_ left10:12
ArcTanSusan left10:13
marcjs joined10:13
m0ltar joined10:14
ahmedelgabri joined10:16
Silmarilion joined10:17
ewnd9_ left10:17
fphilipe joined10:18
nicedice joined10:18
marcjs left10:18
leeN joined10:19
ahmedelg_ left10:19
diegoviola left10:19
takamichi left10:19
diegoviola joined10:19
hyperair joined10:19
tgkokk left10:21
tgkokk joined10:21
charon left10:21
takamichi joined10:21
bvi left10:22
bvi joined10:24
ahmedelg_ joined10:24
el3ctron left10:25
tgkokk left10:26
promethazin left10:26
tgkokk joined10:26
corni joined10:26
promethazin joined10:26
Sound left10:27
arietis joined10:27
ahmedelgabri left10:27
Sound joined10:28
danicampa901 left10:28
LucasKA joined10:29
eletuchy left10:30
eletuchy joined10:30
promethazin left10:30
jtri joined10:31
tma996 left10:33
khmarbaise joined10:33
jtri hello, I started a branch and did some dev in it using > git checkout -b voting10:33
bvi left10:33
jtri right after this, on another machien i noticed a change i wanted to make on master branch, so i made it from that machine, then made the same change in my branch10:34
LucasKA left10:34
jtri i committed both of these10:34
I pushed them both too, using > git push origin voting & > git commit10:34
pantsman left10:35
jtri eventually i finished the development in the branch and so i tried to merge it with master, but perhaps i forgot to pull master, not sure10:35
anyway, I used > git merge -s ours master10:35
there were a few files i left out of the commit from the branch voting, because I didn't want to add them in until i ran south migrations on the other machine10:37
anyway, i have this huge mess now10:37
and i'm wondering how to go back to the point i know the branches are in good shape, and try this again, or what to do...10:38
cbreak jtri: do you know what -s ours means?10:38
jtri stragety ours,10:38
thought that was what i wanted10:38
cbreak yes. Ignore all changes from the other branch10:38
jtri figured that meant take the master and keep the branch10:38
phipes joined10:39
jtri which made sense, but i think it did some odd things with files that were not in master10:39
cbreak that's irrelevant10:39
master is ignored10:39
jtri like decided that even though i had added them in the branch they woudl be removed? does that make sense?10:39
MIFL joined10:39
kesha_ joined10:40
cbreak jtri: !lol, please pastebin the result10:40
gitinfo jtri: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all10:40
cbreak and tell me which the commits are that you want to be on10:40
kesha left10:40
cbreak oh, also pastebin the output of git status10:40
jtri here's the woa tangled mess: http://dpaste.com/1547709/10:41
MIFL Hi Guys10:42
gitinfo MIFL: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.10:42
MIFL I need help with git am10:42
cbreak jtri: where do you want to be at?10:42
MIFL It is possible to revert a patch with this command?10:43
jtri 1440ef6 is the good spot on the end of the branch, that's where i meant to merge it back to master, excpept for a couple of south migations10:43
cbreak MIFL: git revert reverts things.10:43
jtri: so, if you have no uncommitted changes that you want to keep10:44
jtri 78275d3 is the master i meant to merge with10:44
phipes left10:44
cbreak just check out the branch you want to be on10:44
MIFL cbreak: yes but need revert varios commits10:45
jkremser joined10:45
jkremser left10:45
jkremser joined10:45
cbreak so, git checkout voting for example10:45
jrib joined10:45
cbreak jtri: then git reset --hard commityouwanttobeon (this will nuke away uncommitted changes)10:45
it will also rewrite history10:45
jtri: do this for master too10:46
and after that you have the history you want10:46
jtri: you can then git cherry-pick 8203efa for example to get a copy of that commit into your rewritten branches10:46
MIFL: sure, you can do that.10:46
just git revert all of them10:47
cmpera joined10:47
dyng joined10:47
MIFL one by one?10:48
hellopat joined10:48
cbreak you can also give it a range10:48
A..B means all commits reachable by B but not A10:48
(all commits between A and B, but not including A, but including B)10:49
jtri ok, so got the voting branch and > git reset --hard commitiwanttobeon, same with master (which one's will that nuke?)10:49
cbreak both10:49
all your uncommitted changes will be gone10:50
bvi joined10:50
cbreak history will become unreachable from those two branches10:50
jtri oh, so the history will be there, just seperated?10:50
cbreak it will be in the reflog10:50
MIFL I usually use this command: git apply -R --check --verbose --ignore-space-change --ignore-whitespace < ./patches/updates/update-01/revert.patch10:51
cbreak but not reachable by normal branch heads10:51
ahmedelgabri joined10:51
ewnd9_ joined10:51
cbreak MIFL: and what's that good for?10:51
albertgrala left10:51
acharlieh joined10:51
cbreak a simple git revert seems much simpler than messing around with patches10:51
dyng left10:52
MIFL Ok. Thanks10:52
hellopat left10:53
ahmedelg_ left10:54
takamichi left10:55
JSharpe2 left10:55
ahmedelg_ joined10:55
ahmedelgabri left10:56
jtri ok, ran > git reset --hard 78275d3 from master, and > git reset --hard 1440ef6 from voting branch10:57
vince_prignano joined10:57
jtri it indicated "HEAD is now on ###### in both cases10:58
guessing i could checkout back and forth between those now safely and see they are correct?10:58
cbreak jtri: or just look at !lol10:58
gitinfo jtri: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all10:58
arietis left10:59
jtri here's where I'm at: http://dpaste.com/1547724/11:00
cbreak jtri: what do you want to do with 8203efa and 1b7c611?11:01
diegoviola left11:02
jtri i'm still a little confused, those are new change numbers, right?11:02
cbreak jfield: if you want to keep those changes (but forget about the merge 7195056)11:02
no11:02
those are commits11:02
they are already pushed to origin11:02
JPohlmann joined11:03
jtri oh, no, they just moved up11:03
quup_ joined11:03
cbreak if you want to keep them, cherry-pick them11:03
jtri i see11:03
cbreak (starting with 8203efa)11:03
PeterBooker joined11:03
cbreak after that you can force push to nuke the history on origin too11:03
jtri so they are now dangling11:03
cbreak no11:03
cehteh_ joined11:04
cbreak they are reachable by origin/master and so on11:04
as you can see11:04
and origin/voting11:04
khmarbaise left11:04
GT4066 left11:04
edude03_ joined11:06
jtri should i cherry pick them from both voting and master?11:06
King_Hual` left11:06
King_Hual left11:06
jtri they should be in voting, until i merged it with master...11:06
mahler_io joined11:06
jtri so they were created in voting11:07
cbreak you cherry-pick them into the branch you want them to be11:07
jtri ok11:07
arietis joined11:07
c0ded left11:07
brainproxy_ joined11:07
c0ded joined11:08
rurufufuss left11:08
moondoggy left11:08
lfaraone left11:08
cehteh left11:08
JPohlman1 left11:08
silverf0x left11:08
idoru left11:08
edude03 left11:08
camt left11:08
NanoArrow left11:08
linduxed left11:08
xintron left11:08
awx left11:08
geomyidae left11:08
cwillu_at_work left11:08
St_Marx left11:08
atrus left11:08
ozymandias left11:08
tapout left11:08
simpleminds left11:08
Edgan left11:08
DANtheBEASTman left11:08
dmarr left11:08
akersof left11:08
w0ng left11:08
aucecil left11:08
zz_karupanerura left11:08
MIFL left11:08
tgkokk left11:08
rendar left11:08
squentin left11:08
JerryT left11:08
NBeeuwsaert_ left11:08
WaReZ left11:08
ra4king left11:08
slyfox left11:08
Noctis_Lux left11:08
nemesit|znc left11:08
hike left11:08
LeeXiaolan_ left11:08
toothrot left11:08
rfoust left11:08
Barn3y left11:08
polyzen left11:08
eli left11:08
RogerWS left11:08
qsuscs left11:08
kamal_ left11:08
graphitemaster left11:08
Eridius left11:08
whiskers75 left11:08
mikaelj_ left11:08
kossy left11:08
KK4MGV left11:08
alindeman left11:08
bitkid left11:08
gtmanfred left11:08
ToothlessGear left11:08
Exio4 left11:08
igalic left11:08
unsignedint left11:08
abyss42 left11:08
frobware left11:08
blueyed left11:08
myme1 left11:08
spudz_ left11:08
spacepluk left11:08
tomek left11:08
ahf left11:08
Mission-Critical left11:08
mz` left11:08
dpwrussell left11:08
dsockwell left11:08
einonm_ left11:08
luminous left11:08
runeg_ left11:08
_ikke_ left11:08
CareBear\ left11:08
masak left11:08
drbean left11:08
zso left11:08
ndngvr left11:08
docwhat left11:08
jkremser left11:08
leeN left11:08
ewet left11:08
quup left11:08
doev left11:08
tango_ left11:08
deavid left11:08
mitz left11:08
bdavenport left11:08
craigp left11:08
pekster left11:08
preflex left11:08
gwb3 left11:08
conan left11:08
Suprano left11:08
looper left11:08
akitada left11:08
titusjose__ left11:08
OliverJAsh left11:08
ELLIOTTCABLE_ left11:08
jab416171 left11:08
knownasilya left11:08
netiul left11:08
TheFuzzball left11:08
salamanderrake left11:08
bhldev left11:08
sami| left11:08
Console left11:08
lahwran left11:08
ConstantineXVI left11:08
SamB left11:08
Mez left11:08
bedouin left11:08
dytrivedi left11:08
_Parnic left11:08
kini left11:08
nickoe left11:08
ryanakca left11:08
dsop left11:08
dwmw2_go` left11:08
Sp4rKy left11:08
jeek left11:08
kwmiebach left11:08
konr left11:08
Imdsm left11:08
NimeshNeema left11:08
Fill left11:08
arcanis left11:08
grn left11:08
bauruine left11:08
Werring left11:08
asQuirreL left11:08
abackstrom left11:08
joevandyk left11:08
adam_ left11:08
skelterjohn left11:08
relipse left11:08
cuppscakes left11:08
pikpik left11:08
joelmo left11:08
jds left11:08
mino left11:08
adamm left11:08
quadz left11:08
TheMoonMaster left11:08
gerard0 left11:08
flexd left11:08
marshmn left11:08
spaceone left11:08
stfn left11:08
kulp left11:08
saurik left11:08
xrq left11:08
jayne left11:08
brainproxy left11:08
Ghjnut left11:08
Tritania left11:08
matthias_dev left11:08
PhonicUK left11:08
max_weller left11:08
theForce1 left11:08
dawik left11:08
meatmanek left11:08
iAsterisk_ left11:08
so left11:08
alip left11:08
gde33 left11:08
rom1504 left11:08
dunpeal left11:08
tapout joined11:08
phipes joined11:08
KeiKun left11:09
pantsman joined11:09
sq-one joined11:09
KeiKun joined11:09
jtri ok, I cherry picked those two into voting: http://dpaste.com/1547725/11:09
Silmarilion left11:10
jtri the graph still looks strange to me11:10
there are three independent branches at the top now11:11
cianuro joined11:12
jtri furthermore, i'm on voting and the code that was in voting is not there... like in models.py11:13
phipes left11:13
mz` joined11:13
kesha_ left11:13
juliohm joined11:13
jtri oh, wait, i think models is fine11:13
i was wrong about that, i think11:14
timewa1ker joined11:14
marcjs joined11:14
jtri yeah, ok, voting looks fine11:14
cianuro buongiorno a tutti11:14
jtri how do i read the tuples like: (HEAD, voting)11:15
NanoArrow joined11:15
awx joined11:15
jtri (origin/master, origin/HEAD)11:15
xintron joined11:15
fphilipe left11:15
linduxed joined11:15
calcifea left11:17
jtri i'm not sure what to do next, whether to push any of this for example, or whether i can/should try merging voting into master11:17
petertretyakov joined11:18
marcjs left11:18
calcifea joined11:18
Silmarilion joined11:19
h0bbit_ joined11:20
ahmedelg_ left11:20
fphilipe joined11:20
MissionCritical joined11:21
jtri the message I get when I checkout master says: Your branch is behind 'origin/master' by 7 commits, and can be fast-forwarded.11:21
heliomaster joined11:22
cbreak jtri: as I said: you have to force push afterwards11:23
jtri: those are just lists of refs that point there11:23
HEAD is your currently checked out branch11:24
origin/master is the master your origin repository had when you last fetched11:24
jtri: if you force push, you can kill the origin/* history11:24
for example, git push -f origin master voting11:24
cmpera left11:26
cbreak that will push those two branches, replacing remote history11:27
valgrind joined11:27
jtri so are voting and master still seperate and both safe?11:27
cbreak jtri: check !lol11:27
gitinfo jtri: A nifty view of branches, tags, and other refs: git log --oneline --graph --decorate --all11:27
cbreak that will show you how they relate11:27
after force pushing, you have to git fetch and then git reset --hard the local branches in every single clone that exists11:28
jtri (you can refer to it as nifty now :) i have it11:28
acharlieh left11:28
Sly1986 joined11:28
nevyn /win 411:28
tma996 joined11:29
jtri i'm still wondering when i merge voting with master?11:29
dobalina joined11:30
LucasKA joined11:30
the_cybersphinx joined11:30
jtri if there's no star on an intersection, do they not intersect?11:31
that all of a sudden makes the graph much less confusing11:31
codeforfun joined11:31
jtri the * is a point where things join, and the others are crossings but not touching?11:32
what are the double vertical stars **11:32
aChatir joined11:32
jtri just two points with a line between but the line is not drawn to safe space?11:32
cianuro left11:33
mikecmpbll joined11:34
skorgon_ joined11:34
Sp4rKy joined11:34
LucasKA left11:35
jtri ok, i think i see it now, i will force push both voting, and master, then it will be time to merge, correct?11:35
why force push before merging?11:35
p3lim left11:36
jtri also, i will only run > git reset --hard on the other clones, not the one' i'm fixing this stuff from, correct?11:36
rurufufuss joined11:37
gnu-man joined11:38
jtri also, does > "git push -f origin master voting" force push both simultaniously, or am i missing something?11:38
is that the same as > "git push -f origin master" followed by > "git push -f origin voting"11:38
ahmedelgabri joined11:39
whiskers75 joined11:41
EvilDMP joined11:41
EvilDMP how can I undo a git add when it's the very first add? git reset earns me a "fatal: Failed to resolve 'HEAD' as a valid ref."11:42
jtri well, i ran it: git push -f origin master voting and i can see it removed everything that looked like a branch, all one line now11:42
thevishy left11:43
cwillu_at_work joined11:43
St_Marx joined11:43
atrus joined11:43
ozymandias joined11:43
DANtheBEASTman joined11:43
simpleminds joined11:43
Edgan joined11:43
dmarr joined11:43
akersof joined11:43
valgrind left11:44
petey joined11:45
valgrind joined11:46
Sound left11:46
jtri so it looks like this now: http://dpaste.com/1547754/11:46
whiskers75nodejs11:46
nodejswhiskers7511:47
jtri i should catch master up to the top now, no?11:47
somehow...11:47
lfaraone_ joined11:47
jkremser joined11:47
leeN joined11:47
ewet joined11:47
doev joined11:47
tango_ joined11:47
deavid joined11:47
mitz joined11:47
bdavenport joined11:47
craigp joined11:47
preflex joined11:47
gwb3 joined11:47
conan joined11:47
Suprano joined11:47
looper joined11:47
akitada joined11:47
titusjose__ joined11:47
jab416171 joined11:47
ELLIOTTCABLE_ joined11:47
OliverJAsh joined11:47
knownasilya joined11:47
netiul joined11:47
TheFuzzball joined11:47
salamanderrake joined11:47
bhldev joined11:47
sami| joined11:47
Console joined11:47
grn joined11:47
lahwran joined11:47
ConstantineXVI joined11:47
SamB joined11:47
Mez joined11:47
bedouin joined11:47
dytrivedi joined11:47
_Parnic joined11:47
kini joined11:47
nickoe joined11:47
ryanakca joined11:47
dsop joined11:47
dwmw2_go` joined11:47
jeek joined11:47
kwmiebach joined11:47
konr joined11:47
Imdsm joined11:47
bauruine joined11:47
Fill joined11:47
NimeshNeema joined11:47
arcanis joined11:47
Werring joined11:47
asQuirreL joined11:47
abackstrom joined11:47
joevandyk joined11:47
adam_ joined11:47
skelterjohn joined11:47
dunpeal joined11:47
relipse joined11:47
cuppscakes joined11:47
pikpik joined11:47
joelmo joined11:47
jds joined11:47
marshmn joined11:47
mino joined11:47
adamm joined11:47
quadz joined11:47
TheMoonMaster joined11:47
gerard0 joined11:47
flexd joined11:47
spaceone joined11:47
stfn joined11:47
kulp joined11:47
saurik joined11:47
xrq joined11:47
jayne joined11:47
Ghjnut joined11:47
Tritania joined11:47
matthias_dev joined11:47
dickson.freenode.net set mode: +vvvv11:47
PhonicUK joined11:47
max_weller joined11:47
theForce1 joined11:47
dawik joined11:47
dickson.freenode.net set mode: +vvvv11:47
meatmanek joined11:47
iAsterisk_ joined11:47
gde33 joined11:47
so joined11:47
dickson.freenode.net set mode: +vvvv11:47
alip joined11:47
rom1504 joined11:47
dickson.freenode.net set mode: +vv11:47
enr joined11:47
enr left11:47
cbreak jtri: your decision when to merge11:48
enr joined11:48
cbreak the * are commits11:48
jtri: if you're on OS X or so, check out source tree11:48
it has a GUI with a better graph11:48
luto source tree <311:48
dyng joined11:48
cbreak jtri: force push removed the old merge commits11:49
you can make a new one if you want11:49
EvilDMP: git rm --cached should do it11:49
EvilDMP: git status should tell you11:49
EvilDMP thank you cbreak11:49
cbreak jtri: master is a bunch of commits behind11:49
cmpera joined11:49
petey left11:50
cbreak jtri: you can now check out master, then git merge voting (which will be fast forward). add --no-ff if you want an actual merge commit11:50
insejn left11:50
mvelioglu left11:51
silverfox_ joined11:51
rendar joined11:51
squentin joined11:51
JerryT joined11:51
NBeeuwsaert_ joined11:51
WaReZ joined11:51
ra4king joined11:51
slyfox joined11:51
Noctis_Lux joined11:51
nemesit|znc joined11:51
hike joined11:51
LeeXiaolan_ joined11:51
toothrot joined11:51
rfoust joined11:51
Barn3y joined11:51
polyzen joined11:51
eli joined11:51
RogerWS joined11:51
qsuscs joined11:51
kamal_ joined11:51
graphitemaster joined11:51
Eridius joined11:51
mikaelj_ joined11:51
kossy joined11:51
KK4MGV joined11:51
alindeman joined11:51
bitkid joined11:51
gtmanfred joined11:51
ToothlessGear joined11:51
Exio4 joined11:51
igalic joined11:51
unsignedint joined11:51
abyss42 joined11:51
frobware joined11:51
blueyed joined11:51
myme1 joined11:51
spudz_ joined11:51
spacepluk joined11:51
tomek joined11:51
ahf joined11:51
dpwrussell joined11:51
dsockwell joined11:51
einonm_ joined11:51
luminous joined11:51
runeg_ joined11:51
_ikke_ joined11:51
CareBear\ joined11:51
masak joined11:51
drbean joined11:51
zso joined11:51
ndngvr joined11:51
docwhat joined11:51
f8l left11:51
jtri ok, i'll try it with --no-ff11:51
charon joined11:52
charon left11:52
charon joined11:52
ahf left11:52
pikaren left11:52
ahf joined11:52
dyng left11:53
jtri yay, my little branch is there: http://dpaste.com/1547760/11:53
whiskers75 lol11:54
petertretyakov left11:54
mvelioglu joined11:55
insejn joined11:55
jtri so was > "git push -f origin master voting" same as > "git push -f origin master" and then > git push -f origin voting11:55
tgkokk joined11:55
gnu-man left11:55
cbreak yes11:57
gnu-man joined11:57
cbreak jtri: also, don't use -s ours unless you're sure you want it :)11:57
jtri so just merge by itself, no arguments and i should be safe?11:58
i don't mind fixing conflicts!11:58
matanya left11:58
jtri i'm going to run > git reset --hard on the other machine now11:58
p4denis joined11:58
jtri should i do that from master?11:58
f8l joined11:59
fphilipe left12:00
jtri should i run pull first?12:00
matanya joined12:00
fphilipe joined12:00
Sound joined12:00
fphilipe left12:02
cbreak jtri: you should git fetch origin first12:02
bremner jtri: fwiw, your use of ">" to suggest a prompt is a bit confusing, since it means output redirection.12:02
cbreak jtri: then git reset --hard origin/master while on master12:02
and so on12:02
that will kill local history12:02
promethazin joined12:02
jtri shit, i already messed it up, i did the reset first, then > git pull12:02
and i can tell it's messed up b/c the first south migration is missing12:03
p4denis left12:03
tma996 left12:03
jtri ok, ran git reset --hard origin/master while on master12:04
understood on the carrot12:06
gnu-man_ joined12:07
FerreusR joined12:08
gnu-man left12:08
petertretyakov joined12:08
jtri cbreak: ok, i think i'm back on track, thanks for you help!12:08
juliohm The thing I like most about Git is the way changes are tracked, we can add to the commit just the wanted subset of modifications12:08
jtri left12:09
juliohm This doesn't happen with Mercurial for instance12:09
juliohm is getting to Git12:09
phipes joined12:09
whiskers75 git ftw12:10
cbreak np :)12:10
pinage404 left12:10
pinage404 joined12:10
Noctis_Lux left12:11
koda joined12:11
jceb joined12:11
Exancillatus joined12:12
tma996 joined12:12
phipes left12:14
psyl0n joined12:14
kcj left12:14
marcjs joined12:14
jkremser left12:17
whiskers75windowssucks12:18
windowssuckswhiskers7512:18
juliohm left12:18
whiskers75disconnect12:18
disconnectwhiskers7512:19
_tpavel joined12:19
whiskers75codercat12:19
marcjs left12:19
codercatminetest12:19
minetestwhiskers7512:19
David joined12:20
Noctis_Lux joined12:24
David left12:25
fesoj joined12:25
VinceThePrince left12:26
mtk left12:27
elbeardmorez left12:29
khmarbaise joined12:29
elbeardmorez joined12:29
shruggar left12:29
promethazin left12:30
tirengarfio left12:30
mtk joined12:30
promethazin joined12:30
LucasKA joined12:31
khmarbaise left12:31
h0bbit_ left12:33
Advocation joined12:33
whiskers75iline12:33
ilineoline12:33
olinewhiskers7512:33
mrbubbles joined12:34
dougsland joined12:35
promethazin left12:35
LucasKA left12:35
m0ltar left12:36
hellopat joined12:37
_tpavel left12:38
albertgrala joined12:38
makubi left12:39
ShalokShalom joined12:39
tma996 left12:40
tma996 joined12:40
freestyl3r joined12:41
makubi joined12:41
LuxuryMode joined12:41
hellopat left12:42
ewet identity crisis ...12:42
whiskers75 lol12:42
sorry :P12:42
macben joined12:43
shruggar joined12:43
enr^ joined12:43
whiskers75 .12:46
jayrobot joined12:46
marcjs joined12:47
jkremser joined12:47
jkremser left12:47
jkremser joined12:47
macben left12:47
enr_ joined12:48
enr left12:48
_ikke_ ..12:48
codeforfun left12:48
dyng joined12:49
fphilipe joined12:50
gnu-man_ left12:50
enr^ left12:51
lifelike left12:52
ewnd9_ left12:52
lifelike joined12:52
KeiKun left12:54
KeiKun_ joined12:54
kent\n annoying: git ls-remote doesn't work on shallow clones :(12:54
Advocation left12:54
dyng left12:54
ciampix joined12:54
kent\n renders a fatal error about trying to fetch/clone.12:54
mklappstuhl joined12:54
cbreak kent\n: just cd out of it12:55
kent\n oh, as in 'ls-remote .' bails, but 'cd ../; ls-remote foo' is good? Thats weird.12:56
dobalina left12:56
cbreak you'll have to use the URL12:57
ewet left12:57
ewet joined12:57
kent\n "have to use the url" ?12:58
m-o-s joined12:58
ewet left12:58
doener joined12:58
kent\n its not budging regardless what I try.12:58
cbreak git has no clue what foo is12:58
you have to use ssh://git@foo.local/foo.git12:59
from outside the git repo12:59
pantsman left12:59
cbreak because then you're not inside a shallow clone :)12:59
kent\n ls-remote ./foo # no good ls-remote file://<path>/ # no good either12:59
cbreak it will12:59
your problem is that it doesn't work in shallow clones13:00
pfFredd joined13:00
cbreak if you cd out, then you're no longer in a shallow clone13:00
Mode-M joined13:00
kent\n if I'm using the non-shallow URI, well, of course _that_ will work.13:00
cbreak the remote must be non-shallow anyway13:00
but that's a given13:00
kent\n right. But the reason I'm using ls-remote in the first place is because its such an old api it works back to git 1.413:00
cbreak yeah, and?13:01
shallow clones can't be used as remotes13:01
ewet joined13:01
kent\n and it allows me to do things I'd usually need other functions/parameters to get working, things that don't work on <git 1.613:01
ie: i'm just wanting to get branch names.13:01
jcvfen joined13:01
cbreak git branch13:02
kent\n is useless, because you have to filter out the decorations13:02
osse for-each-ref ?13:02
_ikke_ There are plumbing commands13:02
cbreak kent\n: nope, no decorations13:03
kent\n * # A decoration13:03
V1TSK joined13:03
cbreak unless you want them13:03
for-each-ref, show-ref, ...13:03
Freeman42 left13:03
kent\n I was using for-each-ref, but I switched to ls-remote for some reason ( cant remember why , backcompat support )13:04
cbreak obviously you can only use local commands13:04
dobalina joined13:04
kent\n oh, right. for-each-ref doesn't exist on <1.513:05
_ikke_ and show-ref?13:05
cbreak 1.5 is irrelevant.13:05
mrbubbles left13:05
cbreak 1.7 is four years old already13:05
mrbubbles joined13:06
cbreak even Mac OS X ships with 1.8.3.413:06
arietis left13:06
osse cbreak: pre-installed? o_O13:06
kent\n Yes. I'm writing a unifying wrapper to support as many versions of Git as possible, in Perl, where supporting Perl >10 years old is stil "normal"13:06
cbreak osse: no, install on demand13:06
osse: if you get Xcode or the compiler command line tools13:06
jcvfen- joined13:06
osse ahh13:06
cbreak I am not sure how the latter work, but there seem to be stubs for the programs13:07
so if you type gcc on the command line, it'll ask you if you want to install them13:07
jcvfen left13:07
cbreak osse: apple seems to be a big fan of git13:08
kent\n In my tooling stack, I can force users to upgrade to newer Perl packages easily, so I can progressively expand support for things, but its harder to get consumers to upgrade git, and I literally have test reports from our network of automated testers with fails that occur due to installs of git 1.4*13:10
phipes joined13:10
_ikke_ whut13:10
mfulz joined13:10
cbreak 1.4 is like... 2007 or so?13:11
2006 even13:11
kent\n Yeah. But that said, I get test reports from Perl 5.8, which are like, 200313:11
cbreak morons who can't even update in 8 years are probably not worth the effort13:11
kent\n *shrugs* I can support it reasonably easy, so I do.13:12
Advocation joined13:12
kent\n but upgrading modules is easy, upgrading binary deps, much harder13:12
cbreak if the OS itself doesn't support it, get something like homebrew.13:13
kent\n its sensible for devs, and I really do wish people would upgrade, and we do encourage using the latest of everything13:13
cbreak it's a kind of a "package manager"13:13
kent\n but we're also in the reality where people have old things in production, and even though they want to upgrade it too, they're not allowed to13:13
mostly, because of the upgrade techincal debt.13:13
macben joined13:13
cbreak good thing that git is irrelevant in production13:13
qsuscs yup13:13
cbreak it's a development tool13:14
qsuscs Siemens still uses cvs13:14
and now they consider to use svn. maybe.13:14
alansaul-laptop joined13:14
unreal left13:14
kent\n though I still have non-humans with git installed on their automated testing boxes, and I can't exactly get them to upgrade.13:15
phipes left13:15
cbreak you can ignore those outdated testing boxes since they evidently don't test anything useful13:16
kent\n but this is not just my problem either, everyone who writes tools based on git has this problem and they don't see it till they get the reports back.13:16
So I'm trying to write a somewhat unifying api that gets more git features available without them having to innately know what is and isnt supported13:16
bernalex left13:16
bernalex joined13:16
kent\n so that they get less erroneous error reports that arent' relevant to them13:16
cbreak sounds like a waste of time13:17
reimplementing git so you can install more software instead of updating git13:17
mklappstuhl left13:17
kent\n We do incidentally have a module that munges git things without git at all, but I'd rather rely on git itself as much as possible13:17
unreal joined13:17
kent\n ( its not reimplementing, just wrapping at this point )13:17
arietis joined13:17
wrouesnel1 joined13:17
Advocation left13:18
macben left13:18
cbreak it sounded like you were trying to reimplement for-each-ref :)13:19
listing branches in a git repo without git isn't trivial13:19
m-o-s left13:19
cbreak there are packed refs that require you to look into binary files13:20
mvelioglu left13:20
mklappstuhl joined13:20
jceb left13:21
hayalet joined13:21
kent\n yeah, I get that, which is one of the reasons I'm trying to avoid dealing with raw .git/ access directly myself13:21
hayalet left13:22
rue joined13:22
rue left13:22
kent\n I was bitten somewhat when I was using the "no git" tool and a repository suddenly started shipping with GPG sigs, which caused all sorts of fun because the code was too naive to decode the commit attributes13:22
kent\n hasn't tried to see how old git handles this mind, it might be no better13:22
mvelioglu joined13:23
codeforfun joined13:26
ewnd9_ joined13:27
ingentis joined13:28
thevishy joined13:29
marhaban joined13:29
mtk left13:29
Watabou left13:30
jkremser left13:30
carbon joined13:30
Kulrak left13:30
takamichi joined13:31
insejn left13:31
LucasKA joined13:31
carbon left13:31
tgkokk left13:32
pikaren joined13:32
glebihan left13:32
sq-one left13:32
jayallen left13:32
V1TSK left13:33
jayallen_ joined13:33
mikecmpbll left13:34
glebihan joined13:34
Noldorin joined13:35
LucasKA left13:36
eletuchy left13:37
doev left13:37
eletuchy joined13:37
Nizumzen joined13:38
psyl0n left13:41
axl_ joined13:42
tgkokk joined13:42
eletuchy left13:42
psyl0n joined13:43
tobias__ joined13:43
cmpera left13:44
Kulrak joined13:44
macben joined13:44
tgkokk left13:44
Kulrak left13:45
Kulrak joined13:46
petey joined13:46
tgkokk joined13:46
kent\n alternatively, is there a safe way to detect a shallow repository? I can code around the problem a differently if I have to13:46
tgkokk left13:48
aard_ joined13:48
tgkokk joined13:48
tgkokkGuest4040313:49
Guest40403 left13:49
thevishy left13:49
fphilipe_ joined13:49
macben left13:49
doev joined13:50
petey left13:50
cbreak kent\n: sure13:51
tgkokk joined13:51
Kayra joined13:51
fphilipe left13:52
cbreak it should be in the config13:53
thrakcattack left13:53
cbreak cat .git/shallow13:54
m0ltar joined13:54
earny left13:54
thrakcattack joined13:55
pantsman joined13:55
xlinkz0 joined13:56
dougsland left13:56
mtk joined13:56
doev left13:57
tirengarfio joined13:57
Noldorin left13:57
xlinkz0 i did git -rm '*' thinking that it would only remove staged removes13:57
how do i go back and actually do that? :D13:58
CheckDavid joined13:58
doev joined13:58
adaptr left13:58
p4denis joined13:59
harish_ joined13:59
moritz git reset --hard HEAD # maybe !backup first13:59
gitinfo Worried about your data while trying out stuff in your repo? To back up commit history on all branches/tags: `git clone --mirror`. To backup everything, including work tree and staging area: `tar cf repo-backup.tar repodir`. Or do your experiment in a throwaway clone instead. See also http://sethrobertson.github.com/GitBestPractices/#backups13:59
hyperboreean left13:59
doev left13:59
psyl0n left13:59
doev joined14:00
xlinkz0 thanks14:00
harish left14:01
pinage404 left14:01
psyl0n joined14:01
psyl0n left14:02
psyl0n joined14:02
kent\n rsync -avp $REPO/ $NEW/ # is what I've been known to do, just no idea how safe that is with regard to hardlinks14:02
cads left14:02
aChatir left14:02
p4denis left14:04
harish_ left14:04
cbreak it'll probably break them14:05
which is no correctness problem14:05
arvind_khadri joined14:05
doev left14:05
doev joined14:07
tummy__ joined14:07
brainproxy_brainproxy14:07
Freeman42 joined14:07
eletuchy joined14:08
tummy_ left14:09
bull_g joined14:10
bull_g left14:10
cads joined14:10
quup_ left14:10
phipes joined14:11
chamunkszz_chamunks14:12
takamichi left14:12
OleVik joined14:12
fphilipe joined14:12
JSharpe2 joined14:12
WaReZ left14:13
fphilipe_ left14:15
phipes left14:15
barbles left14:16
MindfulMonk joined14:16
zz_chamunkschamunks14:19
hellopat joined14:19
alansaul-laptop left14:19
sohail joined14:20
sohail left14:20
sohail joined14:20
jayrobot left14:21
JSharpe2 left14:23
Nizumzen left14:25
jayrobot joined14:26
aard_ left14:26
_tpavel joined14:27
LucasKA joined14:32
h0bbit_ joined14:32
Exancillatus left14:36
Kayra left14:36
LucasKA left14:37
WaReZ joined14:37
King_Hual joined14:38
King_Hual` joined14:38
BSaboia joined14:39
tma996 left14:40
OleVik Anyone able to give a hand in setting up a ssh config correctly? Having a bit of trouble with my /.ssh/config file and connecting to my server14:40
Diemuzi joined14:40
gitinfo set mode: +v14:40
jave left14:40
Neptu left14:41
bgerber left14:41
mvelioglu left14:42
bgerber joined14:42
jave joined14:42
Neptu joined14:43
mvelioglu joined14:43
sohail left14:43
LuxuryMode left14:44
Baluse left14:45
Baluse joined14:45
jatt joined14:46
BSaboia left14:46
dougsland joined14:46
yhager joined14:47
johnmilton joined14:47
BSaboia joined14:47
LuxuryMode joined14:48
gnu-man joined14:49
mvelioglu left14:50
WaReZ left14:50
ws2k3 left14:50
ws2k3 joined14:50
sohail joined14:52
sohail left14:52
sohail joined14:52
mvelioglu joined14:53
promethazin joined14:54
giusef joined14:54
tnkhanh joined14:54
tnkhanh hi14:54
gitinfo tnkhanh: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.14:54
ws2k3 left14:54
promethazin left14:55
bhldev_ joined14:55
MatrixiumnCaveJohnson14:55
bhldev left14:55
promethazin joined14:55
petertretyakov left14:55
beastd joined14:56
ehmatthes joined14:57
M-ou-se left14:57
Nizumzen joined14:58
oriba joined14:58
M-ou-se joined14:58
petertretyakov joined14:58
m0viefreak joined14:59
promethazin left14:59
xlinkz0 left15:00
xlinkz0_ joined15:00
matanya left15:01
WaReZ joined15:02
khmarbaise joined15:02
Nicholas_Rishel joined15:05
mizu_no_oto joined15:06
koda left15:07
starkhalo joined15:07
M-ou-se_ joined15:10
Dreamer3__Dreamer315:10
ws2k3 joined15:10
Sound left15:11
M-ou-se left15:11
doev left15:11
DrShoggoth joined15:11
phipes joined15:11
King_Hual_ joined15:11
axl_ left15:13
yhager left15:13
cads left15:13
bhldev_ left15:13
bhldev joined15:14
fphilipe left15:14
King_Hual left15:14
King_Hual joined15:14
DrShoggoth left15:14
ws2k3 left15:15
DrShoggoth joined15:15
h0bbit_ left15:15
M-ou-se joined15:15
ws2k3 joined15:15
King_Hual` left15:15
angelsl left15:15
fphilipe joined15:15
h0bbit_ joined15:16
M-ou-se_ left15:16
angelsl joined15:16
phipes left15:16
jcvfen- left15:17
macben joined15:17
crazydiamond joined15:18
plasticle joined15:18
matheus23 joined15:19
Gavrisimo joined15:19
ingentis left15:19
Kayra joined15:19
David joined15:20
macben left15:22
ewnd9_ left15:22
ewnd9 joined15:22
hyperair left15:22
plasticle left15:23
shruggar left15:23
mklappstuhl left15:23
plasticle joined15:23
M-ou-se left15:23
ewnd9 left15:23
M-ou-se joined15:24
David left15:25
olivion joined15:25
ewnd9 joined15:26
john2x left15:27
DrShoggoth left15:27
jan1337z left15:27
DrShoggoth joined15:27
ewnd9 left15:28
ewnd9 joined15:28
sohail left15:28
jkremser joined15:29
jkremser left15:29
jkremser joined15:29
nlogn joined15:30
M-ou-se left15:32
LucasKA joined15:32
M-ou-se joined15:32
khmarbaise left15:36
khmarbaise joined15:37
mklappstuhl joined15:37
Gavrisimo left15:37
LucasKA left15:37
Gavrisimo joined15:37
khmarbaise left15:38
h0bbit_ left15:38
khmarbaise joined15:38
glebihan left15:38
glebihan joined15:39
godgodgodgo joined15:40
hyperair joined15:41
jkremser left15:42
_5kg left15:42
Freeman42 left15:43
petey joined15:45
axl_ joined15:45
Kayra left15:45
DrShoggoth left15:46
BSaboia left15:47
DrShoggoth joined15:47
mizu_no_oto left15:47
zeppo joined15:49
HicksD left15:53
Ratler left15:55
fphilipe left15:55
BSaboia joined15:55
bvi left15:55
HicksD joined15:56
Ratler joined15:56
Ratler left15:56
Ratler joined15:56
hyperair left15:56
pulpfiction joined15:56
pulpfiction heyo, i'm new to git, but i have one stupid question15:57
i'm pretty sure i'm missing something15:57
bvi joined15:57
pulpfiction but when i do git status, it shows me 1 new file and 2 modified files15:57
why there's nothing when i do git diff?15:58
pikaren left15:58
pulpfiction the files are already added for commit (they are green on git status)15:58
hyperair joined15:58
luto git diff --cached15:58
shows added files15:58
pulpfiction oh yes, that's nice15:58
exactly that15:58
thank you luto15:59
luto you're welcome :)15:59
p4denis joined15:59
M00sL0gB0t left16:01
M00sL0gB0t joined16:01
GODDOG joined16:02
sohail joined16:02
sohail left16:02
sohail joined16:02
p4denis left16:04
dougsland left16:05
m0ltar left16:05
dougsland joined16:05
Mode-M left16:05
dsdeiz left16:05
mvelioglu left16:06
marhaban left16:06
Mode-M joined16:07
cagedwisdom left16:08
dglambert joined16:08
pekster joined16:09
livingstn joined16:09
livingstn left16:09
mvelioglu joined16:10
hyperair left16:11
pinage404 joined16:11
yhager joined16:12
dprophit joined16:12
w0ng joined16:12
aucecil joined16:12
zz_karupanerura joined16:12
dickson.freenode.net set mode: +v16:12
phipes joined16:12
Dougie187 joined16:14
psyl0n left16:15
jnewt joined16:15
takamichi joined16:16
phipes left16:17
jnewt it's been a bit since i've used git, so i want to make sure i have this straight in my head. i've got a bunch of changes (dozens of files in my working directory). some are staged (don't remember why), and i'm also behind the origin.16:17
Gavrisimo left16:17
halu joined16:17
jnewt if i do git reset HEAD -- ./* none of my working directory files will be changed, i'll just clear the list of files to be committed16:18
mvelioglu left16:18
Nevik jnewt: yes. git status tells you as much16:18
jnewt then because it says i can fast forward, i can pull, also without changing the working directory.16:19
noname001__ left16:19
nemesit|znc left16:19
Nevik probbly. if not, pull will abort telling you about it16:19
jnewt then i'm basically cleaned up, i can stage and commit the files i want16:19
Nevik in which case, stash, pull, stash pop16:19
yeap16:19
jnewt ok, i was unsure if pull would warn or abort or simply overwrite unstaged / committed files16:20
KeiKun_KeiKun16:20
Nevik nope, pull/merge will not overwrite WC changes16:20
Dougie187 left16:20
m0ltar joined16:20
fesoj left16:20
grawity a merge aborts if you have uncommitted changes16:20
if all of them are committed, though, it would try to, uh, merge them.16:20
nemesit|znc joined16:21
fire joined16:21
guampa left16:22
tplaner joined16:22
guampa joined16:23
pantsman left16:23
nemesit|znc left16:23
nemesit|znc joined16:24
diegoviola joined16:24
eijk_ joined16:24
KeiKun left16:26
KeiKun_ joined16:26
ErKa joined16:26
nemesit|znc left16:26
phipes joined16:26
Gitzilla left16:26
nemesit|znc joined16:26
dsdeiz joined16:27
Gitzilla joined16:27
nemesit|znc left16:29
jan1337z joined16:30
nemesit|znc joined16:30
JSharpe2 joined16:30
mizu_no_oto joined16:30
mfulz left16:31
_ikke_ Note that merge can just continue when the uncomitted changes wouldn16:32
wouldn't have to be touched16:32
LucasKA joined16:33
becks__ joined16:33
becks__ left16:33
mvelioglu joined16:34
yhager left16:34
dsdeiz left16:34
ewet I'd say that's a prime case to stash your changes, do all the things and pop the stash again. you wouldn't have to think about your changes at all this way.16:36
salamanderrake left16:37
Gavrisimo joined16:38
m0ltar left16:38
thiago joined16:38
whiskers75meow16:38
phipes left16:38
meowwhiskers7516:39
petertretyakov left16:39
salamanderrake joined16:39
movedx joined16:39
movedx Hello. I have added ignores in my project, but I cannot remove files I added before the ignores were put in place: https://github.com/mrcrilly/rita/tree/master/rita -- I've tried 'git rm --cached', but that's not working, git claiming nothing matches the pattern I am giving.16:40
I just want to clean up that directory to only contain source code and the configuration so I can place the other files elsewhere.16:41
milki movedx: !untrack16:41
gitinfo movedx: To remove a file from git's tracking, without deleting it from your working tree, `git rm --cached <file>`. Note that any repo which pulls this change will delete their local copy of that file. You can "bring it back" using `git checkout HEAD@{1} file` immediately after pulling / merging16:41
gebi joined16:41
milki movedx: and !repro since you did that16:41
gitinfo movedx: Please paste (using https://gist.github.com/ or similar) a transcript (https://gist.github.com/2415442) of your terminal session -- or, even better for complex issues, design a minimal case in which your problem can be reproduced, and share it with us. This will help immensely with troubleshooting.16:41
mfulz joined16:41
alansaul-laptop joined16:41
tgkokk left16:42
Nicholas_Rishel left16:43
gebi left16:44
jayallen joined16:44
movedx Ah, it's my fault, milki. Seomthing I keep doing all the time: looking at the wrong branch in Github :)16:44
jayallen_ left16:44
mvelioglu left16:45
gwb3 left16:45
dutis joined16:45
dutis left16:45
kent\n personally I don't understand the fuss about promoting 'pull'. I never ever want pull, I always want 'git remote update' && compare histories && apply merges/rebases as applicable16:46
Kayra joined16:46
milki movedx: that doesnt sound related but ok o.O16:46
dutis joined16:46
milki kent\n: not everyone is patient enough to do that16:46
kent\n I guess it does require patience, but so many people get bitten by how magical pull is16:47
axl_ left16:47
kent\n "merging with your current tree" is one of the residual behaviours that made other scms' hateful.16:47
gwb3 joined16:47
gwb3 left16:47
offby1 I too avoid pull16:48
mvelioglu joined16:48
Nizumzen left16:48
kent\n there are worse things I guess, like HG's branch implementation which gives user a workflow that goes "Oh hey, look, a branch appeared upstream, merge it?"16:49
movedx milki: The master branch hasn't been merged with the development branch, so the maste is still tracking those files, right?16:49
kent\n and I had a nightmare because idiot cow-workers kept merging branches that were not supposed to be merged16:49
gwb3 joined16:49
mklappstuhl left16:49
sq-one joined16:49
_ikke_ Most people refuse any knowledge about how vcs's work16:50
They just want to throw their code over the hedge16:50
JSharpe2 left16:51
kent\n I have frustrations with people who are smart, but their obstacle to git is "Git doesn't do X like CVS does" -> "here is how you do that " -> "But I don't want to learn" *faceplam*16:51
bremner to be fair, they mostly don't want to know how their code works, either16:51
mklappstuhl joined16:51
khmarbaise left16:52
tgkokk joined16:52
khmarbaise joined16:53
takamichi left16:53
shinnya left16:53
takamichi joined16:53
rethus joined16:54
ianmcorvidae|alt joined16:54
CareBear\ kent\n : I get disappointed by that too16:54
offby1 _ikke_: I hope that's not true16:54
y'all harshing my mellow16:54
kent\n I'll give you the upside, the pessimists optimisim: Everyone on the internet is wrong :D16:55
BinGOs that isn't right :p16:55
ianmcorvidae left16:55
tmcmahon joined16:55
_ikke_ If you don't want to learn, you might want to consider a career switch16:56
kent\n I am in the set labelled "Everyone"16:56
mklappst_ joined16:56
mklappstuhl left16:56
codeforfun left16:57
tmcmahon left16:57
offby1 I'm a barber; I shave those men who don't shave themselves16:57
Nevik offby1: do you make house calls :o16:58
glebihan left16:58
wrouesnel1 left16:58
BinGOs just shaves yaks.16:58
kent\n offby1: do you shave yaks, and or cats?16:58
offby1 nope nope16:58
glebihan joined16:59
kent\n darn16:59
offby1 someone shaved (well, discretely trimmed) the neighbor cat often visits. It looks good on him.16:59
rethus left16:59
offby1 Quite they mystery who done it, though.16:59
kent\n goes back to exploring the wild countryside of Yakistan, ploughing through impenetrable long forests of yak hair16:59
Nevik offby1: i would have wanted to rent you :o17:00
offby1 I'd be too busy trying to decide if I should shave myself or not17:02
LucasKA left17:03
Nevik lolol17:03
hwrdprkns joined17:05
rethus joined17:05
Kulrak left17:05
Advocation joined17:05
Gavrisimo left17:07
nnyk_ joined17:07
diegoviola left17:08
phipes joined17:09
travisstaton joined17:09
rethus left17:10
albertgrala left17:11
npatten joined17:12
ianmcorvidae|altianmcorvidae17:12
Exancillatus joined17:12
phipes left17:14
Sly1986 left17:16
arietis left17:16
hyperair joined17:16
nemesit|znc left17:17
nemesit|znc joined17:17
BSaboia_ joined17:18
Goplat joined17:19
Shusshu joined17:19
nemesit|znc left17:19
nemesit|znc joined17:20
BSaboia left17:20
Noldorin joined17:21
Shusshu left17:21
sorressean joined17:21
blarson joined17:21
macben joined17:21
girishr joined17:22
KeiKun_ left17:22
nemesit|znc left17:22
sorressean I have a quick question. I am working on a game engine and then I have my game on top of that. my engine is separate code wise, and in a different repo. I would like to type git pull though and update the engine under the game and then update the game if that is possible. Is there a way to merge two repos somehow?17:22
nemesit|znc joined17:22
cmpera joined17:23
KeiKun joined17:23
richwestcoast left17:23
richwestcoast joined17:24
kermit joined17:24
nemesit|znc left17:25
shruggar joined17:25
nemesit|znc joined17:25
macben left17:26
_ikke_ sorressean: Sounds like !subtree17:26
gitinfo sorressean: The subtree merge method is great for incorporating a subsidiary git repo into your current one with "unified" history. Read http://git-scm.com/book/en/Git-Tools-Subtree-Merging for more info, or try one of the !subtree_alternatives17:26
rurufufuss left17:26
sorressean awesome, thanks17:27
_ikke_ Note that subtree merge is not part of git-core yet17:27
kerrick joined17:28
Diemuzi left17:28
ewet it's also less than elegant, but apparently one of the very few strategies available ...17:29
arietis joined17:29
giusef left17:30
offby1 never tried subtree17:30
pekster left17:30
_ikke_ me neither17:30
pekster joined17:30
SHyx0rmZ left17:31
blarson I've got a git master that can't complete being pushed too because it runs out of memory. How do I clean up this mess so I can use it?17:31
theRealGentleman joined17:32
_ikke_ !big_repo17:32
gitinfo [!large_repos] Git can be slow in the face of large repositories. There are git-config options which can help. pack.threads=1; pack.deltaCacheSize=1; pack.windowMemory=512m; core.packedGitWindowSize=16m; core.packedGitLimit=128m. Other likely ones exist.17:32
alansaul-laptop left17:32
ehmatthes left17:33
hyperair left17:33
lasers left17:34
hyperair joined17:35
olivion left17:35
LucasKA joined17:35
lazers joined17:36
ahmedelgabri left17:37
petey left17:38
petey joined17:39
richwestcoast left17:39
mahler_io left17:39
matanya joined17:39
harobed_ joined17:39
harobed_ left17:40
richwestcoast joined17:40
harobed_ joined17:40
nemesit|znc left17:41
petey left17:41
nemesit|znc joined17:41
eijk joined17:41
petey joined17:41
takamichi left17:41
flebron left17:42
GODDOG left17:43
takamichi joined17:43
eijk_ left17:43
tchan left17:43
nemesit|znc left17:44
nemesit|znc joined17:44
CKyle joined17:46
edwardly left17:46
Advocation left17:47
CKyle left17:47
boblee left17:48
nnyk_ left17:48
Kromitvs Hy. How do I find out in which commit a bug, or a line of code was introduced? Do I have to checkout every commit manually?17:53
grawity Kromitvs: `git bisect` is useful for this17:53
and `git log -G` for searching diffs17:54
canton7 Kromitvs, if you're looking for the history of a line of code, git blame / git gui blame. if you're searching history for when a line was added / removed, git log -S / -G17:54
if you're looking for the commit which breaks a particular test, git bisect17:54
grawity Kromitvs: basically, do `git bisect start <badcommit> <goodcommit>` and go17:54
canton7 yeah, there are some good examples on the man page17:54
tchan joined17:55
tchan left17:55
tchan joined17:55
Kromitvs Ok. Thanks for helping17:55
rdd left17:55
LuxuryMode left17:55
nemesit|znc left17:56
nemesit|znc joined17:58
bob_4234 joined17:58
KeiKun left17:58
KeiKun joined17:58
el3ctron_ joined17:59
p4denis joined18:00
phipes joined18:00
DrNick left18:00
bob_4234 left18:01
Silmarilion left18:01
gnu-man left18:02
nnyk_ joined18:02
fesoj joined18:02
craigp left18:03
kerrick left18:04
jnavila joined18:04
petey left18:04
edwardly joined18:04
p4denis left18:04
petey joined18:05
jayallen left18:06
jayallen_ joined18:06
gnu-man joined18:06
aweorit joined18:07
fesoj left18:07
LuxuryMode joined18:07
skorgon_ left18:07
travisstaton left18:08
aweorit is it me or eol handing in git is completely fucked up18:09
petey left18:09
_ikke_ aweorit: it's you18:10
mribeirodantas joined18:10
_ikke_ !crlf18:10
gitinfo to fix problems with line endings on different platforms, check out http://line-endings.gitrecipes.de/18:10
swillits joined18:11
DrNick joined18:12
Kromitvs left18:12
slyfox left18:17
craigp joined18:17
a-l-e joined18:18
eijk left18:18
slyfox joined18:18
slyfox left18:18
slyfox joined18:18
bl33 left18:19
bl33_ left18:20
insejn joined18:20
fire left18:20
David joined18:20
CKyle joined18:21
aweorit it seems overly complicated18:22
Lunatrius Hey, quick question. "warning: push.default is unset; its implicit value is changing in ...", which one will it chose by default, matching or simple (MSYSGIT)?18:23
offby1 doesn't the message tell you? I certainly don't know18:24
bl33 joined18:24
_ikke_ currently, upstream. git 2.0 will use simple18:24
Lunatrius Ah, I'm stupid. Don't mind me.18:24
David left18:25
gnu-man left18:25
_ikke_ It's matching by default, not upstream18:26
CKyle left18:26
tnkhanh left18:26
bl33_ joined18:26
petey joined18:28
sorressean I am trying to add the most recent git commit logs to my mysql database with post-receive. I have something using git log, but Ican't tell if there's a way to just get the most recent commit(s) that were just pushed.18:29
psyl0n joined18:29
moritz sorressean: post-receive hooks receive the commit ranges on STDIN18:29
man githooks18:30
gitinfo the githooks manpage is available at http://jk.gs/githooks.html18:30
sorressean ah, thanks.18:30
mizu_no_oto left18:30
CKyle joined18:30
AaronMT joined18:31
aard_ joined18:31
LucasKA left18:32
Advocation joined18:32
amcsi joined18:32
gnu-man joined18:32
OleVik left18:33
eliasdiem joined18:33
Nizumzen joined18:33
sorressean ur, I'm sorry. I'm using post-receive. I thought that sounded off, since it doesn't show anything but the object being updated.18:33
ewet left18:34
sorressean I see the reference to pre-receive.18:34
moritz This hook executes once for the receive operation. It takes no18:35
arguments, but gets the same information as the pre-receive hook does18:35
on its standard input.18:35
takamichi left18:35
moritz that's what 'man githooks' says about post-receive18:35
gitinfo the githooks manpage is available at http://jk.gs/githooks.html18:35
moritz ah, that's what you probably meant18:35
sorressean eah. that's what I'm saying. I had them backwards, but it doesn't actually receive the range.18:36
eliasdiem left18:36
sorressean it receives the objects being changed.18:36
moritz sorressean: maybe you just meesed up reading the input?18:37
sorressean: 'cause I know it worked for me, I've written a post-receive hook18:37
CKyle_ joined18:37
Kayra left18:37
sorressean moritz: from the docs: <old-value> SP <new-value> SP <ref-name> LF so old-value is the old value, new-value is the new object name and then it has the object.18:38
moritz not name18:38
sha118:38
and once you have them, you can run git log $old..$new18:38
plus some options for formatting, to make it easier to parse the output18:39
sorressean ah. that makes sense, thank you.18:39
krononaut joined18:40
CKyle left18:40
Goplat left18:41
CKyle_ left18:42
clarkfischer left18:42
nemesit|znc left18:43
nemesit|znc joined18:43
heliomaster left18:43
madewokherd joined18:45
nurey joined18:46
enr_ left18:47
petey left18:50
nemesit|znc left18:50
nemesit|znc joined18:50
petey joined18:50
zeppo left18:51
nnyk_ left18:51
Nizumzen left18:52
CKyle joined18:52
bl33_ left18:53
bl33 left18:53
mizu_no_oto joined18:53
ra4king left18:53
macben joined18:54
Advocation left18:54
petey left18:55
dyng joined18:55
CKyle left18:56
jayallen joined18:56
acharlieh joined18:56
mklappstuhl joined18:57
jayallen_ left18:57
Exancillatus left18:58
BSaboia_ left18:58
dyng left18:59
macben left18:59
mklappst_ left18:59
zeppo joined19:00
acharlieh left19:01
LuxuryMode left19:02
BSaboia joined19:03
Acidnerd joined19:03
master_j left19:05
eletuchy left19:05
dougsland left19:05
swillits left19:05
dougsland joined19:05
ingentis joined19:08
CKyle joined19:08
Nicholas_Rishel joined19:08
harobed_ left19:08
Kayra joined19:09
krizzii joined19:10
harobed joined19:10
harobed left19:10
harobed joined19:11
arietis left19:11
aweorit` joined19:11
Kayra left19:12
zeppo left19:12
Kayra joined19:13
zeppo joined19:13
pheaver left19:13
longbeach joined19:14
aweorit left19:15
AaronMT left19:16
CKyle left19:16
JesseCW joined19:18
JesseCGuest4218219:18
Guest42182 left19:18
JesseCW left19:18
Silmarilion joined19:19
rpg joined19:19
adamwathan joined19:21
cads joined19:21
danecando joined19:22
hiroyuki joined19:23
angelsl left19:24
khmarbaise left19:25
macben joined19:25
kent\n annoying. for-each-ref is *less* useful than ls-remote19:26
because ls-remote supports 'refs/heads/**' while for-each-ref does not.19:26
Kayra left19:26
kent\n which means that wil only return heads/foo and heads/bar , but not heads/foo/bar19:28
ErKa left19:28
LucasKA joined19:29
momomomomo joined19:29
macben left19:30
eletuchy joined19:30
daivyk joined19:31
zapb left19:31
kent\n argh. git for-each-ref 'foo/' # is the same as ls-remote 'foo/**' , but ls-remote 'foo/' is the same as for-each-ref ''19:32
_W_ left19:34
hiroyuki left19:34
LucasKA left19:35
_W_ joined19:35
petey joined19:35
hwrdprkns left19:36
falconfox joined19:37
toiletbowlJoel joined19:39
robbyoconnor left19:39
gchristensen joined19:39
robbyoconnor joined19:39
LuxuryMode joined19:40
gchristensen Hi, will git clone --mirror clone all refs, such as I never need to access the origin again?19:41
oriba_ joined19:41
master_j joined19:42
pinage404 left19:44
tgkokk left19:44
robbyoconnor left19:44
zapb joined19:44
oriba left19:44
tgkokk joined19:45
robbyoconnor joined19:45
_ikke_ gchristensen: Yes, it will fetch all refs19:46
petey left19:47
petey joined19:48
fesoj joined19:49
zeppo left19:50
tgkokk left19:50
scott3 joined19:50
gchristensen wonderful, _ikke_. are there other steps I should consider to do a final archive? these repos are about to be removed from the primary git server, due to their age and inactivity19:50
robbyoconnor left19:50
jceb joined19:51
robbyoconnor joined19:51
scott3 How do I download from github? I've been using Cola Git GUI but after I put the URL in it does nothing? I'm trying to download https://github.com/betfair/API-NG-sample-code/tree/master/java19:51
gitinfo set mode: +v19:52
scott3 seems like i can only download 1 file at a time using the website19:52
Plouj- left19:52
blahdodo joined19:53
geomyidae joined19:53
kent\n scott3: you have to point to the repository base address, not an individual resource19:54
dreiss joined19:54
kent\n which here, would be: https://github.com/betfair/API-NG-sample-code.git #19:55
if you're more used to SVN/CVS, just know you can't do clones of directories in git like you can with them19:55
scott3 I'm not used to SVN/CVS either19:56
macben joined19:56
scott3 I'll give that a try although it looks like it wants to download code for other languages as well19:56
mvelioglu left19:57
AaronMT joined19:57
Exancillatus joined19:58
scott3 yeah that's worked, thanks19:58
khmarbaise joined19:58
petey left19:59
harobed_ joined19:59
harobed_ left19:59
petey joined19:59
tgkokk joined20:00
harobed_ joined20:00
p4denis joined20:00
scott3 left20:00
macben left20:00
harobed left20:01
tgkokk left20:01
tgkokk joined20:01
dutis left20:02
Exancillatus left20:03
sohail left20:03
petey left20:04
pheaver joined20:04
npatten left20:04
p4denis left20:05
tgkokk left20:06
sjohnson left20:06
veebers joined20:07
primitive joined20:08
pantsman joined20:08
YuviPandazz_YuviPanda20:09
Mode-M left20:10
zeppo joined20:11
zeppo left20:12
Exancillatus joined20:12
kcj joined20:12
jayallen left20:13
LuxuryMo_ joined20:14
cmpera left20:14
jayallen joined20:15
enr joined20:15
LuxuryMode left20:16
David joined20:17
Exancillatus left20:17
enr left20:19
enr joined20:20
mvelioglu joined20:20
acharlieh joined20:20
Silmarilion left20:21
aard_ left20:21
craigp left20:23
ArcTanSusan joined20:23
KeiKunGuest4001020:23
KeiKun_ joined20:23
Guest40010 left20:24
David left20:24
calcifea_ joined20:25
calcifea left20:26
harobed_ left20:27
macben joined20:27
ArcTanSusan left20:27
Watabou joined20:27
JerryT left20:28
sq-one left20:29
lfaraone_lfaraone20:30
alansaul-laptop joined20:30
Goplat joined20:30
raniere joined20:30
diegoviola joined20:31
krizzii left20:31
LucasKA joined20:31
craigp joined20:32
Watabou left20:32
macben left20:32
aChatir joined20:33
craigp left20:34
craigp joined20:34
jatt left20:36
raniere left20:36
xSmurf left20:36
kcj left20:37
psyl0n left20:37
phipes left20:39
liri_ joined20:40
Nicholas_Rishel left20:40
petey joined20:44
ewnd9 left20:45
King_Hual_ left20:46
aChatir left20:46
raniere joined20:49
Happzz left20:49
LulzonAwayLulzon20:50
dan64 left20:51
psyl0n joined20:52
LucasKA left20:53
mizu_no_oto left20:53
dyng joined20:55
dan64 joined20:57
longbeach left20:57
Exancillatus joined20:58
PeterBooker left20:59
Mars joined20:59
MarsGuest2687621:00
framling left21:00
LucasKA joined21:00
dyng left21:00
eletuchy left21:01
oriba_ left21:01
eletuchy joined21:01
Guest26876 left21:02
King_Hual left21:03
cyphase left21:04
albertgrala joined21:06
dprophit left21:06
a-l-e left21:07
VictorCL joined21:07
King_Hual joined21:07
endiruna joined21:08
jnavila left21:08
corni left21:09
acharlieh left21:09
hellopat left21:10
hellopat joined21:10
primitive left21:11
swaechter_ joined21:11
phipes joined21:11
tummy__ left21:13
barbles joined21:13
hellopat left21:15
jceb left21:17
yhager joined21:18
King_Hual left21:18
dexterity joined21:19
King_Hual joined21:19
vince_pr_ joined21:19
Nizumzen joined21:19
vince_prignano left21:20
c-vit joined21:20
dexterity How do I revert a branch to a specific tag? (I revert commit(s) as the repo has been pushed)21:21
Arun_ joined21:21
_tpavel left21:21
cbreak dexterity: you can use git revert A..HEAD21:22
Watabou joined21:22
offby1 dexterity: or, depending what you meant by "revert", "git reset --hard A"21:22
cbreak or git revert -n A..HEAD && git commit -m "blah blah blah"21:22
aweorit` left21:23
codehotter left21:23
Nicholas_Rishel joined21:24
codehotter joined21:25
dexterity cbreak: what do you mean by A? is it a commit or a tag?21:26
cbreak dexterity: it's the commit you wish you would be on21:26
saorge_ joined21:26
c-vit left21:27
xlinkz0_ left21:28
cagedwisdom joined21:29
dexterity cbreak: does `git revert <tagname>` produce the same result as `git revert <tagged commit>..HEAD`?21:29
cbreak no21:30
git revert T reverts the commit T21:30
saorge left21:30
cbreak git revert T.. reverts all commits from T (not including T) to HEAD21:30
dexterity: see man gitrevision21:30
dexterity: see man gitrevisions21:31
gitinfo dexterity: the gitrevisions manpage is available at http://jk.gs/gitrevisions.html21:31
XxLocutusxX joined21:31
m0viefreak is there a straight-forward solution to this in case T is not an ancester of HEAD?21:31
i could only thing of something like git diff T | git apply --reverse21:32
[emmajane]emmajane21:32
afhammad joined21:32
thiago dexterity: let's start with what you mean by "revert"21:32
dexterity: explain21:33
afhammad left21:33
ariscop joined21:33
mribeirodantas left21:34
Bosox20051 joined21:34
acl_ joined21:35
fesoj left21:35
petertretyakov joined21:35
ValicekB left21:38
Kicer86 left21:38
cyphase joined21:38
LucasKA left21:40
MattMaker joined21:41
rawtaz silly question perhaps, but does it make more sense to tag versions with just 1.0 and 1.0.3 instead of 1.0.0 and 1.0.3 (i.e. ditching the last digit when it's a new "major" version)?21:42
CKyle joined21:42
aard_ joined21:42
Happzz joined21:42
rudi_s rawtaz: Keeping all three digits makes it easier to sort.21:43
grawity only if your sorting algorithm is odd21:43
yhager left21:43
grawity I usually see "1.0" sorted above "1.0<anything>"21:44
XxLocutusxX left21:44
rawtaz well those comments seem to make sense :)21:44
MacGyver rawtaz: I prefer if the numbering of all versions includes all points.21:44
rawtaz: Because otherwise confusion at the end user can ensue, e.g. "does 1.0 refer to 1.0.0 or the latest 1.0.x"21:45
hillct left21:45
rawtaz on a similar note, do you name stuff v1.0.0 or just 1.0.0 ? i think it's kinda more obvious when seeing a tag or release branch named v1.0.0 than just 1.0.021:45
MacGyver: thats another good point indeed. thanks21:45
tobias__ left21:47
Nizumzen left21:48
bwreilly joined21:49
zapb left21:49
yhager joined21:49
matanya left21:50
aard_ left21:51
redrocket joined21:51
matheus23 left21:54
LucasKA joined21:54
bremner I tend to think the v is redundant in a tag, but otherwise sane seeming people disagree21:55
simesy joined21:56
CKyle left21:56
cbreak I use v for versions and r for revisions21:56
dyng joined21:56
cbreak that way I keep them separated from other tags21:56
bremner what's a revision?21:57
beastd bremner: depends on your preferences i guess. the leading v in the tag can certainly serve as a namespace for releases and release candidates21:57
ngladitz I've got a commit followed by two reverts that cancel each other out ... is there anyway to rebase those three commits into one?21:57
cbreak bremner: a counter-like version number... like a release number maybe?21:58
ngladitz: squash21:59
ngladitz: rebase -i can also delete commits21:59
both are rewriting history as usual with rebase21:59
rawtaz cbreak: do you mean that you have for example v1.0.0 when theres a release, but revisions/bug fixes you name e.g. r1.0.1 ?21:59
Mars joined21:59
cbreak nah21:59
jcalonso joined21:59
ngladitz I tried git rebase -i HEAD~3 and used pick, fixup, fixup but then it tells me "You asked to amend the most recent commit, but doing so would make it empty."21:59
dexterity left21:59
cbreak in most projects I work on I don't bother with version numbers21:59
there's just r0, r1, ... r10, r1121:59
MarsGuest6397821:59
diegoviola left22:00
cbreak because I don't have to maintain old releases.22:00
new == better :)22:00
JerryT joined22:00
macben joined22:00
VictorCL left22:00
DrNick left22:01
rawtaz cbreak: i see, just release numbers then22:01
ngladitz I tried deleting the revert commit before but then the merge from my staged topic branch into the integration branch fails ... it tells me my branch is already there :\22:01
p4denis joined22:01
dyng left22:01
mklappst_ joined22:03
royho joined22:03
macben left22:05
mklappstuhl left22:05
dougsland left22:05
dougsland joined22:05
tpollard joined22:06
p4denis left22:06
Vinnie_win joined22:06
royho left22:06
LucasKA left22:06
Guest63978 left22:07
hellopat joined22:07
jcalonso left22:08
jackneill left22:09
thiago ngladitz: why do you think merge is wrong?22:09
gordian joined22:10
mklappst_ left22:10
hellopat left22:10
mklappstuhl joined22:10
ngladitz thiago: hm?22:10
you mean why it refuses to merge?22:10
phipes left22:10
thiago ngladitz: assume git is right22:10
ngladitz: and then just look into why you thought it was wrong.22:11
ValicekB joined22:11
LuxuryMo_ left22:11
acl_ left22:11
ngladitz thiago: I don't doubt git is right ... I don't think it is wrong22:11
doener left22:11
juls joined22:12
ngladitz but that doesn't help me :\22:12
hoschi left22:13
de-Vri-es left22:13
master_j left22:13
thiago ngladitz: then explain the problem22:14
King_Hual left22:14
ngladitz thiago: didn't I?22:14
King_Hual joined22:14
thiago ngladitz: not enough22:14
ngladitz: please re-explain22:14
what command did you run?22:15
David joined22:15
ngladitz thiago: ok I'll try to reiterate in more detail ... I prepared a topic for integration that I pushed and merged22:15
I had a semantic conflict with another topic so I reverted my topic, pushed and merged again22:16
then the topic I conflicted with was reverted so I reverted my earlier revert, pushed and merged again22:16
thiago what's "pushed and merged" ?22:16
and what do you mean by "reverted my topic" ?22:17
I need git commands22:17
ngladitz "git push stage HEAD" for the push22:17
thiago ok22:17
that's a push22:17
then what?22:17
ngladitz the merge is performed by some remote ssh command (I am not entirely sure how it works :\)22:18
bvi left22:18
ngladitz it takes the name of the topic that I pushed to stage and merges it into the integration branch22:18
KeiKun joined22:18
jayallen_ joined22:18
jayallen left22:18
jayallen_jayallen22:18
DrNick joined22:18
ngladitz so far all went like expected22:19
now usually when I merged multiple commits I rebase to clean up history, then I force push and merge again22:19
gdogrady joined22:19
thiago rebase on top of what?22:20
before that push?22:20
ngladitz when my topic has e.g. 3 commits in it I run "git rebase HEAD~3" and use fixup for the last two22:20
swaechter_ left22:21
KeiKun_ left22:21
thiago ok22:21
did you do that before the push?22:21
ngladitz I first push all commits, then rebase, then force push22:21
thiago ok, that's mistake 122:21
gdogrady left22:22
gdogrady joined22:22
ngladitz can you elaborate?22:22
thiago force push was a mistake22:22
what did the CI on the other side do when you force-pushed?22:22
looper left22:23
ngladitz nothing yet ... it works on the integration branch after I merge22:23
CI (continuous integration I hope?)22:23
Vivekananda joined22:24
nurey left22:24
thiago ah, ok22:24
ngladitz so far all of this usually works22:24
thiago so you detected the mistake before anything used the first push?22:24
mishok13 left22:25
ngladitz no it was already merged into the integration branch22:25
VictorCL joined22:25
psyl0n left22:25
thiago ok22:25
toiletbowlJoel left22:25
thiago what did you do after the force push?22:25
I'm assuming that unless you do something, it doesn't get used22:26
so what did you do?22:26
ngladitz I tried to merge my topic into the integration branch22:26
johnmilton left22:26
thiago that's the mistake22:26
don't do it22:26
ngladitz that usually works :\22:26
jayallen_ joined22:26
thiago don't do it22:26
jayallen left22:26
jayallen_jayallen22:26
ngladitz can you elaborate?22:27
thiago get the commits right the first time. Once they've been merged into something, they're there for good.22:27
NEVER rebase them again22:27
ngladitz hm that is the given workflow22:27
thiago time to change it22:27
cbreak if you rebase public history, you create new history to which the old version still exists22:27
so afterwards you have two versions of history22:28
rpg left22:28
rendar left22:28
cbreak you can kill the old public history22:28
but you have to do that in every single clone22:28
good luck with that :)22:28
ngladitz nothing is based on the history of the integration branch22:28
cbreak is the branch useful?22:28
if not, throw it away22:28
iderik joined22:28
thiago ngladitz: are you saying that the result of the first merge is thrown away?22:28
ValicekB left22:28
ngladitz for automated testing only22:28
I assume it isn't thrown away22:29
Cyb3r-Assassin left22:29
cbreak either you throw it away or you keep it22:29
thiago ngladitz: then don't merge the force push22:29
cbreak if you keep it, you have two versions of history22:29
thiago ngladitz: you have two choices:22:29
throw the first merge away before merging the rebase; or not rebase22:30
ngladitz: choose one22:30
eijk joined22:30
Diemuzi joined22:30
ngladitz hm but that isn't even the part that broke for me yet22:30
gitinfo set mode: +v22:30
thiago ngladitz: anything past this point is busted alerady22:31
ngladitz: I don't even care what you did afterwards, if it's after the first mistake22:31
ngladitz: anyway, from now on, you'll change your workflow22:31
ngladitz there is a "master" branch on the remote that contains the final history22:31
macben joined22:31
ngladitz the topics get merged into it when they pass integration22:31
thiago fair enough22:32
but you told us that the result of the first merge is not thrown away22:32
if that's the case, DO NOT rebase22:32
ngladitz wouldn't that only break if someone branched from the integration branch?22:33
kcj joined22:33
thiago yes22:33
which is what you do if you merge more things into it22:33
sohail joined22:33
thiago so I am telling you: don't22:33
endiruna left22:33
ngladitz I still don't know how the remote script is doing the merge22:34
thiago I am assuming you know what you're talking about22:34
you said you did the first push, then caused your commits to be merged and tested22:35
Silmarilion joined22:35
mvelioglu left22:35
thiago then you rebased, pushed again and asked the script to merge that now22:35
endiruna joined22:35
thiago you also said the original commit was not removed22:35
THAT is the mistake22:35
ngladitz yes ... but I don't know if it keeps the initial merge when I merge the topic again22:35
thiago you need to change your workflow:22:35
either make the script throw away the commit, or stop rebasing22:35
which way will you choose?22:36
ngladitz it isn't my script (nor my workflow) :)22:36
thiago for our purposes here, it is22:36
you're using it, therefore it's yours22:36
ValicekB joined22:36
jatt joined22:36
macben left22:36
ngladitz I can't inspect what it does or modify it though :p22:36
phipes joined22:36
thiago you can take conclusions from the results or you can ask the person who wrote it22:37
alezost left22:37
ngladitz so far it is working so I just assume it is doing the right thing22:38
thiago let's proceed on the assumption that the person who wrote the script thought it through: the failed tests are discarded22:38
ngladitz like I said as far as I can tell so far none of that broke anything22:38
thiago so you received the results, saw there was a problem, so you made a new set of commits22:38
then you force-pushed them22:38
ok so far?22:38
ngladitz not exactly22:38
I saw the conflict and just reverted my last commit, then pushed and merged22:39
(so far no force or rebase)22:39
WaReZ left22:39
ngladitz then the conflicting topic was reverted by someone else22:39
thiago if we assume that the script is doing the right thing, only the last push is relevant22:39
so let's skip to the last push22:39
what did you do after the last push?22:39
ngladitz so I reverted my original revert, pushed and merged again22:40
mklappst_ joined22:40
mklappstuhl left22:40
thiago with git revert?22:40
ngladitz yes22:40
thiago ok22:40
what happened then?22:40
ngladitz now to clean up my history (like usually) I ran "git rebase HEAD~3" and set the two reverts to "fixup"22:40
thiago ok22:40
ngladitz and that failed22:41
thiago the rebase failed?22:41
ngladitz yes22:41
thiago pastebin the output22:41
tuocuggino joined22:41
Mars joined22:42
MarsGuest1307422:42
ngladitz http://pastebin.com/yRUaFuuN22:42
axl_ joined22:42
Guest13074 left22:42
thiago ngladitz: which commit is "Revert "AddDependencies: new policy requires dependencies to exist"" ?22:43
the first of the reverts?22:43
ngladitz yes22:43
thiago instead of fixup'ing the two reverts, just remove them22:43
Cyb3r-Assassin joined22:44
tuocuggino hi guys someone know what means this error after a git commit: "error unable to create temporary file file exists error error building trees"22:44
?22:44
calcifea_ left22:44
ngladitz that I tried as well but then the merge on the remote fails telling me the topic is already in the integration branch22:45
thiago tuocuggino: pastebin the terminal, including the command you ran22:45
ngladitz: force-push?22:45
acharlieh joined22:45
mizu_no_oto joined22:45
ngladitz I force pushed (worked) but when I invoke the remote ssh merge it doesn't work22:46
thundar97 joined22:46
thundar97 125 voiced what???22:46
tuocuggino thiago, the problem is not on my pc, but on pc of my coworker... and he there isn't here now, i know only the error22:46
thiago ngladitz: what command did not work?22:46
thundar97 anyway, is it possible to pull request for a whole NEW branch on github?22:47
thiago tuocuggino: ok.22:47
khmarbaise left22:47
thiago tuocuggino: come back when you have the information22:47
thundar97: ask in #github22:47
thundar97: but merges apply to the entire branch22:47
tuocuggino thiago, ok, what kind of information u need?22:47
ngladitz thiago: the remote ssh command that performs the merge22:47
thundar97 yeah thats what i though22:48
thiago thundar97: just make sure that the other person knows to do a git merge22:48
tuocuggino: I've already told you22:48
tuocuggino: 14:45 < thiago> tuocuggino: pastebin the terminal, including the command you ran22:48
ngladitz (from my staged topic branch into the integration branch)22:48
tuocuggino the complete output?22:48
thiago ngladitz: what git command was run?22:48
tuocuggino: I need the command that was run and the exact output from git.22:49
tuocuggino ok22:49
VictorCL left22:49
ngladitz thiago: if only I knew for sure ... the parameters that look like they belong to git at the end look like this: merge -b integration-branch my-topic22:49
thiago ngladitz: if that merge said "already up to date", it implies that my-topic was already merged22:49
ngladitz but I don't know what the script actually executes :\22:49
EvilDMP left22:50
thiago ngladitz: job done then22:50
ngladitz I think the error might be custom since I haven't been able to google it anywhere22:50
jonascj left22:50
thiago ngladitz: that means something merged that commit to the base of what the integration script uses22:51
ngladitz: my guess is that the script automatically does that if the tests pass, which they did when you pushed the commit + revert + reverting the revert22:52
ngladitz I'll try finding out upstream about the error ... I guess it might not even be git related ... assuming I didn't do anything obviously wrong in the steps in between :)22:52
thiago ngladitz: you cannot fix the revert and revert revert anymore.22:52
ngladitz thanks for all your help22:52
thiago ngladitz: so the recommendation is: make sure your commits are right before you ask the integration script to run22:52
Arun_ left22:53
rawtaz since annotated tags are stored as objects (if i understand it correctly), does that mean that you cannot edit or remove them later on without the rest of the history (following that tag's point/commit) is affected somehow?22:53
ingentis left22:53
thiago rawtaz: yes and no22:53
rawtaz or are they not part of the regular chain so to speak22:53
ngladitz usually I only know if the commits are "right" after the integration tests ran :)22:53
thiago rawtaz: you cannot edit or move a tag. Everyone will notice.22:53
rawtaz: but the tag is not part of the commit history. If you remove a tag, the commit history remains intact.22:54
falconfox left22:54
rawtaz thiago: i think thats what i was after, that it doesnt affect the commit history (i.e. the hashes etc)22:54
WaReZ joined22:54
Arun_ joined22:55
thiago rawtaz: right22:55
rawtaz thank you. i did try it and didnt see any change but wasnt sure22:55
pantsman left22:55
Diemuzi left22:55
mklappstuhl joined22:55
falconfox joined22:56
xequence left22:57
EngierkO joined22:57
mklappst_ left22:57
dyng joined22:58
petertretyakov left22:58
tuocuggino thiago, he has just se me an email with the error22:58
http://pastebin.com/9HRz8gXb22:58
Nicholas_Rishel left22:58
thiago tuocuggino: that's not Linux, is it?22:59
rafaqueque joined22:59
xSmurf joined22:59
frogonwheels joined22:59
tuocuggino yes he is using windows22:59
thiago tuocuggino: then I can't help you further23:00
jayallen left23:00
thiago try upgrading to the latest Git, to be sure, but this is as far as I can go23:00
jayallen_ joined23:00
tuocuggino already done but dosen't work23:00
floatingpoint joined23:01
floatingpoint ugh. what the f is this? error: object file .git/objects/28/33769eec39a2312125808b0fe5e1282dc5ff17 is empty23:01
AndChat92225 joined23:02
dyng left23:02
yhager left23:02
eijk left23:02
LucasKA joined23:03
floatingpoint can I just blow that file away?23:03
alansaul-laptop left23:05
dik_dak joined23:06
alansaul-laptop joined23:06
SeptDePique joined23:07
MetaCosm left23:07
AndChat92225 left23:07
grawity well, it's empty anyway, so sure23:07
AndChat92225 joined23:07
grawity but I'm guessing `git fsck` will complain about the repository missing some stuff23:08
MetaCosm joined23:08
offby1 floatingpoint: you could try putting something in it :-)23:08
ngladitz left23:08
offby1 that was NOT a serious suggestion.23:08
leeN left23:08
LucasKA left23:09
AndChat92225 left23:10
weld_kodia joined23:11
weld_kodia left23:11
petey left23:11
petey joined23:12
Mangellan2497 left23:12
weld_kodia joined23:12
weld_kodia left23:12
ciampix left23:12
tuocuggino left23:13
jatt left23:13
weld_kodia joined23:13
rawtaz heh. what is the "index on ..." commit about? im not sure what created it. could it have been the stashing?23:13
in http://pastebin.mozilla.org/3998862 , that is23:13
dsdeiz joined23:14
weld_kodia left23:14
D4v33 joined23:14
jexmex joined23:14
grawity that's part of the stash, yes23:14
jexmex can anybody recommend a really good book to help me understand the more advance parts of git?23:14
rawtaz im trying to interpret the diffs23:14
jexmex somehow I end up getting double merges and crap23:15
mizu_no_oto left23:15
LuxuryMode joined23:15
rawtaz ok to me it seems that 555dafa is what was staged in the index, and cc4a84f contains some (presumably unstaged) working copy changes23:15
petey left23:16
godgodgodgo left23:17
offby1 jexmex: the only good book I know of is the stadard one23:17
weld_kodia joined23:17
jexmex offby1: you mean the gitbook?23:18
ciampix joined23:18
jexmex http://git-scm.com/book23:18
beastd left23:19
offby1 yep23:19
jexmex ok will go through that again23:19
enr left23:20
gitinfo set mode: +v23:21
veebers left23:21
offby1 it's perhaps not _that_ advanced, but if you know everything in that book, you should have no trouble reading the man pages23:22
veebers joined23:22
SeptDePique left23:23
SeptDePique joined23:23
ValicekB left23:23
Cyb3r-Assassin left23:25
ErKa joined23:25
weld_kodia There are also introductory videos on git-scm.com23:26
LuxuryMode left23:26
madewokherd left23:26
D4v33 this may be a dumb question, but I'm a newb. is it possible to check in one file that's among a number of staged files or do all have to be checked in?23:27
osse D4v33: git add that/one/file; git commit23:27
offby1 well, there are others staged.23:28
osse oh23:28
offby1 D4v33: technically, no23:28
but it's easy to work around23:28
"git stash"23:28
then stage the one file and commit it23:28
then git stash pop23:28
or ...23:28
just unstage all the other files.23:28
that's conceptually simpler.23:28
osse git commit that/one/file.txt23:28
offby1 or ...23:28
osse that ignores the index23:28
offby1 oh!23:28
offby1 slaps forehead23:29
osse joins in23:29
offby1 that must be relatively new -- i.e., introduced in the last five years :-)23:29
ow.23:29
jayallen joined23:29
osse ow incidentally matches my initials.23:29
jayallen_ left23:29
offby1 coincidence? You be the judge23:29
Silmarilion left23:29
offby1 my intials are "slaps osse upside the haid".23:30
true story.23:30
ZujkisNx joined23:30
D4v33 thanks I look into stashing, so much flexibility!23:30
offby1 D4v33: as a wise man once said: git stash is cool.23:30
ValicekB joined23:31
phipes left23:31
mklappstuhl left23:32
weld_kodia left23:32
osse offby1: it's been in at least since Aug 8 200523:32
weld_kodia joined23:33
gnu-man left23:33
Cyb3r-Assassin joined23:33
offby1 funny, I _never_ think to do that.23:34
'Course 98% of my interaction with git these days is through a nice front-end23:34
uu1101 left23:35
Mars joined23:35
vince_pr_ left23:36
mizu_no_oto joined23:36
MarsGuest4277523:36
Mangellan2497 joined23:36
osse It's started to become a habit of mine if I've changed only one file. 'git commit <tab>' is one character shorter than 'git commit -a' :p23:37
ciampix_ joined23:37
offby1 heh23:37
ciampix left23:38
MindfulMonk left23:38
grawity well, `git ci -a` is shorter than both23:38
osse grawity: I usually use 'g ci <tab>' :p23:38
KeiKun left23:38
rawtaz crap. i think i just pruned some stuff i wanted to cherry pick :>23:40
w0ng left23:40
rawtaz but i have them in a completely separate/diverged place, so i guess i can grab it from there23:40
osse heh, prune and cherry.23:40
uu1101 joined23:40
w0ng joined23:40
mizu_no_oto left23:41
TehRandom joined23:41
TehRandom left23:41
D4v33 left23:42
dobalina left23:42
FerreusR left23:43
offby1 raisin and pear!23:43
gordian left23:43
offby1 in math class I learned about logs, roots, "branch cuts", and leaves. Nothing about sticks or stems that I can recall though.23:44
LuxuryMode joined23:45
albertgrala left23:45
pgokeeffe joined23:46
phipes joined23:46
elbeardmorez left23:46
ggonzalez joined23:46
ggonzalez hi23:46
gitinfo ggonzalez: hi! I'd like to automatically welcome you to #git, a place full of helpful gits. Got a question? Just ask it — chances are someone will answer fairly soon. The topic has links with more information about git and this channel. NB. it can't hurt to do a backup (type !backup for help) before trying things out, especially if they involve dangerous keywords such as --hard, clean, --force/-f, rm and so on.23:46
ggonzalez thanks gitinfo, really helpful23:47
gitinfo ggonzalez: you're welcome, but please note that I'm a bot. I'm not programmed to care.23:47
uu1101 left23:47
acharlieh left23:47
alansaul-laptop left23:48
ggonzalez Once in a while a create a branch from master for a separate version but after a while this new branch became the main project source code, making master outdated. Which is the best way to make this branch go to master again? rebase? merge?23:48
offby1 a fairly clever one, however23:48
ggonzalez: I'd check out master, then merge in that other branch.23:49
That way you generally have your master branch being current.23:49
Note that this isn't always important; if you're the only user of the repository, then it doesn't much matter which branch has the new hotness in it.23:49
ZujkisNx left23:49
offby1 Even if other people are using it, you _could_ just tell them "hey, forget about master; all the cool stuff is in the 'frotz' branch".23:49
But ... it's more conventional to keep master up-to-date, so that's probably what you want to do.23:50
ggonzalez offby, yeah I wouldn't mind keep using the branch but I used github for issue tracking and I can't close the issues directly from the branch, which is a bit of a pia23:50
s/used/use/23:50
uu1101 joined23:50
Happzz left23:50
weld_kodia left23:50
ggonzalez this is basically the main reason from moving everything back to master23:51
weld_kodia joined23:51
weld_kodia left23:51
enr joined23:51
ggonzalez offby, so merge, ok thx. Why not rebase in this case?23:51
petey joined23:52
offby1 rebase is fine too. The choice is mostly about style (although people here will probably flame me for saying that)23:52
there are pros and cons to each.23:52
ggonzalez heheh23:53
offby1 actually, you really don't want to rebase master if other people are tracking it.23:53
osse hmm, how about a dose of reset blow that old master branch to kingdom come?23:53
offby1 that's got the same downside as rebasing.23:53
cordoval joined23:53
cordoval guyz23:53
offby1 but otherwise that's not necessarily a bad idea.23:53
d00dz23:53
osse srsly23:54
cordoval which is a perfect way to squash all commits into one without interaction?23:54
thiago cordoval: are they in the current branch?23:54
cordoval well yes23:54
ggonzalez ok thx pals :)23:54
cordoval i mean i have say feature/x23:54
and master23:54
thiago cordoval: git reset --soft last-commit-not-to-be-squashed && git commit -m "squash"23:55
cordoval and i want to squash 20 commits on feature/x on top of master23:55
osse cordoval: merge --squash feature/x23:55
floatingpoint left23:55
ggonzalez left23:55
cordoval the merge will merge into a branch, that is not what i want23:55
i am sending a PR23:55
so merge --squash is not an option right?23:55
thiago press release?23:55
offby1 for super-atomic squash, I occasionally use "git commit-tree".23:55
osse cordoval: no it won't. it will squash it on top23:55
thiago merge --squash is an option23:55
hellopat joined23:56
osse it will take the whole of feature/x and bolt it onto master like a pair of fake tits23:56
cordoval hmm will it keep author info?23:56
enr left23:56
cordoval i don't want it to merge on master yet23:56
thiago cordoval: no. You get the credit now.23:56
cordoval i want to just do it on the same branch23:56
thiago cordoval: do what I suggested then.23:56
cordoval git reset --soft ..23:56
osse cordoval: about git merge --squash: "This allows you to create a single commit on top of the current branch whose effect is the same as merging another branch"23:57
cordoval ok i will test it23:57
m0viefreak left23:57
m0viefreak joined23:57
cordoval i mean merge --squash23:57
as osse confused me23:57
osse cordoval: ahh. but if you want to squash without actually merging then you cannot use it23:58
cordoval ok then reset23:58
ok i have it clear that it has to be reset23:58
osse git reset --soft master && git commit should do the tricknicity23:58
hellopat left23:58
cordoval yeah now i just have to calculate the `master`23:59
because it is a PR with a specific base23:59

Logs Search ←Prev date Next date→ Channels Documentation