A while ago, I was wondering how rename tracking in Git worked. I was told that renames didn’t really exist in Git, as Git tracked content, not files themselves. Fair enough.

But, I just stumbled upon something:


1 $ gdc vendor/plugins/acts_as_money/LICENSE
2 diff -git a/vendor/plugins/acts_as_money/LICENSE b/vendor/plugins/acts_as_money/LICENSE
3 index e69de29..a273c73 100644
4 -
- a/vendor/plugins/acts_as_money/LICENSE
5 + b/vendor/plugins/acts_as_money/LICENSE
6 @ -0,0 +1,4 @
7 +one:
8 + user: active
9 + name: name
10 + description: description

Tell me, does that look right? I’ll manually fix that file, but that just decreased my confidence level in Git.

The original LICENSE file was empty, and there apparently was another file (a fixture file) that was empty too, and the latter saw some content added.

Why did this happen? LICENSE was updated as part of a merge—from a branch in which the LICENSE file doesn’t exist.

Git is a wonderful system. It has all kinds of nooks and crannies that one forgets about. Anyway, I was doing client work this morning, and my build server (Integrity, but this isn’t about Integrity) didn’t fail, although my local tests were failing. I began investigating, and vendor/plugins wasn’t even on the build server. Uh? I began investigating, and found vendor/plugins had turned into a git submodule a while back. I even had the commit’s SHA1 of when that happened. I found myself in the unenvious position of having to find and install every plugin we had before that commit back into the application.


1 # 04f7e1 is the commit when the submodule was born
2 # Checkout the commit before that error occured
3 $ git checkout 04f7e1^
4 $ ls vendor/plugins > plugins
5 $ git checkout master
6 $ cat plugins
7 $ script/plugin install git://github.com/giraffesoft/timeline_fu.git
8 # And so on, for the 9 other plugins

And then, there was this one plugin which we haven’t released yet which I was missing. It’s called configurable_mailer, and allows us to configure ActionMailer::Base from tests and from some environment variables. Anyway, I again checked out the code from 04f7e1^, copied vendor/plugins/configurable_mailer outside the repository, checked out master again, and moved the plugin back into place. As you can imagine, this was painful. And error-prone. Then I ran my tests, and immediately had errors. This application is based off of Blank, and was using slightly modified versions of certain plugins. So I added Blank as a remote, fetched and merged. Ran my tests again. Still had errors. And lots of them:


1 $ rake test:units
2 (in /Users/francois/Projects/project)
3 /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -Ilib:test "/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader.rb" "test/unit/account_activation_mailer_test.rb" "test/unit/company_test.rb" "test/unit/event_test.rb" "test/unit/fanship_test.rb" "test/unit/internal_message_test.rb" "test/unit/job_application_test.rb" "test/unit/job_creation_presenter_test.rb" "test/unit/job_suggestion_test.rb" "test/unit/job_test.rb" "test/unit/media_test.rb" "test/unit/message_mailer_test.rb" "test/unit/message_test.rb" "test/unit/password_reset_mailer_test.rb" "test/unit/person_test.rb" "test/unit/profile_url_test.rb" "test/unit/recommendation_mailer_test.rb" "test/unit/recommendation_presenter_test.rb" "test/unit/recommendation_test.rb" "test/unit/relationship_test.rb" "test/unit/timeline_event_test.rb"
4 Loaded suite /Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/rake_test_loader
5 Started
6 …………FFF………EEEEEEEEEEEEE……………………FFFFFFFFFFFFFFFFFFFF.F….F…..EF..EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………….
7 Finished in 45.235105 seconds.
8
9 542 tests, 762 assertions, 26 failures, 73 errors

Bad, I’m telling you. Then I remembered something about git checkout being able to checkout certain paths. I read about this somewhere but I can’t find the source, anymore. Sorry! Without even reading the manual, I set out to work.


1 $ get checkout b fix
2 $ git rm -r vendor/plugins
3 $ git checkout -m "Removing submodule’d vendor/plugins (how did that happen?)"
4 $ git checkout 04f7e1^ -
vendor/plugins

Wall clock time? 10 seconds. I was ready to add and commit.

This is a post to remind you to know your tools, and know them well. Sorry I can’t stay anymore. I’m off to read autotest’s source and documentation, again.

Just received an email from Apple today:

From: devbugs@apple.com
Subject: Re: Bug ID 6543251: Git is not available by default on Leopard

