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

Re: [RFD] Deepen the git directory structure a bit.

From
FKFabian Kössel <mok4sin@googlemail.com>
Date
Feb 25, 2010, 10:58 UTC
Message-ID
<4B8657EC.8060302@googlemail.com>
In-Reply-To
<7v7hq46gwe.fsf@alter.siamese.dyndns.org>
On 22.02.2010 23:32, Junio C Hamano wrote:
> I'll queue with a trivial addition of "rm builtin/*.o" to the "make
clean"
> target.  I am not looking forward to merging the result of this with
other
> topics, though... X-<.

Just out of curiosity, how do you actually merge such a relatively big rename with other branches?

I haven't found a pleasant way yet to merge rename+modification in one branch and modification on an old path in another branch.

There is git file-merge theirs base ours . But it only seems to take filenames and no git object specifications. It would be very handy if something like

git file-merge bfile HEAD^:afile afile
would be possible.
For clearification, here an example
echo "First line" > afile

git add . git commit -m "First commit in master"

git checkout -b mybranch

echo "Second line in mybranch" >> afile git mv afile bfile

git commit -a -m "Change and rename in mybranch"
git checkout master
echo "Changed first line in master" > afile
git commit -a -m "changed afile"
git merge mybranch
Regards
Fabian
Previous: Junio C HamanoNext: Junio C Hamano
Message 10 of 11 in “[RFD] Deepen the git directory structure a bit.”
  1. Linus TorvaldsFeb 18, 2010
  2. Junio C HamanoFeb 18, 2010
  3. Avery PennarunFeb 18, 2010
  4. Linus TorvaldsFeb 18, 2010
  5. Linus TorvaldsFeb 18, 2010
  6. Christian MICHONFeb 18, 2010
  7. Pavan Kumar SunkaraFeb 19, 2010
  8. Linus TorvaldsFeb 22, 2010
  9. Junio C HamanoFeb 22, 2010
  10. Fabian KösselFeb 25, 2010
  11. Junio C HamanoFeb 27, 2010

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.