From: Santi <sbejar@gmail.com>
To: git <git@vger.kernel.org>
Subject: Re: [PATCH] Fetch: get the remote branches to merge from the branch properties.
Date: Sat, 23 Sep 2006 02:47:01 +0200 [thread overview]
Message-ID: <8aa486160609221747s7859c6b6jb7164abe72b74e80@mail.gmail.com> (raw)
In-Reply-To: <874puza2qq.fsf@gmail.com>
2006/9/23, Santi Béjar <sbejar@gmail.com>:
> If in branch "foo" and this in config:
>
> [branch "foo"]
> merge=bar
>
> "git fetch": fetch from the default repository and program the "bar"
> branch to be merged with pull.
>
> Signed-off-by: Santi Béjar <sbejar@gmail.com>
Just to comments (it's late here):
.- the branch.foo.merge must be the same as specified in the remotes/$remote.
.- I've already found a bug (it's late and I need to sleep, sorry).
This must only be done for the default repository (origin, or in
branch.foo.remote).
Santi
prev parent reply other threads:[~2006-09-23 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 23:41 [PATCH] Fetch: get the remote branches to merge from the branch properties Santi Béjar
2006-09-23 0:45 ` Junio C Hamano
2006-09-23 0:53 ` Santi
2006-09-23 0:47 ` Santi [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=8aa486160609221747s7859c6b6jb7164abe72b74e80@mail.gmail.com \
--to=sbejar@gmail.com \
--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).