search for: committe

Hello, Please join me in welcoming Gene Cumm as official committer to the Syslinux project. In 19 years, Gene is only the third committer to this project, a reflection of his technical and community contributions over the last several years. Thank you! -hpa

...nge author. I think that's better for attribution than just including "Patch By: username" in the message which is default for arc, especially now that we're finally using Git. However, I've noticed that when the change breaks bots, emails are sent only to the author, not the committer. I think that's counterintuitive because the author in these cases doesn't even have permission to revert the change (otherwise they would have pushed the change themselves). Can we modify bot notifications to either send the email to committer or (preferably) both? -------------- next pa...

Ian, this one is special just for you. I''m sending it as an attachment because my email client will mangle it. This patch will remove the cmake dependency from xen prior to autoconf stubdom This patch applies ontop of [VTPM v7 3/8] vtpm/vtpmmgr and required libs to stubdom/Makefile You can apply it to your tree by doing the following: git rebase -i <VTPM v7 3/8 revision>

...ldbot. We'd have to discuss where we'd draw the line between 'fast' and 'slow'. How difficult would it be with GitHub to set up something to automatically merge pull requests if they keep the buildbots happy? The workflow would then be to send a pull request annotated by a committer as ready to merge (i.e. reviewed / due for post-commit review). If it passed, then no more human interaction would be required - once the buildbots had finished testing it, it would be the new master (effectively, we’d merge to a speculative-master and then perform a simple fast-forward push from...

.... If I'm comfortable with the patch, I commit > directly, if I want others opinions, I create a review. If we move as > you propose, I'd lose the second option. A pull request is a mechanism. The community can decide what the policy is. > I also don't think pre-commit review committers should be just relying > on the fast bots passing. There are many other issues like code > quality, formatting, tests, etc. that need to be done properly. I agree, but it’s much harder to automate that (though having clang-format automatically applied might be nice). > If we go this ro...

...sides. We've seen a lot of patches on the mailing lists that did > > not get chance to be either reviewed or applied and that means we will > > potentially loose a lot contributions -- or even worse, contributors. > > > > Therefore, I'm here to call to become the new committer/maintainer of > > the Syslinux project and help the project as much as I can on > > reviewing/applying patches, tracking and fixing bugs, supporting new > > contributors and the project itself. > > > Congratulations! Syslinux will benefit a lot from your maintenance. &gt...

...seen a lot of patches on the mailing lists that did >> > not get chance to be either reviewed or applied and that means we will >> > potentially loose a lot contributions -- or even worse, contributors. >> > >> > Therefore, I'm here to call to become the new committer/maintainer of >> > the Syslinux project and help the project as much as I can on >> > reviewing/applying patches, tracking and fixing bugs, supporting new >> > contributors and the project itself. >> > >> Congratulations! Syslinux will benefit a lot from y...

...related thing) from both HPA and Genec sides. We've seen a lot of patches on the mailing lists that did not get chance to be either reviewed or applied and that means we will potentially loose a lot contributions -- or even worse, contributors. Therefore, I'm here to call to become the new committer/maintainer of the Syslinux project and help the project as much as I can on reviewing/applying patches, tracking and fixing bugs, supporting new contributors and the project itself. Thanks, Paulo -- Paulo Alcantara, C.E.S.A.R Speaking for myself only.

I'm happy to announce that I've added Roman Kagan as a committer to the https://github.com/libguestfs/libguestfs repo. Roman has contributed many high quality patches over a period of one year. Roman, the rules are: - Post patches first on the mailing list. - Uncontroversial patches should receive one ACK before being pushed upstream. - Very complex...

On Fri, Dec 13, 2013 at 6:36 PM, H. Peter Anvin <hpa at zytor.com> wrote: > Hello, > > Please join me in welcoming Gene Cumm as official committer to the > Syslinux project. In 19 years, Gene is only the third committer to this > project, a reflection of his technical and community contributions over > the last several years. > > Thank you! And thank you. I'm honored. -- -Gene

