From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/7] Let's get that @{push}!
Date: Thu, 23 May 2013 20:42:43 +0530 [thread overview]
Message-ID: <1369321970-7759-1-git-send-email-artagnon@gmail.com> (raw)
[7/7] is the meat. Sorry it's in such a messy state: I was having a
field day tracing what push is actually doing. Anyway, I wanted to
send out the series now to get early feedback.
In other news: why on earth is push doing _so_ much processing before
pushing? Is it written very badly, or am I missing something?
Thanks.
(based on rr/die-on-missing-upstream)
Ramkumar Ramachandra (7):
sha1_name: abstract upstream_mark() logic
sha1_name: factor out die_no_upstream()
sha1_name: remove upstream_mark()
remote: expose parse_push_refspec()
remote: expose get_ref_match()
sha1_name: prepare to introduce AT_KIND_PUSH
sha1_name: implement finding @{push}
remote.c | 4 +--
remote.h | 4 +++
sha1_name.c | 111 ++++++++++++++++++++++++++++++++++++++++++++----------------
3 files changed, 88 insertions(+), 31 deletions(-)
--
1.8.3.rc3.17.gd95ec6c.dirty
next reply other threads:[~2013-05-23 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:12 Ramkumar Ramachandra [this message]
2013-05-23 15:12 ` [PATCH 1/7] sha1_name: abstract upstream_mark() logic Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 2/7] sha1_name: factor out die_no_upstream() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 3/7] sha1_name: remove upstream_mark() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 4/7] remote: expose parse_push_refspec() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 5/7] remote: expose get_ref_match() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 6/7] sha1_name: prepare to introduce AT_KIND_PUSH Ramkumar Ramachandra
2013-05-24 13:22 ` Felipe Contreras
2013-05-24 13:27 ` Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 7/7] sha1_name: implement finding @{push} Ramkumar Ramachandra
2013-05-24 16:09 ` Duy Nguyen
2013-05-24 16:15 ` Ramkumar Ramachandra
2013-05-24 16:21 ` Duy Nguyen
2013-05-24 16:29 ` Ramkumar Ramachandra
2013-05-24 18:01 ` Junio C Hamano
2013-05-24 18:21 ` Ramkumar Ramachandra
2013-05-24 19:12 ` 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=1369321970-7759-1-git-send-email-artagnon@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).