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

Re: git-cvsexportcommit and commit date

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Feb 10, 2008, 05:45 UTC
Message-ID
<200802100645.32743.robin.rosenberg.lists@dewire.com>
In-Reply-To
<loom.20080210T033717-237@post.gmane.org>
söndagen den 10 februari 2008 skrev Derek Mahar:
Show 8 quoted lines
> How do you get git-cvsimport to avoid the "duplicate" commit that it creates
> when it imports a commit that you "landed" in CVS with git-cvsexportcommit?  I
> call this commit a duplicate because though it has a different SHA1 identifier,
> commit timestamp, and even committer email address, it refers to the same tree
> identifier as the landed commit.  However, because it has the same textual
> difference as the landed commit, the duplicate commit introduces no new textual
> difference.  It is essentially an "empty" commit.  Do you just accept and ignore
> this empty commit?

git rebase will drop those "empty" commits by default and you'll end up with the cvs-imported version.

-- robin
Previous: Derek MaharNext: Derek Mahar
Message 3 of 9 in “Re: git-cvsexportcommit and commit date”
  1. Martin LanghoffFeb 6, 2008
  2. Derek MaharFeb 10, 2008
  3. Robin RosenbergFeb 10, 2008
  4. Derek MaharFeb 10, 2008
  5. Derek MaharFeb 10, 2008
  6. Robin RosenbergFeb 10, 2008
  7. Derek MaharFeb 10, 2008
  8. Robin RosenbergFeb 10, 2008
  9. Derek MaharFeb 10, 2008

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.