From: Santiago Torres <santiago@nyu.edu>
To: Mike Hawes <mhawes24@gmail.com>
Cc: git@vger.kernel.org, mh351681@wne.edu
Subject: Re: Bug
Date: Tue, 13 Sep 2016 13:26:59 -0400 [thread overview]
Message-ID: <20160913172658.7s4rhxjwp7j76zp4@LykOS.localdomain> (raw)
In-Reply-To: <B1BB8E37-C36E-4F4A-BC5F-FDA32CE162AF@gmail.com>
Hi, Michael.
It would be helpful to get more context on what triggered this bug. I'm
not a 'core' dev, so there may be a better way to send this. In general,
you want to state the following:
0) Information about your git installation, host system, etc.
1) Information about your repo (was it GitHub? local? self-hosted?)
2) What did you do? (git push origin master? git push?)
3) What happened instead of working? (the error message would be
helpful.
Hope this helps.
Cheers!
-Santiago.
On Tue, Sep 13, 2016 at 01:18:52PM -0400, Mike Hawes wrote:
> To whom this may concern,
>
> I found a bug in git while trying to push my website.
>
> I redid the process and it happened again.
>
> I also tried it on another computer and it happened again.
>
> I was wondering how to claim a bug?
>
> Thank you,
>
>
> Michael Hawes
next prev parent reply other threads:[~2016-09-13 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Santiago Torres [this message]
2016-09-14 22:14 ` Bug Dennis Kaarsemaker
-- strict thread matches above, loose matches on Subject: below --
2020-06-26 21:11 bug Luke Knoble
2020-11-04 16:10 BUG Alex Marginean
2020-11-04 17:02 ` BUG Randall S. Becker
2020-11-04 17:54 ` BUG Randall S. Becker
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160913172658.7s4rhxjwp7j76zp4@LykOS.localdomain \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=mh351681@wne.edu \
--cc=mhawes24@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).