Hello François,

This is a follow up to Bug ID# 6543251. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5404556. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.

Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.

Best Regards,

Kit Cheung
Apple Developer Connection
Worldwide Developer Relations

This is a followup to Want Git preinstalled on next Mac OS X?

They just work. Ain’t that cool ?


1 $ ln -s a b
2 $ git add b
3 $ git commit
4 $ git svn dcommit
5 $ cd ../svn-wc
6 $ svn up
7 $ svn pl -v b
8 Properties on ‘b’:
9 svn:special : *
10 $ ls -l
11 lrwxr-xr-x 1 francois staff 14 29 mai 15:10 a
12 lrwxr-xr-x 1 francois staff 14 29 mai 15:10 b -> a

Did you know symlinks were supported in Subversion since 1.1.0 ? I certainly didn’t remember.

I just found out Howto use Git and svn together, by Flavio Castelli. In there, he lists the steps he uses to develop using Git, but keeping a Subversion repository in the loop.

In his Solve git-svn rebase problems section, Flavio uses git-stash to workaround git-svn rebase problems when your tree has local modifications. I use a different solution. I develop locally on a branch and never commit directly on master. This way I can git-svn rebase with impunity. When I’m ready to merge, I’ll git-svn rebase, followed by git checkout my-branch, git rebase master (to freshen my changes with the remote repository), and finally, I’ll git merge onto master. The steps:


1 git checkout -b francois
2 # work and commit locally on branch francois
3 git checkout master
4 git svn rebase
5 git checkout francois
6 git rebase master
7 # run the tests!
8 git checkout master
9 git merge francois # I might use —squash if the new feature warrants it
10 git svn dcommit # push to Subversion

Overall, my experience with this workflow has been great. I can the features of each system to it’s fullest advantage. I can be on the road, still Gittin’ it done, and the rest of the team still uses Subversion. This is a great combination!

Thanks to Jean-François Couture for showing me the light.

James Bowes has a super simple git-rebase explanation: git rebase: keeping your branches current.

If you have any difficulty understanding the concept, or want an easy way to explain to someone, go ahead.

I’m just starting to use git-svn and git-rebase, and the combination rocks.


1 $ git status
2 # On branch master
3 nothing to commit (working directory clean)
4 $ echo $?
5 1

Shouldn’t a successful git status in a git repository return a status code of 0 ? Doing it in a random folder returns a sensible value:


1 $ git status
2 fatal: Not a git repository
3 Failed to find a valid git directory.
4 $ echo $?
5 128

Can anybody shed some light on this ?

I found Possible bug in ‘git status’ exit code is 1 instead of 0. What is the rational for this ? It goes against everything Unix ?!?

Well, I just got the answer I needed: how to clone just the tip of a remote Git repository ? Here’s how:

Sometimes you just want to distribute the source code without its history, and that’s where git-archive comes in.

git archive <tree-ish> > my_new_archive.tar

Kate Rhodes in Getting just the tip of a Git repo

I think I might use this in Piston. I’m not too sure yet, as I haven’t implemented piston-git, but it looks like a promising candidate.

Now that I’ve had a good change to play with Git, I’m ready to implement Git support in Piston. This will involve a couple of refactorings. I can see 4 cases currently:

Repository Working Copy Strategy
Subversion Subversion Use current strategy of storing data in Subversion properties
Subversion Git Clone the Git repository, copy the files over and store the metadata as Subversion properties. Use Git to handle the merging for Piston (Yay!)
Git Subversion svn export the data and use a hidden YAML file to store the metadata in the pistonized directory
Git Git Use Git submodules perhaps ? Or git clone + copy + YAML

I have no idea how git submodules work, so I can’t really say that I will be handling that last case in the most efficient manner. I’m planning on having completed this work by the end of next week (March 14th). Stay tuned for details !

My friend, Carl Mercier, unveiled Defensio in November 2007. At the time, I had repeatedly told Carl I would write a plugin for Mephisto to integrate with Defensio. Then, in December 2007, TheWebFellas released a plugin that integrated Mephisto and Defensio.

I installed the plugin, but it didn’t work out for me. And then, I had other stuff to do (like nobody does, duh). And now, a couple of months later, I am just learning about Git, and how Git empowers people to make wholesale changes to an application, and still be able to exchange that code with everyone.

