From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] built-in tar-tree and remote tar-tree
Date: Thu, 18 May 2006 22:50:48 -0700 [thread overview]
Message-ID: <7v7j4ik1fr.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vodxulnqx.fsf_-_@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Thu, 18 May 2006 20:03:34 -0700")
Sorry for sending a crapoid that does not even compile. I ran
format-patch while on a wrong branch.
Tonight's "pu" will have a fixed up one for people who are
interested to play with.
next prev parent reply other threads:[~2006-05-19 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 19:21 Feature wish: Cloning without history Sven Ekman
2006-05-18 19:35 ` Jakub Narebski
2006-05-19 3:03 ` [PATCH] built-in tar-tree and remote tar-tree Junio C Hamano
2006-05-19 5:50 ` Junio C Hamano [this message]
2006-05-19 21:43 ` Sven Ekman
2006-05-19 21:56 ` Jakub Narebski
2006-05-19 22:56 ` 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=7v7j4ik1fr.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 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.