git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthias Apitz <guru@unixarea.de>
To: git@vger.kernel.org
Cc: Matthias Apitz <guru@unixarea.de>
Subject: small documentation issues
Date: Mon, 20 Mar 2023 13:16:51 +0100	[thread overview]
Message-ID: <20230320121651.GB9@sh4-5.1blu.de> (raw)


Hello,

For the migration from SVN to a local git repository I followed the
document https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git
Chapter 9.2 Git and Other Systems - Migrating to Git
and run into two small issues.

1)
It is explained as an example how the files users.txt should look:
schacon = Scott Chacon <schacon@geemail.com>
selse = Someo Nelse <selse@geemail.com>
I did the error and let away the user fullnames, puting only the mail
addr in the file, i.e. like
schacon = <schacon@geemail.com>
selse = <selse@geemail.com>
because in my case the file has ~50 entries and in some cases the
person's names are not know anymore. This gives the error:

...
        A       sip2slnp/src/main/Sip2SlnpDaemon.c
        A       sip2slnp/src/main/Sip2SlnpServer.c
fatal: name consists only of disallowed characters:
32768 at /usr/lib/perl5/vendor_perl/5.26.1/Git/SVN/Ra.pm line 476.

and it took me a while to understand that the message means that the
full name MUST be there. IMHO this should be noted.

2)
The page says in the section about cleanups after cloning that the
branch 'trunk' should be delted, but this gives an error:

    git branch -d trunk
    error: branch 'trunk' not found.

I do have only:

    git branch --list | egrep 'master|trunk|HEAD'
    * master
      origin/trunk

Thanks for the good doc.

	matthias
-- 
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub

                 reply	other threads:[~2023-03-20 13:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230320121651.GB9@sh4-5.1blu.de \
    --to=guru@unixarea.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).