From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Make more commands builtin
Date: Tue, 23 May 2006 14:36:54 +0200 [thread overview]
Message-ID: <e4uvku$o28$1@sea.gmane.org> (raw)
In-Reply-To: 20060523122056.GA5777@bohr.gbar.dtu.dk
Peter Eriksen wrote:
> Btw.
>
> I used these commands to produce the patch series:
>
> git diff --stat -C 24b65a30015aedd..pe/builtin
> git-send-email --no-chain-reply-to --compose \
> --from=s022018@student.dtu.dk --not-signed-off-by-cc \
> --quiet \
> --subject="Make more commands builtin" \
> --to=git@vger.kernel.org Patches/*
I wonder why the patches themselves are not replies to the main/summary
email, i.e. "Make more commands builtin" email...
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-23 12:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11483865361243-git-send-email-1>
2006-05-23 12:15 ` [PATCH 1/8] Builtin git-ls-files Peter Eriksen
2006-05-23 12:15 ` [PATCH 2/8] Builtin git-ls-tree Peter Eriksen
2006-05-23 12:15 ` [PATCH 3/8] Builtin git-tar-tree Peter Eriksen
2006-05-23 12:15 ` [PATCH 4/8] Builtin git-read-tree Peter Eriksen
2006-05-23 12:15 ` [PATCH 5/8] Builtin git-commit-tree Peter Eriksen
2006-05-23 12:15 ` [PATCH 6/8] Builtin git-apply Peter Eriksen
2006-05-23 12:15 ` [PATCH 7/8] Builtin git-show-branch Peter Eriksen
2006-05-23 12:15 ` [PATCH 8/8] Builtin git-diff-files, git-diff-index, git-diff-stages, and git-diff-tree Peter Eriksen
2006-05-23 12:20 ` Make more commands builtin Peter Eriksen
2006-05-23 12:36 ` Jakub Narebski [this message]
2006-05-23 12:54 ` Peter Eriksen
2006-05-23 13:05 ` Jakub Narebski
2006-05-23 16:32 ` Ryan Anderson
2006-05-23 12:15 Peter Eriksen
2006-05-23 23:48 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2006-05-23 8:31 Peter Eriksen
2006-05-23 8:23 Peter Eriksen
2006-05-23 8:41 ` Junio C Hamano
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='e4uvku$o28$1@sea.gmane.org' \
--to=jnareb@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).