From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2011, #02; Sat, 11)
Date: Sun, 12 Jun 2011 17:44:39 +0530 [thread overview]
Message-ID: <BANLkTinHCX0vmAdk+su-_Y0th9vLQ6qsnw@mail.gmail.com> (raw)
In-Reply-To: <7voc23sfxd.fsf@alter.siamese.dyndns.org>
Hi Junio,
Have you seen my "libify reset" patch [1]? I thought it was an easy candidate.
Thanks.
-- Ram
[1]: http://mid.gmane.org/1307772613-30775-1-git-send-email-artagnon@gmail.com
next prev parent reply other threads:[~2011-06-12 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 6:49 What's cooking in git.git (Jun 2011, #02; Sat, 11) Junio C Hamano
2011-06-12 12:14 ` Ramkumar Ramachandra [this message]
2011-06-13 0:17 ` "libify part of reset" mini-series (Re: What's cooking in git.git (Jun 2011, #02; Sat, 11)) Jonathan Nieder
2011-06-13 13:16 ` What's cooking in git.git (Jun 2011, #02; Sat, 11) Junio C Hamano
2011-06-12 16:18 ` Sverre Rabbelier
2011-06-13 15:25 ` Junio C Hamano
2011-06-13 16:07 ` Sverre Rabbelier
2011-06-14 4:27 ` Elijah Newren
2011-06-16 21:05 ` Jeff King
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=BANLkTinHCX0vmAdk+su-_Y0th9vLQ6qsnw@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).