zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: <zsh-workers@zsh.org>
Subject: Re: PATCH: sshfs user-side automount
Date: Tue, 18 Feb 2020 11:24:58 +0000	[thread overview]
Message-ID: <20200218112458.5599341a@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <1582024239.4529.13.camel@samsung.com>

Peter Stephenson wrote on Tue, 18 Feb 2020 11:10 +0000:
> On Tue, 2020-02-18 at 10:44 +0000, Daniel Shahaf wrote:
> > Peter Stephenson wrote on Mon, 17 Feb 2020 15:45 +0000:  
> > > 
> > > This certainly won't go in until the dust has settled, both on the
> > > release and the proposed change,  
> > Why don't you push it to the 5.9 branch, then?  That's what it's for.  
> 
> As I understand it, the 5.9 branch is for finished changes;
> there won't be any rationalisation when it's rebased into master,
> so there's no more point pushing work in progress there than to
> any other public branch, or have I missed the point?

I think you haven't: the 5.9 branch is for changes that would be
suitable for master if master weren't in soft freeze due to being in
the wake of a major release.

> Thanks for the other notes, I'll feed them into some further
> tweaks.

You're welcome.

Daniel

  reply	other threads:[~2020-02-18 11:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200217154528eucas1p17c3730dd3979ce40eb383d7f6889c5e2@eucas1p1.samsung.com>
2020-02-17 15:45 ` Peter Stephenson
2020-02-18 10:44   ` Daniel Shahaf
2020-02-18 11:10     ` Peter Stephenson
2020-02-18 11:24       ` Daniel Shahaf [this message]
2020-03-16 10:11       ` Peter Stephenson
2020-03-16 18:36         ` Daniel Shahaf
2020-03-17 12:19           ` Peter Stephenson
2020-03-17 14:00             ` Daniel Shahaf
2020-03-17 14:08               ` Peter Stephenson

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=20200218112458.5599341a@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).