From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Git workflow overview
Date: Sat, 29 Mar 2008 12:31:36 +0100 [thread overview]
Message-ID: <87ej9t4vhj.fsf@gnu.org> (raw)
In-Reply-To: 871w5uqreg.fsf@ossau.uklinux.net
Hi Neil,
Neil Jerram <neil@ossau.uklinux.net> writes:
> Now, what am I doing wrong here? I've created a load of new
> .gitignore files, and tried to push them to Savannah's master and
> 1.8.x branches. The push to master looks good, but the push to 1.8.x
> does nothing:
I had similar troubles when using a local branch name different from
`branch_release-1-8': somehow, Git doesn't memorize the branch name
mapping for push.
The easy fix, of course, it to name local branches like remote
branches---which is what I did, because I was lazy.
The "real" fix involves `.git/config' magic (or `.git/remotes', or
`.git/branches'), to tell Git about the name of the remote branch where
it should push. git-push(1) mentions several possibilities, but I
haven't tried them.
Alternatively, "git-push origin 1.8.x:branch_release-1-8" should work,
but I haven't tried either.
Maybe you could tell us which trick works best? :-)
BTW, regarding `.gitignore', it's possible to use glob patterns, like
"*.x", "*.doc", "*.lo", etc.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-03-29 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 21:29 Git workflow overview Ludovic Courtès
2008-03-28 4:36 ` Han-Wen Nienhuys
2008-03-28 16:38 ` Ludovic Courtès
2008-03-29 0:56 ` Neil Jerram
2008-03-29 11:31 ` Ludovic Courtès [this message]
2008-03-29 17:44 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ej9t4vhj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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).