From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, linux-cachefs@redhat.com
Subject: Re: [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache
Date: Fri, 21 Apr 2006 11:56:45 -0400 [thread overview]
Message-ID: <444900BD.1030903@RedHat.com> (raw)
In-Reply-To: <1145634832.8150.22.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> 'git fetch' or 'git pull'? You almost always want to do the latter,
> since the former doesn't attempt to merge the changes into your
> repository.
ah... I did the former... thanks...
steved.
next prev parent reply other threads:[~2006-04-21 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 15:14 [PATCH][RFC] NFS: Adding hooks to enable the use of FS-Cache Steve Dickson
2006-04-21 15:31 ` Trond Myklebust
2006-04-21 15:42 ` Steve Dickson
2006-04-21 15:53 ` Trond Myklebust
2006-04-21 15:56 ` Steve Dickson [this message]
2006-04-21 15:44 ` [Linux-cachefs] " David Howells
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 15:47 Steve Dickson
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=444900BD.1030903@RedHat.com \
--to=steved@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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).