[LLVMdev] code-owner sporks

[NAKAMURA Takumi]

Greg,

Unfortunately, I don't expect pulling would not work better as our expected.
For example, GIT_AUTHOR is not honored for 3rd committer to
git-svn-dcommit, even if GIT_AUTHORS is registered person.

I am planning to implement the pre-commit tester, like Buildbot's "Try
builder". Then changesources could be our Phab.

I think to provide a method to confirm consistency with unit tests
would help us. How do you think?

ps. It would be helpful; To mention "My proposal is also available in
{{sha1}} in github/person/repo.git" like pull-request, in a proposal.
Pulling commits from other git repos is easier to some of us.

...Takumi


2012/11/16 Greg Fitzgerald <garious at gmail.com>:
> Just brainstorming here, but what if each CODE_OWNER maintained a spork on
> Github and accepted Pull Requests?  What's a spork, you ask?  Well it's fork
> with no intent to diverge - it spoons some centralized repo (be it via git
> or git-svn).  If you haven't heard the term 'spork' in this context before,
> it's either because I just made it up or that we share the same incapacity
> to google effectively.
>
> As a contributor, my process would be to fork Github's llvm-mirror and make
> my patch locally.  Then I'd crawl up the directory tree from my code changes
> until I found a CODE_OWNER.TXT.  Worst case, I get to the root directory and
> spot a CODE_OWNER.TXT with a URI to the central repository.  All other
> CODE_OWNER.TXT files would contain a git URI pointing to the code owner's
> spork.  I'd make a Pull Request and hope for a review from the owner and/or
> anyone else monitoring that spork.  Once the owner accepts the Pull Request,
> it'd be between the members of the code-owner oligarchy how and when the
> patch is upstreamed to the central repository.
>
> Thoughts?
>
> Thanks,
> Greg
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>