From: "Jon Smirl" <jonsmirl@gmail.com>
To: git <git@vger.kernel.org>
Subject: parsecvs and unnamed branches
Date: Fri, 16 Jun 2006 17:44:43 -0400 [thread overview]
Message-ID: <9e4733910606161444i2f996096sbd1f9b3f3ff3a32d@mail.gmail.com> (raw)
I'm getting thousands of messages about unnamed branches and even
'unnamed branch from master-UNNAMED-BRANCH'.
How do you get unnamed branches into CVS, are these check-in errors or
are people actually working on unnamed branches? Or is parsecvs not
finding all of the branch info?
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2006-06-16 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 21:44 Jon Smirl [this message]
2006-06-16 22:19 ` parsecvs and unnamed branches Keith Packard
2006-06-16 22:28 ` Jon Smirl
2006-06-16 22:39 ` Jon Smirl
2006-06-16 22:51 ` Keith Packard
2006-06-17 3:02 ` Jon Smirl
2006-06-17 3:12 ` Pavel Roskin
2006-06-17 3:31 ` Jon Smirl
2006-06-17 4:08 ` Pavel Roskin
2006-06-17 4:15 ` Jon Smirl
2006-06-17 4:35 ` Pavel Roskin
2006-06-17 5:30 ` Keith Packard
2006-06-17 5:51 ` Jon Smirl
2006-06-17 17:13 ` Keith Packard
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=9e4733910606161444i2f996096sbd1f9b3f3ff3a32d@mail.gmail.com \
--to=jonsmirl@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).