[MPlayer-dev-eng] [PATCH 2/2] build: Add .gitignore file.

[Reimar Döffinger]

On 22 Jun 2011, at 08:08, Reimar Döffinger <Reimar.Doeffinger at gmx.de> wrote:
> On 21 Jun 2011, at 23:36, Clément Bœsch <ubitux at gmail.com> wrote:
>> On Wed, Jun 22, 2011 at 12:30:34AM +0300, Ivan Kalvachev wrote:
>>> On 6/21/11, Reimar Döffinger <Reimar.Doeffinger at gmx.de> wrote:
>>>> On Mon, Jun 20, 2011 at 10:07:03AM +0200, Diego Biurrun wrote:
>>>>> On Mon, Jun 20, 2011 at 12:20:20AM +0200, Ingo Brückl wrote:
>>>>>> Diego Biurrun wrote on Sun, 19 Jun 2011 23:33:19 +0200:
>>>>>> 
>>>>>>> While MPlayer does not currently use git, this is useful when working
>>>>>>> with
>>>>>>> git-svn clones and will ease a future transition from Subversion to
>>>>>>> git.
>>>>>>> .gitignore |   54
>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>> 1 files changed, 54 insertions(+), 0 deletions(-)
>>>>>>> create mode 100644 .gitignore
>>>>>> 
>>>>>> I'd say let's introduce git stuff when we officially use git, not now.
>>>>>> Who
>>>>>> needs this now, should add it to his working copy.
>>>>> 
>>>>> That's annoying and everybody has to duplicate the same effort locally
>>>>> - what's the point of waiting?
>>>> 
>>>> It's fine by me, I think it's ok to have it in SVN.
>>> 
>>> Fine by me, too.
>> 
>> OK with me if that wasn't clear of course. BTW, what's blocking us from
>> using git? A sysadmin? external sub repositories?
> 
> Doing it properly means building a git repo with proper, full-name author entries
> from SVN commit names and "patch by" attributions, checking that we get everything
> external in a proper way via submodules (by what I can tell submodules still do not support
> always fetching the latest version?), write usage documentation and accept we can
> no longer fix commit messages.
> I at least don't feel like investing the effort for what seems like not much of an advantage
> if any over git-svn.

And I forgot: losing human-usable version numbers unless we make an extra effort.
In short: I think git is great for experienced developers, but for something that users use directly or new developers IMO it at best is crappy.