IRCloggy #git 2009-02-02

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.

2009-02-02

jrmuizel joined00:00
Sigma left00:00
Flathead joined00:01
ben_h joined00:02
seangrove joined00:03
moon_unit joined00:03
moon_unit is there a way to check out a single file of a repository?00:04
caoliver joined00:04
moon_unit and00:04
set it up as a submodule00:04
offby1 doubt it.00:05
kevlarman currently, no00:05
you can only clone the whole thing00:05
offby1 submodle == commit, more or less00:05
s/submodle/submodule/00:05
plasticine joined00:08
shd moon_unit: a limited form of cloning can speed up the process, see shallow clone00:08
jmspeex joined00:09
moon_unit so i'm basically just trying to share a bunch of config files between projects00:09
caoliver left00:10
moon_unit they're all in different directories in my projects00:10
is there any way to do that without setting up one repository per file?00:10
like say, config/s3.yml = shared_repo/s3.yml, lib/rake = shared_repo/rake, etc00:12
what's the cleanest solution00:13
sshc I have about 90 useless whitespace commits just to test server-side hooks. how do I erase those 90 commites from history?00:13
Pieter rebase -i00:13
or filter-branch00:13
or, if they're the top commits, reset --hard00:14
PYP00:14
plasticine left00:16
icwiener left00:16
iskaldur left00:18
zaius joined00:21
lisyzavu joined00:21
plasticine joined00:23
_Vi left00:24
dulia joined00:27
carllerche joined00:27
name joined00:28
gwoo left00:30
fynn joined00:31
fynn What does the following error message mean:00:31
warning: 2 lines add whitespace errors.00:32
dsop fynn: that you have e.g. 2 times trailing whitespaces00:32
EmilMedve1 joined00:33
doener if you know which commit that was, you can use "git diff --check $commit^!" to see where the errors are00:34
jayne why is trailing whitespace at the end of a line bad?00:34
doener because it's useless and people might have setup their editor to automatically strip it00:34
leading to a lot of noise and totally useless conflicts00:35
you can configure which whitespace errors git complains about00:35
jayne why would anyone want their editor to make unsolicited changes to a file?00:35
reprore_ joined00:35
fynn dsop, doener: thanks.00:35
dsop jayne: because they are smart enough to know that whitespaces can cause unecessary trouble00:36
EmilMedve left00:36
jayne hm. This seems to me like a case of the solution being its own problem00:36
pinholecamera joined00:36
doener jayne: even if it's not automatic, it can still cause problems. I might edit a line, and later change it back, not forget to add the useless whitespace00:37
fynn left00:37
pinholecamera hey folks, i'm trying to build git on debian etch from source, brand new debian install... for some reason after i do ./configure (which appears successful), there is no make command, just says it's not found... any ideas why that might be?00:37
Whtiger it says make isn't found?00:37
jayne that doesn't seem like a problem that would be restricted to end-of-line whitespace. What about mid-line whitespace?00:37
plasticine__ joined00:38
pinholecamera Whtiger: yeah, it's really weird!00:38
jayne "if(" vs "if (", (x+y)/2 vs (x + y) / 2, etc.00:38
dsop jayne: go and fix your coding styles00:38
doener jayne: or two devs change code that is nearby, one replaces a line with "\t" with two empty lines (two separate his new code block from the surrounding code), the other keeps the \t00:38
pinholecamera Whtiger: says command not found, it's wild... never encountered that on a successful ./configure before00:39
doener jayne: that's coding style, and one way to do it should be enforced anyway. It's not useless but gives consistency to the code00:39
pinholecamera i've got the output in a pastebin here: http://pastebin.com/m3d50cdd2 ... looks a-okay to me00:40
doener pinholecamera: configure doesn't check for make IIRC, do you have make installed?00:41
pinholecamera doener, it's a default debian etch install, it should be installed by default, or at least was in past experiences for me00:42
but let me check00:42
eddyp left00:42
pinholecamera hrmm, not seeing it so far, do you know the name of the package off the top of your head?00:44
plasticine__ left00:44
doener make00:44
pinholecamera ahh thought there was more to it. damn, not installed, that'd do it, haha.00:45
weird that it's not installed on this machine, never run into that before00:45
thanks doener00:47
firstdate joined00:48
jmspeex left00:48
jmspeex joined00:49
Dodji joined00:49
fynn joined00:49
plasticine__ joined00:50
plasticine left00:51
wagle joined00:51
fynn doener: btw, is there a way to find the offensive commit if I don't know which it is?00:51
firstdate left00:51
firstdate joined00:53
radarek left00:55
doener fynn: I guess you could loop over a commit range and do the diff --check for each commi00:57
t00:57
torarne left00:58
fynn doener: looping in something like a bash script, I assume?00:58
EmilMedve1EmilMedve00:58
plasticine__ left00:59
doener yeah, for commit in $(git rev-list ....); do echo $commit; git diff --check $commit^! ; done00:59
or whatever00:59
neunon left00:59
doener adding some checks to handle merge commits in a better way would be good I guess01:00
troter joined01:01
Whtiger HI01:01
er01:01
Irssi should tell me if I'm in the wrong channel01:02
jayne normally it does tell you your channel in the status line01:02
plasticine joined01:02
fynn doener: cool, thanks.01:05
sgrimm left01:06
sgrimm joined01:06
carllerche left01:07
carllerche joined01:09
plasticine left01:11
Niamor left01:12
name left01:12
Niamor joined01:13
carllerche left01:14
fynn left01:14
plasticine joined01:15
sshc left01:20
firstdate left01:20
bobesponja left01:23
plasticine left01:24
plasticine joined01:26
seangrove left01:30
seangrove joined01:31
nothingHappens joined01:31
plasticine left01:32
nothingHappens left01:32
therrg joined01:32
travisjeffery left01:33
gretch joined01:33
Ariens left01:36
seangrove left01:37
seangrove joined01:37
seangrove left01:37
aziz left01:41
plasticine joined01:41
parasti left01:43
Niamor left01:43
Niamor joined01:44
mithro joined01:46
parasti joined01:46
plasticine left01:47
nick_h[litage] joined01:53
plasticine joined01:54
qrush_ joined01:56
jchris joined01:59
plasticine left02:00
kelvie joined02:02
krh left02:04
cgardner left02:09
nick_h[litage] left02:09
nick_h[litage] joined02:10
reprore_ left02:11
matt dumb question02:11
so i created a branch, changed the file02:11
plasticine joined02:11
matt i want to merge the branch back into master and commit to master (its already commited on the branch)02:12
Flathead left02:12
matt how?02:12
qrush_ git checkout master02:12
git merge otherbranch02:12
deskin matt: git checkout master && git merge thebranch02:12
matt ah02:13
ok thanks guys02:13
johnw left02:14
matt do i need to recommmit after a merge?02:14
kevlarman no02:14
deskin only if you have to manually resolve merge conflicts02:14
matt nope. ok great thanks :)02:15
j416 joined02:16
qrush_ matt: just check git log, you'll see the commit you merged02:18
foca left02:19
jerbear left02:21
nick_h[litage] left02:22
nick_h[litage] joined02:22
fynn joined02:24
plasticine left02:27
plasticine joined02:28
dulia left02:28
parasti left02:28
GeertB left02:34
caseym joined02:35
GeertB joined02:35
kukks left02:35
j416 Does anyone have a neat way of storing branch descriptions? This has been discussed on the mailing list, but quite some time ago it seems. Keeping it in-branch kind of hinders merging (branch descriptions would fly all over the place)02:36
ndim left02:37
ndim joined02:37
plasticine left02:38
toxx_ left02:40
plasticine joined02:40
mark[oz]_ joined02:43
mark[oz]_ left02:47
Niamor left02:48
Niamor joined02:49
mark[oz]_ joined02:50
plasticine left02:52
scientes joined02:54
plasticine joined02:54
fynn OK, I have a weird situation here:02:54
"modified: foo/bar/baz"02:55
bondjuan joined02:55
fynn in `git status`. However, foo/bar/baz is a directory.02:55
Also, doing `git checkout foo/bar/baz` returns no feedback, but also doesn't change anything.02:55
bondjuan Hey guys, I'm kinda confused on how I can checkout a remote branch and pull it down to create a local branch on my computer?02:55
fynn What's up, and how do I fix it?02:55
bondjuan Is it considered a "tracking" branch?02:56
iskaldur joined02:56
paulboone left02:57
iskaldur how good is the git eclipse plugin?02:57
mark[oz] left03:00
caseym left03:01
Ilari fynn: foo/bar/baz is submodule?03:02
bondjuan: Create local branch starting from apporiate remote tracking branch and the check that branch. There is shortcut for that: 'git checkout -b <newbranchname> <trackingbranch>'.03:03
fynn Ilari: possibly... I'm not even sure how to check that.03:05
bondjuan Ilari: thank you :)03:06
patmaddox joined03:09
bryanl joined03:09
iskaldur left03:09
plasticine left03:09
plasticine joined03:11
Bass10 left03:12
mark[oz]_ left03:13
mark[oz] joined03:14
plasticine left03:20
cytrinox joined03:20
schierbeck left03:23
martinpaul_ joined03:23
Flathead joined03:23
gouki git config --global user.name is user-based, right? I mean, if user A does it, it won't overwrite for user B on the same machine.03:24
Ilari fynn: 'foo/bar/baz/.git' exists?03:24
gouki: Correct (system-global would be --system).03:24
deskin gouki: you're correct; --global modifies ~/.gitconfig03:24
gouki deskin and Ilari thank you very much.03:25
Ilari gouki: And for obivious reasons, --system likely requires root...03:25
gouki: For setting options, that is.03:25
fynn Ilari: yes it does!03:25
cytrinox_ left03:25
Ilari fynn: Then foo/bar/baz is a submodule.03:26
fynn: You can use 'git add' to stage submodule changes as usual...03:26
wagle left03:26
plasticine joined03:27
fynn Ilari: what I actually want is to revert all changes.03:29
ben_h_ joined03:32
akitada_ joined03:32
ben_h left03:33
ben_h_ben_h03:33
ben_hben_h_underscore03:33
plasticine left03:35
ben_h_underscore left03:36
ben_h joined03:36
flaguy48 left03:36
markelikalderon left03:37
mark[oz]_ joined03:38
mark[oz]__ joined03:38
girishr joined03:39
mark[oz] left03:39
mark[oz]___ joined03:39
plasticine joined03:40
martinpaul left03:40
ben_h_ joined03:42
ben_h_ left03:42
ben_h left03:42
ben_h joined03:43
ankit9 left03:45
plasticine left03:48
nick_h[litage] left03:50
mark[oz]_ left03:55
plasticine joined03:57
perezd88 joined04:00
jackdempsey joined04:01
dulia joined04:04
thumper left04:05
thumper joined04:06
jackdempsey left04:06
spearce joined04:06
ankit9 joined04:06
mark[oz]__ left04:06
akitada_ left04:07
alezandro left04:08
thom__ So I made a bunch of changes (added tons of files) to an archive on another machine, pushed the changes to the master repository on this machine, and now when I do git status it says all the newly added files are deleted. What do I need to do? git merge?04:08
travisjeffery joined04:09
thom__ or git checkout to grab the new files?04:09
Arrowmaster thom__: git faq non-bare04:09
Gitbot thom__: Pushing to non-bare repositories is discouraged. See http://git.or.cz/gitwiki/GitFaq#non-bare04:09
fynn left04:10
fynn joined04:12
bwwww joined04:12
bwwww hi guys. what man page explains the tree-ish notation?04:13
thom__ hmmm, so what should I do in the future? a git pull from the master archive machine?04:13
Arrowmaster yeah04:14
kevlarman bwwww: probably git rev-parse04:14
bwwww kevlarman, yea, thats the one04:15
thom__ is pushing to a branch safe?04:15
bwwww thanks04:15
plasticine left04:15
spearce left04:16
plasticine joined04:18
girishr left04:18
bwwww left04:19
dulia left04:19
mark[oz]___mark[oz]04:20
Marmouset joined04:23
plasticine left04:23
fynn basically, you're not supposed to push to non-bare repos, because you may be creating conflicts for the person working on them?04:25
cthompson left04:26
bryanl left04:27
kevlarman fynn: you're not supposed to push to non-bare repos because if you push into the checked out branch you'll trash the index04:28
plasticine joined04:30
thom__ trash the index? I just did a git reset --hard because I didn't have any changes on this side so I think things are okay, but.... if I had just a git commit on this side it would have simply shown all the new files I had added as deleted, right?04:31
kevlarman not on your end, the other end04:32
Hydrogen joined04:33
thom__ when I did a git status on the "pushed too" side it said all the new files i added on the other machine were deleted. Makes sense, I hadn't checked them out, there weren't there, so a commit would have just have recorded them as dleted in the HEAD, no?04:35
I think I resolved this correctly with the git reset, just trying to understand as a "learning moment"04:36
plasticine left04:39
kevlarman thom__: see faq non-bare04:39
Gitbot thom__: Pushing to non-bare repositories is discouraged. See http://git.or.cz/gitwiki/GitFaq#non-bare04:39
spearce joined04:39
plasticine joined04:43
girishr joined04:43
troter left04:44
jony_ joined04:44
bryanl joined04:44
troter joined04:47
plasticine left04:48
aboodman joined04:49
aboodman Hello all, I realize preserving timestamps is a sore subject, and I've read the FAQ and http://kerneltrap.org/mailarchive/git/2007/3/1/240167. But I was wondering -- if I wanted to hack git to restore the last modified time on checkout, is that data already stored in the repository -- or would I have to store it?04:52
neunon joined04:54
plasticine joined04:55
doener left04:56
kevlarman aboodman: wouldn't that screw badly with things like make?04:56
offby1 aboodman: I assume you'd have to store it.04:56
dunno where04:56
sshc joined04:57
aboodman kevlarman: I have modified my build to plaace the build results in different directories for each branch04:57
so, no04:57
sshc I have a hook with private information (3 passwords) on a gitosis hosted git repository. Can a normal client see the hook?04:58
kevlarman aboodman: in that case, no, git only stores commit times04:58
Ilari sshc: No.04:58
sshc: Assuming only git:// or ssh:// (through gitosis) access...04:58
doener joined04:58
sshc ok04:59
cedricv joined04:59
aboodman thanks kevlarman04:59
bryanl left05:00
Ilari aboodman: There are really two places you could store it: 1) In the commit object or 2) in some special file in tree. Even if one could define new commit header that indirects to listing of modification times, this isn't good idea because of reachability analysis wouldn't get it right...05:01
sverrej joined05:01
cawel left05:02
tbrx joined05:02
plasticine left05:04
zjason joined05:04
deskin I've been idly thinking of reworking git-svn to put git-svn-id: lines in git notes objects, but I wonder if this would be down the path of using notes for all commit metadata which doesn't really belong; wonder what using it for mtimes would look like05:06
plasticine joined05:06
SRabbelier joined05:07
ekidd left05:09
tjafk1 joined05:10
schlort_ joined05:12
plasticine left05:12
Niamor left05:13
psankar joined05:14
Niamor joined05:14
bondjuan left05:14
plasticine joined05:16
CardinalNumber joined05:17
ashleyw joined05:19
perezd88 left05:21
schlort_schlort05:23
zobie joined05:25
plasticine__ joined05:26
tjafk2 left05:27
jrmuizel left05:27
ProperNoun left05:28
jrmuizel joined05:28
perezd88 joined05:29
perezd88 left05:30
jrmuizel left05:31
plasticine left05:34
bobesponja joined05:35
travisjeffery left05:36
plasticine__ left05:37
fynn left05:38
Niamor left05:38
jrmuizel joined05:38
Niamor joined05:39
ToxicFrog joined05:40
plasticine joined05:40
schlort left05:43
fynn joined05:45
joshdavey joined05:49
girishr left05:50
girishr joined05:51
Hydrogen left05:52
Beket left05:53
jrmuizel left05:56
jrockway joined05:56
bdimcheff left05:56
zaius left05:59
ieure Okay, so is it me, or is git-svn just an utterly worthless piece of shit?06:00
Every time I’ve tried to use it, it’s been a massive pain in the ass, constantly doing the wrong goddamn thing and fucking up my repos.06:00
Ilari ieure: More like it does its best with SVN, but SVN is just too much... :-)06:01
plasticine left06:01
ieure Ilari, I’m no fan of SVN, but the level of retarded bullshit I have suffered with Git is _nothing_ compared to SVN.06:02
I just dcommited some shit, and git-svn decided to commit it to a tag for some fucking reason.06:02
kevlarman because you had a tag checked out06:03
(or you merged a tag, which the man page tells you not to do for this very reason)06:03
plasticine joined06:03
ieure kevlarman, Nope. Unless git-svn was retarded enough to check out a tag for me.06:04
I did: "git svn clone --stdlayout $SVNPATH"06:04
Then worked.06:04
Then dcommitted.06:04
Did my work on branches, and specifically did "git checkout master" before I dcommitted.06:05
curvature left06:06
curvature joined06:06
k776 joined06:09
deskin ieure: git-svn checks out whatever the most recent commit in svn was initially, wherever it may be06:10
ieure deskin, That qualifies as retarded.06:10
k776 left06:10
deskin patches welcome06:11
ieure Where is that documented?06:11
plasticine left06:12
deskin not sure it is documented in any docs which ship with git06:12
wagle joined06:12
ieure Awesome! So I quite possibly get a repo for a different branch/tag of my SVN repo every time I clone it with git-svn, and it’s undocumented behavior?06:13
Sign me the fuck up.06:13
reithi joined06:13
ludde joined06:14
deskin ieure: it's a bug if the git repo is different between clones; but yes, you'll get a different branch checked out. Of course, you're then able to checkout the branch you want to work on06:15
deskin sleep06:16
DrNick I take it you get the most recent SVN revision?06:16
sshc left06:16
ieure I don’t really grok the Git lingo, but what I’m saying is: The files you get are for a random SVN path when you clone.06:17
Which seems to be what you’re saying. And I just cannot believe that anyone considers that helpful in any fucking way.06:17
DrNick I wasn't talking to you, I was talking to deskin06:18
gwoo joined06:18
DrNick you seem to have an attitude problem and aren't worth interacting with06:18
ieure My attitude problem is caused by the endless grief Git causes me every time I try to use it.06:19
DrNick then don't06:19
davidfetter left06:22
qrush HEY DRNICK06:22
I HATE THE SOFTWARE THAT YOU SHOULD KNOW EVERYTHING ABOUT06:22
can't answer my questions? too bad, i'm gonna be an asshole anyway06:22
excuse me while i go beat my wife and throw my monitor out the window06:22
speakman joined06:22
speakman hi folks!06:23
bdiego left06:23
plasticine joined06:25
qrush heyo06:25
a-priori joined06:26
ph^ joined06:26
travisjeffery joined06:27
Weaselweb joined06:27
muthu_ joined06:28
dulia joined06:29
agenteo left06:30
iulian joined06:31
moriyoshi joined06:32
the6step joined06:32
bobesponja left06:33
plasticine left06:33
mansour joined06:39
plasticine joined06:40
robinr joined06:45
plasticine left06:45
Tuomas joined06:46
Tuomas left06:50
Tuomas joined06:51
dwmw2_gonedwmw206:55
plasticine joined06:57
speakman There's a thing with Git I do not really figure out how to handle; I have my very special patches in the kernel which I maintain myself. I've cloned the kernel source via Git and made my own branch (ts-2.6). But how do I now make sure everything new happening at my clone source to be merged/pulled into my own branch?06:58
j416 speakman: git pull ?06:59
blarz joined07:02
blarz left07:02
speakman will it by default pull the HEAD of the remote repo?07:03
Aikawa left07:03
j416 yeah07:06
plasticine left07:07
j416 it will update your copy of the remote repo07:07
then merge with it07:07
a-priori left07:08
neunon left07:10
girishr left07:10
plasticine joined07:10
speakman is there any point with making my own branch named "master"?07:10
ashH joined07:10
moore_ joined07:10
j416 how do you mean?07:11
you can name it to whatever you want. :)07:11
mark[oz] left07:11
speakman HEAD is still what's count?07:11
j416 I am not sure what you mean07:12
personally I try to keep all commits common to all branches in my master branch07:12
speakman I'm new to Git, there's alot of things to figure out, sry :)07:12
j416 that way i can easily merge in master to any branch and get all "global" updates07:12
speakman: :)07:13
i have only used it for just over a month myself07:13
happy learning!07:13
HEAD is just a reference to the tip of the current branch07:13
speakman The Right Way <tm> would have been to NOT branch the master but just applying my patches to it and keep developing in that branch?07:13
j416 it points to a commit07:13
Phlogi joined07:14
j416 speakman: you could develop using only one branch, yes07:14
Phlogi I onced forked a git repot but just copying files and pushing them to another repo. Now I would like to get some changes from the original repo back into my forked version. Whats the easiest way? Can I import just some commits?07:14
troter left07:14
speakman E.g; "git clone git://some.repo/kernel.git" and then just apply my patches and keep developing?07:14
j416 but as you learn more, you will see that keeping multiple branches is very convenient.07:14
speakman Is there any reason to use branches even when not trying something "new" out?07:15
j416 yes07:15
maybe you have a separate version of your project with only slight modifications07:15
that could be a separate branch07:15
speakman Where should critical bugfixes go to then?07:16
j416 for example, I keep a debug branch that is in sync with the dev branch, but which contains code that spits out debug info07:16
speakman oh! nice point (y)07:16
j416 a nice way to fix a bug would be to branch off, fix the bug in its own branch, test that it works, then merge it in again07:16
priidu_ joined07:17
fynn left07:17
j416 that way you could continue working on a functional project version if you, say, can't fix the bug directly07:17
plasticine left07:19
moore__ left07:19
speakman should I delete the branch when it's been merged?07:19
j416 if you see no other use for it, I don't see a reason to keep it07:19
ceyusa joined07:19
j416 (it would be troublesome to end up with hundreds of small branches in the end)07:19
speakman sounds true :)07:20
j416 when you merge it, its history will be recorded in the branch you merge with anyway07:20
so you don't lose anything07:20
robinr left07:22
Phlogi so I would add the original forked git repo as a local branch with git remote add foo foo_url ?07:23
plasticine joined07:24
madewokherd left07:24
spearce left07:24
arlenik_ joined07:25
Phlogi and now I fetched that... so how can I diff those two branches for example or how can I just merge single commits?07:25
arlenik_ I added files with 'git add *.o', now how do I remove them?07:25
ruskie git rm *.o ?07:26
j416 no07:26
speakman left07:26
speakman_ joined07:26
j416 git reset *.o07:26
speakman_ (sorry, lost network connection)07:26
j416 git status tells you this07:26
giallu joined07:26
ruskie ow yeah...07:26
I keep forgetting that bit07:26
j416 git rm would delete your file from working dir aswell07:26
and from the repo07:26
giallu left07:26
ruskie only if it's git rm -f isn't it?07:27
j416 git reset resets your index07:27
giallu_ joined07:27
j416 git rm removes the file from git alltogether07:27
arlenik_ I get an error 'main.o has changes staged in the index'07:27
j416 (or rather, records it as deleted)07:27
Phlogi I mean I don't want to merge the whole branches... just specific commits? Is that possible?07:27
arlenik_ i only want to remove it from the index07:27
giallu_ left07:27
ruskie Phlogi, cherry pick07:27
DrNick arlenik_: git rm --cached07:28
ruskie Phlogi, git cherry-pick --help07:28
Phlogi ok thanks07:28
plasticine_ joined07:28
Phlogi ruskie: does this hash value specifiy the commit completely or do I need to tell the branch too?07:29
arlenik_ DrNick: i get usage error for git rm --cached07:29
nvm07:29
ruskie hashes are supposed to be unique all over the place from what I understand...07:29
arlenik_ I have uncommented '*.[ao]' in my info/exclude file but git still tells me things like main.o are untracked07:30
Phlogi ruskie: thanks its works already :)07:32
j416 Phlogi: the hashes are unique07:33
Phlogi nice :)07:33
and if I want to update my remote branch I do just git fetch foo bar again?07:33
bentob0x joined07:33
j416 (otherwise git wouldn't work :))07:33
fetch yes07:34
girishr joined07:34
giallu joined07:34
Phlogi jup07:36
j416: how many of those hashes exist? :D its a hex value right?07:36
j416 more than enough :)07:36
google "sha1" for info07:37
troter joined07:37
sandGorgon joined07:37
troter left07:38
arlenik_ I don't get it. why do i need to add stuff to the index? why can't I just make my changes and do commit?07:39
DrNick I don't get it. Why can't I make partial commits of only the changes I want to make right now? Why do I have to commit everything at once?07:40
troter joined07:40
arlenik_ amusing07:40
johan-s left07:40
shapeshed joined07:41
plasticine left07:41
arlenik_ so adding stuff to the index is like mini-commits?07:41
DrNick you stage things for commits, yes07:42
arlenik_ does the index get cleared after each commit?07:43
DrNick the index is basically a flattened view of the entire working tree, so it doesn't it cleared, it gets updated to match (or, rather, you're creating a new commit from the contents of the index)07:44
j416 arlenik_: the index contains everything that will be committed on the next commit07:45
au- joined07:45
j416 when git status reports that your working dir is clean, it means everything matches your index07:46
when you alter a file, your working copy will be different from the copy stored in the index, so you update the index with git add07:46
every time you do git add <your file>, your file is copied to the index07:47
DrNick (more accurately, a new blob is created for the file contents, and the index is updates to point to that blob)07:47
j416 and files (or individual changes) you don't add after editing them will simply not be included in the next commit07:47
Casan left07:48
j416 so at any time, when your working directory is reported to be clean, or you have files that are staged for commit07:49
it means git has stored a copy of that data07:49
untracked files and unstaged changes are not in git at all.07:49
what happens when you do a commit, is that a pointer is created to that data, and it is stored as part of your history07:50
simply explained.07:50
arlenik_: still there? :)07:51
arlenik_ yes, i'm reading07:51
it's making more sense now07:51
so, how would i tell git to untrack a file that it's tracking right now?07:51
j416 so say you only want to commit changes you made to file A, because the changes you have made to file B are not ready, and besides, they are totally unrelated to the changes in file A07:51
then you might choose to only stage A and commit07:52
naeu joined07:52
j416 arlenik_: git rm <file> will remove the file from index, and from your working dir07:52
and in the next commit, it will be marked as deleted07:53
if you do git rm --cached, it will not touch your working copy, but still remove it from the index07:53
(cached = index)07:53
arlenik_ ahh, okay. i see.07:53
j416 and it will show up as untracked07:53
kervel joined07:55
arlenik_ j416, DrNick, you've been a great help. Thank you for your time. I've got to go have fun with git now :-)07:55
travisjeffery left07:55
arlenik_ left07:55
kervel hello, we have a big project with lot of branches, and we need to keep track of "which commits need merging to master". with "git log" it works fine, except for commits that were already cherrypicked into master, they remain in the log. any solution ?07:56
j416 you're.. welcome07:56
therrg left07:56
j416 :)07:56
kervel i found this comes close: http://kerneltrap.org/mailarchive/git/2008/7/23/2648344 but it needs rebasing07:56
tal67 joined07:56
harinath left07:56
webben joined07:57
webben Hi, I'm trying to find out if git-svn supports generation of svn:mergeinfo metadata yet.07:57
ahupp|fb joined07:58
shapeshed left07:58
harinath joined07:58
webben I found this: http://marc.info/?l=git&m=121196641823189&w=207:58
Niamor left07:58
webben but I'm not sure where to look to see if something like it has been integrated and works.07:59
Niamor joined07:59
DrNick kervel: git cherry doesn't do what you want?08:00
shapeshed joined08:00
moore__ joined08:01
webben nvm ... grep -r "mergeinfo" git-1.6.1/* turns up nothing08:01
libc__ joined08:03
harinath left08:06
meyering joined08:08
hdl2 joined08:10
moore_ left08:11
naeu left08:12
libc_ left08:13
muthu_ left08:14
hyperboreean joined08:20
hyperboreean hey guys, is there a way to remove the global git configs? a more elegant one, rather than doing git config user.name "" ?08:21
j416 hyperboreean: rm ~/.gitconfig08:21
if you are looking to unset a single key using git config08:22
Pieter or git config --unset --global user.name08:22
j416 you will find the flag --unset in its man-page :)08:22
hyperboreean thanks guys, I think removing git config will do it :)08:25
j416 hyperboreean: note that the git config files are plain text files in ini-style format08:25
jmesnil joined08:25
j416 you can edit them as they are if you want08:26
hyperboreean yes, I have edited some of them ... just I didn't know that I have a global one :)08:26
j416 git config is just a command-ish way of doing just that08:26
moore_ joined08:26
j416 ok :)08:26
vuf_ joined08:27
moore__ left08:28
johan-s joined08:29
shapeshed left08:30
ben_h hi folks08:31
i've got a repo with a bunch of commits - i'd like to undo the latest two commits, i.e. move the HEAD back to HEAD^2, but leave the changes from those two commits in the working copy08:32
remove two commits without touching the files on-disk in effect.08:32
is there an easy way to do that?08:32
Pieter git reset HEAD^208:33
derRichard joined08:35
telmich morjen08:37
shoe left08:38
foca joined08:38
pierre- joined08:39
shoe joined08:40
ben_h jeez, that _is_ easy :)08:43
thanks Pieter08:43
bbl all08:43
naeu joined08:43
kervel i tried git log --cherry-pick and git cherry for showing A..B log that should omit everything from B that was cherrypicked in A, and it still shows the cherrypicked changes08:44
ben_h left08:44
martinpaul_martinpaul08:46
charon joined08:47
hurikhan|Work joined08:47
vuf_ I have a detached HEAD, and want to move master to where I'm at ... how would I do that?08:48
Pieter vuf_: git branch -f master08:49
vuf_ Pieter: right, that escaped me ... thanks08:49
I was looking for a named version of reset08:50
charon left08:52
derRichard left08:53
rraasch joined08:55
sverrej_ joined08:55
sjn joined08:55
lebreeze joined08:58
lebreeze left08:58
Marmouset left09:00
lebreeze joined09:01
lebreeze left09:02
dwave joined09:03
charon joined09:04
comphappy joined09:04
j416 left09:05
muthu_ joined09:05
arekm joined09:06
comphappy if I put a system link in my local git, when i do git add will it see as system link, or the files inside of it09:06
arekm wonder why git send-email can't be used from outside of repository. I often work with repositories on one machine and would like to send-email from another09:06
tal67 left09:07
sverrej left09:07
DrNick comphappy: a what?09:08
charon arekm: it uses the repo's .git/config too. you could make a patch to make that optional09:08
moore_moore3309:09
comphappy DrNick: I have my local git project repo at ~/triageproject09:09
I have another project i want to put in that git repo at ~/workspace/otherproject09:09
__name__ joined09:10
comphappy can I put a system link in ~/triageproject that points to ~/workspace/otherproject09:10
or is that just asking for trouble09:10
DrNick oh, you mean a symbolic link?09:10
no, you can't, git will just store the symlink itself09:10
comphappy sorry... yes I need some more coffee09:11
ok that is what I though09:11
__name__ left09:11
name joined09:11
moore33 comphappy: If you want to include one project in another, you need submodules or to read about doing a subtree merge.09:11
comphappy the problem with sub-modules is that trac cannot work with them09:12
tal67 joined09:12
plasticine_ left09:14
zjason left09:18
benjo2 left09:19
samjam joined09:22
comphappy left09:22
solydzajs joined09:23
derwolf joined09:24
mark[oz] joined09:24
sverrej_ left09:25
sverrej_ joined09:26
mithro left09:27
jchris left09:32
benjo2 joined09:35
name left09:35
name joined09:37
moore33 left09:40
moore33 joined09:41
Catfish joined09:42
Catfish Heya09:42
Anyone use emerge? I've gotten stuck trying to do a merge over ssh...09:42
After using a or b to select a difference, are you supposed to just manually remove the conflict markers, or is there a command?09:43
I can't seem to find it...09:43
cmarques joined09:43
psychoschlumpf joined09:47
psychoschlumpf hi09:47
is there a way to only allow a user to push his changes to the master repo if all tests run fine on it?09:48
like with svn's pre-commit-hooks09:48
simoncpu joined09:49
simoncpu hello09:49
thiago you can use pre-recieve hooks09:49
simoncpu i'm experimenting with a workflow that uses both cvs and git09:49
how can i ignore CVS/* directories?09:49
thiago which technically are a misnomer: it's after the reception, but before the update09:49
simoncpu: echo CVS >> .gitignore09:49
psychoschlumpf thiago: will a pre-recieve hook check the whole bunch of commits or every single commit?09:50
simoncpu but there are lots of CVS directories... =)09:50
thiago psychoschlumpf: it will do whatever you write in the script09:50
simoncpu: but they are all called "CVS"09:50
simoncpu ah...09:50
lemme try09:50
very coooool09:50
psychoschlumpf ok: the other way around: will git call the post-receive hook for the whole push or for every single revision which is pushed in one push?09:50
simoncpu gives thiago a beer09:50
thiago psychoschlumpf: I think you should read the documentation of the pre-receive hook instead09:51
psychoschlumpf thiago: okay, thanks09:52
thiago there's a hook that is called for every single commit in the pack09:53
but that's not the pre-receive hook09:53
psychoschlumpf just read it09:53
pre-receive hook is called once and gets the single commits on stdin09:53
thiago the pre-receive hook receives a list of branch changes in stdin. It's up to you to decide what to do.09:54
you can test every single commit introduced, or you can test just the finals, or you can do anything in-between09:54
uhu01 joined09:58
uhu01 hi, is there a command to condense three commits to one? I think i red it some time ago, but I couldn't find a hint anywhere10:00
teuf uhu01: git rebase -i helps you to do that10:00
markelikalderon joined10:00
tokkee uhu01: git rebase -i -> squash the commits.10:00
uhu01 thx10:01
dulia left10:04
moriyoshi left10:05
Clebrate joined10:06
moore_ joined10:06
Clebrate Does anybody here speak Scandinavian?10:07
thiago I can read Norwegian10:07
Clebrate I need to translate "to fork a project"10:07
thiago: God bless you :)10:07
thiago from a Scandinavian language or to?10:07
pierre- left10:07
Clebrate To.10:08
Pieter the 'from' part would be easy10:08
moore33 left10:08
Clebrate heheh10:08
yeah...10:08
pierre- joined10:08
jnl thiago: any scandinavian language in particular, or just.. scandinavian in general? :)10:08
thiago jnl: --> Clebrate10:09
Pieter |> deflection10:09
thiago Clebrate: you can try the "å forke" verb...10:09
:-P10:09
Clebrate hehe10:09
<Rounin> Å forke...10:10
<Rounin> Eneste forskjellen er at o'en kanskje er litt lengre, og tonefallet er helt ødelagt10:10
thiago that's norwegian10:10
Clebrate <Rounin> Synkende tone frem til midten av o'en, og så stiger det på et øyeblikk... Akkurat som i "bønner" og "venner"10:10
<Rounin> Vi har jo ord som "forgrene" (branch) osv., men forking er forking10:10
from some other channel10:10
Pieter that's norwegian10:11
Clebrate he was kinda joking though10:11
yup10:11
Pieter oh10:11
I was too late :10:11
:)10:11
thiago why are you talking about tones?10:11
Clebrate dunno10:12
thiago and he's saying that "forking is forking"10:12
Clebrate i think he's a vocal coach10:12
Pieter he's a hardcore forker10:12
thiago "the only difference is that the 'o' can be a bit longer, and the tonefall is entirely destroyed. The sinking tone from the middle of o and lasts for an instant, like in 'bønner' and 'venner'. We have words like 'forgrene' (branch), but forking is forking"10:13
Niamor left10:13
Niamor joined10:14
Pieter in Dutch we just use 'branch' for 'branch'10:14
or, at least I do10:14
thiago I would too in Portuguese, even though it sounds nothing like Portuguese10:14
Pieter most tech-talk is very English-centric anyway10:15
Clebrate :D10:15
those are my two favorite languages10:15
Pieter compared to German or French, where a lot of stuff is translated10:15
Clebrate oh and arabic10:15
thiago Portuguese has only one word with the /tʃ/ sound and was imported from Italian10:15
Clebrate portuguese and dutch that is10:15
markelikalderon left10:16
Pieter :) Dutch is very easy if you're a native speaker10:17
just like with any other language10:17
mark[oz] left10:17
solydzajs left10:19
ankit9 left10:19
mark[oz] joined10:21
Kbyte joined10:21
ben_h joined10:21
ahupp|fb left10:27
tango_ left10:28
tango_ joined10:28
moon_unit left10:28
aguerreiro joined10:29
bgmarete left10:32
timebomb joined10:34
timebomb heya im trying to convert a mercurial repo to git and fast-export fails. anyone come across this error before? http://pastie.org/37720810:35
_Vi joined10:35
flow joined10:36
tanek joined10:37
tal67 left10:37
thiago that means the reader side closed10:37
check if git-fast-import created a crash log in your target .git10:37
sandGorgon left10:37
ben_h left10:38
ben_h joined10:38
timebomb http://gist.github.com/4e25308d7a5e5d1b086e10:39
ankit9 joined10:39
trupheenix joined10:40
timebomb says mark :0 not declared but obviously i do not know how to deal with that10:40
trupheenix how do i correct spelling mistakes inside the message for a commit after the commit is done?10:41
thiago git commit --amend10:41
trupheenix thiago: older commits?10:41
speakman_ (missed the scandinavian discussion, but I'm from Sweden if it's to any help)10:41
thiago git rebase -i oldestcommit^10:41
speakman_speakman10:41
thiago change to "edit"10:41
remember that you can't change commits that other people already have10:41
speakman wont a spelling fix change the sha1?10:42
thiago it will10:42
that's why you can't change commits that other people already have10:42
timebomb any idea how to deal with that thiago ? hg verify says everything is fine ...10:44
j416 joined10:44
thiago what does git say?10:44
ah, you pasted it10:44
it's a bug in the fast-export10:45
tal67 joined10:46
timebomb known bug? i couldn't find anything about it but maybe i was just searching for the wrong thing10:47
thiago I don't know if it's known10:47
but it's telling fast-import to use mark 0, but it didn't define that mark10:48
therefore, it's a bug10:48
jaeckel joined10:48
Pieter I'd guess it can't find a commit's mark number and just returns 010:51
timebomb mh10:51
pinholecamera_ joined10:54
pinholecamera left10:58
pinholecamera_pinholecamera10:58
ankit9 left10:59
tamiko left11:02
tamiko joined11:02
schierbeck joined11:02
gretch left11:02
greyface joined11:04
schierbeck left11:06
mark[oz] left11:06
gouki_ joined11:06
aguerreiro left11:08
sverrej_ left11:09
kraymer joined11:09
flow left11:12
sverrej joined11:12
plediii left11:14
Phlogi left11:16
kbingham joined11:16
Phlogi joined11:17
gouki left11:22
mark[oz] joined11:23
eddyp joined11:28
gouki_ left11:32
gouki_ joined11:32
Flathead left11:32
madnashua joined11:32
hurikhan|Work left11:32
muthu_ left11:32
telmich hmm, why can't I git push --all --tags?11:35
Voker57 use --mirror maybe11:36
Pieter I think --all implies --tags?11:36
Voker57 nope11:36
hurikhan|Work joined11:37
telmich oh, yes...strange, though11:37
I would not thing --mirror function really excludes me from naming both manually11:38
troter left11:39
timebomb hm hg-to-git doesn't work either :S11:40
Yuuhi joined11:42
lorandi joined11:43
grahal joined11:45
j416 left11:47
moore_ left11:49
moore_ joined11:49
trupheenix left11:52
harinath joined11:52
radarek joined11:54
bryanl joined12:02
johan-s_ joined12:03
hurikhan|Work left12:05
hurikhan|Work joined12:07
iulian left12:10
schlort joined12:12
johan-s left12:13
eddyp left12:13
Hendu joined12:15
cemerick joined12:16
slava joined12:16
slava i have a patch that renames a file, only changing its case, and now i'm having trouble pulling this change onto a mac (case-insensitive file system12:16
is this a known bug?12:17
shd i think it's a feature12:18
simosx joined12:18
slava a feature?12:18
yeah, because it encourages people to switch to linux instead of using inferior operating systems, right, haha12:19
shd right :-)12:19
au- noob question.12:19
shd no seriously, the project that uses such names is at fault here..12:20
au- git can't merge 2 files if it doesn't have to commit history right?12:20
shd au-: right, but patching is different12:20
slava shd: regardless of coding practices and naming conventions, git shouldn't refuse to pull a patch that renames a file changing case12:20
johan-s joined12:20
slava in this instance it was renaming foo.TXT to foo.txt12:20
au- can I do it with patching? /me looks up 'patch'12:20
slava one would think this woudl be pretty harmless12:20
shd slava: better mail your report to git mailing list12:21
mark[oz] left12:21
slava I will, but their answer will probably be similar to yours12:21
where I work, refusing to fix a bug would get you fired ;-)12:21
Sho_ joined12:22
shd slava: fortunately it's an open source project so we can argue what is a bug and what is not..12:22
au- it's an "unintended feature"12:22
slava shd: if 'git status' reports that there are no uncommitted changes, and git pull only has to fast forward without doing a merge, and it fails, that's clearly a bug12:23
ashleyw_ joined12:24
moore__ joined12:25
Arjen foo.txt and foo.TXT are the same file on osx, hence the error12:25
Kathrin-25^away joined12:25
slava sure, but there's no time when both exist at once12:26
Arjen Just create a case-sensitive HFS+ disk image and use that12:27
There has been lots of threads about this on the mailing list12:27
iulian joined12:28
webben left12:30
slava sounds like something that should be fixed, then12:30
Arjen slava: What's the exact error message? Something like "fatal: destination exists ..." ?12:30
ashleyw left12:31
slava I don't have it on hand anymore, but roughly 'untracked file foo.TXT would be overwritten by merge"12:32
but the file was checked in and git status did not report uncommitted changes12:32
let me reset the repo and pull agian12:32
error: Untracked working tree file 'basis/io/encodings/japanese/CP932.txt' would be overwritten by merge.12:33
gouki_gouki12:33
moore_ left12:34
mark[oz] joined12:35
Arjen It's know, and apparently hard to fix well12:36
s/know/known/12:36
madnashua left12:37
mark[oz] left12:37
johan-s left12:37
johan-s_ left12:38
vbabiy joined12:39
johan-s joined12:39
EmilMedve left12:40
kraymer_ joined12:40
kraymer left12:40
plasticine joined12:41
parasti joined12:43
imarcusthis &win 212:45
meh12:45
cannonball joined12:45
plasticine left12:46
slava left12:46
KRiSPY joined12:47
wereHamster what's the best way to check from a script whether the working tree is dirty or not?12:47
tokkee fonseca: Hi!12:47
doener wereHamster: regarding the index or HEAD?12:47
tokkee fonseca: I'm getting the following when using tig 0.13 with LC_ALL=C: http://osprey.tokkee.org/~tokkee/tmp/tig-0.13-lc_all=c.png12:48
fonseca: Any ideas what might be wrong?12:48
wereHamster doener: HEAD I assume. I want to see if I can safely do git-rebase12:48
reithi left12:48
au- okay so I have 2 different branches that I need to merge. I have no history of the files12:49
KRiSPY left12:49
au- does git have any tools to make this easy?12:49
bryanl left12:49
tokkee fonseca: It works fine with e.g. en_us.UTF-8.12:49
mikl joined12:49
doener wereHamster: I'd probably copy the checks from git-rebase.sh12:50
awarde joined12:50
greyface left12:51
doener wereHamster: maybe using --quiet with diff-index command12:51
girishr left12:51
jel joined12:51
jel Hey guys. Anyone know how to fix a "fatal: bad object HEAD" error?12:52
jony_ left12:54
greyface joined12:55
cbrake_awaycbrake12:55
wereHamster doener: thanks, the rebase script has indeed these checks12:55
arekm left12:55
sverrej left12:56
wereHamster or, well, I could call git-rebase directly and let it fail if the working tree is dirty..12:56
deskin DrNick: (from ~7 hours ago) you get the most recent revision from SVN, mapped to trunk/branch/tag however you specify, and git checks out a local master branch at that commit12:57
jel: what does the contents of .git/HEAD look like?12:58
solydzajs joined12:58
mcella joined13:01
GeertB left13:01
tokkee fonseca: That seems to happen with any non-UTF-8 locale, both using ncursesw 5.5 and a "5.7+20090124" snapshot.13:02
timebomb left13:03
johan-s left13:07
jel deskin: "refs/heads/master". That refs file is present.13:07
deskin 'refs/heads/master', not 'ref: refs/heads/master' ?13:07
jel deskin: sorry, yes. ref:...13:07
deskin what does git rev-parse refs/heads/master say? What is the content of .git/refs/heads/master ?13:08
jel deskin: .git/refs/heads/master is just a hash. The tree used to work before I zipped them all up and moved them to a windows machine.13:10
rev-parse gives: fatal: ambiguous argument 'refs/head/master': unknown revision or path not in the working tree.13:10
thiago is there a .git/refs/heads/master file?13:12
deskin hmm; windows aside, copying the repo to another machine ought to work13:12
jel thiago: there is. It contains a hash, which looks normal as far as I can tell13:12
thiago why didn't you push to another machine instead?13:12
KRiSPY joined13:12
deskin my best advice at this point is to run git fsck --lost-found, look through the dangling commits listed with git show <hash>, and when you find the right one, git update-ref refs/heads/master <hash>13:13
I'm wondering if it's a permissions issue, but that's just a shot in the dark13:13
are you running cygwin? Can you strace git rev-parse and pastebin it somewhere?13:14
thm joined13:14
jel deskin: ok. Thanks. At least I know it should be fixable. Gotta go now. Any chance it's related to the remote repos ssh aliases not being set yet?13:14
deskin no, that has nothing to do with locating objects13:14
jel deskin: cygwin, yes. msys gave the same error. I'll give that a shot later.13:14
deskin: ok, thanks13:14
deskin alright, good luck13:15
ceyusa left13:15
ekidd joined13:18
cmarcelo joined13:20
thm left13:24
Acry joined13:24
Acry left13:25
foutrelis joined13:28
cthompson joined13:31
davidfetter joined13:32
EmilMedve joined13:33
bryanl joined13:33
ProperNoun joined13:34
a-priori joined13:35
naeu left13:36
naeu joined13:37
samjam left13:38
jas4711 joined13:39
markelikalderon joined13:40
CardinalNumber left13:40
EmilMedve1 joined13:47
cmarcelo left13:48
Niamor left13:48
cmarcelo joined13:49
Niamor joined13:49
boto joined13:49
EmilMedve left13:49
cawel joined13:50
metaperl_work joined13:50
metaperl_work what git command lists the latest pushes/commits?13:50
imexil joined13:50
ciaran log13:50
psankar left13:50
ciaran :/13:50
Kathrin-25^away left13:50
ashleyw_ left13:51
metaperl_work thank you13:51
imexil Hi, I've got a free floating commit which is not attached to any branch. How can I now apply this to, let's say master?13:51
ashleyw joined13:52
Voker57 git cherry-pick13:52
emss joined13:53
imexil yes of course ... thank you Voker57 :)13:53
metaperl_work git log doesnt show me which files were pushed with each commit13:54
doener -p|--name-only|--name-status|--stat|...13:54
nothingmuch metaperl_work: git whatchanged13:54
Araneidae joined13:55
Araneidae How do I view the previous revision of a file, please?13:56
nothingmuch git show decafbad:path/to/file13:56
similarly git checkout can be used to go back to the previous revision13:57
metaperl_work wow13:57
thank you nomis13:57
i mean nothingmuch13:57
Araneidae Well, it's quite painful to find the decafbad bit13:57
Is there a way to say simply last nth version?13:57
nothingmuch read on git-rev-parse13:57
HEAD~N13:57
Araneidae $ git blame sstrip.sh~113:58
fatal: cannot stat path scripts/build/tools/sstrip.sh~1: No such file or directory13:58
parasti metaperl_work: note that "push" is what happens when you use "git push"13:58
nothingmuch git blame HEAD~1:sstrip.sh13:58
i think13:58
dantrell joined13:58
dantrell Let's say there's repos foo and bar. Bar is a much smaller version of foo but maintains the same format. I want to create a patchset for foo to use to update to bar's changes. Is there no way to do this for an outside repo?13:58
ceyusa joined13:58
doener nothingmuch: without the :13:59
gitte joined13:59
nothingmuch metaperl_work: note that doener's answer is also for you13:59
doener nothingmuch: blame takes revision and name, not just a blob13:59
nothingmuch ah right13:59
if it were show it'd probably need the colon though, right?13:59
doener blob's have no history, so it'd be pretty hard for blame to do anything useful13:59
yep, show <blob> (i.e. with colon) shows the blob14:00
Araneidae Unfortunately I think `git blame HEAD~1 filename` is giving me the filename as of the previous HEAD version.14:00
doener show <commit> <path> shows the commit with the diff limited to <path<14:00
Pieter Poor little Bobbie Blob.. he only knows what's happening now, but not what hap -- what was I saying?14:00
Araneidae Not so useful when I'm trying to track back through the history of one particular file14:00
nothingmuch Araneidae: what are you trying to find out?14:00
Araneidae I'm trying to find when a particular pattern was in this one file14:00
wildmind joined14:00
Pieter Araneidae: git log -S'searchmatch' -- path/to/file14:01
Araneidae There's a line that isn't in the file in head, and isn't in early versions14:01
wildmind I pushed some changes to a remote branch. The changes appear in the index on the remote but are not commited ... how come?14:01
Pieter wildmind: did you read faq non-bare ?14:02
Gitbot wildmind: Pushing to non-bare repositories is discouraged. See http://git.or.cz/gitwiki/GitFaq#non-bare14:02
moore__ How about git-log -n2 file?14:02
johan-s joined14:02
Araneidae Pieter, that was helpful. Odd, though. The offending line doesn't seem to be in my history! Hmm.14:03
Kathrin-25^away joined14:03
wildmind Pieter: thanks14:03
Araneidae At least, assuming that my -S'pattern' would have picked up all commits containing matching lines...14:04
Pieter Araneidae: it only shows commits in which that pattern was added or removed14:05
not in which it moved14:05
Araneidae: you can also try a 'git log -p' and search through that with less if you want a quick fix14:05
;)14:05
Araneidae I have a horrible feeling the offending line was in a branch which isn't in my history (I'm searching a `git svn` history)14:06
Actually, `git-log -p` is exactly what I wanted! Thanks.14:06
moore__ Araneidae: previous revision of file: git-rev-list --max-count=2 HEAD foo.c | tail -114:06
Pieter moore__: -1 --skip=114:07
bobmcw joined14:07
Araneidae Unfortunately I use git very infrequently, so every time I do I'm painfully rusty!14:07
ekidd left14:07
Pieter yeah, that happens.. I have the same with hg/bzr or even svn14:08
moore__ Pieter: cool14:08
EmilMedve1EmilMedve14:09
nothingmuch svn can drive me nuts... svn log -n... no worky, svn log -l... nope, svn log --last? urgh!!! then I read the help14:10
(that's git style, svk style and then darcs style...)14:10
muthu_ joined14:10
hegge left14:11
hegge joined14:11
Araneidae Ah well. Most of my work is with svn -- I know to avoid working with branches!14:12
EiNZTEiN left14:12
Pieter yeah, that results in having to write very clean code all the time, it's a very good practice :)14:12
Araneidae The other thing I really have to watch with svn: as soon as any directory structure changes ... commit as soon as possible!14:14
dantrell Let's say there's repos foo and bar. Bar is a much smaller version of foo but maintains the same format. I want to create a patchset for foo to use to update to bar's changes. Is there no way to do this for an outside repo? I don't want to pull in the outside repo (which is really big) just to patch it.14:17
Voker57 git diff14:18
moore__ dantrell: git format-patch and git-am can be used to shuttle patches between dissimilar repos.14:20
esparkman joined14:20
ekidd joined14:21
aziz joined14:22
joshdavey left14:22
girishr joined14:23
wildmind left14:23
a-priori left14:24
dantrell moore__: I have been looking at git format-patch but I don't see how to diff foo and bar and get a single patch from that.14:25
nothingmuch Araneidae: git-svn is a real life saver14:25
it makes svn bearable14:25
joshdavey joined14:26
moore__ dantrell: Are there revisions of foo and bar where their contents are the same?14:26
xl0 joined14:27
dantrell moore__: Nope.14:27
Bass10 joined14:27
nothingmuch you can [ab]use git cherry-pick14:27
Araneidae nothingmuch, I guess I ought to try using it for my svn development! So far I've only used it to browse external repositories, when it's very useful. But then I'm used to svn and its quirks.14:27
moore__ dantrell: What does it mean to update one to the other then?14:28
plediii joined14:28
tro what could I have done to my repo or its config that git gui doesn't notice about half the changes made to the working copy? i have to run git update-index --really-refresh to have them show up in git gui14:28
moore__ You could just dump all the files from bar into foo and commit the result.14:28
tro i'm using msysgit14:28
xl0 Hi, guys. Could someone please tell me, what's the right way to set up a bare repository to track an other repo?14:29
Git pull doesn't work on bare repositories, and even if it worked, how would it handle the branches besodes master?14:30
parasti xl0: use git fetch instead14:31
dantrell Voker57: Wait, I think git diff does it...maybe...14:31
parasti xl0: pull is fetch + merge14:31
francois___ joined14:31
krh joined14:31
jschoolc joined14:31
francois___ left14:32
jschoolc is there an easy way to rollback/revert to a commit and blow away everything that happened after that, committed or not?14:32
dantrell moore__: Say foo has a/1 a/2 b/1 c/1 and bar has a/3 b/2 d/* e/*. There are pretty much more conflicts. I want what bar has in foo.14:32
nothingmuch jschoolc: git reset --hard14:32
dantrell much no conflicts*14:32
nothingmuch dantrell: you can use git fetch and then git cherry-pick14:32
dmlloyd joined14:33
moore__ dantrell: cp -r from bar into foo and commit the result. The diff isn't interesting, right? If you want to preserve the history in bar's commits, then you need to start from some common point in foo and bar.14:34
_Vi left14:34
moore__ dantrell: cp -r the working tree of bar, of course.14:34
jschoolc nothingmuch: does reset take a sha to reset to?14:34
ben_h left14:35
nothingmuch jschoolc: git help rev-parse... like any other command14:35
sha1, ref name, an expression involving ~ or ^ or @...14:35
dantrell moore__: I just want to create a patch to send to the foo maintainer. So I need the diff.14:35
girishr left14:36
GeertB joined14:36
moore__ dantrell: Do what I described, commit the result in foo, then use git-diff.14:36
dantrell: Rather, use git-format-patch for the canonical result.14:37
samjam joined14:37
moore__ dantrell: Otherwise, use plain old diff.14:37
ph^_ joined14:39
qrush_ left14:39
xl0 parasti: And how should I set up the origin remote?14:39
greister joined14:39
greister how to use git clone the tag?14:39
spearce joined14:39
dantrell moore__: Thanks.14:39
imexil left14:41
Araneidae left14:42
sverrej joined14:43
metaperl_work left14:43
vladimirprieto joined14:43
vladimirprieto hi14:53
ph^ left14:53
Niamor left14:53
Niamor joined14:54
vladimirprieto i'm thinking about installing git on the server, but i have some doubs about. is there's anybody that can answer a specific question on the use of git?14:54
bartman joined14:54
xl0 parasti: Just git fetch does not seem to work. What am I doing wrong? ;)14:54
vladimirprieto: Don't ask to ask, just ask.14:55
vladimirprieto ok14:55
this is my problem: i got a few programmers working on a web project. this project is already working and it had been using on differents customers on the same server.14:56
every custumer has its own directory www.myserver.com/customer14:57
every customer directory is an instance of the project we are programing, but every instance is not exactly the same. so, the question is: git can copy/export the project for productions WITHOUT touching some files in it (cus that files make identify every project)?14:59
ekidd left14:59
soul9 joined15:00
soul9 hi15:00
tryiong to rebase:15:00
qrush__ joined15:00
soul9 $ git rebase origin/master15:00
could not detach HEAD15:00
vuf_ left15:00
xl0 vladimirprieto: yes, if you ask it the right way.15:00
soul9 anyone got a clue? ☺15:01
kukks joined15:01
jrmuizel joined15:02
vladimirprieto x10: thanks for answer, but what do you mean exactly15:02
xl0 vladimirprieto: First, you have explicitly add newly created files to be tracket by git.15:03
bwalk joined15:03
xl0 And you can even select which files to include in a commit, if there are multiple changed files.15:04
shoe left15:04
ekidd joined15:04
vladimirprieto ok15:05
EiNZTEiN joined15:05
gitte soul9: without more information, no.15:05
vladimirprieto x10: i think i understand.15:05
EiNZTEiN_ joined15:05
vladimirprieto x10: thank you very much15:05
ashleyw_ joined15:08
Dvyjones joined15:10
ben_h joined15:11
xl0 Found what I was looking for.15:14
git --bare clone15:14
git remore --mirror add origin git://...15:14
git remote update now updated all the branches properly.15:15
Why isn't git remore --mirror add dont by git clone automatically? ;)15:15
ekidd xl0: git clone --mirror is probably what you want.15:15
gitte xl0: in general, it does not make any sense at all.15:16
marvil07 joined15:16
gitte xl0: --mirror overwrites the local copies of the tracked branches.15:16
xl0 gitte: It makes a lot of sence when --bare is used.15:16
ekidd: It is not yet in the man pages. ;)15:17
gitte xl0: not necessarily. As I said, it _overwrites_ the local copies of the tracked branches.15:17
rraasch left15:17
xl0 gitte: What else would I want a bare repository update to do?15:17
lebreeze_ joined15:18
gitte xl0: if you only have one upstream, right.15:18
lebreeze_ left15:18
soul9 gitte: ?15:18
gitte: ask..15:18
Niamor left15:18
Niamor joined15:19
gitte xl0: but Git is _decentralized_.15:19
soul9 i'd be happy to help you help me15:19
gitte soul9: was that really all that Git said? I cannot believe that.15:19
soul9 yes15:19
it was15:19
xl0 gitte: I understand it quite well. Probably yes, it should not be the default, but git clone --mirror seems to be a good idea.15:20
soul9 git rebase origin/master15:20
rewwinding...15:20
could not detach HEAD15:20
ashleyw_ left15:20
ashleyw_ joined15:21
gitte soul9: so what is your current branch right now ("git branch")?15:21
soul9 WIP215:21
Weasel[DK] joined15:21
gitte soul9: could you try "git checkout origin/master^0"?15:21
kanru left15:22
ashleyw left15:23
soul9 gitte: is the ^0 deliberate?15:23
gitte soul9: yes.15:23
soul9 (if it is, what does it mean?)15:23
Hendu left15:24
soul9 sec, it's my co-worker who's having problemms, so i'm copying his repo over..15:24
gitte soul9: it means that I want to detach the HEAD, not check out "origin/master" itself.15:24
ekidd left15:24
bdiego joined15:26
soul9 hmm15:26
ok15:26
lorandi left15:27
MarcWeber joined15:27
acoc joined15:27
MarcWeber When renaming/moving a lot of files which is the best strategies to follow changes made to another repo? Will git still apply the changes to the new location or will I get delete /modified conflicts all the time?15:28
soul9 gitte: nice, ok, that gave me something to work on15:30
rraasch joined15:30
xl0 left15:30
gitte soul9: I am sure I don't understand... no problem there?15:31
jrmuizel left15:31
soul9 gitte: no, that command gave me a usable error message15:31
gitte soul9: ah, okay. Good, then.15:32
soul9 gitte: yeah, it was: untracked local file would be overwritten..15:32
gitte soul9: that's what I expected, actually.15:32
soul9 yeah, well, it wasn't that obvious to me ;-)15:33
i hope i remember ^015:33
gitte soul9: it happened to me, recently, that's why...15:33
soul9 ah, i see15:33
gitte soul9: although it happened with rebase -i, and that command does not hide the error message.15:33
vladimirprieto left15:33
soul9 i see15:33
what is the difference between rebase and rebase -i?15:34
gitte soul9: the latter is interactive...15:34
soul9 i don't understand exactly..15:34
frsk Try for yourself and see the difference?15:34
soul9 what would interactive mean in the context of a rebase15:34
i did15:34
hmm15:34
gitte soul9: it lets you choose the order, and lets you skip commits.15:35
soul9 it was a long time ago, when i wasn't a git wiz yet ;-)15:35
i see15:35
well, i don't want that15:35
i'd like git to give me a usable error tho15:35
is there a rebase --verbose or something?15:35
15:35
krawek joined15:36
hugo_ joined15:38
akitada joined15:38
greister left15:38
foca_ joined15:39
gitte soul9: not that I know of. It uses "git checkout -q" to detach the HEAD, and that suppresses warnings _and_ errors.15:39
soul9: I mean the messages, of course.15:39
mahesh left15:41
Kathrin-25^away left15:42
Kathrin-25^away joined15:43
Knirch if I accidently did git reset HEAD~1, how can I quick and easy get that changeset back?15:43
gitte Knirch: should be a matter of "git reset HEAD@{1}".15:44
wereHamster how do I get the output of 'request-pull' into an email? I can't pipe it to imap-send, so it leaves me with manual copy&paste. But the lines are >80 chars so my MUA wraps those15:44
foca left15:44
gitte Knirch: does not work if you had uncommitted but staged changes, though.15:44
Knirch gitte: thanks, just what I was looking for15:44
wereHamster and I see that the pull requests sent to the kernel mailing list aren't wrapped, how do they do it?15:45
Knirch all the rev-parse fairy dust is confusing me, I should read that page once a day until it sticks15:45
ashleyw joined15:45
khisanth_ joined15:47
hugo_ left15:48
akitada left15:48
Knirch hmm, I was toying around with apply.whitespace, had it at fix, git add file ; git commit -mtest echoed rewrite file (93%), resetting to HEAD~1 and changing apply.whitespace to error and adding/committing again still rewrites the file15:49
khisanth_Khisanth15:49
Knirch is the resolution cached somewhere?15:49
tango_ left15:49
qrush__ left15:50
Knirch guess I'm just confusing myself, nevermind15:53
ashleyw_ left15:53
adam[pac] left15:54
EiNZTEiN left15:55
EiNZTEiN_EiNZTEiN15:55
dwave left15:55
skorpan joined15:57
adam[pac] joined15:58
Ryback_ joined16:00
Sho_ left16:01
lresende joined16:03
willb joined16:03
jrmuizel joined16:03
cib3r joined16:07
Ratler_ joined16:08
au- left16:15
mikearr left16:15
johan-s left16:16
bgmarete joined16:16
ben_h left16:17
cib3r How do I make git exclude files that are already on svn? I can get it to ignore files that don't yet exist, but not already existing files...16:19
withanx joined16:19
marvil07 left16:19
withanx if I committed changed files and I wanted to pull them out of the commit, back to a changed state, how would I do that?16:20
bantic joined16:20
paulboone joined16:21
jesselucas joined16:21
bgmarete left16:21
mikearr joined16:21
foca_ left16:23
rubydiamond joined16:23
greyface_ joined16:23
akitada joined16:23
ekidd joined16:26
dwave joined16:26
vuf withanx: git reset HEAD^, assuming it is the latest commit16:28
or, you could make your additional changes and do "git commit --amend" to replace the latest commit16:28
rwaite joined16:30
offby1 cib3r: I imagine you'll have to "git rm" them, _then_ add them to .gitignore16:30
cib3r offby1, would that remove them from svn as well?16:30
offby1 once you dcommitted, yes.16:31
jchris joined16:31
cib3r no way to do it without removing from svn?16:31
withanx HEAD^ is the last commit on current branch?16:31
offby1 I can't think of any way. You're suggesting that you want your git repository to be permanently out of sync with your svn repository, which seems weird.16:31
withanx: I think so, yes16:32
vuf withanx: HEAD is the latest, HEAD^ is the one before16:32
withanx aha16:32
offby1 is off by one, as befits his nick16:32
vuf hehe16:32
withanx so git reset HEAD^ would stage everything from the last commit?16:33
thiago no16:33
withanx or unstage16:33
uncommit16:33
heh16:33
thiago it would simply move the index and the branch back to the last commit16:34
icwiener joined16:34
thiago leaving the checkout intact16:34
greyface left16:34
bcardarella joined16:34
withanx would you lose all the data from the last commit, or would they show as modified?16:34
paulboone left16:34
bcardarella Was 'git-svn create-ignore' removed?16:35
thiago the checkout is intact16:35
meaning the files are not modified: they are left exactly as they were committed16:35
bcardarella Because I'm on version 1.5.2.4 of git-svn and I'm getting an error16:36
jpeeler joined16:37
naeu left16:38
Weaselweb bcardarella: "an error" doesn't say anything about your problem, so you have to post your error message to get someone helping you16:39
korpios joined16:40
gitte CURSES the genius that made "mount -o iocharset=iso8859-15" ignore the _explicit!_ option16:40
jpeeler left16:40
jpeeler joined16:41
jpeeler left16:41
bcardarella Weaselweb: good point :p... lemme pastie: http://pastie.org/37742916:41
Circuitsoft Is it possible to plug different diff modules into git?16:41
(filetype-specific diff)16:41
rraasch left16:41
rindolf joined16:42
jpeeler joined16:42
rindolf Hi all.16:42
jpeeler left16:42
Weaselweb bcardarella: that's not an error message, it's the usage message for you how to call git-svn (despite the fact, the actual git-svn command was ommited) indicating, you typed something wrong16:42
rindolf Using git cvsimport - is there any way I can set up an initial date to restrict the import from?16:42
bcardarella Weaselweb: I typed 'git-svn create-ignore' in my repos root directory16:43
chem_ joined16:43
mikearr left16:43
ekidd left16:43
mikearr joined16:43
jpeeler joined16:43
jpeeler left16:43
mithraic joined16:44
jpeeler joined16:44
Weaselweb bcardarella: mh, according to the usage message you posted, you're git version doesn't support "git-svn create-ignore", but i'm not firm with features in specific versions. maybe anotherone may help you here16:45
bgmarete joined16:45
bcardarella Weaselweb: okay, I'll see if I can find a better version... currently I'm on 1.6.0.4 from MacPorts.16:46
agile joined16:46
Weaselweb bcardarella: some minutes ago you said, you're using version 1.5.2.416:46
bcardarella Weaselweb: that's the version of git-svn16:46
If they're both supposed to have the same version number then maybe that's the issue16:47
Weaselweb mh, i would expect they have the same version, but i'm not sure16:47
jpeeler left16:47
ekidd joined16:48
jpeeler joined16:48
jpeeler left16:48
jpeeler joined16:49
jashmenn joined16:49
jpeeler left16:49
chem_ left16:49
bcardarella Weaselweb: yeah, that was the issue. Wrong version of git-svn. Thanks!16:49
Weaselweb you're welcome16:49
fields left16:50
jpeeler joined16:50
plediii left16:50
jpeeler left16:50
rlorandi joined16:51
johan-s joined16:52
jpeeler joined16:52
hurikhan|Work left16:53
rindolf Using git cvsimport - is there any way I can set up an initial date to restrict the import from?16:53
jtimberman left16:54
sgrimm left16:55
Weaselweb rindolf: maybe "-d" from cvsps will help you16:56
rindolf Weaselweb: ah.16:56
qrush_ joined16:57
rafael_lorandi joined16:57
travisjeffery joined16:58
giallu left16:59
moore__ left16:59
ToxicFrog left16:59
chem_ joined17:00
moore__ joined17:00
Kathrin-25^away left17:02
Kathrin-25^away joined17:03
alley_cat joined17:03
chem_ left17:03
foca joined17:05
scientes left17:08
paulboone joined17:08
chem_ joined17:09
ashleyw_ joined17:09
lois[pac] joined17:09
ekidd left17:10
david_koontz joined17:10
scientes joined17:12
jel *sigh* by default, Visual IRC keeps a tiny buffer, and doesn't log.17:12
I was talking to someone earlier about fixing "fatal: bad object HEAD".17:12
Can someone point me in the right direction (and explain what would cause this)?17:13
rlorandi left17:13
cgardner joined17:15
jelmer left17:17
hurikhan|Work joined17:17
_raz_1 joined17:17
_raz_1 left17:18
Hydrogen joined17:18
jelmer joined17:19
Knirch jel: your looking for deskins suggestion?17:19
you're17:19
jel Knirch: yep, that was him.17:19
Knirch: if you have it logged, that'd be great.17:19
(or just remember)17:19
chem_ is away: (automatically dead ) [BX-MsgLog Off]17:20
chem_ is idle, automatically dead [bX(l/on p/off)]17:20
Knirch [14:13] < deskin> my best advice at this point is to run git fsck --lost-found, look through the dangling commits listed with git show <hash>, and when you find the right one, git update-ref refs/heads/master <hash>17:20
jel deskin: don't suppose you're still around?17:20
stepz joined17:20
jel Knirch: thanks :)17:20
deskinm I am, but busy with $work; PM me and I can try to get to it17:21
speakman left17:21
deskinm jel: ^^17:22
sgrimm joined17:22
jel deskinm: no worries, I was rushing earlier and didn't realise your instructions were so complete. That should do, I'll ask the channel in general if I get stuck :)17:22
deskinm: thanks again :)17:22
stepz I'm trying to figure out how to get my existing git repository with linear history into subversion, can anyone recommend how to approach that?17:22
deskinm sure17:22
stepz found a thread in the mailinglist archives that should be a solution, but I can't figure out for the life of me, what I ahve to rebase on what and merge with what17:23
jel git fsck --lost-found shows lots of missing blobs and a few (but still numerable) dangling blobs. Is that normal?17:24
ashleyw left17:24
kevlarman stepz: easiest way is probably to make the first commit by hand (using regular svn), then git svn init, checkout the svn branch, and merge your history (make sure it's a fast forward), then dcommit17:25
mithraic left17:25
bobesponja joined17:26
moore_ joined17:26
stepz how do I merge my history?17:26
kevlarman git merge <branch>17:26
(it might require some rebasing to convince git that the branches share a common history)17:27
moore__ left17:27
stepz that rebasing I'm trying to figure out17:28
the first commit of the git repo and of the empty checkout have nothing in common17:29
halogenandtoast joined17:30
kevlarman it's really an empty checkout?17:30
halogenandtoast what is the difference between git update-index --assume-unchanged and git rm --cached? (and what do they do)17:30
dantrell left17:30
stepz yep, no files in it17:30
kevlarman stepz: could probably use a graft17:31
stepz basically, I suppose I have to something like this: http://gist.github.com/5699417:31
chem_ left17:31
Tv joined17:31
stepz ok, git-graft looks exactly like what I think will work17:33
thanks for the tip17:33
kevlarman stepz: echo $(git rev-parse B) $(git rev-parse a) > .git/info/grafts17:33
plediii joined17:33
kevlarman (and possibly filter-branch to permanently rewrite your history)17:33
softdrink joined17:34
dwave left17:34
tclineks joined17:35
stepz I have to run for now, I'll see if it works tomorrow17:35
fallonetwo joined17:35
stepz thanks for the help17:35
fallonetwo hey folks, how goes it17:35
Kathrin-25^away left17:35
tclineks could someone point me to some resources regarding my git-svn situation described here: http://dpaste.com/115727/ ? i'm looking at http://duncan.mac-vicar.com/blog/archives/282 and http://kerneltrap.org/index.php?q=mailarchive/git/2008/12/14/4416604 wondering if anything else out there would be illuminating17:36
zacharyc joined17:36
Clebrate left17:36
fallonetwo i know with .git/info/excludes you can tell the add process what to skip over... is there a way to say explicitly "only add/check for changes in these files and directories" instead of the reverse, the implicit excluding?17:37
jaeckel left17:38
tclineks fallonetwo: i think you could ignore * then add !(pattern) lines as well17:39
Niamor left17:39
fallonetwo it'd nice to mitigate if my client decides to create a bunch of directories without telling me17:39
Niamor joined17:39
rindolf left17:41
skorpan in git, is the "head" the "latest commit" in a specific branch?17:41
kevlarman skorpan: the current branch specifically (if you're on a branch)17:42
Weiss or for a bare repository, a reference to the branch which will be checked out on a non-bare clone17:43
(i think?)17:43
lisyzavu left17:43
skorpan so it's *the current branch*, not some commit on the current branch?17:44
fallonetwo tclineks: hrmm, do you know of any good docs on the !(pattern) stuff for git exclude?17:44
tclineks using git-svn i was tracking a branch at /foo/branches/bar (cloned with --stdlayout --prefix=svn/ (svnurl)/foo) It was moved to /tmp-foo/branches/bar then /foo/trunk/foo -- wanting to guide git-svn to keep history correctly17:44
qogezil joined17:44
kevlarman skorpan: it's the most recent commit in whatever you have checked out (the current branch, or no branch in the case of a detached HEAD)17:45
skorpan oh, okay. thanks17:45
Weiss skorpan: cat .git/HEAD to see - it's a symbolic reference17:45
or usually is (?)17:46
skorpan yeah, it was17:46
jel left17:47
kevlarman tclineks: i had a similar problem with svn mv, but i ended up just switching to git completely so i can't help17:47
plediii left17:47
tclineks kevlarman: i know it's possible, just having to dive a little deeper than i'd like. might make a good blog post17:47
lucsky joined17:48
lucsky left17:48
Kathrin-25^away joined17:48
qrush__ joined17:51
tal67 left17:52
fallonetwo tclineks: so something like this to ignore all files except the explicitly defined ones? http://pastebin.com/m44aa52d6 i seem to be only getting admin/ and the *.php files there17:56
tclineks !admin/*17:57
probably17:57
fallonetwo ah, i see17:57
keymone joined17:57
kevlarman !admin/ != !/admin/ iirc17:57
keymone hi17:57
can i specify more that one remote for a branch?>17:57
kevlarman if you have the same folders it might match both of them17:57
keymone i just want git pull to sync with few remotes17:58
fallonetwo hrmm, that doesn't seem to work, it just sees the *.php files now17:58
kevlarman keymone: git pull = fetch + merge, and merge tends to fail on non-trivial merges when merging more than one branch17:59
hurikhan|Work left18:00
Niamor left18:01
hurikhan|Work joined18:01
keymone kevlarman: so is it possible? merging can fail anyway..18:02
Niamor joined18:02
fallonetwo is there something i'm missing that needs to go on the end of the !pattern exceptions? i'm not really seeing anything in the man pages18:02
willb left18:07
willb joined18:07
drizzd_ joined18:07
leachim6 left18:08
softdrink left18:08
plediii joined18:09
halogenandtoast left18:10
leachim6 joined18:10
hdl2 left18:12
wwalker joined18:12
qrush_ left18:13
wwalker I used to use git diff to see the changes in my local files, but I just did and it returns nothing. I have recently run git -add -u. Does that make git not see any differences? If so, how do I get git to show me the diff between current state and last committed?18:13
jmesnil left18:13
PerlJam wwalker: sounds like you want git diff --staged18:14
fallonetwo left18:14
wwalker PerlJam: thank you18:15
lebreeze joined18:17
wwalker PerlJam: --cached was what I was looking for (found by searching the git-add man page for stage :)18:17
thanks18:17
cedricv left18:18
moore_ wwalker: --cached diffs between the index and a named commit.18:19
cedricv joined18:20
wwalker moore_: or HEAD if nothing given, which is the behavior I need. I have staged the commit but then wanted to review the changes I was about to commit (I know I should have done that before I ran git add -u, but...)18:20
nick125_ joined18:21
lebreeze left18:21
PerlJam wwalker: --cached and --staged are synonyms18:21
muthu_ left18:21
Kathrin-25^away left18:21
Kathrin-25^away joined18:21
daaku joined18:21
muthu_ joined18:21
Jc2k joined18:22
ToxicFrog joined18:22
bcardarella left18:23
dmlloyd left18:23
fynn joined18:23
hyperbor1ean joined18:23
jashmenn_ joined18:24
ceej joined18:25
wwalker PerlJam: my version (1.5.5.1) says --staged is invalid option18:25
dmlloyd joined18:25
drizzd left18:25
daaku left18:26
jashmenn left18:26
bdiego left18:26
cthompson left18:26
tanek left18:26
Eridius left18:26
alexkane left18:26
hyperboreean left18:26
pogma joined18:26
Leonidas joined18:26
willb left18:27
thiago_home joined18:27
Fearliss joined18:28
canidae is there some magic trick to clone a --bare repository over http? it looks for /info/refs, but that does not appear to exist in --bare repos18:28
willb joined18:29
andreaja joined18:29
Tv left18:29
pinholecamera hrmm, still not having luck with those !pattern exceptions, there must be something simple i'm missing18:30
nick_h[litage] joined18:30
hyperbor1ean left18:30
Hydrogen left18:30
qogezil left18:31
harinath left18:31
qelyrupaz joined18:31
hyperboreean joined18:31
thiago_home canidae: did you run the command you need to run for http serving to work?18:33
git update-server-info18:33
canidae argh, i always forget that one18:33
thanks18:34
Kbyte left18:34
fonseca tokkee: The problem you have was fixed in http://repo.or.cz/w/tig.git?a=commit;h=495fd0788ecb4aeda6ee3b47fbfc000f7036894818:35
tokkee: I will release a tig-0.14 with many regression fixes one of the coming days18:36
rafael_lorandi left18:36
lorandi joined18:37
pinholecamera is there some kind of delimeter at the end of the !pattern excludes?18:37
qelyrupaz left18:37
drobbins joined18:38
drobbins is it normal for "git am" to choke on certain mail headers and abort?18:38
and is there any way to deal with this issue?18:38
leqy joined18:38
cmarques left18:39
Kathrin-25^away left18:40
plediii left18:40
Kathrin-25^away joined18:40
WALoeIII joined18:42
torarne joined18:43
krawek_ joined18:43
daaku joined18:43
bdiego joined18:43
cthompson joined18:43
tanek joined18:43
Eridius joined18:43
alexkane joined18:43
japhb joined18:43
dkr21 joined18:43
Kudos_ joined18:43
jim_c joined18:43
Fissure joined18:43
Toad joined18:43
dirker joined18:43
Toad__ joined18:45
w00t joined18:45
lorandi left18:46
lorandi joined18:46
mick_laptop left18:47
Sigma joined18:51
ceej_ joined18:51
skorpan left18:51
dirker left18:51
Fissure left18:51
dkr21 left18:51
jim_c left18:51
cthompson left18:51
japhb left18:51
Kudos_ left18:51
daaku left18:51
Toad left18:51
alexkane left18:51
tanek left18:51
bdiego left18:51
Eridius left18:51
knitt1 joined18:55
knitt1 hi! how can i add a second root-commit?18:55
drizzd_ knitt1: git symbolic-ref HEAD newroot18:55
or simply "git remote add" of an unrelated repository18:56
icwiener left18:56
icwiener joined18:56
purestorm joined18:57
Thargor left18:57
purestorm Can someone point me to a resource explaining how git svn rebase could ever fail when importing a new repository?18:57
knitt1 drizzd_: thanks. i know i can pull another repo, but i wanted to do it in-place18:59
drizzd_ purestorm: I'm not a git-svn user, but that sounds awfully vague18:59
dkerschn1r joined19:00
Thargor joined19:00
parasti purestorm: rebase can't work in an empty repository with nothing checked out. you want either git svn clone or git svn fetch19:00
moore_ left19:00
japhb joined19:00
moore_ joined19:01
purestorm parasti: I have an empty svn repository with only trunk/tags/branches directories. I want to import my git stuff into that svn repository. How could rebase fail? The local patches should be conflict-less, should they not be? I'm trying to understand what's going on here...19:01
Kudos joined19:01
daaku joined19:02
bdiego joined19:02
cthompson joined19:02
tanek joined19:02
Eridius joined19:02
alexkane joined19:02
dkr21 joined19:02
Kudos_ joined19:02
jim_c joined19:02
Fissure joined19:02
dirker joined19:02
krawek left19:02
ahupp|fb joined19:03
rindolf joined19:04
rindolf Hi all.19:04
parasti purestorm: ok, then I misunderstood what you were doing19:04
rindolf git cvsimport -d :pserver:anoncvs@sourceware.org:/cvs/src/ -p -d,2009-01-01 gdb seems to be stuck at {{ cvs rlog: Logging src/etc }}. What can I do?19:04
Thargor left19:04
purestorm parasti: Do you have an idea?19:04
parasti purestorm: like drizzd_ says, you'll have to provide more details... what you want to do, what commands you used, and what errors you got19:06
leqy left19:06
ceej left19:07
dkr21_ joined19:07
purestorm OK, sorry, I have to run. Evidently, this would take some time to understand :) Thanks, though.19:07
purestorm left19:07
jaalto joined19:07
nirihy joined19:07
bentob0x left19:07
Tv joined19:08
Toad__Toad19:10
name left19:10
name joined19:11
mutex hmmm19:11
Kudos_ left19:11
dkr21 left19:11
jim_c left19:11
daaku left19:11
mutex how do i extract a patchset for applying to a source tree ?19:11
git-format-patch creates everything in email format19:11
thiago_home that's it19:12
gitte mutex: Have you found the "git diff" command yet?19:12
rindolf left19:12
thiago_home mutex: the email format is the second best format available19:13
Thargor joined19:13
mutex gitte: yes of course, but maybe I have missed something19:13
because I can't seem to get it to produce proper merge commit diffs19:13
moore_ left19:13
warthog9 joined19:13
gitte mutex: how should that go? A diff for a _merge_? Render me puzzled.19:14
moore_ joined19:14
lorandi left19:15
rlorandi joined19:15
gitte thinks that somebody fell in love with a horrible name: "primer"19:16
canidae how "dangerous" is it to set up a repository with --enable=receive-pack? eg. can that completely ruin a repo?19:16
s/that/someone/19:17
dirker left19:17
Fissure left19:17
cthompson left19:17
alexkane left19:17
tanek left19:17
bdiego left19:17
Eridius left19:17
krh 5~19:17
gitte canidae: you mean git daemon?19:17
canidae yeah19:17
libc__libc19:17
canidae s/set up/share/ :)19:17
gitte canidae: you might have said that right away...19:17
bdiego joined19:17
cthompson joined19:17
tanek joined19:17
Eridius joined19:17
alexkane joined19:17
Fissure joined19:17
dirker joined19:17
gitte canidae: I can wreck your whole work if you let me push to your git daemon.19:18
bdiego left19:18
gitte canidae: I can introduce backdoors, viruses, you name it.19:18
canidae: I can create fake branches, make up committer names, fake work in your name.19:18
canidae: and I can delete everything.19:18
tanek__ joined19:18
nirihy left19:18
canidae that sounds about my definition of "dangerous"19:19
gitte canidae: so... "dangerous"? For some interpretations of "dangerous", the answer is "yes, absolutely".19:19
canidae: you should have known that before asking, though, as you'd allow write permissions without authentication.19:19
nyzaquvoc joined19:19
bdiego joined19:20
canidae basically i'd like to set up a repo <anonymous> can push to, and rather let me pick the stuff i want. sending them patches per mail has proven less than efficient19:20
ice799 joined19:21
gitte canidae: why don't you set up a repository on repo.or.cz and initialize the "mob" branch?19:21
mansour I don't understand when do I need to create repo with the --bare option. One site says, it's for repo without working directory. What does that mean? can someone explain ?19:21
bdiego left19:22
gitte mansour: you had any exposure to Subversion or something like that?19:22
canidae i guess i could do that, yeh19:22
mansour yes, I did sirk with SVN for a while.19:23
but all from eclipse19:23
gitte mansour: so you know what a working directory is.19:23
mansour I did work with SVN19:23
mithraic joined19:24
mansour well, my understanding it's the dir holding the main project19:24
nyzaquvoc left19:24
helo_ joined19:24
mansour gitte: am I right ?19:24
gitte mansour: close. It only holds a particular revision of your project.19:24
tuqagiw joined19:25
gitte mansour: to get another revision into your working directory, you have to ask the repository, right?19:25
mansour hum, ... ok ? so what is the deffrence between working and none working then ?19:25
yeah, u r right ?19:25
tuqagiw left19:25
mansour yep true19:25
johan-s left19:25
mansour how does this compare to "none-working" dir ?19:26
gitte mansour: with Git, the repository happens to be much more closely coupled to the working directory, it does not sit on a remote server, but in a subdirectory named .git/ (at least that is the common case).19:26
reli joined19:26
gitte mansour: for some applications, you do not need a working directory, it can even be undesirable, as with a "public" repository people can clone.19:27
mansour Ok, I see what u mean ? yes, when I create it with --bare, it has lots of files19:27
gitte mansour: there, you do not want any working directory, as the repository _already_ contains all the revisions, and you want people to clone it, not inspect a working directory.19:27
simosx_ joined19:27
gitte mansour: no, that is not it. If you create it with --bare, you do not have a .git/ subdirectory holding the repository.19:28
mansour: instead, you have the contents of the repository right there, in your current directory.19:28
mansour ok, let me make sure I understand.19:28
gitte mansour: because you asked not to have any working directory, the repository can live there.19:28
mansour I C.19:28
helo_ i comitted a new file, made some changes, did a "git stash" and then did a "git checkout HEAD~3"... then i did a "git unstash", wanting to switch back to the latest commit, so did "git checkout HEAD", but the file i stashed was pulled into my (branchless) HEAD~319:29
mithraic left19:29
dirker left19:29
Fissure left19:29
cthompson left19:29
alexkane left19:29
tanek left19:29
Eridius left19:29
helo_ and apparently it wants me to merge the new file before changing branches... i'd rather just leave HEAD~3 untouched...19:29
mansour So, when I create it with bare it has no project structure (dir heirarichy). When without bare, it greates the repo in .git. I noticed they are the same structure.19:29
I mean .git and the repo --bare19:30
I C now19:30
but here's the catch.19:30
rubydiamond left19:30
mansour gitte an I right up to here ?19:30
gitte mansour: I am waiting for the "catch".19:31
mansour ok,19:31
plasticine joined19:31
mithraic joined19:31
mansour now, I created a project , and did "git init", then If i need to put it where athers can see it, then I need to push only what ?? .git ??19:32
gitte thinks that jidanni definitely has way too much time on his hands, but does not use it for useful stuff.19:32
gitte mansour: umm. How do you want to push _directories_?19:32
doener gitte: but apparently he got a crystal ball ;-)19:32
muthu_ left19:33
mansour I created, a project and it was cool "assume, it never really happened". And I want to put it on my remote repo19:33
gammons joined19:33
gitte doener: he has mushrooms, cooked to a nice mash, where I have the organ using 25% of my oxygen intake.19:33
mansour do I just copy .git with ssh to the server ?19:33
gitte mansour: I suggest reading up on "publishing your work" or some such in the Git manual.19:34
ceyusa left19:34
mansour ok, I will. thank you.19:34
You answered the main question I have, and I can dig further now. thak you gitte19:34
gammons Hey I have a (hopefully not too n00b) question. I have a local branch, called local/release, and on my origin server, I have a branch called origin/release. I'd like to push the changes I made in my local branch to the remote branch. I've been calling 'git push origin release', but the changes don't seem to be making it to the remote branch. Anything obvious I am doing wrong?19:34
agib joined19:36
nick_h[litage] left19:36
helo_ where can i find out what "* Unmerged path somefile.cpp" when i try to "git stash pop" means?19:36
thiago_home helo_: it means there was a conflict19:37
gitte gammons: yes, you should rename your branch to "release" with "git branch -m local/release release". No need for an extra hierarchy for local branches.19:37
helo_: just look for "<<<<<<" in somefile.cpp.19:38
gammons gitte: hah! that worked! thanks a log19:39
s/log/lot19:39
actually log is funnier19:39
henry_kleynhans joined19:41
ph^_ph^19:41
resmo joined19:43
simosx left19:43
charon left19:45
eddyp joined19:47
ahupp|fb_ joined19:49
mikl left19:49
cgardner left19:50
qrush__ left19:51
ashleyw_ left19:52
felipec joined19:54
plasticine left19:57
korpios left19:57
krawek__ joined19:57
henry_kleynhans left19:59
sdboyer-laptop joined19:59
bryanl left20:02
hurikhan|Work left20:03
LotR left20:04
hurikhan|Work joined20:05
sdboyer-laptop left20:07
NSaibot joined20:08
shapeshed joined20:10
ahupp|fb left20:10
plediii joined20:10
gammons left20:11
bryanl joined20:12
scientes left20:13
rwaite left20:13
plediii left20:13
krawek_ left20:14
earcar joined20:14
plediii joined20:14
hurikhan|Work left20:16
mansour gitte, u there ?20:16
gitte Sort of.20:17
hurikhan|Work joined20:17
cgardner joined20:17
rlorandi left20:17
mansour cool, I looked around and couldn't find a clear doc that gives me what I want.20:17
dramsay joined20:17
mansour again, I created a project and decided to put it on a remote, pushing doesn't work as there's no repo on the remote yet. So do I create it with --bare on the server, or do I just copy ".git" dir20:18
?20:18
charon joined20:18
bieneff joined20:18
ahupp|fb_ left20:19
thumper left20:20
foca_ joined20:21
thumper joined20:21
gitte mansour: create it with --bare.20:23
acoc if I git mv a file, does the new file retain the history of the previous file20:23
gitte mansour: or use one of the many providers that make it easy for you.20:24
acoc: history in Git is revision-based, not file-based, so your question does not make full sense to me.20:24
simosx_simosx20:24
nick_h[litage] joined20:25
dirker joined20:25
cthompson joined20:25
tanek joined20:25
Eridius joined20:25
alexkane joined20:25
Fissure joined20:25
bgmarete left20:25
hurikhan|Work left20:25
acoc gitte, if I were to do a git log of the new file, would it contain the previous commits or only the last one that moved it20:25
mansour I C, gitte thank you, I will20:26
gitte acoc: huh? If you commit the result, the parent commit of the new one will be the current HEAD, so I really do not get your question. What's it with the files?20:26
Marmouset joined20:27
acoc gitte, if you were doing a diff of that new file from an older revision, would it be able to see that it's location changed an compare it to the file as it was in it's origional location20:28
ahupp|fb joined20:29
krh acoc: yes, use git log --follow (and don't mind gitte, he's being deliberately obtuse ;)20:29
MarcWeber gitte: I think acoc means: When renaming a file is there a command to conviniently follow the renamings to get all patches containing that file?20:29
I've checked, qgit does'nt recognize this20:29
gitteobtuse-gitte20:29
kevlarman -M?20:30
foca left20:31
jashmenn_ left20:31
acoc krh, thanks that was helpful20:34
docwhat joined20:34
canidae uh. someone got "user.name=Foo Bar", although in logs it just show "Foo". he's using cygwin, anyone heard about this before?20:36
Ratler_Ratler20:37
robinr joined20:38
dreiss joined20:39
obtuse-gitte canidae: it's probably even unquoted, right?20:40
canidae: so make sure that "Foo Bar" is quoted in .git/config20:41
canidae aight, we can try that20:41
plediii left20:41
ijcd joined20:42
ephebo joined20:43
canidae didn't help :(20:44
johnw joined20:44
Tuomas left20:45
vuf left20:46
mczepiel joined20:46
mczepiel left20:46
jrmuizel left20:46
jrmuizel joined20:47
qrush_ joined20:48
ekidd joined20:48
plediii joined20:48
johnw left20:49
obtuse-gitte canidae: recorded commits will not change...20:49
canidae he tried new commits20:50
or so he said, but he ran off now. i'll check that again when he gets back (which may take some hours)20:50
obtuse-gitte Check if "git var -l" shows the correct name.20:50
canidae thanks for the help, though :)20:50
obtuse-gitte runs off, too20:51
obtuse-gitte left20:51
HanLecter joined20:55
MarcWeber left20:55
earcar_ joined20:56
GlycaDS joined20:58
jasber joined20:58
travisjeffery left20:59
kraymer_ left20:59
GlycaDS left21:00
Kathrin-25^away left21:00
drobbins what is the best way to figure out why I can't push (a non-fast-forward merge)?21:01
eddyp I have multiple branches and two remotes; I want that push to one of the remotes to push two branches and the other to push just one; how do I configure th elocal repo to specify the to branches I want pushed for remote 1?21:01
Kathrin-25^away joined21:01
doener drobbins: I like "gitk --left-right local...remote"21:01
earcar_ left21:02
drobbins doener: I just merged some changes in, but I don't understand why this broke things.21:02
eddyp the remotes are origin and puorcz21:02
puborcz21:02
drobbins doener: how about on cmdline?21:02
doener eddyp: set remote.origin.push and remote.purocz.push21:02
eddyp puborcz is the one which I want to contain two branches21:02
drobbins doener: just applied some patches and did a merge, not sure why it's not a basic "here are some recent commits.."21:03
eddyp doener: I figured out that part, but how do I specify the two refspecs for puborcz?21:03
doener drobbins: same deal. Though I'd probably just use "local..master" (two dots) with git log21:03
drobbins doener: maybe it's due to some of the commits being chronologically earlier21:03
doener drobbins: telling the left and right side apart in the text log isn't something my brain likes21:03
drobbins ok, maybe I just need to pull and figured it was trickier than it really was.21:04
doener drobbins: the log command then tells you what's missing from the local branch21:04
drobbins looks like I'm missing a commit that is upstream, that I pushed from another box.21:04
doener: excellent21:04
doener: while I have you here....21:04
doener: I've been getting inline patches in emails...21:04
eddyp doener: now I have : "refs/heads/mob:refs/heads/mob", but I can't figure out the format to add the master, too21:04
doener eddyp: add a second remote.<whatever>.push line21:05
eddyp: if you use "git config", use the --add option21:05
drobbins: save as mbox/maildir, feed to "git am"21:06
eddyp doener: that was the missing bit, thanks21:06
drobbins doener: see, I did that... and it said that it was an invalid patch or some such thing, error on line 28 or thereabouts (unfortunately don't have the error in front of me right now)21:06
keystr0k joined21:06
drobbins doener: are my submitters generating these patches the wrong way if I'm getting that error?21:07
doener ah, the header thing, saw that while flying through my scrollback21:07
drobbins yep21:07
dmlloyd left21:07
doener hard to tell without the email at hand, at least for me21:08
dmlloyd joined21:08
doener I don't recall hearing of such problems caused by headers. The mail body, yes, but not headers.21:09
plediii_ joined21:09
earcar left21:14
markelikalderon left21:14
joevano joined21:14
drobbins left21:15
drobbins joined21:15
drobbins left21:18
Voker57 left21:19
esparkman left21:19
drobbins joined21:19
cmarcelo left21:19
Voker57 joined21:20
cmarcelo joined21:20
Murr joined21:23
derwolf left21:25
esparkman joined21:26
cmarcelo left21:28
seezer left21:32
warthog9 left21:32
warthog9 joined21:33
seezer joined21:33
keystr0k I've been working on a branch... can I pull into my master without merging, just automatically assume the branch is the version of the file(s) I want.21:36
?21:36
ia left21:36
keystr0k I guess I need my master branch to look exactly like my "testing" branch.21:36
jayne there is an "ours" merge strategy21:37
ia joined21:37
drizzd_ keystr0k: if you don't want your local changes, I'd just throw them away and create a new branch based on the remote master21:37
pierre- left21:37
bradly joined21:38
keystr0k drizzd_, well, all of the data/branches are local... It's just a repo on my local machine. I made changes to branch X and I need to make sure master looks just like branch X.21:38
plediii left21:39
drobbins doener: had to reboot due to keyboard not responding21:39
doener: I have a paste for you21:39
doener: this is what I am experiencing: http://www.privatepaste.com/16Y3Yrw2Sl21:39
doener and line 34 is?21:40
drobbins doener: those patches were saved by mutt into a maildir21:40
drizzd_ keystr0k: git checkout master; git reset --hard X;21:40
keystr0k drizzd_, aaaah.21:40
drobbins doener: one moment.21:40
keystr0k drizzd_, thanks. that looks good.21:40
johnw joined21:40
keystr0k I knew about git reset hard but I didn't know you could reference a different branch.21:41
resmo left21:41
drizzd_ keystr0k: if X was based on master, git merge X would do the trick too (that's the normal mode of operation)21:41
drobbins doener: http://www.privatepaste.com/e40rBMLy7b see line 34 (I'm assuming it means line 34 from the top of the mail header)21:42
keystr0k drizzd_, okay... yeah, it is based on master... I'll do a normal merge and if the results aren't desired I'll try the other method.21:42
torarne left21:44
priidu_ left21:45
metze_awaymetze21:45
GeertB left21:46
drobbins doener: any ideas? does it look like a git bug of some kind?21:47
doener drobbins: no, seems to skip the header before starting to count the lines21:47
drobbins ok21:47
let me get the patch body then.21:47
doener hm, or maybe not21:48
doener is confused right now21:48
drobbins hrm.21:48
doener I shouldn't mess with my terminal colors while working21:48
black cursor on black background just doesn't work21:48
drobbins maybe mutt is word-wrapping the inline attachment before it saves it.21:48
I notice that everything is word-wrapped so that it meets the standard 78 or so column limit21:49
stevecrozz joined21:50
doener using "s" or "C" in mutt? never seen that messing with my mails21:50
stevecrozz can someone please help me troubleshoot this error: warning: remote HEAD refers to nonexistent ref, unable to checkout.21:50
Dvyjones left21:50
stevecrozz I've published a git repository over http, and I can't get 'git clone' to work with it21:50
drobbins doener: looks like it's word-wrapping.21:51
doener: I'm assuming that the patch can't be word-wrapped or it b0rks git, understandably.21:52
doener The header on line 11, 12 looks funny21:52
though that's far mor than 78 chars21:52
docwhat left21:53
Catfish left21:54
Weaselweb left21:54
stevecrozz "error: warning: remote HEAD refers to nonexistent ref, unable to checkout." -- how do we fix this ?21:54
doener drobbins: btw, which git version is that?21:54
RandalSchwartz stevecrozz - fix the remote head. :)21:55
drobbins doener: 1.6.1.2 and 1.6.1.021:55
stevecrozz thanks RandalSchwartz... but how?21:55
RandalSchwartz is it a bare repo?21:55
stevecrozz no, its got an initial commit21:55
RandalSchwartz no - bare means "does it have a working tree"21:56
stevecrozz i was able to do: "git push upload master" from my project repo21:56
RandalSchwartz err. the opposite of that21:56
stevecrozz that worked21:56
cubuanic joined21:56
RandalSchwartz waits for bare vs non-bare to be answered21:56
doener did you run "git update-server-info" after the push?21:56
stevecrozz I'm very new to git... I'm not sure how to answer the question21:57
RandalSchwartz that's not needed if it's bare21:57
stevecrozz not i didn't run that21:57
RandalSchwartz stevecrozz... is there a "checkout"?21:57
doener RandalSchwartz: hm? That's always required for http21:57
RandalSchwartz local files besides just the .git?21:57
oh - didn't realize this was http21:57
when did he say that?21:57
stevecrozz i started a project here, built a git repo, then uploaded it to my web server....21:57
RandalSchwartz scrolls back21:57
doener about 7 minutes ago21:57
RandalSchwartz ok, missed that21:58
then yes, you need the update-server-info step21:58
but eventually, you should get away from http transport21:58
drobbins doener: did some research, and it appears to be an issue with the email as sent out by the upstream developer.21:58
doener drobbins: mind bouncing that to me?21:58
stevecrozz RandalSchwartz: this is a brand new project... i can move away now if need be21:58
you prefer git:// ?21:59
markelikalderon joined21:59
drobbins doener: the email? sure, what's your addy?21:59
doener [email@hidden.address]21:59
RandalSchwartz you make it sound like it's me personally that prefers it. :)21:59
but yes, for best functionality, you want git-over-ssh protocol21:59
abbe joined21:59
RandalSchwartz that's what everthing is optimized for22:00
stevecrozz hmmm.. i want to avoid creating shell accounts for everyone who needs to use the git repo....22:00
RandalSchwartz isn't that what gitosis is about?22:00
agenteo joined22:00
stevecrozz i have no idea... im a super noob, is it?22:01
RandalSchwartz ... http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way22:01
that might be outdated22:01
but it says what I was about to say22:01
stevecrozz ok22:01
RandalSchwartz ... It manages multiple repositories under one user account, using SSH keys to identify users. However, users do *not* need shell accounts on the server, instead they will talk to one shared account that does not allow arbitrary commands22:01
doener stevecrozz: for read-only access git:// using the daemon is fine. For push, you'll want ssh, maybe in combination with gitosis or similar things22:02
stevecrozz ok..22:02
RoPP joined22:03
drobbins doener: gimme a few mins and I'll get it out to you22:04
doener no need to hurry22:04
ekidd left22:04
drobbins just need to pretend22:04
(that I'm hurrying) - so I don't forget :)22:04
doener heh, I know how that works :-)22:05
stevecrozz hmm gitosis has an ubuntu package in the official repo22:05
ill try it22:05
cemerick left22:05
Murr left22:07
Murr joined22:07
dwmw2dwmw2_gone22:08
dwave joined22:09
jesselucas left22:11
esparkman left22:13
ferdy left22:14
markelikalderon left22:14
drobbins doener: bounced. and I found out that the patch was sent via kmail, which could explain the mangling.22:14
charon left22:14
cannonball left22:15
ferdy joined22:15
doener drobbins: yep, the patch definitely looks broken, just from the huge context in the first hunk22:15
drobbins doener: ok, cool, good to know. thank you for your help.22:16
robinr left22:16
vbabiy left22:17
doener xenoterracide: there's a section about sending patches with KMail in Documentation/SubmittingPatches22:17
shapeshed left22:17
xenoterracide doener: interesting but I've a more interesting issue now (don't know that I like kmail anywho22:17
tanek__ left22:18
doener drobbins: hm, maybe you meant gmail?22:18
bieneff left22:18
xenoterracide git format-patch -1 ea11098821f1495bd499e6926dd3a4232da839b7 --stdout -M funtoo/funtoo.org I'm trying that... but the patch being sent is this one d9aefeeb which happens to be the latest head on funtoo/funtoo.org, maybe I've missed something?22:19
metzemetze_away22:19
doener xenoterracide: you're passing two commits to format-patch22:20
xenoterracide: -1 limits it to the most recent one22:20
xenoterracide: just drop the funtoo/funtoo.org at the end22:21
xenoterracide ah22:21
bryanl left22:21
doener and if you want multiple single commits, use --no-walk instead of -122:22
drobbins sounds like we need a HOWTO for format-patch submissions22:22
Hydrogen joined22:22
doener basically, format-patch works like "log", with one exception, if you give just a single commit (and no -1, --no-walk or whatever), it defaults to $commit..22:23
so "git format-patch foo" and "git log foo" differ, the former is like "git log foo.." (WRT the commit range it operates on)22:24
dwave left22:24
Flathead joined22:24
doener but "git format-patch foo..bar" and "git log foo..bar" work on the same commits22:25
NSaibot left22:25
drobbins will test in a bit.22:27
mark[oz] joined22:27
xenoterracide doener: hmm... can't find -1 in the man page22:28
or no-walk22:29
bobmcw left22:29
radarek left22:29
stevecrozz left22:29
doener --no-walk is in the rev-list man page, -1 would be -n 1 if one wasn't lazy22:30
cbrakecbrake_away22:30
xenoterracide doener: why does the SubmittingPatches guide (for git) tell you to use the remote-branch?22:30
doener -n is also in the rev-list man page22:30
xenoterracide be nice if they were in the format-patch man page22:30
since that's the command I'm running22:30
doener xenoterracide: then the whole rev-list man page would be in there... and the diff manpage as well22:31
would be slight overkill22:31
xenoterracide yeah I suppose22:32
foca_ left22:32
xenoterracide doener: at least I know where to look now22:32
doener xenoterracide: it uses origin/master because it then operates on origin/master.. == origin/master..HEAD ==> all commits in the history of the checked out commit that aren't in upstream22:32
it's just a shortcut22:33
kansan i forked a git project. now im within my checkout dir ... and i want to pull the commits from the mainline of the project (not my forked version).... how can i do this?22:33
i forked via github that is22:33
doener kansan: add the mainline repo as a remote (git remote add <name> <url>)22:33
Ryback_ left22:33
DrNick git remote add -f mainline git://mainline22:33
aroben joined22:34
purestorm joined22:35
kansan ok i did that22:36
now what do i do22:36
doener with -f or without?22:36
purestorm Hi, so back to my issue. I have a git repository and now I want to use a subversion repository as the central server. I found this how-to: http://code.google.com/p/support/wiki/ImportingFromGit. Now, I get conflicts on git svn rebase and I do not understand how this could happen, my git repository contains a linearized of patches, right?22:37
mcella left22:37
mark[oz] left22:38
perezd88 joined22:39
mark[oz] joined22:39
Phlogi left22:40
dmq joined22:42
dmq wonders if its a bug that git diff -w doesnt ignore missing newline at eof.22:43
keystr0k left22:43
bdiego joined22:43
rogg joined22:43
johnw dmq: sounds ilke it tome22:43
mcella joined22:46
mcella left22:46
felipec left22:47
Kathrin-25^away left22:48
Kathrin-25^away joined22:49
kansan say i have a git repo that has in the root: foo/ ... now i decide i want to yoink out foo and put it in a brand new repo where its root. can i do this?22:49
aroben left22:49
sjzzalx joined22:50
krawek joined22:50
sjzzalx Hi all. When I try to git svn clone, I get http://pastebin.com/m6fe99d5a on password prompt. I don't like this. Anyone know how to fix it?22:50
aroben joined22:52
dmq that looks like you have a slightly broken perl install actually.22:52
you need to install the perl Term::Readkey module somehow.22:52
esparkman joined22:52
sjzzalx dmq: Ok, awesome, thanks. : )22:53
dmq its a little weird tho, as afair that module should be around already.22:53
chuck joined22:54
dmq unless your vendor has shipped a broken perl.22:54
chuck hey, i've got a rather complex problem, but I figure i'll ask, as git might be able to do it22:54
dmq oh, no, wait, im wrong.22:54
its not a core module.22:55
but i you do need to install it.22:55
chuck I want to write a fork of something that is using SVN, and trunk/ is always ready-to-run, so I want to use the latest SVN. how would I go about doing that in git so I could easily merge in the latest changes upstream?22:55
EiNZTEiN left22:56
dmq ah right, Term::ReadLine is core.22:56
since 5.00222:57
lordpil- joined22:57
Marmouset chuck, cannot you use git-svn ?22:57
chuck Marmouset: would that work for this?22:57
sjzzalx dmq, thanks, I got it installed and that problem's gone now actually. But now I get error: More than one value for the key svn-remote.svn.fetch: :refs/remotes/git-svn22:57
. :( brb, gotta restart pidgin22:57
sjzzalx left22:57
chuck I have no idea what git-svn is all about, but I'm open to try it22:57
bantic left22:57
sjzzalx joined22:57
flaguy48 joined22:58
Marmouset chuck, git-svn enables you to create a git repo from a svn one. try git-svn clone followed bu the depot svn utl22:58
url22:58
dmq that part i cant really help with sjzzalx.22:58
Marmouset From the man page : git-svn - Bidirectional operation between a single Subversion branch and git22:58
Weasel[DK] left22:58
Marmouset chuck, I use that to track svn repos22:58
chuck Marmouset: would that be able to have the upstream code in a branch of something so I can merge22:59
sjzzalx dmq, I see, thanks.22:59
krawek__ left22:59
dmq im kinda curious why git svn is using Term::ReadKey and not Term::ReadLine.23:00
:-)23:00
aroben_ joined23:00
sjzzalx left23:01
sjzzalx joined23:01
Marmouset chuck, you get a git repo. So you do whatever git let you do :)23:01
SRabbelier left23:02
chuck so would I do something like: git svn clone http://whatever/svnroot/whatever23:02
then make a branch for my fork?23:02
that seems backwards23:02
Marmouset git-svn not git svn23:02
chuck maybe I can use git pull?23:02
yeah w/e23:03
Marmouset check git-svn options23:03
you can tell it what is the branch/trunk/tag directory and so on23:03
LotR joined23:05
Voker57 left23:05
markelikalderon joined23:08
reli left23:10
Murr left23:11
EmilMedve left23:11
solydzajs left23:13
lordpil left23:13
pathall joined23:14
jmspeex left23:14
pathall hi, i would like to merge several repos under an umbrella repo. so i have app1, ... app5, and i want to create umbrella/{app1,...app10} . what command should i be looking at?23:14
oops, s/5/10/ :)23:15
vbabiy joined23:15
aroben left23:17
a-priori joined23:17
purestorm How could a git rebase from an external repository to an empty repository fail? I thought that a repository contained conflict-free patches.23:18
klmann pathall: this is how i did it: go to the repos app1...5 and move the root content into a new created direcotry (mkdir app_n; git mv * app_n). then merge the repositories to the umbrella-repo23:18
Ariens joined23:19
qrush__ joined23:19
helo_ left23:19
vomjom purestorm, i don't even think it makes sense to rebase there23:20
maybe you misunderstand what rebase does?23:20
purestorm I have to :/ it is a svn repository.23:20
qrush_ left23:20
purestorm Or I am understanding something wrong.23:20
I have a git repository23:20
pathall klmann: ah good idea, thanks23:20
aroben_ left23:21
purestorm and now I want to push everything to a subversion repository following http://code.google.com/p/support/wiki/ImportingFromGit23:21
vomjom purestorm, did you do svn clone?23:21
klmann pathall: but i have to warn you. i moved from svn to git and i had this idea of one umbrella-repo too, but it showed that it is not as flesible as multiple git repositories23:22
*flexible23:22
pathall klmann: i just want to squeeze a bunch of stuff under one app on github because of the private app limit23:22
vomjom http://gitready.com/intermediate/2009/01/31/intro-to-rebase.html <--- this is a good explanation of what rebase does by the way23:22
urbanmonk joined23:22
purestorm vomjom: https://gist.github.com/801115105eaeeaf3c01823:22
klmann pathall: all right, then its ok ;)23:23
RandalSchwartz oof - what an evil web page23:23
vomjom purestorm, is that what you did?23:23
purestorm vomjom: The paste, yes.23:23
and it fails23:24
RandalSchwartz why do people think it's cute to change the annotations for "this is a link" to something really unfamiliar23:24
vomjom purestorm, sorry, no idea why it's failing then. what message are you getting?23:24
purestorm error: patch failed: Sequential/SConscript:123:25
error: Sequential/SConscript: patch does not apply23:25
Hrm, this could be linked to a merge later on...23:25
fejo joined23:26
purestorm or a branch23:26
hm, is it possible to rebase something back in time to something back in time?23:26
sjzzalx purestorm, git reset?23:27
LotR left23:27
sjzzalx not sure if it does everything you want but it will put your repo back to an old commit23:27
krawek_ joined23:30
radarek joined23:30
purestorm hrm, OK23:30
Well, I'll resolve it by hand then.23:31
Thanks, nevertheless.23:31
Sigma left23:32
chuck oh good god, git-svn clone downloads every single revision T^T23:33
a-priori left23:33
klmann chuck: yeah, it actually does what it says ;)23:33
pathall hmm, klmann, what if i just cloned the dirs without making the subdirectory? like, git clone /home/blah/app1/.git /home/blah/umbrella/app123:33
chuck klmann: how do I grab the latest revision? xD23:33
klmann pathall: you would not have the history of the imported repository in the main repo23:34
pathall: ... i think. actually, i didnt try it23:34
pathall klmann: oh, clone doesn't keep the history?23:34
klmann klmann: man git-svn. i dont know the command23:34
Gitbot klmann: the git-svn manpage can be found at http://git.or.cz/man/git-svn23:34
klmann chuck: yes, but it does not merge the hostory in the umbrella-repo23:35
pathall: so if you use git log in the umbrella-repository, you will not see the changes in the other repositories23:35
chuck klmann: how do I just grab the latest code23:35
pathall klmann: yep, you're right, just checked that. thx23:35
alley_cat left23:35
klmann chuck: i dont know23:36
boto left23:36
chuck .-.23:36
Guest58011 joined23:37
Guest58011 Hello everyone. quick question: I have 2 local repos I want to merge.. can I do this? checkout a branch or tag from a diff local repo?23:38
tvw joined23:38
aroben joined23:38
shd Guest58011: git pull /path/to/other/repo23:39
Guest58011 and I can point to a SHA1 in that repo correct?23:39
or tag?23:39
git pull /path/to/other/repo/tag||sha1?23:39
shd you can do it like this:23:39
cd /path/to/other/repo23:40
git checkout -b newbranch SHA1/tag23:40
cd /path/to/first/repo23:40
git pull /path/to/other/repo newbranch23:40
aroben_ joined23:40
shd hmm.. i think git pull /path/to/other/repo SHA1/tag might work as expected..23:40
Guest58011 awesome! thank you very much. git rules23:41
shd please try the latter first..23:41
Guest58011 will do23:41
CrazyTux1 left23:41
shd Guest58011: often, what people do is track the other repo as a remote23:42
purestorm Gah, now I got a segmentation fault in git svn dcommit. Am I lost now, my newer commits do not show any more and I am stuck with an unclean repository state.23:42
shd Guest58011: then you can simply do: git merge SHA123:43
Guest58011: branch name isn't really important23:43
aroben__ joined23:44
WALoeIII left23:44
Guest58011 ok the fetch is working taking a while..23:45
akitada left23:46
krh left23:47
plopix why is a fast-forward merge failing on that? http://pastebin.com/d3fe9e50c23:48
synsol joined23:49
aroben_ left23:50
aroben_ joined23:50
moore__ joined23:51
purestorm left23:51
krawek left23:51
tvw left23:52
moore_ left23:52
Circuitsoft Is it possible to plug filetype-specific diff modules into git?23:54
softdrink joined23:55
grover joined23:56
krawek__ joined23:56
Arrowmaster Circuitsoft: http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html#_generating_diff_text23:57
aroben left23:58
agile left23:58
grover if one does "git pull git://git..../proj.git master" do you pull in that tree's lightweight or heavyweight tags?23:58
Guest58011 Can I get the SHA1 of a tag?23:59
Circuitsoft Guest58011: git rev-parse23:59
<tagname>23:59
ph^ left23:59

Logs Search ←Prev date Next date→ Channels Documentation