Search Results for "malware-patch"

...By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. ...

git-branchless is a suite of tools that enhances Git in several ways. It makes Git easier to use, both for novices and for power users. Patch-stack workflows: strong support for "patch-stack" workflows as used by the Linux and Git projects, as well as at many large tech companies. (This is how Git was "meant" to be used.) Prototyping and experimenting workflows: strong support for prototyping and experimental work via "divergent" development. git sync: to rebase all local commit stacks and branches without having to check them out first. git move: The ability to move subtrees rather than "sticks" while cleaning up old branches, not touching the working copy, etc. ...

...To stage part of a file you need to use a command-line program to step through each hunk and if a hunk can't be split down any further but contains code you don't want to stage, you have to edit an arcane patch file by hand? Are you KIDDING me?! Sometimes you get asked to stash your changes when switching branches only to realize that after you switch and unstash that there weren't even any conflicts and it would have been fine to just check out the branch directly? If you're a mere mortal like me and you're tired of hearing how powerful git is when in your daily life it's a powerful pain in your ass, lazygit might be for you.

patchview is one addon to patchutils, with this tool you can view, in a simplified way,only the sub-patches, that you want, of one (big) patch file. You can split patches.To simplify this, it makes the enumeration of the files and you can choose b Code is now available on github : https://github.com/sergiomb2/patchutils

Tired of bogging down your machine to RUN all the TESTS, having to WAIT for the CruiseControl build to be green, or causing other developers HEARTACHE by skipping these steps when checking in your changes to source control? The Patch Process Is for YOU!

A parser for patch (diff) files written as a Python module around the GNU patch code.

With QGit you will be able to browse revisions history, view patch content and changed files, graphically following different development branches.

Xcvs is a web-based CVS tracking tool. It traces the log information in CVS and generates a single patchset for each commit command. It also generates a patch file that captures the change for each patchset. The web interface allows one to query the patc

The Patch Lifecycle Manager (PLM) provides a central point for tracking the lifecycle of patches against a source tree. Regardless of the RCS type system used by the developer to track development of the patch (CVS, Subversion, BitKeeper, or by hand...)

CVSACL is a patch for CVS. It adds two new subcommands (acl & racl) to cvs for access control list management. It provides advanced ACL definitions per modules, directories, and files on branch/tag for all cvs subcommands.

A simple easy-to-use application for "visually editing" large patch files (unified diff files); different patches/diffs/folders/files can be selected/deselected, the resulting patch file can be saved and/or run against a source tree (e.g.).

This patch allows CVS to have a user-level security for the modules. A person is only able to make operations(in pserver mode) if he has the given permissions.

An extension of the current diff & patch programs to support the analysis of differences between binary files. Will include module support to specially handle user-defined types using user-created modules

A patch for CVS that allows bookmarks (stored in ~/.cvsbookmarks file) to be used instead of long and complex repository names.