unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: martin f krafft <madduck@madduck.net>
To: David Bremner <bremner@unb.ca>
Cc: notmuch@notmuchmail.org
Subject: Re: patchwork test instance
Date: Thu, 11 Feb 2010 11:00:38 +1300	[thread overview]
Message-ID: <20100210220038.GG16186@lapse.rw.madduck.net> (raw)
In-Reply-To: <87tytpjx0x.fsf@rocinante.cs.unb.ca>

also sprach David Bremner <bremner@unb.ca> [2010.02.10.2149 +1300]:
> I'm not sure what merging patches means here; some kind of squash
> operation?  Anyway it seemed to me that every every patch series
> that I looked at was broken into individual patches. Maybe I am
> just unlucky, or does patchwork really not understand the concept
> of series of patches in a thread?

I don't think it does, this is what bundles are for, but these need
to be created manually at the moment. Patch series are pretty easy
to detect, so maybe the bundle could be automatically generated.

http://lists.ozlabs.org/pipermail/patchwork/2010-February/000226.html

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
because light travels faster than sound,
some people appear to be intelligent,
until you hear them speak.
 
spamtraps: madduck.bogus@madduck.net

  reply	other threads:[~2010-02-10 22:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 14:00 Git feature branch Sebastian Spaeth
2010-01-20 20:00 ` micah anderson
2010-01-22  8:09   ` Sebastian Spaeth
2010-01-22  8:50     ` Sebastian Spaeth
2010-01-22 21:10       ` Carl Worth
2010-01-25 21:32         ` martin f krafft
2010-01-26  0:46           ` sebastian
2010-01-26 22:24             ` micah anderson
2010-01-27 19:17               ` Ben Gamari
2010-02-24 18:58                 ` Carl Worth
2010-01-27 19:19               ` Jameson Rollins
2010-01-27 19:41               ` martin f krafft
2010-01-28  7:05                 ` James Rowe
2010-02-01 22:31                   ` patchwork test instance (was: Git feature branch) martin f krafft
2010-02-02 11:38                     ` Marten Veldthuis
2010-02-10  3:25                     ` patchwork test instance martin f krafft
2010-02-10  8:49                       ` David Bremner
2010-02-10 22:00                         ` martin f krafft [this message]
2010-02-10  9:25                       ` Sebastian Spaeth
2010-02-10 22:22                         ` martin f krafft
2010-02-24 19:10                           ` Carl Worth
2010-02-24 20:39                             ` martin f krafft
2010-02-24 19:08                         ` Carl Worth
2010-02-25  8:06                           ` martin f krafft
2010-02-04  3:05           ` Git feature branch Carl Worth
2010-02-04  3:50             ` martin f krafft
2010-02-05  3:36               ` patchwork now auto-updates patches from Git (was: Git feature branch) martin f krafft
2010-02-04  3:58             ` Git feature branch Jameson Rollins
2010-02-24 19:13               ` Carl Worth

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100210220038.GG16186@lapse.rw.madduck.net \
    --to=madduck@madduck.net \
    --cc=bremner@unb.ca \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).