Hi,
> On Thu, Jun 10, 2010 at 8:30 PM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote:
>>
>> If its really a problem, maybe "remote: " prefix should turn into
>> something shorter and language agnostic, like "<< ". But thus far
>> we hadn't had to worry about it, since we didn't have translation
>> support in Git... (though yes, I see that is changing now).
>>
I'm also in favor of making the default '>>' instead of 'remote:' if
nothing isn't an option.
Using Heroku as an example, this is what their current hook output looks like:
$ git push origin master
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 684 bytes, done.
Total 5 (delta 2), reused 0 (delta 0)
-----> Heroku receiving push
-----> Sinatra app detected
Compiled slug size is 3.9MB
-----> Launching....... done
http://fi-quote.heroku.com deployed to Heroku
To git@xxxxxxxxxx:fi-quote.git
0bb7fa2..2755742 master -> master
Now, if you compare that to what it would look like if they were
running a more recent version of git, the verboseness of remote: is
quite apparent:
$ git push origin master
Counting objects: 9, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 684 bytes, done.
Total 5 (delta 2), reused 0 (delta 0)
remote:
remote: -----> Heroku receiving push
remote: -----> Sinatra app detected
remote: Compiled slug size is 3.9MB
remote: -----> Launching....... done
remote: http://fi-quote.heroku.com deployed to Heroku
remote:
To git@xxxxxxxxxx:fi-quote.git
0bb7fa2..2755742 master -> master
In a perfect world, I think it should be up to the user to determine
the amount of information they receive (using a verbose switch
perhaps), but short of that, at least toning down what is output would
be much appreciated.
Cheers,
PJ
--
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