From: Sverre Rabbelier <srabbelier@gmail.com>
To: Carlo <mr.spoon21@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git for collaborative web development
Date: Thu, 26 Mar 2009 20:18:00 +0100 [thread overview]
Message-ID: <fabb9a1e0903261218y329562f6uf18613f3f9e15836@mail.gmail.com> (raw)
In-Reply-To: <loom.20090326T184207-345@post.gmane.org>
Heya,
On Thu, Mar 26, 2009 at 19:51, Carlo <mr.spoon21@gmail.com> wrote:
> Using git he should save, commit, add, push... so it's a bit longer.
>
> Is there a nice compromise? Or a better way to use git for such a task or web
> development in general?
$ git config alias.tryout "!git branch -f tryout && git checkout
tryout && git add . && git commit -m TryOut && git push shared_repo
tryout"
You can even see the page live if you set the proper attributes ;).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-26 19:20 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 [this message]
2009-03-26 19:41 ` Mr.SpOOn
2009-03-26 19:44 ` Sverre Rabbelier
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=fabb9a1e0903261218y329562f6uf18613f3f9e15836@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).