From: Derek Mahar <derek.mahar@gmail•com>
To: git@vger•kernel.org
Subject: Re: git-cvsexportcommit and commit date
Date: Sun, 10 Feb 2008 03:53:43 +0000 (UTC) [thread overview]
Message-ID: <loom.20080210T033717-237@post.gmane.org> (raw)
In-Reply-To: 47AA0FD8.1050801@catalyst.net.nz
Martin Langhoff <martin <at> catalyst.net.nz> writes:
> I just don't worry about the timestamps
>
> I normally track the Moodle CVS tree, and do all my "new feature" and
> "client customization" branches in git. The feature branches I rebase
> aggressively, until they are ready to be "landed" in CVS. It is in that
> "landing in cvs" that I use cvsexportcommit, usually with a long list of
> commits!
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?
Derek
next prev parent reply other threads:[~2008-02-10 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFFF18703C.5539A99A-ON852573E7.00699FE4-852573E7.006A0F3E@db.com>
2008-02-06 19:51 ` git-cvsexportcommit and commit date Martin Langhoff
2008-02-10 3:53 ` Derek Mahar [this message]
2008-02-10 5:45 ` Robin Rosenberg
2008-02-10 6:01 ` Derek Mahar
2008-02-10 6:13 ` Derek Mahar
2008-02-10 13:15 ` Robin Rosenberg
2008-02-10 16:01 ` Derek Mahar
2008-02-10 16:17 ` Robin Rosenberg
2008-02-10 16:30 ` Derek Mahar
[not found] <OFEEDE9683.291E2C34-ON852573E2.00555C6A-852573E2.0055C505@db.com>
2008-02-01 23:50 ` Martin Langhoff
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=loom.20080210T033717-237@post.gmane.org \
--to=derek.mahar@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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