you can push a separate whiteboard branch directly to a new git repo including 
all history with one command.

i agree that that commit history before dontation is not a big issue, but the 
commit history after the donation and before moving to a new git repo is 
important.

stefan

>-----Original Message-----
>From: Daniel Klco [mailto:[email protected]]
>Sent: Tuesday, January 9, 2018 4:59 PM
>To: [email protected]
>Subject: RE: Where do we put new git modules?
>
>I was just thinking about this as well. What would be the advantage of
>branches over subfolders? When converted to the "real" repo for the module,
>you'd still lose the commit history, right?
>
>Folders might make it easier to see and explore the "contrib" /
>experimental features.
>
>On Jan 9, 2018 7:48 AM, "Stefan Seifert" <[email protected]> wrote:
>
>>
>> >On Tue, Jan 9, 2018 at 1:47 PM, Robert Munteanu <[email protected]>
>> wrote:
>> >> ...- place it in the whiteboard and move it to a proper repo before
>its
>> >> first release, with the release manager proposing a name..
>> >
>> >+1, it's simple and leaves time to make a proper naming decision.
>> >
>> >-Bertrand
>>
>> yes, this would avoid making the naming decision early, or even the
>> decision to release it at all.
>> on the other hand it makes it more difficult if the contribution was
>> already developed in a standalone git repo outside the ASF and perhaps
>> there is already a commit history we want preserve - getting this into
>the
>> whiteboard master branch in a subdirectory is complicated.
>>
>> or do you propose a new branch for each contribution in the whiteboard,
>> not related to it's master branch at all?
>> having everything in the master branch also makes it difficult to split
>it
>> later (yes i know, it's possible in git, but still requires more effort
>> then just having one branch per module).
>>
>> having one branch per contrib/whiteboard module may seem unorthodox on
>the
>> first sight, but might come very handy when it's moved later, and also
>for
>> the first import.
>>
>> stefan
>>
>>

Reply via email to