I was on the #github channel on Friday night, having some problems creating a new repository. Comes alongs halorgium telling me “why didn’t you name your repository Mephiso ?” Good question. And I asked him if Rick Olson (techno-weenie) had a public Git repository for Mephisto. Halorgium replied with Rick’s repository URL, and told me that it was down at the moment. But, he had a recent clone, which he pushed to GitHub. I then simply forked his repository, and started coding like mad.

It’s now 4 days later, and I am releasing a refactored Mephisto. Instead of being intimately tied to Akismet, or Defensio for that matter, this version of Mephisto uses the Strategy and Adapter design patterns to enable any spam detection engine to connect to Mephisto.

I don’t know Rick personally, nor do I know Mark Dagget, but if they wish, they can now pull from my repository, and the whole Mephisto community will have a much better Mephisto available to them all.

So:

  • If halorgium hadn’t been on #github on Friday, I wouldn’t have known about Rick’s Mephisto repository;
  • If halorgium hadn’t had a clone, I wouldn’t have started then;
  • If I hadn’t been using Git, I wouldn’t have attempted this (too many changes in too many places for Subversion);

Git empowered me to make big changes to a foreign code base. I’m not afraid of losing any of my changes, and anyone can pull from my repository. This is a completely different working model than Subversion.

If you wish to play with this Mephisto version, you can pull from my public clone URL: git://github.com/francois/mephisto.git

Update 2008-03-03: After discussion with Halorgium on #github, I have pushed a multiengine branch. Use that instead of my master, which has been reset.


1 git clone git://github.com/francois/mephisto.git mephisto_defensio
2 cd mephisto_defensio
3 git checkout multiengine
4 rake db:bootstrap db:migrate
5 thin start

If you already have a clone of Mephisto’s repository from someone else, add mine as a remote:


1 cd mephisto
2 git remote add francois git://github.com/francois/mephisto.git
3 git fetch francois
4 git branch —track multiengine francois/multiengine
5 git checkout multiengine
6 rake db:migrate
7 thin start

In case you want to look at the code first, you can browse the GitHub repository using http://github.com/francois/mephisto/tree/multiengine

I suggest starting with Mephisto::SpamDetectionEngine::Base, and exploring from there.

Well, it turns out somebody (probably named dmo?) did all the hard work: Multiple branches using git-svn

If you’re like me, you need to track multiple branches in the same Git repository. I’m going to use this extensively in the XLsuite repository. I have 2 trunks/mainlines: one for the closed source, and one for the open sourced version, I also have a stable version, and some work in progress branches.

Okay, I have a use case which I think shouldn’t be too hard. Jean-François, my Montreal on Rails buddy, gave me a good hand, but I think there’s some interaction going on between Github and git-svn that causes friction…

I have a new project which I want to track using Git, but I also want to keep a push-only Subversion repository on Rubyforge.

So, I started like any old project:


1 $ svn checkout svn+ssh://fbos@rubyforge.org/var/svn/theproject
2 $ svn mkdir tags branches
3 $ newgem theproject
4 $ mv theproject trunk
5 $ svn add trunk
6 $ svn commit -m "New project layout"

Then, I imported that into a fresh Git repository:


1 $ git svn clone svn+ssh://fbos@rubyforge.org/var/svn/theproject -T trunk -t tags -b branches theproject

I then started coding and commiting using Git. All was well, and I was happy. Then, I pushed to Subversion, like any good developer should:


1 $ git svn dcommit

That worked well enough. Then, I was ready to have a public Git repository. I went to Github, where I have an account, and created a new repository. I then did:


1 $ git remote add github git@github.com:francois/theproject.git
2 $ git push github master

That gave me a couple of errors:


1 error: remote ‘refs/heads/master’ is not a strict subset of local ref
2 ‘refs/heads/master’. maybe you are not up-to-date and need to pull first?
3 error: failed to push to ‘git@github.com:francois/theproject.git’

After some discussion with Jean-François, he told me to have a separate branch on which to do development, and merge to master when I am ready to dcommit. So, I did:


1 $ git checkout -b mainline
2 # code again
3 $ git checkout master
4 $ git merge mainline
5 $ git svn dcommit

That works well enough. Now I want to push my mainline to Github. So I do:


