From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: bk pull on NEW ia64 linux tree
Date: Thu, 29 Jul 2004 17:49:40 +0000 [thread overview]
Message-ID: <200407291049.40832.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <41093338.6050603@intel.com>
On Thursday, July 29, 2004 10:26 am, Tony Luck wrote:
> <aegl@agluck-lia64.sc.intel.com> (04/07/28 1.1855)
> # Signed-off-by: Gordon Jin <gordon.jin@intel.com>
> # Signed-off-by: Arun Sharma <arun.sharma@intel.com>
> # Signed-off-by: Tony Luck <tony.luck@intel.com>
This changeset isn't very descriptive. :) You have to both comment the
individual files *and* the whole changeset when doing a checkin, since that
makes the changeset overview (e.g.
http://lia64.bkbits.net:8080/to-base-2.6/ChangeSet%40-3d?nav=index.html) much
more useful.
Thanks,
Jesse
next prev parent reply other threads:[~2004-07-29 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 17:26 bk pull on NEW ia64 linux tree Tony Luck
2004-07-29 17:49 ` Jesse Barnes [this message]
2004-07-29 17:59 ` 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=200407291049.40832.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.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