Re: Request for a personal git tree for AT91/AVR32

[Robert Schuster <theBohemian@gmx.net>]

[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]

Hi Ulf,

somehow nobody cared to answer this :$
Ulf Samuelsson schrieb:
> Is the "personal" git tree really personal, or can you have
> a git tree which is available to a group?
We normally give r/w access to individuals. With write access you have
the possibility to create user branches. After you fixed/added/whatever
a certain feature you can propose your changes on the list and if its
fine it can be merged.

> It makes sense for me to have an "atmel" group which I
> could share with other interested atmel employees.
I think the closest you can get with git is that one person commits on
behalf of someone else, e.g. git commit --author <the other person>

Of course it would also be possible to give write access to more people.

> Who is making decisions on access?
The OE team. Someone proposes you and then the rest of OE informally
votes. If no one has strong objections which needs to be discussed
write access will be granted.

I will write that proposal for you. :)

Regards
Robert

> 
> Best Regards
> Ulf Samuelsson
> 
> 
>>>
>>> I then made the linux recipy depend on the u-boot native tools,
>>> and then u-boot.git was selected and oe tried
>>> to do git access to www.angstrom-distribution.org or something similar.
>>> I do not know why, and could not figure out why it did so.
>>>
>>> That is why I wrote the new recipy.
>>>
>>>> so I don't see real point in using versioned approach.
>>>
>>> If you want to add patches they may or may not be broken by a later git
>>> version.
>>> It is more important to have something which has been tested and
>>> validated
>>> than the latest stuff.
>>>
>>> I agree that it would have been better to use the 2008.10 though.
>> Wel, look at u-boot_git.bb, it has tags fixed for some machines, and
>> apply patches too. I never had problems with it. That could save you
>> lots of time.
>> you can fix versions by providing git commit hashes in SRC_URI. Look
>> at mentioned
>> u-boot_git on how this is done.
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]