From: Keshav Kini <keshav.kini@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] git-svn.txt: mention how to rebuild rev_map files
Date: Wed, 25 Sep 2013 21:21:47 -0500 [thread overview]
Message-ID: <87mwn0pbk4.fsf@gmail.com> (raw)
In-Reply-To: 20130926000648.GE9464@google.com
Jonathan Nieder <jrnieder@gmail.com> writes:
> Keshav Kini wrote:
>
>> I changed the wording of your first paragraph a bit according to what I
>> thought it meant. Does it still convey what you wanted to convey, and is
>> it still correct?
>>
>> Mapping between Subversion revision numbers and Git commit
>> names. In a repository where the noMetadata option is not set,
>> this can be rebuilt from the git-svn-id: lines that are at the
>> end of every commit (see the 'svn.noMetadata' section above for
>> details).
>
> Sounds good.
>
>> Also, I'm having a bit of trouble trying to get a definition to start
>> with a '.' character in AsciiDoc. Escaping the '.' produces a
>> definition block, but with a literal '\' before the '.'. If I don't
>> escape the '.', asciidoc thinks it's a section heading or something. Is
>> asciidoc just incapable of doing this, or am I missing something?
>
> Oh. Yeah, this can be a pain. Quoting the filename with `backticks`
> might work. Writing $GIT_DIR instead of .git might be simpler (see
> v1.5.3.2~18 "Documentation/git-config.txt: AsciiDoc tweak to avoid
> leading dot", 2007-09-14).
Good point. Actually it seems to me that writing $GIT_DIR is in fact
more correct, since $GIT_DIR need not be ".git" at all. So I'll just
use that. Reroll coming up in a bit.
-Keshav
next prev parent reply other threads:[~2013-09-26 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 21:19 [PATCH] git-svn.txt: mention how to rebuild rev_map files Keshav Kini
2013-09-25 19:44 ` Jonathan Nieder
2013-09-25 19:47 ` Eric Wong
2013-09-25 23:37 ` Keshav Kini
2013-09-26 0:06 ` Jonathan Nieder
2013-09-26 2:21 ` Keshav Kini [this message]
2013-09-26 2:41 ` Keshav Kini
2013-09-29 23:45 ` [PATCH v2 0/4] git-svn.txt: miscellaneous changes Keshav Kini
2013-09-29 23:45 ` [PATCH v2 1/4] git-svn.txt: fix AsciiDoc formatting error Keshav Kini
2013-09-29 23:45 ` [PATCH v2 2/4] git-svn.txt: reword description of gc command Keshav Kini
2013-09-29 23:45 ` [PATCH v2 3/4] git-svn.txt: replace .git with $GIT_DIR Keshav Kini
2013-09-29 23:46 ` [PATCH v2 4/4] git-svn.txt: elaborate on rev_map files Keshav Kini
2013-09-30 19:24 ` [PATCH v2 0/4] git-svn.txt: miscellaneous changes Jonathan Nieder
2013-10-10 6:59 ` Eric Wong
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=87mwn0pbk4.fsf@gmail.com \
--to=keshav.kini@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 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).