s of all topic branches (while each branch has within it the documentation that pertains to it only). (rendered == the main online doc page at http://sitaramc.github.com/gitolite

03[15:27] * himsin (~91.himans@180.149.53.114) has joined #git

[15:27] tango_: that only means it’s probably easier to *detect* an evil merge in git (and force the offendor to take the entire team to lunch)

03[15:28] * thm (421734fed3@fedora/thm) has joined #git

03[15:28] * w0bni (~Mads@cm-84.215.30.88.getinternet.no) has joined #git

[15:28] what is the rationale for git-svn using an empty remote? the branches are named remoes/trunk, for example.

02[15:29] * SimonNa (~simon@p4FC8B570.dip.t-dialin.net) Quit (Ping timeout: 240 seconds)

[15:29] sitaram: the team I’m working at has been using NO any scm for years. Yes, they do that manually. They had written down the changed files list and after that moved the changes manually to production

02[15:29] * ramusara (~ramusara@220.156.210.236.user.e-catv.ne.jp) Quit (Quit: Leaving…)

02[15:29] * sonnym (~sonny@rrcs-184-74-137-69.nys.biz.rr.com) Quit (Read error: Connection reset by peer)

[15:30] that happenned until I came and told them about mercurial :3

03[15:30] * LeglessFlamingo (~quassel@ns.hi-net.cz) has joined #git

03[15:30] * beakerman (~beakerman@216-164-125-3.c3-0.drf-ubr1.atw-drf.pa.cable.rcn.com) has joined #git

03[15:30] * stephenp (~stephenp@204.251.33.100) has joined #git

03[15:30] * bodom (~quassel@2001:470:1f0b:ac0::2) has joined #git

02[15:31] * cggaurav (~Adium@212-181-83-218.customer.telia.com) Quit (Remote host closed the connection)

[15:31] zerkms: there’s nothing wrong with *any* system that works for the team, in a purely philosophical way. (Why else would so many people still be using Windows 95 or 2000 or whatever)? The problem is saying «this is better…» :)

[15:31] well, anything is better that manually doing SCM work

[15:31] even CVS is better

02[15:31] * mklappstuhl (~mklappstu@fak8.grp.tu-berlin.de) Quit (Quit: WeeChat 0.3.5)

[15:32] zerkms: you clearly haven’t heard Linus’s opinions of CVS then. He once famously said exchanging tar balls is better :)

[15:32] IIRC

[15:32] is there a command that lets me see the total number of lines of code in a git repo?

[15:32] well, this question has nothing to do with reset :-(

[15:32] dabukalam: define lines of code. And define «git repo» — all the branches, just the current one, just «master»?

[15:33] oh, I know

02[15:33] * hyperair (~hyperair@ubuntu/member/hyperair) Quit (Read error: Connection reset by peer)

[15:33] blabla, reset all changesets. And asnwer: «the repo have 0 lines now»

02[15:33] * maheshk (~makulkar@nat/nokia/x-bsksimcjzcleywkp) Quit (Remote host closed the connection)

03[15:34] * maheshk (~makulkar@nat/nokia/x-gxaukdisxbncqwal) has joined #git

[15:34] sitaram: the current one. So how many lines of code in the whole thing. I’m using «git ls-files | xargs cat | wc -l» atm, but it’s imperfect because symlinks are counted, and it tries to cat directories with periods in them

03[15:35] * dvaske (~asolsson@nat/nokia/x-sgghwcpgyvndaxuo) has joined #git

02[15:35] * Prasad (~prasadkr@117.192.245.230) Quit (Ping timeout: 258 seconds)

[15:35] I am going to commit a giant branch soon, and just to be pedantic I’d like to see that all unit tests pass at every commit. What is the easiest way to go through each commit from A..B and run a command ?

03[15:36] * Murr_ (~murr@80-218-32-38.dclient.hispeed.ch) has joined #git

[15:36] dabukalam: how is it related to git at all?

[15:36] shruggar: git rev-list A..B | while read line; do git checkout $line; git reset –hard; git clean -fdx; command; done # or similar.

[15:36] (ie, is there an easier way than git rev-list A..B | while read commit do …. yeah

02[15:37] * BiggFREE (~BiggFREE@modemcable215.196-22-96.mc.videotron.ca) Quit (Remote host closed the connection)

[15:37] I think there is, actually, but I can’t remember what it is. В¬_В¬

[15:38] zerkms: I was hoping there would be a command built into git. But I guess I’m hoping for too much…

[15:38] shruggar: man git-for-each-ref

[15:38] shruggar: *automatic message* the ‘git-for-each-ref’ manpage can be found at http://www.kernel.org/pub/software/scm/git/docs/git-for-each-ref.html

[15:38] maybe…

[15:38] nah, rev-list is better.

[15:38] That sounds like what I was thinking but doesn’t sound better, yeah.

[15:38] dabukalam: I cannot get the idea of it. Let’s suppose I have 10 lines file. I removed that 10 lines with another 10 lines

[15:39] so I have 2 commits. How many lines do you expect as an answer?

03[15:39] * replore_ (~replore@ntkngw133234.kngw.nt

Комментарии запрещены.