Shawn O. Pearce wrote:
What about this on top of Jeff's patch? $ git fetch jc ... ==> git://repo.or.cz/alt-git.git * tag junio-gpg-pub ......................... (new) * tag v1.5.0 .......................... (tag moved) $ git fetch me ... ==> git://repo.or.cz/git/spearce.git * branch gitk -> spearce/gitk ............... (new) * branch maint -> spearce/maint * branch master -> spearce/master * branch next -> spearce/next * branch pu -> spearce/pu ......... (forced update) * branch todo -> spearce/todo ............... (new) The width of the terminal is computed to produce the ... padding. I used a very narrow terminal to produce the above so it doesn't linewrap badly in email. If we cannot get the terminal width then we just don't produce the padding.
Melikes, although using a fairly narrow padding isn't necessarily a bad idea. I usually hate it when the output on the left is 15 chars wide, the one on the right is 5-10 chars wide and there are 60 dots between them. It's ugly and doesn't make it a easier to read. -- Andreas Ericsson andreas.ericsson@xxxxxx OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
