All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Barker" <pbarker@konsulko.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] Drop old presentations from repository
Date: Tue, 24 Nov 2020 09:25:30 +0000	[thread overview]
Message-ID: <CAM9ZRVvg+dijfUxJ1sCDrHnfSCUpTZ8k2hSKx1UZdw-Cd=2u-Q@mail.gmail.com> (raw)
In-Reply-To: <CAP71WjzsEtkxaGprSCc7emQ=aqiNJAWcMzWRMRmQpSxfSc9SYw@mail.gmail.com>

On Tue, 24 Nov 2020 at 07:20, Nicolas Dechesne
<nicolas.dechesne@linaro.org> wrote:
>
> On Mon, Nov 23, 2020 at 9:32 PM Paul Barker <pbarker@konsulko.com> wrote:
> >
> > The `presentations` directory contained two talks which are now over 7
> > years old and are unlikely to be relevant to current users of the
> > project. They don't fit in well with the rest of the contents of this
> > repository and should be dropped. If anyone wants them, they'll still be
> > stored in the git history :)
> >
> > Signed-off-by: Paul Barker <pbarker@konsulko.com>
>
> Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
>
> > ---
> >
> >     I created this patch with the --no-binary argument to git-format-patch to
> >     avoid sending megabytes of redundant data to the list. However that means
> >     the patch doesn't apply as-is. The following steps work for me:
> >
> >         git am 0001-Drop-old-presentations-from-repository.patch
> >         git rm -r presentations
> >         git am --continue
>
> You might want to post your patch in a branch for us to pull from.

Ah yes, that would have been the obvious solution. I was having a dumb day.

RP has already applied this to master-next so I think we're ok now.

-- 
Paul Barker
Konsulko Group

      reply	other threads:[~2020-11-24  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 20:32 [PATCH] Drop old presentations from repository Paul Barker
2020-11-24  7:19 ` [docs] " Nicolas Dechesne
2020-11-24  9:25   ` Paul Barker [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='CAM9ZRVvg+dijfUxJ1sCDrHnfSCUpTZ8k2hSKx1UZdw-Cd=2u-Q@mail.gmail.com' \
    --to=pbarker@konsulko.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=nicolas.dechesne@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.