IRCloggy #git 2009-10-26

Logs Search ←Prev date Next date→ Channels Documentation

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

2009-10-26

j416 joined00:01
neunon left00:02
neunon joined00:02
fcuk112 joined00:03
bremner_ joined00:03
bremner__ joined00:07
drubies_ joined00:09
Garen left00:09
icwiener left00:10
eno left00:10
bremner__ left00:10
javatexan left00:10
flazz left00:11
sgh left00:12
eno joined00:14
fualo_ left00:16
ChenKaie joined00:20
bremner_ left00:22
fualo_ joined00:23
drubies left00:24
babilen left00:28
JasonWoof left00:28
JasonWoof1 joined00:28
JasonWoof1JasonWoof00:29
hyperair joined00:31
tbuehlmann left00:31
Yuuhi left00:32
mithro left00:33
dennda left00:34
ChenKaie_ left00:34
jlilly left00:38
jlilly joined00:40
muthu joined00:40
corni left00:42
Adlai` joined00:42
onigiri left00:43
krynnotaur left00:44
Adlai left00:45
Adlai`Adlai00:45
martianlobster left00:46
Garen joined00:48
javatexan joined00:49
rchavik joined00:50
davegb3 joined00:52
drubies_ left00:53
orafu left00:55
OuLouFu joined00:55
OuLouFuorafu00:55
davegb3davegb3|00:58
NET||abuse left00:59
NET||abuse joined00:59
drubies joined01:00
chrisr joined01:00
kentnl_ left01:00
chrisr What is the consequence of not committing your changes before switching to another branch? Ive only just started using git today and i was wondering what would happpen01:00
kardan| joined01:00
chrisr does anyone know01:00
?01:01
FauxFaux Try it and see.01:01
sitaram the uncommitted changes get carried along01:01
kent\n joined01:01
sitaram as long as, for the files you changed, there are no differences between the branch you came from and the one you are going to01:01
chrisr So the file stays the same? What if the files are massively different?01:02
jinzhu joined01:02
sitaram massively different from what?01:03
chrisr If the file i change and dont commit is massively different than the same file on the branch I have changed to01:03
What happens then?01:03
If I then commit on the branch i have changed to, will I override the file in that branch?01:04
This is hard to describe!01:04
ereslibre left01:04
cytrinox_ joined01:05
sitaram chrisr: read what I said above carefully. if the from-branch and to-branch have the same copy of *this* file, it doesn't matter01:05
chrisr yeah, but what if the file isn't the same between branches, what happens then?01:06
sitaram try it and see01:06
chrisr: also http://permalink.gmane.org/gmane.comp.version-control.git/104457 might be useful, though the question was asked in a different context01:06
kpreid_ left01:06
sitaram chrisr: hint: git will try very, very, hard no to lose any "in progress" work, and you have to explicitly tell it to do so in most cases01:07
chrisr ah ok, thats good to know.01:07
kardan_ left01:07
shruggar left01:08
scarabx joined01:10
chrisr it still doesn't explain what happens to the changed file in the branch i am changing to.01:10
Ilari chrisr: It if the committed file is the same in both, the changes get carried over. If they aren't, the checkout will abort.01:11
DrTrevorkian_ joined01:12
Ilari chrisr: Working tree changes are not part of any branch. Nor are staged changes.01:12
vinse joined01:13
chrisr llari: I see, so that allows you to decide which branch to make the change on after you have made a change01:13
davey_ joined01:13
chrisr makes sense01:13
DrTrevorkian left01:14
Ilari chrisr: There's also two switches: -f makes it discard your changes and -m makes it attempt to merge them (may produce conflicts, and is as such bit of russian roulette).01:14
chrisr ok cool01:15
what does "git reset" do? and "git reset --hard"?01:15
sitaram http://sitaramc.github.com/concepts/soft-hard-mixed.html01:15
might help; once you've read the man page01:16
shd chrisr: "git reset" undoes any 'git add' commands you might have done before the commit01:16
chrisr: 'git reset --hard' undoes your git add commands and resets files to their original state before modifications01:16
DrTrevorkian_ left01:16
shd chrisr: git reset doesn't touch any files, only undoes the staging (that is, git add)01:16
name left01:16
DrTrevorkian_ joined01:17
Ilari Also any 'git rm --cached's01:17
shd chrisr: in addition, git reset and git reset --hard may place the branch pointer to arbitrary revision01:17
chrisr: often one does: git reset HEAD^ after a bad commit, then git add && commit again01:17
cytrinox left01:18
cytrinox_cytrinox01:18
relix left01:18
donpdonp joined01:18
Ilari git commit --amend01:18
n3m left01:18
chrisr is there an easy way to remove all the .svn folders from all my brances? I still want them to exist, but not in git01:18
donpdonp ive got all these untracked files i want to delete. git reset --hard doesnt remove them.01:18
shd donpdonp: git clean --help01:18
donpdonp shd: thx01:19
Ilari chrisr: Import using git svn?01:19
chrisr llari: too late for that01:19
a389742 joined01:19
simosx left01:19
chrisr I only found out about git-svn after i had been using git a couple of hours01:19
DrTrevorkian_DrTrevorkian01:20
Mezner joined01:21
donpdonp left01:21
Ilari chrisr: Export your changes as patches, import using git svn and apply the patches?01:21
chrisr ok ill do that?01:22
Ilari chrisr: Useful commands: git format-patch and git am01:23
abw_ left01:29
paltman94 joined01:30
xyz left01:30
coolcat left01:31
smuf left01:32
krynnotaur joined01:34
meanburrito920_ left01:36
jinzhu_ joined01:37
jinzhu left01:37
Chillance left01:37
meanburrito920_ joined01:38
abw_ joined01:38
krynnotaur left01:39
KIAaze left01:41
hyperair left01:42
schmukkk joined01:46
clever how do i undo changes to a local file, to sync it back to the git repo?01:51
git revert?01:51
Ilari clever: 'git checkout -- <file>'.01:51
gartenstuhl left01:53
hyperair joined01:59
johnmclane left02:00
clever Ilari: thanks02:00
j416 left02:00
aziz left02:01
warthog9 joined02:01
jinzhu_ left02:02
intripoon left02:03
kingfishr left02:07
sagsousuke left02:10
murph__ joined02:11
kpreid_ joined02:11
patcito left02:13
kingfishr joined02:18
davey_ left02:18
kingfishr left02:19
kingfishr joined02:19
jschoolcraft left02:19
davey_ joined02:20
davey_ left02:22
murph_ left02:27
lulika left02:33
sergiodj_ joined02:34
sergiodj left02:34
cenuij left02:34
squentin left02:36
upul joined02:39
hyperair left02:43
hyperair joined02:43
jepler left02:45
jepler joined02:49
rektide i'm trying to find out which tip of a remote is the most recent02:51
any suggestions ?02:51
hagabaka joined02:52
hagabaka I had a git tracked project, but for some reason created a new directory to "rewrite" it, but I still ended up copying a lot of the old code. how can I let git track the new directory and detect some of the old code if possible?02:54
DrTrevorkian left02:57
paltman94 left02:57
warthog9 left02:58
warthog9 joined02:58
Ilari rektide: Fetch them and use merge-base to compare?03:01
kpreid_ left03:04
kpreid_ joined03:04
zheng joined03:04
saintdev joined03:08
muthu left03:09
sheriff joined03:09
sheriff I want to run git status on a directory to which I don't have write permissions03:09
But I'm getting an error about not creating a lock file03:09
Pewpewarrows joined03:09
sheriff Any suggestsions? I want to get the key of the last commit in that dir03:10
daddius joined03:12
impulze hm where do i find parsecvs to import cvs into git?03:15
seems like all mirrors are down03:15
sitaram sheriff: "key" of the last commit? do you mean the hash/SHA1? you can try 'git log'; git status is more for looking at uncommitted stuff03:15
sheriff Thanks - I found it in FETCH_HEAD in the end, but git log looks like it works too03:17
Ilari impulze: git://repo.or.cz/parsecvs.git maybe?03:20
saintdev i have a branch that introduces some new files. i just merged in changes from upstream, and this broke something, how do i bisect this?03:20
ie: normally bisect checks out a commit in upstream, but i can't test it because it doesn't contain the new files.03:20
cytrinox_ joined03:20
Ilari saintdev: If both parents of merge work but the merge doesn't then that's pretty much mismerge.03:21
impulze Ilari: hm last commit in march, is that still the way to go?03:21
mumutou joined03:21
rchavik1 joined03:23
Ilari impulze: Might very well be...03:23
rchavik left03:26
impulze hm also that clone doesn't seem to be compilable03:26
rchavik1rchavik03:26
bcardarella joined03:26
saintdev Ilari: so it isn't possible (other than manual search) to figure what commit in another branch broke something?03:27
rchavik1 joined03:28
rchavik left03:30
rchavik1rchavik03:30
sparta joined03:32
sparta is there a git diff command to get the recursive difference between 2 local repositories03:33
?03:33
mumutou yes03:34
epoxy left03:35
cedricv joined03:35
Ilari saintdev: The problem is that if the commits themselves are not testable for the bug, bisect can't locate the offending commit...03:36
cytrinox left03:36
cytrinox_cytrinox03:36
mumutou sparta:you can use the git command as "git diff branch1..branch2"03:36
zheng left03:37
Ilari Just take into account that diff can only diff two commits that both exist locally.03:37
(if diffing commits).03:37
sitaram sheriff: FETCH_HEAD doesnt necessarily show you what I think is meant by "last commit in that dir" (even assuming "dir" meant "branch"). It was a coincidence that your last *operation* was probably a pull which resulted in a fast forward merge. Ask if you need me to explain this better03:37
sparta what if i want to find diff between 2 codes in 2 different local repositories using git?03:38
flazz joined03:38
Ilari sparta: Fetch the branch from one to another first.03:38
sitaram sparta: you'll have to fetch one into the other and then diff03:39
saintdev Ilari: thanks, didn't think there was a way, but wanted to ask first ;)03:39
Theravadan left03:40
sparta whats the exact command for fetch?03:41
Ilari saintdev: Well, bisect is binary bisection search. Perhaps use similar algo for finding the offending commit?03:41
joeytwiddle left03:41
Ilari sparta: 'git fetch <remote> <branch>'. That fetches the branch as FETCH_HEAD.03:41
saintdev Ilari: yeah, that was the plan ;)03:41
sparta ok thanks03:44
m0 left03:48
jonmasters left03:48
daemoen left03:48
galador left03:49
meanburrito920_ left03:49
galador joined03:49
LRN left03:50
daemoen joined03:50
m0 joined03:50
jonmasters joined03:50
_jason553839 joined03:51
tjafk joined03:52
m0 left03:53
daemoen left03:53
_|Nix|_ left03:53
jonmasters left03:53
_|Nix|_ joined03:53
m0 joined03:53
daemoen joined03:54
epoxy joined03:54
timj left03:54
jonmasters joined03:55
cedricv left03:56
kpreid_ left03:57
kpreid_ joined03:57
bcardarella left03:58
saintdev left04:02
bcardarella joined04:04
eno left04:08
_jason553839 left04:09
eno joined04:11
javatexan left04:15
engla left04:17
Creap_ joined04:20
nadim_ joined04:21
JackWinter2 joined04:21
jonmasters left04:21
m0 left04:21
daemoen left04:21
ChenKaie left04:21
fcuk112 left04:21
lresende left04:21
Aikawa_ left04:21
ryoma left04:21
ia left04:21
JackWinter left04:21
pgalbraith left04:21
kmamykin left04:21
asksol left04:21
jaalto left04:21
Swimming_Bird left04:21
corecode left04:21
cantoma left04:21
BTK left04:21
Helios- left04:21
Aestas left04:21
\\steve left04:21
cxreg left04:21
jujule2_ left04:21
tchan left04:21
henr_k left04:21
vkroll left04:21
Creap left04:21
fr| left04:21
nadim left04:21
tazle_ left04:21
thermal_ left04:21
Thumper_ left04:21
a-atwood left04:21
mugwump left04:21
Iff left04:21
agrippa left04:21
lharc left04:21
kyron left04:21
johnjay left04:21
ricky left04:21
TDJACR left04:21
tomoyuki28jp left04:21
fr joined04:21
johnjay joined04:22
ChenKaie joined04:22
BTK joined04:22
kyron joined04:22
corecode joined04:22
vkroll joined04:22
Thumper_ joined04:22
shad joined04:22
fcuk112 joined04:22
jujule2 joined04:22
ricky joined04:22
Aestas joined04:22
Iff joined04:22
m0 joined04:22
cxreg joined04:22
segher left04:22
\\steve joined04:22
henr_k joined04:22
Aikawa joined04:23
krynnotaur joined04:24
asksol joined04:26
kmamykin joined04:26
pgalbraith joined04:26
tchan joined04:26
Helios- joined04:26
lresende joined04:26
agrippa joined04:27
scarabx left04:27
ryoma joined04:27
bcardarella_ joined04:28
bdimcheff left04:28
Swimming_Bird joined04:29
bcardarella left04:30
bcardarella_bcardarella04:30
loops joined04:30
Mezner left04:31
ahf left04:31
lresende left04:31
KingBug left04:31
tiglionabbit joined04:31
ahf joined04:32
KingBug joined04:33
thermal_ joined04:34
lharc joined04:34
ia joined04:35
tomoyuki28jp joined04:35
cantoma joined04:37
scarabx joined04:37
daemoen joined04:37
Jconyers joined04:38
wanders_ joined04:40
wanders left04:41
rchavik1 joined04:41
rchavik left04:42
rchavik1rchavik04:42
daddius left04:42
scarabx left04:43
Rolenun left04:44
reidab joined04:46
kpreid_ left04:50
kpreid_ joined04:50
JoeConyers left04:52
cedricv joined04:52
priidu joined04:56
ArdRigh joined04:58
lucs joined04:59
FunkeeMonk joined05:00
_jason553839 joined05:00
sparta left05:01
abms1116 joined05:02
flazz left05:03
panpainter joined05:08
panpainter left05:08
tierney joined05:10
tierney left05:10
DrTrevorkian joined05:11
univate left05:12
elliottcable joined05:15
Garen left05:16
univate joined05:18
mcdebugger joined05:21
_jason553839 left05:24
mumutou left05:24
amigojapan joined05:26
Dude-X joined05:27
RobertLaptop_ joined05:27
RobertLaptop left05:27
amigojapan hi, I am trying to clone a repository on a remote linux machine using tortoise.... what should I enter in the url part?05:27
RobertLaptop_ left05:28
RobertLaptop joined05:28
bsdvodsky joined05:31
chupino joined05:31
cloudhead left05:31
girishr_ joined05:32
chupino left05:33
sitaram amigojapan: I have no clue about tortoise, but man git-clone will show you a bunch of example URLs somewhere near the bottom (search for "ssh:" on that web page); I imagine tortoise will use the same URLs05:35
Gitbot amigojapan: the git-clone manpage can be found at http://git.or.cz/man/git-clone05:35
amigojapan thanx05:35
sitaram amigojapan: URLS to be precise05:36
amigojapan: oops; I mean http://www.kernel.org/pub/software/scm/git/docs/git-clone.html#URLS05:36
amigojapan ok, anyway I am going to eat, try it after I get back, thanx guys05:36
thanx sitaram05:36
sitaram you're welcome!05:36
yhager joined05:41
drubies left05:41
cedricv left05:41
_jason553839 joined05:42
kpreid_ left05:43
kpreid_ joined05:43
Adlai` joined05:46
ThellThell|Away05:46
hyperair left05:46
Adlai left05:47
Adlai`Adlai05:47
Dude-X whats' the default install directory of git in debian linux? and where can i find the config files05:52
Adlai Dude-X: try `which git' at the shell05:52
Dude-X ah which05:53
Adlai `man git-config' to read about the system-wide and personal config files.05:53
Gitbot Adlai: the git-config manpage can be found at http://git.or.cz/man/git-config05:53
Dude-X that's the command not "where'05:53
Fissure Dude-X: if it's a binary, and not essential, and not something that only root should use, it goes in /usr/bin05:54
sprasanna joined05:54
Fissure see: filesystem hierarchy standard05:55
kingfishr left05:55
Dude-X basically i want to set the set name for the remote, so that on my home system i can clone the repo05:55
agenteo left05:58
karmi joined05:59
bcardarella left06:01
mugwump joined06:02
a-atwood joined06:02
jonmasters joined06:02
roop joined06:03
abms1116 left06:03
tazle_ joined06:05
JoeConyers joined06:07
JoeConyers left06:08
LRN joined06:09
a389742 left06:09
_jason553839 left06:09
Adlai left06:14
Adlai joined06:14
epoxy left06:15
maleknet joined06:16
Jconyers left06:16
warthog9 left06:16
gunmuc joined06:17
saurabhverma joined06:18
SunilThaha joined06:21
NemesisD joined06:23
NemesisD hi all. ive got changes on a separate branch and i want to merge it into master. i do a git diff and i think it will eliminate some of the changes i made in master. they don't conflict at all but im afraid if i checkout master and merge the other branch, it will just toss them out. is there a way to force a conflict or something so i can make sure my changes to master stay?06:24
univate left06:25
univate joined06:26
sheriff left06:27
tasslehoff joined06:28
jceb joined06:29
Cesario joined06:31
Tuomas joined06:32
Adlai man git-merge06:34
Gitbot Adlai: the git-merge manpage can be found at http://git.or.cz/man/git-merge06:34
SunilThaha NemesisD: is the edit is on the same line of a file on both branches, you will get a conflict06:34
NemesisD im on the manpage now, im looking at the strats but all of them seem to do things automagically06:34
Adlai NemesisD: look at the --no-commit option06:34
NemesisD SunilThaha: i don't think so, when i do a gif on the files i see '-' before my master lines that i don't want to lose with no + nearby06:35
Aestas left06:35
NemesisD Adlai: ok, will --no-commit leave those lines in the file or will i have to look at an older version of the file or something?06:35
SunilThaha you could rebase with master06:36
Adlai no, it'll make the merge, just refrain from committing.06:36
kpreid_ left06:36
kpreid_ joined06:36
Adlai I don't entirely understand your situation though. It sounds as though you'd get a merge conflict.06:36
NemesisD SunilThaha: my colleague doesn't have git, i checked out his branch on my machine, rebased with master, pasted his files into the dir, haven't even committed his changes to his branch yet06:37
Theravadan joined06:37
SunilThaha Adlai: I think the master has a line, which git deleted in the branch06:37
s/git/got06:37
Adlai so that line will get deleted when they merge06:37
SunilThaha yes06:37
Adlai unless the master also touched that line06:37
NemesisD wait this shouldn't happen if my rebase with master was successful06:38
SunilThaha yes !!06:38
Adlai in which case there'll be a conflict06:38
NemesisD because it would add those non-conflicting lines06:38
SunilThaha Adlai: no ...06:38
Adlai no?06:38
SunilThaha since the line in the master did not change .. .06:38
there won't be a conflict06:38
Adlai so it'll just get deleted.06:38
SunilThaha yes06:38
Adlai doesn't really see what the problem is...06:39
jceb left06:39
niki left06:40
SunilThaha Adlai: master has 10 lines, he branches out, deletes line 5, and adds line 11,1206:40
warthog9 joined06:40
SunilThaha when you merge with master .. line 5 gets deleted06:40
a389742 joined06:40
SunilThaha right?06:40
nighthwk1 left06:41
ixti joined06:41
Adlai I think so...06:41
NemesisD wow. looking at the diff i suppose i should fix his mistakes before doing anything06:41
SunilThaha he doesn't want that to happen06:41
NemesisD: you could branch out from master06:41
and to fix the mistake06:41
hyperair joined06:42
SunilThaha then merge both the branches with the master06:42
Adlai: he doesn't want the line 5 to go away06:42
univate left06:43
Adlai so you merge without making a commit, reset half of it, and commit.06:43
(assuming you have a recent git with 'reset -p')06:43
karmi left06:45
krawek left06:45
krawek joined06:45
NemesisD i think this will be okay06:47
every time he sends me code he keeps changing all the curly braces on functions to start on a different line than the param list :|06:48
but i have git and i control the repo so i put em back :D06:48
Adlai NemesisD: if it's your project, let him know what the coding style is (I find it helps to have a style file for clarity and consistency), and explain that contributions to your project should comply with your style preferences.06:51
loops left06:51
dunolie left06:53
Axius joined06:53
NemesisD Adlai: school project, i really don't have the authority to do that, so we must result to passive aggression for the time being06:55
BeerSerc left06:55
NemesisD also, git ended up removing lines from my master in the merge :|06:55
SunilThaha NemesisD: You could use the astlye06:56
NemesisD whats that now?06:56
SunilThaha astyle --indent=spaces=4 --brackets=linux \06:56
--indent-labels --pad=oper --unpad=paren \06:56
--one-line=keep-statements --convert-tabs \06:56
--indent-preprocessor \06:56
`find -type f -name '*.cpp'` `find -type f -name '*.h'`06:56
NemesisD: its a tool/utility to format the source06:57
kkoehne joined06:58
NemesisD that sounds friggn awesome06:59
univate joined06:59
aliceinwire joined06:59
FunkeeMonk left07:00
maleknet left07:02
maleknet joined07:02
sde_antrix2 joined07:03
Azeroth-Working joined07:03
rchavik1 joined07:04
Octalot left07:05
da5id left07:06
abms1116 joined07:06
Azeroth-Work left07:07
hyperair left07:08
ludde joined07:11
hyperair joined07:12
rchavik1 left07:12
fluxusps joined07:12
alireza_ joined07:13
elTigre joined07:15
univate left07:15
Pupeno joined07:17
cedricv joined07:17
murph__murph07:18
rchavik left07:20
reidab left07:20
galderz joined07:21
thiago_home joined07:21
rchavik joined07:22
girishr_ left07:23
roop_ joined07:23
rchavik left07:25
dunolie joined07:26
elliottcable left07:26
krawek left07:26
Adlai left07:26
hyperair left07:26
Adlai joined07:27
Pupeno left07:27
RDev joined07:28
mithro joined07:28
RDev hi07:29
j416 joined07:29
kpreid_ left07:29
kpreid_ joined07:29
maleknet left07:29
bentob0x joined07:30
univate joined07:31
RDev Can somebody suggest me a Project-/Time-/Version/Issue Management and a Wiki? I'm starting a new project with 5 people. We will develop a midsized PHP applikation for the next 6months.07:31
we work on linux/windows and macintosh machines07:32
relix joined07:32
khmarbaise joined07:33
ph^ joined07:33
thiago_home well, Git for version management07:34
then look at what issue-management tools are available with Git07:34
the rest, I never use, so I can't help you07:35
univate left07:35
RDev hmm07:36
I'm trying to find the optimal working-environment and tools07:36
hyperair joined07:36
ajonat left07:37
roop left07:38
VVSiz joined07:40
thiago_home Git and the rest :-)07:41
DrTrevorkian left07:41
thiago_home for project management, we're simply using a table in the wiki07:43
gitorious has wiki support if you want, otherwise just use mediawiki07:43
tango_ joined07:44
tango_ left07:45
tango_ joined07:45
ph^ left07:45
sitaram RDev: take a look at indefero.com -- sort of like googlecode + git integration (they support other VCSs also I believe, though I only care about git)07:46
Affero GPL I think or maybe plain GPL07:46
mastro joined07:46
j416 left07:46
ph^ joined07:47
RDev thiago: I'm doing this for a highly professional Software-Developement course at the university. Where we shall use all Software-Development Standards available.. unfortunately nobody tells us which tools,IDE, vcs, etc..07:47
currently my problem is to find a way to organise all of the TODO's from a UML Diagramm and a Mind-Map to a realistic workflow07:48
reidab__ joined07:51
da5id joined07:52
thiago_home in my experience, there is no connection07:54
UML and such things are to keep professors and clients happy that they are getting something07:55
Fullmoon joined07:55
thiago_home I'm sure other people have uses for them, though07:55
sitaram the larger diagrams, once printed, can be used for my kids school projects (the reverse side)07:55
so dont go knocking UML ok?07:56
reidab__ left07:58
onigiri joined07:58
mtkd_ joined07:59
RDev hmm..08:00
ryoma left08:00
sitaram ok... considering the dead silence, I'd better admit I was half-joking :)08:00
Weasel[DK] joined08:03
tasslehoff sitaram: good morning. mind talking a bit about the recipe you gave me friday? I've read some tutorials about git, so I understand more of it now :)08:07
NemesisD left08:09
robin joined08:09
robinGuest5866008:10
karmi joined08:10
univate joined08:11
yaotti joined08:13
yaotti_aw joined08:13
yaotti_awyaotti_08:13
da5id left08:13
cilly joined08:13
nitrate joined08:16
nitrate left08:16
univate left08:16
reidab__ joined08:17
dominikh left08:18
mcella joined08:20
reidab___ joined08:20
reidab___reidab08:21
gunmuc1 joined08:21
kpreid_ left08:22
kpreid_ joined08:22
reidab___ joined08:23
robinr left08:23
psankar joined08:25
RDev left08:25
dpino joined08:26
thiago_home left08:26
johan-s joined08:26
j416 joined08:28
Axius left08:29
reidab left08:29
univate joined08:30
shruggar joined08:31
transplant joined08:31
mithro left08:32
ntoll joined08:32
Guest58660 left08:33
ciskje joined08:34
gunmuc left08:35
reidab__ left08:36
zoniq joined08:38
reidab___ left08:40
gunmuc1 left08:40
ph^ left08:41
j416 left08:42
j416 joined08:42
gunmuc joined08:43
NET||abuse left08:48
rchavik joined08:48
chrisr left08:48
omenking joined08:48
univate_ joined08:48
gretch joined08:48
ph^ joined08:49
univate left08:50
karmi left08:50
DavidKlein joined08:50
sitaram tasslehoff: hi; I'm at work so I'll be in and out but sure...08:51
hyperair left08:51
tasslehoff sitaram: good. http://pastebin.com/m31c04746 (in case you don't have it at hand).08:52
sitaram yup08:52
tasslehoff sitaram: when you update the local repo and the user machines, why do you fetch instead of pull? you have to merge afterwards anyway, right?08:53
sitaram tasslehoff: no particular reason except that I usually want to do the merge manually -- I find I often don't use the defaults and specify everything explicitly (like 'git push origin master' instead of 'git push')08:55
tasslehoff: so I just write it like that08:55
psoo joined08:55
sitaram tasslehoff: if I recall, you have an upstream, but you won't be pushing anything back to it -- is that correct?08:56
xenoterracide left08:58
Theravadan left08:59
dunolie left08:59
hyperair joined09:01
tasslehoff sitaram: that's correct09:03
sitaram tasslehoff: and you want one central location where your developers can pull from / push to09:04
right?09:05
tasslehoff sitaram: I tried making another cookbook without the mirror, using branches. does this look ok? http://pastebin.com/d62d2697409:05
sitaram: yes09:05
sitaram tasslehoff: I can't recall if your devs also have direct access to the internet (and thus this upstream repo)...09:05
looknig09:05
looking09:05
tasslehoff thanks.09:06
DavidKlein left09:06
univate_ left09:07
univate_ joined09:07
sitaram tasslehoff: my first comment is depending on the scale of your development, you will need "topic branches" that the devs will create. Example "bug-1234" might be a topic branch made to fix that bug. These topic branches will be pushed to the central server for testing/QA/validation etc09:08
tasslehoff: i.e., they shouldn't be doing all the work off of mystable -- things will become a little messy unless they're all small, quick, localised, changes09:08
tasslehoff: this also bears upon the fact that your flow does not have any "developer pushes his work up to the server" piece09:09
tasslehoff sitaram: an important not I have forgotten. we will most likely not change much in this software09:09
it's like a third-party product that I want an extra level of stability control over.09:09
sitaram tasslehoff: that's fine, then you're saying you may not need topic branches -- fair enough09:10
tasslehoff: do you know what a "bare" repo is?09:10
tasslehoff sitaram: barely (pun intended). I checked the manpage after you gave me your suggestion09:11
perez joined09:11
Jurko joined09:11
sitaram tasslehoff: any repo that someone will be *pushing to* (as opposed to only pulling from) should ideally be a bare repo09:11
tasslehoff: http://sitaramc.github.com/concepts/bare.html has a good example09:11
ab3 joined09:11
_Ikke_ a bare repo is a repository that only has the .git directory, no working directory09:11
sitaram _Ikke_: true but that usually does not help to understand why it is needed :)09:12
alireza_ left09:12
_Ikke_ sitaram: indeed, thats the next step09:12
ashH left09:12
sitaram _Ikke_: :)09:12
maleknet joined09:13
joeytwiddle joined09:13
_Ikke_ sitaram: is it btw possible at all to push to a none bare repo?09:13
tasslehoff sitaram: I'm following (I think). The devs might have to do some pushes to the server repo.09:13
sitaram tasslehoff: your paste line 22/23/24 says "merge changes from stable over to mystable" seems to indicate that you will do this *on* this repo, which in turn means it is not bare. I suggest you do that on some other repo (maybe one senior dev does that on his workstation and updates "mystable" on the server)09:13
_Ikke_: sure it is...09:13
yaotti left09:14
_Ikke_ sitaram: ah ok, I thought it gave an error when I tried that09:14
sitaram _Ikke_: from 1.7 or so it will, if you push to the currently checkedout branch09:14
_Ikke_: right now its a big bad warning09:14
(I think)09:14
_Ikke_ sitaram: ah ok. Clear.09:14
tasslehoff sitaram: sounds good, since the senior dev (me) will have to compile and test on hw anyway.09:15
sitaram tasslehoff: that will make this repo a bare repo -- it gets dev and stable from the outside, and it gets mystable from the people inside (likely only the senior dev)09:15
dunolie joined09:15
kpreid_ left09:15
kpreid_ joined09:15
tasslehoff sitaram: ok09:16
kumbayo joined09:16
Dude-X left09:17
sitaram tasslehoff: you still have to decide how your normal devs should update mystable. They can push to some other branch and the senior dev -- after testing/qa -- can merge those onto the official "mystable" (this is what *I* would do, unless the team is very small and communicates well)09:17
tasslehoff: the other alternative is for everyone to be able to push to mystable, which is not a bad thing in small, well-knit teams09:17
tasslehoff sitaram: I choose the last one. for now we are three guys sitting next to eachother :)09:18
sitaram tasslehoff: agreed09:18
tasslehoff: the latter means that the "senior dev" does not have any special privs as far as the system is concerned -- anyone can do what he does, although in practice -- like the situation you said -- they wont09:18
GodEater left09:18
GodEater joined09:18
giallu joined09:19
simosx joined09:19
sitaram tasslehoff: one suggestion: turn on receive.denyDeletes and core.logAllRefUpdates -- this ought to protect you in case someone makes a mistake09:20
transplant left09:20
babilen joined09:21
Pupeno joined09:22
tasslehoff sitaram: ok09:23
sitaram it wont tell you "who" but it'll tell you when, and more important it'll keep a record of any refs that accidentally got blown away09:23
(for some 30 days or so anyway... there's some time limit in the config somewhere)09:23
xenoterracide joined09:24
aatanasov joined09:24
Axius joined09:25
JackWinter joined09:26
TDJACR joined09:27
tasslehoff sitaram: ok. new try at the server workflow : http://pastebin.com/ma469b0a09:27
tono left09:28
sitaram tasslehoff: I dont get it... who and where will you be merging "stable" and "mystable"?09:29
cenuij joined09:29
Fullmoon left09:30
tasslehoff sitaram: it's probably me that's not getting it :)09:30
ramlev joined09:30
sitaram tasslehoff: let me write up something; give me about 20 min -- getting into a meeting09:30
Grahack joined09:31
eevar2 joined09:32
jas4711 joined09:33
lucsky joined09:33
univate_ left09:34
lucsky 'morning09:34
univate joined09:36
JackWinter2 left09:36
ab3 left09:37
bsdvodsky left09:38
tasslehoff sitaram: here's a note on how I thought our discussion turned out :) http://pastebin.com/d208c1fc009:40
j416 left09:41
Pupeno left09:41
Stravy joined09:41
ruxpin joined09:45
psankar left09:45
ruxpin hi, I need some advice09:45
I stashed my master and checkouted a branch09:45
then did some unsuccessful merge09:45
and now I want to undo it09:45
but I want to make sure that the master stash stays put09:45
is "git checkout --hard HEAD" safe?09:45
tbf joined09:46
tasslehoff read "reflog" as "re-flog", and thought it was a severe "blame"09:48
da5id joined09:48
univate left09:48
corni joined09:50
intripoon joined09:51
psankar joined09:53
ruxpin ok, I took a backup and did the operation. stash was ok09:54
sitaram tasslehoff: http://pastebin.com/m55fec7c809:54
tasslehoff: bonus: http://imagebin.ca/view/Yh8moN.html09:54
tasslehoff: note the arrow in that picture; which ones are single headed and which ones are double09:55
Yuuhi joined09:55
sitaram tasslehoff: comments on your paste http://pastebin.com/d208c1fc0 -- line 3: you cant pull when using a bare repo (pull implies merge, which requires a working tree and human intervention in case of conflict), otherwise it's largely the same as what I posted except I gave commands09:56
tasslehoff sitaram: nice. and that image is quite correct :)09:56
sitaram graphviz++ :)09:57
http://pastebin.com/d699f5a1b if you want the source of that little thing!09:57
tasslehoff :)09:59
univate joined09:59
froschi joined10:00
roop_ left10:00
tbf left10:03
jspiros left10:04
capndiesel joined10:04
jspiros joined10:05
tbf joined10:06
kpreid_ left10:08
kpreid_ joined10:09
elTigre left10:11
__iron joined10:16
cehteh left10:18
tasslehoff sitaram: hm. I'm having a bit of trouble already on the first step :)10:18
sitaram ok which one10:19
j416 joined10:19
schierbeck joined10:19
Axius left10:19
tasslehoff I do a "git clone --bare", but then I can't say "origin/dev" afterwards when I create the branch?10:19
sitaram I guess a bare clone doesn't have origin/ -- I forgot :-)10:20
engla joined10:20
tasslehoff sitaram: ok. just wanted to check :)10:20
sitaram actually neither does it have an origin, it seems... hmm!10:21
actually the way to do it is to create a bare repo, (not a clone), add a remote called origin, and fetch... testing10:22
hyperair left10:23
hyperair joined10:23
Axius joined10:24
sitaram yeah that seems to work fine; changing doc10:24
jschoolcraft joined10:25
sitaram tasslehoff: http://pastebin.com/m61b3d468 -- sorry; still not quite tested (am juggling a few different things at the same time right now) so test it out10:27
amigojapan_ joined10:28
muguruma1kenseimuguruma-kensei10:28
tasslehoff sitaram: I think I can figure out what I need from your previous paste now10:29
thanks a _lot_10:29
sitaram no problem10:29
"previous paste"? you mean the last one... http://pastebin.com/m61b3d468 I assume10:29
(not the one before)10:29
gretch left10:30
Tama00 joined10:34
Tama00 Hey10:34
froschi left10:34
corecode can i change author info with rebase or amend?10:36
scrooloose left10:36
ArdRigh left10:37
scrooloose joined10:38
sitaram corecode: latest commit; git commit --amend --author should do. Others; you can rebase -i, choose "edit" so it stops, do the commit --amend --author, and proceed10:38
corecode i see10:38
i did a format-patch + edit10:38
sitaram probably easier; for some silly reason its asking for an existing commit with the new author name I want to use :)10:40
mtkd_ left10:40
corni left10:40
corni joined10:41
sitaram probably to prevent horrible typos in manually typed stuff10:42
ihoka joined10:43
eevar2 how do you guys back up your git repos? we have ~a dozen shared repos, some of them with a bit of data, on a central server, but only 1-2 of them are actually used regularly10:44
parasti joined10:46
aliceinwire left10:46
amigojapan left10:46
n3m joined10:47
eevar2 worth taring them up individually and only keeping ones with changes? -- we probably should keep a few old backups around, in case someone decides to do some creative history-rewriting?10:47
aliceinwire joined10:47
patrikf joined10:47
gasbag joined10:48
gasbag left10:49
yaotti joined10:51
eevar2 ^^ or is there a failsafe method to prevent commits that change history?10:53
sitaram eevar2: last question first: yes: man git-config and look for receive.denyNonFastForwards10:54
Gitbot eevar2: the git-config manpage can be found at http://git.or.cz/man/git-config10:54
eevar2 thanks10:54
name joined10:55
mattayers joined10:58
sitaram eevar2: my "backup" is a script that clones any new repos, and git fetch + git including tags in old ones10:58
dominikh joined10:58
sitaram I guess I could just rdiff-backup the repo itself too; should work10:58
ashH joined10:59
onigiri left11:00
eevar2 okies, just using rsync or similar sounds great11:01
kpreid__ joined11:02
kpreid_ left11:02
Axius left11:02
Stravy left11:04
muguruma-kensei left11:04
scarabx joined11:06
rraasch joined11:06
harinath joined11:08
harinath left11:08
tasslehoff sitaram: I meant the one from before :)11:09
onigiri joined11:09
univate left11:10
tasslehoff sitaram: but forget that :), now I mean the latest one :)11:11
solofight joined11:12
univate joined11:21
_Cro_Crx joined11:22
froschi joined11:23
altrux joined11:23
VVSiz left11:24
amigojapan_ left11:24
tfarina joined11:26
upul left11:31
sitaram :)11:32
hugoxrosa joined11:32
Cro_Cr715 joined11:33
brizly1 left11:33
brizly joined11:35
sagsousuke joined11:35
Axius joined11:36
Cro_Crx left11:36
Araneidae joined11:39
lamont`` joined11:39
Araneidae I need to rebase from one Linux patch fix to another ... and I don't want to rebase the fixes, of course, which a simple `rebase <new-branch>` forces. What can I do instead?11:40
lamont` left11:40
sitaram I didnt understand; maybe if you elaborated a little...?11:40
Araneidae Sure. I currently have some patches based on top of Linux 2.6.30.4 (or something like that)11:41
sitaram ok11:41
Araneidae I just ran `git rebase v2.6.31.5` and it came up with *lots* of patch conflicts11:41
But of course, the patch conflicts are nothing to do with my patches, they're just conflicts between the two bug-fix branches11:42
Pieter you should probably only rebase your own changes11:42
Araneidae yep11:42
Pieter se the --onto option in man git-rebase11:42
Gitbot Pieter: the git-rebase manpage can be found at http://git.or.cz/man/git-rebase11:42
sitaram oh that's like this then: git rebase --onto v26315 v26304 mybranch11:43
Araneidae: ^11:43
Araneidae Ah, I think I see.11:43
sitaram Araneidae: in general, rebase --onto A B C says, take the changes between B and C, and put them on A, and call the new tip "C"11:43
solofight left11:44
sitaram does that sound like what you're trying to do?11:44
Araneidae Thanks, that's what I need!11:44
sitaram ok11:45
_Cro_Crx left11:45
Azeroth-Working left11:45
engla Is it asocial to say "Only master won't be rebased, everything else are WIP branches" for my repo on github11:45
sitaram engla: I do that myself11:45
Araneidae Given that C is my current branch, is it optional?11:46
sitaram engla: although I *try* to not rebase the others its not a promide11:46
engla I have some trouble with a project I maintain. I have a clean master with some merges but mostly pick and rebase in contributions11:46
sitaram promise*11:46
engla yeah I want to make my work open but at the same time it is WIP11:46
that collaborators can comment on or build upon11:46
jschoolcraft left11:46
sitaram Araneidae: yes it is optional; but in general I try to specify everything in general (just a personal habit)11:46
eevar2 left11:47
engla sitaram: great to hear you do the same11:47
sitaram yup -- the gitolite project says so on the front page of its home on github :)11:47
jjuran engla: git.git has branches that are documented as having forced updates. Also, you might consider keeping them in a namespace, like 'wip/topic'.11:47
engla sitaram: I just miss a field for this in the github project page, the description field is too small, I want a field where I can say "Branch policy for this repo::" (like repo.or.cz has a "field" for this)11:47
jjuran: also a good idea11:48
sitaram engla: I just typed all that in there; only the entry field is too small -- just type it11:48
jschoolcraft joined11:48
sitaram engla: my current 'desc' reads: standalone, souped-up (started with per-branch permissions as the only extra feature, now lots more), version of gitosis. In perl. [Note: ALL branches except master are subject to rebase/rewind :-)]11:49
jas4711 left11:49
engla it's not pretty. but there are many things about github's interface that could be better. I like the technical/social function still11:50
the problem is that I manage the project, and I have one main collaborator that contributes a lot11:50
it is a new collaboration, I mostly take his changes and rebase to my master, fixing them up11:50
our trouble is finding the right way of branching and merging.. branches have to start in my master to be mergeable, but my collaborator prefers his master which was criss-cross merged with mine11:51
which I can't merge of course11:51
Axius left11:52
jas4711 joined11:52
engla So, does anyone have a template for an unformal workflow like this?11:52
d0k joined11:53
sitaram that's a tough problem, but it's a social one. I'd offer to make a feature freeze or something, fix up a nice master, have him fetch and start from that, and from then on everything he does has to be rebased off the origin master or something11:53
lorandi joined11:53
__iron left11:53
sitaram he doesnt *have to* rebase though11:53
jjuran engla: I believe you need a common master. Perhaps your partner could rebase his work onto the common (older) master.11:53
Adlai left11:54
engla yes, perhaps. should he just reset his master to mine, after that?11:54
that will be a break, but perhaps not so important11:54
Adlai joined11:55
kpreid__ left11:55
doener left11:55
kpreid_ joined11:55
lamont``lamont11:56
sdboyer left11:56
sdboyer joined11:56
jepler left11:56
sergiodj_sergiodj11:57
cannonball joined11:58
doener joined11:59
solofight joined11:59
jds left11:59
rolfb joined11:59
abw_ left12:01
jepler joined12:01
qrush_ joined12:04
tetha left12:08
tetha joined12:08
Jurko left12:08
tasslehoff any guides on how I could/should setup git & git-daemon on Ubuntu?12:13
Adlai try `apt-get install git'12:15
ludde how do i change branch when i have local changes?12:15
Adlai ludde: man git-stash12:15
Gitbot ludde: the git-stash manpage can be found at http://git.or.cz/man/git-stash12:15
ludde hm12:16
ok12:17
Adlai the examples section is pretty good12:17
also, if you use gitk, you'll see where you've created stashes12:17
(sp?)12:17
bdiego joined12:17
ludde why can't i just switch branch and it applies all my local changes on the new branch?12:17
Adlai oh, I assumed you wanted to keep your changes branch-local12:18
you should be able to just checkout the new branch, and it'll preserve any changes in your working tree while checking out the new branch. If there are conflicts, though, it won't merge, it'll just refuse to switch.12:19
so use the stash if there are conflicts and you want to merge them12:19
shruggar is there any way to automatically discard repeated trivial merges?12:19
Adlai shruggar: I'm not sure what you mean by discard12:21
DavidKlein joined12:22
scarabx left12:22
elTigre joined12:23
shruggar Adlai, basically I've been using "git pull" to pull in upstream changes every-now-and-then, and usually this results in a trivial merge (no differences, just two parents). I'd like to find all the trivial merges and act as if I used "rebase" instead of "merge" on those12:23
roop joined12:24
psankar left12:24
bcardarella joined12:25
Adlai hmm, I'm not sure exactly how to do that, but I can guess... first make a backup branch / lightweight tag, so you don't lose your current commit12:25
then try just rebasing onto the upstream12:25
sitaram shruggar: by trivial merge do you mean "one which resulted in no conflicts"? because otherwise a pull should have become a fast-forward, not a merge at all12:25
awnstudio left12:25
Adlai I -think- that rebase will ignore the merges, and only rebase your commits12:25
shruggar sitaram: I mean one which has no diff-output. Is there another term for that?12:26
Adlai sitaram: why?12:26
a merge with no conflicts is still a merge, if the upstream and the local repo both have changes12:27
sitaram correct12:27
Cro_Cr715Cro_Crx12:27
corni left12:28
doener shruggar: note that "no diff output" doesn't necessarily mean "no changes"12:28
shruggar doener, okay, in what cases would there be changes but no diff output?12:28
corni joined12:29
doener shruggar: the default format for diffs for merge commits is "condensed combined" (--cc), which only shows differences if the contents in the merge commit differ from _all_ parents12:29
Mezner joined12:29
shruggar doener, well I guess I mean "empty patch". I'm not actually using diff output to judge12:29
n3m_ joined12:29
doener shruggar: so upstream repeatedly did "git commit; git revert HEAD" or what?12:30
shruggar: if a merge commit was created, there were new commits12:30
shruggar: or did you basically cherry-pick each upstream commit before you merged?12:31
shruggar upstream had a bunch of regular commits. I, down here, used "git pull" to pull in changes. I didn't use "git rebase", because I don't know until after I've done it whether or not the changes touched the same files. I _do_ want to keep anything which touched the same files, but anything else I just want to discard the merge-commits, since as far as I know they're worthless12:32
tstclair joined12:34
nevyn_ joined12:34
doener is seriously confused12:35
Cro_Crx left12:35
doener I guess "same files" means "the same files that I modified in my local commits"12:35
Mezner left12:36
shruggar yes12:36
doener but the distinction between "merge" and "rebase" makes absolutely no sense to me12:36
Mezner joined12:36
marcoecc left12:36
doener especially given the previous "I want to act as if I have used 'rebase' instead of 'merge' on those [trivial merges]"12:36
when doing "git merge foo; git rebase foo", the "git merge foo" part is pretty much entirely pointless12:38
n3m left12:38
n3m_n3m12:38
nevyn left12:38
Cro_Crx joined12:38
doener so any merge commits before a "trivial merge" would of course also be dropped12:38
shruggar (typing up a graph)12:39
onigiri left12:39
Pupeno joined12:43
tasslehoff what do I need to setup to let other devs clone git repos from my pc? is it enough to start git-daemon with the correct options?12:44
bdiego_ joined12:45
Adlai left12:46
Adlai joined12:46
Altreus I am in the middle of a rebase, and the conflict markers says on one side HEAD and on the other side is a summary from a commit I made12:46
tasslehoff I want them to be able to push & pull/fetch12:46
Altreus err12:47
never mind12:47
ChanServ set mode: +o12:47
Mikachu changed the topic to: 1.6.5.2 | Homepage: http://git-scm.com | Everyone asleep or clueless? Try [email@hidden.address] | Git User's Survey 2009! http://git.or.cz/gitwiki/GitSurvey2009 | Channel log http://tinyurl.com/gitlog | Mailing list archives: http://tinyurl.com/gitml | Gits on git: http://tinyurl.com/gittalks | Pastebin: http://gist.github.com/ | "Alles wird Git" is over!12:47
Mikachu set mode: -o12:47
Altreus I was going to ask how I find out what HEAD is but ... I know that12:47
Altreus thick12:47
Ryback_ joined12:47
kpreid_ left12:48
kpreid_ joined12:48
aziz joined12:49
Altreus hmm12:49
nenne joined12:50
Altreus no HEAD seems to have nothing to do with the change I can see12:50
nenne hello, i am a bit of a newbie when it comes to git and version control and need some help12:50
Altreus how can I find out where the other half of the conflict is coming from?12:50
nenne i have created a repo at my webb server and cloned it to my development machine, made a change and pushed it back upp and commited it. after this. how do i make it actually modify my files according to this commit?12:51
shruggar okay, I apologize for my horrible explanation, mixing of terms, and not fully thinking through what I was talking about before asking. Perhaps this will help: http://gist.github.com/21862512:52
charon Altreus: during a rebase, HEAD is the last rebased commit and the other side will be the patch that it is currently trying to apply12:52
Altreus charon: How do I find out what commit that is12:53
the "other side" patch12:53
charon: The problem I'm having is that an entire function has been deleted, and it is a function that I have added to, hence the conflict, but I can't work out in what commit it was deleted.12:54
charon Altreus: interactive or normal rebase?12:55
Altreus normal12:55
univate left12:55
univate joined12:56
charon Altreus: hm... never needed this, but i think the corresponding patch file should be in .git/rebase-apply/patch12:56
shruggar perhaps a way of describing what I want is: "I want to remove every merge-commit which can be removed without my hand-resolving any conflicts. If there were no conflicts, the result would be identical to if I had used rebase from the start. Otherwise it would just be as if I had only run merge when there were conflicts"12:56
Altreus thanking12:56
charon shruggar: this isn't very constructive because i can see that your request should be possible "usually"; but note that this is not possible in general, as a single merge might conflict where a series of merges did not12:57
Altreus ach12:57
bdiego left12:57
boto joined12:57
Altreus This shows me the code I did but does not tell me who made the conflicting code :<12:57
shruggar charon, ah right, I forgot about that. Wasn't there a plan to have it fall-back to a more incremental approach when a conflict is detected? (but then I suppose the opposite is true too)12:58
charon oh12:58
Mizar-jp mm... may have failed to send the patch to [email@hidden.address] (content is http://github.com/mizar/gitk/blob/c20bcd2fdcb0583bbcf5fe4a5262374a84bbaafc/po/ja.po12:58
charon Altreus: i see. so you really want to know what HEAD has in that function, don't you? since the patch "on top" is yours12:59
Altreus: so i'd just try 'git blame HEAD -- $file'12:59
Altreus charon: git show HEAD seems to just show a section of the patch that .git/rebase-apply/patch is12:59
charon will have to actually test his own advice if the blame didn't help13:00
Altreus charon: Issue though13:01
_Cro_Crx joined13:01
Altreus There is nothing in the blame, because I am trying to blame a deletion13:01
perez left13:01
Altreus So there's no lines in the file that correspond to it13:01
priidu left13:02
Altreus hmm how do I find the FCA of master and $branch, again?13:02
charon i see. if you have a function name, you can try 'git log -p -Sfunction_name -- $file'13:02
or you can play with blame --reverse13:02
johnnyg joined13:02
charon $(git merge-base A B), but what does the F stand for?13:03
johnnyg left13:03
Altreus first common ancestor13:03
I suppose it is redundant13:04
Mizar-jp I have this patch to a mailing list is sent to one hour before, the mail is anyone I have not received it?13:04
Altreus I will try the -p thing though, that sounds useful13:04
tono joined13:04
kupsch I'm trying to clone a svn project. The project has a svn std layout, so this is what I'm doing:13:08
git svn -s clone https://subversion/repo/foo/foo/trunk foo13:08
foo is the name of the project13:08
however, cloning doesn't work. There's one line in the output which is strange:13:09
WebDragon joined13:09
modsognir joined13:09
kupsch Using higher level of URL: https://subversion/repo/foo/foo/trunk => https://subversion/repo/foo13:09
any ideas?13:09
Ilari kupsch: Maybe 'git svn clone -s https://subversion/repo/foo'?13:10
kupsch .../repo/foo is the location of the repository13:10
.../repo/foo/foo is the location of the project13:10
git svn clone -s https://subversion/repo/foo/foo then?13:11
no /trunk?13:11
roop_ joined13:11
Ilari kupsch: Well, try it.13:12
elTigre left13:13
Altreus grr it didn't even find the *creation* of the string13:14
this is nuts13:14
charon: how likely would you say that git log -S thing is to find the string? :S13:15
Cro_Crx left13:15
Axius joined13:15
Ilari Altreus: It finds commits where number of times that string is present changes...13:15
Altreus hmm so it may miss it13:15
Time to go with the common ancestor route13:16
veiz joined13:16
Altreus According to $(git diff ${FCA}..HEAD $file) the file in question has not changed between the merge base of this branch and master13:17
Irrespective of how I form that diff (I tried various ways)13:18
I made sure I was on master when I used HEAD :P13:18
However, if I rebase $branch onto master, it shows me a conflict in which this function has been deleted completely13:18
and it does not exist in master13:18
charon Altreus: well, the precise definition is: -Sstring finds all commits whose pre- and postimage counts of 'string' differ13:18
so moving 'string' around does not trigger it, but adding/deleting instances does13:18
Altreus hmm so it should have found it *somewhere* in the history13:19
tasslehoff "remote HEAD refers to nonexistent ref, unable to checkout" <- is this the way it should be when I clone a bare repository?13:20
Ilari Altreus: 'git diff A...B' impiles taking ancestor of A and B and then diffing it to B.13:22
Altreus yarr13:22
I tried A..B, A...B and A B and got no diff at all for the file13:22
kukks joined13:22
Altreus ... which is odd because the log shows stuff13:22
Ilari tasslehoff: That happens when remote default branch is set to point to something nonexistent.13:22
Altreus so that stuff must be older than B. /me checks13:22
sprasanna left13:23
corni left13:23
kupsch Ilari: now only the trunk is checked out. I can't see the other svn branches in 'git branch'.13:23
corni joined13:23
Ilari kupsch: 'git branch -r'.13:24
Adlai left13:24
kupsch aaah. alright. thanks!13:24
bdiego_bdiego13:24
cenuij left13:24
Adlai joined13:24
_Cro_Crx left13:24
tasslehoff Ilari: but it's ok? I'm following http://pastebin.com/m61b3d468 that sitaram wrote down for me, and the message come when I clone the repo from my server to a dev-machine13:25
roop left13:26
Ilari tasslehoff: If you don't have branch called 'master' on server, you need to set the default branch to something existent or you get that error.13:27
roop__ joined13:27
Ilari tasslehoff: That needs to be done on server (excluding some management interfaces that can set default branch).13:27
tasslehoff ah. I'm playing with openembedded, and I think their default is org.openembedded.dev, not master13:27
spearce joined13:29
veiz left13:29
Ilari tasslehoff: The clone suceeds. You just need to create a local branch from some remote branch (as usual).13:29
spearce: Hi spearce.13:29
hummingkid left13:30
Blackshark joined13:30
Cro_Crx joined13:30
krynnotaurTuttle_13:31
Tuttle_Krynnotaur13:31
gunmuc left13:32
tasslehoff Ilari: ok. I tried creating a local branch from "git branch --track mystable origin/stable". that worked, but on checkout it said "warning: You appear to be on a branch yet to be born", but that should be okay to, right?13:32
Altreus This is nuts. The merge-base of master and $branch is more recent than the last change to $file in master. However, I get conflicts rebasing $branch onto master.13:33
ihoka left13:33
Altreus But if $file has not changed in master since the merge-base, where is the conflict coming from?13:33
bcardarella_ joined13:33
Altreus and why does my $file not have the same content?13:33
And how can I find out?13:33
being the main question13:33
bcardarella left13:34
bcardarella_bcardarella13:34
toscano joined13:34
Ilari tasslehoff: Yes.13:34
priidu joined13:34
Ilari tasslehoff: Except that branch should be named 'stable' so names match and git push pushes it without any refspecs.13:35
Adlai left13:36
sde_antrix2 left13:36
javatexan joined13:36
Adlai joined13:36
paltman94 joined13:36
Jinzhu joined13:38
jlilly left13:40
spearce morning Ilari13:40
bousquet joined13:40
bdimcheff joined13:40
kpreid_ left13:41
kpreid_ joined13:41
roop_ left13:42
Adlai left13:42
keystr0k joined13:42
lohrun joined13:42
Cro_Crx left13:42
sde_antrix2 joined13:43
Adlai joined13:43
Swimming_Bird left13:43
Cro_Crx joined13:44
Ilari spearce: Oh, and if you want some numbers on remote helpers without any buffering (pushing updates for stuff): TX: 6 reads, 24530 bytes on layer 7 (4088 byte average TU). RX: 2 reads, 397 bytes on layer 7 (198 byte average TU).13:47
aliceinwire left13:47
phako how can I install something that is the output of a custom compiler commanf?13:49
command13:49
Ilari phako: Huh? What binary it is?13:50
_Cro_Crx joined13:50
phako er make13:51
or a custom makefile target13:51
agile left13:51
phako needs to build a kernel module13:51
broonie This doesn't sound like a git-related question?13:51
aspotashev left13:51
phako oops13:51
sorry13:52
bcardarella left13:52
phako wrong channel13:52
Ilari spearce: The only problematic place is the server initial ref advert. That's flushed at the end, so buffering that for send isn't that hard...13:54
Adlai left13:54
Adlai joined13:54
aspotashev joined13:55
ctusar joined13:56
Blub\0 joined13:56
Blub\0 what's the best way to maintain a "stable" branch?13:56
can I somehow track the commits which have been cherry-picked?13:56
or compare the trees of two or more branches13:56
paltman94 left13:57
Blub\0 so that for example I can see which commits are not yet in the stable tree?13:57
also, can I somehow pick multiple commits so that they're automatically applied in order?13:58
as in, start a merging process, pick commits, and then let them be applied in order to avoid conflicts which could emerge by simply cherry-picking the commits in the wrong order?13:59
reto__ Blub\0: git cherry13:59
GarethAdams|Work joined14:00
Blub\0 oh...14:00
hehe14:00
_Cro_Crx left14:00
reto__ Blub\0: git cherry -v master stable # <- what commits are applied to stable but not to master14:00
Blub\0 it's that obvious :D14:00
reto__ well, but you see the basic problem? the commit ids are not the same14:00
there are two different commtis14:01
if you cherry-pick changes14:01
you should, as long as possible, git merge stuff14:01
Blub\0 can I merge a certain commit directly? (git merge stable <commit>) ?14:01
reto__ nah14:02
you can't merge a commit, you can only merge the commit and its whole history14:02
tasslehoff left14:02
nighthwk1 joined14:02
reto__ a given commit contains everything (lets say all features) up to (including) the commit14:02
shruggar Blub\0, I'd recommend putting commits into a "fixes" branch, and merging that with both stable and dev14:03
reto__ shruggar: whats the base of the fixes branch?14:03
Mizar-jp Phew, it seems finally succeeded in sending mail. http://permalink.gmane.org/gmane.comp.version-control.git/13125014:03
bcardarella joined14:03
reto__ Blub\0: cherry-picking -> just get the changes described in that single commit, git merge, merge everything within this commit14:04
jas4711 left14:05
vbabiy joined14:05
Blub\0 reto__: but I'd want to pick commits one by one without merging the full dev tree into stable14:05
reto__ I know, use the fix branches as shruggar has adviced14:06
jds joined14:06
flazz joined14:06
reto__ but usually you develop stuff in your master tree14:06
I know :)14:06
flazz left14:06
shruggar reto__, the base of fixes would be the beginning of "stable"14:07
flazz joined14:07
Blub\0 shruggar: can you elaborate on that idea?14:07
alezandro left14:07
reto__ shruggar: where master and stable diverts?14:08
shruggar reto__, right14:08
reto__ shruggar: hmm, but therefore you should/woluld/could never develop on stable itself?14:08
Altreus Is there a simple way of saying "What's the first commit before $(git merge-base $A $B) that changes $file"?14:08
shruggar reto__, Blub\0: basically, as if you were applying fixes directly to "stable" and merging them back into "master", but personally I think that looks weird in the history14:08
reto__ shruggar: alright... :)14:09
shruggar reto__, personally I don't like developing on stable itself, but that's just personal preference14:09
Altreus I mean I can do it in more than one command but I wondered if git had a feature14:09
vbabiy left14:09
reto__ shruggar: got your point :) thx14:09
Blub\0 oh, so, work on dev, cherry-pick into fixes and merge it with stable?14:09
what advantage would that give me?14:09
reto__ not cherry-pick14:09
JNR___ joined14:10
dimsuz joined14:10
reto__ Blub\0: so basically create a branch called 'fixes' on stable, when you fix something 'in stable' you develop it in fixes, then you merge it from master and you merge it from stable14:10
but in stable it will be only a fast forward merge14:10
dimsuz hi! is there a command to help me find which remote branch is tracked by my local branch?14:10
shruggar Blub\0, when you cherry-pick, git doesn't keep track of it having been put from one into the other14:10
Blub\0 hmmmm14:10
reto__ dimsuz: less .git/config14:10
Blub\0 that sounds weird14:10
shruggar Blub\0, basically, it bypasses what you might considered to be git's merge-tracking14:10
ramlev left14:11
Blub\0 I'd like to "pick" commits and still keep track of them :S14:11
not necessarily the full tree14:11
reto__ Blub\0: well if your commit is already in master you can't do anything but cherry-pci kthem14:11
Blub\0 well, full history14:11
hmm14:11
reto__ Bucciarati: but if you switch to the 'stable-fixes' branch before working on these 'stables fxies'14:12
Adlai left14:12
johnny_ joined14:12
johnny_ t14:12
reto__ Blub\0 I mean14:12
Swimming_Bird joined14:12
reto__ Blub\0: you can use git's much more flexible system14:12
Blub\0: basically you can do a git checkout master; git merge stable-fixes; and be sure that everything is there14:12
Adlai joined14:12
reto__ at any time14:12
dimsuz reto__: i suspected that :) just wondered if there's a command option perhaps (didn't find any on man git-branch). thanks14:13
Gitbot reto__: the git-branch manpage can be found at http://git.or.cz/man/git-branch14:13
perez joined14:14
Blub\0 okay14:14
thanks for the help14:14
I think we found our solution14:14
:)14:14
reto__ Blub\0: read man git-cherry if you have to cherry-pick14:14
Blub\0 (one step closer to moving from svn to git :P hrhr)14:14
Gitbot reto__: the git-cherry manpage can be found at http://git.or.cz/man/git-cherry14:14
johnny_ left14:14
schierbeck left14:15
reto__ dimsuz: perhaps there's even a command, but I'd open the config file :)14:15
Cro_Crx left14:15
Altreus can I omit <since> from <since>..<until> ?14:15
jmcantrell joined14:16
dimsuz reto__: yep. no probs, i just did it ;)14:16
Blub\0 another question - related though:14:17
say, I have a history: A B C D E F G, and the stable branch is now: A B C' D' G' (so, C, D and G have been cherry-picked)14:17
corni left14:18
Blub\0 now I'd want to merge master to stable14:18
corni joined14:18
reto__ wait a sec..14:18
you mean merge stable into master?14:18
Blub\0 eh14:19
dev to stable14:19
master would be the dev branch14:19
reto__ alright14:19
k!14:19
Blub\0 so, master/dev = A .. G, and stable with G' at the end, now I merge them14:19
jlilly joined14:19
Blub\0 so that E and F are merged into it14:19
could that result in conflicts?14:19
since I basically apply E and F after having applied G already?14:19
reto__ you mean because of the cherry-picks?14:19
Blub\0 yes14:19
reto__ nana.. git is pretty intelligengt14:20
Blub\0 because, this currently can easily cause conflicts in SVN14:20
reto__ should handle that pretty well14:20
Blub\0 with some strange tool we use14:20
reto__ :)14:20
Altreus how do I get a log for a file *before* $commit, rather than since/14:20
I tried git log ..$commit -- $file14:20
reto__ Altreus: gimme a seoncd14:20
Altreus it just blanked me :(14:20
sitaram Altreus: ..$commit means HEAD..$commit, which is probably empty14:21
charon Altreus: git log $commit -- $file14:21
sitaram right14:21
Altreus sitaram: oh14:21
that was silly of me14:21
well maybe14:21
I assumed that <since>..<until> meant that ..<until> would DWIM14:21
s0ber joined14:22
reto__ Blub\0: merging cherry-picked (duplicated) commits shouldn't be a big problem with git ,but perhaps somebody with more experience can comment on that14:22
jas4711 joined14:23
hgb21 joined14:23
sitaram Altreus: as charon said, for "everything upto commit" you dont need a special syntax; it's what you get by default anyway. You need something special to make it stop, and that's what the left side of the .. is14:24
Blub\0 okay, thanks, I hope someone who knows more will comment on it :)14:24
I'll be around :)14:24
patcito joined14:24
Blub\0 usually 24/7 - I just forgot to rejoin when the server got rebooted :P14:24
charon Altreus: it does DWIM, leaving out one side of .. and ... means HEAD14:25
JNR___ left14:25
charon Altreus: the <commit-ish> arguments mean: all commits reachable from the positive refs, but not reachable from the negative ones14:25
Altreus: so 'git log A B ^C' gives you all commits contained in A or B (or both), but not contained in C14:25
Altreus: A..B means B ^A, see man git-rev-parse for the other equivalences14:26
Gitbot Altreus: the git-rev-parse manpage can be found at http://git.or.cz/man/git-rev-parse14:26
Altreus charon: so I M the wrong thing :)14:26
priidu left14:26
designs703 joined14:28
designs703 is there an equivalent to the -i flag for ssh in git commands?14:28
for passing a different key file14:28
babilen left14:28
bdiego_ joined14:28
Lemon|work joined14:29
reto__ designs703: i'm sure there is ,but why dont you specify it in your .ssh/config14:29
_14:29
Lemon|work Do i loose my subversion commit history if i migrate to git?14:29
or is there a way to convert to git?14:30
agile joined14:30
reto__ Lemon|work: there's even a way to use svn as a backend for a git local repo14:30
Lemon|work: check out git svn14:30
Lemon|work: there are some limitations of course14:30
s0ber_ left14:30
designs703 reto__, I'm working on a deployment app that ideally ships with the ssh key14:30
Lemon|work i guess i can just start from "version 1"14:30
in git14:30
and archive the subversion repository14:31
loincloth joined14:31
Lemon|work got another question14:31
more concept like14:31
reto__ Lemon|work: its really easy, if you use the trunk/branches/tags structurein svn14:31
Lemon|work: its git svn clone -s <path to svn>14:31
Lemon|work ah ok14:31
reto__ Lemon|work: and it transforms all your history..14:31
Lemon|work cool i'll try that14:31
hgb21 I am trying to make my first commit to my remote serever where git is but I am getting the following error anyone know why ?14:31
http://gist.github.com/21869514:31
reto__ Lemon|work: invest the 20 minutes.. or so14:31
jrmuizel joined14:31
reto__ Lemon|work: its probably worth it14:32
nenne i have created a repo at my webb server and cloned it to my development machine, made a change and pushed it back upp and commited it. after this. how do i make it actually modify my files according to this commit?14:32
Lemon|work btw what is the best way to use stable, beta, development branches?14:32
johan-s left14:32
Lemon|work just merge to the beta first and if the beta is stable merge that to the master ?14:32
reto__ nenne: you shouldn't use a repoistory with a working dir as a central repo14:32
nenne: I mean: your central repo shouldnt have its data checked out14:33
nenne: ideally you have three repos, the central one, one checkout at your desk, one where you want14:33
designs703 it appears that this is not an option (based at least on the help for clone and ls-remote)14:33
reto__ nenne: btw. github is really ncie for the central one14:33
hgb21 anyone know why I have this error . . . http://gist.github.com/21869514:34
kpreid_ left14:34
nenne reto__: aah ok, pretty new to version control and git :) . what i trying to do is using git as a way of cloing my webapp and modding it and then using git to set the changes "live". this might not be the way its ment to be used?14:34
bdiego left14:34
designs703 maybe there's a way to include the path in the SSH string?14:34
kpreid_ joined14:34
reto__ nenne: thats no problem, just use an independet '--bare' central repository14:35
nenne: imho thats the best way to deploy an application14:35
nenne: just use a dedicated 'bare' repo as a central hub14:35
:)14:35
hgb21 ?14:35
Aides left14:35
designs703 :P http://osdir.com/ml/git/2009-02/msg00355.html14:36
reto__ hgb21: fatal: remote origin already exists. read the error14:36
hgb21: you alread<y have this remote, check out your .git/config and man git-remte14:36
hgb21 ?14:36
nenne reto__: so i push my changes to this bare repo and use it as a stage, then i retreive it from there to the actual live server? so i have dev - stage and live in a sense14:36
reto__ hgb21: the first command already spawns a error14:36
hgb21 i am folowing this http://articles.slicehost.com/2009/5/13/capistrano-series-setting-up-git14:37
reto__ nenne: you have a checkout 'dev', a checkout 'live' and a central repo which is --bare..14:37
of course, thanks to git, all your repos can work independent14:37
temoto joined14:37
temoto Is it normal, that git clone URL creates local master and git clone /path/bundle does not?14:38
What the reasoning behind this difference?14:38
nenne reto__: reto__14:38
LiamH joined14:39
nenne reto__: oops mt . i think i understand now. will try it out. thanks alot14:39
reto__ so i'm afk14:39
bushwakko joined14:39
bushwakko How can I diff my undcommited patches against the server14:40
using svn as a central repo14:40
Turias joined14:40
Adlai left14:41
Adlai joined14:41
designs703 mercurial allows this ...14:41
bushwakko what is that?14:42
suman joined14:42
designs703 providing an identity file for an ssh connection manully14:42
*manually14:42
FunkeeMonk joined14:42
dwmw2_gonedwmw214:44
designs703 I think I will be able to do it this way: http://git-scm.org/gitwiki/GitTips#Howtopasssshoptionsingit.3F14:44
segher joined14:44
squentin joined14:44
Turias left14:45
fsalgo joined14:45
Turias joined14:45
JoeConyers joined14:46
mattayers Hi guys, I've got a branch with 4 commits I want but not the last one. Can I just merge in the SHA IDs of all the other commits?14:46
JohnFlux joined14:47
bdiego joined14:47
JohnFlux Hey all14:47
fsalgo hey guys! I want to commit a default database config file but want to ignore it in future commits when I have keyed in the actual credentials14:47
JohnFlux how do I do: git stash filename ?14:47
bdiego_ left14:48
teuf mattayers: git merge branchname^ maybe ?14:48
fsalgo so the problem is even after putting the file in .gitignore it still shows up at modified14:48
johan-s joined14:49
smuf joined14:49
Thumper_ j3114:50
JohnFlux fsalgo: I don't think you can do what you want14:50
fsalgo: it's a pretty common question in here14:50
fsalgo JohnFlux: how do you guys go about it?14:51
SjB joined14:51
fsalgo JohnFlux: I mean whats the git approach for it?14:51
JohnFlux fsalgo: put the credentials in a different, untracked, file?14:52
and include that file?14:52
hgb21 reto__: so what is the problem ?14:52
alezandro joined14:52
Mezner left14:53
fsalgo JohnFlux: but then in other file which I'll commit will have reference to the difference file!14:53
designs703 the technique described here is not working for me, has anyone here had success with it? http://git-scm.org/gitwiki/GitTips#Howtopasssshoptionsingit.3F14:54
sergiodj_ joined14:54
x-demon left14:54
mattayers Is there anyway to merge a commit in without doing it's parents?14:54
fsalgo JohnFlux: cant one just start ignoring a file midway?14:55
sergiodj left14:55
designs703 I am able to connect when providing the key to ssh with the -i flag and I've written this script with that key provided via an absolute path. I get prompted for a password when connecting to the server after setting GIT_SSH to this env var14:55
fsalgo as we have migrated from svn to git and now for future commits we'd like to ignore few files14:55
jjuran mattayers: Not really. You'd have to create a new commit without the unwanted parents.14:55
mattayers jjuran: Ok thank you14:56
jjuran fsalgo: Git doesn't ignore tracked files. If you remove the files, then they'll be ignored if they match .gitignore.14:57
bgerber left14:57
sergiodj_ left14:58
sergiodj_ joined14:58
fsalgo jjuran: yes I read that git doesnt ignore tracked files. so do you recommend that I make a sample config file commit it, delete it and then create it with actual credentials and start ignoring it?14:59
Haarg joined15:00
nothingHappens joined15:00
fsalgo jjuran: as the file was deleted, ignored and recreated will git still track it?15:00
spearce left15:00
x-demon joined15:02
fsalgo jjuran: yes that works :D15:02
jjuran: JohnFlux: thanks guys15:02
malumalu joined15:03
abms1116 left15:03
babilen joined15:03
abms1116 joined15:03
sde_antrix2 left15:03
abms1116 left15:04
dpino left15:05
Axius left15:07
priidu joined15:08
drubies joined15:08
DrTrevorkian joined15:08
johan-s left15:09
gionn_gionn15:10
sde_antrix2 joined15:12
ihoka joined15:12
macmaN6789 joined15:13
_jason553839 joined15:14
javatexan left15:14
macmaN6789 does anyone use export_auth_hook in their gitweb.conf here?15:15
yaotti left15:15
javatexan joined15:16
Mezner joined15:16
macmaN6789 searching through gitlog it would appear export_auth_hook is not a popular topic15:16
evl joined15:17
bgerber joined15:18
ph^ left15:18
wolog joined15:18
spearce joined15:18
cehteh joined15:18
mrlemao joined15:18
sitaram never heard of it, but a quick read suggests it should be quite straight forward, assuming you got gitweb itself running ok15:18
designs703 left15:19
macmaN6789 conceptually yes15:20
mrlemao left15:20
macmaN6789 just something wack happens when you put simply return 0; for the hook15:20
USA_NO_1_ joined15:21
wwalker_ joined15:21
macmaN6789 something somewhere spits out some extra garbage after the normal "no projects found" gitweb page15:21
Grahack left15:21
macmaN6789 is there a git issue tracker somewhere even?15:21
hyperair i believe it's the mailing list.15:21
evl left15:21
macmaN6789 thought so15:22
paltman94 joined15:22
Cro_Crx joined15:23
mithro joined15:23
hgb21 is there a way of changing the password of my remote git server15:23
I forgotten15:24
hyperair ssh?15:24
a389742 left15:24
hyperair ssh <user>@<host> passwd15:24
johan-s joined15:24
sergiodj_ left15:24
sergiodj_ joined15:25
hgb21 hyperair: well I have forgotten my old password15:26
sergiodj_sergiodj15:26
hyperair well ask the administrator of that server to reset it15:26
gnukid joined15:26
ia left15:27
kpreid_ left15:27
kpreid_ joined15:27
hgb21 I am the admin . . .15:27
solofight left15:27
wwalker_ http://gist.github.com/218730 - I fixed my first git conflict, the command says run add, I did, it still says run add. What do I actually need to do to clear the conflict? <repeating as I think my client went crazy, my nick changed when I posted>15:27
wolog left15:28
wolog joined15:28
hobodave joined15:29
Cro_Crx left15:29
Cro_Crx joined15:29
hgb21 hyperair: ?15:29
hyperair hgb21: ...can you access the server at all?15:30
hgb21 yes15:30
fhr joined15:30
hgb21 I am loged in15:30
hyperair right15:30
wwalker_wwalker15:30
hyperair get root access15:30
can you get root access?15:30
slaydragon joined15:31
roop__ left15:31
hgb21 yes15:32
qrush_ left15:32
hgb21 and I did -- su git15:32
qrush_ joined15:32
hgb21 it asked me for password but I dont remmeber it.15:32
lucs hunter215:32
USA_NO_1 left15:33
sitaram sck-thebs15:33
oops!15:33
Ilari hgb21: Do 'su git' from root and it won't prompt for password.15:33
Cro_Crx left15:34
selckin joined15:35
Cro_Crx joined15:35
Ilari hgb21: Also, 'passwd git' as root should work to change the password.15:35
ia joined15:37
hgb21 Ilari: I got this now Cannot execute /usr/bin/git-shell : No such file or directory15:37
hgb21 left15:39
Ilari hgb21: Well, 'passwd git' as root should work.15:39
_jason553839 left15:39
Adlai left15:39
maleknet left15:40
n3m left15:44
hgb21 joined15:44
hgb21 and i have it insalled15:45
asksol left15:45
Cro_Crx left15:45
abms1116 joined15:46
_Mica_ joined15:47
evl joined15:47
qrush_ left15:47
__iron joined15:48
Adlai joined15:49
madewokherd left15:49
aatanasov left15:50
omenking_ joined15:51
Adlai left15:51
hgb21 Ilari: from root ...when I do "su git" I get this15:51
annot execute /usr/bin/git-shell : No such file or directory15:51
Adlai joined15:52
doener wwalker: you resolved the conflict to "no changes", so there's nothing to be committed. Use "git rebase --skip" to skip the commit15:52
Ilari hgb21: Also, 'sudo -H -u git /bin/bash' might work to get shell as git user.15:53
EricInBNE left15:53
FunkeeMonk left15:53
hgb21 Ilari: yest that works15:53
Cro_Crx joined15:54
hgb21 It still ask me to provide my old password when I attempt to change it15:55
Cro_Crx left15:55
Ilari hgb21: 'passwd git' as root. It does not ask for old password.15:56
Cro_Crx joined15:56
fsalgo left15:56
bushwakko left15:58
_jason553839 joined16:00
kpreid_ left16:00
sde_antrix2 left16:00
saurabhverma left16:00
omenking left16:01
marc_kdab left16:01
Theravadan joined16:02
marc_kdab joined16:02
helo joined16:02
univate left16:02
sitaram idly wonders how many people are being inducted into the magic of the Unix command line because of git16:02
gambler left16:03
Adlai sitaram: git was the first command-line app that I really used on the command-line16:03
sitaram bingo! score 1 for my hypothesis :)16:03
Adlai started out half a year ago on the Jaunty Jackalope16:03
helo aggressively wonders how many more people are avoiding git because they are afraid of the Unix command line voodoo16:03
Adlai now tiles stumpwm on Archlinux :D16:03
sitaram idly googles stumpwm16:04
sitaram (( ok ))16:04
Adlai hehe16:04
sitaram (( got (it )))16:04
hgb21 Ilari: I still have problem when I attempt to push16:04
http://gist.github.com/21869516:04
Adlai sitaram: It's definitely a niche WM...16:05
hgb21 the new password is not been recognised .16:05
Ilari hgb21: Maybe ssh settings don't allow remote login as git?16:05
nevyn_ left16:05
hgb21 what do you mean ?16:06
Ilari hgb21: If you forbid ssh logins to some account, ssh behaves like all authentications fail. Thus you get password prompt which doesn't accept any password.16:07
warthog9 left16:07
alley_cat joined16:07
wolog left16:07
hgb21 yes I have restricted the ssh to the remote git16:07
Ilari hgb21: Anyway, this is ssh problem, not git problem.16:07
hgb21 Ilari: But how can I enable that /16:08
Ilari hgb21: sshd configuration file controls that.16:08
_Cro_Crx joined16:09
asksol joined16:09
qhoxie joined16:09
tbuehlmann joined16:10
omenking joined16:10
johan-s left16:11
hakunin left16:11
justin-george joined16:11
justin-george left16:11
sitaram /etc/ssh/sshd_config; look for AllowUsers (case insensitive)16:12
Ilari Isn't There's also allowGroups ?16:12
sitaram I think so; yes. Although I only ever use AllowUsers16:13
LRN left16:13
abms1116 left16:14
hakunin joined16:16
_Cro_Crx left16:17
omenking_ left16:18
dogmatic69 joined16:18
wwalker doener: thank you16:18
dogmatic69 hi all... im trying to remove a file from a repo, could someone help me16:18
_Cro_Crx joined16:18
dogmatic69 i tried rm filename.ext and commit --amend16:19
nikki93 joined16:19
Ilari dogmatic69: 'git rm filename.extension' and then commit.16:20
nikki93 Hey guys! Say there's this little experimental change I want to do. It's a small change, and it wont conflict with many things. I make the change, then I continue working on the project. Say in the future I want to undo just that change, how should I do this?16:20
j416 left16:20
nikki93 Make a new branch for that change? But, the things I do after the change are normal, just that particular change is experimental.16:20
dogmatic69 Ilari: that is what i did.. is it the --amend16:21
nikki93 I will stick to it most probably anyway, but I would like to be able to choose whether I can 'turn it off'.16:21
kennethlove joined16:21
selckin branch sounds reasonable then16:21
Ilari dogmatic69: --amend does handle file removals too.16:22
paltman94 left16:22
charon dogmatic69: the 'git' in 'git rm' is important.16:22
nikki93 selckin: So I make a new branch for it, and then I should work on future things on that branch, or on master?16:22
spaceonline joined16:22
WALoeIII left16:22
dogmatic69 charon: sorry i had the git also ... all the commands start with git afaik16:22
Cro_Crx left16:23
_Cro_CrxCro_Crx16:23
godsflaw joined16:23
qrush_ joined16:23
krawek joined16:23
giallu left16:24
_jason553839 left16:24
BeerSerc joined16:25
jgoulah whats the best way to send an email on push (ideally with what was pushed)16:25
charon dogmatic69: in that case, you did everything right, and should probably describe what you expected to happen and how git disagreed with that16:25
well, i wouldn't amend though16:25
dogmatic69 charon: http://github.com/dogmatic/cake-currency-converter i want that loose file gone16:25
Tanguy Hi.16:26
juan_arandaalvar joined16:26
froschi left16:27
Tanguy Do you know if a merge tool can be invoked with the true original file as middle file, without the conflicts markers?16:27
murph_ joined16:27
charon dogmatic69: you didn't push, or the push failed because you amended16:27
dogmatic69 ok, let me try again16:27
Jinzhu left16:28
dogmatic69 now its saying its not there me git rm currency.php16:28
nikki93 jgoulah: I believe you can add 'hooks' to events.16:29
selckin Tanguy: git mergetool with a diff tool configured that does three way merges, or do i misunderstand16:29
jgoulah well i saw this, just don't know where to put it http://git.kernel.org/?p=git/git.git;a=blob;f=contrib/hooks/post-receive-email;h=60cbab65d3f8230be3041a13fac2fd9f9b3018d5;hb=HEAD16:30
i have a gitosis setup16:30
Gitbot [git 60cbab65d]: http://tinyurl.com/yl9f3g3 [blob]16:30
charon dogmatic69: do the following: (1) run 'git reflog' and verify that the first (topmost) entry says 'commit (amend)'; (2) having verified that, see if you have any uncommitted changes with 'git status'; (3) having checked that you don't: run 'git reset --hard HEAD@{1}' to undo the amend; (4) run 'git rm currency.php' again; (5) run 'git commit' without(!) --amend this time16:30
dogmatic69: if all that went well, do 'git push'16:31
Tanguy selckin: I use a mergetool that does three way merges, but that expects a middle file intact, without conflict markers.16:31
charon dogmatic69: the reason for all this is: you should never rewrite commits that were already pushed elsewhere, so steps (1-3) undo the --amend.16:31
gnukid left16:31
Tanguy selckin: And git gives it the conflict-marked file instead of the original one.16:31
SRabbelier joined16:32
dogmatic69 charon: amend is at the top \o/16:32
selckin Tanguy: not sure, never seen conflict marks in mine16:32
corni left16:32
bentob0x eeh: Already up-to-date. Yeeah!16:32
?16:32
evl left16:32
sdboyeragentrickards_lu16:33
dogmatic69 charon: and it says no changes added to commit16:33
agentrickards_lusdboyer16:33
SRabbelier Ilari, madduck: could you s/"Alles wird Git" is over!/GitTogether 2009 in progress/ the channel topic?16:33
charon bentob0x: iirc that's the message for an octopus merge of branches that are already contained16:33
Axius joined16:34
bentob0x charon: the 'Yeeah' ?16:34
murph left16:34
charon indeed. the up-to-date message is different for ordinary and octopus merges16:34
bentob0x is the 'Yeeah' random?16:35
charon i just told you it's deterministic :)16:35
Ilari changed the topic to: 1.6.5.2 | Homepage: http://git-scm.com | Everyone asleep or clueless? Try [email@hidden.address] | Git User's Survey 2009! http://git.or.cz/gitwiki/GitSurvey2009 | Channel log http://tinyurl.com/gitlog | Mailing list archives: http://tinyurl.com/gitml | Gits on git: http://tinyurl.com/gittalks | Pastebin: http://gist.github.com/ | GitTogether 2009 in progress16:35
Tanguy selckin: I think the “meld” definition is just wrong, I will try an modify git-mergetool to see what it does.16:35
dogmatic69 charon: omg thanks :)16:36
got it to disapear16:36
nikki93 So I'd like to make the experimental change, stick with it, but if I have problems, just undo only that. Is a branch the way?16:36
Ilari dogmatic69: Oh yeah, there's IIRC delay in github web interface...16:37
Qwindoo joined16:37
dogmatic69 Ilari: i tried yesterday16:37
ferric joined16:37
charon dogmatic69: ok. please take away the following lesson: don't ever use --amend, rebase or filter-branch on commits that were already pushed.16:37
dogmatic69 charon: i think the lesson is dont copy past crap from the net :)16:37
Theravadan left16:37
charon that too ;)16:38
dogmatic69 its the first day im using this :)16:38
properly16:38
ferric question, I have a local branch that references a submodule in a commit. the submodule was subsequently pulled into the repo on an upstream branch. how do i get my local branch to understand this? rebase complains.16:38
s/an/the/16:38
d3z joined16:38
_jason553839 joined16:38
ab3 joined16:39
univate joined16:39
gambler joined16:40
Qwindoo left16:40
peff joined16:40
WALoeIII joined16:40
bentob0x thx charon :)16:41
Ilari ferric: Deleteting the submodule locally would probably at least allow the rebase to start...16:41
icwiener joined16:41
FunkeeMonk joined16:41
JohnFlux how do I do a git merge --continue, so to speak?16:41
charon nikki93: depends how confident you are; if you feel it has little chances of surviving, make a separate topic branch and use throw-away merges to test the interaction with other branches. if you think it has good chances of staying, just make the commit and if it turns out to be a bad idea, revert it16:41
ferric Ilari: cool, I'll try that -- and then probably redo my last commit since I just noticed that it is the only commit that references that submodule16:41
Pupeno left16:42
charon JohnFlux: add the resolved files and then commit. git-merge told you when it complained about conflicts!16:42
Tanguy selckin: In fact, it seems that meld is just unable to save into a file different than the original one, thus it is incompatible with git-mergetool's behaviour (four file names: original, local, remote, merged).16:43
ntoll left16:43
bentob0x left16:43
nikki93 charon: Well it ain't that bad, but the thing is, I might want to just 'try it without it' even a few commits later.16:44
dogmatic69 left16:44
charon nikki93: no harm there; you can always say 'git checkout HEAD^0; git revert $change' to do a "test revert" in the second case. remember to 'git checkout $branch' afterwards to re-attach your HEAD16:45
jchris left16:45
univate left16:46
nikki93 charon: I see.16:46
selckin Tanguy: maybe you can write a wrapper script to move things around16:46
univate joined16:46
Mezner left16:47
Tanguy selckin: Yes, I shall do that.16:47
rolfb left16:49
rraasch left16:51
jaysern joined16:51
LRN joined16:53
adamm joined16:53
kumbayo_ joined16:54
cantoma left16:54
nikki93 charon: Is it possible to 'unapply' an older commit, on a current one?16:55
charon: Without changing the history.16:55
(by making a new commit that does the reverse)16:55
Mikachu nikki93: git revert16:56
charon nikki93: that's precisely what 'git revert $commit' does16:56
mastro left16:56
nikki93 Yay. :D16:56
I thought git revert was only for the latest commit.16:56
crankharder left16:57
nikki93 So... Any git developers here?16:57
Cro_Crx left16:57
sitaram lots, I'm sure...16:57
khmarbaise left16:58
d3z Although the gittogether is happening right now.16:58
nikki93 charon: And if I want to reapply that older commit after reverting it? :P16:58
hgb21 left16:58
Ilari nikki93: Revert the revert?16:58
nikki93 Cool.16:58
bdiego left16:59
Thell|AwayThell16:59
charon though you may want to make up your mind at some point :)17:00
nikki93 Well most probably this change will stay.17:00
kumbayo left17:02
lhz joined17:04
crowbar left17:06
bushwakko joined17:06
eletuchy joined17:07
slaydragon left17:07
jgoulah is there a way to configure git so i don't have to do every command from the root dir?17:07
Sigma joined17:07
selckin thats the default?17:07
name left17:08
jgoulah if im in a subdir it doesn't know what i'm talkin bout17:08
dfr|work joined17:08
jgoulah says stuff about untracked files17:09
_jason553839 left17:09
helo i'm considering using git to keep track of and push configuration/application updates out to remote servers... anyone have experience with this?17:09
charon jgoulah: which command(s) in which usage?17:09
jgoulah git status , for example17:10
charon ah but that's one of the few that work relative to the current directory...17:11
mattayers left17:11
jgoulah ok17:12
charon this is admittedly not very consistent between commands17:12
Lemon|work left17:13
sitaram *always* works at the root; too confusing otherwise (probably my fault for not researching enough to know which commands work and which don't)17:14
charon what _is_ consistent, however, is that commands that do not work with the worktree at all are always(?) relative to the repo root17:14
ciskje left17:14
sitaram _is_ and (?) dont got together :)17:14
charon damn you caught me17:14
sitaram go*17:14
:)17:14
FunkeeMonk left17:14
charon i put the (?) because by the time i got to writing "always", i remembered git-reset isn't17:15
but then, it works with worktree files too if you tell it to17:15
sitaram so it doesnt count17:15
niki joined17:15
jgoulah yeah but i am converting people from svk and was hoping to reduce confusion since in there it doesn't much matter where you are, no worries tho17:15
sitaram s/do not work with.../never work with.../ maybe?17:15
FunkeeMonk joined17:16
charon hrm, well not that either. *sigh*17:17
'git log -- $file' also resolves the $file first17:17
i guess the git UI design is: DWIM, or when in doubt, DWLM17:18
Bass10 joined17:19
Axius left17:20
froschi joined17:20
sitaram :)17:20
priidu left17:20
sitaram or rather, :(17:20
_jason553839 joined17:21
jefferai If you have a feature branch that you want to merge into mainline, but that you also want to be able to revert if something turns out to e broken, what is the best way to do it?17:22
I know you can rebase it into one commit and apply, but that loses history17:22
but it's also not nice to have to revert a ton of commits17:22
is there a possibility of simply reverting the merge commit that merged the branches?17:22
evl joined17:24
aliceinwire joined17:24
elTigre joined17:24
joevandyk_ joined17:25
joevandyk_ git push HEAD~2:origin does not work. what would the syntax for that be?17:25
i want to push out to the origin branch, but i don't want to include the last two commits in the push17:25
numbah git push origin HEAD~2:master17:26
raalkml joined17:26
sitaram jefferai: if you push somewhere after the merge, doesn't matter how you do it; a revert is the only way. But you can revert many commits in one revert if you like17:26
(not by the revert command)17:26
jmcantrell left17:26
jefferai sitaram: err, sorry -- you can revert many commits in one revert, but not by the revert command?17:27
raalkml he means: revert takes only one commit in its argument17:27
d2dchat joined17:28
catphish joined17:29
jefferai so how do you revert a range of commits?17:29
godsflaw left17:29
_jason553839 left17:29
sitaram jefferai: it involves an incantation using git reset twice; let me think...17:30
jefferai ah17:30
patrikf jefferai: you can use git revert to revert commit-by-commit, possibly using "-n" to have all the reverts happen in one commit.17:30
alternatively, if your history isn't yet public, you can use git reset17:31
jefferai sitaram: also, when you merge, the history of the branch merges into the log, right? so what would be a good way to pull out just the various commits that were in that branch?17:31
patrikf or git rebase -i17:31
jefferai nha, history will be public already17:31
:-|17:31
sitaram patrikf: I'd say using revert assumes you cant use rebase but not sure if jefferai meant it that way17:32
(meanign someone pulled already)17:32
jefferai people will have pulled already17:32
patrikf sitaram: consider that part of my sentence that started with "if your history isn't yet public"17:32
jefferai (is a safe assumption)17:32
shaggyoaf joined17:33
shaggyoaf Hi, all. I've got two SVN repositories that I want to merge into a single git repository17:34
I figured out git-svn clone and I can bring them both down17:34
and I want one repo to contain another17:34
is there a way I can do that and preserve the svn history?17:34
sitaram patrikf: I did; sorry it sounded like I didn't... I meant thats not the use case here17:34
patrikf yeah, just mentioned it for completeness of the picture :)17:35
sitaram jefferai: git reset --hard HEAD~3; git reset --soft HEAD@{1}; now make new commit17:35
jefferai: assuming top 3 to be reverted17:35
altrux left17:35
jefferai yeah, that's not a good assumption either17:35
if we have to revert this, it's likely to be weeks from now17:35
(and many commits on top)17:35
altrux joined17:36
sitaram jefferai: then the "-n" method someone mentioned has to be explored17:36
mbroeker joined17:36
godsflaw joined17:37
sitaram jefferai: it does work (just tested) but make sure you do them in reverse order. And watch for conflicts17:37
johan-s joined17:37
jefferai sitaram: what does work?17:38
you didn't actually paste your -n foo :-)17:38
Lisimba left17:38
sitaram jefferai: yup; sorry. So you want to revert HEAD~2, HEAD~3, and HEAD~4. You do "git revert -n HEAD~2" then 3 then 4; then commit with some suitable message17:39
the first 3 reverts are with -n17:39
raalkml left17:39
sitaram s/first//17:39
s/someone/patrikf/ too I guess -- sorry again! just doing too many things at the same time *and* getting old :(17:40
shruggar left17:40
jefferai sitaram: OK, I see. But, when you merge the histories of the branches are merged together right?17:41
so is there a good way to find that list of revisions that constituted that branch?17:41
kmamykin left17:42
Mezner joined17:43
sitaram jefferai: eh? where did a branch get in here?17:43
sitaram checks backlog17:43
sitaram aah17:43
jefferai: when you find that something you merged was bad, you do this in the original branch you merged into mainline, then merge again17:44
jefferai wait, you do the revert in the original branch?17:45
that doesnt' make sense17:45
sitaram and now that I read your original question again, yes you can simply revert the merge commit if you wish; play with "-m 1" or "-m 2"17:45
cedricv left17:45
sitaram jefferai: why doesnt it make sense? the problem was caused there; you fix it there and propagate the fix17:46
peff sitaram: reverting merges is a bit dangerous, though17:46
sitaram indeed17:47
peff If you later want to remerge, the history doesn't quite do what you expect.17:47
jefferai sitaram: no, the problem wasnt' caused there17:47
the problem would be merging that branch into mainline17:47
like, if we want to revert, we will want to revert the entire merge17:47
not specific revisions in the merged-in branch17:47
ryoma joined17:48
jceb joined17:48
sitaram jefferai: try -m 1 or -m 2 on the revert17:49
jefferai sitaram: OK -- so, if I wanted to revert merging that branch, I could go to the merge commit, then could do -m X ...17:50
fhr left17:50
jefferai I see in the man-page the references to revert-a-faulty-merge17:50
I'll look at it17:50
fhr joined17:50
warty9_andy joined17:51
priidu joined17:51
warty9_andy anyone seen sop / spearce?17:52
Pupeno joined17:52
kpreid_ joined17:52
engla left17:53
peff warty9: yeah, he was sitting right in front of me a minute ago17:53
bnovc how can I create a remote branch without creating a local branch and committing first?17:54
i have servername/foo-devel and I want servername/bar based on foo-devel17:54
peff bnovc: you can't. A branch exists only as a pointer to some commit. If you have no commits, you have no branch.17:54
kpreid_ left17:54
bnovc there are commits, but not in that branch i mean17:54
peff Ah.17:54
bnovc i just want it to point to HEAD of foo-devel17:55
Theravadan joined17:55
_jason553839 joined17:55
Ilari bnovc: 'git push servername servername/foo-devel:refs/heads/bar'.17:55
bnovc thanks, ill try that17:55
peff Ilari: that's right, though I think you can drop the refs/heads in recent git17:55
bnovc thats what i was going to ask about17:55
Ilari peff: No, you can't.17:55
peff Ilari: I thought we added automagic detection of branch type for remote branches as well as local17:56
bnovc why is that necessary/what does it significy?17:56
*signify17:56
Ilari peff: Unless "recent" means more recent than master few days ago.17:56
zoniq left17:56
peff Ilari: recent may mean "in my repo and I haven't submitted to the list yet" ;)17:56
perez left17:56
smuf left17:56
bnovc heh17:56
FunkeeMonk left17:57
Pupeno left17:57
kpreid_ joined17:57
sitaram Ilari: I routinely do git push remote foo:foo without using ...;refs/heads/foo -- what am I missing?17:57
s/...;/...:17:58
manithree joined17:58
Pupeno joined17:58
peff sitaram: we detect the type of "foo" and say "oh, it's a branch. The other side is a branch, too"17:58
manithree left17:58
manithree joined17:58
peff sitaram: but in this example, it is actually pushing refs/remotes/server/foo-devel17:58
breitz joined17:58
warty9_andy left17:59
sitaram oh in this case he wants to create a remote branch based on anothe remote branch ?17:59
Ilari Yup, not even current pu would handle it right without refs/heads...17:59
Create remote branch based on remote tracking branch...17:59
PeakerWork joined17:59
vital joined18:00
sitaram ok18:00
PeakerWork how do I get a THREE way merge in mergetool? git mergetool only shows me the local/remote ver, but not any base18:01
sitaram I see the difference18:01
PeakerWork: depends on which tool you use; kdiff3 shows all 3 at least, so does meld18:01
doener sitaram: "fetch ... bla:foo" turns foo into refs/heads/foo, but "push ... bla:foo" failes18:01
sitaram actually they all should18:01
doener s/les$/ls/18:01
PeakerWork sitaram: I use git mergetool -t meld - it shows me my local and remote on the left/right. in the middle I get the merged result, but not a base18:02
sitaram: a 3-way merge typically has 4 views. base, local, remote, and result18:02
sitaram PeakerWork: meld mutiplexes; try kdiff3 -- it will show you 3 on top, and the result across the bottom18:02
jceb left18:02
priidu left18:02
sitaram doener: I could have sworn I did git push origin foo:bar once or twice18:02
PeakerWork sitaram: you mean the result pane has the base in it?18:03
sitaram PeakerWork: yes18:03
PeakerWork: no; wait the top row has 3 subpanes: base, local, remote18:03
PeakerWork sitaram: it seems to have the <<< and === signs from the file -- not the base18:03
sitaram PeakerWork: the bottom row is just one file; the result18:03
patmaddox joined18:04
doener sitaram: sorry, forgot to add "when 'foo' doesn't exist yet"18:04
PeakerWork sitaram: you talking about kdiff3 or meld? I don't think I have kdiff3 installed18:04
sitaram PeakerWork: kdiff3 shows <<< and ===? when invoked with "git mergetool -t kdiff3"? this is new to me... I use it all the time and never saw them18:04
PeakerWork sitaram: I was talking about meld there18:04
gunmuc joined18:04
sitaram doener: even so; but my memory isn't that good18:04
doener sitaram: and if "bar" is refs/heads/bar locally, then that's a special case, too18:04
dominikh left18:05
sitaram PeakerWork: rethinking... I dont think meld even shows the base, sorry18:05
peff Ilari: ok, you're definitely right about the refs/heads thing. Probably we should add that to the DWIM in remote.c:guess_ref18:06
PeakerWork sitaram: I wondered how people praised meld so much when it seemed to me to be very sub-par18:06
evl when rebase complains a file isn't up to date, what am I missing?18:06
sitaram I moved from meld to kdiff3 some time ago :)18:06
patmaddox I ran "git log master.." to see all the commits that existing in my branch but not in master. Is there an easy way to generate a patch from it all? Basically I just want to see the contents of those commits18:06
head joined18:07
_hp_ left18:07
peff patmaddox: do you want one patch per commit, or a patch of the whole thing?18:07
doener patmaddox: git log -p master..18:07
patmaddox peff: log -p works nicely for showing one patch per commit (thanks doener). Is there a way to see one giant patch too?18:08
doener patmaddox: or "git diff master..." (three dots) to get a diff from the common ancestor of master and HEAD, and HEAD (i.e. changes that would be merged to master)18:08
patmaddox: OTOH "git diff master.." would show a direct diff between master and HEAD, which is unlikely to be what you want (it would show everything that happened on master as being undone)18:09
bushwakko left18:10
pantsman joined18:11
sitaram doener: http://pastebin.com/m3e7709d4 -- what did I misunderstand this time? :(18:12
rolfb joined18:12
rolfb left18:12
onigiri joined18:13
doener sitaram: foo resolved to "refs/heads/foo", so "bar" is assumed to be "refs/heads/bar"18:13
saurabhverma joined18:13
sitaram oh... 'when foo doesn't exist yet' (misread that as ...bar...); how can you do anything like that anyway when foo doesnt exist?18:14
Dashkal joined18:14
doener sitaram: in my example, "foo" was the destination, not the source18:14
sitaram: http://pastebin.com/m55f2e22e18:14
sitaram doener: but bar, the destination, doesnt exist yet in mine...18:15
dominikh joined18:15
bugfux joined18:15
tango_ left18:15
engla joined18:15
catphish left18:15
doener sitaram: but the source was resolved to refs/heads/foo, and then the destination is assumed to live in refs/heads/, too18:16
sitaram if you'd tried push ~/a refs/heads/master:master it would have worked?18:17
patmaddox left18:17
doener sitaram: yep, as would have "master:master" or just "master"18:17
manithree left18:17
warthog9 joined18:17
sitaram ok18:17
doener sitaram: but IIRC only since 1.5.6 or so. Previously, for refs to be created, you always had to use the full refspec18:17
sitaram yeah I'm usually at the latest anyway18:18
bnovc I have a servername/foo-devel and I used a mercurial to git importer which created a local "master" branch... to include all these chanegs in servername/foo-devel, do I need to make a new branch that tracks it and cherry-pick everything from the "master" branch?18:18
godsflaw left18:18
Grahack joined18:19
bnovc hopefully there is an easier way than that18:19
Ilari bnovc: Check out the new local branch and merge master into it?18:19
mcella left18:21
bnovc I guess my real problem is that I don't know how to push directly without uploading all of these to Gerrit first18:21
maybe I should just do this on the server18:21
manithree joined18:21
godsflaw_ joined18:24
_Mica_ left18:24
wwalker I've just done a git svn rebase I want to see the changes in some of the files. is there a git equivalent to PREV?18:24
Weasel[DK] left18:24
mattayers joined18:24
Weasel[DK] joined18:24
Ilari wwalker: 'branch@{1}'?18:25
_jason553839 left18:26
godsflaw_ left18:26
SRabbelier GitTogether talk at #gittogether18:26
wwalker Ilari, thank you!18:27
corni joined18:30
galderz left18:31
LiamH left18:31
trip0 joined18:33
Markus2 joined18:33
Markus2 www.europa-irc.de18:33
Markus2 left18:34
godsflaw_ joined18:34
ph^ joined18:35
Axius joined18:36
wagle left18:37
bdiego joined18:37
jgoulah if you are tracking a remote branch and want to push commits, git push won't do?18:37
broquaint joined18:37
patmaddox joined18:38
jgoulah i'm getting this: http://gist.github.com/21891018:38
broquain1 joined18:39
broquain1 left18:40
rchavik left18:41
PerlJam jgoulah: did you pull before pushing? Perhaps there have been other changes to that branch while you were making your changes.18:42
jgoulah didn't pull, but nobody else is working on it atm, it looks the branch was pushed but that master rejected is my confusion18:43
tfarina left18:43
PerlJam jgoulah: the master branch was rejected because there are differences between the local master and the remote master.18:44
(usually)18:44
jgoulah i didn't think it mattered since i was on the branch but yes that is probably true18:44
owen1 joined18:44
priidu joined18:44
jgoulah do i pull to fix ?18:44
PerlJam it's a start :)18:45
jgoulah tries18:45
owen1 how to see changed i made on a file that i already added with git add?18:45
PerlJam pull may fix it, but you might have conflicts that need resolving.18:45
owen1: git diff --cached18:45
_jason553839 joined18:45
Sho_ left18:46
owen1 PerlJam: nice, thanks18:46
jgoulah PerlJam: http://gist.github.com/21891618:47
PerlJam jgoulah: then next I would suspect that the lineages of your local master and remote master have diverged somehow.18:48
evl Is there a nicer way to push a rebase other than -f?18:48
jgoulah hmm, i mean really nobody else is working on it, a file was added and removed from master18:48
i added an email hook on the gitosis setup18:48
thats about it18:49
PerlJam did you do a git commit --amend or git rebase after you pulled at some point?18:49
evl It's only me working on the remote git(hub) repo so I didn't think I had to pull before I rebased since last push, was i wrong?18:49
PerlJam evl: no. rebasing is not nice.18:49
jfkw joined18:50
evl I was trying to combine two commits to make the history look nicer, since the last commit was really just me forgetting to add a file in the previous commit18:50
kpreid_ left18:50
godsflaw_ left18:50
PerlJam evl: If you rebased commits that were already pushed, then that would cause problems.18:50
evl Is there any better way of doing this?18:50
Other than being a bit more careful before pushing? :)18:51
PerlJam evl: no. Be more careful :)18:51
jgoulah PerlJam: sorry, no i wouldn't even know to do that i'm pretty newb18:51
evl Alright, good enough for me. It looks nice and all but it messes up the github commit log18:51
drewolson joined18:53
PerlJam jgoulah: Hmm. Did you make another clone and do some work from that other clone?18:53
jgoulah PerlJam: actually more probably did happen on master, i convered from svn earlier, and added a couple dirs to master18:53
and those weren't added on branch18:53
wagle joined18:53
jgoulah but yeah those were added from another clone, then work on this clone was done, but only on the branch18:54
toscano left18:54
godsflaw joined18:54
psoo left18:54
PerlJam jgoulah: Dunno. I'm leaning towards "you screwed something up", but I'm not sure what at the moment.18:56
jgoulah oh god, git can't be -that- easy to screw up can it :)18:56
not much has really happened18:56
PerlJam: looks like checkout master; pull; checkout branch; push fixes it (don't even need the push)18:57
but i dont understand why18:57
godsflaw left18:57
jgoulah do i have to pull master just to push a branch?18:57
godsflaw joined18:57
ryoma is there a quick way to merge the last 2 commits into one? or do i have to do an interactive rebase?18:58
PerlJam jgoulah: oh. you were on a branch other than master when you did a pull before?18:59
madduck left18:59
thiago_home joined18:59
PerlJam jgoulah: you must have been. It fetched the commits from master but only merged the commits for the branch you were on.18:59
jgoulah PerlJam: yep18:59
i see18:59
so always pull from master?18:59
PerlJam jgoulah: you needed to merge the changes on the master branch before pushing.18:59
corni left19:00
hummingkid joined19:00
corni joined19:00
qrushqrush|away19:00
PerlJam jgoulah: you pull from where ever. pull == fetch + merge fetch will get all the changes for all branches. But you only get to merge one branch at a time (the one you're on)19:01
dvyjones left19:01
jgoulah so what is hte proper workflow if i only want to push a branch to remote19:01
davegb3| left19:02
bousquet left19:02
abms1116 joined19:02
kpreid_ joined19:03
vbabiy joined19:03
PerlJam jgoulah: um ... pushing didn't look to be your problem, pulling was19:04
jgoulah PerlJam: it sounded like the pull from the branch was the problem19:06
PerlJam: but then you say i can pull from anywhere19:06
PerlJam: but pulling from master is what fixed my issues, so i'm slightly confused19:06
PerlJam jgoulah: you were on some branch other than master but expected pulling to merge master (which it won't)19:07
godsflaw_ joined19:07
bushwakko joined19:08
wagle left19:08
jgoulah thats why i'm asking for proper workflow for just pushing a branch :)19:08
i get pull is fetch+merge and i get it won'tn merge a branch im not on19:09
thus putting me out of sync, and not letting me push19:09
_jason553839 left19:09
jgoulah but is it possible to just pull (or fetch+merge) for one branch19:09
abms1116 left19:10
tbuehlmann left19:10
kumbayo_ left19:13
kumbayo_ joined19:14
Stravy joined19:14
nevyn joined19:15
godsflaw left19:15
madduck joined19:16
Aides joined19:17
Tuomas left19:19
doladowanie joined19:19
doladowanie http://darmowe-doladowanie.org/index.php?c=viral&m=index&id=1ab8c7f36a6ba0e393e2e2af4bfc821119:20
doladowanie left19:20
godsflaw__ joined19:21
drubies left19:23
rudi_s joined19:24
drizzd are we seriously going to do this checkout guessing?19:24
is there nobody else who thinks this is insane?19:25
ryoma (sorry for the repeat) is there something like git commit --amend except that it says "i meant to do an amended commit" -- i.e. merging the most recent commit with the previous one? i am guessing not, and you have to do an interactive rebase.19:26
matten joined19:27
drizzd ryoma: no. your guess is correct.19:28
this never happens to me though19:28
statim joined19:28
drizzd because I realize as soon as I see the empty commit message19:28
sgh joined19:28
drizzd and I just exit with an empty message, which aborts the commit19:29
Geralt joined19:29
godsflaw_ left19:30
statim hey guys, im having trouble figuring something out: sometimes people do a merge which leaves just a Merged xyz commit message with no diff. i totally think in terms of diffs, so i like to see every line that changed between a commit to audit what people are changing. is that totally lost when someone does a merge that isnt a fast-forward?19:30
godsflaw_ joined19:32
drizzd statim: git log -c19:32
bushwakko left19:34
ciskje joined19:34
bcardarella left19:34
altrux left19:34
cantoma joined19:34
sergiodj left19:35
drizzd I wonder how to show everything though19:35
bnovc if i have servername/foo pointing to the 5th commit and servername/bar pointing to the 6th commit, how can I move foo to point to the same place as bar remotely?19:35
altrux joined19:35
statim drizzd: i see what its supposed to do via the man page with -c, but as far as i can tell im seeing exactly the same output so far in the log19:36
drizzd statim: normally you don't see any diff with merges19:36
statim: you need -p as well19:36
statim thanks19:37
drizzd bnovc: servername/foo, servername/bar are the remote tracking branches19:37
bnovc: git checkout -t servername/bar; git merge servername/foo; git push19:37
rado2 joined19:37
drizzd umh, other way around19:37
you get the idea19:37
paltman94 joined19:38
altrux left19:38
drizzd you could do git push servername servername/bar:foo, but that would be evil19:39
Blackshark left19:39
altrux joined19:39
altrux left19:40
altrux joined19:40
drizzd No Ilari today? feels almost lonely19:40
wagle joined19:41
godsflaw__ left19:41
bnovc drizzd: apparently i don't get it, since that seems to do nothing19:41
i dont know why it would be a merge anyway19:42
drizzd it's a trivial merge19:42
JohnFlux left19:42
bnovc but why is that considered a merge at all when nothing is being merged19:43
Ilari bnovc: 'git fetch servername' first so that those remote tracking branches are up to date?19:43
macmaN6789 !seen tv19:43
ramlev joined19:43
drizzd bnovc: I mixed up foo and bar in my example, did you catch that?19:43
you need to merge bar into foo (since bar is ahead of foo)19:44
Ilari macmaN6789: Haven't seen him here for a long time...19:44
capndiesel left19:45
macmaN6789 Ilari: ah ok19:45
Ilari macmaN6789: Something related to gitosis, I presume?19:45
drizzd And don't worry about the merge, it won't be recorded in history.19:45
macmaN6789 i just implemented an export_auth_hook for gitosis19:45
was wondering if that's even new19:45
or i just couldnt find anyone else had done it19:45
i now have gitweb selectively showing repos depending on who is logged in with apache basic auth19:46
from gitosis19:46
Ilari macmaN6789: Gitosis has been obsoleted by gitolite anyway...19:46
macmaN6789 huh?19:47
what is gitolite19:47
riiight.19:47
Rhonda gitosis done right. :)19:47
macmaN6789 uhhh. well this was a day well spent then.19:48
on obsolete technology19:48
:)19:48
Ilari macmaN6789: Well, you can reuse the gitweb side of things, can't you?19:48
gergap-wlan joined19:50
macmaN6789 uh. should i basically switch over immediately.19:50
Nailbar joined19:51
Ilari macmaN6789: Well, you can implmement it for both... But the changes of getting it to upstream repo are considerably higher with Gitolite than Gitosis...19:52
kpreid_ left19:52
bnovc drizzd: did you mean --branch in front of the checkout19:52
ferric left19:52
bnovc doesnt seem that -t can be done by itself19:52
macmaN6789 this is top hit for many git searches - http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way19:53
Nailbar left19:53
macmaN6789 doesnt have a word about gitolite19:53
i guess i should add19:53
bnovc i did `git checkout origin/foo-devel && git merge origin/master`19:53
doesnt seem to do anything except spam me with "create mode 100644 " modes19:53
Ilari bnovc: That's the diffstat for merge.19:53
macmaN6789: Its from 2007. IIRC, Gitolite was started couple months ago...19:54
macmaN6789 Ilari: yeah, but comments have come up to this month19:54
i was mainly thinking about the comments, usually someone updates with breaking info like that19:55
AkumaStreak left19:56
AkumaStreak joined19:57
drizzd bnovc: git checkout -t origin/<branch> creates a new branch names <branch> which tracks origin/<branch>. Unless you have an old git. Then you should get a warning about a detached HEAD.19:57
ramlev left19:57
mattayers left19:58
drizzd bnovc: with older git you can create the branch using "git checkout -b foo origin/foo"19:58
bnovc fatal: git checkout: --track and --no-track require -b19:58
ya, i normally use "git checkout --track -b FOO origin/foo"19:59
drizzd bnovc: oh, ok19:59
pantsman left19:59
drizzd good19:59
bnovc do I have to have a local branch before I can merge them?19:59
jarib left19:59
drizzd normally yes19:59
Ilari bnovc: No, but pushing without local branch can be interesting...19:59
drizzd in this case you could cheat using the evil command I gave before, but I don't recommend it (we are the good guys, after all)20:00
Ilari bnovc: And to name current branch: 'git checkout -b <newbranchname>'.20:00
bnovc why is that not good to do?20:00
that seemed to do what i wanted20:01
tono left20:02
kpreid_ joined20:02
jmcantrell joined20:03
drizzd_ joined20:04
drizzd_ bnovc: it's just error prone to take this shortcut, and it's not much of a shortcut anyways20:04
bnovc error prone if something has changed upstream?20:05
jas4711 left20:06
bx2 joined20:09
madewokherd joined20:09
temoto left20:10
rudi_s_ joined20:13
fualo left20:13
fualo_fualo20:13
nikki93 left20:13
Aikawa_ joined20:14
bushwakko joined20:14
rudi_s left20:15
pantsman joined20:16
javatexan left20:19
Dashkal left20:22
Dashkal joined20:23
drizzd_ bnovc: for example20:24
it's generally a good idea to test before you publish20:24
you cannot easily undo it after all20:25
drizzd left20:26
uMish joined20:27
mjf joined20:29
hakunin left20:29
hakunin joined20:29
tbuehlmann joined20:30
pippijn how do I fix a commit --amend when I pushed the one before that?20:30
evl left20:30
Aikawa left20:30
PerlJam pippijn: eh?20:31
pippijn I did git commit, git push, git commit --amend20:31
and now it rejects the push20:31
PerlJam pippijn: you have to force the push20:31
pippijn it still rejects it20:31
error: unable to create temporary sha1 filename ./objects/f5: File exists20:32
kumbayo_ left20:32
psoo joined20:32
pippijn ah20:32
charon pippijn: permissions problem, the misleading error happens because git tries a few alternate strategies and eventually bumps into this20:32
pippijn permission20:32
yes20:32
fixed it, thanks20:32
hyperair left20:33
thiago_home left20:34
pantsman left20:35
hgb21 joined20:35
jmcantrell left20:36
SjB left20:37
cilly left20:37
tstclair left20:40
tstclair joined20:40
coolcat joined20:41
__iron left20:41
helmut joined20:42
helmut hi. can I somehow checkout the empty history?20:42
__iron joined20:42
owen1_ joined20:43
impulze you mean the root commit?20:43
sgh_ joined20:44
uMish left20:44
helmut impulze: probably20:45
impulze: I observed that git init; git add .; git commit -am initial; git checkout HEAD^ # <- the checkout does not work.20:46
Aikawa joined20:46
tbuehlmann left20:47
mugwump helmut: you can use git symbolic-ref HEAD refs/heads/blah20:50
froschi left20:50
mugwump but that's not checked out; eg 'git status' after that will show lots of pending updates20:50
hugoxrosa left20:51
FunkeeMonk joined20:51
tbuehlmann joined20:52
sergiodj joined20:52
ihoka left20:53
saurabhverma left20:54
maattd joined20:54
doener helmut: if you just want to fix up your initial commit (maybe because you added files you didn't mean to add), "git commit --amend" is a better option20:54
Guest58660 joined20:54
owen1 left20:54
maattd left20:55
maattd joined20:55
sgh left20:57
Aikawa_ left20:57
helmut well I'd like to prune early history and wanted to rebase a later commit on root.20:57
I mean I only want to ignore history, not changes.20:57
vbabiy left20:58
coolcat left20:59
doener helmut: so you basically just want to cut off history at some point, without modifying any trees?20:59
_rane squeeze?21:00
doener helmut: filter-branch is better suited for that purpose. I'd setup a graft that does the cut-off, make it permanent with filter-branch and then drop the graft again21:00
d0k left21:01
matten left21:01
cannonball left21:02
corp186 left21:04
drizzd_ wouldn't squashing to the trick as well?21:04
well, I don't really understand what helmut is trying to do21:04
doener drizzd_: can't easily squash into the root commit21:04
peff left21:04
helmut basically my history is becomming too big21:05
drizzd_ are you sure? I don't see why not21:05
Axius left21:05
helmut so i'd like to take a commit and make it the new root.21:05
drizzd_ ok, if you have non-linear branches or even more than one branch, that's a problem21:05
helmut this allows git gc to drop objects no longer needed21:06
drizzd_ *non-linear history21:06
doener helmut: too big? How many commits are we talking about? Half a million?21:06
helmut doener: not how many, but how big21:06
drizzd_ helmut: just removing files from the root commit won't remove it from the children. You really need to use filter-branch in that case.21:06
owen1_ left21:07
doener helmut: unless dropping the commits means that the big blobs become dangling, that likely won't help much.21:07
mbroeker left21:07
helmut daemoen: exactly that is the case21:07
javatexan joined21:08
doener helmut: even if you make an old version of "big blob" dangling, the new version might still be around, and the delta compression should likely already make having two versions not much more expensive than having just one version21:08
babilen left21:11
Ceeram joined21:13
suman left21:14
Ceeram i did git config --global alias.foo something then got config --global alias.foo somethingelse, how would i now unset or reses alias.foo it now gives an error: More than one value for the key alias.foo21:15
bremner_ joined21:16
helmut doener: let's say I can get rid of a big binary blob? (old images for instance)21:17
Ceeram git config --unset alias.foo has no result21:18
lorandi left21:18
Ilari Ceeram: 'git config --unset-all --global alias.foo'?21:18
doener helmut: well, if you really want to cut-off the history, I already told you how to (graft + filter-branch)21:18
helmut: though dropping just the image might be a better idea21:19
gergap-wlan left21:19
_Ikke_ how come sometimes git self cannot merge some conficts, but when i run the mergetool it automaticly solves the conflict?21:19
Ceeram Ilari: thx was afraid unset-all would also unset other vars21:19
doener helmut: in that case, the answer is filter-branch as well, with --index-filter 'git rm --cached -q --ignore-unmatch <path>' or something like that21:19
agenteo joined21:20
Ilari Ceeram: The description is: "Remove all lines matching the key from config file.". Note "matching the key".21:20
Tama00 man im strugling soo hard to stay awake at work right now21:20
bremner__ joined21:22
Guest58660 left21:23
Mezner left21:24
Mezner joined21:25
Ceeram Ilari: true, didnt look that far, thought unset was what i needed, my bad thx again21:25
fhr left21:25
tfarina joined21:25
flazz left21:26
rolfb joined21:26
flazz joined21:26
Mezner left21:26
malumalu left21:27
WALoeIII_ joined21:27
hakunin_ joined21:28
Lisimba joined21:28
helmut doener: thanks. I'll need to read up on that then.21:29
elliottcable joined21:33
jceb joined21:33
keystr0k left21:33
kurkale6ka joined21:34
kurkale6ka I have used git add .vim but then I used mv .vim/* . and removed .vim. Do I need to git remove .vim? Or only add the new content before commiting?21:35
Stravy left21:36
Ceeram how would i put following into alias: git diff HEAD > foo.txt, i tried with git config --global alias.foo 'diff HEAD > foo.txt' but that doesn work giving fatal. the first statement itself does work21:36
Grahack left21:36
dwmw2dwmw2_gone21:37
SRabbelier Anyone know what Junio did with the remote-cvs helper series?21:37
drizzd_ SRabbelier: it's based on something that's not in next yet I think21:38
he mentioned it in his latest "what's cooking" mail21:38
gitster Yes I do. It breaks tests in 'pu', and Shawn seems to know the fix in Daniel's series (that is in 'pu', I think) but I haven't seen a patch.21:39
SRabbelier gitster: ah, you ejected it from pu then; that explains why I can't find it :)21:41
martianlobster joined21:41
bremner___ joined21:41
gitster Yeah, given the purpose of 'pu', probably I should queue it again and remove 'pu' from the set of branches I run test suite before pushing out.21:41
SRabbelier gitster: could you perhaps push it somewhere?21:42
gitster: that works too; either that or create yet another branch21:42
martianlobster is there some sort of version number for a repository which is modified with a commit or a push? If so, how can I tell what version number a repository is on?21:43
gitster Ok, it's back on 'pu'.21:43
babilen joined21:43
SRabbelier gitster: thank you21:43
kpreid_ left21:43
Ilari SRabbelier: You don't have earlier fetch of pu that includes it (well, its back there as well)? reflogs do cover remote tracking branches...21:43
bremner_ left21:43
SRabbelier Ilari: I had some trouble rebasing, so wanted to make sure I used the latest version if I'm going to have to be resolving conflicts21:44
gitster: have you pushed it anywhere?21:44
hakunin left21:45
gitster k.org has its usual mirroring delays (the host we push to are not facing outside world).21:45
Try alt-git.git at repo.21:45
macmaN6789 left21:45
WALoeIII left21:45
WALoeIII_WALoeIII21:45
Sigma left21:45
SRabbelier gitster: ah, that works, thanks!21:46
bushwakko left21:47
hakunin_hakunin21:47
Thell anyone aware of a monotone <-> git bridge?21:47
hagabaka is there a way to list the filenames of a repository without cloning it?21:48
lucsky left21:49
SRabbelier hagabaka: if there's a gitweb for it you can look at it's tree view, otherwise no21:50
hagabaka oh21:50
loincloth left21:52
Thell what would be the normal [prefix] for the git mailing list if your posting a script just to share with others? We have a MS VS git-describe generated FileVersionInfo.h script other may find useful...21:53
SRabbelier Thell: you could use [FYI patch]21:54
jceb left21:54
Thell sounds good21:54
kpreid_ joined21:54
mfilipe joined21:54
suman joined21:56
lll left21:57
bremner__ left21:58
bremner_ joined21:58
kurkale6ka after a dd, is there a way to paste without the newline?21:58
alley_cat left21:59
boto left21:59
bremner___ left21:59
Ilari kurkale6ka: dd?22:00
kurkale6ka delete a line!22:00
sorry, vim channel22:00
awnstudio joined22:01
Sent left22:01
hgimenez joined22:01
elliottcable left22:01
kpreid_ left22:02
bdimcheff left22:02
qrush_ left22:03
qrush joined22:03
hgb21 left22:03
sgh_ left22:04
DavidKlein left22:06
bremner__ joined22:07
AkumaStreakAkumaAFKSpeaking22:07
martianlobster Sorry to repeat myself, but I am a git noob, and I still don't understand if there is some sort of version number which gets incremented with a push or a commit. Is there a version number? Is there some way for me to look at two different git repositories, which were cloned from the same base, and see which one is newer, and which needs to have a "git pull" command executed?22:07
AkumaAFKSpeakingAkumaStreak22:07
Ilari martianlobster: No, there isn't incremential version numbers.22:08
martianlobster is there anything like, a last pull date stored somewhere?22:08
Ilari: thanks for telling me about the version numbers22:08
Ilari martianlobster: Well, just try to fetch and merge? It will say so if you are up to date...22:09
martianlobster ok22:09
Theravadan left22:11
tbuehlmann left22:11
Ilari martianlobster: There is way to compare two commits: 'git rev-parse A^{commit} B^{commit}' to resolve them, then 'git merge-base <id-A> <id-B>'. If <id-A> and <id-B> are equal, the commits are the same, if merge-base is <id-A>, then <id-B> is newer. If merge-base is <id-B>, then <id-A> is newer. If merge-base is neither <id-A> nor <id-B>, then neither is newer. If merge-base produces no result, then they are disjoint.22:11
martianlobster: The end is: "... If merge-base produces noresult, then they are disjoint." (in case it cuts off).22:12
fluxusps left22:12
hgb21 joined22:12
Ilari martianlobster: That is sufficiently complicated so it is best made a script.22:12
bremner__ Or use gitk22:13
mfilipe left22:13
ereslibre joined22:14
drewolson left22:16
godsflaw_ left22:17
d2dchat left22:18
intripoon left22:20
martianlobster left22:20
godsflaw joined22:21
bdimcheff joined22:23
paltman94 left22:23
barfbarfbarf joined22:24
rolfb left22:24
hgb21 left22:24
bremner__ left22:25
maattd left22:25
maattd joined22:26
barfbarfbarf hello...is the the right place to ask a user level question?22:27
selckin sure22:27
barfbarfbarf my question is regarding the git branch -a command...22:27
I see two origin branches, one called HEAD the other master22:28
(I cloned a remote)22:28
temoto joined22:28
barfbarfbarf the question is what is the difference between origin/HEAD and origin/master?22:28
mugwump you don't normally get origin/HEAD22:29
barfbarfbarf here's what I did...22:30
charon mugwump: well yes, if the remote has one...22:30
barfbarfbarf git clone [email@hidden.address]22:30
cd <projname>22:30
git branch -a22:30
* master22:31
origin/HEAD22:31
origin/master22:31
bdimcheff left22:31
charon barfbarfbarf: basically, the HEAD of a remote (i.e., its bare repository) is a way of saying which branch should be the default22:31
barfbarfbarf ok, so they are essentially the same?22:32
mugwump oh wow, haven't seen that before22:32
that must be new22:32
lhz left22:32
barfbarfbarf might be a github thing22:32
bremner_ left22:33
charon barfbarfbarf: actually my git says 'origin/HEAD -> origin/master'22:33
i.e., 'git branch -a' shows what origin/HEAD points to22:33
kpreid_ joined22:33
Rovanion joined22:33
mugwump yeah mine too, neat22:33
barfbarfbarf charon: nope, not mine.... checking version of git installed....22:34
mugwump it's not in my .git/config though22:34
barfbarfbarf git version 1.6.2.222:34
mugwump I'm on 1.6.3.322:34
barfbarfbarf I'll try upgrading... I'm just using whatever macports installed ;)22:34
spaceonline left22:34
suman left22:34
drubies joined22:34
barfbarfbarf 'origin/HEAD -> origin/master' makes sense to me22:35
godsflaw_ joined22:35
drubies left22:35
ctusar left22:37
barfbarfbarf thanks for the help!!22:37
WALoeIII left22:38
WALoeIII joined22:38
priidu left22:38
Ceeram how would i put following into alias: git diff HEAD > foo.txt, i tried with git config --global alias.foo 'diff HEAD > foo.txt' but that doesn work giving fatal. the first statement itself does work22:40
agile left22:41
godsflaw left22:41
charon in any case, odds are about 99% it points to origin/master22:41
209d33622:41
charon left22:41
Gitbot [git 209d336]: http://tinyurl.com/yj89hxe -- builtin-branch: improve output when displaying remote branches22:41
austindog joined22:42
charon joined22:43
babilen left22:44
charon Ceeram: you can use tricks such as '!sh -c "git diff HEAD > \$1" foo'22:45
though you should note that ! aliases always run at the repo root22:45
Weasel[DK] left22:46
Ceeram i am at root of the repo22:46
command itself runs ok, then i want to alias it, then running the alias gives the fatal22:46
austindog If I'm using git svn and create a .gitignore file usually I like to commit it (so it is tracked), but I don't want to propagate that commit back upstream to the subversion server. Is there any way to tell git svn to selectively ignore some git commit when sending the data back to the subversion server?22:47
Ilari Ceeram: What fatal error?22:47
Ceeram fatal: ambiguous argument '>': unknown revision or path not in the working tree.22:47
austindog left22:47
austindog_ joined22:48
Ceeram Use '--' to separate paths from revisions22:48
Ilari Ceeram: Hmm... For some reason it is interpretting '>' as part to pass to command.22:48
Ceeram but running git diff HEAD > foo.txt works fine22:48
charon Ceeram: with my shell command or a plain alias?22:49
bremner_ joined22:49
Ceeram didnt try your shell command charon22:49
sorry guys im no command line hero22:50
im on well you know what os im on, only my git repo is on linux22:50
krenso joined22:51
krenso hello22:51
austindog_ left22:52
krenso i have problem with git format-patch22:52
charon Ceeram: well the point is, ordinary aliases without the leading ! are simply shorthands for git commands22:52
rudi_s_ left22:52
aresnick joined22:53
Ceeram well git diff is a git command right?22:53
charon Ceeram: yes but the effect of having an alias mydiff = 'diff HEAD > foo.txt' is that of saying 'git diff HEAD ">" foo.txt' in the shell: the > never has a special meaning22:53
you need ! to go through the shell22:54
bdiego left22:54
krenso i got From: =?UTF-8?q?Roman=20Fro=C2=B3ow?22:54
instead From: =?UTF-8?q?Roman=20Fro=C5=82ow?22:54
Ceeram charon: you lost me there, sorry my bad, well i just keep typing it by hand22:54
cloudhead joined22:55
Turias left22:55
Ilari C2 B3 => codepoint 0xB3 => SUPERSCRIPT THREE C5 82 => codepoint 0x142 => LATIN SMALL LETTER L WITH STROKE ... Hmm...22:55
krenso when i create some html page in vim, firefox displays it correctly22:56
barfbarfbarf fyi, I just upgraded to 1.6.5.1 and now "git branch -a" shows "remotes/origin/HEAD -> origin/master" which makes my head stop hurting22:56
krenso with utf8 encoding selected22:56
mrlemao joined22:57
Ilari krenso: What's hexdump of author name in commit?22:57
bremner__ joined22:57
krenso how should i get it?22:58
temoto left22:58
krenso hexdump patch?22:58
Haarg left22:59
manithree left22:59
Ilari krenso: Dump the commit, extract correct line (using head and tail) and then run it through od -t x1?22:59
secoif joined22:59
krenso here is patch dumped http://dpaste.com/112392/plain/23:00
how to dump the git commit23:01
Ilari krenso: 'git cat-file commit <id>'.23:02
aliceinwire left23:02
Ilari krenso: Then '| head -x | tail -1' to get the author line. Then pass to '| od -t x1' to get hex dump.23:02
krenso: (x is some number, depending on commit).23:03
Altreus left23:03
Altreus joined23:03
Ilari krenso: I would guess that x = 3...23:03
lresende joined23:03
Ilari krenso: You may try 'git cat-file commit f959c128650d16e1d91ea59ab1fa6f0fff769c2d | head -3 | tail -1' and see if it produces 'author ...'.23:05
countd left23:05
JackWinter left23:05
JackWinter joined23:06
bx2 left23:06
ixti left23:07
patmaddox left23:08
EricInBNE joined23:08
krenso Ilari: thanks, commit was wrong23:08
Ilari krenso: Yeah. Everything in commit should be UTF-8 encoded unless shown otherwise...23:09
s/shown/specified/23:09
ludde left23:09
godsflaw__ joined23:09
krenso what about git config --global format.headers "Content-Type: text/plain; charset=\"utf-8\""23:11
mcella joined23:11
jon joined23:11
jonjonthefly23:11
jonthefly hey23:11
krenso when should i use it?23:11
Ilari krenso: Doesn't help. This is about commit encodings (presumably set by 'encoding' header, defaulting to UTF-8 if absent).23:11
jonthefly Is there a way to create a new repository based of an existing folder and preserve history?23:12
Ilari jonthefly: No. Git history is whole-project history. Smallest unit that can be copied with history is branch.23:12
jonthefly I do not care if the history changes to new object id's23:13
fualo left23:13
jonthefly i just want the new folder to contain the diff's and versions of old code23:13
jrmuizel left23:13
Ilari jonthefly: Well, man git-filter-branch23:13
Gitbot jonthefly: the git-filter-branch manpage can be found at http://git.or.cz/man/git-filter-branch23:13
jonthefly ahh23:13
cool ill take a look thanks23:13
trip0 left23:14
WebDragon left23:16
bremner__ left23:16
qrush left23:16
Ryback_ left23:17
jonthefly ahh so in theory what i could do.23:17
is clone the repo.23:17
git filter-branch --tree-filter 'rm filename' HEAD23:17
for all files that i do not want to keep23:17
mfilipe joined23:17
corni left23:18
bremner_ left23:18
WebDragon joined23:19
godsflaw_ left23:19
marcelo joined23:19
marcelo hello23:19
does anyone know why this would happen: http://pastie.org/67089823:19
I have no idea on how to solve it :(23:19
tbf left23:20
Azeroth-Work joined23:20
selckin yell at the server admin23:20
Ilari marcelo: Maybe broken gitosis/gitolite install?23:21
marcelo Ilari, it does work from other clients. From my laptop, it connects fine23:22
However, from a specific location, it hangs like this23:22
icwiener left23:22
marcelo maybe a DNS issue?23:22
Ilari marcelo: What does 'ssh git@<host>' yield?23:23
mrlemao left23:23
marcelo Ilari, it goes :S23:24
I mean, it accesses23:24
weird23:24
Ilari marcelo: Shell?23:24
marcelo yes23:24
kurkale6ka left23:24
Ilari marcelo: Can you pastebin ~/.ssh/authorized_keys (from the remote account)?23:24
Dashkal left23:25
ToyKeeper joined23:25
mcella left23:26
ToyKeeper wonders how to make "git merge --no-ff" default23:27
marcelo hmm23:28
is there a way to, when you ssh to another server, use the public key from the origin server?23:28
Ilari marcelo: agent forwarding (it has its own problems)?23:30
ToyKeeper: AFAICT, can't be done.23:30
Rovanion left23:30
marcelo Ilari, ah, yeah23:30
that's tru23:30
true23:30
khiraly1 joined23:31
muthu joined23:31
khiraly1 hi23:31
git checkout HEAD~1023:31
how can I come back to my latest commit?23:31
Ilari khiraly1: 'git checkout <branch>'.23:31
ToyKeeper Hmm, this looks promising... "git config --global alias.merge 'merge --no-ff'"23:31
Ilari ToyKeeper: Doesn't work.23:31
khiraly1 Ilari: hmm, thats true23:32
ctusar joined23:32
Ilari ToyKeeper: Neither builtins nor external subcommands can be overridden with aliases.23:32
Azeroth-Working joined23:33
Ceeram_away joined23:33
patcito left23:33
ToyKeeper Okay, I guess I can at least alias something like 'mg = merge --no-ff'.23:33
Ilari ToyKeeper: That does work... But why you want --no-ff? git svn?23:34
makeworkeasy joined23:34
ToyKeeper I just can't think of any time I'd ever want to merge inline... it's probably the biggest thing which bugs me about git and hg.23:34
madewokherd left23:34
xname joined23:34
patcito joined23:35
Ilari ToyKeeper: If two developers use --no-ff, the history will never converge.23:35
Geralt left23:35
ToyKeeper I tend to branch, break everything to add a feature, spend ten revisions fixing it, and then merge once the branch is tested. I don't want the intermediate revisions in master.23:35
Maybe --no-ff is the wrong approach to get explicit merging?23:36
gunmuc left23:36
Ilari ToyKeeper: interactive rebase.23:36
ToyKeeper: And merge WILL make those commits part of master.23:36
justin-george joined23:36
ToyKeeper If master changed during my revisions, it gives me an explicit branch anyway. But if master hasn't changed, everything goes inline.23:37
Ideally, I'd want master to contain nothing except merges, with all development happening in bugfix or feature branches.23:37
Ilari ToyKeeper: Yeah, but in both cases the commits become part of master branch.23:38
ToyKeeper They're in the repository, but a graph would show they're not on the main line of history.23:38
slabbeh joined23:38
Ilari ToyKeeper: They are on master branch.23:39
ToyKeeper I get the feeling I'm using the wrong terminology... sort of new to git.23:40
qhoxie left23:40
patcito left23:41
Ilari ToyKeeper: Minimizing merges is usually seen as good thing. Of course, as soon as you have multiple main branches or multiple people involved, the synchronization between those creates merges (too painful to avoid).23:41
ToyKeeper: s/merges/merge commits/23:41
patcito joined23:42
patcito left23:42
Ilari ToyKeeper: Merging B into A makes all commits of B part of branch A. Even if you delete B, these commits still remain in A.23:42
ryoma left23:43
patrikf left23:43
ToyKeeper Yes, just not on the main development line.23:43
SRabbelier left23:43
ToyKeeper I'm basically trying to make all merges go like this: http://toykeeper.net/tmp/git-explicit-branch.png23:43
lamont left23:44
Ilari ToyKeeper: That's meaningles.23:44
ToyKeeper Basically, that creates a single line of history which contains only "cooked" versions, without broken development versions.23:44
Ilari ToyKeeper: After finishing development branch, use rebase to break it down to logical chunks (so that each works).23:45
ToyKeeper That's a lot of extra work, and not always very feasible.23:45
Ilari ToyKeeper: Its not a lot of extra work...23:45
jrmuizel joined23:46
Ilari ToyKeeper: And don't go submitting such stuff to other's projects (it causes problems with format-patch and looks ugly).23:46
ToyKeeper I may spend a week working on a new feature, submit it for review, spend a few more days adding things suggested by review, and then at the end have a branch which is ready to merge. So, the git approach is to flatten the changes or rewrite them to ensure each step is fully functional?23:48
lamont joined23:48
Ilari ToyKeeper: Flattening the changes is not done by --no-ff merge.23:49
Ceeram left23:49
ToyKeeper No, it's not. I'm just asking what the preferred approach is.23:49
Azeroth-Work left23:50
Ilari ToyKeeper: You should break it into logical chunks before submission. Then the changes can be done using 'edit' in interactive rebase...23:50
ToyKeeper: Combining stuff using interactive rebase is quite easy. Splitting it is bit more involved but doable.23:51
ToyKeeper If I gut and replace a core component of a program, it might not be functional at all during development... that could be a pretty large logical chunk.23:53
Ilari ToyKeeper: Also quite helpful is when noticing a bug, fixing it in the commit it was made in...23:53
lohrun left23:53
Ilari ToyKeeper: Well, then squash all that into one commit. It will be large one, but it is logical chunk.23:53
patcito joined23:54
ciskje left23:54
Ilari ToyKeeper: Note that just having the broken commits merged there will mess with bisect.23:54
ToyKeeper That's actually part of the point of using explicit branches instead of inlining it during merge.23:55
yaotti joined23:55
ToyKeeper Explicit branches don't mess with bisect, even if they contain broken code.23:56
Ilari ToyKeeper: Merging with --no-ff won't help with bisecting a bit. In fact, wheither merge is done using --no-ff or --ff should not alter what bisect offers for testing at all.23:56
ToyKeeper Strange.23:56
qrush joined23:56
d2dchat joined23:57
Ilari ToyKeeper: In git, branches can be non-linear.23:57
gitster has long wondered if "git bisect --first-parent" mode is sensible...23:57
ToyKeeper Is there any way to tell what a branch was called after it has been merged and the original branch deleted?23:57
gitster No.23:57
Chillance joined23:58
gitster You can guess by reading "Merge ... branch" messages, though.23:58
ToyKeeper ... if a merge was recorded.23:58
gitster branch in git is illusion.23:58
ToyKeeper So it seems.23:59
Ilari The history might contain nontrivial merge from mainline to side branch and then trivial merge side branch to mainline. Messes up --first-parent real good.23:59
bcardarella joined23:59
Ilari Or it is just set of commits satisfying certain properties.23:59
ToyKeeper Yeah, that's a pretty common pattern.23:59
maattd left23:59
Ilari With one distingunished commit.23:59

Logs Search ←Prev date Next date→ Channels Documentation