public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: XFS Master Branch Rebase
Date: Tue, 27 Jul 2010 11:16:06 -0500	[thread overview]
Message-ID: <1280247366.2002.111.camel@doink> (raw)

Some recent commits have resulted in changes to
the XFS master branch that result in non-trivial
merges, which are not something we want to have in
our git history.  (I didn't realize this when I
pushed my last set of updates out, unfortunately.)

To remedy this, I'm have re-based the XFS master
branch on oss.sgi.com against v2.6.35-rc6.

This is important to you if you currently have
a git tree tracking this branch in the XFS
repository, because doing a typical "git pull"
won't produce in the desired result.

Instead, you should issue a command like one
of the following to update your private branch.

If your branch "xfs-master" tracks branch "master"
at git://oss.sgi.com/xfs/xfs.git, and you now
have "xfs-master" checked out, you can do this:
    git pull --rebase -f

If you have a different branch checked out, you
can do this instead to force the re-based commits
to land in your "xfs-master" branch:
    git pull git://oss.sgi.com/xfs/xfs.git +master:xfs-master

Another way to get a current branch to line up with
the newly re-based XFS master branch is  to reset
it to an earlier commit (such as v2.6.35-rc5) and
follow that with a "git pull" command:
    git reset --hard v2.6.35-rc5
    git pull git://oss.sgi.com/xfs/xfs.git master

					-Alex

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2010-07-27 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 16:16 Alex Elder [this message]
2010-07-27 23:27 ` XFS Master Branch Rebase Dave Chinner
2010-07-28  8:44   ` Christoph Hellwig
2010-07-28 11:09     ` Dave Chinner
2010-07-28 11:19       ` Christoph Hellwig
2010-07-28 16:18       ` Alex Elder
2010-07-28 16:43   ` Alex Elder

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=1280247366.2002.111.camel@doink \
    --to=aelder@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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