1 $ git remote add github git@github.com:francois/theproject.git
2 $ git push github mainline
3 $ git push github mainline
4 updating ‘refs/heads/mainline’
5 from 0000000000000000000000000000000000000000
6 to 31d6eee71b00f829b8568937ab3adaaa8831205c
7 Generating pack…
8 Done counting 201 objects.
9 Deltifying 201 objects…
10 100% (201/201) done
11 Writing 201 objects…
12 100% (201/201) done
13 Total 201 (delta 100), reused 0 (delta 0)
14 refs/heads/mainline: 0000000000000000000000000000000000000000 -> 31d6eee71b00f829b8568937ab3adaaa8831205c

Great! It works. Except… The repository page on Github still shows I need to create the repository. Just for fun, without doing anything else I created a new empty Git repository, touched README, added that, remoted Github and pushed. Voilà, Github showed me the repository, with README being added.

Can anyone shed some light on this ? Here’s a reproduction recipe:


1 $ cat repro.sh
2 #!/bin/sh
3
4 rm -rf repos wc theproject
5 svnadmin create repos
6 svn checkout file:///`pwd`/repos wc
7 cd wc
8 svn mkdir tags branches
9 newgem theproject
10 mv theproject trunk
11 svn add trunk
12 svn commit -m "Initial revision"
13 cd ..
14 git svn clone file:///`pwd`/repos theproject
15 cd theproject
16 echo "The new revision" > README
17 git add README
18 git commit -a -m "New README content"
19 git checkout -b mainline
20 git checkout master
21 git svn dcommit
22 git checkout mainline
23 echo "More content" >> README
24 git commit -a -m "More README goodness"
25 git remote add github git@github.com:francois/theproject.git
26 git push github mainline
27 git checkout master
28 git merge mainline
29 git svn dcommit

And here’s a sample bash +x run:


