IRCloggy #git 2006-05-15

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.

2006-05-15

mugwump how do I push my changes into a new head with git-push?00:16
ah, git-push URL localbranch:refs/heads/remotebranch00:17
I was missing the "heads" bit00:17
GeertB joined00:33
PugMajere mugwump: Doesn't "git push lcoalbranch:remotebranch" work?01:11
dbindner_ joined01:24
mugwump PugMajere: it refused for some reason, lemme see if I can reproduce01:52
error: dst refspec split-mute2 does not match any existing ref on the remote and does not start with refs/.01:52
PugMajere hrm01:57
YGingras joined05:29
Tv joined06:29
BearMan joined07:25
agile joined07:39
dedekind_deaddedekind07:53
ferdy joined08:21
BearManBearPerson08:34
mchehab joined10:07
dwmw2_gonedwmw210:50
benlau joined11:00
e-type left11:09
chris2 joined11:09
lilo joined11:59
mchehab joined12:16
Oeje1 joined12:24
coywolf joined12:51
timlarson_ joined12:52
dst_ joined13:05
robfitz joined13:11
alley_cat joined13:22
spuk- joined13:24
jdl blinks in amazement.13:34
boto joined13:34
jdl Quesstion: after a "git repack" do I need to do a "git update-server-info" too? Is it done automatically if the post-update hook is enabled?13:34
chris2 git repack will call it13:39
jdl Sweet. Thanks13:39
coywolf left13:48
agile joined13:54
coywolf joined15:06
mchehab joined15:24
dwmw2dwmw2_gone16:07
emrys anyone here actually use git-cvsserver?16:07
I'm trying to figure out what perms it actaully needs, it seems to want +w on .git, which is not so good to globally grant16:08
tmokros joined16:33
emrys well, I modified it to use .git/cvs instead of .git for its dbs, that seems to work16:41
GyrosGeier joined16:59
GyrosGeier joined17:00
GyrosGeierGyrosBuitre17:01
juvenis- joined17:03
wereHamster joined17:18
wereHamster hi17:18
Oejet Hello, wereHamster.17:19
wereHamster I thin kI'm stupid.. ;)17:19
no, I'm not ..17:20
how do I export a patchset (or several commits) into a directory? kinda like git-format-patch would do, just without the mail headers17:21
.. because git-imap-send gives me IMAP command 'APPEND "INBOX.Drafts" ' returned response (NO) - Message contains invalid header17:22
Oejet Good question. I don't know, I must admit.17:23
nickh how do you run git format-patch?17:30
Beber` joined17:34
z3ro nickh: git-format-patch (some git commands can't be called like "git foo")17:34
loops wereHamster, likely your drafts folder isn't a subfolder of INBOX.. try git repo-config imap.folder Drafts17:34
nickh nevermind, i was thinking that i wasn't getting those headers, but i am. and then i delete them later.17:35
z3ro oh, it seems you can call any command via "git foo" (just they are not all listed when you run "git" with no arguments)17:35
wereHamster loops, IMAP command 'APPEND "Drafts" ' returned response (NO) - Mailbox does not exist17:36
loops Not sure then wereHamster :o/17:37
So, INBOX.Drafts was correct, hard to see why its balking at the patch messages17:41
wereHamster I'm using the Host = mail.domain.com, User = ... Pass = ... config opetions as I couldn't get the ssh tunnel working17:44
loops that all looks fine.. Do you see it say "sending x messages" ?17:48
GeertB joined17:49
wereHamster loops, http://git.pastebin.com/71915217:50
loops don't know were.. you should probably store the format-patch output to a file, and then selectively remove headers until git imap-send < <file> works17:54
if you figure out what the problem is, it can probably be patched to work for you17:54
wereHamster loops, I've tried git-imap-send this file: http://git.pastebin.com/719175 .. but it won't work17:59
dedekinddedekind_dead17:59
loops wereHamster: hmm well that file doesn't produce an error when used here ;o) do you have a different imap server you can try? maybe it's misconfigured?18:00
wereHamster it's cyrus imapd18:02
loops well, its just that it doesn't cause a problem here so i _think_ it's not a problem with git-imap-send.. possible of course.. but it sounds more like a configuration issue18:03
wereHamster yeah.. I'll ask the admin :)18:03
dashinhomatinho18:14
matinhodashinho18:15
anholt_ joined18:16
Eludias joined18:20
Beber` joined18:34
Tv joined18:43
robfitz joined19:11
Tv joined19:50
robinr joined19:53
Euler joined20:11
anholt_ joined20:12
boto joined20:24
ferdy nickh: got a minute ? I've got a bug in http-fetch.c probably introduced in 8d9fbe57b3acf756a9325884d11f004ef6f7e884 . More information at https://bugs.gentoo.org/show_bug.cgi?id=133412 . I've tried to take a look at the code, but you'll probably know it better than me :)20:34
I got to that commit bisecting20:35
pasky wait, there's SEVENTY THREE PEOPLE here?!20:35
that's sick20:35
wereHamster why?20:36
ferdy haha20:36
DrNick joined20:45
Oejet Maybe we can take over #haskell with 220 people. It seems Freenode is seeing big increase in members.20:55
nickh ferdy: yep, i can take a peek at that20:56
ferdy #0 0xb7e40578 in Curl_compareheader () from /usr/lib/libcurl.so.320:57
#1 0x00000000 in ?? ()20:57
thats what I got from a quick bt20:57
I don't know if that'll help20:57
nickh can i access the repo listed in that bug?20:59
ferdy sure, should be public20:59
nickh that'll help, thx20:59
ferdy just for the record the '-webdav' feature sets NO_EXPAT=YesPlease and 'webdav' doesn't pass it21:01
Oejet Anyone following the current stash discussion on the ml?21:01
nickh can you find the request that generated the 405 response in the server logs?21:02
Oejet cworth: ping21:03
cworth Oejet: pong21:03
ferdy nickh: mmm well, we don't own the server21:03
Oejet cworth: I have an idea for the stash thing. git-stashnswitch:21:04
ferdy nickh: I probably confused you with the repository being 'public'21:04
nickh np, i can track it down from the client side21:04
ACSpike[Work] joined21:04
ferdy ok21:04
ACSpike[Work] where is the most apropriate place to git clone cogito from?21:06
Oejet This would be uquivalent to: git commit -a -m "This is the stash special commit message"; git checkout <branch>; [if HEAD contains special commit message do git-reset HEAD^]21:06
cworth Oejet: perhaps "git checkout -s <stash-branch> somewhere" ?21:06
Oejet cworth: Maybe I told you this before a long time ago, I don't remember. :-)21:07
No, then you'd have to name the stash branch. My idea was to just stash on top of the current branch.21:08
cworth Oejet: Oh, sorry, I misread yours...21:08
Oejet: Yes, I see.21:08
ACSpike[Work] http://git.kernel.org/pub/scm/cogito/cogito.git is that it?21:08
cworth Oejet: So then just "git checkout -s somewhere" to do a stash first.21:08
Oejet cworth: Ok, that's just naming (git checkout -s <branch> = git stashnswitch <branch>).21:09
cworth Oejet: Right. I think it would be better to not invent more commands for changing the current branch.21:10
Oejet But then you could accidentially do a normal checkout on a stashed branch, which breaks the transparency. Hm.21:11
cworth Oejet: But that seems like a rather reasonable way to implement what I want.21:11
PugMajere joined21:11
cworth Oejet: Isn't than an argument for not making it be a new command? We would want the standard "git checkout" to do the restore of the stash.21:12
Oejet Yes, you're right.21:12
cworth And with the new branch-specific config stuff one might use git repo-config to record the stashed state rather than using a magic commit message.21:13
(Since presumably one would also never want to push a stashed branch anywhere... Oh, but I might do a local clone and not pick up the config that way. Hmmm...)21:14
Oejet The question is then, if this stash commit is a convetion, how much of Git should be aware of it?21:14
GyrosGeier joined21:17
wereHamster left21:30
Euler Your momma uses freenode!21:31
GeertB joined21:40
ACSpike[Work] left21:46
ferdy nickh: any thing you find, can you please mail it to me to [email@hidden.address] ? thanks for taking a look at it21:55
now, time to get some sleep :) g'night21:55
schofield joined21:59
spuk joined22:11
GyrosGeier joined22:23
ShadeHawk joined22:27
agile joined23:28
cworth joined23:54

Logs Search ←Prev date Next date→ Channels Documentation