git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: git <git@vger.kernel.org>
Cc: jnareb@gmail.com
Subject: Re: Minor documentation problems
Date: Thu, 2 Nov 2006 12:41:49 +0100	[thread overview]
Message-ID: <20061102114149.GL20017@pasky.or.cz> (raw)
In-Reply-To: <vpqmz7a1694.fsf@ecrins.imag.fr>

  Hi,

Dear diary, on Thu, Nov 02, 2006 at 11:40:23AM CET, I got a letter
where Matthieu Moy <Matthieu.Moy@imag.fr> said that...
> I found minor problems with the doc, which deserve to be fixed:
> 
> * http://www.kernel.org/pub/software/scm/cogito/docs/cg-commit.1.html
>   Mentions .git/config, but not ~/.gitconfig (which is indeed _the_
>   place where I think most people want to set their name and email).

  thanks for pointing this out, further releases will mention both.

>   Side note: it can be interesting to have a command to do this.
>   For example, bzr has "bzr whoami 'me <myself@myisp.com>'", which
>   avoids having to learn the config file syntax.

  Yes, you are certainly not the first to wish this, I'm seriously
thinking about introducing cg-admin-config for setting the most common
configuration variables.

  Moreover, I'm more and more thinking about removing the fallback on
guessing based on /etc/passwd and hostname. _Many_ people were and will
be burnt by it, and I think it's more sane to require the user to
confirm once what the valid credentials are (at _that_ point it's ok to
guess, but the user has to confirm it) than let them unconsciously do
200 commits with completely bogus author lines.

  What do the Git people think? Perhaps we could introduce GIT_NO_GUESS
environment variable which will prevent var.c from guessing?

> * RSS link on the wiki:
>   The URL
>   http://git.or.cz/gitwiki/RecentChanges?action=rss_rc&ddiffs=1&unique=1
>   seems to be working as an RSS feed for changes, but it's not linked
>   to by http://git.or.cz/gitwiki/RecentChanges. Usually, there's an
>   RSS icon, and an HTML <link rel="alternate" ...> to help finding it.

  Fixed, thanks.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1

  reply	other threads:[~2006-11-02 11:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 10:40 Minor documentation problems Matthieu Moy
2006-11-02 11:41 ` Petr Baudis [this message]
2006-11-02 13:20   ` Matthieu Moy
2006-11-02 12:39 ` Minor documentation problems [RFC PATCH] Sean
2006-11-02 13:29   ` Matthieu Moy
2006-11-02 13:54   ` Johannes Schindelin
2006-11-02 14:30     ` Sean
2006-11-02 14:51       ` Johannes Schindelin
2006-11-02 15:44         ` [PATCH] Add --global option to git-repo-config Sean

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=20061102114149.GL20017@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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 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 NNTP newsgroup(s).