On Sun, Mar 12, 2017 at 5:47 AM, Jeff King wrote:
> On Fri, Mar 10, 2017 at 10:50:50PM +0100, Christian Couder wrote:
>
>> I don't think it's a good idea to add those "hint: ..." and
>> "reporting-bugs: ..." lines.
>>
>> I think it's better to do things like the following:
>>
>> - add `git version
On Fri, Mar 10, 2017 at 10:50:50PM +0100, Christian Couder wrote:
> I don't think it's a good idea to add those "hint: ..." and
> "reporting-bugs: ..." lines.
>
> I think it's better to do things like the following:
>
> - add `git version -h`
> - add proper documentation for `git version` so tha
On Fri, Mar 10, 2017 at 7:13 PM, Jonathan Nieder wrote:
> Hi,
>
> Stefan Beller wrote:
>
>> When reporting bugs, users will usually look at the output of
>> 'git --version' at one point to write a quality bug report.
>> So that is a good spot to provide additional information to the user
>> about
Hi,
Stefan Beller wrote:
> When reporting bugs, users will usually look at the output of
> 'git --version' at one point to write a quality bug report.
> So that is a good spot to provide additional information to the user
> about e.g. additional the organizational quirks how to report a bug.
>
>
Git is distributed in various ways by various organizations. The Git
community prefers to have bugs reported on the mailing list, whereas
other organizations may rather want to have filed a bug in a bug tracker
or such. The point of contact is different by organization as well.
When reporting bug
5 matches
Mail list logo
