From: Imran M Yousuf <imyousuf@gmail.com>
To: Peter Krefting <peter@softwolves.pp.se>
Cc: git@vger.kernel.org
Subject: Re: Not pushing all branches?
Date: Fri, 13 Mar 2009 14:12:02 +0600 [thread overview]
Message-ID: <7bfdc29a0903130112w17d40473s14a895d518dbf8ae@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0903130846410.17450@perkele.intern.softwolves.pp.se>
On Fri, Mar 13, 2009 at 1:48 PM, Peter Krefting <peter@softwolves.pp.se> wrote:
> Hi!
>
> Doing "git push remote" pushes all my local branches by default. Is there a
> way to set it to *not* do that, and (for this particular remote repository)
> just push the current branch? Or failing that, not allow me to run "git
> push" without specifying a branch?
Just try -
git push remote branch :)
>
> The git-config manual page leads me to believe that I should recofigure
> "remote.<name>.push", but it points me to the "refspec" spec on git-push,
> which is a tad cryptic.
>
> --
> \\// Peter - http://www.softwolves.pp.se/
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: imran@smartitengineering.com
Blog: http://imyousuf-tech.blogs.smartitengineering.com/
Mobile: +880-1711402557
next prev parent reply other threads:[~2009-03-13 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 7:48 Not pushing all branches? Peter Krefting
2009-03-13 8:12 ` Imran M Yousuf [this message]
2009-03-13 9:44 ` Peter Krefting
2009-03-13 10:49 ` Johannes Schindelin
2009-03-13 11:38 ` Finn Arne Gangstad
2009-03-13 8:25 ` John Tapsell
2009-03-13 10:51 ` Johannes Schindelin
2009-03-13 12:37 ` John Tapsell
2009-03-13 13:53 ` Johannes Schindelin
2009-03-13 13:56 ` John Tapsell
2009-03-13 15:48 ` Michael J Gruber
2009-03-13 16:00 ` Johannes Schindelin
2009-03-13 20:02 ` Junio C Hamano
2009-03-14 1:08 ` Miles Bader
2009-03-17 8:24 ` Jeff King
2009-03-13 16:49 ` Jeff King
2009-03-14 1:27 ` [PATCH] git-push.txt: describe how to default to pushing only current branch Chris Johnsen
2009-03-14 19:26 ` Junio C Hamano
2009-03-14 20:34 ` Jeff King
2009-03-14 20:56 ` Jeff King
2009-03-15 2:49 ` Chris Johnsen
2009-03-15 11:30 ` [PATCH] git-push.txt: describe how to default to pushing only Chris Johnsen
2009-03-17 7:46 ` [PATCH] git-push.txt: describe how to default to pushing only current branch Jeff King
2009-03-14 21:25 ` Junio C Hamano
2009-03-14 21:46 ` Jeff King
2009-03-16 4:51 ` Junio C Hamano
2009-03-15 2:32 ` [PATCH v2] " Chris Johnsen
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=7bfdc29a0903130112w17d40473s14a895d518dbf8ae@mail.gmail.com \
--to=imyousuf@gmail.com \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
/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).