linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] misc: add 2038 timestamp support
Date: Thu, 18 Apr 2024 23:46:08 -0400	[thread overview]
Message-ID: <20240419034608.GC3374174@mit.edu> (raw)
In-Reply-To: <E44A9FB1-280E-4EB7-9092-856E200EE500@dilger.ca>

On Thu, Apr 18, 2024 at 04:04:10PM -0600, Andreas Dilger wrote:
> 
> I've never used Github actions for this. If I fork tytso/e2fsprogs and
> push to adilger/e2fsprogs, are those actions automated already with a
> config file inside the repo, or do I need to set that up myself?

Github actions should be enabled by default (although enterprise
accounts can have the default changed or prohibited by the enterprise
administrator's policy).

The config file is checked into the repo at .github/workflows/ci.yml
so if you fork the repo, you should get it.

> PS: the kernel.org repo looks like it has not been updated in 4 months,
> despite emails that you have landed patches. I was pulling from there
> and didn't notice until now that you have been pushing only to github.

I don't update kernel.org as frequently as github, but I suspect the
issue is that you were probably looking at the master branch, and the
updates were going on the next branch.  When I'm processing a large
number of patches, sometimes I don't update master until I'm really
confident everything is in great shape to update the master branch to
point at next.

It's just that April has been super crazy busy me for me, so master
lagged next by a few weeks.

Cheers,

						- Ted

      reply	other threads:[~2024-04-19  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  5:40 [PATCH] misc: add 2038 timestamp support Andreas Dilger
2024-04-01 21:29 ` Andreas Dilger
2024-04-17  2:03 ` Theodore Ts'o
2024-04-18 14:36 ` Theodore Ts'o
2024-04-18 18:32   ` Theodore Ts'o
2024-04-18 22:04   ` Andreas Dilger
2024-04-19  3:46     ` Theodore Ts'o [this message]

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=20240419034608.GC3374174@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).