From: Jonathan Nieder <jrnieder@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Better advice on using topic branches for kernel development
Date: Thu, 21 Oct 2010 11:32:08 -0500 [thread overview]
Message-ID: <20101021163208.GC3732@burratino> (raw)
In-Reply-To: <4cc06a8128436b591e@agluck-desktop.sc.intel.com>
Hi Tony,
Luck, Tony wrote:
> Maybe they do this because they read it in the Git user-manual.
>
> Fix the manual to give them better guidance.
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
[...]
> Originally posted on October 1st ... no comments received.
No comments received, but applied to "maint". Sorry for the
confusion.
Occasionally there has been discussion of automating notification
that a patch was applied. Maybe someone on the git@ list might
consider it worth trying (or maybe not).
Thanks.
next prev parent reply other threads:[~2010-10-21 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 16:29 [PATCH] Better advice on using topic branches for kernel development Luck, Tony
2010-10-21 16:32 ` Jonathan Nieder [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-01 18:57 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=20101021163208.GC3732@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).