git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ryan Leigh" <ryanl.pi@gmail.com>
To: git@vger.kernel.org
Subject: Push merges?
Date: Wed, 26 Mar 2008 14:52:06 -0700	[thread overview]
Message-ID: <ba5eca00803261452r4b5a7b6bi600c30e79b945477@mail.gmail.com> (raw)

Hello all,

I've been getting to know git and I've stumbled across a "problem" and
I haven't yet been able to find a solution. For example, say I have a
branch "base" and two branches of that "foo" and "bar". I make some
change in "base", commit it, and now I would like to have it in both
"foo" and "bar". Is there a command that rather than get another
branch and merge with the current branch will instead take the current
branch and apply a merge on other branches? I've done google searches
and looking through documentation and tutorials and I can't seem to
find an answer one way or another. I wanted to make sure that before I
go write some script to handle it that what I am looking for isn't
already a feature.

Thank you,
Ryan

             reply	other threads:[~2008-03-26 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-26 21:52 Ryan Leigh [this message]
2008-03-27  3:09 ` Push merges? Jeff King

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=ba5eca00803261452r4b5a7b6bi600c30e79b945477@mail.gmail.com \
    --to=ryanl.pi@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).