All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-merge-subordinate
Date: Wed, 25 Oct 2006 18:11:05 +0200	[thread overview]
Message-ID: <eho29l$1td$1@sea.gmane.org> (raw)
In-Reply-To: 20061025155009.GD5591@parisc-linux.org

Matthew Wilcox wrote:

> Linus doesn't like seeing unnecessary merges in his tree.  I'm not a huge
> fan of them either.  Wouldn't it be nice if we had a merge method that
> did a merge without creating a merge?  I call it git-merge-subordinate
> (since my tree is subordinate to the tree I'm pulling from).  I suppose
> you could call it 'slave' if you want to be more pithy.  Anyway, this
> is a first attempt, and it's totally cargo-cult programming; I make no
> claim that I understand what I'm doing.  But it does seem to work.

Hmmm... the --squash option to git-merge/git-pull isn't enough?

--squash::
        Produce the working tree and index state as if a real
        merge happened, but do not actually make a commit or
        move the `HEAD`, nor record `$GIT_DIR/MERGE_HEAD` to
        cause the next `git commit` command to create a merge
        commit.  This allows you to create a single commit on
        top of the current branch whose effect is the same as
        merging another branch (or more in case of an octopus).


-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git


  reply	other threads:[~2006-10-25 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 15:50 git-merge-subordinate Matthew Wilcox
2006-10-25 16:11 ` Jakub Narebski [this message]
2006-10-25 16:19   ` git-merge-subordinate Johannes Schindelin
2006-10-25 16:27     ` git-merge-subordinate Shawn Pearce

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='eho29l$1td$1@sea.gmane.org' \
    --to=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.