From: Ram Rachum <ram@rachum.com>
To: git@vger.kernel.org
Subject: git cascade and git forward-merge
Date: Tue, 01 Apr 2014 13:41:37 +0300 [thread overview]
Message-ID: <533A97E1.5080806@rachum.com> (raw)
Hi guys!
I just made two Git scripts of mine open-source:
https://github.com/cool-RR/git-cascade
<https://github.com/cool-RR/git-cascade>
This project contains two scripts:
- git cascade - Cascade changes from each branch to its dependents.
- git forward-merge - Merge branches without checking them out.
Click the GitHub link above to read all about them.
Thanks,
Ram.
next reply other threads:[~2014-04-01 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:41 Ram Rachum [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-29 23:01 git cascade and git forward-merge Schuyler Duveen
2014-04-30 0:05 ` Felipe Contreras
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=533A97E1.5080806@rachum.com \
--to=ram@rachum.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.