From: Alex Riesen <raa.lkml@gmail.com>
To: Nicholas Wourms <nwourms@gmail.com>
Cc: Paul Umbers <paul.umbers@gmail.com>,
git@vger.kernel.org, Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Git Cygwin - unable to create any repository - help!
Date: Thu, 17 Jan 2008 21:30:54 +0100 [thread overview]
Message-ID: <20080117203054.GB3615@steel.home> (raw)
In-Reply-To: <478FA438.9010909@gmail.com>
Nicholas Wourms, Thu, Jan 17, 2008 19:53:44 +0100:
> Alex Riesen wrote:
> >
> > Something is fishy here (aside from the horrible selection of
> > information in the trace output):
> >
>
> That is a matter of opinion. Besides, Cygwin's strace was designed first and
> foremost with debugging the Cygwin dll in mind. Perhaps the choice of name for
> the utility was a poor one, since it implies that it ought to be the same as
> the official strace.
Perhaps. I actually did not intend debugging Cygwin dll at all and
just assumed (being used to the very useful output of linux' strace)
I get something *useful*. It was kinda usefult, just not exactly for
this problem.
As to reporting the issue to cygwin list: there are very trivial
problems which when long enough overlooked tend to give an impression
of malignant stupidity. I expect a wish to change the output of this
particular program in this particular project wont ever be granted
however long argued and whatever the arguments.
Prove me wrong (IOW: report it to cygwin and see something good happen).
next prev parent reply other threads:[~2008-01-17 20:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 17:21 Git Cygwin - unable to create any repository - help! Paul Umbers
2008-01-14 20:29 ` Alex Riesen
2008-01-14 22:21 ` Paul Umbers
2008-01-15 5:48 ` Alex Riesen
2008-01-15 15:21 ` Paul Umbers
2008-01-15 20:04 ` Alex Riesen
2008-01-15 20:12 ` Paul Umbers
2008-01-15 21:20 ` Alex Riesen
2008-01-15 21:57 ` Paul Umbers
2008-01-15 22:51 ` Alex Riesen
2008-01-15 21:59 ` Paul Umbers
2008-01-15 22:55 ` Alex Riesen
2008-01-15 23:02 ` Robin Rosenberg
2008-01-16 7:18 ` Alex Riesen
2008-01-16 15:42 ` Paul Umbers
2008-01-16 17:55 ` Junio C Hamano
2008-01-16 18:10 ` Paul Umbers
2008-01-16 18:38 ` Alex Riesen
2008-01-16 18:57 ` Paul Umbers
2008-01-16 18:31 ` Alex Riesen
2008-01-16 18:48 ` Paul Umbers
2008-01-16 19:12 ` Alex Riesen
2008-01-16 19:17 ` Alex Riesen
2008-01-16 21:44 ` Paul Umbers
2008-01-16 23:45 ` Alex Riesen
2008-01-17 18:37 ` Paul Umbers
2008-01-17 18:51 ` Linus Torvalds
2008-01-17 19:17 ` Johannes Schindelin
2008-01-17 20:13 ` Paul Umbers
2008-01-17 20:24 ` Linus Torvalds
2008-01-17 20:38 ` Pascal Obry
2008-01-17 20:50 ` Johannes Schindelin
2008-01-17 20:53 ` Pascal Obry
2008-01-17 22:32 ` Paul Umbers
2008-01-17 20:18 ` Alex Riesen
2008-01-17 18:53 ` Nicholas Wourms
2008-01-17 20:30 ` Alex Riesen [this message]
2008-01-16 18:50 ` Paul Umbers
2008-01-15 17:08 ` Pascal Obry
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=20080117203054.GB3615@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nwourms@gmail.com \
--cc=paul.umbers@gmail.com \
--cc=torvalds@linux-foundation.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).