From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: archer ml <archer@sourceware.org>
Subject: git tip
Date: Thu, 05 Mar 2009 22:10:00 -0000 [thread overview]
Message-ID: <1236291031.28372.44.camel@localhost.localdomain> (raw)
Hi,
Perhaps everyone else knows about this except me, but I thought it would
be useful to share anyway:
To avoid having to type that big remote branch name when you are pushing
to your branch in the archer repo, you can set a default refspec to push
to when you don't specify anything to 'git push'. Just edit .git/config,
and add a line like this to the [remote "origin"] section:
push = <local branch name>:<remote branch name>
In my case this would be:
push = python:archer-tromey-python
So now instead of writing:
% git push origin python:archer-tromey-python
I can just type:
% git push
I don't know yet if you can add multiple push entries in .git/config to
create multiple branch mappings, but perhaps you can.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next reply other threads:[~2009-03-05 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 22:10 Thiago Jung Bauermann [this message]
2009-03-05 22:23 ` Roland McGrath
2009-03-06 22:51 ` Doug Evans
2009-03-08 4:37 ` Thiago Jung Bauermann
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=1236291031.28372.44.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=archer@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).