From: Konstantin Khomoutov <kostix@bswap.ru>
To: shirlin.joseph@bt.com
Cc: git@vger.kernel.org
Subject: Re: FW: Merging in Git with Branches
Date: Mon, 26 Mar 2018 13:48:55 +0300 [thread overview]
Message-ID: <20180326104855.cfdmgeleemexumin@tigra> (raw)
In-Reply-To: <84fd5584332c450abe8b634921e7b568@rew09926dag15b.domain1.systemhost.net>
On Mon, Mar 26, 2018 at 10:12:04AM +0000, shirlin.joseph@bt.com wrote:
[...]
> Currently there are two main branches that we are utilizing A(master)
> and B(branch of A). Branch is utilised for individual stories(as per
> delivery).
[...]
Cross-posted to [1] as well.
1. https://groups.google.com/d/topic/git-users/nN_faSpd4A4/discussion
prev parent reply other threads:[~2018-03-26 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:12 FW: Merging in Git with Branches shirlin.joseph
2018-03-26 10:48 ` Konstantin Khomoutov [this message]
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=20180326104855.cfdmgeleemexumin@tigra \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
--cc=shirlin.joseph@bt.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).