From: Yves Goergen <nospam.list@unclassified.de>
To: "Carlos Martín Nieto" <cmn@elego.de>,
"Yves Goergen" <nospam.list@unclassified.de>,
git@vger.kernel.org
Subject: Re: Bug! Git merge also fails with a wrong error message
Date: Fri, 13 Jan 2012 19:59:34 +0100 [thread overview]
Message-ID: <4F107F16.30009@unclassified.de> (raw)
In-Reply-To: <20120113175617.GE2850@centaur.lab.cmartin.tk>
On 13.01.2012 18:56 CE(S)T, Carlos Martín Nieto wrote:
> You still haven't told us what version of (msys)git you're using nor
> have you provided a transcript of your session or found a minimal
> reproducible example.
In case one of my other mails didn't arrive, the Git version is 1.7.8.
There is no session transcript because I use TortoiseGit and I'm not
going to add a screencast here.
> Gmane is a mailing list viewer and there /only/ is the real maling
> list. The e-mail you provided for yourself looks bogus, but if it
> isn't, you'll notice we communicate via e-mail.
Well, I am very confused. Starting from git-scm.com, the only support
site is a mailing list, and the hyperlink on that word sends me to Gmane
which says I am in a newsgroup called "gmane.comp.version-control.git".
Since I don't have access to the news system, I need to use the Gmane
website. I don't know exactly what it is. I know mailing lists, but that
doesn't look like one at all. There's not even a subscription page or
address. For users of the modern web who are not familiar with 70s nntp
technology and cannot use a mailing list by merely knowing its address,
this is very support-unfriendly. I almost would have considered that the
official Git website doesn't want to offer any support at all. In that
case I would likely have searched for an alternative and switched right
away. Assuming I could have extracted the remainders of my source code
from the broken Git repository.
So am I now subscribed to that "git@vger.kernel.org" mailing list and do
my posts show up there? I have no idea what's going on, neither in my
repository, nor in this mailing list. Confusing and intransparent.
--
Yves Goergen "LonelyPixel" <nospam.list@unclassified.de>
Visit my web laboratory at http://beta.unclassified.de
next prev parent reply other threads:[~2012-01-13 18:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 18:44 Bug? Git checkout fails with a wrong error message Yves Goergen
2012-01-13 12:50 ` Holger Hellmuth
2012-01-13 17:46 ` Yves Goergen
2012-01-13 19:28 ` Holger Hellmuth
2012-01-15 8:14 ` Yves Goergen
2012-01-16 11:07 ` Holger Hellmuth
2012-01-16 18:50 ` Yves Goergen
2012-01-16 19:09 ` Jeff King
2012-01-16 21:20 ` Yves Goergen
2012-01-16 21:27 ` Jeff King
2012-01-17 7:41 ` Yves Goergen
2012-01-16 19:17 ` Thomas Rast
[not found] ` <4F152767.9010104@unclassified.de>
2012-01-17 8:45 ` Thomas Rast
2012-01-17 17:56 ` Yves Goergen
2012-01-19 10:24 ` Thomas Rast
2012-01-16 21:18 ` Erik Faye-Lund
2012-01-16 18:58 ` Yves Goergen
2012-01-13 17:37 ` Bug! Git merge also " Yves Goergen
2012-01-13 17:50 ` Jeff King
2012-01-13 18:49 ` Yves Goergen
2012-01-13 18:54 ` Jeff King
2012-01-13 19:05 ` Yves Goergen
2012-01-13 17:56 ` Carlos Martín Nieto
2012-01-13 18:59 ` Yves Goergen [this message]
2012-01-13 19:34 ` Jakub Narebski
2012-01-15 8:17 ` Yves Goergen
2012-01-15 10:08 ` Jakub Narebski
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=4F107F16.30009@unclassified.de \
--to=nospam.list@unclassified.de \
--cc=cmn@elego.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.