On Tue, Aug 6, 2019 at 9:32 AM Micah Morton wrote:
>
> Unfortunately I didn't have the mental model quite right of what
> happens during the pull request. I was thinking along the lines of my
> commits being cherry picked onto your tree, rather than how it
> actually happens with git merge where
On Mon, Aug 5, 2019 at 12:27 PM Konstantin Ryabitsev
wrote:
>
> On Mon, Aug 05, 2019 at 12:17:49PM -0700, Linus Torvalds wrote:
> >> However, I suspect that getting message-ids for all your pull
> >> requests
> >> would significantly complicate your workflow.
> >
> >Yeah, that would be a
On Mon, Aug 05, 2019 at 12:17:49PM -0700, Linus Torvalds wrote:
However, I suspect that getting message-ids for all your pull
requests
would significantly complicate your workflow.
Yeah, that would be a noticeable annoyance. If I were to process pull
requests the way I used to process emailed
On Mon, Aug 5, 2019 at 12:11 PM Konstantin Ryabitsev
wrote:
>
> However, I suspect that getting message-ids for all your pull requests
> would significantly complicate your workflow.
Yeah, that would be a noticeable annoyance. If I were to process pull
requests the way I used to process emailed
On Mon, Aug 05, 2019 at 11:20:59AM -0700, Linus Torvalds wrote:
I don't know if it's worth changing the pr-tracker-bot rules. I *do*
think that the whole unquoted
for you to fetch changes up to [hex string]
is by far the strongest single signal for a pull request, but it's not
clear that
On Mon, Aug 5, 2019 at 7:28 AM Konstantin Ryabitsev
wrote:
>
> On Sun, Aug 04, 2019 at 10:47:54AM -0700, Linus Torvalds wrote:
> > - maybe pr-tracker-bot ignores follow-up emails with "Re:" in the
> > subject?
>
> Yes, this is the culprit. Here are the matching regexes:
>
>
On Sun, Aug 04, 2019 at 10:47:54AM -0700, Linus Torvalds wrote:
- maybe pr-tracker-bot ignores follow-up emails with "Re:" in the
subject?
Yes, this is the culprit. Here are the matching regexes:
On Thu, Aug 1, 2019 at 11:11 AM Micah Morton wrote:
>
> The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
>
> Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
>
> are available in the Git repository at:
>
> https://github.com/micah-morton/linux.git
>
On Thu, Aug 1, 2019 at 11:11 AM Micah Morton wrote:
>
> Add entry in MAINTAINERS file for SafeSetID LSM.
So I've pulled this now.
However, I have to say that I'm now very nervous about future pulls,
simply because the last one had basically everything that can be wrong
be wrong.
Random
Sorry about that. To fix it I did a "git reset hard" to before any of
those commits by Jann Horn, then fast-forwarded to the v5.3-rc2 tag
and force pushed that to my origin/master then pushed a new branch up
with my MAINTAINERS file changes. Hopefully this is a valid fix.
--
The following changes
On Wed, Jul 31, 2019 at 2:30 PM Micah Morton wrote:
>
> You mentioned a couple weeks ago it would be good if I added myself to
> the MAINTAINERS file for the SafeSetID LSM. Here's the pull request
> for v5.3.
There's a lot more than the maintainer ID in there. You've rebased old
patches that I
Hi Linus,
You mentioned a couple weeks ago it would be good if I added myself to
the MAINTAINERS file for the SafeSetID LSM. Here's the pull request
for v5.3.
Thanks!
--
The following changes since commit 179757afbef5f64b9bd25e6161f72fc1a52a8f2e:
Merge commit 'v5.3-rc2^0' (2019-07-31 13:45:16
12 matches
Mail list logo
