public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com> To: yngves@sources.redhat.com Cc: gnats-prs@sourceware.cygnus.com Subject: Re: gnats/196: Not able to edit PRs Date: Thu, 23 Aug 2001 05:14:00 -0000 [thread overview] Message-ID: <20010823121400.15781.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR gnats/196; it has been noted by GNATS. From: Yngve Svendsen <yngve.svendsen@clustra.com> To: m_venkateshkumar@mindtree.com,gnats-gnats@sourceware.cygnus.com Cc: Subject: Re: gnats/196: Not able to edit PRs Date: Thu, 23 Aug 2001 14:09:07 +0200 At 06:20 23.05.2001 +0000, m_venkateshkumar@mindtree.com wrote: >I've created some PRs in various categories. The files reside with these >permissions: >-rw-rw-rw- 1 root root 1211 May 16 17:14 67 > >But, when I do an edit-pr 67, I get the following response from the >edit-pr program. : >pr-edit: Invalid PR pending/67. > > >The PR resides in the GCCS directory, not the pending directory. >My default submitter is root in the config file. >Another strange thing is that in the same directory, i have another PR >with number 66, with the SAME permissions >I am able to edit and modify 66, but not 67. This is just an example - its >happening to many other PRs as well. > >What could be the problem? >I'm attaching my categories file for reference. Are you still seeing this problem? I am fairly certain that this is due to your configuration, since the permissions and ownership of the file mentioned above looks highly suspicious. Yngve Svendsen Gnatsweb maintainer
next reply other threads:[~2001-08-23 5:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-23 5:14 Yngve Svendsen [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-09-12 15:29 yngves 2001-08-22 17:05 yngves 2001-05-22 23:24 m_venkateshkumar
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=20010823121400.15781.qmail@sourceware.cygnus.com \ --to=yngve.svendsen@clustra.com \ --cc=gnats-prs@sourceware.cygnus.com \ --cc=yngves@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: linkBe 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).