From: Jan Hudec <bulb@ucw.cz>
To: Elijah Newren <newren@gmail.com>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: git-cvsimport bug with dates
Date: Sat, 17 Nov 2007 22:36:17 +0100 [thread overview]
Message-ID: <20071117213617.GG5198@efreet.light.src> (raw)
In-Reply-To: <51419b2c0711170739p1a2bf6c7g87f615676f72aedf@mail.gmail.com>
On Sat, Nov 17, 2007 at 08:39:08 -0700, Elijah Newren wrote:
> Okay...so I guess my suggestion could be translated as: don't worry
> about when the commit entered; instead make git-cvsimport mark the
> refs as changed as of the CVS date mentioned instead of as of the
> import time.
>
> I guess there would be reluctance to do this whenever git-cvsimport
> would be used for incremental commits on a repository that also had
> local commits? Sounds like the issue is deeper than I first realized
> and this probably isn't worth the effort it'd take.
Actually local commits don't need to be involved at all. Incremental import
is enough.
One good reason to use reflog is when you notice something does not work and
recall, that it worked yesterday evening. Than you need to know what you were
looking at at that time, not at what was latest, because you didn't
necessarily have to be up-to-date.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
prev parent reply other threads:[~2007-11-17 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 4:59 git-cvsimport bug with dates Elijah Newren
2007-11-16 6:06 ` Junio C Hamano
2007-11-16 14:12 ` Elijah Newren
2007-11-17 10:12 ` Robin Rosenberg
2007-11-17 15:39 ` Elijah Newren
2007-11-17 21:36 ` Jan Hudec [this message]
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=20071117213617.GG5198@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=robin.rosenberg.lists@dewire.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).