git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] My Git Dev Blog - Week 3

From
Atharva Raykar <raykar.ath@gmail.com>
Date
Jun 7, 2021, 12:52 UTC
Message-ID
<D56DACFE-1E85-4765-80AC-0B60C2403CC8@gmail.com>
In-Reply-To
<37725450-9769-01f1-d615-b3869ebbb33d@gmail.com>
On 07-Jun-2021, at 14:27, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
Show 17 quoted lines
> 
> 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`?

I actually created another branch based off master, and then applied those two patches on them. Me mentioning 'merge (A) on master' was a mistake. I'll correct it.

Show 5 quoted lines
> 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.
Agreed.
> Thanks.
> 
> -- 
> An old man doll... just what I always wanted! - Clara
Previous: Bagas SanjayaNext: Kaartic Sivaraam
Message 4 of 7 in “[GSoC] My Git Dev Blog - Week 3”
  1. Atharva RaykarJun 6, 2021
  2. Christian CouderJun 7, 2021
  3. Bagas SanjayaJun 7, 2021
  4. Atharva RaykarJun 7, 2021
  5. Kaartic SivaraamJun 7, 2021
  6. Atharva RaykarJun 8, 2021
  7. Kaartic SivaraamJun 8, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.