From: Junio C Hamano <junkio@cox.net>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Ensure author information is set before asking for commit message.
Date: Sat, 13 May 2006 19:41:27 -0700 [thread overview]
Message-ID: <7vlkt5s4yw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <BAYC1-PASMTP10DC791E7560155D9E71F4AEA20@CEZ.ICE> (seanlkml@sympatico.ca's message of "Sat, 13 May 2006 21:51:15 -0400")
Sean <seanlkml@sympatico.ca> writes:
> It's better to find out you need to set your author information
> properly before you enter a long commit message.
>
> Signed-off-by: Sean Estabrooks <seanlkml@sympatico.ca>
Makes sense but I suspect you would want COMMITTER not AUTHOR.
Imagine you pulled from somewhere else and it conflicted,
requiring you to hand resolve and then run git-commit.
next prev parent reply other threads:[~2006-05-14 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060513215115.5bbae2ab.seanlkml@sympatico.ca>
2006-05-14 1:51 ` [PATCH] Ensure author information is set before asking for commit message Sean
2006-05-14 2:41 ` Junio C Hamano [this message]
[not found] ` <20060513230932.41ef4982.seanlkml@sympatico.ca>
2006-05-14 3:09 ` [PATCH] Ensure author & committer " 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=7vlkt5s4yw.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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