From: Will <william.duclot@gmail.com>
To: git <git@vger.kernel.org>
Cc: "Stefan Beller" <sbeller@google.com>
Subject: Re: Git pull confusing output
Date: Tue, 27 Nov 2018 22:34:40 +0000 [thread overview]
Message-ID: <1A9DD0D0-A1CD-44B8-A44A-35D795DA18D1@gmail.com> (raw)
In-Reply-To: <CAGZ79kbDHyzFF-HtDcD=rOLZB+RFRnVqZgXb9uwm=9_m-6E0QA@mail.gmail.com>
On 27 Nov 2018, at 19:24, Stefan Beller wrote:
> The different phases taking each one line takes up precious
> screen real estate, so another approach would be delete the line
> after one phase is finished, such that you'd only see the currently
> active phase (that can be useful for debugging as in "The phase of
> 'Writing objects' takes very long" -> slow network connection).
I like this idea
>>> Pushing to github.com:williamdclt/some-repo.git… done
>>> 1ca9aaa..4320d30 master -> master
>>
>>
>> I’d be more than happy to work on this (`git push` is an example
>> amongst so many other), but want the mailing list’s opinion on it. Am
>> I wrong in thinking that this output is not something users want, am I
>> fighting windmills or maybe just being ignorant?
>
> I think this would be a useful patch, but it could get complicated
> quickly: push uses other low level git commands to prepare the
> packfile to be sent to the server, currently it only needs to pipe
> through the output of the low level command (or even have the
> low level command directly write to the terminal).
>
> The output of those low level commands should not be changed
> when run on their own, I would assume.
Agreed. I didn’t expect it to be so subtle, but I’ll look into it
and see if that’s something within my reach.
next prev parent reply other threads:[~2018-11-27 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 16:52 Git pull confusing output Will
2018-11-27 19:24 ` Stefan Beller
2018-11-27 22:34 ` Will [this message]
2018-11-27 23:37 ` Ævar Arnfjörð Bjarmason
2018-11-28 6:31 ` Junio C Hamano
2018-11-28 20:27 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1A9DD0D0-A1CD-44B8-A44A-35D795DA18D1@gmail.com \
--to=william.duclot@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).