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

Re: [PATCH 7/7] Documentation: git-init: flesh out example

From
Linus Arver <linusarver@gmail.com>
Date
Aug 6, 2014, 05:34 UTC
Message-ID
<20140806053428.GD12559@k0>
In-Reply-To
<xmqqegwuoa7b.fsf@gitster.dls.corp.google.com>
On Tue, Aug 05, 2014 at 03:14:48PM -0700, Junio C Hamano wrote:
Show 21 quoted lines
> Linus Arver <linusarver@gmail.com> writes:
> 
> > Signed-off-by: Linus Arver <linusarver@gmail.com>
> > ---
> >  Documentation/git-init.txt | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
> > index b94d165..16e9f9c 100644
> > --- a/Documentation/git-init.txt
> > +++ b/Documentation/git-init.txt
> > @@ -138,10 +138,12 @@ Start a new Git repository for an existing code base::
> >  $ cd /path/to/my/codebase
> >  $ git init      <1>
> >  $ git add .     <2>
> > +$ git commit    <3>
> 
> I agree it is a good discipline to make the initial "pristine"
> import immediately after "git add ." without doing anything else.
> Perhaps the description below wants to make it more explicit?
> 
I could add a comment like the following:
    For new repositories, creating a commit immediately after "git add
    ." is good practice as it will cleanly separate any preexisting work
    (done under some other VCS, for example) from any new work done with
    git.

Does this make sense? I am not sure how explicit you want it to be, or whether I captured what you wanted to be explained.

Actually, I would like to know if anything is special about the "root-commit" (I only know it is written as such, with a hyphen, because that is what you get from git's output message). I am not sure if this "root-commit" idea is explained in detail in git's other documentation.

Show 10 quoted lines
> >  ----------------
> >  +
> > -<1> prepare /path/to/my/codebase/.git directory
> > -<2> add all existing file to the index
> > +<1> Create a /path/to/my/codebase/.git directory.
> > +<2> Add all existing files to the index.
> > +<3> Create the first root-commit.
> >  
> >  GIT
> >  ---
Previous: Junio C HamanoNext: Junio C Hamano
Message 20 of 30 in “lots of documentation fixes/rewordings in git-init(1)”
  1. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 2, 2014
  2. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 2, 2014
  3. Junio C HamanoAug 5, 2014
  4. Linus ArverAug 6, 2014
  5. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 2, 2014
  6. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 2, 2014
  7. Junio C HamanoAug 5, 2014
  8. Linus ArverAug 6, 2014
  9. Junio C HamanoAug 6, 2014
  10. Linus ArverAug 8, 2014
  11. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 2, 2014
  12. Junio C HamanoAug 5, 2014
  13. Linus ArverAug 6, 2014
  14. Junio C HamanoAug 6, 2014
  15. Linus ArverAug 8, 2014
  16. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 2, 2014
  17. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 2, 2014
  18. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 2, 2014
  19. Junio C HamanoAug 5, 2014
  20. Linus ArverAug 6, 2014
  21. Junio C HamanoAug 6, 2014
  22. Linus ArverAug 8, 2014
  23. lots of documentation fixes/rewordings in git-init(1)Linus Arver, Aug 8, 2014
  24. 1/7 Documentation: git-init: typographical fixesLinus Arver, Aug 8, 2014
  25. 2/7 Documentation: git-init: list items faceliftLinus Arver, Aug 8, 2014
  26. 3/7 Documentation: git-init: template directory: rewordLinus Arver, Aug 8, 2014
  27. 4/7 Documentation: git-init: --separate-git-dir: clarifyLinus Arver, Aug 8, 2014
  28. 5/7 Documentation: git-init: reword parenthetical statementsLinus Arver, Aug 8, 2014
  29. 6/7 Documentation: git-init: template directory: reword and cross-referenceLinus Arver, Aug 8, 2014
  30. 7/7 Documentation: git-init: flesh out exampleLinus Arver, Aug 8, 2014

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.