[LLVMdev] Howdy + GIT

Sean Silva chisophugis at gmail.com
Fri Jan 16 14:31:27 PST 2015


On Fri, Jan 16, 2015 at 5:38 AM, Reid Spencer <reid at reactific.com> wrote:

> Owen, and many others …
>
> I do not wish to belabor this conversation as it distracts from everything
> else you all have to do.
>
> The fact that llvm does have a synchronized repository on github is
> sufficient for me. I can fork it, hack on it, and keep it up to date as
> needed. If a change I make is sufficiently useful, I’ll just submit a
> patch.
>
> The arguments about monotonically increasing revision number are, in my
> view, rather silly. That is not a very good reason for choosing or even
> staying with an SCM. There are stronger arguments for sticking with SVN.
>
> The arguments about having a single line of change is valid, but SVN isn’t
> the only tool that supports that model. I’m in support of this approach as
> I use it on all my projects, including those using GIT.
>
> I do understand that many automated processes are now built up around SVN
> and changing to git would be a huge effort with little to be gained.
>
> In putting out my inquiry, I was concerned more about LLVM being
> sequestered off in a corner of the Internet and not having its code as
> easily available as on, say, github. Code access and brows ability is one
> of the things that fosters innovation. However, I get that switching would
> be a huge pain and that LLVM is by now a mature project where perhaps
> innovation is taking a back seat to maintaining a standard development
> model that its many existing developers have grown accustomed to.
>
> So, let’s follow Owen’s suggestion and end the conversation about SCM
> choice and replace it with conversations about improving the development
> process. I for one will need to get back into that process before I can
> comment because it is clear that after 7 years, things just ain’t the same.
> :)
>

There is definitely quite a bit of stuff that is recognized as being pretty
crusty and in need of revitalization (and for all I know, you might find
familiar even with 7 years of absence). Bugpoint, TableGen, the llvm.org
website, bugzilla, etc.

-- Sean Silva



>
> Best,
>
> Reid.
>
> On Jan 16, 2015, at 6:40 AM, Owen Anderson <resistor at mac.com> wrote:
>
>
> On Jan 16, 2015, at 3:26 AM, Erik de Castro Lopo <mle+cl at mega-nerd.com>
> wrote:
>
> As for all the reason why the LLVM project does not use Git, I wonder
> why large complex projects like the Linux kernel, Wine, MinGW-w64,
> GHC and many many others don't seem to have any major problems using
> Git.
>
>
> Lots of projects are also happy with Mercurial, or BZR, or even CVS.
>
> Every open source community has its own established workflows by which
> developers interact with and ultimately contribute to the mainline
> repository.  Those workflows, and the common use cases that lead to them,
> strongly impact what specific SCM arrangements will or will not work.
>
> To take the Linux kernel as an example, they use a very different
> integration strategy from LLVM that is predicated on having a significant
> hierarchy of developers whose major roles are to act as integrators for
> incoming patches.  Obviously they use (and built!) an SCM tool that
> supports their workflow.
>
> LLVM does *not* use such a workflow.  The outcome of several iterations of
> this discussion on this list has been that, for the LLVM community’s
> workflow, the advantages of moving mainline to git have not been seen as
> substantial versus our current arrangement, and it will lose some features
> that are useful.
>
> Any re-opening of this discussion needs to address the fundamental
> question of how switching mainline to git will actively help the LLVM
> community’s development process, and whether those benefits will outweigh
> the downsides.
>
> —Owen
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150116/74cde87f/attachment.html>


More information about the llvm-dev mailing list