From: Matthias Urlichs <smurf@smurf.noris.de>
To: git@vger.kernel.org
Subject: Re: SVN import issue
Date: Sat, 10 Sep 2005 18:23:13 +0200 [thread overview]
Message-ID: <pan.2005.09.10.16.23.07.865934@smurf.noris.de> (raw)
In-Reply-To: m3fysuodbg.fsf@lugabout.cloos.reno.nv.us
Hi, James Cloos wrote:
> Matthias> Paths in SVN are usually prefixed "/trunk/" (main branch) or
> Matthias> "/branches/foo/" (branch foo); tagging is done by creating
> Matthias> "/tags/bar", with the trunk (or branch) revision it is
> Matthias> pointing to as its parent.
>
> Anyone working on this should note that /usually/ is vital above.
Thanks; I'll keep that in mind.
Is it common (possible?) to have more than one of these?
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
There is no distinctly American criminal class except Congress.
-- Mark Twain
prev parent reply other threads:[~2005-09-10 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 10:40 SVN import issue Matthias Urlichs
2005-08-28 5:11 ` James Cloos
2005-09-10 16:23 ` Matthias Urlichs [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=pan.2005.09.10.16.23.07.865934@smurf.noris.de \
--to=smurf@smurf.noris.de \
--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