From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Patches for 2.6.33-rc1
Date: Wed, 09 Dec 2009 13:04:31 +0200 [thread overview]
Message-ID: <1260356671.19669.1296.camel@localhost> (raw)
In-Reply-To: <1260355174.13499.8.camel@pc1117.cambridge.arm.com>
On Wed, 2009-12-09 at 10:39 +0000, Catalin Marinas wrote:
> On Wed, 2009-12-09 at 10:20 +0000, Artem Bityutskiy wrote:
> > It is so much helpful when people add proper prefixes to patches, like
> > ARM or something. I wander, do we have a requirement for this somewhere?
> > But please, consider doing this, this makes it easier surfing git-log or
> > gitk info.
>
> It would be useful, indeed, so I haven't seen an official statement from
> Russell on this (and I usually run gitk on specific directories).
>
> Traditionally we used the patch system which was adding a prefix but
> since it cannot cope with a different author from the submitter, I just
> use Git these days (I don't mind either way).
Well, for people like me who did not use the patch system long time
before and did not get accustomed to it, the system is looks very
ancient and sub-standard.
But since I'm not an ARM developer, I do complain about this. If ARM
people find the system good, and the standard lkml-sytle patch exchange
culture does not work for them - fine :)
--
Best Regards,
Artem Bityutskiy (????? ????????)
next prev parent reply other threads:[~2009-12-09 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 10:09 [GIT PULL] Patches for 2.6.33-rc1 Catalin Marinas
2009-12-09 10:20 ` Artem Bityutskiy
2009-12-09 10:39 ` Catalin Marinas
2009-12-09 11:04 ` Artem Bityutskiy [this message]
2009-12-09 11:23 ` Artem Bityutskiy
2009-12-09 12:43 ` Catalin Marinas
2009-12-09 12:49 ` Mark Brown
2009-12-09 13:21 ` Catalin Marinas
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=1260356671.19669.1296.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).