From: Chandan Babu R <chandanbabu@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: akiyks@gmail.com, cmaiolino@redhat.com, corbet@lwn.net,
dan.carpenter@linaro.org, dchinner@redhat.com, djwong@kernel.org,
hch@lst.de, hsiangkao@linux.alibaba.com, hughd@google.com,
kch@nvidia.com, kent.overstreet@linux.dev, leo.lilong@huawei.com,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
longman@redhat.com, mchehab@kernel.org, peterz@infradead.org,
sfr@canb.auug.org.au, sshegde@linux.ibm.com, willy@infradead.org
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 75bcffbb9e75
Date: Wed, 13 Mar 2024 12:23:17 +0530 [thread overview]
Message-ID: <87o7bihb66.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <ZepcRgdO39xIrXG2@dread.disaster.area>
On Fri, Mar 08, 2024 at 11:31:02 AM +1100, Dave Chinner wrote:
> On Thu, Mar 07, 2024 at 03:16:56PM +0530, Chandan Babu R wrote:
> Hi Chandan,
>
> I'm finding it difficult to determine what has changed from one
> for-next update to the next because there's only a handful of new
> commits being added to this list.
>
> In this case, I think there's only 1 new commit in this update:
>
>> [75bcffbb9e75] xfs: shrink failure needs to hold AGI buffer
>
> And I only found that out when rebasing my local tree and that patch
> did not apply.
>
> When I was doing these for-next tree updates, I tried to only send
> out the list of commits that changed since the last for-next tree
> update rather than the whole lot since the base kernel it was
> started from. That made it easy for everyone to see what I'd just
> committed, as opposed to trying to find whether their outstanding
> patches were in a big list already committed patches...
>
> Up to you, but I'm bringing it up because I am finding it difficult
> to track when one of my patches has been committed to for-next right
> now...
>
You are right. I didn't realize this problem. I will limit for-next
announcements to include only new patches that were added/removed to/from the
existing pile.
--
Chandan
next prev parent reply other threads:[~2024-03-13 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 9:46 [ANNOUNCE] xfs-linux: for-next updated to 75bcffbb9e75 Chandan Babu R
2024-03-08 0:31 ` Dave Chinner
2024-03-13 6:53 ` Chandan Babu R [this message]
2024-03-15 2:36 ` Darrick J. Wong
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=87o7bihb66.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=akiyks@gmail.com \
--cc=cmaiolino@redhat.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@linaro.org \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=hsiangkao@linux.alibaba.com \
--cc=hughd@google.com \
--cc=kch@nvidia.com \
--cc=kent.overstreet@linux.dev \
--cc=leo.lilong@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mchehab@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sshegde@linux.ibm.com \
--cc=willy@infradead.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox