From: "Elijah Newren" <newren@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-cvsimport bug with dates
Date: Fri, 16 Nov 2007 07:12:29 -0700 [thread overview]
Message-ID: <51419b2c0711160612r1a80bd5o686040f945e8d9c3@mail.gmail.com> (raw)
In-Reply-To: <7vr6iq207f.fsf@gitster.siamese.dyndns.org>
On Nov 15, 2007 11:06 PM, Junio C Hamano <gitster@pobox.com> wrote:
> When you use "branch@{date}" notation, you are not asking a
> question on the project history, but a question on the local
> view from _your_ repository on that project.
Interesting; that makes sense from a merge or pull viewpoint, but
wouldn't it make more sense to have cvsimport ensure the commits are
treated as though they actually existed in master as of the date
specified in CVS?
Elijah
next prev parent reply other threads:[~2007-11-16 14:12 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 [this message]
2007-11-17 10:12 ` Robin Rosenberg
2007-11-17 15:39 ` Elijah Newren
2007-11-17 21:36 ` Jan Hudec
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=51419b2c0711160612r1a80bd5o686040f945e8d9c3@mail.gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).