Shawn O. Pearce schrieb:
Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote:
Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote:
Unfortunately, "Fetch" does not yet work[*] from within git-gui, so you
have to fall back to git-fetch on the command line.
It's the scripted fetch that does not work. The symptom is that the output
^^^^^^^^^^^^^^
of at least one of the commands (upload-pack, I think, because what I see
is wire protocol) goes to a newly spawned console instead of wherever it
was redirected to.
I didn't bother reporting since builtin-fetch is on the way (which will
hopefully make this a moot point) and our team here is comfortable with
calling git fetch on the command line.
Hmm. The way the builtin-fetch works this shouldn't happen, but
I'd appreciate it if you could test and report back before that
topic merges into master.
This happens with git 1.5.3 plus the git-gui that comes with that.
FWIW, I'm in the process of merging master of git.git into git/mingw.git,
and then the builtin-fetch series (because on top of that there is my
fork/exec removal series, which I'd like to adjust for Windows). And *then*
I'll be able to report back to you.
-- Hannes
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
