Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

CCMA 1.0a5 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News CCMA 1.0a5 (Default branch)
# 1  
Old 01-26-2009
CCMA 1.0a5 (Default branch)
Image CCMA is a simple, lightweight change request control manager. When done consistently and accurately, change requests make a invaluable tool. It's the aim of this project to make change request management easy and as useful as possible. License: GNU General Public License v3 Changes:
The following changes were made to the CCMA installer. The security key was changed to be randomly generated rather than asking the end user. The example URL information is explained more clearly at the end of a new install. The readme information was improved. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT OSX

git-request-pull

GIT-REQUEST-PULL(1)						    Git Manual						       GIT-REQUEST-PULL(1)

NAME

       git-request-pull - Generates a summary of pending changes

SYNOPSIS

       git request-pull [-p] <start> <url> [<end>]

DESCRIPTION

       Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with
       the branch description, summarizes the changes and indicates from where they can be pulled.

       The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that
       commit, up to the commit named by <end>, by visiting the repository named by <url>.

OPTIONS

       -p
	   Include patch text in the output.

       <start>
	   Commit to start at. This names a commit that is already in the upstream history.

       <url>
	   The repository URL to be pulled from.

       <end>
	   Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.

	   When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the
	   <local>:<remote> syntax, to have its local name, a colon :, and its remote name.

EXAMPLE

       Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you
       push that change to your public repository for others to see:

	   git push https://git.ko.xz/project master

       Then, you run this command:

	   git request-pull v1.0 https://git.ko.xz/project master

       which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public
       repository.

       If you pushed your change to a branch whose name is different from the one you have locally, e.g.

	   git push https://git.ko.xz/project master:for-linus

       then you can ask that to be pulled with

	   git request-pull v1.0 https://git.ko.xz/project master:for-linus

GIT

       Part of the git(1) suite

Git 2.17.1							    10/05/2018						       GIT-REQUEST-PULL(1)