From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Docs for git-checkout-script.
Date: Wed, 07 Sep 2005 17:34:27 -0400 [thread overview]
Message-ID: <431F5CE3.4000608@gmail.com> (raw)
In-Reply-To: <7v3bog6082.fsf@assigned-by-dhcp.cox.net>
Actually, I'm cherry-picking the easier ones in an effort to reduce my
stress about my impending move to the LA area.
Hopefully you did git-diff-script, git-format-patch-script, and
git-rev-parse which don't look easy to document.
Junio C Hamano wrote:
> You read my mind. I just finished documenting some other
> commands and was about to push things out.
next prev parent reply other threads:[~2005-09-07 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 21:17 [PATCH] Docs for git-checkout-script A Large Angry SCM
2005-09-07 21:23 ` Junio C Hamano
2005-09-07 21:34 ` A Large Angry SCM [this message]
2005-09-07 22:26 ` 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=431F5CE3.4000608@gmail.com \
--to=gitzilla@gmail.com \
--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).