public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Release_2003_06_03 tag
Date: Mon, 23 Jun 2003 15:44:00 -0000	[thread overview]
Message-ID: <3EF71F2E.4050402@eCosCentric.com> (raw)
In-Reply-To: <1056381742.28422.863.camel@hermes>

Gary Thomas wrote:
> On Mon, 2003-06-09 at 12:14, Jonathan Larmour wrote:
> 
>>I just happened to notice a tag has appeared in the repository, 
>>Release_2003_06_03. That's not a big deal although I know no-one generally 
>>makes a public tag except for releases.
>>
>>The odd thing is that looking at the repository, the files tagged were 
>>last touched by user "anoncvs". That's very odd as that user shouldn't be 
>>allowed to make tags!
>>
>>So if someone knows where this tag came from, let me know. It doesn't need 
>>to be deleted - I just want to check there hasn't been something go wrong 
>>somewhere, especially if it means anoncvs users can change things!
>>
> 
> 
> Did you ever learn anything about this?  I know that I didn't do it :-)

Sort of: http://sources.redhat.com/ml/overseers/2003-q2/msg00243.html

and I've made a corrected version of the change there to CVSROOT/taginfo 
so it can't affect us again.

I'm actually not _that_ bothered if people wanted to make the odd tag, but 
deleting/moving tags is right out.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

      reply	other threads:[~2003-06-23 15:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 18:14 Jonathan Larmour
2003-06-23 15:31 ` Gary Thomas
2003-06-23 15:44   ` Jonathan Larmour [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=3EF71F2E.4050402@eCosCentric.com \
    --to=jifl@ecoscentric.com \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=gary@mlbassoc.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).