git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Djordjevic <igor.d.djordjevic@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Phil Martel <pomartel@comcast.net>,
	git@vger.kernel.org, git-for-windows@googlegroups.com
Subject: Re: Problem installing Git
Date: Sun, 26 Nov 2017 13:15:15 +0100	[thread overview]
Message-ID: <7beb6393-5b64-2f61-48be-a3f5041ea4c3@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1711252312270.6482@virtualbox>

Hi Johannes,

On 25/11/2017 23:16, Johannes Schindelin wrote:
> 
> > [ +Cc:  Git for Windows mailing list ]
> 
> I have no idea why it claimed that that group does not exist, the
> email address looks correct to me.

I suspected the culprit was me not being a member of the group, where 
the group requires it for (initial?) posting (but you already noticed 
that other e-mail about it there[2], this is more a follow-up for 
anyone here, still wondering).

> > p.s. Note the existence of "Git for Windows"[1] specific mailing
> > list as well, where this issue might belong better.
> >
> > [1] git-for-windows@googlegroups.com
> 
> I think a much better place is the Git for Windows bug tracker (if
> you ever wonder where the bug tracker is, or the home page, or the
> repository or the FAQ, there are links in the upper left of the
> release notes -- which probably nobody reads, even if I really try to
> make them worth the while -- and which you can find in C:\Program
> Files\Git\ReleaseNotes.html if you closed the tab after installing
> Git for Windows).
> 
> And indeed, there is already a ticket for this issue:
> https://github.com/git-for-windows/git/issues/1074

I myself am aware of the tracker, just that I didn`t really 
anticipate this as a Git for Windows bug, seeing various mentions 
around the net pointing to Inno Setup (being in use here as well).

That said, I see the logic in thinking the other way around, too, and 
possibly addressing it somehow inside Git for Windows, in spite of 
what happens on Inno Setup side. At least working around it a bit 
better, if possible.

I can remember to keep an eye on the tracker more often, just in 
case, as that would have clearly helped here. Thanks for the heads-up.

Regards, Buga

[2] https://groups.google.com/d/msg/git-for-windows/0hn7Th4uGZk/oJTdmXa5AgAJ

  reply	other threads:[~2017-11-26 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 18:51 Problem installing Git Phil Martel
2017-11-23 21:30 ` Igor Djordjevic
     [not found]   ` <001a1148fe243ade02055ead2599@google.com>
2017-11-23 21:41     ` Delivery Status Notification (Failure) Igor Djordjevic
2017-11-23 23:35   ` Problem installing Git Phil Martel
2017-11-23 23:44   ` Problem installing Git (followup) Phil Martel
2017-11-24  0:12     ` Igor Djordjevic
2017-11-25 22:16   ` Problem installing Git Johannes Schindelin
2017-11-26 12:15     ` Igor Djordjevic [this message]
2017-11-27 21:12     ` Phil Martel

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=7beb6393-5b64-2f61-48be-a3f5041ea4c3@gmail.com \
    --to=igor.d.djordjevic@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=pomartel@comcast.net \
    /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).