From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-send-mail in sh
Date: Sat, 26 Nov 2005 23:35:38 +0100 [thread overview]
Message-ID: <4388E33A.8000004@op5.se> (raw)
In-Reply-To: <7vwtiwmvfp.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Andreas Ericsson <ae@op5.se> writes:
>
>
>>It doesn't CC them, but any number of email-addresses can be specified
>>on the command line (so long as they don't include spaces, but that can
>>be taken care of).
>
>
> Again I do not think I'd ever use that feature from the original
> send-email myself, but the difference is that this CC list
> depends on each commit (sign-offs taken from a commit are
> added to CC list for only that commit).
>
Had a thinko when I wrote that. I've added --cc-signers, --cc-author and
--cc (for both --cc-signers and --cc-author).
> But you are right. We could make a single <commit> a short-hand
> for "origin"..<commit>;
Actually, I meant that a single <commit> would mean "<commit>..HEAD",
like git-format-patch does it. Doing the other way around in a tool so
closely coupled would be very confusing, I think.
Here's what I have on disk right now. The ${var##*^} syntax was decided
to be portable in some earlier discussion, so I'm sticking with it
(mostly because I don't know how to do it with expr and Junio pokes me
when I do it with sed. Enlightenment welcome).
if [ "$com2" ]; then
range="$com1..$com2"
else
case "$com1" in
?*..?*)
# nicely ranged already
range="$com1"
;;
..)
range=origin..HEAD
;;
?*^)
# single commit
com1="${com1##*^}"
range="$com1^1..$com1"
;;
?*^[0-9]|?*^[0-9][0-9])
# series of commits, ranging back from <commit-ish>
range="$com1..${com1%%^*}"
;;
^[0-9]|^[0-9][0-9])
# series of commits, ranging back from HEAD
range="HEAD$com1..HEAD"
;;
*)
range="$com1..HEAD"
;;
esac
fi
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-26 22:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 9:45 git-send-mail in sh Andreas Ericsson
2005-11-25 10:12 ` Nikolai Weibull
2005-11-25 10:59 ` Andreas Ericsson
2005-11-25 11:06 ` Fernando J. Pereda
2005-11-25 11:05 ` Johannes Schindelin
2005-11-25 14:25 ` Andreas Ericsson
2005-11-25 17:20 ` A Large Angry SCM
2005-11-25 11:15 ` Junio C Hamano
2005-11-25 17:26 ` Andreas Ericsson
2005-11-25 18:30 ` Junio C Hamano
2005-11-26 22:35 ` Andreas Ericsson [this message]
2005-11-27 22:01 ` Junio C Hamano
2005-11-27 23:34 ` Andreas Ericsson
2005-11-28 0:15 ` Nikolai Weibull
2005-11-26 20:12 ` Junio C Hamano
2005-11-26 23:34 ` Yann Dirson
2005-11-25 16:33 ` Ryan Anderson
2005-11-25 17:04 ` Andreas Ericsson
2005-11-28 0:49 ` Ryan Anderson
2005-11-28 9:02 ` Andreas Ericsson
2005-11-28 9:34 ` Junio C Hamano
2005-11-29 13:04 ` Andreas Ericsson
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=4388E33A.8000004@op5.se \
--to=ae@op5.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.