git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karl Hasselström" <kha@treskal.com>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/3] Re: Author name and e-mail address in .stgitrc
Date: Sun, 12 Nov 2006 00:23:22 +0100	[thread overview]
Message-ID: <20061111232322.17760.26214.stgit@localhost> (raw)
In-Reply-To: <b0943d9e0611111502q2f68be67l1a2441d84923a732@mail.gmail.com>

On 2006-11-11 23:02:04 +0000, Catalin Marinas wrote:

> On 11/11/06, Karl Hasselström <kha@treskal.com> wrote:
>
> > Is there any particular reason to have the author and committer
> > names in ~/.stgitrc? Simply taking them from the same place git
> > does would probably be a usability enhancement (unless they're
> > specified on the command line, of course).
> 
> At the time I added these to .stgitrc, the only place git was taking
> them from was the environment variables and I wanted to put them in a
> single place. I also didn't like the idea of having the committer
> e-mail address be some username@local-machine as I don't think the
> name of the machine where I create patches is relevant. I also define
> the committer/author per repository in the .git/stgitrc file (i.e. I
> use @arm.com for Linux patches and @gmail.com for StGIT).

Well, this should all be sorted out now; git has both per-repository
and per-user config files.

> I use StGIT almost exclusively, even in "maintainer" mode and I
> would like not to spread the configuration options over many files.
> It is on my todo list to use the same configuration file as git
> (with a [stgit] section) since it has a format that should be
> understood by the Python config module.

The last patch in this series deprecates name and email config in
stgitrc by not mentioning them in the example stgitrc, because
teaching newbies to use yet another layer of identity configuration on
top of what git already provides is madness. Old-timers may continue
using stgitrc for that purpose for now (but as you say, integrating
the configuration with git is on the TODO list).

-- 
Karl Hasselström, kha@treskal.com

  reply	other threads:[~2006-11-11 23:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 11:35 Double From:s in StGIT's patch email template Karl Hasselström
2006-11-11 14:15 ` Author name and e-mail address in .stgitrc Karl Hasselström
2006-11-11 14:31   ` Robin Rosenberg
2006-11-11 14:57     ` Karl Hasselström
2006-11-11 20:26       ` Robin Rosenberg
2006-11-11 22:30         ` Karl Hasselström
2006-11-11 23:02   ` Catalin Marinas
2006-11-11 23:23     ` Karl Hasselström [this message]
2006-11-11 23:30       ` [PATCH 1/3] Ask git for author and committer name Karl Hasselström
2006-11-11 23:35         ` Karl Hasselström
2006-12-04 22:24         ` Catalin Marinas
2006-12-05  9:10           ` Karl Hasselström
2006-12-05  9:17             ` Catalin Marinas
2006-11-11 23:31       ` [PATCH 2/3] Don't mention deprecated template variables Karl Hasselström
2006-11-11 23:31       ` [PATCH 3/3] Deprecate author and committer details in stgitrc Karl Hasselström
2006-11-12  0:20     ` Author name and e-mail address in .stgitrc Karl Hasselström
2006-11-11 14:40 ` Double From:s in StGIT's patch email template Karl Hasselström

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=20061111232322.17760.26214.stgit@localhost \
    --to=kha@treskal.com \
    --cc=catalin.marinas@gmail.com \
    --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 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).