Hi again!

On Thu, Aug 12, 2010 at 09:20:22AM +0200, Daniel Fanjul wrote:
> No, it is not an empty repository. I already have commits and other
> branches.
> 
> For example:
> *...@rayado:~/tmp[master]$* mkdir ticgittesting
> *...@rayado:~/tmp[master]$* cd ticgittesting
> *...@rayado:~/tmp/ticgittesting[master]$ *git init
> Initialized empty Git repository in /home/dfanjul/tmp/ticgittesting/.git/
> *...@rayado:~/tmp/ticgittesting$* for i in `seq 5`; do touch $i; git add "$i";
> git ci -m "$i" "$i"; done
> [master (root-commit) 4403532] 1
> ...
> *...@rayado:~/tmp/ticgittesting[master]$* git br
> * master
> *...@rayado:~/tmp/ticgittesting$** cat .git/HEAD
> ref: refs/heads/master*
> *...@rayado:~/tmp/ticgittesting[master]$* ti new
> I, [2010-08-12T08:56:44.996317 #4133]  INFO -- : creating ticgit repo branch
> I, [2010-08-12T08:56:50.058287 #4133]  INFO -- : saving 1281596210_foo_15
> /usr/lib/ruby/1.8/git/lib.rb:643:in `command': git branch -a 2>&1:fatal:
> Failed to resolve HEAD as a valid ref. (Git::GitExecuteError)
> from /usr/lib/ruby/1.8/git/lib.rb:615:in `command_lines'
> from /usr/lib/ruby/1.8/git/lib.rb:209:in `branches_all'
> from /usr/lib/ruby/1.8/ticgit/base.rb:241:in `load_tickets'
> from /usr/lib/ruby/1.8/ticgit/base.rb:72:in `reset_ticgit'
> from /usr/lib/ruby/1.8/ticgit/base.rb:67:in `ticket_new'
> from /usr/lib/ruby/1.8/ticgit/cli.rb:348:in `handle_ticket_new'
> from /usr/lib/ruby/1.8/ticgit/cli.rb:41:in `execute!'
> from /usr/lib/ruby/1.8/ticgit/cli.rb:12:in `execute'
> from /usr/bin/ti:10

Alright, I just had an idea …  Is there any chance you have set color.ui
or color.branch to always in your Git configuration?  This seems to
upset libgit-ruby’s handling of branches in the way you are describing.
If so, try setting it to auto as a workaround (this still enables colour
on the console, but disables it on pipes), and I’ll reassign to
libgit-ruby.

Cheers,
-- 
Michael Schutte <[email protected]>



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to