From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [GSoC] My Git Dev Blog - Week 3
Date: Mon, 7 Jun 2021 15:57:55 +0700 [thread overview]
Message-ID: <37725450-9769-01f1-d615-b3869ebbb33d@gmail.com> (raw)
In-Reply-To: <FC56DF49-CEC5-4C9F-BDE4-B0119558E4B2@gmail.com>
Hi Atharva,
On 06/06/21 19.26, Atharva Raykar wrote:
> Hi,
>
> Here is my latest instalment in my weekly Git blog:
> http://atharvaraykar.me/gitnotes/week3
>
You said:
> Simple enough, I thought. Just fast-forward merge (A) on master, and then, uhh, cherry pick and apply (B) on top of the newly merged (A). Resolve any conflict in this stage. That way I get (A) and (B) in their pristine individuality, as well as a third branch that combines both the changes.
But before, you said:
> Once it was becoming clear that would not happen, I thought of combining those two branches on another branch (that would hold all my patches so far).
Are you merging two branches that contains your separated patchsets
directly to your own `master` branch, or are you merging them to
temporary branch that is branched directly from `master`?
Also, you advised that:
> Check your resolved conflict before continuing the merge
IMO, once you have resolved all the conflicts, compile and test before
commit the resulting merge. This way, it will be nicer for review.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-06-07 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 12:26 [GSoC] My Git Dev Blog - Week 3 Atharva Raykar
2021-06-07 8:19 ` Christian Couder
2021-06-07 8:57 ` Bagas Sanjaya [this message]
2021-06-07 12:52 ` Atharva Raykar
2021-06-07 18:55 ` Kaartic Sivaraam
2021-06-08 7:13 ` Atharva Raykar
2021-06-08 17:55 ` Kaartic Sivaraam
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=37725450-9769-01f1-d615-b3869ebbb33d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=raykar.ath@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).