From: Mark Burton <markb@ordern.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-gui: Teach start_push_anywhere_action{} to notice when remote is a mirror.
Date: Tue, 2 Dec 2008 16:31:04 +0000 [thread overview]
Message-ID: <20081202163104.29306f22@crow> (raw)
In-Reply-To: <20081202153007.GJ23984@spearce.org>
Hi Shawn,
> Yea, it is a chunk of work. I thought about trying to do it myself
> right now, but realized I won't be able to do it in 15 minutes and
> gave up. :-)
Well, when you/someone looks at updating the push dialog you could
consider adding another checkbox that disables the refspec so that the
push uses whatever default refspec has been configured. I think that would
be a useful addition.
Cheers,
Mark
prev parent reply other threads:[~2008-12-02 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:15 [PATCH] git-gui: Teach start_push_anywhere_action{} to notice when remote is a mirror Mark Burton
2008-12-02 15:30 ` Shawn O. Pearce
2008-12-02 16:31 ` Mark Burton [this message]
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=20081202163104.29306f22@crow \
--to=markb@ordern.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).