From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: Author name and e-mail address in .stgitrc
Date: Sat, 11 Nov 2006 15:31:15 +0100 [thread overview]
Message-ID: <200611111531.16304.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20061111141530.GF11224@diana.vm.bytemark.co.uk>
lördag 11 november 2006 15:15 skrev Karl Hasselström:
> 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).
AFAIK StGit already does that, at least if you (like me) do not have
a .stgitrc.
next prev parent reply other threads:[~2006-11-11 14:29 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 [this message]
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 ` [PATCH 0/3] " Karl Hasselström
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=200611111531.16304.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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).