1 + rm rf repos wc theproject
2 + svnadmin create repos
3 + pwd
4 + svn checkout file:////home/francois/src/repro/repos wc
5 Checked out revision 0.
6 + cd wc
7 + svn mkdir tags branches
8 A tags
9 A branches
10 + newgem theproject
11 create
12 create config
13 create doc
14 create lib
15 create log
16 create script
17 create tasks
18 create test
19 create tmp
20 create lib/theproject
21 create History.txt
22 create License.txt
23 create Rakefile
24 create README.txt
25 create setup.rb
26 create lib/theproject.rb
27 create lib/theproject/version.rb
28 create config/hoe.rb
29 create config/requirements.rb
30 create log/debug.log
31 create tasks/deployment.rake
32 create tasks/environment.rake
33 create tasks/website.rake
34 create test/test_helper.rb
35 create test/test_theproject.rb
36 dependency install_website
37 create website/javascripts
38 create website/stylesheets
39 exists script
40 exists tasks
41 create website/index.txt
42 create website/index.html
43 create script/txt2html
44 force tasks/website.rake
45 dependency plain_theme
46 exists website/javascripts
47 exists website/stylesheets
48 create website/template.rhtml
49 create website/stylesheets/screen.css
50 create website/javascripts/rounded_corners_lite.inc.js
51 dependency install_rubigen_scripts
52 exists script
53 create script/generate
54 create script/destroy
55 create Manifest.txt
56 readme readme
57 Important
58 =====
59
60 * Open config/hoe.rb
61 * Update missing details (gem description, dependent gems, etc.)
62 + mv theproject trunk
63 + svn add trunk
64 A trunk
65 A trunk/Manifest.txt
66 A trunk/History.txt
67 A trunk/doc
68 A trunk/setup.rb
69 A trunk/tmp
70 A trunk/test
71 A trunk/test/test_theproject.rb
72 A trunk/test/test_helper.rb
73 A trunk/tasks
74 A trunk/tasks/deployment.rake
75 A trunk/tasks/website.rake
76 A trunk/tasks/environment.rake
77 A trunk/lib
78 A trunk/lib/theproject.rb
79 A trunk/lib/theproject
80 A trunk/lib/theproject/version.rb
81 A trunk/script
82 A trunk/script/txt2html
83 A trunk/script/destroy
84 A trunk/script/generate
85 A trunk/Rakefile
86 A trunk/website
87 A trunk/website/stylesheets
88 A trunk/website/stylesheets/screen.css
89 A trunk/website/javascripts
90 A trunk/website/javascripts/rounded_corners_lite.inc.js
91 A trunk/website/index.txt
92 A trunk/website/template.rhtml
93 A trunk/website/index.html
94 A trunk/log
95 A trunk/log/debug.log
96 A trunk/config
97 A trunk/config/requirements.rb
98 A trunk/config/hoe.rb
99 A trunk/License.txt
100 A trunk/README.txt
101 + svn commit -m ‘Initial revision’
102 Adding branches
103 Adding tags
104 Adding trunk
105 Adding trunk/History.txt
106 Adding trunk/License.txt
107 Adding trunk/Manifest.txt
108 Adding trunk/README.txt
109 Adding trunk/Rakefile
110 Adding trunk/config
111 Adding trunk/config/hoe.rb
112 Adding trunk/config/requirements.rb
113 Adding trunk/doc
114 Adding trunk/lib
115 Adding trunk/lib/theproject
116 Adding trunk/lib/theproject/version.rb
117 Adding trunk/lib/theproject.rb
118 Adding trunk/log
119 Adding trunk/log/debug.log
120 Adding trunk/script
121 Adding trunk/script/destroy
122 Adding trunk/script/generate
123 Adding trunk/script/txt2html
124 Adding trunk/setup.rb
125 Adding trunk/tasks
126 Adding trunk/tasks/deployment.rake
127 Adding trunk/tasks/environment.rake
128 Adding trunk/tasks/website.rake
129 Adding trunk/test
130 Adding trunk/test/test_helper.rb
131 Adding trunk/test/test_theproject.rb
132 Adding trunk/tmp
133 Adding trunk/website
134 Adding trunk/website/index.html
135 Adding trunk/website/index.txt
136 Adding trunk/website/javascripts
137 Adding trunk/website/javascripts/rounded_corners_lite.inc.js
138 Adding trunk/website/stylesheets
139 Adding trunk/website/stylesheets/screen.css
140 Adding trunk/website/template.rhtml
141 Transmitting file data ……………………
142 Committed revision 1.
143 + cd ..
144 +
pwd
145 + git svn clone file:////home/francois/src/repro/repos theproject
146 Initialized empty Git repository in .git/
147 A trunk/History.txt
148 A trunk/test/test_helper.rb
149 A trunk/test/test_theproject.rb
150 A trunk/License.txt
151 A trunk/log/debug.log
152 A trunk/Rakefile
153 A trunk/setup.rb
154 A trunk/website/template.rhtml
155 A trunk/website/index.txt
156 A trunk/website/javascripts/rounded_corners_lite.inc.js
157 A trunk/website/index.html
158 A trunk/website/stylesheets/screen.css
159 A trunk/Manifest.txt
160 A trunk/script/txt2html
161 A trunk/script/destroy
162 A trunk/script/generate
163 A trunk/config/requirements.rb
164 A trunk/config/hoe.rb
165 A trunk/tasks/deployment.rake
166 A trunk/tasks/website.rake
167 A trunk/tasks/environment.rake
168 A trunk/lib/theproject/version.rb
169 A trunk/lib/theproject.rb
170 A trunk/README.txt
171 W: empty_dir: branches
172 W: +empty_dir: tags
173 W: +empty_dir: trunk/doc
174 W: +empty_dir: trunk/tmp
175 r1 = 01d09dc543711efb5bbd39e71ea2d1fe12516926 (git-svn)
176
177 Checked out HEAD:
178 file:////home/francois/src/repro/repos r1
179 + cd theproject
180 + echo ‘The new revision’
181 + git add README
182 + git commit -a -m ‘New README content’
183 Created commit 16eaad5: New README content
184 1 files changed, 1 insertions(
), 0 deletions(
)
185 create mode 100644 README
186 + git checkout b mainline
187 Branch mainline set up to track local branch refs/heads/master.
188 Switched to a new branch "mainline"
189 + git checkout master
190 Switched to branch "master"
191 + git svn dcommit
192 A README
193 Committed r2
194 A README
195 r2 = 5b2c01dde36111a37f942d9fb6670689089ad9ed (git-svn)
196 No changes between current HEAD and refs/remotes/git-svn
197 Resetting to the latest refs/remotes/git-svn
198 + git checkout mainline
199 Switched to branch "mainline"
200 + echo ‘More content’
201 + git commit -a -m ‘More README goodness’
202 Created commit 49df2b5: More README goodness
203 1 files changed, 1 insertions(+), 0 deletions(
)
204 + git remote add github git@github.com:francois/theproject.git
205 + git push github mainline
206 error: remote ‘refs/heads/mainline’ is not a strict subset of local ref ‘refs/heads/mainline’. maybe you are not up-to-date and need to pull first?
207 error: failed to push to ‘git@github.com:francois/theproject.git’
208 + git checkout master
209 Switched to branch "master"
210 + git merge mainline
211 Auto-merged README
212 CONFLICT (add/add): Merge conflict in README
213 Automatic merge failed; fix conflicts and then commit the result.
214 + git svn dcommit
215 No changes between current HEAD and refs/remotes/git-svn
216 Resetting to the latest refs/remotes/git-svn
217 README: needs update

