From: Alan Cox <email@example.com> To: Christoph Hellwig <firstname.lastname@example.org> Cc: Marcelo Tosatti <email@example.com>, lkml <firstname.lastname@example.org>, email@example.com, Christoph Hellwig <firstname.lastname@example.org>, Jan Kara <email@example.com> Subject: Re: -- END OF BLOCK -- (fwd) Date: 14 Jul 2003 16:03:36 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <20030714143613.GA9349@lst.de> On Llu, 2003-07-14 at 15:36, Christoph Hellwig wrote: > Now it seems Alan merged other stuff without telling the person > who send him the original patch, thus -ac seems to have code the > XFS tree and -aa don't have. Yes I merged the vendor fixes that stopped it hanging machines. I was suprised you didn't work from that base since that had extensive vendor tree testing and while it had some uglies which you cleaned up in the other stuff it would have been a saner base point
next prev parent reply other threads:[~2003-07-14 14:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <Pine.LNX.4.55L.email@example.com> 2003-07-14 14:36 ` Christoph Hellwig 2003-07-14 15:03 ` Alan Cox [this message] 2003-07-14 17:12 ` Marcelo Tosatti
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: -- END OF BLOCK -- (fwd)' \ /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
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).