All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Patches pulled, linux-gfs2.git for-next rebased
Date: Thu, 6 Jul 2017 08:05:48 -0400 (EDT)	[thread overview]
Message-ID: <809534946.28914565.1499342748378.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1625048138.28914561.1499342738758.JavaMail.zimbra@redhat.com>

Hi,

Linus has pulled the latest set of patches from the for-next branch of
the linux-gfs2.git tree, so I rebased the tree from Linus's master.
So the current tree is back to having no unmerged GFS2 patches.

Regards,

Bob Peterson
Red Hat File Systems



       reply	other threads:[~2017-07-06 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1625048138.28914561.1499342738758.JavaMail.zimbra@redhat.com>
2017-07-06 12:05 ` Bob Peterson [this message]
     [not found] <1244612705.11367413.1552320572843.JavaMail.zimbra@redhat.com>
2019-03-11 16:09 ` [Cluster-devel] GFS2: Patches pulled, linux-gfs2.git for-next rebased Bob Peterson
     [not found] <695428944.58981868.1546454049944.JavaMail.zimbra@redhat.com>
2019-01-02 18:34 ` Bob Peterson
     [not found] <1739630125.41715739.1528723577398.JavaMail.zimbra@redhat.com>
2018-06-11 13:26 ` Bob Peterson
     [not found] <23895149.16372982.1522937850510.JavaMail.zimbra@redhat.com>
2018-04-05 14:20 ` Bob Peterson
     [not found] <1273604153.5698348.1517429149503.JavaMail.zimbra@redhat.com>
2018-01-31 20:06 ` Bob Peterson
2018-01-31 21:49   ` Andrew Price
     [not found] <1869966235.32176668.1510756115474.JavaMail.zimbra@redhat.com>
2017-11-15 14:28 ` Bob Peterson
     [not found] <1861372219.4841245.1494077880646.JavaMail.zimbra@redhat.com>
2017-05-06 13:40 ` Bob Peterson

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=809534946.28914565.1499342748378.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.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 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.