IRCloggy #git 2008-05-25

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2008-05-25

davi left00:02
zachinglis joined00:03
bdiego left00:04
dwave- joined00:05
jerbear joined00:07
threeve joined00:11
schacon_ left00:12
dwave_ left00:18
kukks left00:20
GarethAdams joined00:31
igorgue_ joined00:33
schacon joined00:38
zmonx joined00:38
igorgue left00:50
zmonx left00:51
schacon left00:52
saintdev left00:52
igorgue_igorgue00:52
saintdev joined00:55
koke joined01:03
igorgue left01:05
igorgue joined01:05
doener_ joined01:05
brosner joined01:09
doener left01:18
radarek left01:20
consolers joined01:20
cout how do I undo a git rm?01:28
BabelO left01:28
tpope git checkout HEAD filename01:33
threeve left01:34
cout ok, I remember that now01:35
feels unintuitive to me, but so did "cvs add" to undo "cvs remove" when I friirst started using cvs yuears ago01:36
nkallen joined01:37
lirit joined01:45
felipec left01:46
bugfux joined01:47
goibhniu left01:50
cypher23 left01:53
kukks joined01:55
koke left02:00
Xyrio joined02:07
bwwww joined02:09
saintdev left02:18
j_cook left02:20
roylee17 left02:21
threeve joined02:29
bwwww left02:32
leachim6 left02:32
zachinglis left02:33
CodeOfficer joined02:39
zebrahat joined02:44
mtodd left02:47
mtodd joined02:48
bugfux how cam I merge a remote without the message Merge commit 'origin/master'02:51
pergesu joined02:55
FunkeeMonk joined02:58
Mikachu bugfux: you can git commit --amend to change the message02:59
bugfux i dont want any message02:59
all im doing is pulling in from remote02:59
so i dont want anything to say that im merging02:59
Mikachu then don't have local changes03:00
bugfux hmm03:00
thats bananas03:00
nkallen left03:00
Mikachu or use rebase instead of pull03:00
you can't make commits without making commits03:00
nkallen joined03:04
das-q left03:06
bugfux hmmm03:06
G_SabinoMullane joined03:09
Mikachu is the format of info/grafts documented anywhere?03:10
ah, repository-layout.txt03:10
consolers "Whatsoever ye shall bind on earth shall be bound in heaven: and whatsoever ye shall loose on earth shall be loosed in heaven." -- kjv10.txt03:17
sorry.03:17
misfire. i was giving a ref about the "loose" "lose" misspelling being biblical03:18
Crimea joined03:27
nkallen left03:30
bugfux left03:35
kukks left03:41
consolers left03:47
saintdev joined03:55
mtodd left04:03
das-q joined04:06
jones- joined04:09
threeve left04:11
G_SabinoMullaneZ_SabinoMullane04:13
mtodd joined04:19
mtodd__ joined04:24
rubydiamond joined04:25
tjafk1 left04:27
tjafk1 joined04:27
CodeOfficer left04:30
kanru left04:33
mtodd___ joined04:38
mtodd__ left04:40
ckoehler joined04:41
janm joined04:43
mtodd left04:51
lirit left04:52
cmarcelo joined04:53
tflsh i dont see the misspelling04:57
loose is the opposite of bind04:57
lose isnt04:57
Crimea left05:03
jones- left05:03
Debolaz joined05:08
Debolaz Hmm.. How would I go about incrementally importing a cvs repository that git-cvsimport can't grok correctly?05:09
Right now I'm using tailor, but tailor can't figure out branches automatically.05:09
djwonk left05:15
Crimea joined05:18
madewokherd left05:24
bobesponja left05:26
rubydiamond left05:26
bwwww joined05:27
mtodd___ left05:29
ckoehler left05:33
etnt` joined05:40
Z_SabinoMullane left05:43
Lucine2 left05:46
Lucine2 joined05:50
mtodd joined05:51
bwwww left05:54
nkallen joined05:55
maveriick joined06:01
maveriick hi erveybody06:01
I experienced a problem during git commit due to power outage....I would if anyobdy can hint on any help....06:02
I am issuing a git commit ..... writing the commit msg in the editor...in that time power outage occured....06:02
now when I give the command git status it says: fatal: index file smaller than expected06:02
sgrimm joined06:04
sgrimm left06:05
sgrimm joined06:05
maveriick Anybody faced similar situation?06:12
csc` left06:18
csc` joined06:20
nkallen left06:37
asdx left06:52
etnt` left07:02
FunkeeMonk maveriick: yikes, that sounds scary. Did you manage to recover from the problem yet?07:04
stni left07:06
stni joined07:07
cmarcelo left07:07
bwwww joined07:13
rvo joined07:14
thiago_home maveriick: it looks like your repository files got corrupted07:17
try checkout -f HEAD07:17
rvo left07:21
robinr joined07:23
brosner left07:35
rubydiamond joined07:41
maveriick thiago: i am just back after recovering....07:50
thiago_home: what I did is ...sit in a cowrokers PC then add myself as remote....and then fetch my repo from there....07:50
thiago_home, it looks clean there....07:51
thiago_home: Donno how it works ....but i am happy that it worked ......it consists labor of 3 days in that commit...07:51
anttih joined07:52
maveriick brb .....(logging in from another PC)07:52
maveriick left07:52
lolage0 left07:55
jerbear left08:00
csc` left08:00
devogon joined08:05
lirit joined08:06
priidu joined08:06
priidu left08:07
priidu joined08:11
ph^ joined08:11
lirit left08:12
priidu left08:14
rubydiam_ joined08:15
rubydiamond left08:15
bwwww left08:16
priidu joined08:17
deavid joined08:21
Beket joined08:26
d0k joined08:34
hein2 joined08:35
Sho_ left08:35
hein2Sho_08:35
igorgue left08:37
holizz joined08:45
mjponce joined08:51
mjponce left08:51
gitte joined08:55
_graham_ joined09:00
jones- joined09:02
scorp007 joined09:04
scorp007 what is the typical way of releasing a tagged version of the repo?09:05
jast depends on the way you want to release it09:06
one way is to tell people the name of the tag :)09:06
scorp007 what if I wanted to archive a stable version?09:06
say, by zipping it up.09:07
jast try git archive09:08
scorp007 ah ok09:08
jast you can even give it a tag name iirc09:08
scorp007 ah, you're right.09:09
jast seems to output to stdout09:09
scorp007 thanks09:09
there's an example that zips it.09:09
Pieter git archive HEAD | gzip > project.tar.gz09:10
that's how most people use it09:10
scorp007 yep, that's similar to the example09:10
mfwitten left09:11
jast and to think i wrote my own script to do that some time ago... :C09:13
Pieter §9§909:13
oops09:13
scorp007 what's the pax_global_header files it creates?09:15
file *09:15
jast a tar archive09:18
(uncompressed)09:18
use --format=zip for, well, zip09:18
scorp007 oh ok09:20
rubydiam_rubydiamond09:22
cypher23 joined09:30
RoboTeddy joined09:33
RoboTeddy left09:33
consolers joined09:34
consolers how to deal with git-cvsimport: request for non-existent rev 1.1 in file XXX09:34
(its a new file added to the repository)09:35
chris2 joined09:36
consolers (its a new file added to the repository in a new branch)09:38
goibhniu joined09:42
Sho_ left09:43
Sho_ joined09:46
DrNick left09:48
dwave- left09:51
Husio left09:51
DrNick joined09:54
DV|HearthCore left09:55
DV|HearthCore joined09:55
DV|HearthCore left09:55
_DV|HearthCore joined09:56
chris2 left09:57
Yuuhi joined09:59
gitte left10:00
MarcWeber left10:02
felipec joined10:06
consolers Why does git even choose to use cvsps10:15
sheesh10:15
priidu left10:19
Xyri0 joined10:23
jmspeex joined10:27
jast well, you need *some* way of reading stuff from the repo10:28
Beket Hi people. Is this mem leak a false alarm http://rafb.net/p/tXlCyR86.html ?10:30
jast it doesn't actually run the script, does it?10:31
also, git-cvsimport is a perl script and perl has a garbage collector10:31
Beket mm, thanks jast10:32
jast try the advice from the last line if you want to see what exactly causes the leak10:33
(i haven't used valgrind yet so i can't give any specific advice)10:33
AlexB When you do, don't remove anything called MD_Update ;-)10:35
jengelh only debian users would do that10:35
jast bashing debian never gets old, does it :D10:35
jengelh debian itself is old10:35
jast not after i spent four hours updating ssh keys everywhere10:35
Xyrio left10:36
Xyri0Xyrio10:36
_DV|HearthCore left10:37
consolers I've no idea how i'm going to fix this. turning on debugging in cvsps gives gobs10:39
dirk1296 joined10:41
consolers the files are under Attic/10:43
branch files go under Attic/ ?10:43
jast normally, "old" files go under Attic/, i.e. deleted files (iirc)10:48
holizz_ joined10:49
scorp007 errm, how do I undo a change in my working copy to what is in the HEAD?10:50
on 1 file10:50
jast git checkout HEAD -- filename10:50
if it's still untouched in the index, you can omit the HEAD10:50
scorp007 ah, cool10:50
thanks10:50
how do I verify a repo is non-corrupt, if I may have accidently interrupted a push?10:53
consolers jast, yet when i checkout the branch with -r, the files are correct. theyre in Attic/ though10:53
cvsps fails horribly because it cant find the files10:54
this is on the CVSROOT repo10:55
shaftyy joined10:56
consolers so i am to infer that new files in a new branch go to Attic/10:57
rubydiamond left11:01
holizz left11:04
PferdOne joined11:06
consolers (its documented in the CVS manual under Attic/)11:11
priidu joined11:12
Ilari scorp007: 'git fsck --full' on remote end. Be aware that lots of 'dangling' messages are to be expected...11:12
scorp007 Ilari, ok cool11:14
so those danglings messages are safe?11:15
ferdy left11:15
scorp007 wierd, no output.11:15
ferdy joined11:15
Ilari scorp007: If that repo does not have working tree, and has never had branch rewound, then no output is expected... In any case, no output means it passed the checks.11:16
scorp007 oh ok11:16
it seems to be missing a tag though..11:17
ah, nevermind.11:17
shermanl left11:18
Ilari scorp007: For pushes over ssh:// (and git:// if repository owner doesn't care about security), updating the remote repository is done by a program running on remote host, not by direct writing.11:19
scorp007: For HTTP WebDAV push (yuck), the files are written directly, but it is possible to write files in correct order (packfile, packfile index, packfile list, refs, refs list), so the repository stays valid at any point during the update...11:26
sdiz left11:29
Judofyr joined11:30
GarethAdams left11:32
priidu left11:32
GarethAdams joined11:33
Fullmoon left11:34
robin joined11:42
Fullmoon joined11:43
jast does http-push really write pack files?11:47
bentob0x joined11:49
ebel joined11:52
G_SabinoMullane joined11:52
robinr left11:54
Ilari jast: Even if it writes loose objects, the operations can be still be done in correct order not to corrupt the repo...11:55
BabelO joined11:59
PferdOnePferdOne`TV12:01
anttih__ joined12:03
Beket left12:04
jast yeah, except if it writes a partial object12:04
Mikachu it doesn't write to a temp file and rename?12:06
consolers anyone has hacked cvsps before?12:06
jast i don't know. i haven't looked at http-push. i'm not sure i want to.12:07
i know even less about cvs internals and, by extension, about cvsps12:09
chris2 joined12:11
dirk1296 left12:13
perg joined12:14
pergesu left12:14
rubydiamond joined12:15
cypher23 left12:17
consolers from reading the comments in cvsps.c:412 assign_pre_revision (33357c69) it looks like I'm fucked12:18
hatsffilc joined12:19
anttih left12:20
consolers the problem isnt that it is looking for a file which is in Attic, it is looking for wrong revision12:20
_graham_ left12:21
_graham_ joined12:21
d0k left12:21
devogon left12:21
mithro left12:21
niki left12:21
johan-s_ left12:21
statim left12:21
jdq left12:21
Pistahh left12:21
albertito left12:21
EvanCarroll left12:21
majoh left12:21
bartman left12:21
noz left12:21
shawn__ left12:21
Mutru_ left12:21
kergoth left12:21
mojombo left12:21
bryanl left12:21
benp- left12:21
Illocution left12:21
Thumper_ left12:21
robbyonrails left12:21
henr_k left12:21
frsk left12:21
Ted left12:21
Tv left12:21
CIA-53 left12:21
hatsffilccliffstah12:21
Ted joined12:23
d0k joined12:23
devogon joined12:23
mithro joined12:23
niki joined12:23
johan-s_ joined12:23
statim joined12:23
EvanCarroll joined12:23
jdq joined12:23
Illocution joined12:23
Mutru_ joined12:23
CIA-53 joined12:23
benp- joined12:23
albertito joined12:23
Tv joined12:23
noz joined12:23
bryanl joined12:23
frsk joined12:23
henr_k joined12:23
bartman joined12:23
shawn__ joined12:23
Thumper_ joined12:23
majoh joined12:23
kergoth joined12:23
robbyonrails joined12:23
Pistahh joined12:23
mojombo joined12:23
noz left12:25
felipec left12:25
consolers wow this may be fixed in cvsps 2.2b1 which git repo is unaware of12:26
Mikachu how many git repos and home pages does that program have anyway?12:31
dirk1296 joined12:31
consolers I counted 2 git repos and 3-4 locations for the sources :)12:31
Mikachu heh12:32
consolers problem is on upadate, i'll bet it'll change the patchsets it finds, thereby giving ALL commits new shas.12:33
it is _impossible_ to duplicate two imports12:33
to give the same git repo12:33
Mikachu update compares timestamps i think though?12:33
consolers cvsps does, yes12:34
but if i had wanted to rebuid the git repo and get consistent shas from the CVS repo from scratch, i'd have to keep the cvsps binary and snapshots of aCVSROOT12:35
heh12:35
PferdOne`TV left12:37
Mikachu what's the stuff in ~/.cvsps for?12:39
dirk1296 does anyone here have experience with "git filter-branch --subdirectory-filter" under msysGit?12:51
kukks joined12:53
consolers cache12:55
I'm facing a problem after merging:12:55
I fix the conflict and do a commit, i get error: Error building trees12:56
that means i'm screwed/12:58
?12:58
kixx joined12:59
jast it sure sounds so. tried git fsck?12:59
consolers i'm in the middle of a merge12:59
let me try anyway12:59
one dangling blob13:00
which on cat-file proves to be the last conflicting file (with conflicts in it)13:01
jast that doesn't explain the error message13:04
dangling blobs are pretty normal, after all13:05
perhaps try the commit with GIT_TRACE=1 for more details13:05
consolers bah. anyway 2.2b1 doesnt fix my problem13:06
felipec joined13:10
perg left13:14
ec left13:15
consolers nope. trace: built-in: git 'commit13:19
easy enough to find it in builtin-commit.c as an error in cache_tree_update13:20
git-diff is non-nil13:23
how do i cancel the merge?13:23
is there a canned command?13:23
chris2 i'm making an tar with git-archive, but i'd like to add additional files, is there a nice trick?13:29
jast you can use tar to append files to an existing archive13:30
chris2 i could "tar r" them, but i want a directory prefix13:30
jast i.e. pipe the stuff through another instance of tar before gzipping it (or whatever you do)13:30
chris2 and i dont know how to make tar add to a subdirectory :/13:30
statim left13:32
robin chris2: there is a --transform option13:33
chris2 not in my version on osx here13:33
but that's what i would need13:33
robin ah, cripplix13:34
chris2 it's a gnutar13:34
consolers you can use -r with a list of files to append to a tar archive, or create a diff.tar contaning the new files and and use -A to cat13:34
chris2 but oldish13:34
that doesnt allow me to put them into a subdirectory13:34
will try using pax13:35
consolers i dont understand. you create the diff.tar with the subdir structure you want13:35
or you use -r subdir/filename13:35
chris2 i want to avoid making the prefix directory in my fs13:35
consolers i dont understand13:36
chris2 if tar simply had a --prefix option it would be fine13:36
i use git-describe as prefix13:36
for making releases13:36
koke joined13:37
consolers how would a --prefix option work with tar?13:37
chris2 tar --prefix pre -r filename => tar -r pre/filename13:38
jast one thing you could do, though it's ugly, is create a temporary symlink to the dir and pass -h to tar13:38
chris2 where pre only exists in the archive13:38
i'll use pax13:38
consolers so just temporarily mkdir pre; mv filename pre; tar -r pre/filename13:38
whats your problem?13:38
holizz_ left13:39
chris2 it makes the script more complicated :)13:39
jast that's what scripts are for ;)13:39
consolers youre going to rm -rf pre anyway13:39
heh13:39
chris2 i dont have to if it doesnt exist :)13:39
consolers I still have the setup where my git-commit is failing if someone wants to help me debug the cache issue13:40
jast consolers, as i said, try with GIT_TRACE=1 to get more information that's possibly more suitable for debugging13:41
consolers no, TRACE=1 just shows that builtin-commit is being used13:41
jast ah13:41
consolers the problem is that `cache_tree_update' fails and that can fail for 2 reasons13:42
charon joined13:42
consolers but if someone with git-fu could spot it at a glance ....13:42
jast to cancel merges, by the way: git reset --hard (the usual warnings apply)13:43
edward joined13:43
madewokherd joined13:43
imyousuf joined13:44
bdiego joined13:45
jast will probably fix the problem too13:45
edward anybody using git to store a collection of photographs?13:45
edward is wondering if there is any best practice13:45
imyousuf I want to see all the commits in which a file (object) has been changed, what would be the easiest way to do it?13:46
priidu joined13:46
cobrapg joined13:49
consolers hhmm13:49
git-log --name-only --follow file.c gives the full log13:49
bah13:49
i mean it doesnt give "name only"13:49
imyousuf I see13:50
let me check13:51
jast edward, what makes it useful to use git for that?13:51
consolers thats of course because i misread the documentation for --name-only13:53
jast imyousuf, --pretty=oneline may be helpful too to get a better overview. you can even leave out --name-only then because you'll only get the id and subject13:53
imyousuf consolers: thanks git-log --follow file.c this worked13:53
I was also reading man of git-log13:53
jast tring the --pretty option13:54
cobrapg I have a problem with Git... is asking for help allowed here?13:54
jast cobrapg, definitely, yes13:54
imyousuf :) yeah cobrapg13:54
cobrapg cool!13:54
imyousuf jast thanks, that shortcut helps as well :-D13:55
jast one of the main points of this channel, really13:55
cobrapg I am trying to do a rebase with Git and I get a SSL not supported error13:55
jast git-svn rebase, i assume?13:55
cobrapg yes13:55
Illocuti1n joined13:55
jast did you initially clone the repo from the same system?13:56
edward jast: so i can track changes13:56
jast *on* the same system, i mean13:56
cobrapg I get the same error13:57
imyousuf cobrapg: One policy I follow in git svn development is I keep by SVN branch clean and work in another branch13:58
jast edward, well. most photo collections i know don't change, but makes sense. what sort of best practices do you mean?13:58
cobrapg This is the error I get13:58
RA layer failed to init socket layer: SSL is not supported at /usr/bin/git-svn line 135913:58
imyousuf so a simple svn fetch, git merge, git dcommit, git rebase is fine13:58
and did not get any error13:58
jast no, that's not a git-specific error13:58
it's either ssl support missing on your system13:58
imyousuf I develop projects in google code13:58
jast or on the other side, if it's seriously broken... can't tell which13:58
cobrapg hmmmm13:59
edward jast: just wondering if i should like jpegs unchanged, store a file with a list of changes, like rotate and crop. i just wondered if anybody here was doing that kind of thing13:59
anttih__ left13:59
jast i can't figure out right now what ssl lib is used13:59
cobrapg jast: what is interesting is that I can do a svn checkout from a https enabled repo14:00
jast that's weird14:00
lirit joined14:00
jast i dunno how git-svn works there. i'll try to check in a couple of minutes14:00
Illocuti1n left14:00
cobrapg jast: OK14:00
priidu left14:00
cobrapg jast: I thought git-svn did an internal pipe, but it seems to be done differently14:01
if I do a svn --version14:01
jast edward, problem is jpegs don't delta-compress well (because they're already compressed). therefore keeping several versions of your pictures will consume approximately as much space in the repo as all versions of all files.14:01
cobrapg, it uses the perl cpan module SVN (or something like that), but also perl's libwww directly. dunno how that one works.14:02
(i dunno how either works, really. i *think* perl's svn module uses libsvn)14:02
cobrapg yes14:02
I have all the perl bindings14:02
edward jast: thanks14:02
cobrapg cause I can checkout with git-svn as long as the repo is not SSL enabled14:03
jast libsvn uses neon for webdav (including ssl)14:07
scorp007 left14:07
jast what os/distribution are you using?14:07
cobrapg CentOS 4.514:07
priidu joined14:07
cobrapg so... is there a way to check if neon has SSL enabled in it?14:08
jast i think it depends on libssl14:08
problem is i don't know what all these packages are called in fedora-like systems14:08
cobrapg you mean openssl?14:08
jast libneon in this case14:09
in ubuntu it's helpfully called libneon2714:09
cobrapg hmmmm14:09
Illocution left14:10
jast if you know your way around rpm you can probably find out14:12
cobrapg right14:12
now...14:12
when compiling from source... is ssl an option for neon?14:13
shaftyy left14:13
jast i'm pretty sure it is14:13
in debian it's a hard dependency, so there's no way around it there14:14
shaftyy joined14:14
cobrapg OK14:14
shaftyy left14:15
jast does plain svn work with ssl? because if it does, you can be sure neon has ssl support14:15
cobrapg yes14:15
lydgate joined14:15
cobrapg it does14:15
jast oh, you already said :{14:15
koke left14:15
cobrapg so... that means neon has SSL then?14:16
athought joined14:16
jast i'm pretty sure, yes14:16
what version of git are you using, by the way?14:17
oh, sorry, i gotta go for about an hour.14:17
a-priori joined14:18
cobrapg left14:19
d0k left14:19
shaftyy joined14:19
cobrapg joined14:20
cobrapg sorry I got disconnected14:20
I am using git 1.5.5.114:20
shaftyy left14:21
felipec left14:22
koke joined14:23
koke left14:23
cobrapg left14:24
cedricv joined14:24
imyousuf left14:25
csc` joined14:26
[Cobra] joined14:26
priidu_ joined14:27
[Cobra] left14:27
shaftyy joined14:27
athought left14:28
priidu left14:28
kixx left14:31
shaftyy left14:33
djwonk_ joined14:34
fadec joined14:35
priidu_ left14:37
felipec joined14:37
statim joined14:41
priidu joined14:43
chris2 pax -waf tarball -s ':^:prefix/:' new files works14:43
but not with the id-tagged tarballs, so you need to archive HEAD^{tree}14:44
cypher23 joined14:51
shaftyy joined14:54
kixx joined14:56
priidu left14:56
advany joined14:59
bobesponja joined15:00
priidu joined15:02
mtodd__ joined15:02
priidu left15:03
priidu joined15:06
consolers Actually 2.1b1 will fix the problem.15:09
cmarcelo joined15:10
priidu left15:12
bdiego left15:14
priidu joined15:14
schacon_ joined15:15
yann left15:18
beeble left15:18
anders_ left15:18
xkr47 left15:18
mtodd left15:18
priidu left15:20
tflsh_ joined15:25
tflsh left15:26
yann joined15:26
xkr47 joined15:26
beeble joined15:26
priidu joined15:26
anders_ joined15:26
priidu left15:31
lirit left15:32
tflsh joined15:32
zachinglis joined15:37
radarek joined15:38
tflsh left15:44
tflsh joined15:45
consolers left15:47
tflsh_ left15:47
Ramune left15:54
Illocution joined15:55
zachinglis left15:58
nkallen joined15:59
cypher23 left16:00
kanru joined16:00
GarethAdams left16:01
zachinglis joined16:02
GarethAdams joined16:03
jp_tix if i have added a submodule to my project, the only thing needed to keep it up-to-date is `cd submodule/ && git pull && cd .. && git commit` ?16:03
jast it may be necessary to do a git add submodule (without / at the end) before the commit16:05
Ilari jp_tix: Yea. No, '/' at the end, or the result will be a mess. Watch out, bash autocompletion puts that '/' there by default.16:08
jast as does zsh's, i guess16:08
Mikachu it does not16:10
Judofyr as does fish's...16:11
Debolaz Hmm.. How would I go about incrementally importing a cvs repository that git-cvsimport can't grok correctly and I don't have direct access to the ,v files for?16:12
jp_tix Ilari: for `cd dir` that shouldn't matter, no?16:15
Ilari jp_tix: Yes, it doesn't matter for 'cd'. It matters for 'git add'.16:15
jp_tix ah, didn't put that on my line16:16
it seems that if i do git diff after the submodule pull, it references a different submodule commit16:16
and that seems to be enough16:16
Ilari jp_tix: Yea. That's supposed to happen.16:17
jp_tix so what is the need for `git add` in this context?16:17
Ilari jp_tix: 'git add submodule'.16:17
jp_tix i need that after every submodule pull?16:18
Ilari jp_tix: Well, if you want to update the version recorded in supermodule. I think that 'git commit <submodule>' or 'git commit -i <submodule>' might also work (see 'git status <submodule>' and 'git status -i <submodule>').16:19
jast doesn't commit simply commit the index? in that case, add is unavoidable (or commit -a, of course)16:21
zachinglis left16:23
Ilari jast: Commit also accepts filesnames. Specify those, and its like 'reset HEAD', 'git add <filenames>' (include -i option to leave the reset out).16:24
jast oh, right. i haven't used that yet.16:24
and the one time i tried i did something wrong and it didn't work16:25
Ilari jast: It is very rarely used...16:25
robin left16:25
kixx left16:25
dirk1296 left16:25
bdiego joined16:26
robin joined16:27
consolers joined16:32
consolers the `Error building trees' I'm seeing on git-commit, is really a bad merge is it?16:33
Ilari consolers: Does 'git status' give anything unusual, like unmerged entries?16:38
stni left16:39
holizz joined16:39
CodeOfficer joined16:40
consolers well git-commit reports unmerged entries before bombing out16:40
I am comitting after resolving a conflict16:40
i.e. in the middle of a merge16:41
so git-status is a little out of date: it shows that file to be unmerged16:41
and the rest: modified16:42
__dexter__ joined16:42
consolers hmm git-commit shows unmerged "hunks" i think in that one file16:42
flaguy joined16:42
jast did you call git add on that (now unconflicted) file?16:43
consolers tests a hunch16:43
jast (after making sure there are no conflict markers in it, of course)16:43
consolers kicks self16:44
consolers thanks jast16:45
jast sometimes it's the small things ;)16:45
GarethAdams left16:48
consolers git-cvsimport needs to be updated for cvsps-2.1b1 in how branch ancestors are calculated16:50
Mikachu you mean 2.2b116:51
consolers indeed16:51
Sho_ left16:53
Sho_ joined16:54
bdiego left16:55
Judofyr left16:56
ebel left16:57
advany left16:57
brosner joined16:58
pergesu joined17:02
SuttoL joined17:08
holizz left17:08
__dexter__ left17:08
etnt` joined17:09
manveru_ joined17:17
serfurj joined17:18
manveru left17:19
serfurj I pushed changes to a repo, but forgot to check them out before making changes. How can I merge the changes to the working copy with the committed changes? For some reason "git merge master" says "Already up-to-date".17:20
Mikachu that's why you shouldn't push to a non-bare repo17:21
do you know the sha1 the repo was at before the push?17:21
serfurj Mikachu: yes17:22
Mikachu i haven't tested this, but i think it should work17:22
git reset --soft thatsha117:22
git commit yourfiles17:22
git rebase thenewtipyoupushed17:23
does that make sense?17:23
ie, the last sha1 is where the branch is now17:23
so you want to go back to where it was, make the commit, then rebase it to the new code17:23
pasky i think that won't work17:23
Mikachu why?17:24
pasky since the commit will have thenewtipyoupushed as the parent17:24
so rebase won't do anything17:24
no?17:24
Mikachu you soft resetted to thatsha1 first17:24
pasky oh17:24
right, that'll change your head17:24
serfurj Mikachu: I'll try that. Thanks17:25
Mikachu just make sure you don't type reset --hard ;)17:25
serfurj Mikachu: I'll test it out on a copy first17:26
Mikachu that's probably a good idea :)17:26
if you do a git branch old first you can do git rebase old instead of copying that sha1 too, then just git branch -d old17:27
(or a tag)17:27
serfurj what is thenewtipyoupushed?17:28
Mikachu that's the sha1 you're at before you did any of the steps i wrote17:29
ie, the one you pushed17:29
serfurj oh ok17:29
Mikachu it should be HEAD@{1} or so probably :)17:29
hm, or maybe 2 or 3 ;)17:30
consolers left17:31
serfurj Mikachu: worked, thanks.17:36
d0k joined17:38
Mikachu nice, you're welcome :)17:42
drizzd joined17:43
rubydiamond left17:51
koke joined17:52
etnt` left17:56
Crimea left17:57
Crimea joined17:59
ebel joined18:00
shermanl joined18:04
consolers joined18:05
Crimea left18:05
tagx joined18:12
tagx does svn 1.5 break git-svn?18:12
because i am getting segfaults with git-svn now18:12
mithro left18:12
jengelh sh, don't use svn :p18:12
tagx i have to18:14
but i want to use git on top of it18:14
so it will be nicer18:14
jengelh it can't be nicer than the ugliest link18:14
Ilari tagx: In what component it segfaults in? Git-svn itself, libsvn, apr?18:15
tagx Ilari: how do i find out?18:15
Ilari tagx: No way to get stack backtrace?18:16
consolers Mikachu, so git-importsvn will have to be reworked completely I think, calling cvsps without -A ?18:17
tagx apr i tihnk18:17
Mikachu i have no idea how it works internally, sorry18:17
consolers I added a branch to parse the Branches: line and build a hashtable18:17
ok18:17
chris2 left18:17
consolers linus ancestor finding hack was just wrong anyway18:18
at least on the repo of my interest:18:18
tagx Ilari: could bad interaction with svn 1.5rc5 be causing the segfault?18:19
Ilari tagx: With badly written software, doing one small mistake may cause segfault (even if it appeared to work in previous version)...18:21
Pieter hi18:21
_manveru joined18:24
manveru_ left18:25
Debolaz tagx: Make sure the svn perl modules are updated on the client side.18:27
schacon_ left18:28
Debolaz A perl script, which git-svn is, should *not* segfault, so the problem is likely to be in the subversion libraries themselves.18:28
jengelh well if you can make perl crash, that's scary18:28
tagx im downgrading my svn version now18:29
cypher23 joined18:29
Mikachu http://bugs.gentoo.org/show_bug.cgi?id=21920318:30
schacon joined18:34
schacon left18:37
G_SabinoMullane left18:39
pergesu left18:42
kixx joined18:49
tagx hmm, now im getting permission denied...18:49
Pieter that's better18:50
tagx when i try to create a new git-svn repo18:50
but using an older one18:50
it works now18:50
cliffstah left18:52
cliffstah joined18:52
cliffstah left18:52
cliffstah joined18:52
cliffstah left18:52
blackdaemon left18:59
a-priori left19:00
cliffstah joined19:04
consolers left19:05
biz I've pushed a commit from another machine where I didn't set my realname, is there a way to fix this afterwards? (The log on gitweb shows my login name now...)19:11
drizzd biz: is it the last commit?19:22
Crimea joined19:23
bdiego joined19:24
biz drizzd: I think doing a git-revert won't remove it from history, only a git-reset --hard HEAD^ && git-push -f origin? Since I'm actually the only active one on this project, there should be no problems with this, or would you suggest some other way?19:24
And yes, it's the last commit.19:24
Mikachu just running git commit --amend should fix it19:25
Pieter you can do git reset --soft HEAD^ && git commit to commit again19:25
I was wondering how ammend does that19:26
so if you ammend someone else's commit, you'll be the author?19:26
how about git rebase -i and edit?19:26
Mikachu not much point if it's the last commit19:26
Pieter yeah, but what does rebase -i do?19:26
retain the original author?19:26
jengelh rebase retains author afair19:27
Mikachu both amend and rebase retains it19:27
jengelh as does cherry pick19:27
Mikachu you can git commit --amend --author 'whatever <a@b>' then19:27
and -C HEAD to suppress the editor19:28
but maybe reset --soft HEAD^ && git commit -c HEAD@{1} is easier then :)19:28
Pieter --amend is the easiest anyway19:29
Mikachu but you have to write the author manually then19:29
Pieter oh well19:29
;)19:29
what if you set GIT_AUTHOR_NAME?19:29
Mikachu you still have to set it manually then19:30
Pieter ah19:30
I was thinking about GIT_EDITOR=cat GIT_AUTHOR_NAME="Pieter" git rebase -i HEAD~50 :)19:30
Mikachu i mean setting that is manual :)19:30
Pieter oh :)19:30
biz git commit --amend yields:19:31
! [rejected] master -> master (non-fast forward)19:31
(the push afterwards I'm talking about)19:31
Mikachu of course19:31
nkallen left19:31
Mikachu but you should continue reading19:31
bentob0x what's the difference between git reset --soft HEAD and git reset HEAD?19:39
Mikachu soft doesn't change the index, while the other one does (--mixed)19:40
in fact, git reset --soft HEAD is a no-op19:40
bentob0x git reset HEAD = git reset --mixed HEAD?19:40
Mikachu yes, --mixed is the default mode19:40
Pieter yes19:40
bentob0x k19:40
(was in the man, didn't see it)19:41
Mikachu git reset --soft sha1 changes HEAD to sha1 (or rather, the branch HEAD points to when it isn't detached)19:41
mixed does that, and updates the index to match that commit19:41
nkallen joined19:41
Mikachu --hard additionally updates the working tree19:41
bentob0x so I have tons of modifications and I started to add files for a commit but I want to restart it all while keeping the modifications, I have to do a git reset --soft HEAD and I'll keep the modifications untouched?19:41
advany joined19:42
Mikachu you want --mixed then19:42
as i said, --soft HEAD is a no-op19:42
bentob0x I want to unstage everything basically but keep it all as it is19:42
Mikachu indeed19:43
actually just "git reset" is sufficient19:43
larsl joined19:43
a-priori joined19:44
bentob0x I just did git reset HEAD19:44
seems fine19:44
git reset == git reset HEAD == git reset --mixed HEAD19:44
thx guys19:44
Mikachu np19:44
felipec hmm, "echo foo | git commit" is trying to use my editor19:45
Mikachu who said git commit reads commit messages on stdin?19:46
biz Thanks Mikachu and Pieter19:46
felipec Mikachu: so how can I read a commit message from a file?19:46
bentob0x git commit -m "foo" felipec19:46
robin -F file19:46
in tfm19:47
felipec robin: cool, can it be -F -?19:47
bentob0x be nice with people robin or I call batman19:47
^^19:47
robin :)19:47
felipec: reading man pages doesn't hurt19:48
even git man pages sometimes contain useful information19:48
Mikachu even if it didn't have -, -F /dev/stdin usually works19:49
felipec robin: yeah, I just thought git would automatically ready the message from stdin if there was input there19:49
Mikachu felipec: that would mean it would read from the terminal instead of the started editor19:49
SuttoL left19:49
Mikachu unless you do weird things like isatty()19:49
robin no sane programs does that19:53
jengelh actually, git-filter-branch reads it from stdin... in a way.19:53
robin sure programs read from stdin, but not by detecting if there in input on stdin or not. They always read from stdin or they don't, depending on optins19:54
jamessharpe joined20:00
priidu joined20:04
d0k left20:05
shaftyy_ joined20:05
shaftyy_ left20:06
shaftyy_ joined20:06
shaftyy_ left20:06
a-priori left20:09
Crimea left20:10
statim left20:11
larsl left20:13
koke left20:14
shaftyy left20:20
shermanl left20:22
pygi left20:22
ec joined20:27
cliffstah left20:27
jjlee joined20:31
jjlee after a git-svn clone, git-branch only lists "master", despite the clone operation showing multiple branches being fetched20:32
gitk seems to show some branches but not others -- but I'm not used to reading gitk display20:33
Modius_ left20:33
jjlee example: Found possible branch point: https://python-nose.googlecode.com/svn/trunk => https://python-nose.googlecode.com/svn/branches/160-jython, 43620:34
but I don't have a branch 160-jython, or similar20:34
why not?20:34
Mikachu jjlee: git branch -a20:34
jjlee ah, I see - thanks20:35
I still don't understand why, in gitk, only some branches are displayed in the "Branches:" list as hyperlinks20:36
for example, in "Branches: master, remotes/0.10.2-stable, remotes/141-collect-only, remotes/tags/0.10.2-release, remotes/trunk"20:37
"remotes/141-collect-only" is not a hyperlink, but the others are20:37
Mikachu probably because the commit it points to isn't shown in the graph20:38
jjlee why would it not be shown in the graph?20:38
Mikachu you didn't ask for it, try gitk --all20:39
jast gitk shows only the current branch by default20:40
(iirc)20:40
i rarely use gitk, truth be told20:40
jjlee yes, --all just discovered that :-)20:40
jast: you prefer command line, or some better GUI tool?20:41
threeve joined20:41
jast i use command line most of the time20:42
but the main reason for that is that i mainly use git for smallish projects and svn project (which don't have complicated branch structures)20:42
Mikachu i usually use qgit when i want to look at more complicated history, i get confused by gitk's nonstraight lines20:42
janm left20:46
jjlee can anybody explain what "File->Update" and "File-Reread references" in gitk mean?20:47
I'm guessing "references" here means the same thing as the "refs" in this diagram20:47
http://utsl.gen.nz/talks/git-svn/git-model.png20:47
ironfroggy joined20:47
jjlee (though I don't really know what those "refs" are either ;-))20:48
specifically, I'm wondering what the difference is between "refs" and "heads"20:48
Mikachu nothing, "branch" is another word20:49
i guess branch is a subset of refs though, tags are also refs20:49
niki left20:49
jjlee that diagram lists "refs", "heads" and "tags"20:50
all three20:50
Ilari jjlee: They update the display to reflect changes in refs. Not sure about the difference (it could be that one picks new refs, while the other doesn't)...20:50
Mikachu it describes refs and heads identically afaics20:50
jjlee: if you commit something you use those to refresh the display20:51
jjlee ok, so "reread references" does not alter the working tree (as I expected)20:51
does File-Update alter the working tree?20:51
Ilari jjlee: Nope.20:51
bentob0x left20:52
jjlee what does it do?20:52
Ilari jjlee: It apparently performs full refresh of the drawn graph (picking up any possible new refs created, etc...)20:54
jjlee: (effect pretty much similar to closing and restarting gitk with the same parameters).20:55
jjlee ok. I'm a coward :-)20:56
Mikachu i think the only thing gitk can do is cherry-pick?20:56
Ilari jjlee: If you want GUI that can actually do a lot to the working tree, use git-gui...20:56
jjlee: Altough Git-gui AFAIK can't do rebase operations (those must be done from command line), but is otherwise quite capable...20:57
jjlee not especially - it's just nice to know what a button labelled "Update" will do before you click it20:58
G_SabinoMullane joined20:58
Ilari jjlee: At least it won't do anything destructive. :-)20:58
jamessharpe left20:59
threeve left20:59
jjlee hmm, I prefer the straight lines in qgit too - thanks for the pointer21:00
ironfroggy left21:04
sbeyer joined21:06
jjlee though there seems no easy way in qgit to browse through patches, which is something I like about gitk21:06
Mikachu if you double click a commit it'll show the patch in a new tab21:07
jjlee not quite as easy as up/down arrow21:07
priidu left21:09
angasule_ joined21:11
angasule left21:11
statim joined21:18
ph^ left21:22
angasule_angasule21:24
ec_ joined21:27
ec left21:29
ferdy_ joined21:32
ferdy_ left21:32
ferdy_ joined21:32
marze joined21:32
ferdy left21:32
ferdy_ left21:32
ferdy joined21:32
jroes left21:33
larsl joined21:34
ToxicFrog Hmm. How do I push tags?21:35
dato push --tags21:35
ToxicFrog That was simple. Thanks.21:35
What if only want to push a specific tag?21:35
larsl If I have a CVS working directory containing a subdirectory coming from a separate repository, is there any way to get git-cvsimport to import the whole thing from both repositories as a single Git repository?21:35
vmiklos git push origin v1.0?21:35
larsl With history intact.21:36
ToxicFrog Aha! I was missing the "origin"21:36
It's "git push <branch> tag <tagname>"21:36
vmiklos nope :)21:38
git push remote tag v1.021:38
<remote>*21:38
origin is not a branch21:38
Sonderblade left21:39
mugwump larsl: do them independently, then stitch together with git-filter-branch21:39
you'll probably need to develop your own script for the stitching21:39
larsl mugwump: Ah, interesting - hadn't seen that before.21:39
mugwump you'll probably want to use a "tree filter", and in that tree filter, put the other project in as a submodule21:40
get it working for just the first commit or two, and check that you can clone the result21:41
git-filter-branch *might* need some minor changes to work with that - but it's shell so should be pretty straightforward.21:41
redondos joined21:43
larsl mugwump: Thanks, I'll have a look.21:43
kristoffer joined21:47
Mikachu ToxicFrog: it's just git push <remote> <refname>, no "tag"21:49
ToxicFrog Mikachu: what's the man page on about, then?21:50
Ilari ToxicFrog: If you specifically want to refer to tag (say, you got branch by the same name), then its 'git push remotename tags/tagname'.21:52
Mikachu oh, i didn't know you could say tag <tag>, hm21:55
jengelh kinda ugly though21:56
Mikachu what if you have two branches named "tag" and "test"?21:56
kristoffer left21:57
kristoffer_ joined21:57
mugwump then you probably need to use the full syntax to specify them :)21:57
jengelh what syntax if there is none21:57
Mikachu who came up with that?21:57
jengelh oops21:57
mugwump you can use git push remotename refs/tags/foo21:57
"tag foo" is just a shortcut21:57
Mikachu i guess you could jsut say git push foo tag instead, but you have to remember to put the "tag" last21:58
no, that doesn't work either...21:59
% git branch tag21:59
% git push . tag master21:59
error: src refspec refs/tags/master does not match any.21:59
% git push . master tag21:59
fatal: tag shorthand without <tag>21:59
btw, isn't that error message missing a noun?21:59
mugwump it's missing a verb, yes21:59
why not send a grammar patch21:59
:)21:59
Mikachu how is it missing a verb?22:00
it should have "existing refs." at the end i think22:00
mugwump the second one is missing a verb, the first one is a bit awkward22:00
Yuuhi left22:00
Mikachu ah, the second is a fatal message, not an error message :P22:00
mugwump fatal is a class of error22:01
Mikachu yes, i was just defending my ambiguous referring to the first one earlier :)22:01
mugwump puts away his Pedant's Own™ grammar book22:01
Mikachu it should really say "fatal error:"22:02
marze left22:02
Mikachu lots of things can be fatal22:02
so i guess what we learned is to not call branches "tag"22:02
Debolaz ponders how much effort it'd take to write a new cvs to git converter with support for incremental updates.22:04
_manverumanveru22:06
larsl Debolaz: git-cvsimport does do incremental updates.22:06
schacon joined22:08
programmerq left22:09
drizzd left22:09
CIA-53 left22:10
larsl But it's sloooooow.22:11
mugwump I think the problem with a lot of importers is that they muddle what should be separate phases of conversion: loading the information, mining out and converting history, and then exporting it22:12
charon left22:12
mugwump and then people are left trying to paper over those problems by adding switches to try and change the behaviour of the combined thing, rather than just being able to add some mapping data to a database table and then re-exporting22:13
ec_ left22:13
schacon left22:16
Debolaz larsl: Slowness isn't an issue, it's that it just doesn't work on some repositories. Admittedly, it's hard to make it work right everywhere considering how fucked up CVS really is, so I'm not going to say cvsimport is crap, but it's still a problem for me when it doesn't work where I need it.22:16
CIA-2 joined22:17
jengelh well, it's just fubar :)22:17
deavid left22:17
larsl Debolaz: Yeah, it doesn't work when the CVS repo owner has done weird things in CVSROOT/modules to create "virtual modules" for example.22:18
larsl is trying to work around that at the moment.22:18
jengelh start afresh.22:19
larsl I really don't want to get that far deep in CVS.22:20
redondos left22:23
Debolaz Luckily, I found that tailor was able to convert the cvs repository to git. But it cannot detect branches automatically, so you must explicitly specify them (With a separate configuration section even) or you only get the mainline.22:24
Ilari Doesn't CVS have per-file history (not per-project history like most VCSs do)? :-/22:25
Debolaz Ilari: It has per-file history yes.22:25
redondos joined22:26
larsl That's why importing is such a pain.22:26
johan-s left22:26
larsl git-cvsimport checks out every revision of every file in a repository.22:26
Ilari Trying to approximate it with per-project history could be quite nasty...22:27
Add to that some bizarre tags that are sometimes encountered...22:27
Debolaz And sometimes, there are a few commits that it just seems to be unable to grok.22:28
I suspect it might have something to do with character sets used, but that's really just guessing.22:28
brosner left22:29
ebel left22:31
larsl Hm, git filter-branch looks a bit too complicated for a one-night hack.22:33
I wonder if it would be easier to hack cvsps to merge the rlogs from two CVS repositories.22:33
mugwump that's the problem with conversions isn't it. you think it shouldn't take long22:33
cjb joined22:34
cjb Hi! Is there any way to squash commits (using git-rebase --interactive) once I've already pushed them to a remote repo?22:34
Or does modifying the commit history only work locally?22:34
jengelh it works everywhere, but people won't be happy if you change the timeline22:35
cjb I tend to get an error from the server when I push. Would it work with git push --force?22:35
mugwump perhaps. if that doesn't work you can usually push a delete, then push a "new" branch22:35
cjb I'm only merging several commits into one, rather than changing the timeline.22:35
mugwump that's counted as history rewriting22:36
people who have already pulled will end up requiring a merge22:36
but that's their problem ;)22:36
larsl Bah, screw the history. I'll just add the appropriate versions of the "submodule" in the heads of all branches.22:36
mugwump they should know instead to rebase22:36
advany left22:36
cjb Yeah, I don't think anyone has pulled yet.22:36
mugwump larsl: appropriate, especially if the history is there in the submodule22:37
cjb But I'm a little worried about getting the repo inconsistent.22:37
schacon joined22:37
mugwump people can always come along later and cleanup the history, then use a graft to attach it to their history22:37
larsl mugwump: Yeah, and I need this set up tomorrow when GSoC starts. =)22:37
mugwump right22:38
felipec I can't specify the date in a git commit, right?22:38
vmiklos GIT_AUTHOR_DATE? :)22:39
and GIT_COMMITTER_DATE22:40
felipec vmiklos: so I specify that on env?22:40
cool22:41
mugwump see git-commit-tree(1)22:41
larsl cvsps doing an entire rlog for each incremental cvsimport is a bit annoying though. There should be a way to see what files have changed and just log those.22:41
akibahara left22:43
cjb ok, tried and:22:44
error: remote 'refs/heads/master' is not a strict subset of local ref 'refs/heads/master'. maybe you are not up-to-date and need to pull first?22:45
Is it better to git push --force here, or something different?22:45
it failed:22:47
cehteh guess why it suggests to pull first?22:47
cjb error: denying non-fast forward refs/heads/master (you should pull first)22:47
ng refs/heads/master non-fast forward22:47
cehteh: not because there are changes waiting for me; there aren't.22:47
cehteh no-one else cloned that repository yet?22:48
pygi joined22:48
cehteh its not shared?22:48
cjb I ran git pull moments before, and I can see from gitweb that there are no new commits.22:49
but I'll see if pulling again helps, now that I've rewritten the history.22:49
cehteh well that wont work then22:49
_graham_ left22:49
cehteh with rewriting history you destroy that old branch, you have to be make sure that no one uses that22:50
vmiklos felipec: yes22:50
cjb Ouch. Now I have both the original commits, and extra ones for my history rewriting. Suck.22:50
cehteh: it's a tiny repository with few other committers.22:50
p_bclr joined22:51
cehteh well even with a few, it might break the others22:51
cehteh suggest to switch to a new branch and inform the others to use that too22:52
cehteh when all acknowledged then you can roll over branches22:52
cjb I see. I guess I'll leave it alone, then, thanks.22:52
cehteh (delete the old, rename the new on to the old name)22:52
ckknight joined23:00
ckknight hey all, what would cause git log to hang?23:00
Ilari ckknight: Errorneous (cyclic) grafts data?23:01
felipec and the signers?23:01
ckknight I believe the data is correct, though23:01
I'm calling git log in the update hook23:01
Ilari ckknight: Does the remote repo pass 'git fsck --full'?23:02
ckknight I'm not sure23:02
how can I tell?23:02
kristoffer_ left23:03
mugwump pasky: repo.or.cz[0: 2a01:b0:0:2::]: errno=No route to host23:04
what's your v6 routing like?23:04
Ilari ckknight: Can you figure out what parameters the hook is trying to pass to log? Can you reproduce the hang?23:08
p_bclr left23:08
ckknight Ilari: git log --name-only --pretty=format:23:09
and it seems to reproduce each time a push is tried23:09
basically, what I'm trying to do is use git log to get the list of all files created by the resultant push. it's hackish but it works. I'm open to another way to do it23:10
cjb left23:11
jengelh for i in `git rev-list a..b`; do git log -p "$i"^! | lsdiff; done | sort -u;23:11
where a..b is told you by the push operation23:12
d2dchat joined23:14
Ilari ckknight: For the net added files (so files added and then deleted won't show up): 'git diff-tree -r --name-only --diff-filter=A <old> <new>' (or something like that)...23:15
mithro joined23:15
d2dchat How can I import an existing git repo into my repo?23:16
There will be no concflicts as far as files go23:16
thiago_home left23:16
d2dchat or maybe it's a better idea to make a branch ?23:17
Ilari d2dchat: fetch it as new branch(es) (git fetch), or even merge the branches (git pull)?23:17
igorgue joined23:17
d2dchat Ilari: I can git pull within a repo?23:18
from a remote repo?23:18
Ilari d2dchat: 'git pull <repo> <branch>' fetches and merges branch <branch> from repository <repo>.23:19
ckknight Ilari: what's <old> and <new>?23:19
Ilari ckknight: Revision numbers. IIRC, update hook gets them as parameters...23:19
ckknight Ilari: what if old is 40 0's?23:20
Mikachu then it's a new branch usually23:21
Ilari ckknight: For old version and new version. If old is 40 0s, it is branch creation ('git ls-tree -r --name-only -z <new>'). Also, maybe add -z to that diff-tree command...23:22
ckknight: Also, new may be 40 0s (branch delete).23:22
Mikachu don't you just want git diff --name-only old new?23:25
maybe i should read everything instead of just the first and last few lines ;) nwm23:26
d2dchat Ilari: I did a git fetch but i don't see the files23:27
Ilari: what happened?23:27
fujin left23:27
Ilari d2dchat: 'git fetch' won't merge. If you did 'git fetch <repo> <branch>', that branch wound up being called FETCH_HEAD.23:27
d2dchat Ilari: so how do I merge it where i want it?23:28
Ilari d2dchat: For fetch&merge, use 'pull', not 'fetch'.23:28
d2dchat Ilari: can I run a git pull now instead or do I need to do something with the assets git fetch may or may not have pulled down?23:29
kixx left23:29
Ilari d2dchat: 'git merge FETCH_HEAD'?23:30
d2dchat: That merges in what is stored in FETCH_HEAD.23:30
d2dchat Ilari: is there a way to merge it into a specific directory?23:31
fujin joined23:31
Ilari d2dchat: There's subtree merge in new enough versions (see git-merge(1))23:32
d2dchat Ilari: perhaps my approach is all wrong23:32
I'm used to subversion23:32
where you have trunk, branches, etc.23:32
is there a git way to just have separate trees? I think there is I just don't know how to do it23:33
Ilari d2dchat: Git does not use directories as branches. It has first-class branches.23:33
mugwump d2dchat: ok, first thing to do is to take all your SVN experience and forget it, it's worthless23:33
d2dchat forgets svn experience23:33
redondos left23:34
mugwump good23:34
d2dchat mugwump: no what?23:34
now*23:34
ckknight d2dchat: what you're used to trunk being is now a branch called "master"23:34
mugwump now read the user manual ;)23:34
Ilari d2dchat: 'git branch <name-for-new-branch> FETCH_HEAD'. That would create new branch <name-for-new-branch> from the data you fetched...23:34
d2dchat hehe, is there a way to purge the remote stuff that I pulled? I kinda want to re-arrange everything now23:35
mugwump you don't need to do23:35
d2dchat ah so I don't need to purge that stuff23:35
I can just put it into the new branch right away23:35
mugwump every branch is independent and does not affect the others23:35
Ilari d2dchat: And even the concept of 'branch' is different from SVN: One commit can be in multiple branches simultaneously, branches are not necressarily linear, etc...23:38
d2dchat noice23:39
OK I just did a git branch public FETCH_HEAD23:40
and a git status23:40
and now all my files on master did something23:40
Ilari d2dchat: It should now show up in 'git branch'...23:41
d2dchat Ilari: do I have to git commit and push first?23:41
ah I see it23:41
Ilari d2dchat: No need to commit after changing branches. Branches are first-class, not some brain-damaged SVN branches-as-directories stuf...23:42
d2dchat :)23:42
schacon left23:43
ec joined23:43
d2dchat Ilari: now how do I switch to a branch?23:45
Ilari d2dchat: 'git checkout <branchname>'.23:46
ben_h joined23:46
d2dchat this is sweet lol23:47
what is origin ?23:49
robin left23:49
Ken69267 joined23:50
Ken69267 is it possible to clone a branch?23:51
rather than master23:51
Ilari Ken69267: Those should show up in 'git branch -r', but don't get local branches by default.23:52
d2dchat git push origin public.. nice23:52
I love it23:52
:)23:52
Ken69267 Ilari: aha, thanks23:53
d2dchat Ilari: thx23:53
chjunior joined23:54
jjlee left23:55
bdiego left23:59

Logs Search ←Prev date Next date→ Channels Documentation