From: Manu Abraham <abraham.manu@gmail.com>
To: Halim Sahin <halim.sahin@t-online.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [vdr] [v4l-dvb-maintainer] [Wanted] dvb-ttpci maintainer
Date: Thu, 25 Sep 2008 20:40:46 +0400 [thread overview]
Message-ID: <48DBBF0E.8030000@gmail.com> (raw)
In-Reply-To: <20080925160417.GA11821@halim.local>
Halim Sahin wrote:
> Hi,
> On Do, Sep 25, 2008 at 07:04:13 +0400, Manu Abraham wrote:
>> Halim Sahin wrote:
>>> Hi,
>>>
>>> On Do, Sep 25, 2008 at 06:01:41 +0400, Manu Abraham wrote:
>>>> http://lwn.net/Articles/297301/
>>>
>>> Please read this:
>>>
>>> http://www.linuxtv.org/pipermail/vdr/2008-January/015329.html
>>> You wrote the merge window is open for 2.6.25.
>>> We have now stable 2.6.26 and 2.6.27 is allmost ready.
>> As i wrote, fixes came in and had to be fixed. You can see the commit
>> history here:
>>
>> http://jusst.de/hg/multiproto/shortlog
>
> Right
>
>> In between, i went for vacation due to my marriage. During that period i
>> had little access, but did whatever possible to get feedback/patches in
>> there, during whatever time and access i had.
>
> During your vacation somebody else could ad patches if you
> wanted to work with other developers.
If you see the logs, the last fix changeset 9039 was added while i was
away. Anyone can add patches to the tree, just that i need to pull back
the changes from that person.
For example: while i was away, somebody else did a clone of the same
tree and added the patches.
> This could only happen if you have your code under linuxtv.org and or
> merged it completely to v4l-dvb!
There are 2 development models, a centralized style (CVS/SVN etc) and a
distributed style (mercurial/git etc). The centralized model, offers a
CVS tree or a SVN tree to which multiple people have commit access to.
This was how the old DVB and dvb-kernel CVS trees worked. But this
centralized development model was phased out quite long back, in favour
of a distributed model.
The distributed development model works the same from any place. Person
A makes the changes to his local tree and those changes can be pulled in
to the working repository.
> You are the maintainer of multiproto and
> So nobody could work on it in your absence time!
As i pointed out just above, somebody else did a clone of the tree and
added in some changes that people sent to the ML. I can pull in those
changes as what is applicable from that tree. This is how distributed
development works.
> Sorry this sounds not ok to me.
I don't have any problem in using whatever SCM, but it makes it a little
bit easier for the user to have some similarities between development
trees. Maybe if more people are for a centralized repository, then
people should voice concern as to change the SCM. This has nothing to do
with me.
> Anyway the problem is nobody should leave linuxtv.org project.
> We should now stop this and go on.
> Please !!!!!!!!!
> Thanks for your great work!
Regards,
Manu
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-25 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 17:22 [linux-dvb] [Wanted] dvb-ttpci maintainer Oliver Endriss
2008-09-24 17:48 ` Goga777
2008-09-25 10:09 ` Oliver Endriss
2008-09-24 17:55 ` VDR User
2008-09-25 1:28 ` [linux-dvb] [v4l-dvb-maintainer] " hermann pitton
2008-09-25 1:40 ` Torgeir Veimo
2008-09-25 1:45 ` [linux-dvb] Re : " manu
2008-09-25 2:01 ` hermann pitton
2008-09-25 10:54 ` [linux-dvb] " Oliver Endriss
2008-09-25 12:28 ` [linux-dvb] [vdr] " Halim Sahin
2008-09-25 14:01 ` Manu Abraham
2008-09-25 14:50 ` Halim Sahin
2008-09-25 15:04 ` Manu Abraham
2008-09-25 16:04 ` Halim Sahin
2008-09-25 16:40 ` Manu Abraham [this message]
2008-09-26 15:14 ` [linux-dvb] " Oliver Endriss
2008-09-26 18:43 ` hermann pitton
2008-09-26 19:10 ` VDR User
2008-09-26 19:31 ` hermann pitton
2008-09-26 19:26 ` Markus Rechberger
2008-09-25 2:10 ` [linux-dvb] " Markus Rechberger
2008-09-26 9:44 ` Oliver Endriss
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=48DBBF0E.8030000@gmail.com \
--to=abraham.manu@gmail.com \
--cc=halim.sahin@t-online.de \
--cc=linux-dvb@linuxtv.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