Re: Bug report: GIT PRO/Branches chapter

From: Robert Macháček <lighthunt.net@gmail.com>
Date: Sep 9, 2015, 08:16 UTC
Message-ID: <CACwN7xFU4yFeh=RPmPk4kwKBL5WjTB7pBY8RFFFNgf+k-a_Q4w@mail.gmail.com>
In-Reply-To: <9039e46ed0bc66aec7b30c24183acdb0@dscho.org>

Hi Johannes,

Sorry, I am new to git, I have just followed instructions at https://git-scm.com/community which says:

Mailing List Questions or comments for the Git community can be sent to the mailing list by using the email address git@vger.kernel.org. Bug reports should be sent to this mailing list.

The last sentence is made with BOLD font and I assumed that this applies to the book as well as it is hosted on this domain (so what other bugs are they talking about BTW?)

I'll have a look to github*/issues as you've suggested.

Thanks, Robert

On Wed, Sep 9, 2015 at 3:08 PM, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:

Show 22 quoted lines

> Hi Robert,
>
> On 2015-09-09 08:11, Robert Macháček wrote:
>
>> Just reading this chapter:
>> https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell
>>
>> I believe that: Figure 3-9. Divergent history
>> (https://git-scm.com/book/en/v2/book/03-git-branching/images/advance-master.png)
>> does not show the final "2 branch situation" as described in the
>> example in this chapter.
>
> I guess you want to report it here:
>
>     https://github.com/progit/progit2/issues
>
> (as suggested by the link on the left side of the page you referred to, where it says: "The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome.")
>
> You might want to search the tickets first, though, to make sure that it has not been reported before (or even already addressed).
>
> Ciao,
> Johannes