From: "Constantine Plotnikov" <constantine.plotnikov@gmail.com>
To: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
Cc: "Daniel Barkalow" <barkalow@iabervon.org>,
git@vger.kernel.org, davej@codemonkey.org.uk
Subject: Re: [PATCH] Fix argument handling for fetch-pack call when stdout is connected and -q/--quiet is supplied.
Date: Sat, 4 Oct 2008 00:33:35 +0400 [thread overview]
Message-ID: <85647ef50810031333m254036bav81d6dd4a58fb56da@mail.gmail.com> (raw)
In-Reply-To: <4ac8254d0810031318j3e0f326ewc4bf250c51681670@mail.gmail.com>
I think such patch would be too harsh for IDE plugin developers. When
git is run from IDE, the isatty(1) will be true. But progress
information will be still useful, to display an operation progress to
user. Please provide a way to force output of progress (for example
using environment).
Regards,
Constantine
On Sat, Oct 4, 2008 at 12:18 AM, Tuncer Ayaz <tuncer.ayaz@gmail.com> wrote:
> On Fri, Oct 3, 2008 at 9:50 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
>> On Fri, 3 Oct 2008, Tuncer Ayaz wrote:
>
> <snip>
>
>>> diff --git a/transport.c b/transport.c
>>> index 71433d9..1f24011 100644
>>> --- a/transport.c
>>> +++ b/transport.c
>>> @@ -644,7 +644,7 @@ static int fetch_refs_via_pack(struct transport *transport,
>>> args.include_tag = data->followtags;
>>> args.verbose = (transport->verbose > 0);
>>> args.quiet = args.no_progress = (transport->verbose < 0);
>>> - args.no_progress = !isatty(1);
>>> + args.no_progress = args.quiet || !isatty(1);
>>
>> If you're doing that, remove the "args.no_progress =" from the previous
>> line, which was there to have that effect (but not so clearly). Aside from
>> that, it looks good to me.
>>
>
> <snip>
>
> Thanks Daniel, that makes a lot of sense.
>
> Signed-off-by: Tuncer Ayaz <tuncer.ayaz@gmail.com>
> ---
> transport.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/transport.c b/transport.c
> index 71433d9..35cac44 100644
> --- a/transport.c
> +++ b/transport.c
> @@ -643,8 +643,8 @@ static int fetch_refs_via_pack(struct transport *transport,
> args.use_thin_pack = data->thin;
> args.include_tag = data->followtags;
> args.verbose = (transport->verbose > 0);
> - args.quiet = args.no_progress = (transport->verbose < 0);
> - args.no_progress = !isatty(1);
> + args.quiet = (transport->verbose < 0);
> + args.no_progress = args.quiet || !isatty(1);
> args.depth = data->depth;
>
> for (i = 0; i < nr_heads; i++)
> --
> 1.6.0.2
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-10-03 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 19:34 [PATCH] Fix argument handling for fetch-pack call when stdout is connected and -q/--quiet is supplied Tuncer Ayaz
2008-10-03 19:50 ` Daniel Barkalow
2008-10-03 20:18 ` Tuncer Ayaz
2008-10-03 20:33 ` Constantine Plotnikov [this message]
2008-10-03 20:39 ` Daniel Barkalow
2008-10-03 20:44 ` Tuncer Ayaz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85647ef50810031333m254036bav81d6dd4a58fb56da@mail.gmail.com \
--to=constantine.plotnikov@gmail.com \
--cc=barkalow@iabervon.org \
--cc=davej@codemonkey.org.uk \
--cc=git@vger.kernel.org \
--cc=tuncer.ayaz@gmail.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.
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 NNTP newsgroup(s).