From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Mr.SpOOn" <mr.spoon21@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git for collaborative web development
Date: Thu, 26 Mar 2009 20:44:12 +0100 [thread overview]
Message-ID: <fabb9a1e0903261244n15d31b1dw4990e31aafca64f3@mail.gmail.com> (raw)
In-Reply-To: <8f67b6f80903261241s7bbb179bwf5e9fa64f657ca1d@mail.gmail.com>
Heya,
On Thu, Mar 26, 2009 at 20:41, Mr.SpOOn <mr.spoon21@gmail.com> wrote:
> That seems cool. I'll take a look to some documentation to understand it :D
There's probably some typo's and thinko's in there, but you get the
idea. You can use aliases in git to define your own commands. If you
do not prefix the command with a bang it is interpreted as git
command, I use this one to review the changes I made with respect to
origin:
$ git config alias.new "log -C -M --reverse -p origin/master.."
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-26 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:51 Git for collaborative web development Carlo
2009-03-26 19:18 ` Sverre Rabbelier
2009-03-26 19:41 ` Mr.SpOOn
2009-03-26 19:44 ` Sverre Rabbelier [this message]
2009-03-27 0:57 ` Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fabb9a1e0903261244n15d31b1dw4990e31aafca64f3@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=mr.spoon21@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).