From: Linus Torvalds <torvalds@osdl.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Fix typo in tutorial-2.txt
Date: Mon, 5 Jun 2006 16:58:29 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606051654390.5498@g5.osdl.org> (raw)
In-Reply-To: <20060605234441.GB14993@fieldses.org>
On Mon, 5 Jun 2006, J. Bruce Fields wrote:
>
> But don't commit SHA1's, e.g., depend on times, authors, etc., that we
> can't count on being the same?
You can set all these by hand with the
GIT_{AUTHOR,COMMITTER}_{NAME,EMAIL,DATE}
variables. In fact, the test script library already does that for authors
(although not for dates, I think) to get consistent answers.
Linus
next prev parent reply other threads:[~2006-06-05 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 19:47 Fix typo in tutorial-2.txt Linus Torvalds
2006-06-05 23:15 ` Johannes Schindelin
2006-06-05 23:44 ` J. Bruce Fields
2006-06-05 23:58 ` Linus Torvalds [this message]
2006-06-05 23:38 ` J. Bruce Fields
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=Pine.LNX.4.64.0606051654390.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).