From: Finn Arne Gangstad <finnag@pvv.org>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/7] git push: New options --matching and --current
Date: Tue, 10 Mar 2009 09:54:33 +0100 [thread overview]
Message-ID: <20090310085433.GB11448@pvv.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0903091938150.19665@iabervon.org>
On Mon, Mar 09, 2009 at 07:49:47PM -0400, Daniel Barkalow wrote:
> On Mon, 9 Mar 2009, Finn Arne Gangstad wrote:
>
> > diff --git a/transport.h b/transport.h
> > index 6bbc1a8..b897d0c 100644
> > --- a/transport.h
> > +++ b/transport.h
> > @@ -34,6 +34,15 @@ struct transport {
> > #define TRANSPORT_PUSH_DRY_RUN 4
> > #define TRANSPORT_PUSH_MIRROR 8
> > #define TRANSPORT_PUSH_VERBOSE 16
> > +#define TRANSPORT_PUSH_MATCHING 32
> > +#define TRANSPORT_PUSH_CURRENT 64
> > +/**
> > + * All push flags that imply a certain set of refspecs to be pushed must
> > + * be combined into TRANSPORT_PUSH_MODE_MASK
> > + **/
> > +#define TRANSPORT_PUSH_MODE_MASK \
> > + (TRANSPORT_PUSH_ALL | TRANSPORT_PUSH_MIRROR | TRANSPORT_PUSH_MATCHING | \
> > + TRANSPORT_PUSH_CURRENT)
>
> It's kind of odd that you define these flags as TRANSPORT_PUSH_*, but
> implement them before entering transport_push(). I'm not sure which is
> right, but the combination is odd. I think just taking care of it in
> builtin-push with flags or options defined there is probably the best
> thing, currently.
True, this was not very beautiful. I will make something better.
- Finn Arne
next prev parent reply other threads:[~2009-03-10 8:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 22:35 [RFC/PATCH] git push usability improvements and default change Finn Arne Gangstad
2009-03-09 22:35 ` [PATCH 1/7] remote: Make "-" an alias for the current remote Finn Arne Gangstad
2009-03-09 22:35 ` [PATCH 2/7] New config option push.default Finn Arne Gangstad
2009-03-09 22:35 ` [PATCH 3/7] git push: New options --matching and --current Finn Arne Gangstad
2009-03-09 23:49 ` Daniel Barkalow
2009-03-10 8:54 ` Finn Arne Gangstad [this message]
2009-03-09 22:35 ` [PATCH 4/7] git push: Display warning on unconfigured default push Finn Arne Gangstad
2009-03-10 0:25 ` Jay Soffian
2009-03-09 22:35 ` [PATCH 5/7] git push: Document that "nothing" is the future push default Finn Arne Gangstad
2009-03-09 22:35 ` [PATCH 6/7] git push: Change default for "git push" to nothing Finn Arne Gangstad
2009-03-09 22:35 ` [PATCH 7/7] git push: Remove warning for "git push" default change Finn Arne Gangstad
2009-03-09 23:35 ` [RFC/PATCH] git push usability improvements and " Johannes Schindelin
2009-03-10 0:12 ` Junio C Hamano
2009-03-10 8:46 ` Finn Arne Gangstad
2009-03-10 11:01 ` Johannes Schindelin
2009-03-10 11:12 ` Finn Arne Gangstad
2009-03-10 0:07 ` Junio C Hamano
2009-03-10 0:19 ` Junio C Hamano
2009-03-10 10:04 ` Finn Arne Gangstad
2009-03-10 16:20 ` Jay Soffian
2009-03-11 20:35 ` Junio C Hamano
2009-03-12 3:01 ` Nanako Shiraishi
2009-03-12 10:22 ` Finn Arne Gangstad
2009-03-12 10:52 ` Miles Bader
2009-03-12 12:20 ` Finn Arne Gangstad
2009-03-13 8:28 ` Miles Bader
2009-03-13 10:07 ` John Tapsell
2009-03-10 17:52 ` Jeff King
2009-03-10 22:04 ` Finn Arne Gangstad
2009-03-10 22:10 ` Jeff King
2009-03-11 1:57 ` Jay Soffian
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=20090310085433.GB11448@pvv.org \
--to=finnag@pvv.org \
--cc=barkalow@iabervon.org \
--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 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).