From: Sebastian Thiel <byronimo@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-update-index: report(...) now flushes stdout after printing the report line
Date: Mon, 4 Jan 2010 11:30:16 +0100 [thread overview]
Message-ID: <ba5802b21001040230ud27c06bw3531724862cb12c4@mail.gmail.com> (raw)
In-Reply-To: <be6fef0d1001031503h11cb65c6ha34eee345b9b7055@mail.gmail.com>
Thanks Ray Chuan, for the clarification, the progress is supposed to
be sent in git-push and git-fetch ( not git-pull as I mentioned ).
A --progress flag would already do it for me, is there a way to fetch
your code from somewhere for a test run ?
When do you think will your changes be available for a mainline merge,
or would it even be possible to separate the --progress adjustment
from your feature to merge it into mainline individually ?
Thanks,
Sebastian
next prev parent reply other threads:[~2010-01-04 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 21:17 [PATCH] git-update-index: report(...) now flushes stdout after printing the report line Sebastian Thiel
2009-12-30 13:41 ` Nanako Shiraishi
2009-12-30 19:46 ` Junio C Hamano
2009-12-30 13:56 ` Sebastian Thiel
2010-01-03 10:41 ` Sebastian Thiel
2010-01-03 23:03 ` Tay Ray Chuan
2010-01-04 10:30 ` Sebastian Thiel [this message]
2010-01-06 1:04 ` Junio C Hamano
2010-01-06 1:51 ` Tay Ray Chuan
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=ba5802b21001040230ud27c06bw3531724862cb12c4@mail.gmail.com \
--to=byronimo@googlemail.com \
--cc=git@vger.kernel.org \
/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).