From: "Eric S. Raymond" <esr@thyrsus.com>
To: Ilya Basin <basinilya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)
Date: Tue, 23 Apr 2013 17:06:57 -0400 [thread overview]
Message-ID: <20130423210657.GA32382@thyrsus.com> (raw)
In-Reply-To: <538486753.20130423223007@gmail.com>
Ilya Basin <basinilya@gmail.com>:
> For new branches the 'from' command can refer the common ancestor in
> an existing branch. For example:
>
> /----------E thebranch
> /
> A---B---C---D master
>
> Commit E is newer than D; we already imported D; thebranch is new.
> Instead of:
> from refs/heads/thebranch^0
> refer the parent as:
> from refs/heads/master^2
Understood. Do you actually need this much generality in practice,
or is it a theoretical case?
> OK, something's wrong with the man page: starting with '-A' the
> description is unstructured:
Interesting. The aciidoc parser got a little confused, but inserting
some blank lines fixed it.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2013-04-23 21:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 8:18 cvsps: bad usage: invalid argument --norc Ilya Basin
2013-04-14 8:48 ` Ilya Basin
2013-04-14 9:47 ` John Keeping
2013-04-14 11:33 ` State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc) Eric S. Raymond
2013-04-15 5:00 ` Michael Haggerty
2013-04-15 17:58 ` Ilya Basin
2013-04-15 20:43 ` Jakub Narębski
2013-04-18 9:43 ` Eric S. Raymond
2013-04-19 5:29 ` Does git fast-import support deltas? Ilya Basin
2013-04-19 5:44 ` Felipe Contreras
2013-04-19 6:13 ` Jonathan Nieder
2013-04-20 10:22 ` Re[2]: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc) Ilya Basin
2013-04-23 17:50 ` Eric S. Raymond
2013-04-23 18:30 ` Re[2]: " Ilya Basin
2013-04-23 21:06 ` Eric S. Raymond [this message]
2013-04-24 4:47 ` Ilya Basin
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=20130423210657.GA32382@thyrsus.com \
--to=esr@thyrsus.com \
--cc=basinilya@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.