Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Commands using merge from sorted by
Terminal - Commands using merge - 6 results
git checkout develop; git merge --no-ff myfeature
2012-06-01 08:03:49
User: bbelt16ag
Functions: merge
0

source::: http://nvie.com/posts/a-successful-git-branching-model/

git checkout develop

Switched to branch 'develop'

git merge --no-ff myfeature
svn merge -c -REV
2010-06-21 15:11:13
User: shadycraig
Functions: merge
Tags: svn merge revert
1

This command can be used to revert a particular changeset in the local copy.

I find this useful because I frequently import files into the wrong directory. After the import it says "Committed revision 123" or similar. to revert this change in the working copy do:

svn merge -c -123 .

(don't forget the .) and then commit.

convert {$file_in} \( +clone -background black -shadow 60x5+10+10 \) +swap -background none -layers merge +repage {$file_out}
2009-05-06 10:19:39
User: kureikain
Functions: merge
7

Please take notice that if you are going to use an JPG file for shadow effect,

let change -background none to -background white!

Because -background none make a transparent effect while JPG doesn't support transparent! And when viewing, you will get a bacl box!

So we will use an white background under! We can use other color as well!

/usr/local/bin/svn merge -r {rev_num}:HEAD https://{host}/{project}/branches/{branch_name} .
2009-04-03 15:43:32
User: kamiller
Functions: merge
Tags: svn merge
1

This will merge all of the changes from {rev_num} to head on the branch to the current working directory

git merge --no-commit --no-ff
2009-02-09 18:59:26
User: Pistos
Functions: merge
0

Will do the merge, but only apply changes to working copy and index; won't commit.

svn merge -r 1337:1336 PATH PATH
2009-02-06 00:48:17
User: troelskn
Functions: merge
-1

Reverts the changes that were made in a particular revision, in the local working copy. You must commit the local copy to the repository to make it permanent.

This is very useful for undoing a change.

You can revert multiple changes by specifying numbers wider apart; Just remember to put the highest number first.