git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git sideband hook output

From
PJ Hyett <pjhyett@gmail.com>
Date
Jun 11, 2010, 14:34 UTC
Message-ID
<AANLkTikYBB1DsGRRsu4pSNr1j8fFXD-99c4lRAaBqd3M@mail.gmail.com>
In-Reply-To
<AANLkTikQQh4sUA7h2k1jvQ7aMgYyq7WFetJvJZvqpVxt@mail.gmail.com>
Hi,
Show 7 quoted lines
> On Thu, Jun 10, 2010 at 8:30 PM, Shawn O. Pearce <spearce@spearce.org> 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@heroku.com: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@heroku.com: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

Previous: Scott ChaconNext: Wincent Colaiuta
Message 9 of 17 in “Git sideband hook output”
  1. Scott ChaconJun 8, 2010
  2. Shawn O. PearceJun 8, 2010
  3. Peter KjellerstedtJun 9, 2010
  4. Nicolas PitreJun 9, 2010
  5. Peter KjellerstedtJun 10, 2010
  6. Nicolas PitreJun 10, 2010
  7. Shawn O. PearceJun 10, 2010
  8. Scott ChaconJun 10, 2010
  9. PJ HyettJun 11, 2010
  10. Wincent ColaiutaJun 11, 2010
  11. Erik Faye-LundJun 11, 2010
  12. Junio C HamanoJun 11, 2010
  13. Jeff KingJun 12, 2010
  14. A Large Angry SCMJun 11, 2010
  15. Ævar Arnfjörð BjarmasonJun 11, 2010
  16. A Large Angry SCMJun 11, 2010
  17. Johannes SixtJun 9, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.