From: Junio C Hamano <gitster@pobox.com>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: Git Mailinglist <git@vger.kernel.org>
Subject: Re: [bug] pull faulty 'not uptodate'
Date: Wed, 20 Aug 2008 14:50:40 -0700 [thread overview]
Message-ID: <7vwsibnyof.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <EAFC48F0-5512-4A83-B9B2-44FF53319285@ai.rug.nl> (Pieter de Bie's message of "Wed, 20 Aug 2008 23:29:35 +0200")
Pieter de Bie <pdebie@ai.rug.nl> writes:
> On Aug 20, 2008, at 11:22 PM, Junio C Hamano wrote:
>> But I also have to wonder why a git-list regular like you are
>> reporting
>> this _long after_ v1.6.0-rc1 was released. Perhaps this is not
>> really a
>> big-deal bug spelled in capital letters like you have on your Subject
>> line?
>
> I just noticed it and wanted to report it. I thought the usual way to
> do this is to put [BUG] in the subject line. If that is not the common
> way to report bugs, I'm sorry. I can also downcase it ;)
Nah, don't bother --- that wouldn't help. A bug is a bug is a bug.
Checking if it is a regression ("it used to work but recently broken") or
a bug ("it does not work as I expect it") and marking the report as such
would have helped, though.
next prev parent reply other threads:[~2008-08-20 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 21:00 [BUG] pull faulty 'not uptodate' Pieter de Bie
2008-08-20 21:22 ` Junio C Hamano
2008-08-20 21:29 ` [bug] " Pieter de Bie
2008-08-20 21:50 ` Junio C Hamano
2008-08-20 21:50 ` Junio C Hamano [this message]
2008-08-20 22:09 ` "git-merge": allow fast-forwarding in a stat-dirty tree Junio C Hamano
2008-08-20 22:35 ` Miklos Vajna
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=7vwsibnyof.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pdebie@ai.rug.nl \
/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).