public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: patchwork.ipfire.org didn't get last two patches
Date: Sat, 04 Aug 2018 13:57:42 +0200	[thread overview]
Message-ID: <37b355162c8a885628763a16e178989c524d7ed9.camel@ipfire.org> (raw)
In-Reply-To: <1089299d-802f-ca47-43e6-bbf897f55aa3@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

Hi Matthias,
did send also two patches but the last entry in Patchwork is the Squid
update from 2018-07-17 . So yes i can confirm it here too.

Greetings,

Erik
 
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
> Hi,
> 
> my last two commits, sent with "git send-email ..." (and pushed)
> don't
> show up on patchwork.ipfire.org.
> 
> Sending to development list is OK, but nothing can be seen on
> patchwork.
> 
> Can anyone confirm?
> 
> Best,
> Matthias

  reply	other threads:[~2018-08-04 11:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04  8:00 Matthias Fischer
2018-08-04 11:57 ` ummeegge [this message]
2018-08-04 13:54   ` Michael Tremer
2018-08-04 16:04     ` Matthias Fischer
2018-08-04 17:58       ` Michael Tremer
2018-08-04 19:35         ` Matthias Fischer
2018-08-04 19:39     ` git.ipfire =>very slow loading (was: Re: patchwork.ipfire.org didn't get last two patches) Matthias Fischer
2018-08-05 10:24       ` Michael Tremer
2018-08-11 19:45         ` git.ipfire =>very slow loading Matthias Fischer
2018-08-12  7:10           ` Peter Müller
2018-08-15  8:34             ` Michael Tremer

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=37b355162c8a885628763a16e178989c524d7ed9.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.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