git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 7/9] Documentation: clarify branch creation

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 10, 2009, 00:57 UTC
Message-ID
<7viqeodq0s.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20091009183408.GB2477@progeny.tock>
Jonathan Nieder <jrnieder@gmail.com> writes:
> So this page should probably point to the what-is-a-branch section of
> the User's Manual.  Maybe something like this?
Sounds good.  Thanks
Show 12 quoted lines
> -- %< --
> Subject: Documentation: clarify branch creation
>
> The documentation seems to assume that the starting point for a new
> branch is the tip of an existing (ordinary) branch, but that is not
> the most common case.  More often, "git branch" is used to begin
> a branch from a remote-tracking branch, a tag, or an interesting
> commit (e.g. origin/pu^2).  Clarify the language so it can apply
> to these cases.  Thanks to Sean Estabrooks for the wording.
>
> Also add a pointer to the user's manual for the bewildered.
> ...
Previous: Jonathan NiederNext: Jonathan Nieder
Message 15 of 19 in “Documentation tweaks”
  1. 0/9 Documentation tweaksJonathan Nieder, Oct 9, 2009
  2. 1/9 Describe DOCBOOK_XSL_172, ASCIIDOC_NO_ROFF options in MakefileJonathan Nieder, Oct 9, 2009
  3. 2/9 Documentation: git fmt-merge-message is not a scriptJonathan Nieder, Oct 9, 2009
  4. 3/9 Documentation: fix singular/plural mismatchJonathan Nieder, Oct 9, 2009
  5. 4/9 Documentation: say "the same" instead of "equal"Jonathan Nieder, Oct 9, 2009
  6. 4/9 Documentation: clarify mergeoptions descriptionJonathan Nieder, Oct 9, 2009
  7. 5/9 Documentation: clone: clarify discussion of initial branchJonathan Nieder, Oct 9, 2009
  8. Junio C HamanoOct 9, 2009
  9. 5/9 Documentation: clone: clarify discussion of initial branchJonathan Nieder, Oct 9, 2009
  10. 6/9 Documentation: branch: update --merged descriptionJonathan Nieder, Oct 9, 2009
  11. Junio C HamanoOct 10, 2009
  12. 7/9 Documentation: clarify branch creationJonathan Nieder, Oct 9, 2009
  13. Sean EstabrooksOct 9, 2009
  14. Jonathan NiederOct 9, 2009
  15. Junio C HamanoOct 10, 2009
  16. 8/9 Documentation: clarify "working tree" definitionJonathan Nieder, Oct 9, 2009
  17. 9/9 racy-git.txt: explain nsec problem in more detailJonathan Nieder, Oct 9, 2009
  18. Junio C HamanoOct 10, 2009
  19. Junio C HamanoOct 10, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.