...HPA and > Genec sides. We've seen a lot of patches on the mailing lists that did > not get chance to be either reviewed or applied and that means we will > potentially loose a lot contributions -- or even worse, contributors. > > Therefore, I'm here to call to become the new committer/maintainer of > the Syslinux project and help the project as much as I can on > reviewing/applying patches, tracking and fixing bugs, supporting new > contributors and the project itself. > Congratulations! Syslinux will benefit a lot from your maintenance. Regards, > > Thanks,...

Dear Xen Developers, I wanted to announce that Ian Campbell from Citrix has been nominated and elected as Xen Hypervisor committer <http://lists.xen.org/archives/html/xen-devel/2012-01/msg02281.html> and will be responsible for the ARMv7+VE components in xen-unstable. We have seen an increasing number of patches to xen-unstable to enable support for the ARMv7 processor with virtualization extensions: 64 to be preci...

[Let's start a new thread for this so all the mail archives will appear in one place. Please follow up on any of these items, and hopefully we can formulate policy together.] (1) Policy for commits. [with thanks to Dan Berrange for helping to formulate this ...] "In order to become a committer, someone must demonstrate an ongoing skill posting patches of high quality and displaying a full understanding of the libguestfs code. "Once someone becomes a committer, they must post patches first to the mailing list. Two ACKs from other committers are required for uncontroversi...

Erik> I am surprised noone has mentioned the one of the biggest Erik> advantages of Git which is proper author attribution for Erik> non-core and drive-by patch contributors. >From what I can make of the git-svn docs, that LLVM committers should be adding a "From: <email>" field to commit messages instead of "Patch by <name>". If the original author is already in the git commit, you can generate the "From: <email>" field in the SVN commit message with: git svn --add-author-from...

...now looks like this. We intend to go into code freeze at the end of the week, after which patches even for bugfixes will be much harder to get into the tree. We are here: | Feature code freeze | | Bugfixes are allowed provided they are not high-risk. | | No new features will be committed. This is imminent: | Slushy code freeze | after Friday 18 Feb | | Bugfixes are allowed but only if they either: | - fix an important bug; or | - are very trivial and low-risk. | | All changes to receive a formal ack from a maintainer other than | the co...

...he git side. Infrastructure decisions will need to be taken into account, but that doesn't interfere with the "how we commit" discussion in any way. On 25 February 2016 at 08:55, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I'm afraid I've never committed to any github project before, so I am a bit > confused on how committing would work in practice. GitHub (and others) work by fork&pull-request. Simply put, you fork the original repo, do your changes, push to your repo and make a "pull-request" to the original repo. The added wor...

Martin F. Krafft (madduck) has been added to the project. P.S. I'd like to get a release out sometime next week. -- Todd Troxell http://rapidpacket.com/~xtat -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url :

The meeting took place last Wed, the 14th of June Minutes see: http://wiki.xen.org/wiki/Xen_Maintainer,_Committer_and_Developer_Meeting/June_2012_Minutes

...em while they scan the extent tree, and if need_resched() they will drop the lock and schedule. The transaction commit needs to take a write lock for this rwsem for a very short period to switch out the commit roots. If there are a lot of threads doing this caching operation we can starve out the committers which slows everybody out. To address this we want to add this functionality to see if our rwsem has anybody waiting to take a write lock so we can drop it and schedule for a bit to allow the commit to continue. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- I''ve cc...

...I'm not really > inclined to change a process which leaves the system of record *exactly* the > same (a textual acknowledgement of attribution) and only makes one mirror of > it superficially better. Adding --use-log-author to "git svn fetch" will have no effect unless the committer either adds --add-author-from to "git svn dcommit" or does a one-time setup: $ git config --global config svn.addAuthorFrom true You can continue to use "Patch by <name>" if neither you nor the author care. If correct attribution on the git mirror is important to *...