From: Nicolas Vilz 'niv' <niv@iaglans.de>
To: git@vger.kernel.org
Subject: Re: [RFC] empty ident?
Date: Sat, 18 Feb 2006 11:00:03 +0100 [thread overview]
Message-ID: <43F6F023.1020708@iaglans.de> (raw)
In-Reply-To: <7vzmkpqco1.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Junio C Hamano wrote:
> It appears that some people who did not care about having bogus
> names in their own commit messages are bitten by the recent
> change to require a sane environment [*1*].
>
> While it was a good idea to prevent people from using bogus
> names to create commits and doing sign-offs, the error message
> is not very informative. This patch attempts to warn things
> upfront and hint people how to fix their environments.
Mh... it made me not using cg-init, but git-init, and after that editing
.git/config, before the first commit.
This doesn't apply to works with git-svn, because here imported commits
are tailored from the base-uuid of the SVN repository and the commit-user.
niv <niv@$uuid>
after that i can setup my .git/config, as well.
Sincerly
Nicolas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-02-18 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 8:44 [RFC] empty ident? Junio C Hamano
2006-02-18 10:00 ` Nicolas Vilz 'niv' [this message]
2006-02-18 17:27 ` [PATCH] Nice error message for empty idents Petr Baudis
2006-02-18 18:55 ` Junio C Hamano
2006-02-19 4:56 ` [PATCH] Delay "empty ident" errors until they really matter Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43F6F023.1020708@iaglans.de \
--to=niv@iaglans.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.