Well, after reading many interesting articles on Git, I moved Piston’s repository to Gitorious. Clone, fix and extend at will. I will maintain the existing Subversion repository and do releases when fixes come in. I will not maintain Piston itself in any significant ways though.

So, for those of you that expressed an interest in maintaining Piston, go ahead ! Get Git, get coding and publish your repository so I can pull from it.

Piston on Gitorious is available at http://gitorious.org/projects/piston. The mainline (or trunk in Subversion terms) is available as http://gitorious.org/projects/piston/repos/mainline

I have a passing interest in Git. I haven’t migrated my projects over to it now, but am looking into it. Just for fun, I googled “ruby git”, and I found Ruby/Git. I thought more people should know about this.

Hmmm, I know Subversion doesn’t do it any better, but I was led to believe Git tracked directory renames. At least, it didn’t behave as I expected. Here’s a reproduction recipe:

repro.sh

1 #!/bin/sh
2 # This is repro.sh — use at your own risks
3 rm -rf recipe > /dev/null
4 mkdir recipe
5 cd recipe
6 git init
7 mkdir lib
8 echo "v1" > lib/main.rb
9 git add lib/
10 git commit -m "initial version"
11 git checkout -b perf
12 echo "v2" >> lib/main.rb
13 git commit —all -m "perf improvements"
14 echo "v1" > lib/helper.rb
15 git add lib/helper.rb
16 git commit -m "new file"
17 git checkout master
18 git mv lib lib0
19 git commit -m "renamed"
20 git checkout perf
21 git merge master
22 find | grep -v .git


1 $ . repro.sh
2 /home/francois/src/recipe
3 Initialized empty Git repository in .git/
4 Created initial commit a50ea59: initial version
5 1 files changed, 1 insertions(), 0 deletions(-)
6 create mode 100644 lib/main.rb
7 Switched to a new branch "perf"
8 Created commit 73d3379: perf improvements
9 1 files changed, 1 insertions(
), 0 deletions(-)
10 Created commit 01c0e0e: new file
11 1 files changed, 1 insertions(), 0 deletions(-)
12 create mode 100644 lib/helper.rb
13 Switched to branch "master"
14 Created commit 66ac898: renamed
15 2 files changed, 1 insertions(
), 1 deletions(-)
16 delete mode 100644 lib/main.rb
17 create mode 100644 lib0/main.rb
18 Switched to branch "perf"
19 Merge made by recursive.
20 {lib => lib0}/main.rb | 0
21 1 files changed, 0 insertions(+), 0 deletions(-)
22 rename {lib => lib0}/main.rb (100%)
23 .
24 ./lib
25 ./lib/helper.rb
26 ./lib0
27 ./lib0/main.rb

In prose, here’s what I did:

  • Initial development was in lib/main.rb
  • Then, I branched master to create a perf branch
  • On the perf branch, I added lib/helper.rb, and modified lib/main.rb
  • Back on master, I renamed lib/ to lib0/
  • Back on perf, I merged from master

What I expected to see is a move of lib/helper.rb and lib/main.rb to lib0/. Oh well, I don’t rename directories that often anyway. It’s more of a caveat than anything else.

At Montreal on Rails this evening, Jean-François Couture presented Git. I installed it on my Ubuntu Desktop machine, and I found that gitk was horrible to look at. Even after following Jean-François’ Various Tips For Setting Up Git: Improve Gitk Look And Get Bash Completion, gitk wasn’t really up to snuff with the rest of my UI.

On the Git home page, I found a reference to qgit, a much nicer looking application. Install and see for yourself.

Search

Your Host

A picture of me

I am François Beausoleil, a Ruby on Rails and Scala developer. During the day, I work on Seevibes, a platform to measure social interactions related to TV shows. At night, I am interested many things. Read my biography.

Top Tags

Books I read and recommend

Links

Projects I work on

Projects I worked on