From: Christopher Faylor <cgf@redhat.com>
To: Jeffrey A Law <law@redhat.com>
Cc: matthew green <mrg@cygnus.com>, overseers@sources.redhat.com
Subject: Re: Request from matthew green
Date: Mon, 31 Dec 2001 19:40:00 -0000 [thread overview]
Message-ID: <20010117082322.C10642@redhat.com> (raw)
In-Reply-To: <18822.979697489@upchuck.cygnus.com>
On Tue, Jan 16, 2001 at 07:11:29PM -0700, Jeffrey A Law wrote:
>
> In message < 16185.979689352@cygnus.com >you write:
> >
> > This should mean that you can check things in and out of binutils. You'
> > ll
> > have to 'cvs login' as yourself, of course.
> >
> >
> > oh, i'm a moron. my failure was in an anoncvs checked out tree.
>Don't feel bad. That is the single most common mistake when trying to
>do a checkin after getting write privs...
Yep. I sent Matthew private email saying the same thing.
In fact, I feel like a moron myself for not thinking of this immediately...
cgf
WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@redhat.com>
To: Jeffrey A Law <law@redhat.com>
Cc: matthew green <mrg@cygnus.com>, overseers@sources.redhat.com
Subject: Re: Request from matthew green
Date: Wed, 17 Jan 2001 05:23:00 -0000 [thread overview]
Message-ID: <20010117082322.C10642@redhat.com> (raw)
Message-ID: <20010117052300.TsMfbJvWCiCDaUyRcqo3SHuLTFxb-LLdYqSfY8mEsTo@z> (raw)
In-Reply-To: <18822.979697489@upchuck.cygnus.com>
On Tue, Jan 16, 2001 at 07:11:29PM -0700, Jeffrey A Law wrote:
>
> In message < 16185.979689352@cygnus.com >you write:
> >
> > This should mean that you can check things in and out of binutils. You'
> > ll
> > have to 'cvs login' as yourself, of course.
> >
> >
> > oh, i'm a moron. my failure was in an anoncvs checked out tree.
>Don't feel bad. That is the single most common mistake when trying to
>do a checkin after getting write privs...
Yep. I sent Matthew private email saying the same thing.
In fact, I feel like a moron myself for not thinking of this immediately...
cgf
next prev parent reply other threads:[~2001-12-31 19:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 mrg
2001-01-16 14:31 ` mrg
[not found] ` <20010116223122.31244.qmail@sources.redhat.com>
2001-12-31 19:40 ` Christopher Faylor
2001-01-16 15:31 ` Christopher Faylor
2001-12-31 19:40 ` matthew green
2001-01-16 15:37 ` matthew green
2001-12-31 19:40 ` Christopher Faylor
2001-01-16 15:39 ` Christopher Faylor
2001-12-31 19:40 ` Christopher Faylor
2001-01-16 15:54 ` Christopher Faylor
2001-12-31 19:40 ` matthew green
2001-01-16 15:56 ` matthew green
2001-12-31 19:40 ` Jeffrey A Law
2001-01-16 18:15 ` Jeffrey A Law
2001-12-31 19:40 ` Christopher Faylor [this message]
2001-01-17 5:23 ` Christopher Faylor
2001-12-31 19:40 ` matthew green
2001-01-16 15:54 ` matthew green
2001-12-31 19:40 Request from Matthew Green mrg
2001-01-03 19:32 ` mrg
[not found] ` <20010104033238.20223.qmail@sources.redhat.com>
2001-12-31 19:40 ` Christopher Faylor
2001-01-03 19:49 ` Christopher Faylor
2001-12-31 19:40 ` matthew green
2001-01-03 20:24 ` matthew green
2001-12-31 19:40 ` Christopher Faylor
2001-01-03 22:00 ` Christopher Faylor
2001-12-31 19:40 ` Tom Tromey
2001-01-19 13:50 ` Tom Tromey
2001-12-31 19:40 ` Christopher Faylor
2001-01-19 22:21 ` Christopher Faylor
2001-12-31 19:40 ` matthew green
2001-01-03 22:05 ` matthew green
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=20010117082322.C10642@redhat.com \
--to=cgf@redhat.com \
--cc=law@redhat.com \
--cc=mrg@cygnus.com \
--cc=overseers@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).