-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why is the "user-manual" hidden? #1188
Comments
Thanks for reporting this issue @utonsal :) The git-scm website is currently under a redesign work, so this can be addressed very soon. What do you think @jasonlong ? |
I’m out this week, but will take a closer look when I get back. My initial
reaction was that I don’t immediately recognize this page and that we
should definitely include it in the new top-level Manual section.
…On Tue, Mar 20, 2018 at 6:19 AM Pedro Rijo ***@***.***> wrote:
Thanks for reporting this issue @utonsal <https://github.com/utonsal> :)
The git-scm website is currently under a redesign work, so this can be
addressed very soon.
What do you think @jasonlong <https://github.com/jasonlong> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1188 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAX2Abl2GU_sQCZLiKWLS-BjORHt_gwks5tgNeYgaJpZM4Sxmmo>
.
|
Wow. I just spent a few minutes digging for it, and what do you know - it's actually titled "Git's User Manual". It's mentioned briefly in the Description section of In the Git repo, it's Documentation/user-manual.txt. It appears to largely date back to 2007. Man, talk about RTFM. Thanks for bringing this to our attention @utonsal! |
I actually have mixed feelings about So I don't think it's wrong for us to host it or even link to it, but IMHO we should be steering people in search of a prose overview of Git to the book content. |
Am 23.03.2018 um 06:57 schrieb Jeff King:
I actually have mixed feelings about `user-manual.txt`. As you noted, it's pretty old. Most of that stuff hasn't _changed_, but I think that there are better resources these days. Like, say, the Pro Git content we already host, which is more comprehensive and accessible,
has actual non-ascii-art diagrams,
which is a disadvantage, because less universal.
and is more actively maintained.
which is a clear advantage.
There could also be the point, that the book is not considered free
since it's license is CreativeCommons - Non-Commercial.
So I don't think it's wrong for us to host it or even link to it, but IMHO we should be steering people in search of a prose overview of Git to the book content.
greetings,
utonsal
|
It is your opinion that ascii-art diagrams are "more universal". Most of the time it's a bunch of characters that any non-seasoned reader will find ugly and incomprehensible. |
added design label to be considered on #1179 cc @jasonlong |
@pedrorijo91 @jasonlong its this issue is still not resolved? if not I m interested in solving this issue. |
I think it has been considered under the work in #1179 but not sure about the status |
very nice. As from what I see, my point is still not resolved, but
rather has been talked away.
utonsal
Am 06.03.2019 um 09:34 schrieb Prasad Mangesh Gujar:
… @pedrorijo91 @jasonlong its this issue is still not resolved? if not I m interested in solving this issue.
|
Alas, still hidden in 2020. Even if it might not cover recent features, it's still a good medium-length introduction to git, that some users might prefer reading, before delving into the more comprehensive Pro Git book. |
@Vrihub My opinion now is pretty the same as from #1188 (comment). If somebody feels strongly about it enough to make a PR, I wouldn't mind having a link from the |
It's not really hidden, it's featured at the top of the And there is a very good reason not to feature it even more prominently: Git's These updates mostly consist of additions, leaving the existing content unchanged. However, the information provided there is seriously stale. I challenge you to verify that a fresh git.git clone still weighs a mere 40MB, or a clone of linux.git only 640MB. And this issue is just the tip of the tip of the iceberg of issues. In other words, it is probably a very good idea to draw the curtain of charity over this user manual by actively avoiding to draw readers' eyes to it. Having said all that, I could imagine one powerful counter-argument, and really only this one: This counter-argument would need to come in the form of a lengthy patch series on the Git mailing list that would improve, |
Let's just close this, there has no activity that would justify keeping this ticket open. |
hello,
the "user-manual" is stored in git-scm.com/docs/user-manual, but is not viewable when looking in the file git-scm.com/docs/ . Why is it 'hidden' in this way?
I read following notice about opening issues here, but on the [email protected] -mailing list (which is referenced to from git-scm.com/community) , I was redirected here.
"
https://git-scm.com/docs
), which should be raised with the community,"
greetings
The text was updated successfully, but these errors were encountered: