# Bug

3 messages from 2016-09-13 to 2016-09-14. Participants: Mike Hawes, Santiago Torres, Dennis Kaarsemaker.
Thread: https://gitlist.dev/t/44076

## Mike Hawes, 2016-09-13 17:18

Subject: Bug
Message-ID: <B1BB8E37-C36E-4F4A-BC5F-FDA32CE162AF@gmail.com>
URL: https://gitlist.dev/e/B1BB8E37-C36E-4F4A-BC5F-FDA32CE162AF%40gmail.com

```
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

```

## Santiago Torres, 2016-09-13 17:26

Subject: Re: Bug
Message-ID: <20160913172658.7s4rhxjwp7j76zp4@LykOS.localdomain>
URL: https://gitlist.dev/e/20160913172658.7s4rhxjwp7j76zp4%40LykOS.localdomain
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

```

## Dennis Kaarsemaker, 2016-09-14 22:14

Subject: Re: Bug
Message-ID: <1473891298.3248.6.camel@kaarsemaker.net>
URL: https://gitlist.dev/e/1473891298.3248.6.camel%40kaarsemaker.net
In-Reply-To: <B1BB8E37-C36E-4F4A-BC5F-FDA32CE162AF@gmail.com>

```
On Tue, 2016-09-13 at 13:18 -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?

Hi Mike,

When you think git does not behave as you expect, please do not stop
your bug report with just "git does not work".  "I used git in this
way, but it did not work" is not much better, neither is "I used git
in this way, and X happend, which is broken".  It often is that git is
correct to cause X happen in such a case, and it is your expectation
that is broken. People would not know what other result Y you expected
to see instead of X, if you left it unsaid.

Please remember to always state

 - what you wanted to achieve;

 - what you did (the version of git and the command sequence to reproduce
   the behavior);

 - what you saw happen (X above);

 - what you expected to see (Y above); and

 - how the last two are different.

See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for further
hints.

(The above was shamelessly copied from the "A note from the maintainer" mails)

D.

```