From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Andy Parkins" <andyparkins@gmail.com>, git@vger.kernel.org
Subject: Re: git-cvsserver won't add new content on update
Date: Fri, 19 Jan 2007 08:01:56 +1300 [thread overview]
Message-ID: <46a038f90701181101w1ea300b6lb4d7e4354d89be95@mail.gmail.com> (raw)
In-Reply-To: <20070118162222.GE15428@spearce.org>
On 1/19/07, Shawn O. Pearce <spearce@spearce.org> wrote:
> You need to commit first to get the file completely added.
> What you are seeing above is that the file was listed in
> some/sub/directory/CVS/Entries so that the next commit will
> know to upload the file to the server. Until then its not
> actually going to do that...
yup. Also make sure you are using a really recent git-cvsserver, I
recently fixed a couple of problems related to file adds.
cheers.
martin
next prev parent reply other threads:[~2007-01-18 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 16:16 git-cvsserver won't add new content on update Andy Parkins
2007-01-18 16:22 ` Shawn O. Pearce
2007-01-18 19:01 ` Martin Langhoff [this message]
2007-01-19 9:54 ` Andy Parkins
2007-01-19 7:21 ` Andy Parkins
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=46a038f90701181101w1ea300b6lb4d7e4354d89be95@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).