All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Pixley <rich.pixley@palm.com>
To: "openembedded-devel@openembedded.org"
	<openembedded-devel@openembedded.org>
Subject: Re: Git Migration Status
Date: Tue, 29 Jul 2008 10:11:00 -0700	[thread overview]
Message-ID: <488F4F24.3050405@palm.com> (raw)
In-Reply-To: <87abg0ej9q.fsf@neumann.lab.ossystems.com.br>

Otavio Salvador wrote:
> Rolf Leggewie <no2spam@nospam.arcornews.de> writes
>> Richard Purdie wrote:
>>     
>>> There is also the issue of commit ID naming. I'm tempted to propose we
>>> use commit IDs with a domain such as userid@developers.openembedded.org.
>>>       
>> I think something under openembedded.org is a good idea for several
>> reasons.  But how about userid@dev.openembedded.org?
>>     
> I disagree. Using real mail address give a real view of who can be
> sponsoring work and using OE.
Seems to me the point is to have commit id's which encourage and support 
responsibility.  Since we know each other primarily by email id's, (and 
yes, these change periodically), it seems completely reasonable to me to 
request that these be done using functional email addresses.  They may 
or may not represent a, (potentially temporary), work assignment or 
employment.  For someone who frequently changes work assignments or 
employment, a more generic address, either a personal one, or a cut-out 
or email forwarder like gmail intended specifically for that purpose 
might be appropriate.

I read the suggestion as meaning that it should, in general, be possible 
for me as a developer and/or consumer to contact the author of a 
particular commit, which sounds completely appropriate to me, at least 
superficially.  If the commit id's aren't email addresses, then we'd 
need to use some other mapping to figure out how to contact commit 
authors.  Or are there other ways to handle this already?

--rich


  parent reply	other threads:[~2008-07-29 17:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 14:16 Git Migration Status Richard Purdie
2008-07-29 14:54 ` Rolf Leggewie
2008-07-29 15:22   ` Graeme Gregory
2008-07-29 16:40   ` Otavio Salvador
2008-07-29 17:00     ` Tom Rini
2008-07-29 17:21       ` Otavio Salvador
2008-07-29 17:31         ` Tom Rini
2008-07-29 17:11     ` Rich Pixley [this message]
2008-07-29 17:55       ` Otavio Salvador
2008-07-29 19:11 ` Thomas Kunze
2008-07-29 19:31   ` Otavio Salvador
2008-07-29 19:52     ` Tom Rini
2008-07-29 23:57 ` Rod Whitby
2008-07-30  7:20   ` Marcin Juszkiewicz
2008-07-30 11:29     ` Cliff Brake
2008-07-30 12:59       ` Otavio Salvador
2008-07-30 13:07         ` Philip Balister
2008-07-30 14:28           ` Richard Purdie
2008-07-30 15:12             ` Rod Whitby
2008-07-30 16:14               ` Richard Purdie
2008-07-30 17:06                 ` Cliff Brake
2008-07-30 17:26                   ` Cliff Brake
2008-07-31  0:31                     ` Rod Whitby
2008-07-30 17:35                   ` K. Richard Pixley
2008-07-31  2:12                     ` Mike (mwester)
2008-07-31 17:16                       ` K. Richard Pixley
2008-07-31 17:42                         ` Cliff Brake
2008-07-30 17:35                 ` Otavio Salvador
2008-07-30 17:55                   ` Mark Brown
2008-07-31  0:03                 ` Rod Whitby
2008-07-30 16:15             ` Cliff Brake
2008-07-30 17:32             ` Otavio Salvador
2008-07-30 21:35             ` Esben Haabendal
2008-07-30 15:30 ` Rod Whitby

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=488F4F24.3050405@palm.com \
    --to=rich.pixley@palm.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.