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

Re: how to suppress progress percentage in git-push

From
Jeff King <peff@peff.net>
Date
Nov 23, 2009, 16:43 UTC
Message-ID
<20091123164319.GA23011@sigill.intra.peff.net>
In-Reply-To
<20091123155043.GA28963@machine.or.cz>
On Mon, Nov 23, 2009 at 04:50:43PM +0100, Petr Baudis wrote:
Show 11 quoted lines
> On Mon, Nov 23, 2009 at 10:00:00AM -0500, Jeff King wrote:
> > The patch for (1) would look something like what's below.  It's simpler,
> > but it does change the semantics; anyone who was relying on
> > --all-progress to turn on progress unconditionally would need to now
> > also use --progress. However, turning on progress unconditionally is
> > usually an error (the except is if you are piping output in real-time to
> > the user and need to overcome the isatty check).
> 
> I'm actually doing exactly that in the mirrorproj.cgi of Girocco, so I
> would be unhappy if I would have to go through creating ptys or whatever
> now. Maybe conditioning this by an environment variable?

You wouldn't need to do anything that drastic. You would just need to pass "--progress --all-progress" instead of only --all-progress. But you have provided the data point that such a change would break at least one user.

We could also leave --all-progress as-is and add new option to mean "if you are already doing progress, do all progress".

-Peff
Previous: Petr BaudisNext: Petr Baudis
Message 4 of 16 in “how to suppress progress percentage in git-push”
  1. bill lamNov 22, 2009
  2. Jeff KingNov 23, 2009
  3. Petr BaudisNov 23, 2009
  4. Jeff KingNov 23, 2009
  5. Petr BaudisNov 23, 2009
  6. Jeff KingNov 23, 2009
  7. pack-objects: split implications of --all-progress from progress activationNicolas Pitre, Nov 23, 2009
  8. Petr BaudisNov 23, 2009
  9. Nicolas PitreNov 23, 2009
  10. Petr BaudisNov 23, 2009
  11. Jeff KingNov 23, 2009
  12. Nicolas PitreNov 23, 2009
  13. Jeff KingNov 23, 2009
  14. Nicolas PitreNov 23, 2009
  15. bill lamNov 24, 2009
  16. Jeff KingNov 24, 2009

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.