From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: patches added to test tree
Date: Fri, 16 Sep 2005 14:54:39 +0000 [thread overview]
Message-ID: <200509160854.39454.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200509160423.j8G4NCub007777@agluck-lia64.sc.intel.com>
On Thursday 15 September 2005 10:26 pm, Luck, Tony wrote:
> >To: linux-ia64@vger.kernel.org
> >Subject: patches added to test tree
> >
> >The following patches have been added to the test tree:
> >
> ...
>
> Bjorn suggested that it would be helpful if I announced
> when things have gone into my trees. Let me know if I should
> change the format, or add more information to these announce
> e-mails.
This is helpful, thanks. It occurred to me last night (before
I saw your "patches added" mail) that the low-tech solution of
a response to the email containing the original patch has the
advantage of meaningful subject lines and being close in the
email archives. And it gives a nice place to comment on tweaks
that you might have to make to resolve conflicts.
But I know that's a bit more work and might not fit your
workflow of moving patches between trees, so it's just a
possibility.
next prev parent reply other threads:[~2005-09-16 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 4:23 patches added to test tree tony.luck
2005-09-16 4:26 ` Luck, Tony
2005-09-16 4:48 ` Ian Wienand
2005-09-16 14:54 ` Bjorn Helgaas [this message]
2005-09-20 19:14 ` tony.luck
2005-09-23 23:29 ` Luck, Tony
2005-09-26 18:22 ` David Mosberger-Tang
2005-09-26 23:48 ` Ian Wienand
2005-09-27 1:06 ` David Mosberger-Tang
2005-10-05 23:43 ` Luck, Tony
2005-10-26 17:38 ` Luck, Tony
2005-11-01 1:03 ` Luck, Tony
2005-11-07 22:09 ` Luck, Tony
2005-11-09 0:19 ` Luck, Tony
2005-11-10 23:28 ` Luck, Tony
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=200509160854.39454.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@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